Generative AI-Powered Intelligent Document Processing for Healthcare Operations

myriad_genetics · Healthcare · 2025 · source Agentic: yes · promotional bias: med · source-backed · extracted with prompt 0.5.6 (schema v2)

Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.

Problem

Domain: healthcare document processing

Myriad Genetics needed to lower the cost and latency of healthcare document classification while automating manual key information extraction across complex medical forms for prior authorization workflows.

Constraints:

Architecture

Myriad and the AWS GenAI Innovation Center replaced the costly Textract-plus-Comprehend classifier with an AWS GenAI IDP Accelerator implementation using Pattern 2. Incoming order events retrieve documents, concurrency controls coordinate Step Functions jobs and SQS overflow, Textract extracts text/layout/tables/forms, Nova Pro classifies documents with optimized prompts, and Nova Premier performs key information extraction with multimodal document images, few-shot examples, and chain-of-thought style reasoning for ambiguous form marks. Structured results are delivered to Myriad's Authorization System, while the accelerator's evaluation framework, model benchmarks, and SME-refined prompts drive accuracy, latency, and cost optimization.

Diagram confidence: explicit (topology described by the source).

flowchart LR
  order_event_source["Order event source"] --> document_retrieval_and_cache["Document retrieval and cache"]
  source_document_systems["Source document systems"] --> document_retrieval_and_cache
  document_retrieval_and_cache --> concurrency_manager["Concurrency manager"]
  concurrency_manager --> sqs_overflow_queue["SQS overflow queue"]
  concurrency_manager --> step_functions_document_workflow["Step Functions document workflow"]
  sqs_overflow_queue --> step_functions_document_workflow
  step_functions_document_workflow --> amazon_textract_ocr["Amazon Textract OCR"]
  amazon_textract_ocr --> document_classification_service["Document classification service"]
  amazon_textract_ocr --> key_information_extraction_service["Key information extraction service"]
  genai_idp_configuration["GenAI IDP configuration"] --> document_classification_service
  genai_idp_configuration --> key_information_extraction_service
  document_classification_service --> amazon_bedrock_nova_pro["Amazon Bedrock Nova Pro"]
  amazon_bedrock_nova_pro --> document_classification_service
  document_classification_service --> vendor_routing["Vendor routing"]
  vendor_routing --> authorization_system["Authorization System"]
  key_information_extraction_service --> amazon_bedrock_nova_premier["Amazon Bedrock Nova Premier"]
  amazon_bedrock_nova_premier --> key_information_extraction_service
  key_information_extraction_service --> authorization_system
  evaluation_and_sme_loop["Evaluation and SME loop"] --> genai_idp_configuration
Drag to pan · scroll or use +/− to zoom · reconstructed from the source's described component topology

Components

Component Role Interacts with
Order event source Triggers document retrieval for incoming healthcare orders. Document retrieval and cache
Source document systems Existing document management systems that hold healthcare documents for order processing. Document retrieval and cache
Document retrieval and cache Fetches incoming documents and avoids reprocessing documents already available in cache. Concurrency manager
Concurrency manager Tracks concurrent processing jobs and decides which files run immediately or wait in queue. SQS overflow queue, Step Functions document workflow
SQS overflow queue Queues files that exceed configured concurrency limits until the workflow can process them. Step Functions document workflow
Step Functions document workflow Serverless orchestration layer that coordinates OCR, classification, extraction, and output delivery. Amazon Textract OCR, Document classification service, Key information extraction service
Amazon Textract OCR Extracts document text, layout, tables, forms, and checkbox-relevant visual structure. Document classification service, Key information extraction service
GenAI IDP configuration Stores document classes, key attributes, model choices, hyperparameters, and prompts for Pattern 2. Document classification service, Key information extraction service
Document classification service Uses Amazon Nova Pro on Amazon Bedrock to classify extracted document content into operational classes. Amazon Bedrock Nova Pro, Vendor routing
Amazon Bedrock Nova Pro Cost-effective low-latency foundation model selected for document classification. Document classification service
Key information extraction service Uses Amazon Nova Premier with multimodal evidence, few-shot examples, and reasoning prompts to extract healthcare fields. Amazon Bedrock Nova Premier, Authorization System
Amazon Bedrock Nova Premier Higher-reasoning foundation model selected for complex medical information extraction. Key information extraction service
Vendor routing Routes classified documents to appropriate external vendors based on document class. Authorization System
Authorization System Receives structured document-processing results for downstream prior authorization workflows. —
Evaluation and SME loop Uses expected outputs, benchmarks, and subject matter expert refinement to improve prompts, model choices, and configuration. GenAI IDP configuration

Data flow

Incoming order events pull documents from source management systems, reuse cached documents where possible, and enter a concurrency-managed Step Functions pipeline. Textract normalizes visual and textual document evidence, Nova Pro classifies the document from configured prompts, Nova Premier extracts medical fields using text plus visual examples for difficult forms, and structured output is sent through REST operations to Myriad's Authorization System. Evaluation data and SME review feed prompt, model, and configuration updates.

3 supporting quotes
“Document Ingestion: Incoming order events trigger document retrieval from source document management systems, with cache optimization for previously processed documents.”article, stated
“Classification: The configured LLM analyzed the extracted content based on the customized document classification prompt provided in the config file”article, stated
“Structured Output: The pipeline formatted the results in a structured manner and delivered to Myriad’s Authorization System via RESTful operations.”article, stated

Why this architecture

Pattern 2 gave Myriad the low-cost, configurable path needed for complex healthcare documents: Textract preserved document structure, Bedrock models handled semantic classification and extraction, Nova Pro optimized classification cost and latency, Nova Premier supplied stronger reasoning for ambiguous visual extraction, and the accelerator's built-in evaluation and configuration loops let the team tune prompts and model choices without rebuilding the whole system.

3 supporting quotes
“Pattern 2 proved most suitable for this project, meeting the critical requirement of low cost while offering flexibility to optimize accuracy through prompt engineering and LLM selection.”article, stated
“This pattern offers a no-code configuration – customize document types, extraction fields, and processing logic through [configuration]”article, stated
“Amazon Nova Pro achieved optimal balance for Myriad’s use case.”article, stated

Models used: Amazon Nova Pro · Amazon Nova Premier · Anthropic Claude Sonnet 3.7 · Amazon Bedrock

Scale

Alternatives considered (roads not taken)

Keep the Textract plus Amazon Comprehend classifier

Rejected because: It already reached 94% accuracy, but its cost and 8.5-minute latency created operational bottlenecks.

“Their existing solution combined Amazon Textract for Optical Character Recognition (OCR) with [Amazon Comprehend]”article, stated
“Despite 94% classification accuracy, this solution had operational challenges:”article, stated

Use the fully managed Bedrock Data Automation pattern

Rejected because: Pattern 1 was recommended for most use cases, but Myriad needed Pattern 2's lower cost and flexibility for custom prompt and model optimization.

“Uses Amazon Bedrock Data Automation, a fully managed service that offers rich out-of-the-box features, ease of use, and straightforward per-page pricing.”article, stated
“Pattern 2 proved most suitable for this project, meeting the critical requirement of low cost while offering flexibility to optimize accuracy through prompt engineering and LLM selection.”article, stated

Use a specialized SageMaker classification model in Pattern 3

Rejected because: Pattern 3 is positioned for specialized classification, while Myriad's best fit was Pattern 2's Textract plus Bedrock configurability.

“Pattern 2 proved most suitable for this project, meeting the critical requirement of low cost while offering flexibility to optimize accuracy”article, stated

Classify documents from text content alone

Rejected because: Similar healthcare documents shared content, so the team added format-based cues and negative prompts to capture layout and class-specific exclusions.

“We used document structure and formatting as key differentiators to distinguish between similar document types that shared comparable content but differed in structure.”article, stated
“This approach added exclusionary language to classification prompts, specifying characteristics that should not be associated with each document type.”article, stated

Run key information extraction with text-only OCR and prompts

Rejected because: Checkboxes and ambiguous visual marks required document images, few-shot visual examples, and reasoning over mark positions.

“Configuring Textract and improving prompts alone could not handle complex visual elements effectively.”article, stated
“We implemented a multimodal approach that sent both document images and extracted text from Textract to the foundation model”article, stated

Patterns

tool-use-orchestration (document workflow)

The production pipeline orchestrates document retrieval, concurrency management, queues, Step Functions workflows, Textract OCR, Bedrock model calls, vendor routing, and REST delivery into an authorization system.

“Text Extraction: Amazon Textract extracted text, layout information, tables and forms from the normalized documents.”article, stated
“The pipeline formatted the results in a structured manner and delivered to Myriad’s Authorization System via RESTful operations.”article, stated

structured-output-contract (document extraction)

The system defines document classes, extraction fields, key attributes, and prompts in configuration, then emits structured results for prior authorization workflows.

“customize document types, extraction fields, and processing logic through configuration”article, stated
“We customized the definitions of document classes, key attributes and their definitions per document class, LLM choice, LLM hyperparameters, and classification and extraction LLM prompts”article, stated

model-routing (cost and reasoning fit)

Myriad used different Bedrock models for different document-processing subtasks: Nova Pro for low-latency classification, Nova Premier for complex key information extraction, and Claude Sonnet 3.7 reasoning to identify class differentiators.

3 supporting quotes
“Amazon Nova Pro: A cost-effective, low-latency model ideal for document classification”article, stated
“Amazon Nova Premier: An advanced model with reasoning capabilities for information extraction”article, stated
“we provided document samples from each class to Anthropic Claude Sonnet 3.7 on Amazon Bedrock with model reasoning enabled”article, stated

eval-driven-development (benchmarking and iteration)

The team used the accelerator's evaluation framework, 1,200-document model benchmarks, 32-sample KIE testing, human baselines, and accuracy/cost/latency metrics to choose models and tune prompts.

“Its built-in evaluation framework](https://github.com/aws-solutions-library-samples/accelerated-intelligent-document-processing-on-aws/blob/main/docs/evaluation.md) lets users provide expected output through the user interface (UI)”article, stated
“We tested four foundation models—Amazon Nova Lite, Amazon Nova Pro, Amazon Nova Premier, and Anthropic Claude Sonnet 3.7—using 1,200 healthcare documents”article, stated

data-quality-loop (prompt and class refinement)

Class definitions, negative prompts, visual cues, and few-shot examples were refined from sample documents, model reasoning output, and subject matter expert review.

“The model identified distinguishing features between similar document classes, which Myriad’s subject matter experts refined and incorporated”article, stated
“By providing explicit guidance on common misclassification patterns, the system avoided typical errors and confusion between similar document types.”article, stated

cost-aware-routing (model and prompt cost control)

The architecture routes classification to the cheaper Nova Pro model, reserves Nova Premier for complex extraction, uses Pattern 2 for low-cost flexibility, and applies prompt caching for lengthy few-shot examples.

“Amazon Nova Pro achieved optimal balance for Myriad’s use case.”article, stated
“Prompt caching stores lengthy few-shot examples in memory for 5 minutes—when processing multiple similar documents within that timeframe, Bedrock reuses cached examples”article, stated

guardrails-io-filtering (classification constraints)

Negative prompts acted as explicit exclusion rules for confusing document classes, preventing the classifier from treating patient-history forms as lab measurements.

“This approach added exclusionary language to classification prompts, specifying characteristics that should not be associated with each document type.”article, stated
“DO NOT confuse them with test results which contain current/recent lab measurements”article, stated

Tradeoffs

Choose the configurable accelerator pattern.

Chose Pattern 2 with Textract and Bedrock models over Pattern 1 Bedrock Data Automation or Pattern 3 SageMaker classification.

Rationale: Pattern 2 balanced low cost, custom prompt/model optimization, and complex-document flexibility without requiring the specialized classification path of Pattern 3.

“Pattern 2 proved most suitable for this project, meeting the critical requirement of low cost while offering flexibility to optimize accuracy”article, stated
“This pattern is ideal for complex documents requiring custom logic.”article, stated

Split models by document-processing task.

Chose Nova Pro for classification and Nova Premier for extraction over Using one model for both tasks.

Rationale: Classification prioritized low cost and latency, while extraction needed stronger reasoning for ambiguous visual and clinical evidence.

“Amazon Nova Pro: A cost-effective, low-latency model ideal for document classification”article, stated
“Amazon Nova Premier: An advanced model with reasoning capabilities for information extraction”article, stated

Add visual context and few-shot examples to KIE.

Chose Multimodal document images plus extracted text and examples over Textract text and prompt improvements alone.

Rationale: The extra context was necessary for form layouts, checkbox marks, and ambiguous visual evidence that text-only processing could not handle.

“Configuring Textract and improving prompts alone could not handle complex visual elements effectively.”article, stated
“We implemented few-shot learning”article, stated

Use explicit negative prompts for classification.

Chose Exclusionary class definitions over Positive-only class descriptions.

Rationale: Negative prompts reduced confusion where forms and results shared patient-history language but represented different document classes.

“We implemented negative prompting techniques to resolve confusion between similar documents by explicitly instructing the model what classifications to avoid.”article, stated
“Adding a negative prompt like “These forms contain patient medical history. DO NOT confuse them with test results which contain current/recent lab measurements””article, stated

Roll out classification first.

Chose Phased rollout beginning with document classification in Women’s Health over Immediate broad deployment of classification and KIE across all business units.

Rationale: The article reports a staged business rollout, letting Myriad begin with the validated classification savings before expanding across Oncology and Mental Health.

“Myriad has planned a phased rollout beginning with document classification.”article, stated
“They plan to launch our new classification solution in the Women’s Health business unit, followed by Oncology and Mental Health divisions.”article, stated

Gotchas (what bit them)

A high-accuracy classifier was still too slow and expensive for operational workflows.

Root cause: The legacy Textract-plus-Comprehend system reached 94% accuracy but cost 3 cents per page and took 8.5 minutes per document, delaying prior authorization.

Resolution: Benchmark and migrate classification to Nova Pro with optimized prompts, lowering cost and latency while improving accuracy.

“Despite 94% classification accuracy, this solution had operational challenges:”article, stated
“classification accuracy increased from 94% to 98%, processing costs decreased by 77%, and processing speed improved by 80%”article, stated

Manual key information extraction did not scale across nuanced healthcare forms.

Root cause: Medical forms required contextual interpretation of clinical distinctions, variable formats, and patient or insurance fields that were hard to locate consistently.

Resolution: Automate KIE with Textract, multimodal LLM input, Nova Premier reasoning, and few-shot visual examples.

“Information extraction was entirely manual, requiring contextual understanding to differentiate critical clinical distinctions (like “is metastatic” versus “is not metastatic”)”article, stated
“We implemented a multimodal approach that sent both document images and extracted text from Textract to the foundation model”article, stated

Similar healthcare documents caused semantic classification ambiguity.

Root cause: Document types shared content and formatting patterns, so simple content matching confused forms, reports, and results.

Resolution: Use model-assisted prompt engineering, document-format cues, and negative prompts that define what each class is not.

“misclassifications occurred due to structural similarities, overlapping content, and shared formatting patterns across document types.”article, stated
“Adding a negative prompt like “These forms contain patient medical history. DO NOT confuse them with test results which contain current/recent lab measurements””article, stated

Checkbox extraction failed on visual ambiguity that text prompts alone could not resolve.

Root cause: Medical forms contained checkmarks, X marks, handwritten marks, overlapping marks, and content spanning multiple fields.

Resolution: Enable Textract TABLES and FORMS, add visual cue instructions, send images plus text to the model, and use reasoning prompts for ambiguous tick marks.

“checkbox fields required distinguishing between marking styles (checkmarks, X’s, handwritten marks); documents contained ambiguous visual elements like overlapping marks”article, stated
“Configuring Textract and improving prompts alone could not handle complex visual elements effectively.”article, stated

Few-shot visual examples improved extraction but made prompts long enough to affect cost and latency.

Root cause: Multiple document images and expected outputs had to be included so the model could learn form layouts and marking styles.

Resolution: Use Amazon Bedrock prompt caching to reuse the lengthy examples for similar documents processed within a five-minute window.

“Multiple document image examples with their correct extraction patterns create lengthy LLM prompts.”article, stated
“Prompt caching stores lengthy few-shot examples in memory for 5 minutes—when processing multiple similar documents within that timeframe, Bedrock reuses cached examples”article, stated

Evaluation

Myriad evaluated the system with the GenAI IDP Accelerator's expected-output UI, model benchmarking over 1,200 healthcare documents, classification accuracy/latency/cost comparisons, KIE testing over 32 samples, and comparison against a human evaluator baseline.

Metrics: existing classifier accuracy: 94% · Nova Pro classifier accuracy: 98% · classification cost reduction: 77%, from 3.1 to 0.7 cents per page · classification latency reduction: 80%, from 8.5 to 1.5 minutes per document · model benchmark: 1,200 healthcare documents across three classes · KIE test set: 32 document samples · KIE accuracy: 90%, matching the human evaluator baseline · KIE processing time: approximately 1.3 minutes per document · KIE cost: 9 cents per page

3 supporting quotes
“We assessed each model using three critical metrics: classification accuracy, processing latency, and cost per document.”article, stated
“classification accuracy increased from 94% to 98%, processing costs decreased by 77%, and processing speed improved by 80%”article, stated
“The solution achieved 90% accuracy (same as human evaluator baseline accuracy) while processing documents in approximately 1.3 minutes each.”article, stated

Outcomes

The solution targets thousands of daily healthcare documents across Myriad's Women’s Health, Oncology, and Mental Health divisions, with a first rollout in Women’s Health prior authorization workflows.

4 supporting quotes
“We increased accuracy from 94% to 98% through prompt optimization techniques for Amazon Nova Pro”article, stated
“We reduced classification costs by 77% (from 3.1 to 0.7 cents per page) by migrating from Amazon Comprehend to Amazon Nova Pro”article, stated
“We reduced classification time by 80% (from 8.5 to 1.5 minutes per document) by choosing Amazon Nova Pro”article, stated
“Myriad will realize up to $132K in annual savings in their document classification costs.”article, stated