From 6b29ad235abc8308b919202d3e8e2211ac9e15b9 Mon Sep 17 00:00:00 2001 From: Harmke Koning Date: Thu, 28 May 2026 12:44:01 +0200 Subject: [PATCH 1/6] textual improvements data exchange --- input/pagecontent/data-exchange.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/input/pagecontent/data-exchange.md b/input/pagecontent/data-exchange.md index 708d2b1..fb20e7d 100644 --- a/input/pagecontent/data-exchange.md +++ b/input/pagecontent/data-exchange.md @@ -56,13 +56,15 @@ The below listed search requests show how all the ACP agreements, procedural inf 1. Both requests are designed to retrieve the same information, but with different approaches: * A) Retrieves `Procedure` resources representing ACP procedures and includes the associated `Encounter` resource where the procedure took place. * B) Retrieves `Encounter` resources that list an ACP procedure as their reason, and includes the referenced resources in the result. Request A is generally preferred because `Encounter.patient` may not always be present; if absent, it indicates the patient was not involved in the Encounter. Using request A ensures these cases are included as well. -2. Retrieves `Consent` resources for Treatment Directives and includes the agreement parties (Patient, ContactPersons, and HealthProfessionals). -3. Retrieves `Consent` resources for Advance Directives and includes the representatives (ContactPersons). +2. Retrieves `Consent` resources for Treatment Directives and includes the agreement parties (`Patient`, `ContactPersons`, and `HealthProfessionals`). +3. Retrieves `Consent` resources for Advance Directives and includes the representatives (`ContactPersons`). 4. Retrieves `Goal` resources related to advance care planning. 5. Retrieves `Observation` resources related to specific wishes and plans, as defined by the profiles in the Implementation Guide. 6. Retrieves `DeviceUseStatement` resources for devices representing an ICD, and includes the corresponding `Device` resource. 7. Retrieves `CommunicationRequest` resources representing all communication requests related to the ACP procedure. +For `ContactPersons` and `HealthProfesionals` there is no specific query as according to the model there are references made to these persons. If there is a legal representative we expect that to be present in `patient.contact`. For related persons attending the encounter a reference is expected to be made in `encounter.participant`. + #### Advanced Search Parameters Supported The queries above use several search parameter types and modifiers: * `_include`: Returns referenced resources in the same `Bundle`, reducing the need for additional API calls. From 86fcd563191212c42028df037146d23a8f20ed11 Mon Sep 17 00:00:00 2001 From: Harmke Koning Date: Fri, 29 May 2026 10:59:38 +0200 Subject: [PATCH 2/6] Update text to distinghuish zib and resources --- input/pagecontent/data-exchange.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/input/pagecontent/data-exchange.md b/input/pagecontent/data-exchange.md index fb20e7d..bc0cf61 100644 --- a/input/pagecontent/data-exchange.md +++ b/input/pagecontent/data-exchange.md @@ -56,14 +56,14 @@ The below listed search requests show how all the ACP agreements, procedural inf 1. Both requests are designed to retrieve the same information, but with different approaches: * A) Retrieves `Procedure` resources representing ACP procedures and includes the associated `Encounter` resource where the procedure took place. * B) Retrieves `Encounter` resources that list an ACP procedure as their reason, and includes the referenced resources in the result. Request A is generally preferred because `Encounter.patient` may not always be present; if absent, it indicates the patient was not involved in the Encounter. Using request A ensures these cases are included as well. -2. Retrieves `Consent` resources for Treatment Directives and includes the agreement parties (`Patient`, `ContactPersons`, and `HealthProfessionals`). -3. Retrieves `Consent` resources for Advance Directives and includes the representatives (`ContactPersons`). +2. Retrieves `Consent` resources for Treatment Directives and includes the agreement parties (patient, ContactPersons, and HealthProfessionals). +3. Retrieves `Consent` resources for Advance Directives and includes the representatives (ContactPersons). 4. Retrieves `Goal` resources related to advance care planning. 5. Retrieves `Observation` resources related to specific wishes and plans, as defined by the profiles in the Implementation Guide. 6. Retrieves `DeviceUseStatement` resources for devices representing an ICD, and includes the corresponding `Device` resource. 7. Retrieves `CommunicationRequest` resources representing all communication requests related to the ACP procedure. -For `ContactPersons` and `HealthProfesionals` there is no specific query as according to the model there are references made to these persons. If there is a legal representative we expect that to be present in `patient.contact`. For related persons attending the encounter a reference is expected to be made in `encounter.participant`. +For `RelatedPerson` and `Practitioner` there is no specific query as according to the model there are references made to these resources. If there is a legal representative we expect that to be present in `Patient.contact`. For related persons attending the encounter a reference is expected to be made in `Encounter.participant`. #### Advanced Search Parameters Supported The queries above use several search parameter types and modifiers: From 4e47396c67ba1b620c9a94bfa72428f0f212be8c Mon Sep 17 00:00:00 2001 From: Harmke Koning Date: Tue, 2 Jun 2026 13:22:46 +0200 Subject: [PATCH 3/6] start changelog --- input/pagecontent/changelog.md | 11 +++++++++++ input/pagecontent/data-exchange.md | 2 +- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/input/pagecontent/changelog.md b/input/pagecontent/changelog.md index db4eaf9..db65a2a 100644 --- a/input/pagecontent/changelog.md +++ b/input/pagecontent/changelog.md @@ -1,3 +1,14 @@ +### 1.0.0-rc3 +| Issue | Short Description | +|-------|-------------------| +| [#137](https://github.com/IKNL/PZP-FHIR-R4/issues/137) | Replaced legally capable extension on Patient with an Observation to better support representation of legal capacity. | +||| +| [#151](https://github.com/IKNL/PZP-FHIR-R4/issues/151) | Corrected search URLs by fixing code parameter syntax to ensure proper OR behavior. | +| [#138](https://github.com/IKNL/PZP-FHIR-R4/issues/138) | Updated yes/no questions in the questionnaire to use `boolean` instead of `choice`. | +| [#133](https://github.com/IKNL/PZP-FHIR-R4/issues/133) | Aligned API documentation by correcting CommunicationRequest category code in sequence diagram and updating CapabilityStatement to use CommunicationRequest. | +| [#129](https://github.com/IKNL/PZP-FHIR-R4/issues/129) | Clarified ContactPerson artifact documentation for `.relationship:roleAdditional` slice. | +| [#127](https://github.com/IKNL/PZP-FHIR-R4/issues/127) | Added missing `subject` references to QuestionnaireResponse examples and improved consistency of author/source formatting. | + ### 1.0.0-rc2 | Issue | Short Description | diff --git a/input/pagecontent/data-exchange.md b/input/pagecontent/data-exchange.md index bc0cf61..ae4fdf7 100644 --- a/input/pagecontent/data-exchange.md +++ b/input/pagecontent/data-exchange.md @@ -56,7 +56,7 @@ The below listed search requests show how all the ACP agreements, procedural inf 1. Both requests are designed to retrieve the same information, but with different approaches: * A) Retrieves `Procedure` resources representing ACP procedures and includes the associated `Encounter` resource where the procedure took place. * B) Retrieves `Encounter` resources that list an ACP procedure as their reason, and includes the referenced resources in the result. Request A is generally preferred because `Encounter.patient` may not always be present; if absent, it indicates the patient was not involved in the Encounter. Using request A ensures these cases are included as well. -2. Retrieves `Consent` resources for Treatment Directives and includes the agreement parties (patient, ContactPersons, and HealthProfessionals). +2. Retrieves `Consent` resources for Treatment Directives and includes the agreement parties (Patient, ContactPersons, and HealthProfessionals). 3. Retrieves `Consent` resources for Advance Directives and includes the representatives (ContactPersons). 4. Retrieves `Goal` resources related to advance care planning. 5. Retrieves `Observation` resources related to specific wishes and plans, as defined by the profiles in the Implementation Guide. From 1ea68ed157014e9f6f835074d88355f1e1874e53 Mon Sep 17 00:00:00 2001 From: Harmke Koning Date: Tue, 2 Jun 2026 16:40:46 +0200 Subject: [PATCH 4/6] Updated changelog --- input/pagecontent/changelog.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/input/pagecontent/changelog.md b/input/pagecontent/changelog.md index db65a2a..0eb470e 100644 --- a/input/pagecontent/changelog.md +++ b/input/pagecontent/changelog.md @@ -2,12 +2,19 @@ | Issue | Short Description | |-------|-------------------| | [#137](https://github.com/IKNL/PZP-FHIR-R4/issues/137) | Replaced legally capable extension on Patient with an Observation to better support representation of legal capacity. | -||| +| [#132](https://github.com/IKNL/PZP-FHIR-R4/issues/132) | Updated Procedure.code to support multiple ACP procedure codes and ensure compliance with zib/nl-core terminology requirements. | +| [#157](https://github.com/IKNL/PZP-FHIR-R4/issues/157) | Updated CommunicationRequest cardinalities by requiring subject, requester and sender, and adding invariant to ensure request date is present. | | [#151](https://github.com/IKNL/PZP-FHIR-R4/issues/151) | Corrected search URLs by fixing code parameter syntax to ensure proper OR behavior. | +| [#136](https://github.com/IKNL/PZP-FHIR-R4/issues/136) | Improved search query documentation by clarifying how to retrieve specific data items such as ContactPerson (e.g. legal representative). | +| [#135](https://github.com/IKNL/PZP-FHIR-R4/issues/135) | Updated questionnaire answer options to use answerValueSet references where possible and improve alignment with terminology, resolving validation issues. | +| [#138](https://github.com/IKNL/PZP-FHIR-R4/issues/138) | Updated a couple questionnaire items from `choice` to `boolean` to resolve validation issues and align with the dataset. | +| [#126](https://github.com/IKNL/PZP-FHIR-R4/issues/126) | Updated questionnaire to align with latest dataset changes, including support for 'other' treatment directives and addition of missing MeetMethode elements. | +| [#131](https://github.com/IKNL/PZP-FHIR-R4/issues/131) | Replaced fixed questionnaire answer options for 'Functie (specialisme)' with AGB and UZI value sets. | | [#138](https://github.com/IKNL/PZP-FHIR-R4/issues/138) | Updated yes/no questions in the questionnaire to use `boolean` instead of `choice`. | | [#133](https://github.com/IKNL/PZP-FHIR-R4/issues/133) | Aligned API documentation by correcting CommunicationRequest category code in sequence diagram and updating CapabilityStatement to use CommunicationRequest. | | [#129](https://github.com/IKNL/PZP-FHIR-R4/issues/129) | Clarified ContactPerson artifact documentation for `.relationship:roleAdditional` slice. | | [#127](https://github.com/IKNL/PZP-FHIR-R4/issues/127) | Added missing `subject` references to QuestionnaireResponse examples and improved consistency of author/source formatting. | +| [#156](https://github.com/IKNL/PZP-FHIR-R4/issues/156) | Applied QA fixes including ValueSet renaming to avoid duplicate titles. | ### 1.0.0-rc2 From 733a5be729f0b267ce3f4b43c13d55d39e5b443a Mon Sep 17 00:00:00 2001 From: Harmke Koning Date: Tue, 2 Jun 2026 16:46:39 +0200 Subject: [PATCH 5/6] missing enter for rendering --- input/pagecontent/changelog.md | 1 + 1 file changed, 1 insertion(+) diff --git a/input/pagecontent/changelog.md b/input/pagecontent/changelog.md index 0eb470e..1792f7a 100644 --- a/input/pagecontent/changelog.md +++ b/input/pagecontent/changelog.md @@ -1,4 +1,5 @@ ### 1.0.0-rc3 + | Issue | Short Description | |-------|-------------------| | [#137](https://github.com/IKNL/PZP-FHIR-R4/issues/137) | Replaced legally capable extension on Patient with an Observation to better support representation of legal capacity. | From 50ec7fa5c7f411b194aef5bf34f3d2b80f2e4295 Mon Sep 17 00:00:00 2001 From: Ardon Toonstra Date: Tue, 2 Jun 2026 17:00:08 +0200 Subject: [PATCH 6/6] Minor formatting improvements --- input/pagecontent/changelog.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/input/pagecontent/changelog.md b/input/pagecontent/changelog.md index 0eb470e..3f4205b 100644 --- a/input/pagecontent/changelog.md +++ b/input/pagecontent/changelog.md @@ -2,13 +2,13 @@ | Issue | Short Description | |-------|-------------------| | [#137](https://github.com/IKNL/PZP-FHIR-R4/issues/137) | Replaced legally capable extension on Patient with an Observation to better support representation of legal capacity. | -| [#132](https://github.com/IKNL/PZP-FHIR-R4/issues/132) | Updated Procedure.code to support multiple ACP procedure codes and ensure compliance with zib/nl-core terminology requirements. | -| [#157](https://github.com/IKNL/PZP-FHIR-R4/issues/157) | Updated CommunicationRequest cardinalities by requiring subject, requester and sender, and adding invariant to ensure request date is present. | +| [#132](https://github.com/IKNL/PZP-FHIR-R4/issues/132) | Updated `Procedure.code` to support multiple ACP procedure codes and ensure compliance with zib/nl-core terminology requirements. | +| [#157](https://github.com/IKNL/PZP-FHIR-R4/issues/157) | Updated CommunicationRequest cardinalities by requiring `subject`, `requester` and `sender`, and adding an invariant to ensure either `authoredOn` or a reference to Encounter. | | [#151](https://github.com/IKNL/PZP-FHIR-R4/issues/151) | Corrected search URLs by fixing code parameter syntax to ensure proper OR behavior. | | [#136](https://github.com/IKNL/PZP-FHIR-R4/issues/136) | Improved search query documentation by clarifying how to retrieve specific data items such as ContactPerson (e.g. legal representative). | -| [#135](https://github.com/IKNL/PZP-FHIR-R4/issues/135) | Updated questionnaire answer options to use answerValueSet references where possible and improve alignment with terminology, resolving validation issues. | +| [#135](https://github.com/IKNL/PZP-FHIR-R4/issues/135) | Updated questionnaire answer options to use `answerValueSet` references where possible and improve alignment with terminology, resolving validation issues. | | [#138](https://github.com/IKNL/PZP-FHIR-R4/issues/138) | Updated a couple questionnaire items from `choice` to `boolean` to resolve validation issues and align with the dataset. | -| [#126](https://github.com/IKNL/PZP-FHIR-R4/issues/126) | Updated questionnaire to align with latest dataset changes, including support for 'other' treatment directives and addition of missing MeetMethode elements. | +| [#126](https://github.com/IKNL/PZP-FHIR-R4/issues/126) | Updated questionnaire to align with latest dataset changes, including support for 'other' treatment directives and addition of missing 'MeetMethode' elements. | | [#131](https://github.com/IKNL/PZP-FHIR-R4/issues/131) | Replaced fixed questionnaire answer options for 'Functie (specialisme)' with AGB and UZI value sets. | | [#138](https://github.com/IKNL/PZP-FHIR-R4/issues/138) | Updated yes/no questions in the questionnaire to use `boolean` instead of `choice`. | | [#133](https://github.com/IKNL/PZP-FHIR-R4/issues/133) | Aligned API documentation by correcting CommunicationRequest category code in sequence diagram and updating CapabilityStatement to use CommunicationRequest. |