EHMI Delivery Status (EDS)
0.9.0 - ci-build Denmark flag

EHMI Delivery Status (EDS), published by MedCom. This guide is not an authorized publication; it is the continuous build for version 0.9.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 status reporting for EDS from the EDS Client to the EDS Server. EdsBasicDeliveryStatus is used when a Patient entity is not required, for instance for status reporting of Acknowledgments. A basic EdsBasicDeliveryStatus based on the AuditEvent profile for when a EHMI Basic Delivery Status Messaging action happens successfully. It is used when

    • the resource does not have a Patient subject or is otherwise associated with a Patient
      • when the resource is Patient specific then EdsPatientDeliveryStatus is used
    • And the request is authorized
    • When successful
      • Note a failure EdsBasicDeliveryStatus may follow this pattern, but would not be a successful outcome and should have an OperationOutcome
      • Then the EdsBasicDeliveryStatus recorded will conform
  • EdsPatientDeliveryStatus

    EHMI profile based on the EHMI profile EdsBasicDeliveryStatus. EdsPatientDeliveryStatus is used to define the status reporting for EDS from a EDS Client to the EDS Server. EdsPatientDeliveryStatus is used when a Patient entity is required, for instance for status reporting of MedCom FHIR Messages. A EdsPatientDeliveryStatus based on the AuditEvent profile for when a EHMI Patient Delivery Status Messaging action happens successfully. It is used when

    • the resource has a Patient subject or is otherwise associated with a Patient
      • when the resource is not Patient related then EdsBasicDeliveryStatus is used
    • And the request is authorized
    • When successful
      • Note a failure EdsPatientDeliveryStatus may follow this pattern, but would not be a successful outcome and should have an OperationOutcome
      • Then the EdsPatientDeliveryStatus recorded will conform