DK EHMI Delivery Status (EDS)
0.3.0 - ci-build Denmark flag

DK EHMI Delivery Status (EDS), published by MedCom. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-medcom-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:

  • EdsBasicDeliveryStatusCreate

    *** UNDER SPECIFICATION ***

    EHMI profile of the IHE.BasicAudit.Create profile.

    EdsBasicDeliveryStatusCreate is used to define the basic status reporting for EDS from the EDS Client to the EDS Server.

    EdsBasicDeliveryStatusCreate is used when a Patient entity is not required, for instance for reporting of Acknowledgments

    A basic EdsBasicDeliveryStatus based on the AuditEvent profile for when a RESTful EdsBasicDeliveryStatus Create 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 PatientCreate is used

    • And the request is authorized

    • Authorization failures should follow FHIR core Access Denied

    • 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

  • EdsBasicDeliveryStatusQuery

    *** UNDER SPECIFICATION ***

    EHMI profile of the IHE.BasicAudit.Query profile.

  • EdsBasicDeliveryStatusRead

    *** UNDER SPECIFICATION ***

    A basic AuditEvent profile for when a RESTful Read action happens successfully.

    • Given a Resource Read is requested
    • And that resource does not have a Patient subject or is otherwise associated with a Patient
    • And the request is authorized
    • When successful
      • Note a failure AuditEvent may follow this pattern, but would not be a successful outcome and should have an OperationOutcome
    • Then the AuditEvent recorded will conform
  • EdsPatientDeliveryStatusCreate

    *** UNDER SPECIFICATION ***

    EHMI profile of the IHE.BasicAudit.PatientCreate profile based on the EHMI profile EdsPatientDeliveryStatusCreate.

  • EdsPatientDeliveryStatusQuery

    *** UNDER SPECIFICATION ***

    EHMI profile of the IHE.BasicAudit.PatientQuery profile.

  • EdsPatientDeliveryStatusRead with a Patient

    *** UNDER SPECIFICATION ***

    A basic AuditEvent profile for when a RESTful Read action happens successfully, and where there is an identifiable Patient subject associated with the read Resource.

    • Given a Resource Read is requested
    • And that resource has a Patient subject or is otherwise associated with a Patient
    • And the request is authorized
    • When successful
      • Note a failure AuditEvent may follow this pattern, but would not be a successful outcome and should have an OperationOutcome
    • Then the AuditEvent recorded will conform