From 654049d09444da6cc0023fb32fc03934314b90be Mon Sep 17 00:00:00 2001 From: tmsMedcom <88831880+tmsMedcom@users.noreply.github.com> Date: Mon, 8 Jul 2024 10:46:40 +0200 Subject: [PATCH] Updated content and mapping. --- docs/_config.yml | 2 +- .../Mapping_from_IHE-XDS_metadata_to_FHIR.md | 211 +++++------------- docs/index.md | 25 +-- 3 files changed, 64 insertions(+), 174 deletions(-) diff --git a/docs/_config.yml b/docs/_config.yml index c857449..262daeb 100644 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -5,7 +5,7 @@ description: "MedCom standard based on HL7 FHIR" show_downloads: true google_analytics: theme: jekyll-theme-minimal -version: "Version x.y.z-alpha.1" +version: "Version 1.0.0-rc1" fhir_version: "FHIR®© R4" releasenote: /assets/documents/ReleaseNote.md thisurl: https://medcomdk.github.io/MedCom-FHIR-Communication/ diff --git a/docs/assets/documents/Mapping_from_IHE-XDS_metadata_to_FHIR.md b/docs/assets/documents/Mapping_from_IHE-XDS_metadata_to_FHIR.md index 7c30f8c..b588ba7 100644 --- a/docs/assets/documents/Mapping_from_IHE-XDS_metadata_to_FHIR.md +++ b/docs/assets/documents/Mapping_from_IHE-XDS_metadata_to_FHIR.md @@ -1,12 +1,13 @@ [Return](../../index.md) -# Mapping from IHE-XDS metadata to FHIR +# Mapping from IHE XDS metadata to FHIR -This table describes the mapping between the IHE-XDS metadata(IHE-XDS metadata) and FHIR DocumentReference, FHIR Composition, and FHIR Bundle of type Document. **(OBS: TILFØJ ALLE LINKS)** -The purpose of this mapping is to ensure that information from IHE-XDS Metadata corresponds to the correct elements in FHIR. 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. +This table describes the mapping between the IHE XDS metadata and FHIR DocumentReference, FHIR Composition, and FHIR Bundle of type Document, which are all found in the MedCom Document IG. +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 MedCom FHIR Document, DocumentReference, Composition and Bundle can be found here. **(OBS: TILFØJ ALLE LINKS)** +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 MedCom Document IG. -> Please notice XXXXXXXXXXXXXX +> 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.
- +@@ -44,7 +45,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -53,7 +54,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -62,7 +63,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -71,16 +72,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - - - - - - - - - - + @@ -89,7 +81,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -98,7 +90,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -107,16 +99,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - - - - - - - - - - + @@ -125,7 +108,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -134,7 +117,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -143,7 +126,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -152,52 +135,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -206,187 +144,151 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - - - - - - - - - - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - - - - - - - - - - - - - - - - - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - - - - - - - - - - + @@ -395,7 +297,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -404,7 +306,7 @@ The purpose of this table is to help implementers of FHIR. The actual implementa - + @@ -425,6 +327,3 @@ The purpose of this table is to help implementers of FHIR. The actual implementa
Table 1: Mapping from IHE-XDS metadata to FHIR DocumentReference, FHIR Composition and FHIR Bundle.Table 1: Mapping from IHE-XDS metadata to FHIR DocumentReference, FHIR Composition and FHIR Bundle.
DocumentEntry.uniqueIduniqueId R masterIdentifier 0..10..1
DocumentEntry.entryUUIDentryUUID R identifier 1..11..1
DocumentEntry.availabilityStatusavailabilityStatus R status 1..11..1
docStatus
DocumentEntry.typeCodetypeCode R type 1..01..0
DocumentEntry.classclass R category 1..11..1
DocumentEntry.patientIdpatientId R subject 1..11..1
date
DocumentEntry.authorauthor R author 1..21..2
DocumentEntry.author.authorInstitutionauthor.authorInstitution R author 1..11..1
DocumentEntry.author.authorPersonauthor.authorPerson R2 author 0..10..1
DocumentEntry.legalAuthenticatorlegalAuthenticator R2 authenticator 0..10..1
custodian
DocumentEntry AssociationsrelatesTo
DocumentEntry Associations typecode
DocumentEntry Associations referencetarget
DocumentEntry.commentsdescription
DocumentEntry.confidentialityCodeconfidentialityCode R securityLabel 1..11..1
content1..11..1
DocumentEntry.mimeTypemimeType Rattachment.contentTypecontent.attachment.contentType 1..1 1..1
DocumentEntry.languageCodelanguageCode Rattachment.languageCodecontent.attachment.languageCode 1..1 Composition.language 1..1
DocumentEntry.URIURI Oattachment.urlcontent.attachment.url 0..1 0..1
DocumentEntry.sizesize Oattachment.sizecontent.attachment.size 0..1 0..1
DocumentEntry.hashhash Oattachment.hashcontent.attachment.hash 0..1 0..1
DocumentEntry.titletitle Rattachment.titlecontent.attachment.title 1..1 Composition.title 1..1
DocumentEntry.formatCodeformatCode Rformatcontent.format 1..1Composition.date 1..1
DocumentEntry.creationTimecreationTime Rattachment.creationcontent.attachment.creation 1..1Composition.date 1..1
context
encounter
DocumentEntry.eventCodeListeventCodeList R2eventcontext.event 0..1 Composition.event.code 0..1
DocumentEntry.serviceStartTimeserviceStartTime R2period.startcontext.period.start 0..1 Composition.event.period.start 0..1
DocumentEntry.serviceStopTimeserviceStopTime period.endcontext.period.end 0..1 Composition.event.period.end 0..1
DocumentEntry.healthcareFacilityTypeCodehealthcareFacilityTypeCode RfacilityTypecontext.facilityType 1..1 1..1
DocumentEntry.practiceSettingCodepracticeSettingCode RpracticeSettingcontext.practiceSetting 1..1 1..1
DocumentEntry.sourcePatientInfoR sourcePatientInfoRcontext.sourcePatientInfo Composition.subject
DocumentEntry.sourcePatientIdsourcePatientId RsourcePatientInfocontext.sourcePatientInfo Composition.subject
DocumentEntry.referenceIdListreferenceIdList Orelatedcontext.related 0..* 0..*
contentTypeCode
DocumentEntry.homeCommunityIdhomeCommunityId R extension.homeCommunityId 1..11..1
DocumentEntry.objectTypeobjectType R
DocumentEntry.repositoryUniqueIdrepositoryUniqueId R


- - \ No newline at end of file diff --git a/docs/index.md b/docs/index.md index 3dd2fe4..55c3339 100644 --- a/docs/index.md +++ b/docs/index.md @@ -7,35 +7,26 @@ * [1.2 Technical specification](#13-technical-specification) * [1.3 Mapping from IHE-XDS metadata to FHIR to FHIR](#14-mapping-from-oioxml-to-fhir) -This page represents the document profiles (Danish: dokumentprofiler) used in MedComs FHIR®© standards. These profiles describe fundamental information when exchanging information as MedCom Documents. Therefore one or more document profiles are included in all MedCom’s FHIR documents. The MedCom Document profiles do not alone compose a standard but are used to describe important information in MedCom’s standards. Thus, this page includes the IG solely, and technical uses cases and does not include clinical guidelines and test protocols. +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. -> Clinical Guidelines for application and use cases are in both Danish and English. The remaining documentation will be in English. - ## 1 Standard Documentation {#standard} ### 1.1 Use Cases -Use cases describe the different scenarios a standard support. For a certain real-world scenario, it describes the requirements for the content of a Medcom Document. The purpose of the use cases is to ensure a coherent implementation and use of the MedCom Document. The descriptions are targeted IT-system vendors and the people responsible for the implementation in regions and municipalities. - -The use cases are qualified in collaboration with EPR- and vendors catering to the municipalities. +Use cases describe how to exchange documents over an [IHE XDS infrastructure](https://profiles.ihe.net/ITI/TF/Volume1/index.html). These use cases are agnostic to actual implementations and current usage and to which standardformat (CDA, FHIR and others) is exchanged over the infrastructure. The purpose of the use cases is to understand how documents are exchanged. The descriptions are targeted IT-system vendors and the people responsible for the implementation. -Below, you can find the use cases in Danish and English: +Below, you can find the use cases in English: -[Danish: Use cases](assets/documents/UseCases-DA.md)
[English: Use cases](assets/documents/UseCases-ENG.md) ### 1.2 Technical specification -The technical specifications for the MedCom Document profiles are defined in an IG. -The profiles that are part of the technical specification for a MedCom Document are: - * *Insert link to ImplemantationGuides* - -The link below gives an overview of the included profiles, what their purpose is, and which elements the system should support. Further, the structure of the standard is described and supported with examples in different degree of technical skills. +The technical specifications describes which information constitutest the foundation for MedCom FHIR Documents. These these are defined in an IG: + * MedCom Document Implementation Guide -[Click here to read an introduction to the technical specificationscan be found here.](assets/documents/Intro-Technical-Spec-ENG.md) +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. -### 1.3 Mapping from IHE-XDS metadata to FHIR to FHIR -Short description concerning the previous XXXXX standard??? that is replaced by the MedCom Document. -The document is intended to help translate the previous standard to the new FHIR standard. Furthermore, not all elements from the FHIR elements are represented in the MedCom Document; thus, it cannot stand alone for implementation. +### 1.3 Mapping from IHE XDS metadata to FHIR to FHIR +There already exists a standard for IHE XDS metadata in Denmark, 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)