LABORATORY CONNECTORS
LIS Connectors
2 of 8LIS Connectors enable Mediloop to exchange laboratory data with Laboratory Information Systems using industry standards. The LIS remains the system of record for the laboratory and orchestrates workflow and instruments.
BidirectionalStandards-BasedReliableSecureAuditableReconciled
LIS integration overview
Mediloop HIS / EHR
Orders (ORM)
Laboratory Information System (LIS)
Results (ORU)
Mediloop HIS / EHR
Acknowledgements (ACK), retries, reconciliation and exception handling run throughout the flow.
How LIS integration works
1Mediloop creates or retrieves a laboratory order.
2Order is sent to LIS using HL7 ORM or FHIR ServiceRequest.
3LIS validates, assigns accession number and creates specimen workflow.
4LIS routes to instruments/analyzers as needed.
5Results are produced and consolidated in LIS.
6Results are returned to Mediloop using HL7 ORU or FHIR Observation / DiagnosticReport.
Supported standards
| Standard | Use |
|---|---|
| HL7 v2.x | ORM, ORU, OML, ORY, ACK, NTE |
| FHIR R4/R4B | ServiceRequest, Specimen, Observation, DiagnosticReport, Task, Encounter, Patient |
| LOINC | Laboratory tests and panels |
| SNOMED CT | Clinical concepts and findings |
| UCUM | Units of measure |
| ISO 15189 alignment | Laboratory quality and traceability |
Key capabilities
Create, update, cancel and track orders
Retrieve order and specimen status
Receive preliminary and final results
Automatic reconciliation and duplicate detection
Critical / abnormal result notifications
Support attachments such as PDF, CDA and images
Multi-lab / multi-site support
Audit trail for all exchanges
Message flows
| Direction | Message / resource | Purpose |
|---|---|---|
| Mediloop → LIS | ORM / OML / FHIR ServiceRequest | Create, update or cancel laboratory orders |
| LIS → Mediloop | ORU / FHIR Observation + DiagnosticReport | Return preliminary and final results |
| Bidirectional | ACK / OperationOutcome | Confirm processing or report validation errors |
| Query | QRY / QPD / FHIR search | Retrieve patient, order, specimen or result state |
| Events | Webhook / Subscription | Notify status changes and critical-result events |
Order lifecycle
1
Created
Order created in Mediloop
2
Transmitted
Sent to LIS (ORM)
3
Accepted
ACK received and accession assigned
4
In progress
Specimen received and analyzed
5
Completed
Results available in LIS
6
Cancelled
Order cancelled in LIS
Result lifecycle
1
Preliminary
Initial result
2
Validated
Technologist validation
3
Reviewed
Pathologist / scientist review
4
Final
Final result released
5
Delivered
Results delivered to Mediloop
Data mapping & terminology
| Source concept | Canonical / standard mapping | Rule |
|---|---|---|
| Local test code | LOINC | Preserve original local code and mapping provenance |
| Specimen / body site | SNOMED CT | Normalize only when meaning is unambiguous |
| Units | UCUM | Validate and normalize units without losing source value |
| Order / result identifiers | FHIR identifiers + LIS accession IDs | Keep source identifiers for reconciliation |
| Result status | FHIR status / interpretation | Map lifecycle state explicitly and audit changes |
Reliability & reconciliation
Acknowledgements (ACK)
Every message is acknowledged by the LIS.
Retries & backoff
Automatic retries with exponential backoff on failures.
Idempotency
Duplicate orders/results are detected and handled safely.
Reconciliation
Periodic reconciliation checks consistency between systems.
Error handling
Errors are logged, alerted and can be resent after correction.
Security
mTLS / TLS for system-to-system exchanges
OAuth / scoped credentials for FHIR and REST integrations
Tenant, site and laboratory context enforced on every request
Secrets and certificates stored in approved secure stores
Full audit trail for message receipt, transformation and delivery
Minimum-necessary access to laboratory data
Best practices
Keep the LIS as the laboratory system of record whenever possible
Use acknowledgements, idempotency and replay-safe retries
Preserve raw codes, identifiers and source values
Reconcile orders, specimens and results periodically
Test amendments, cancellations and critical-result workflows
Monitor queue depth, latency, failures and stale integrations