diff --git a/docs/_config.yml b/docs/_config.yml index af557e5..988fc28 100644 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -21,6 +21,6 @@ menutxt_item5: EHMI Endpoint Register* menuurl_item6: https://medcomdk.github.io/ehmi/assets/documents/egov/ menutxt_item6: EHMI Governance* menuurl_item7: https://medcomdk.github.io/ehmi/assets/documents/security/ -menutxt_item7: EHMI Security +menutxt_item7: EHMI Security* menuurl_item8: https://medcomdk.github.io/ehmi/assets/documents/glossary/ menutxt_item8: EHMI Glossary diff --git a/docs/assets/documents/eas/index.md b/docs/assets/documents/eas/index.md index 5382ff0..17d6546 100644 --- a/docs/assets/documents/eas/index.md +++ b/docs/assets/documents/eas/index.md @@ -7,7 +7,7 @@
-When a user of EHMI wants to send a message, the correct recipient of the message needs to be found somehow unless the user happens to know it by heart. Such a search function already exists to varying degrees in the various user systems, and to make these searches easier, EAS provides useful standardized search services based on relevant authoritative sources (like for example the national register of organizations within the health domain). +When a user of EHMI wants to send a message, the correct recipient of the message needs to be found somehow unless the user happens to know it by heart. Such a search function already exists to varying degrees in the various user systems, and to make these searches easier, EAS provides useful standardized search services based on relevant authoritative sources (like for example the national register of organizations within the health domain (SOR)). When EAS receives a search request from a user system it in turn calls the relevant authoritative sources responsible for the information needed for the particular type of search request, and based on this EAS constructs the response for the user system. In this way EAS decouples the user systems from the authoritative sources and the, sometimes cumbersome, logic to be implemented to support searches for recipients in various different situations only needs to be implemented and maintained in EAS. @@ -16,10 +16,9 @@ Examples of search services EAS support include: * Search for general practitioners in a delimited geographical area (relevant for patients with no fixed general practitioner). * Search for recipients capable of receiving specific types of messages – not just the overall message type (including version), but also more detailed searches concerning specific aspects of the message to be sent (relevant, e.g., in relation to referrals for X-ray examinations that require special equipment not offered by all X-ray departments). -EHMI uses a component to handle health care adressing. - An outline of the components in the EHMI network's use of the EHMI Adressing Service can be seen here: -![EHMI Pixi - Addressing Service](https://medcomdk.github.io/ehmi/assets/images/EHMI%20Pixi%20-%20Addressing%20Service.png) + +EHMI Addressing Service (EAS) (DA) **The whole specification for EHMI Addressing Service (EAS) can be found** here diff --git a/docs/assets/images/EHMI Pixi - Addressing Service.png b/docs/assets/images/EHMI Pixi - Addressing Service.png index 1707c3a..1703ef2 100644 Binary files a/docs/assets/images/EHMI Pixi - Addressing Service.png and b/docs/assets/images/EHMI Pixi - Addressing Service.png differ