EHMI Delivery Status (EDS)
**Disclaimer**
**The menu items above marked with a star are yet not specified**
EHMI Delivery Status is defined as
- The EDS Server component implemented as a FHIR server that will host the registered data coming in from the clients at each station of EUAs, MSHs and APs in the primary and secondary messaging flow. The server will expose two FHIR APIs for the client to registrate their status:
- EdsBasicDeliveryStatus for registrations of message status without patient data, eg. Acknowledgments (opens in a new window)
- EdsPatientDeliveryStatus for registrations of message status containing patient data (opens in a new window)
- The EDS clients that handle the registration of EHMI Delivery Status (FHIR AuditEvents) from each “station” in both the primary and secondary message delivering from a sender system to a receiver system. That is, EDS Clients can be either an EUA, a MSH or an AP.
The EDS Server and EDS Clients are expected to implement the user stories outlined here
The whole specification for EHMI Delivery Status can be found here
An outline of the components of the EHMI Delivery Status can be seen here:
About
Support or contact
MedCom is responsible for this page. If you have any questions regarding this page, please contact ehmi@medcom.dk.If you want to report an issue regarding this page, please report it at GitHub issues for EHMI®
Version of this documentation
The version of this documentation is: Version 0.9.0 You can find the release note of the version here."EHMI® is the registered trademark of MedCom and is used with the permission of MedCom."