Messaging
The Alberta eOrder Laboratory Messaging Interoperability Specification, enables an exchange of information about an electronic laboratory order between two trusted systems using FHIR messaging. In FHIR messaging, a message is sent from a source application to a destination application when an event happens. A message is a Bundle resource of type message that conforms to specific rules.
The Alberta eOrder Laboratory messaging implementation follows synchronous Message Request and Response paradigm using HTTP-based (POST) MessageHeader/$process-message FHIR operation.
The Alberta eOrder Laboratory REST-based service has a single interface: A Community Information Integration (CII) inbound AB:eOrder-Lab FHIR interface that allows EMRs to submit (POST) FHIR laboratory order messages intended to be lodged within Connect Care Laboratory Information System (LIS).
See section on Constructing Messages and Reducing Message Size in Guidance for additional guidance.
Transactions
The following table shows the transactions that are used in this specification. This is arranged in order of the transaction id.
ID | Name | Focus | Event Code | Note |
---|---|---|---|---|
eOrder-Labm-1 | Send new service request | ServiceRequest | add-service-request | If a requisition contains more than one laboratory tests, the sender SHALL send one message containing multiple ServiceRequest (one for each laboratory test requested) |
eOrder-Labm-2 | Notify update service request | ServiceRequest | notify-update-service-request | If a requisition contains more than one laboratory tests, the sender SHALL send ONLY the laboratory tests that have been updated and MAY send all of them in one message containing multiple ServiceRequest (one for each laboratory test updated); only a few specific elements can be updated using the update message - if an update is desired for an element that can not be updated using the update message, the order SHALL be cancelled (revoked) and a new order message SHALL be sent with the updated data |
eOrder-Labm-3 | Revoke service request | ServiceRequest | revoke-service-request | If a requisition contains more than one laboratory tests, the sender SHALL send ONLY the laboratory tests that have been cancelled and MAY send all of them in one message containing multiple ServiceRequest (one for each laboratory test that has been cancelled) |
Transactions by Participants
The following tables shows the outgoing and incoming transactions that are expected to be supported by each participant.
Requesting Healthcare Provider (Source System: Community EMR)
Incoming / Outgoing | Transaction ID | Transaction Name |
---|---|---|
Outgoing | eOrder-Labm-1 | Send new service request |
Outgoing | eOrder-Labm-2 | Notify update service request |
Outgoing | eOrder-Labm-3 | Revoke service request |
Alberta Precision Laboratories (Target System: Connect Care LIS)
Incoming / Outgoing | Transaction ID | Transaction Name |
---|---|---|
Incoming | eOrder-Labm-1 | Send new service request |
Incoming | eOrder-Labm-2 | Notify update service request |
Incoming | eOrder-Labm-3 | Revoke service request |