HEALTHCARE SYSTEMS CONNECTORS
Orders & Results (ORU)
4 of 9Exchange clinical orders, observations and results between Mediloop, HIS/EHR and departmental systems using HL7 v2 and FHIR across laboratory, imaging, cardiology and other diagnostic services.
HL7 v2ORM / OML / ORUFHIR R4 / R4BServiceRequestObservationDiagnosticReportTaskLIS / RIS / Other
End-to-End Orders & Results Flow
1
Clinician / HIS
Creates lab, imaging, cardiology or other diagnostic order
2
Mediloop Connector
Validates, transforms and routes order
3
Departmental System
LIS, RIS, cardiology or specialty system processes order
4
Results
Preliminary, final or corrected results returned
5
HIS / Mediloop
Normalizes and stores result in patient record
6
Clinician / Patient
Results viewed with notifications and access controls
Preserve original identifiers, codes and units while MSIS performs terminology normalization, validation and reconciliation.
Supported HL7 v2 Messages
| Message | Description | Direction |
|---|---|---|
| ORM | Order request | Inbound / Outbound |
| OML | Laboratory order / response | Inbound / Outbound |
| ORU | Unsolicited result | Inbound |
| ORF | Solicited order result | Inbound |
| ACK | Acknowledgement | Bidirectional |
FHIR Resource Mapping
| FHIR resource | Role | Typical linkage |
|---|---|---|
| ServiceRequest | Order / requested service | Patient, Encounter, requester, performer |
| Specimen | Collected material | ServiceRequest and patient |
| Task | Fulfillment / departmental status | ServiceRequest |
| Observation | Individual quantitative or qualitative result | Patient, specimen, device, DiagnosticReport |
| DiagnosticReport | Grouped final/interim result set | ServiceRequest, Observation, ImagingStudy |
| Practitioner / Organization | Requester / performer | Order and report provenance |
Order & Result Lifecycle
1
Requested
Order created
2
Accepted
Receiving system acknowledges
3
In progress
Procedure/test underway
4
Preliminary
Interim result available
5
Final
Final result released
6
Corrected / amended
Controlled replacement/addendum
Terminology & MSIS
| Domain | Typical standard | MSIS responsibility |
|---|---|---|
| Laboratory tests | LOINC | Validate/match order and result concepts |
| Clinical findings | SNOMED CT | Normalize findings while preserving source code |
| Diagnoses | ICD / SNOMED CT | Map coding systems according to use case |
| Units | UCUM | Normalize units and conversion provenance |
| Local departmental codes | Local/vendor | Reconcile to canonical concept while retaining original |
Developer Integration Surface
How to read this section
FHIR resources and HL7/IHE operations are standards-based integration surfaces. Mediloop REST routes shown here are documentation contracts and must remain marked planned until the corresponding backend route is implemented and production-approved.
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| HL7 v2 | ORM / OML / ORU / ORF / ACK | Connect existing HIS, LIS, RIS and interface engines | Protocol operation |
| FHIR | ServiceRequest / Specimen / Task / Observation / DiagnosticReport | Modern order/result workflows and canonical exchange | FHIR surface |
| Events | order.created / status.changed / result.preliminary / result.final / result.corrected | Drive notifications and downstream workflows | Planned contract |
| REST / SDK | Order routing, result ingestion and reconciliation façade | Mediloop-native apps and modernization | Planned contract |
Reliability & Reconciliation
Use stable placer/filler order numbers and correlation IDs
Return acknowledgements with actionable validation errors
Deduplicate retransmitted results
Track preliminary/final/corrected replacement relationships
Reconcile results that arrive before expected order context
Keep source payload, mapping and terminology provenance
Best Practices
Separate order intent from departmental fulfillment status
Never silently rewrite source clinical values
Make result visibility respect preliminary/final state
Test corrected/amended result scenarios
Monitor order-to-result latency and unmatched results
Keep laboratory/imaging-specific detail in their dedicated connector families