Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions input/pagecontent/changelog.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,22 @@
### 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. |
| [#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. |
| [#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

| Issue | Short Description |
Expand Down
2 changes: 2 additions & 0 deletions input/pagecontent/data-exchange.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,8 @@ The below listed search requests show how all the ACP agreements, procedural inf
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 `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:
* `_include`: Returns referenced resources in the same `Bundle`, reducing the need for additional API calls.
Expand Down
Loading