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

Eds Use Case 1

Post EdsBasicDeliveryStatus

An EDS Client wants to make an EDS Delivery Status registration.

This use case is conforming to this OperationDefinition:

**Be aware:** The exact name of this operation may differentiate, when it comes to the real world implementation, 
but the intention is to implement a service that given the input parameters profile will produce the output parameters Profile.

Generated Narrative: OperationDefinition eer.postEdsBasicDeliveryStatus

URL: [base]/postEdsBasicDeliveryStatus

Input parameters Profile:

http://medcomehmi.dk/ig/eds/EdsBasicDeliveryStatus

Output parameters Profile: HTTP 200 OK

Error use cases for use case 1

There may be many error use cases, here some of them are mentioned. Expect them to grow over time

• error use case 1a - the reported EdsBasicDeliveryStatus does not conform with the profile
• error use case 1b - the RDS Client doesn't have the rights to post an EdsBasicDeliveryStatus at all
• error use case 1c - the RDS Client doesn't have the rights to post an EdsBasicDeliveryStatus on behalf of the Organization which has either the role of a Sender or a Receiver

Error use cases 1a-1c

The output parameter will be an operationOutcome with a failure notice on what went wrong.