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

Use Case 2

Get General Practitioner for a Patient by GPId (Health Insurance Group 1)

This use case concerns the search for the necessary message address metadata information (like the GLN number) of a general practitioner based on the identification of the general practitioner. This is relevant, for example, when the general practitioner of a patient in the National Danish health insurance group 1 is already known. The sequence diagram for this case is as follows:

Once EAS has received the request, the organization id (and other relevant organization information) corresponding to the id of the general practitioner is obtained from the authoritative health organization register (“SOR”). With this and the type of message to be sent, the EHMI Endpoint Register (EER) is called to obtain the GLN number and other relevant information, and finally the response is packed and sent back to the caller of EAS. The message type is, again, needed in the initiating call to EAS, such that EAS can return the correct response for the given message type – it could for example be that the system of the general practitioner does not support receiving the particular type of message.

This use case is conforming to this OperationDefinition: OperationDefinition-eas.SikrGrp1-getReceivingOrganizationByGPId

Error use cases for use case 2

• error use case 2a - SOR-Information does not exist
• error use case 2b - EER-ReceiverData does not exist

Error use case 2a - SOR-Information does not exist

Should an error occur when obtaining the organization id (and other relevant organization information), from the id of the patient’s general practitioner, an error response stating that is packed and returned to the caller of EAS as illustrated in the following diagram:

Error use case 2b - EER-ReceiverData does not exist

Correspondingly, should an error occur when calling EER to obtain the GLN number and other relevant information, an error response stating this is packed and returned to the caller of EAS as illustrated by: