DK EHMI Endpoint Register (EER)
1.0.0-draft - release Denmark flag

This page is part of the DK EHMI Endpoint Register (EER) (v1.0.0-draft: Release 1.x.x Draft) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Eer Use Case 2

Get Device metadata by DeviceID

A MSH or AP calls EER to retrieve the necessary Device metadata information for its own use to handle the data required by EDS DeliveryStatus registrations. The data is pretty static, so it's possible to store this locally and save the infrastructure for too many calls on this.

The sequence diagram for this is as follows:

eer_getDeviceDataByDeviceId

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.eer_getDeviceDataByDeviceId

URL: [base]/eer_getDeviceDataByDeviceId/EerCoreOrganization?identifer=[Device-identifer]

Input parameters Profile:

http://medcomehmi.dk/ig/eer/StructureDefinition/EerDevice

Output parameters Profile:

http://medcomehmi.dk/ig/eer/StructureDefinition/EerDevice

Error use cases for EER use case 1

  • error use case 4a - EerDevice-Information does not exist

Error use case 1a - EER-DeviceData does not exist

Should an error occur when calling EER to obtain the EerDevice metadata, an error response stating this is packed and returned to the caller of EER as illustrated by:

eer_getDeviceDataByDeviceId_error1