Skip to content

Commit

Permalink
Merge pull request #4 from medcomdk/1.0.1-rc1
Browse files Browse the repository at this point in the history
Updated links and version
  • Loading branch information
sksMedcom authored Nov 15, 2024
2 parents 98efc46 + a1189fc commit a7b70b8
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion docs/_config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: "MedCom standard based on HL7 FHIR"
show_downloads: true
google_analytics:
theme: jekyll-theme-minimal
version: "Version 1.0.0-rc1"
version: "Version 1.0.1"
fhir_version: "FHIR®© R4"
releasenote: /assets/documents/ReleaseNote.md
thisurl: https://medcomdk.github.io/MedCom-FHIR-Communication/
Expand Down
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
[Return](../../index.md)
# Mapping from IHE XDS metadata to FHIR

This table describes the mapping between the <a href="https://svn.medcom.dk/svn/releases/Standarder/IHE/DK_profil_metadata/" target="_blank">IHE XDS metadata</a> and FHIR DocumentReference, FHIR Composition, and FHIR Bundle of type Document, which are all found in the <a href="https://build.fhir.org/ig/medcomdk/dk-medcom-document/profiles.html" target="_blank">MedCom Document IG</a>.
This table describes the mapping between the <a href="https://svn.medcom.dk/svn/releases/Standarder/IHE/DK_profil_metadata/" target="_blank">IHE XDS metadata</a> and FHIR DocumentReference, FHIR Composition, and FHIR Bundle of type Document, which are all found in the <a href="https://medcomfhir.dk/ig/document/profiles.html" target="_blank">MedCom Document IG</a>.
The purpose of this mapping is to show how information from IHE XDS Metadata corresponds to the elements in a FHIR Document.
Mapping to the FHIR resources Composition and Bundle ensures that the requirements are adhered to in the FHIR documents, as the metadata information must also be included in the FHIR document. This ensures consistency and integrity between the two standards. The table illustrates the relevant elements and their corresponding counterparts in FHIR, where such exist.

The purpose of this table is to help implementers of FHIR. The actual implementation guides, which includes all requirements for the profiles can be found in the <a href="https://build.fhir.org/ig/medcomdk/dk-medcom-document/profiles.html" target="_blank">MedCom Document IG</a>.
The purpose of this table is to help implementers of FHIR. The actual implementation guides, which includes all requirements for the profiles can be found in the <a href="https://medcomfhir.dk/ig/document/profiles.html" target="_blank">MedCom Document IG</a>.

> Please notice, not all elements from the FHIR profiles are represented in the mapping and therefore it cannot stand alone for implementation. Attributes which are not used in the IHE XDS metadata standard are not included in the mapping.
The table contains:
* 1.: Data elements from the metadata in the <a href="https://svn.medcom.dk/svn/releases/Standarder/IHE/DK_profil_metadata/" target="_blank">IHE XDS metadata standard</a>.
* 2.: Optionalities for the data elements from the IHE XDS metadata standard.
* 3.: Data elements from the <a href="https://build.fhir.org/ig/medcomdk/dk-medcom-document/StructureDefinition-medcom-documentreference.html" target="_blank">MedComDocumentReference profile</a>. This profile is not a part of the standard nor the metadata, but may be used for validation of the metadata.
* 3.: Data elements from the <a href="https://medcomfhir.dk/ig/document/StructureDefinition-medcom-documentreference.html" target="_blank">MedComDocumentReference profile</a>. This profile is not a part of the standard nor the metadata, but may be used for validation of the metadata.
* 4.: Optionalities for the data elements from the MedComDocumentReference.
* 5.: Data elements from the MedComDocumentComposition profile.
* 6.: Data elements from the MedComDocumentBundle profile.
Expand Down Expand Up @@ -94,7 +94,7 @@ The table contains:
<td class="tg-on52"><span style="background-color:#FFF">R</span></td>
<td class="tg-on52"><span style="background-color:#FFF">category</span></td>
<td class="tg-on52">1..1</td>
<th class="tg-ippy"><span style="font-weight:bold"></span>category</th>
<th class="tg-ippy"><span style="font-weight:bold"></span></th>
<th class="tg-ippy"><span style="font-weight:bold"></span></th>
<td class="tg-on52"></td>
</tr>
Expand Down
2 changes: 1 addition & 1 deletion docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Below, you can find the use cases in English:
### 1.2 Technical specification

The technical specifications describes which information constitutes the foundation for MedCom FHIR Documents. These these are defined in an IG:
* <a href="https://build.fhir.org/ig/medcomdk/dk-medcom-document/index.html" target="_blank">MedCom Document Implementation Guide</a>
* <a href="https://medcomfhir.dk/ig/document/index.html" target="_blank">MedCom Document Implementation Guide</a>

The MedCom Document Implementation Guide builds upon the [document specifications](https://hl7.org/fhir/R4/documents.html) that has already been developed by HL7 International.

Expand Down

0 comments on commit a7b70b8

Please sign in to comment.