Diagnostic results enable clear, timely communication about test outcomes in patient-friendly language. When results are received, our system:
Notifies patients that their results are available
Translates complex medical terminology into plain language
Delivers relevant educational content
Keeps patients informed about their care progression
By processing results in real-time, patients are automatically kept informed and engaged in their care journey. Medical jargon is translated into easy to understand text, ensuring patients can better understand their health status and participate in their care.
Required Results
Laboratory
Radiology/Imaging
Cardiology
Pharmacy/Medication
We support all event types and we support all segments and fields. Below is our minimum required segment and field specification.
Segment | Field | Field / Expected Value | Comments |
MSH | 1 | Field Separator |
|
MSH | 2 | ^~& |
|
MSH | 3 | Sending Application |
|
MSH | 4 | Facility Identifier | Unique identifier per facility, e.g. ACME |
MSH | 5 | Receiving Application |
|
MSH | 6 | Interface Identifier | LAB, RAD, CARD, MED |
MSH | 7 | Date/Time of Message |
|
MSH | 9 | Message Type |
|
MSH | 10 | Message Control ID |
|
MSH | 11 | Processing ID | T for Test, P for Prod |
MSH | 12 | Version ID |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
EVN | 1 | Event Type Code |
|
EVN | 2 | Recorded Date/Time |
|
EVN | 4 | Event Reason Code |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
PID | 1 | Set ID |
|
PID | 2 | Patient ID | Enterprise MRN |
PID | 3 | Patient Identifier List | Facility MRN |
PID | 18 | Patient Account Number |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
PV1 | 1 | Set ID |
|
PV1 | 2 | Patient Class | Values table required |
PV1 | 10 | Hospital Service | Values table required |
PV1 | 18 | Patient Type |
|
PV1 | 19 | Visit Number |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
ORC | 1 | Order Control | Values table required |
ORC | 2 | Placer Order Number | Should be consistent across all orders and results |
ORC | 3 | Filler Order Number | Should be consistent across all orders and results |
ORC | 5 | Order Status | Values table required |
ORC | 8 | Parent Order |
|
ORC | 9 | Date/Time of Transaction |
|
ORC | 10 | Entered By |
|
ORC | 12 | Ordering Provider |
|
ORC | 15 | Order Effective Date/Time |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
OBR | 1 | Set ID |
|
OBR | 2 | Placer Order Number | Should be consistent across all orders and results |
OBR | 3 | Filler Order Number | Should be consistent across all orders and results |
OBR | 4 | Universal Service Identifier |
|
OBR | 5 | Priority |
|
OBR | 7 | Observation Date/Time |
|
OBR | 14 | Specimen Received Date/Time |
|
OBR | 15 | Specimen Source |
|
OBR | 16 | Ordering Provider |
|
OBR | 22 | Result Date/Time |
|
OBR | 24 | Diagnostic Service ID |
|
OBR | 25 | Result Status |
|
OBR | 27 | Quantity/Timing |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
OBX | 1 | Set ID |
|
OBX | 2 | Value Type |
|
OBX | 3 | Observation Identifier | LOINC or CPT code |
OBX | 5 | Observation Value |
|
OBX | 6 | Units |
|
OBX | 7 | Reference Range |
|
OBX | 8 | Abnormal Flags | Values table required |
OBX | 11 | Observation Result Status |
|
OBX | 14 | Date/Time of Observation |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
NTE | 1 | Set ID |
|
NTE | 2 | Source of Comment |
|
NTE | 3 | Comment |
|