From 3552e05e44a2905432e5a19b89b8e537cb1eebbf Mon Sep 17 00:00:00 2001 From: tmsMedcom <88831880+tmsMedcom@users.noreply.github.com> Date: Mon, 23 Oct 2023 08:30:51 +0200 Subject: [PATCH 1/3] Updated version of HN, versioning and grammar. #14 --- docs/_config.yml | 2 +- docs/assets/documents/NewToFHIR.md | 22 +++++++++---------- docs/index.md | 35 ++++++++++++++++-------------- 3 files changed, 31 insertions(+), 28 deletions(-) diff --git a/docs/_config.yml b/docs/_config.yml index 93b3079..010e0a9 100644 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -4,7 +4,7 @@ description: "MedCom standards based on HL7 FHIR" show_downloads: false google_analytics: theme: jekyll-theme-minimal -version: "Version 1.0.3" +version: "Version 1.0.4" fhir_version: "FHIR®© R4" releasenote: https://github.com/medcomdk/MedComLandingPage/releases thisurl: https://medcomdk.github.io/MedComLandingPage/ diff --git a/docs/assets/documents/NewToFHIR.md b/docs/assets/documents/NewToFHIR.md index 77cbf8f..8aaad41 100644 --- a/docs/assets/documents/NewToFHIR.md +++ b/docs/assets/documents/NewToFHIR.md @@ -15,15 +15,15 @@ The purpose of this section is to give an introduction to MedCom's FHIR standard ## 1 FHIR Glossary -Fast Healthcare Interoperability Resources (FHIR®©) is developed by the international organization Health Level 7 (HL7) and is an open-source standard developed to exchange healthcare-related information. FHIR defines several resources, often referred to as ‘building blocks’, each describing a delimited area within healthcare e.g., a Patient or an Encounter. These resources are generic and can therefore be used across the world. However, when using the resources in a specific context, such as communication between Danish healthcare parties, the resources need to be profiled to accommodate the use. The profiling could be to require the last name of a Patient. In some cases, it is necessary to extend the generic resources to fit the context e.g., to add a civil registration number (Danish: CPR-nummer) as a patient identifier. +Fast Healthcare Interoperability Resources (FHIR®©) is developed by the international organization Health Level 7 (HL7) and is an open-source standard developed to exchange healthcare-related information. FHIR defines several resources, often referred to as ‘building blocks’, each describing a delimited area within healthcare, e.g. a Patient or an Encounter. These resources are generic and can therefore be used across the world. However, when using the resources in a specific context, such as communication between Danish healthcare parties, the resources need to be profiled to accommodate the use. The profiling could be to require the last name of a Patient. In some cases, it is necessary to extend the generic resources to fit the context, e.g. to add a civil registration number (Danish: CPR-nummer) as a patient identifier. -When creating a MedCom FHIR standard, multiple profiles are assembled to include the information necessary to support the business requirements. Under the auspices of MedCom, these profiles will most often come from multiple Implementation Guides (IG). This decision is further addressed in section "[Why are there Multiple Implementation Guides?](FAQ.md)" that can be founded in the Frequen aked qestions page. +When creating a MedCom FHIR standard, multiple profiles are assembled to include the information necessary to support the business requirements. Under the auspices of MedCom, these profiles will most often come from multiple Implementation Guides (IG). This decision is further addressed in section "[Why are there Multiple Implementation Guides?](FAQ.md)" that can be founded in the Frequently asked questions page. -The first wave of MedCom's modernisation only includes messages, which means that there must always be a sender and a receiver. A relevant exchange paradigm could be to upload data as services or as documents where multiple receivers can get access to data or documents. If another exchange exchange paradigm is to be used, it is possible to reuse the profiles from the Core IG. This is an example of FHIR's reusability across. The optimal exchange paradigm for a standard will be considered when modernizing the next wave of MedCom standards. +The first wave of MedCom's modernisation only includes FHIR messages, which means that there must always be a sender and a receiver. A relevant exchange paradigm could be to upload data as services or as documents where multiple receivers have access to data or documents. If another exchange paradigm is to be used, it is possible to reuse the profiles from the Core IG. This is an example of FHIR's reusability across standards and exchange paradigms. The optimal exchange paradigm for a standard will be considered when modernizing the next wave of MedCom standards. -In the Table 1 you will find the most common terms and associated descriptions and examples. These terms all describe a fundamental feature in FHIR, and they make the foundation to understand FHIR, and why they are presented initially. +In the Table 1 you will find the most common terms and associated descriptions and examples. These terms all describe a fundamental feature in FHIR, and they make the foundation for understanding FHIR, and why they are presented initially. -> Note: the Table 1 uses FHIR-paths to describe exactly which element is referred to e.g. Patient.name refers to the nameelement in the Patient resource. +> Note: the Table 1 uses FHIR-paths to describe exactly which element is referred to e.g. Patient.name refers to the nameelement in the Patient resource.