added use cases

docs/index.md

@@ -2,10 +2,10 @@
 # MedCom Document 
 <!-- below is the table of content. Ensure to update it. -->
 **Table of Content**
-* [1 Standard Documentation](#standard)
-  * [1.1 Use Cases](#12-use-cases)
-  * [1.2 Technical specification](#13-technical-specification)
-  * [1.3 Mapping from IHE-XDS metadata to FHIR to FHIR](#14-mapping-from-oioxml-to-fhir)
+- [1 Standard Documentation {#standard}](#1-standard-documentation-standard)
+  * [1.1 Use Cases](#11-use-cases)
+  * [1.2 Technical specification](#12-technical-specification)
+  * [1.3 Mapping from IHE XDS metadata to FHIR to FHIR](#13-mapping-from-ihe-xds-metadata-to-fhir-to-fhir)
 
 This page represents the document profiles (Danish: dokumentprofiler) used in MedComs FHIR®© standards. These profiles describe fundamental information when exchanging information in documents. The MedCom Document profiles do not alone compose a standard but are used to information generic acrosse in MedCom’s document standards. Thus, this page includes the IG, and technical uses cases and does not include clinical guidelines and test protocols. 
 
@@ -17,7 +17,7 @@ Use cases describe how to exchange documents over an [IHE XDS infrastructure](ht
 
 Below, you can find the use cases in English:
 
-[English: Use cases](assets/documents/UseCases-ENG.md) 
+[English: Use cases (docx)](assets/documents/UseCases-ENG.docx) 
 
 ### 1.2 Technical specification
 
@@ -29,4 +29,4 @@ The MedCom Document Implementation Guide builds upon the [document specification
 ### 1.3 Mapping from IHE XDS metadata to FHIR to FHIR
 There already exists a standard for <a href="https://svn.medcom.dk/svn/releases/Standarder/IHE/DK_profil_metadata/" target="_blank">IHE XDS metadata in Denmark</a>, which is valid for every type of document exchanged over the [national service platform (NSP)](https://www.nspop.dk/display/Web3/Introduktion+til+NSP-platformen). The metadata must to a wide extend be found in the document. To express how this is done, a mapping between the IHE XDS Metadata standard and the profiles MedComDocumentBundle and MedComDocumentComposition is created. The mapping follows the recommendations from HL7 International. Not all elements from the FHIR profiles are represented in the mapping and therefore it cannot stand alone for implementation.
 
-[Mapping from IHE-XDS metadata to FHIR DocumentReference, FHIR Composition and FHIR Bundle..](assets/documents/Mapping_from_IHE-XDS_metadata_to_FHIR.md) <br>
+[English: Mapping from IHE-XDS metadata to FHIR DocumentReference, FHIR Composition and FHIR Bundle.](assets/documents/Mapping_from_IHE-XDS_metadata_to_FHIR.md) <br>