Merge branch 'develop' into 14-QA

Author: ArdonToonstra

input/IKNL_PZP_IG.xml

@@ -3,8 +3,8 @@
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://hl7.org/fhir ../input-cache/schemas/R3/fhir-single.xsd">
   <id value="iknl.fhir.stu3.pzp" />
-  <url value="https://fhir.iknl.nl/fhir/ImplementationGuide/iknl.fhir.stu3.pzp" />
-  <version value="0.1.3-beta3" />
+  <url value="https://api.iknl.nl/docs/pzp/stu3/ImplementationGuide/iknl.fhir.stu3.pzp" />
+  <version value="1.0.0-alpha1" />
   <name value="PZP" />
   <title value="IKNL PZP STU3" />
   <status value="active" />
@@ -29,7 +29,7 @@
   <dependsOn>
     <uri value="https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017/2.2.20" />
     <packageId value="nictiz.fhir.nl.stu3.zib2017" />
-    <version value="2.2.20" />
+    <version value="2.3.2" />
   </dependsOn>
   <definition>
     <page>

input/ignoreWarnings.txt

@@ -97,14 +97,14 @@ ERROR: QuestionnaireResponse/HendrikHartman-20221108: QuestionnaireResponse.item
 
 # Manual check in latest version of SNOMED does find the code '1351964001'. The error might be due to a older version of SNOMED available in tx.fhir.org/r4 
 ERROR: Goal/F1-ACP-Medical-Policy-Goal: Goal.description.coding[0].code: Unknown code '1351964001' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/11000146104/version/20240930'
-ERROR: Goal/F1-ACP-Medical-Policy-Goal: Goal.description: None of the codings provided are in the value set 'Most Important Agreed-upon Goal of Medical Policy' (https://fhir.iknl.nl/fhir/ValueSet/ACP-MedicalPolicyGoal|0.1.0), and a coding from this value set is required) (codes = http://snomed.info/sct#1351964001)
+ERROR: Goal/F1-ACP-Medical-Policy-Goal: Goal.description: None of the codings provided are in the value set 'Most Important Agreed-upon Goal of Medical Policy' (https://api.iknl.nl/docs/pzp/stu3/ValueSet/ACP-MedicalPolicyGoal|0.1.0), and a coding from this value set is required) (codes = http://snomed.info/sct#1351964001)
 ERROR: ValueSet/ACP-MedicalPolicyGoal: ValueSet.compose.include[0].concept[1]: The code '1351964001' is not valid in the system http://snomed.info/sct (Unknown code '1351964001' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/11000146104/version/20240930')
 ERROR: Questionnaire/ACP-zib2020: Questionnaire.item[6].item[1].answerOption[1].value.ofType(Coding).code: Unknown code '1351964001' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/11000146104/version/20240930'
 ERROR: QuestionnaireResponse/HendrikHartman-20201001: QuestionnaireResponse.item[6].item[1].answer[0].value.ofType(Coding).code: Unknown code '1351964001' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/11000146104/version/20240930'
 
 # Manually checked: 72506001 is in the ValueSet, even in the expansion. The ValueSet in the profile bound is allowed as it restricts the zib's required binding. 72506001 zit in "Include codes from SNOMED_CT where concept DescendentOf 260787004"  
-ERROR: Device/P1-ACP-MedicalDevice.Product-ICD: Device.type: None of the codings provided are in the value set 'MedicalDevice ProductType ICD' (https://fhir.iknl.nl/fhir/ValueSet/ACP-MedicalDeviceProductType-ICD|0.1.0), and a coding from this value set is required) (codes = http://snomed.info/sct#72506001)
-ERROR: Device/P2-ACP-MedicalDevice.Product-ICD: Device.type: None of the codings provided are in the value set 'MedicalDevice ProductType ICD' (https://fhir.iknl.nl/fhir/ValueSet/ACP-MedicalDeviceProductType-ICD|0.1.0), and a coding from this value set is required) (codes = http://snomed.info/sct#72506001)
+ERROR: Device/P1-ACP-MedicalDevice.Product-ICD: Device.type: None of the codings provided are in the value set 'MedicalDevice ProductType ICD' (https://api.iknl.nl/docs/pzp/stu3/ValueSet/ACP-MedicalDeviceProductType-ICD|0.1.0), and a coding from this value set is required) (codes = http://snomed.info/sct#72506001)
+ERROR: Device/P2-ACP-MedicalDevice.Product-ICD: Device.type: None of the codings provided are in the value set 'MedicalDevice ProductType ICD' (https://api.iknl.nl/docs/pzp/stu3/ValueSet/ACP-MedicalDeviceProductType-ICD|0.1.0), and a coding from this value set is required) (codes = http://snomed.info/sct#72506001)
 
 # Definition can be found in the Nictiz package. Not sure why the IG publisher cannot access it. Also not a big deal for this IG.
 WARNING: Practitioner/F1-ACP-HealthProfessional-Practitioner-DrVanHuissen: Practitioner.identifier[0].system: No definition could be found for URL value 'http://fhir.nl/fhir/NamingSystem/agb-z'

input/pagecontent/data-exchange.md

@@ -18,11 +18,11 @@ All interactions adhere to the following principles.
 
 This approach provides granular access to the individual clinical statements that constitute the ACP. It allows applications to query for specific data points without processing an entire form.
 
-This approach is useful for applications that need to query specific parts of a patient's ACP, like treatment wishes or stated goals. While it requires multiple API calls, it provides more granular control and returns the ACP in usable resources. The below client requests are in scope of a Patient's context for which an initial request may be needed to match the Patient resource id with a identifier (e.g. BSN).
+This approach is useful for applications that need to query specific parts of a patient's ACP, like treatment wishes or stated goals. While it requires multiple API calls, it provides more granular control and returns the ACP in usable resources. The below listed client requests are in scope of a Patient's context for which an initial request may be needed to match the Patient resource id with an identifier (e.g. BSN).
 
 #### Client Requests
 
-The below listed search request show how all the ACP agreements, procedural information and relevant clinical context can be retrieved. Information on individuals involved in the ACP process are referenced from these resources and can be retrieved using the `_include` statement as defined below, or by resolving the references. Standard FHIR rules apply on the search syntax.
+The below listed search requests show how all the ACP agreements, procedural information and relevant clinical context can be retrieved. Information on individuals involved in the ACP process are referenced from these resources and can be retrieved using the `_include` statement as defined below, or by resolving the references. Standard FHIR rules apply on the search syntax.
 
 ```
 1a GET [base]/Procedure?patient=[id]&code=http://snomed.info/sct|713603004&_include:Procedure:encounter
@@ -33,11 +33,11 @@ The below listed search request show how all the ACP agreements, procedural info
 
 3 GET [base]/Consent?patient=[id]&category=http://snomed.info/sct|11341000146107&_include=Consent:actor
 
-4 GET [base]/Goal?patient=[id]&description:in=https://fhir.iknl.nl/fhir/ValueSet/ACP-MedicalPolicyGoal
+4 GET [base]/Goal?patient=[id]&description:in=https://api.iknl.nl/docs/pzp/stu3/ValueSet/ACP-MedicalPolicyGoal
 
 5 GET [base]/Observation?patient=[id]&code=http://snomed.info/sct|153851000146100,395091006,340171000146104,247751003
 
-6 GET [base]/DeviceUseStatement?patient=[id]&device.type:in=https://fhir.iknl.nl/fhir/ValueSet/ACP-MedicalDeviceProductType-ICD&_include:DeviceUseSatement:device
+6 GET [base]/DeviceUseStatement?patient=[id]&device.type:in=https://api.iknl.nl/docs/pzp/stu3/ValueSet/ACP-MedicalDeviceProductType-ICD&_include:DeviceUseSatement:device
 
 7 GET [base]/Communication?patient=[id]&reason-code=http://snomed.info/sct|713603004
 ```
@@ -80,7 +80,7 @@ This approach is used to retrieve the complete form for uniform registration of
 
 A client retrieves the `QuestionnaireResponse` by performing a `GET` search operation. The search is scoped to a specific patient and is filtered by the canonical URL of the <a href="Questionnaire-ACP-zib2017.html">ACP Questionnaire</a> to ensure that only the correct form is returned.
 
-> GET [base]/QuestionnaireResponse?subject=Patient/[id]&questionnaire=https://fhir.iknl.nl/fhir/Questionnaire/ACP-zib2017
+> GET [base]/QuestionnaireResponse?subject=Patient/[id]&questionnaire=https://api.iknl.nl/docs/pzp/stu3/Questionnaire/ACP-zib2017
 
 
 #### Server Response

input/pagecontent/data-model.md

@@ -1,4 +1,4 @@
-This page provides an overview of the FHIR resources used to represent the ACP dataset, many of which are based on nl-core profiles.
+This page provides an overview of the FHIR profiles used to represent the ACP dataset, many of which are based on nl-core profiles.
 
 ### ACP Questionnaire
 

input/pagecontent/index.md

@@ -1,8 +1,8 @@
 ### Project Description and Scope
 
-This Implementation Guide (IG) supports the Advance Care Planning (ACP) information standard (Dutch: Palliatieve Zorg Planning) and is intended for use within the palliative care domain in the Netherlands. This domain involves care for patients with an incurable illness or condition from which they are expected to die.
+This Implementation Guide (IG) supports the Advance Care Planning (ACP) information standard (Dutch: Proactieve Zorgplanning) and is intended for use within the palliative care domain in the Netherlands. This domain involves care for patients with an incurable illness or condition from which they are expected to die.
 
-Developed by the <a href="https://iknl.nl/en">Netherlands Comprehensive Cancer Organisation</a> (Dutch: Integraal kankercentrum Nederland (IKNL)), this guide provides technical direction for using FHIR to exchange ACP data. It is based on <a href="http://hl7.org/fhir/R4/index.html">HL7 FHIR R4</a> and builds on top of the <a href="https://simplifier.net/packages/nictiz.fhir.nl.r4.nl-core">Dutch Core R4 profiles</a>. 
+Developed by the <a href="https://iknl.nl/en">Netherlands Comprehensive Cancer Organisation</a> (Dutch: Integraal Kankercentrum Nederland (IKNL)), this guide provides technical direction for using FHIR to exchange ACP data. It is based on <a href="http://hl7.org/fhir/STU3/index.html">HL7 FHIR STU3</a> and builds on top of the <a href="https://simplifier.net/packages/nictiz.fhir.nl.stu3.zib2017">Dutch STU3 zib2017 profiles</a>. 
 
 This guide assumes that readers are familiar with the functional specifications of ACP and the **STU3** version of FHIR.
 
@@ -12,7 +12,7 @@ This implementation guide is a work in progress, and its quality and usefulness
 
 1. The <a href="StructureDefinition-ext-EncounterReference.html">EncounterReference extension</a> is an optional extension that enables linking the Consent, Goal, and DeviceUseStatement resources to a relevant Encounter. We invite feedback on whether this extension is truly necessary.
 
-2. The <a href="StructureDefinition-ACP-Communication.html">Communication profile</a> has been developed to capture all communication events related to advance care planning. It specifically documents whether the patient has been informed about their responsibility discuss treatment agreements with relatives. As this profile is newly created rather than derived from zib/nl-core profiles, we welcome input on its structure and modeling approach.
+2. The <a href="StructureDefinition-ACP-Communication.html">Communication profile</a> has been developed to capture all communication events related to advance care planning. It specifically documents whether the patient has been informed about their responsibility to discuss treatment agreements with relatives. As this profile is newly created rather than derived from zib/nl-core profiles, we welcome input on its structure and modeling approach.
 
 3. The <a href="Questionnaire-ACP-zib2017.html">ACP Questionnaire</a> has been developed based on the ACP form dataset and aims to preserve the zib structure as much as possible. We welcome any feedback on its design and implementation.
 

input/pagecontent/information-standard.md

@@ -1,6 +1,6 @@
 ### Information Standard: Documentation and Artifacts
 
-The advance care planning (ACP) information standard defines both the functional and technical design. This implementation guide (IG) specifies how the technical design of the ACP information standard should be applied in practice. To clarify the coherence of the different documents involved, we outline their roles here.
+The advance care planning (ACP) information standard defines both the functional and technical design. This implementation guide (IG) is the technical design and specifies how the ACP information standard should be implemented in HL7 FHIR in practice. To clarify the coherence of the different documents involved, we outline their roles here.
 
 #### Functional design (FD)
 The functional design forms the basis for this IG. It entails: 
@@ -16,9 +16,9 @@ The functional design forms the basis for this IG. It entails:
 [Functioneel Ontwerp](https://palliaweb.nl/overzichtspagina-hulpmiddelen/uniform-vastleggen-proactieve-zorgplanning-2025)  
 
 ##### Datasets, Terminology and scenarios 
-Inside the functional design there are links towards [ART-DECOR](https://decor.nictiz.nl/ad/#/pall-izppz-/project/overview).
-On Art Decor the following information is published: 
--  **Datasets** – PZP dataset and ACP form describing the structure of the information.  
+Inside the functional design there are links directing to [ART-DECOR](https://decor.nictiz.nl/ad/#/pall-izppz-/project/overview).
+On ART-DECOR the following information is published: 
+-  **Datasets** – ACP dataset and ACP form describing the structure of the information.  
 -  **Terminology & code systems** – Description of the used value sets with mappings to SNOMED CT, or domain specific codes.  
 -  **Scenarios & sequence diagrams** – Explanation and visualization of how actors and systems exchange information.
 
@@ -28,15 +28,15 @@ It describes how the ACP information standard is specifically implemented in HL7
 - FHIR profiles and extensions;
 - Use of terminology (SNOMED CT, local codes);
 - Constraints and business rules;
-- containing a traceable mapping to the dataset;
-- ACP Form Questionaire and Questionaire response example; 
+- A traceable mapping to the dataset;
+- ACP Form Questionnaire and Questionnaire response example; 
 - Examples – to support suppliers with implementation and conformance assessment.
 
-#### Test Scripts
+#### Test scripts
 To ensure correct implementation and interoperability, test scripts are provided.  
 These artefacts support vendors and implementers in validating their systems against the requirements defined in the functional and technical design.
 
-[Testscripts](https://palliaweb.nl/overzichtspagina-hulpmiddelen/uniform-vastleggen-proactieve-zorgplanning-2025)
+[Test scripts](https://palliaweb.nl/overzichtspagina-hulpmiddelen/uniform-vastleggen-proactieve-zorgplanning-2025)