Merge pull request #38 from medcomdk/karina-review

Karina review

docs/assets/documents/eas/index.md

@@ -16,14 +16,19 @@ 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.
 
-[TBT] EHMI anvender en komponent til at håndtere Sundhedsadressering.
+EHMI uses a component to handle health care adressing.
 
-[TBT] En skitse over komponenterne i EHMI netværkets anvendelse af komponenten kan ses her:
+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://github.com/medcomdk/ehmi/blob/karina-review/docs/assets/images/EHMI%20Pixi%20-%20Addressing%20Service.png)
+
+**The whole specification for EHMI Addressing Service (EAS) can be found** 
+<a href="https://build.fhir.org/ig/medcomdk/dk-ehmi-eas/" target="_blank">here</a>
+
+<br/> 
 
 ![EHMI Addressing Service (EAS)](/ehmi/assets/images/3_EHMI_Sundhedsadresseringsservice_1315x551.png)
 
 <br/> 
 
 **The whole specification for EHMI Addressing Service (EAS) can be found** 
 <a href="https://build.fhir.org/ig/medcomdk/dk-ehmi-eas/" target="_blank">here</a>
-

docs/assets/documents/ecore/index.md

@@ -59,7 +59,7 @@ In addition to the primary flow, ehmiEnvelopeReceipt will be sent from the Recei
 
 <br/> 
 
-![EHMI Core Message Delivery and Document Sharing](/ehmi/assets/images/1_EHMI_Meddelelsesforsendelse_og_dokumentdeling_1315x563.png)
+![EHMI Core Message Delivery and Document Sharing](https://github.com/medcomdk/ehmi/blob/karina-review/docs/assets/images/EHMI%20Pixi%20-%20Message%20delivery.png)
 
 <br/> 
 

docs/assets/documents/eds/index.md

@@ -18,7 +18,7 @@
 
 <br/> 
 
-The EDS Server and EDS Clients are expected to implement the user stories outlined [here:](./userstories/index.md)
+The EDS Server and EDS Clients are expected to implement the user stories outlined [here](./userstories/index.md)
 
 <br/> 
 

docs/assets/documents/production-pilot/index.md

@@ -46,7 +46,7 @@ The project has a number of deliverables of specifications, which can be seen be
 
 ### Project Time schedule
 
-![EHMI Pixi time schedule](../images/EHM_Pixi_timeschedule.jpg)
+![EHMI Pixi time schedule](https://github.com/medcomdk/ehmi/blob/karina-review/docs/assets/images/EHMI%20Pixi%20-%20tidslinje.png)
 
 <br/> 
 
@@ -139,11 +139,11 @@ EHMI Delivery Status Security is defined as
 
 <bold><i>Note! All links opens in a new window.</i></bold>
 
-- Dansk:
+- Danish:
     - MedCom: <a href="https://medcom.dk/projekter/kommunale-proevesvar-paa-ny-infrastruktur/" target="_blank">MedCom13 projektbesksrivelse af ’Kommunale prøvesvar på ny infrastruktur’</a>
     - SDS: <a href="https://sundhedsdatastyrelsen.dk/-/media/sds/filer/rammer-og-retningslinjer/referenceaktitektur-og-it-standarder/referencearkitektur/maalbillede-for-meddelelseskommunikation.pdf" target="_blank">Målbillede for meddelelseskommunikation på sundhedsområdet</a>
     - MedCom: <a href="https://medcom.dk/systemforvaltning/sundhedsdatanettet-sdn/" target="_blank">Sundhedsdatanettet (SDN)</a>
-- Engelsk:
+- English:
     - <a href="" target="_blank"></a>
     - Digital Europe, eDelivery <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eDelivery" target="_blank">eDelivery</a>
     - Digital Europe, eDelivery <a href="https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Access+Point+specifications" target="_blank">AP specifikationer</a>

docs/assets/documents/security/security-specification-of-ehmi-core.md

@@ -18,11 +18,11 @@
 
 - [General information about security for components in EHMI](#general-information-about-security-for-components-in-ehmi)
 
-- [Specifications – security regarding message communication](#specifications---security-regarding-message-communication)
+- [Specifications - security regarding message communication](#specifications---security-regarding-message-communication)
 
 - [Decentralized regarding security](#decentralized-regarding-security)
 
-- [All components stand-alone – implemented on different servers](#all-components-stand-alone---implemented-on-different-servers)
+- [All components stand-alone - implemented on different servers](#all-components-stand-alone---implemented-on-different-servers)
 
 - [All components stand-alone - grouped together on the same server](#all-components-stand-alone---grouped-together-on-the-same-server)
 
@@ -34,13 +34,13 @@
 
 - [Sending system stand-alone - MSH/AP build together - all grouped together on the same server](#sending-system-stand-alone---mshap-build-together---all-grouped-together-on-the-same-server)
 
-- [Sending system/MSH build together – AP stand-alone - implemented on different servers](#sending-systemmsh-build-together---ap-stand-alone---implemented-on-different-servers)
+- [Sending system/MSH build together - AP stand-alone - implemented on different servers](#sending-systemmsh-build-together---ap-stand-alone---implemented-on-different-servers)
 
-- [Sending system/MSH build together – AP stand-alone - all grouped together on the same server](#sending-systemmsh-build-together---ap-stand-alone---all-grouped-on-the-same-server)
+- [Sending system/MSH build together - AP stand-alone - all grouped together on the same server](#sending-systemmsh-build-together---ap-stand-alone---all-grouped-together-on-the-same-server)
 
-- [Sending system/MSH build together – MSH/AP build together - implemented on different servers](#sending-systemmsh-build-together---mshap-build-together---implemented-on-different-servers)
+- [Sending system/MSH build together - MSH/AP build together - implemented on different servers](#sending-systemmsh-build-together---mshap-build-together---implemented-on-different-servers)
 
-- [Sending system/MSH build together – MSH/AP build together - all grouped together on the same server](#sending-systemmsh-build-together---mshap-build-together---all-grouped-on-the-same-server)
+- [Sending system/MSH build together - MSH/AP build together - all grouped together on the same server](#sending-systemmsh-build-together---mshap-build-together---all-grouped-together-on-the-same-server)
 
 - [All components build together](#all-components-build-together)
 
@@ -74,7 +74,7 @@ A strong authentication of users must take place (according to NIST niveau 3-4 o
 <br/> 
 
 
-## Specifications – security regarding message communication
+## Specifications - security regarding message communication
 
 First, the general guidelines regarding security in the message flow in EHMI are described. Secondly, it is described for the different scenarios of **interconnections** and **grouping**, cf. [General security definitions regarding components in the delivery chain](#general-security-definitions-regarding-components-in-the-delivery-chain) how the guidelines is implemented in the individual scenarios.  
 
@@ -111,7 +111,7 @@ The following table illustrates in general, how the guidelines are regarding sec
 <br/> 
 
 
-### All components stand-alone – implemented on different servers
+### All components stand-alone - implemented on different servers
 
 <br/> 
 
@@ -197,9 +197,9 @@ The following table illustrates in general, how the guidelines are regarding sec
 <br/> 
 
 
-### Sending system stand-alone - MSH/AP build together – all grouped together on the same server
+### Sending system stand-alone - MSH/AP build together - all grouped together on the same server
 
-![Sending system stand-alone - MSH/AP build together – all grouped together on the same server](media/584f59d0d6bb7e4f94aea46de8eb249c.png)
+![Sending system stand-alone - MSH/AP build together - all grouped together on the same server](media/584f59d0d6bb7e4f94aea46de8eb249c.png)
 
 | **EHMI components**              | **Subtask**                                                          | **Who**             |
 |-----------------------------------|------------------------------------------------------------------------|----------------------|
@@ -209,7 +209,7 @@ The following table illustrates in general, how the guidelines are regarding sec
 <br/> 
 
 
-### Sending system/MSH build together – AP stand-alone – implemented on different servers
+### Sending system/MSH build together - AP stand-alone - implemented on different servers
 
 
 ![Sending system/MSH build together – AP stand-alone – implemented on different servers](media/be1c6e9b30bae64a8f5738170ef00b20.png)
@@ -223,7 +223,7 @@ The following table illustrates in general, how the guidelines are regarding sec
 <br/> 
 
 
-### Sending system/MSH build together – AP stand-alone – all grouped together on the same server
+### Sending system/MSH build together - AP stand-alone - all grouped together on the same server
 
 
 ![Sending system/MSH build together – AP stand-alone – all grouped together on the same server](media/be1c6e9b30bae64a8f5738170ef00b20.png)
@@ -236,7 +236,7 @@ The following table illustrates in general, how the guidelines are regarding sec
 <br/> 
 
 
-### Sending system/MSH build together – MSH/AP build together - implemented on different servers
+### Sending system/MSH build together - MSH/AP build together - implemented on different servers
 
 Through dialog with the participating parties, we have learned that this scenario is possible. In that case, it is important, that parties with this kind of setup agree on which MSH is the primary with fulfilling the MSH obligations, and which MSH simply forwards information to the next link in the chain. Once this is in place , the following security instructions will apply. 
 
@@ -252,7 +252,7 @@ Through dialog with the participating parties, we have learned that this scenari
 <br/> 
 
 
-### Sending system/MSH build together – MSH/AP build together – all grouped together on the same server
+### Sending system/MSH build together - MSH/AP build together - all grouped together on the same server
 
 ![Sending system/MSH build together – MSH/AP build together – all grouped together on the same server](media/dc36c10735cb86a5499e120b23a83c79.png)
 

docs/index.md

@@ -15,7 +15,7 @@ This is the homepage of the entire description and all the specifications of EHM
 
 <br/> 
 
-**For now, specifications published here at 01-04-2024 will focus on the Production pilot for EHMI and are therefore narrowed down to show only what is currently ready. By the end of Q2 2024 several more specifications and descriptions will be released on these sites and make the documentation more comprehensive.**
+**For now, specifications published here at 01-04-2024 will focus on the Production pilot for EHMI and are therefore narrowed down to show only what is currently ready. Later in 2024 several more specifications and descriptions will be released on these sites and make the documentation more comprehensive.**
 
 <br/>