Blogs, Genomics

The Order-to-Report Control Plane: What Complex Diagnostic Labs Need Between the EHR, LIS, LIMS, and Billing Stack

Lab technician scanning a specimen barcode during accessioning

Ask five people in a complex diagnostic lab one question:

What is the current, authoritative status of this patient’s test?

The ordering clinician may see an order in the EHR. The interface analyst may see an acknowledged HL7 message. The accessioning team may see a specimen on hold. The bioinformatics team may not see a case in its queue. Billing may see a prior authorization task without an accession number.

Each answer can be accurate within its own system. None may answer the question that matters:

Is the case ready, blocked, reportable, delivered, or financially actionable?

That is not simply a dashboard issue. It may not be a single interface failure.

It is a failure to manage the shared state of a case as it moves through the EHR, interface engine, LIS, LIMS, specimen workflow, pipeline, clinical review, reporting, result delivery, and billing.

Direct answer

A diagnostic lab workflow control plane is an engineering layer that connects the identity, status, rules, exceptions, ownership, and audit record of a case across the EHR, LIS, LIMS, pipeline, reporting, and billing systems. It does not replace those applications. It enables the lab to determine what happened, what is blocked, and what must happen next.

Under 42 CFR § 493.1291, a laboratory must maintain adequate manual or electronic systems that send test results and patient-specific data accurately, reliably, and in a timely manner from entry to the final report destination. The rule applies to data handled through interfaced systems as well as manually entered information.

The operating test is straightforward:

Can the lab reconstruct the case, show what blocked it, identify who owns the next action, and demonstrate how the result moved from order to final report?

For molecular, genetic, genomic, pathology, and specialty labs, that task is often harder than it should be.

A workflow control plane is not a CLIA-defined system category. It is an engineering term for the layer that coordinates shared case identity, readiness rules, state changes, exceptions, ownership, and audit evidence across existing systems.

It does not replace the EHR, LIS, LIMS, laboratory quality program, assay validation process, or clinical sign-out authority. It makes the handoffs among those systems visible, actionable, and traceable.

Building or modernizing a connected lab workflow?

Explore NonStop’s clinical genomics and lab workflow solutions for systems that support intake, processing, analysis, reporting, and result delivery.

Why a Valid EHR Order Can Still Be Unusable for the Laboratory

An HL7 v2 acknowledgment or a structurally valid FHIR resource does not, by itself, confirm that an incoming order maps to the correct laboratory test. An EHR may send a LOINC code, a local order code, or both; the lab must reconcile that code with its active test catalog. A missing, outdated, or incorrect mapping can leave an otherwise well-formed order unable to route to the intended assay—or route it incorrectly. LOINC recommends sending local codes alongside LOINC codes to help detect mapping errors. LOINC’s mapping guidance explains this distinction.

The lab needs an order that is operationally usable.

FHIR separates the request, discrete results, and final report:

  • ServiceRequest represents a request or order for diagnostic work.
  • Observation represents discrete laboratory or diagnostic findings.
  • DiagnosticReport provides the context for reporting those findings.

The lab workflow has similar distinctions. An order can be received but not accepted. A specimen can arrive but not be accessioned. A pipeline can finish, but the case can remain unreportable. A report can be signed but fail to reach the ordering provider.

The key question is not: Did the order reach the lab?

It is: Does the order code map to the intended active test, and do the patient identifiers, specimen, required documentation, and other lab-defined intake rules allow the case to proceed?

Intergenix addresses this intake gap. It checks incoming EHR orders against lab-specific validation rules, detects duplicate retries, reports field-level failures, and routes exceptions to an operational worklist. Its EHR-to-LIMS mappings are tailored for each lab; it should not be assumed to verify consent, payer authorization, or specimen readiness unless those checks are explicitly configured and the necessary data is available.

That is the difference between message transport and diagnostic lab workflow integration.

Why “Order Received” Does Not Confirm That a Case Is Ready to Process

Displayed statusActual conditionLikely consequence
Order receivedPatient identity does not reconcile with the downstream recordAccessioning or reporting is blocked
Order receivedTest code maps to an inactive assay configurationThe wrong workflow, report template, or payer rule may be used
Order receivedConsent, medical necessity, or referral data is incompleteStaff must intervene before work proceeds
Specimen receivedThe specimen cannot be matched to a valid order and testThe lab holds, rejects, recollects, or manually reconciles it
Pipeline completeClinical review, phenotype, or sign-out is incompleteThe result cannot be released
Report signedResult delivery failedThe provider may not receive the report
Claim createdBilling lacks current clinical or accession contextRevenue-cycle work begins with incomplete information

A lab can have functioning interfaces and still have a fragmented case lifecycle.

No Single System Can Reliably Own the Full Diagnostic Case State

An EHR owns the clinical order. An LIS may own accessioning and laboratory processing. A LIMS may manage specimens, batches, instruments, and QC events. A pipeline platform owns analytical execution. A reporting tool manages sign-out and report output. Billing systems manage payer and claim activity.

Each application has a valid role.

The issue is the gap between them.

A workflow control plane manages the information that must remain consistent across the case lifecycle.

Cross-system questionWhy one application cannot always answer itWhat the workflow layer does
Is this the same patient, order, specimen, accession, case, report, and claim?IDs are created and updated in different systemsMaintains crosswalks, relationships, source information, and timestamps
Is the test ready to perform?Consent, test configuration, specimen, and payer data may be distributedApplies readiness rules before downstream work starts
What is blocking the case?Technical logs rarely show clinical or operational impactClassifies exceptions, assigns owners, and measures queue age
Can the specimen proceed?A barcode confirms presence, not full workflow readinessReconciles specimen status with order, test, and accession rules
Is the result reportable?Pipeline completion differs from review, sign-out, release, and deliveryTracks each state separately
Can billing act safely?Billing needs status but should not own clinical truthSends governed status and minimum necessary context

The control plane is not another dashboard. A dashboard is a view.

The control plane is the event model, rules engine, exception workflow, identifier crosswalk, ownership model, and audit record that make that view dependable.

Most labs already have identifiers. The challenge is keeping them connected as a case moves across systems.

A complex diagnostic case may include:

  1. Patient
  2. Order
  3. Requisition
  4. Specimen
  5. Accession
  6. Assay
  7. Run
  8. Interpretation Case
  9. Report
  10. Result Delivery
  11. Claim

These are different objects.

A patient can have multiple orders. One order can include multiple specimens. A specimen can support more than one assay. Many cases can share a sequencing run. A report can be amended after release.

The same case can also generate a counseling task, payer exception, recontact record, or clinical decision-support event.

A durable workflow model preserves:

  • Source-system IDs
  • A crosswalk among patient, order, specimen, accession, run, case, report, and claim IDs
  • Parent-child relationships
  • Current and historical states
  • Event timestamps
  • The person, system, or rule that changed the state
  • Active assay, consent, and report-template versions

FHIR is useful as a modeling discipline, even in labs that rely mainly on HL7 v2 or proprietary APIs. ServiceRequest represents the initial request.

Diagnostic Report represents the report that fulfills it.

Diagnostic Report can reference Observations that contain discrete results.

The point is not to force every internal record into FHIR. The point is to make system relationships explicit.

Why “In Process” Is Too Vague to Manage Turnaround Time

“In process” is not a useful state for a complex lab.

It may mean the case is waiting for consent. It may mean the specimen is waiting for reconciliation. It may mean the assay is waiting for batch placement. It may mean the pipeline is waiting for compute. It may mean a second reviewer has not signed off. It may mean the report is ready, but delivery failed.

Those situations need different owners.

Workflow domainExample stateTypical ownerRequired evidence
Order readinessIncomplete order, duplicate suspected, consent mismatchIntake, client services, genetic counselingMissing data, rule triggered, source, owner, due date
Specimen and accessionReceived, held, rejected, accessionedLab operationsSpecimen ID, receipt time, match result, disposition
Analytical executionQueued, running, QC failed, completeBioinformatics, technical lab teamRun ID, workflow version, QC state, retry event
Clinical review and reportingReview pending, second review, report signed, amendment pendingAnalyst, medical director, reporting teamEvidence state, reviewer, decision, report version
Delivery and financial operationsDelivered, delivery exception, authorization pending, claim-readyInformatics, client services, billingDestination, delivery confirmation, payer task, shared case status

A universal state model is not the goal. Each lab has its own assays, roles, and policies.

The goal is to make local states precise enough to manage.

Need to validate EHR-originated orders before they become downstream exceptions?

We have designed Intergenix for EHR order validation, HL7/FHIR synchronization, deduplication, and operational worklists

Four Workflow Handoffs Where EHR, LIS, LIMS, and Billing Integration Breaks Down

An EHR Test Order Is Not the Same as an Executable Laboratory Test

An EHR order is a clinical request. A lab must turn that request into an executable configuration.

That configuration may include:

  • The active assay or panel version
  • Specimen requirements
  • Diagnosis, indication, or phenotype requirements
  • Consent requirements
  • Prior authorization or payer rules
  • Analytical workflow
  • Report template
  • Sign-out and delivery rules

The mapping can sit across the EHR, test catalog, requisition, LIS, LIMS, billing system and report engine.

This creates configuration debt. A change to one assay can affect order validation, consent, sample routing, payer logic, pipeline settings, and report language.

A workflow control plane validates more than the incoming test code. It verifies that the patient, order, assay version, specimen, and required documents meet the current rules for that case.

SmartReq addresses this upstream control point. It extracts requisition data and passes confirmed information into downstream workflows.

Specimen Receipt Should Not Override Order, Consent, or Test-Readiness Rules

Specimen receipt creates urgency. It should not force a lab to bypass controls.

A barcode identifies a container. It does not prove that the specimen belongs to the correct patient, support the requested assay, or have all required documentation.

The workflow should record what happened from receipt through acceptance, hold, rejection, recollection and release into downstream work.

CLIA test-report requirements include patient identification, the test performed, the report date, specimen source where appropriate, and the disposition of specimens that do not meet the lab’s acceptability criteria. 42 CFR § 493.1291(c).

A reliable report depends on a reliable preanalytic record.

A Completed Bioinformatics Pipeline Does Not Mean the Result Is Ready for Release

A pipeline can complete successfully. The patient's result can still be blocked.

The missing step may be:

  • Phenotype or clinical context
  • Additional variant review
  • Second review
  • A correct assay-to-template mapping
  • Structured-result assembly
  • Clinical sign-out
  • EHR delivery
  • Reconciliation with the original order

The lab must separate these states:

  1. Pipeline complete
  2. Clinical review complete
  3. Report signed
  4. Result delivered

A lab that tracks only pipeline runtime cannot see why a final report is late.

Explore NonStop’s genomics infrastructure and integration engineering for HL7 v2, FHIR R4, Mirth Connect, EHR integration, cloud infrastructure, and clinical-genomics workflow delivery.

Billing Systems Need Case Status Without Becoming the Clinical Source of Truth

Billing, CRM, payer, and prior-authorization systems need context. They may need the test, accession, diagnosis, payer, ordering source, authorization status, and delivery milestone.

They should not own the clinical order, specimen, interpretation or report state.

The architecture needs clear boundaries:

  • Laboratory systems own clinical order, specimen, accession, assay, review, report, and release states
  • Revenue-cycle systems receive the information needed for eligibility, authorization, claims, and exception work
  • Shared IDs keep related records connected
  • Status moves through defined events and rules
  • Role-based controls limit access to the necessary information

This is important when a lab uses XiFin, Quadax, Salesforce, clearinghouses, portals, and payer systems alongside the EHR, LIS, LIMS, and reporting stack.

The objective is not one database. It is reliable context across systems.

Use Recent Exceptions to Find the Actual Breaks in Your Order-to-Report Workflow

A major replacement project is not always the right first move.

Start with 20 to 30 recent cases that required manual intervention, missed turnaround time, sat in an exception queue, needed a corrected report, or created a billing-status issue.

For each case, ask:

  1. Could the lab connect the patient, order, specimen, accession, assay, report and payer event?
  2. Could staff find the current operational state without opening several systems?
  3. Was the blocking condition visible, assigned and time-bound?
  4. Could the lab show which rule, system, or person changed the state?
  5. Did the report reach the intended recipient?
  6. Did billing receive what it needed without becoming the clinical source of truth?

The answers reveal whether the lab has an isolated interface issue or a broader workflow-control problem.

Some labs need a clear identifier crosswalk and readiness rules. Others need exception worklists, state management, status propagation, controlled reporting, or a workflow layer around legacy systems.

The engineering decision should follow the evidence.

Build a Governed Case Record Before the Next Workflow Failure Becomes Manual Rework

The goal is not a better integration diagram.

The goal is a governed case record that answers:

  • What test was requested, and under which active configuration?
  • Which specimen, accession, assay, and run belong to the case?
  • What has completed?
  • What is blocked?
  • Who owns the next action?
  • What supports clinical review and report release?
  • Did the final report reach the right destination?
  • What status can safely flow to billing and payer systems?
  • Can the lab reconstruct the case later?

That record is the foundation of reliable diagnostic lab workflow integration.

NonStop engineers this workflow layer around the systems a lab already uses.

SmartReq reads, extracts, validates, and audit-logs requisition data before incomplete information moves into downstream laboratory workflows.

Intergenix validates EHR orders, detects duplicate orders, synchronizes HL7 v2 and FHIR R4 workflows, manages field-level validation failures, and routes operational exceptions into worklists.

NonStop also designs the integration and platform architecture that connects the EHR, LIS, LIMS, pipeline, clinical review, reporting, result delivery, billing, and portal layers. NonStop’s genomics infrastructure and integration engineering cover HL7 v2, FHIR R4, Mirth Connect, Epic, Cerner, cloud infrastructure, and clinical-genomics workflow requirements.

Identify the Workflow Gaps Before You Commit to a Major Lab Systems Project

A complex diagnostic workflow does not always require a full platform replacement.

It may require targeted changes in:

  • Requisition validation
  • Test-catalog governance
  • Patient, order, specimen, and accession reconciliation
  • Exception routing and workflow ownership
  • Integration monitoring and state management
  • Pipeline-to-report handoffs
  • Reporting and result-delivery controls
  • Billing-status propagation and payer workflow integration

NonStop starts by mapping those breakpoints across the order-to-report workflow. The work identifies which system owns each state, which information must be reconciled, where manual work accumulates, and which engineering changes will reduce operational risk.

Book a 45-Minute Architecture Review

NonStop’s 45-minute Architecture Review gives lab, informatics, bioinformatics, reporting, and revenue-cycle leaders a structured view of the systems, identifiers, rules, exceptions, and handoffs affecting the order-to-report path.

The review defines:

  • The current system and identifier map
  • Workflow states with no reliable owner or source of truth
  • Exception categories that create manual reconciliation and turnaround-time risk
  • Gaps between order readiness, accessioning, pipeline completion, clinical review, report release, and result delivery
  • The highest-priority workflow, integration, and platform changes

Frequently Asked Questions About Diagnostic Lab Workflow Integration

What is a diagnostic lab workflow control plane?

A diagnostic lab workflow control plane is an engineering layer that coordinates shared case identity, workflow states, readiness rules, exceptions, owners, and audit history across the EHR, LIS, LIMS, bioinformatics pipeline, reporting system, and billing tools.

It does not replace those systems. It connects the workflow states that no single application can reliably manage on its own.

Does a diagnostic lab need to replace its LIS or LIMS to build a control plane?

Not necessarily.

Many labs begin by preserving their existing LIS, LIMS, EHR, billing, or reporting systems. The first engineering step is to identify where the workflow breaks between them.

A lab may need an identifier crosswalk, rules engine, exception worklist, status model, integration layer, or reporting control. A full platform replacement becomes relevant only when the current architecture cannot support the required workflow, volume, assay changes, auditability, or integration needs.

What is the difference between EHR integration and diagnostic lab workflow integration?

EHR integration moves orders, demographics, results, and related information between systems. Diagnostic lab workflow integration goes further.

It ensures that the order, specimen, accession, assay, clinical review, report, delivery status, and financial workflow remain connected through a governed case record.

An HL7 message can be accepted while the case is still unusable. The workflow layer identifies why it is unusable, who owns the next step, and what must happen before the case proceeds.

Which HL7 and FHIR resources matter in an order-to-report workflow?

In a typical laboratory workflow:

  • HL7 v2 ORM messages commonly carry order information.
  • HL7 v2 ORU messages commonly carry result information.
  • HL7 v2 ADT messages communicate patient admission, discharge, transfer, and demographic events.
  • FHIR ServiceRequest represents a request for a diagnostic service.
  • FHIR Specimen represents the specimen used for testing.
  • FHIR Observation represents discrete result data.
  • FHIR DiagnosticReport represents the final report and its clinical context.
  • FHIR Task can model workflow assignments and actions.
  • FHIR Provenance can record the source and history of information.

The right implementation depends on the lab’s EHR, LIS/LIMS, interface engine, reporting model, and clinical workflow. HL7’s FHIR ServiceRequest documentation describes a service request as an order or request for a service that may result in an Observation, DiagnosticReport, Procedure, or similar outcome.

What should a diagnostic lab track to reduce turnaround-time risk?

A lab should track the handoffs that occur before and after analytical testing, not only pipeline runtime.

Useful metrics include:

  • Order-receipt-to-readiness time.
  • Specimen-receipt-to-accession time.
  • Exception queue age by category.
  • Duplicate-order resolution time.
  • Time from pipeline completion to clinical review.
  • Time from clinical review to report sign-out.
  • Time from signed report to confirmed delivery.
  • Failed result-delivery events.
  • Number of manual reconciliation steps per case.
  • Exception rates by assay, site, referring provider, interface, and payer.

These measures help distinguish a true analytical bottleneck from an order, specimen, review, reporting, delivery, or revenue-cycle bottleneck.

Can billing or CRM systems become the source of truth for a diagnostic case?

No. Billing and CRM systems need workflow context, but they should not become the authoritative source for clinical order, specimen, interpretation, report, or release status.

The clinical and laboratory workflow should retain ownership of clinical case state. Billing, payer, and CRM tools should receive only the information needed for eligibility, prior authorization, claim processing, exception handling, and commercial operations.

Shared identifiers and governed status changes allow those systems to remain connected without creating conflicting versions of the case.

What does an order-to-report workflow assessment include?

A useful assessment should examine:

  • Existing systems across EHR, LIS, LIMS, interface engine, pipeline, reporting, portal, billing, and CRM.
  • Patient, order, specimen, accession, case, report, and claim identifiers.
  • Order-readiness rules and test-catalog dependencies.
  • Exception categories, owners, escalation paths, and queue aging.
  • Pipeline-to-review-to-report handoffs.
  • Result-delivery confirmation and reconciliation.
  • Billing and payer-status propagation.
  • The highest-priority changes to reduce manual work and TAT risk.