EHMI Delivery Status (EDS)
1.0.0 - release Denmark flag

EHMI Delivery Status (EDS), published by MedCom. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-ehmi-eds/ and changes regularly. See the Directory of published versions

Profiles

The following profiles set the minimum expectations to record, search and fetch health data associated with a MedCom FHIR Message:

  • EdsBasicDeliveryStatus

    EdsBasicDeliveryStatus is used to define the basic delivery status reporting for EDS from an EDS Client to the EDS Server.

    A basic EdsBasicDeliveryStatus is based on the AuditEvent profile for and is submitted when a EHMI Core Messaging transaction from one station in the messageflow to another station happens successfully.

    EdsBasicDeliveryStatus is only used when a Patient entity is not required, for instance for delivery status reporting of Acknowledgments. The EdsBasicDeliveryStatus does not have a Patient subject or is otherwise associated with a Patient. When the message transaction is Patient specific then EdsPatientDeliveryStatus is used.

    When successfully submitted from an EDS Client to the EDS Server then the recorded EdsBasicDeliveryStatus has conformed to the profile otherwise it would not have a successful outcome and the EDS Client will receive an OperationOutcome indicating the failure.

  • EdsPatientDeliveryStatus

    EdsPatientDeliveryStatus is used to define the basic delivery status reporting for EDS from an EDS Client to the EDS Server.

    The EdsPatientDeliveryStatus is an enhancement of the basic EdsBasicDeliveryStatus and is submitted when a EHMI Core Messaging transaction from one station in the messageflow to another station happens successfully.

    EdsPatientDeliveryStatus is used when a Patient entity is required, for instance for status reporting of MedCom FHIR Messages. The EdsPatientDeliveryStatus has a Patient subject entity and is thereby associated with a Patient. When the message transaction is not Patient specific then EdsBasicDeliveryStatus is used.

    When successfully submitted from an EDS Client to the EDS Server then the recorded EdsPatientDeliveryStatus has conformed to the profile otherwise it would not have a successful outcome and the EDS Client will receive an OperationOutcome indicating the failure.