A diagnostics lab receives orders across Epic/Cerner System APIs, partner HL7v2 feeds, and paper requisitions, and results have to reach the ordering clinician only after benefits are verified and any prior auth is cleared. This order-to-results blueprint carries every order through five integration-led stages: templatized System APIs and IDP for intake, Kno2/QHIN aggregation and agents for triage, Availity X12 and Da Vinci for verification, IDP and agents for appeals, and LIMS-driven execution with reconciled payment posting — landing each order as a Salesforce case that reaches a delivered result and a paid claim.
Tags: healthcare, provider, lims, x12, fhir, hl7v2, da-vinci, epic, cerner, salesforce, revenue-cycle
Diagnostic Order Management Lifecycle
Objective: A diagnostics lab receives orders across Epic/Cerner System APIs, templatized partner HL7v2 feeds, and paper requisitions, and a team resolves missing information, verifies benefits, and clears prior authorization before the sample is even processed. When a prior-auth deadline slips, the claim is denied and the result still has to go out. Working looks like every order landing as a structured case regardless of channel, missing information resolved by orchestration and agents, benefits and prior auth verified electronically, denials appealed with a generated letter, and results delivered and payment posted — with a human in the loop only where confidence or regulation demands it.
What's Getting Built
- Diagnostics System API (System API) — pulls Epic/Cerner ServiceRequest orders and writes the finished DiagnosticReport back to the ordering clinician's chart ·
GET /ServiceRequest, POST /DiagnosticReport
- Templatized HL7v2 Listener (System API) — terminates a per-partner HL7v2 ORM feed for referring practices that cannot consume FHIR ·
MLLP LISTEN ORM^O01, ACK^O01
- Order Intake Orchestration (Process API) — converges System API, HL7v2, and IDP-extracted paper orders onto one canonical order and opens the Salesforce case ·
POST /orders/intake, POST /orders/match
- Missing-Information Triage (Process API) — auto-resolves gaps via Kno2/QHIN record retrieval and NPI provider validation before routing to a work-guide queue ·
POST /triage/resolve, GET /qhin/records, GET /npi/{npi}
- Verification & Prior Auth (Process API) — runs Availity X12 eligibility and prior auth, modeling a deferred payer decision as a pending-determination state ·
POST /eligibility 270/271, POST /priorauth 278, POST /davinci/PAS
- Sapio / Clarity LIMS (target) — receives the structured order at intake and is the source of the DiagnosticReport delivered back once the sample clears ·
POST /order, GET /result/{orderId}
Prerequisites
- Anypoint Platform org with API Manager and a non-production deployment target.
- Salesforce Health Cloud (or Client Services) as the case system of record, with the Case model and work-guide orchestration configured.
- Epic and/or Cerner FHIR + HL7v2 System APIs reachable for Administration, Clinical, Diagnostics, and Medication resources.
- Intelligent Document Processing licensed and a document model trained on your requisition and payer-document types.
- Availity (or equivalent clearinghouse) connectivity with a trading-partner agreement and X12 companion guides in hand.
- LIMS endpoints reachable (Sapio, Clarity) with order-matching keys agreed (account / provider / patient / order).
- Kno2 / QHIN entitlement for the record-retrieval path, and NPI registry access for provider validation.
- Financial-institution connectivity for payment reconciliation — Wells Fargo (or equivalent) ERA/EFT feeds and a merchant service gateway.
- Named validation and compliance owner — this flow touches PHI end to end and a change-control path must exist before the first deployment.
Choose your path
- System API-first intake — Choose when the ordering source is Epic or Cerner — pull orders through the Administration, Clinical, Diagnostics, and Medication System APIs and skip document extraction entirely.
- Templatized HL7v2 intake — Choose when a referring practice or partner lab sends HL7v2 ORM feeds directly — deploy a templatized listener per net-new partner and reuse the existing order-matching logic.
- IDP-first intake — Choose when the channel is paper — faxed or emailed requisitions. Documents are categorized and extracted by IDP, low-confidence fields loop a human in, and structured orders are written to the LIMS and Salesforce.
Most labs run all three in parallel — every path converges on the same Order Intake Orchestration and the same case in Salesforce.
EHR vendor notes
Epic
- Pull orders from Epic System APIs scoped to Administration (patient, coverage), Clinical (notes, conditions), Diagnostics (ServiceRequest, DiagnosticReport), and Medication resources — one templatized System API per resource family, reused across partners.
- Deliver the finished result back through the same Diagnostics System API as a DiagnosticReport, so it lands in the ordering clinician's Epic chart without a portal login.
- Bridges ADT/ORM feeds remain the fallback for practices that cannot consume FHIR directly — route them through the templatized HL7v2 listener instead.
Cerner (Oracle Health)
- Pull orders from Millennium via the equivalent FHIR System APIs for Administration, Clinical, Diagnostics, and Medication resource groups — Cerner tenant-specific scopes need separate OAuth registration from Epic.
- Deliver results as a DiagnosticReport into PowerChart; validate MIME types and result-value units against Cerner's diagnostics module before commit.
- Where Cerner sites still send HL7v2 ORM, use the same templatized listener pattern as Epic — the canonical order model downstream is identical.
Architecture
1. Business requirements
- Capture every inbound order — Epic/Cerner System API, partner HL7v2, and paper — without a person opening and re-keying it.
- Resolve missing information fast enough to hit prior authorization deadlines, sometimes on the same day the order arrives.
- Verify benefits and submit prior authorization electronically, and treat a deferred payer decision as a first-class state.
- Turn a denial into an appeal automatically, with the evidence package assembled and the letter drafted.
- Deliver the result back to the ordering clinician and post payment only against confirmed funds, closing the order-to-results loop.
2. Order ingestion — System APIs, HL7v2, and paper
- On the electronic path, pull orders through the Epic/Cerner Diagnostics and Administration System APIs, or receive ORM through a templatized HL7v2 listener per partner; validate against trading-partner rules before translating to your canonical order.
- On the paper path, pick up the requisition via the fax/email API, let IDP categorize the document type, and extract the fields simultaneously.
- Gate on confidence: fields below the threshold route to the Customer Experience team for correction before promotion; clean extractions and System API orders flow straight through.
- Write the structured order to the LIMS (Sapio, Clarity) and open the Salesforce case — one Order Intake Orchestration regardless of channel.
3. Missing-information triage and outreach
- Create the case, route it to the correct queue, and start the orchestration on what the order is missing.
- Auto-resolve first: query QHIN/HIE via Kno2 for missing clinical or demographic data — the C-CDA to FHIR converter normalizes what comes back — and validate the provider against NPI before involving a human.
- Branch the work — billing errors to the billing team, consent/contact gaps to Customer Experience — each following its own work guide.
- Use an agent for outbound HCP outreach and to update the case when the reply arrives — templated, logged, and attributable.
4. Benefits verification and prior authorization
- Query Availity (or your clearinghouse) for eligibility (270/271) over X12 and land the result on the case as "ready for prior auth check."
- Where prior auth is required, submit the 278 and set the case to "pending determination"; reconcile the decision asynchronously when it returns.
- Where the payer supports it, drive the standards path — Da Vinci CRD, DTR, and PAS — rather than a payer-specific portal like Glidian; fall back to the portal only where the standards path isn't offered.
- Embed the eligibility and PA result directly in Salesforce so the specialist verifies from a single screen, following the Prior Auth work guide.
5. Denials, appeals, and results delivery
- Receive the Letter of Determination / EOB by fax or email and extract denial reasons and codes with IDP.
- Aggregate the supporting documents — clinical notes, pathology reports, payer-specific forms — from Telcor document management and RCM/content management.
- Push the denial codes and evidence to Salesforce/LIMS, and have the agent generate a unique appeal letter grounded in that package; a human approves before it is sent.
- Once the sample clears the LIMS, deliver the DiagnosticReport back to the ordering clinician through the same Epic/Cerner System API the order arrived on — no separate portal step for the common case.
- Reconcile ERA (835) against EFT through Wells Fargo (or your financial institution), poll for realized funds, and post to Xifin/RCM only once funds are confirmed; run non-standard remittances through IDP to extract payment and denial codes.
6. Security and compliance
- Encrypt PHI in transit and at rest.
- Audit-log every access to and modification of patient data.
- Enforce minimum-necessary access for integration operators and support users.
For additional HIPAA controls, API policies, and reference security patterns, see the MuleSoft Accelerator for Healthcare on Anypoint Exchange.
Sample payload — Canonical order after intake
{
"orderId": "ORD-2026-08-24-011203",
"source": "EPIC_SYSTEM_API",
"resourceType": "ServiceRequest",
"idp": { "documentType": null, "overallConfidence": null, "reviewStatus": "NOT_APPLICABLE" },
"patient": { "accountName": "Priya Nair", "memberId": "998214450", "groupId": "998214450" },
"provider": { "name": "David Cho", "npi": "1720384912", "signature": "SIGNED" },
"order": { "panel": "Comprehensive Metabolic Panel", "orderDate": "2026-08-24" },
"insurance": { "payer": "Anthem", "payerId": "54321", "priorAuthRequired": false },
"missingInformation": [],
"caseStatus": "READY_FOR_VERIFICATION"
}
Testing and validation
- Send the same order through the Epic System API, an HL7v2 partner feed, and a faxed requisition, and confirm all three converge to one case, not three, via the order-matching keys.
- Fax a requisition with one field below the confidence threshold and confirm it routes to human review and blocks promotion until corrected.
- Submit a prior auth that the payer defers, and confirm the case sits in "pending determination" and reconciles correctly when the decision returns hours later.
- Feed a denial letter with a reason code and confirm the appeal letter cites that code and the Telcor-aggregated evidence, and cannot be sent without human approval.
- Complete a LIMS result and confirm the DiagnosticReport lands back in the ordering clinician's Epic/Cerner chart before the case closes.
- Post an ERA that does not match the EFT and confirm the payment is held, not posted to Xifin, until funds are confirmed.
Phased rollout
Phase 1 — Connect
- Stand up the Epic/Cerner System API connections, Availity, and the LIMS/Salesforce connections and prove auth against a real non-production environment.
- Deploy IDP on one document type and one templatized HL7v2 listener for one partner; prove an order lands as a case all three ways.
Phase 2 — Map and test
- Map System API, HL7v2, and requisition payloads to your canonical order and validate against real historical documents.
- Turn on triage orchestration and Kno2/NPI auto-resolution for one order type, with agent outreach in assistive mode.
Phase 3 — Production
- Widen to all channels and document types, enable electronic prior auth and appeal-letter generation with human approval.
- Move results delivery and payment posting into production, and hand trace review and model monitoring to operations with named owners.
Success metrics
- Case triage time reduced against baseline — the deadline-miss rate on prior authorization is the number that decides whether claims get paid.
- Percentage of orders captured straight-through by System API or IDP without human correction, trending up as coverage matures.
- Prior authorization turnaround reduced and denial rate on submitted documentation trending down.
- Results delivered back to the ordering clinician's chart without a manual lookup, and days-in-AR reduced once payment posting is automated.
Configuration checklist
Before first sandbox deploy, complete the shared Healthcare integration configuration checklist — secure property keys, TLS, OAuth, and credential naming conventions are documented once for all Exchange use cases.
7. Implementation starting point
Stand up templatized System APIs for the Epic/Cerner Administration, Clinical, Diagnostics, and Medication resource families first — onboarding a new EHR partner is then configuration, not a new build.
Deploy one templatized HL7v2 listener for your highest-volume non-FHIR partner and reuse the same canonical order model the System API path writes to.
Configure Availity (or your clearinghouse) credentials in secure properties and wire the X12 270/271/278 path before turning on prior-auth triage.
Wire the LIMS (Sapio, Clarity) as both the intake write target and the source of the DiagnosticReport that gets delivered back to the ordering clinician.
Troubleshooting
- Duplicate cases for one order — Likely cause: System API, HL7v2, and fax paths not deduplicated on the order-matching keys. Fix: Match on account/provider/patient/order at intake and merge before case creation.
- IDP writes a wrong value instead of flagging it — Likely cause: confidence gate applied per document rather than per field. Fix: Threshold each field and loop a human in on any single low-confidence field, regardless of overall score.
- Prior auth appears to stall — Likely cause: synchronous expectation against a payer that responds asynchronously. Fix: Model "pending determination" as a state, correlate the response, and age the case with an alert.
- Result never reaches the ordering clinician's chart — Likely cause: DiagnosticReport delivery relied on a portal notification instead of writing back through the originating System API. Fix: Deliver the result on the same System API family the order arrived on, and treat portal delivery as the fallback for non-FHIR partners only.
- Appeal letter missing evidence — Likely cause: document aggregation ran before Telcor/content management finished indexing. Fix: Gate generation on aggregation completion and re-check the RCM/Telcor source before drafting.
- Payment posted against unconfirmed funds — Likely cause: ERA reconciled without the EFT/bank confirmation. Fix: Hold posting to Xifin until realized funds are confirmed by the financial institution.
Related blueprints
- Medical Device Order Management Lifecycle — the DME/device order-to-cash counterpart; this plan is diagnostics-lab-specific (LIMS, results delivery), that one carries a device order to shipment.
- Benefits and Eligibility Verification — the payer-side eligibility check this plan's verification stage draws on directly.
- Qualified Health Information Network Integration — the QHIN directed-query pattern this plan's triage stage uses via Kno2 to fill missing clinical data.
- Prior Authorization: CRD, DTR, and PAS — the Da Vinci standards path this plan's verification stage prefers over X12 278 where the payer supports it.
Deliverable: An end-to-end order-to-results blueprint for a diagnostics lab — templatized System APIs and IDP for intake, Kno2/QHIN and agents for triage, X12 and Da Vinci for verification, IDP and agents for appeals, and LIMS-driven execution — landing every order as a Salesforce case that reaches a delivered result and a paid claim, with a human in the loop only where it counts.