Orders and acknowledgements
Define order creation, update and cancellation where supported. Track whether the destination accepted the message and how a rejection reaches the owning team.
Healthcare Interoperability / Laboratory IntegrationLaboratory & LIS Integration ServicesA result is only useful
A result is only useful
when it reaches
the right workflow.
Connect your laboratory information system with EHRs, ordering applications and patient products. We help carry the order, the result and its context across system boundaries.
The order-to-result journey
- 01Order createdPatient · test · ordering provider
- 02Laboratory workflowAccession · specimen · status
- 03Result returnedValue · units · reference range
- 04Care team receivesCorrect patient · correct order
Keep the clinical context intactMore than delivering
More than delivering
a message.
An order and a result need to remain connected. We define the identifiers, lifecycle and exceptions that make the exchange useful in your application.
Results and corrections
Map test identifiers, values, units, reference ranges and status. Agree how preliminary and amended reports update the receiving workflow.
Identity and terminology
Match patient, encounter, order, accession and specimen identifiers. Document local test codes and any agreed terminology mapping.
Operational reconciliation
Make failed or unmatched messages visible. Define retry, replay and reconciliation rules with safeguards against duplicate downstream actions.
A connection your team can operate.
An agreed interface contract and field mapping
Test cases for normal, missing and corrected data
Deployment, recovery and reconciliation procedures
Named ownership for application and vendor dependencies
FHIR separates individual observations from the report’s wider clinical context. See HL7’s DiagnosticReport specification. Resource and profile choices depend on your implementation.
What we ask for first.
Your systems
LIS and receiving application, vendor contacts and available interface documentation.
Your workflow
Orders, results or both; expected status changes; volume and acceptable delivery delay.
Your acceptance criteria
Representative de-identified samples, matching rules and the people who will validate the result.
Before we startQuestions worth
Questions worth
answering early.
Can you connect our LIS to an EHR or patient platform?
We scope the available interfaces on both sides, the ordering and reporting workflow, identifiers and access requirements. The connection can involve HL7 v2, FHIR, a vendor API or file-based exchange, depending on the systems. We do not assume that every LIS exposes the same functions.
How do you handle corrected or amended results?
The mapping and workflow need to distinguish preliminary, final, corrected and cancelled information where the source supports those states. We agree how updates are matched, displayed, audited and reconciled so a correction is not treated as an unrelated new result.
Is this a laboratory software replacement?
No. The service connects existing systems and workflows. A new LIS or complete laboratory application would be a separate product-engineering scope.
What determines the implementation timeline?
Interface access, vendor coordination, message variations, test data, terminology mapping and customer validation all affect delivery. We define those dependencies and acceptance criteria before proposing a delivery plan.
Start with your workflow
Where does your laboratory workflow lose the connection?
Bring the source and destination systems, the data you need and the current blocker. Use de-identified examples only.
Thank you. Your enquiry has been received. Our team will review your requirements.