Merge pull request #11 from medcomdk/v.1.0.6-rc1

Added rules for CareCommunication and direct link to VANSenvelope spec

docs/_config.yml

@@ -4,7 +4,7 @@ description: "Governance for MedCom HL7 FHIR®© Messaging is the basic ruleset
 show_downloads: false
 google_analytics:
 theme: jekyll-theme-minimal
-version: "Version 1.0.5"
+version: "Version 1.0.6"
 fhir_version: "FHIR®© R4"
 releasenote: https://github.com/medcomdk/MedCom-FHIR-Communication/releases
 thisurl: https://medcomdk.github.io/MedCom-FHIR-Communication/

docs/assets/documents/030_Governance-for-Network-Layer.md

@@ -26,7 +26,6 @@ MedCom FHIR Messages **SHALL** be enveloped in a VANSEnvelope whether they are s
 * The enveloping of MedCom FHIR Messages **SHALL** follow the VANSEnvelope specification outlined in
   * <a href="https://svn.medcom.dk/svn/releases/Standarder/Den%20gode%20VANSEnvelope/Dokumentation" target="_blank"> Click here to read VANSEnvelope specification</a>. Please be aware that the VANSEnvelope specification is in danish.
 * MedCom FHIR Messages **SHALL** follow the metadata specification outlined in both danish and english:
-  * [Danish:Network Envelope](FHIRMessages_NetworkEnvelopes_DA.md)
   * [English:Network Envelope](FHIRMessages_NetworkEnvelopes_EN.md)
 * VANSEnvelopes **SHALL** only contain one MedCom FHIR Messages
 

docs/assets/documents/090_Governance-for-concrete-standards.md

@@ -1,11 +1,5 @@
 # Governance for concrete MedCom FHIR Message Standards
 
-**Table of contents**
-
-* [1 Acknowledgement](#1-acknowledgement)
-* [2 CareCommunication](#2-carecommunication)
-* [3 HospitalNotification](#3-hospitalnotification)
-
 Each MedCom FHIR Message will potentially add some specific Governance Rules to the mix of overall Governance Rules. These are handled on a separate page, to which the specific standard also will link to.
 
 ## 1 Acknowledgement

docs/assets/documents/governance-for-acknowledgement.md

@@ -51,13 +51,9 @@ The structure and included profiles in MedCom Acknowledgement can be seen on <a
     <td class="tg-0pky"><br><br><br><br>If the response.code is different than 'ok', a reference to an OperationOutcome resource shall be included. </td>
   </tr>
   <tr>
-    <td class="tg-0pky"><br><br><br><br><br>MedCom-messaging- 3  </td>
+    <td class="tg-0pky"><br><br><br><br><br>MedCom-acknowledgement-1  </td>
     <td class="tg-0pky"><br><br><br><br>The message header shall conform to medcom-messaging-acknowledgementHeader profile </td>
   </tr>
-  <tr>
-    <td class="tg-0pky"><br><br><br><br><br>Medcom-messaging- 4 </td>
-    <td class="tg-0pky"><br><br><br><br>The Acknowledgement entry shall contain at least two Provenance resource </td>
-  </tr>
 </tbody>
 </table></div>
 
@@ -76,7 +72,7 @@ MedCom has developed a ValueSet with predefined issues descriptions that can hel
 [Click here to se MedCom defined issue descriptions](https://medcomfhir.dk/ig/terminology/ValueSet-medcom-acknowledgement-issue-details.html)
 
 
-## 1.3 MedComAcknowledgementProvenance
+## 1.3 MedComMessagingProvenance
 When acknowledging a MedCom Message with an Acknowledgement, two Provenance instances SHALL be included; one describing the MedCom Message that is acknowledged and one describing the Acknowledgement. Therefore, an Acknowledgement Message will always contain two instances of Provenance resource.  
 
 Furthermore, all instances of the Provenance resource SHALL comply to the [MedComMessagingProvenance profile](https://medcomfhir.dk/ig/messaging/StructureDefinition-medcom-messaging-provenance.html)  

docs/index.md

@@ -7,6 +7,7 @@
 * [3 Message exchange](#3-message-exchange)
   + [3.1 Governance for Reliable Messaging in general](#31-governance-for-reliable-messaging-in-general)
   + [3.2 Governance for Network Layer](#32-governance-for-network-layer)
+    * [3.2.1 VANSenvelope specifications](#321-vansenvelope-specifications)
   + [3.3 Governance for MedCom FHIR Message Exchange](#33-governance-for-medcom-fhir-message-exchange)
 * [4 MedCom FHIR Messages](#4-medcom-fhir-messages)
   + [4.1 Governance for MedCom FHIR Messages](#41-governance-for-medcom-fhir-messages)
@@ -100,6 +101,10 @@ Reliable Messaging using VANSEnvelope describes different scenarios when using t
 
 [Click here to see how to setup Reliable Messaging using VANSEnvelope](/assets/documents/032_Reliable_Messaging-VANSEnvelope.md)
 
+#### 3.2.1 VANSenvelope specifications
+
+[Click here to go to the specifications for VANSenvelope](/assets/documents/FHIRMessages_NetworkEnvelopes_EN.md).
+
 ### 3.3 Governance for MedCom FHIR Message Exchange
 
 Governance for MedCom FHIR Messaging covers Reliable Messaging using MedCom FHIR Messaging, sending and receiving scenarios, and rulesets for FHIR Messaging and FHIR Messaging Acnowledgement.