[MM-997] "additionalSource" extension cannot be applied on Consent resource - Nictiz BITS

Xporter

Details

Type: Wijzigingsverzoek
Status: Gesloten
Priority: 3
Resolution: Resolved
Fix Version/s: 2019.01 - Maart 2020
Component/s: None

Blokkerend:
Nee
Informatiestandaard:

BgZ, Basisgegevens GGZ, BgLZ
Informatiestandaard onderdelen:

FHIR
Impact:
This is an extension specific to the zib-TreatmentDirective profile, yet formally it cannot be used here - although no problems have been raised so far. Applying this change makes the extension usable again.
Voorgestelde oplossing:
Change context of consentAdditionSources extension from "Consent.source[x]" to "Consent"
Release notes:

Hide

The consent-additionalSources extension for the zib-TreatmentDirective profile had a context restriction on Consent.source[x], while it actually was applied on Consent directly. This fix removes that restriction.

Show
The consent-additionalSources extension for the zib-TreatmentDirective profile had a context restriction on Consent.source [x] , while it actually was applied on Consent directly. This fix removes that restriction.

Description

The zib-TreatmentDirective profile on the Consent resource uses the consent-additionalSources extension to bind multiple zib-AdvanceObjective instances. However, it cannot be applied on the root of the Consent resource; the extension states:

<context value="Consent.source[x]" />

This should be changed to:

<context value="Consent" />

Attachments

Issue Links

gerelateerd aan

MM-430 Extensie op zib BehandelAanwijzing voor ondersteuning meerdere wilsverklaringen

Gesloten

MM-806 Correctie op MM-430: foutieve FHIRPath constraints en locatie

Gesloten

Activity

People

Assignee:: Pieter Edelman

Reporter:: Pieter Edelman

Watchers:: 0 Start watching this issue

Dates

Created:: 12-03-2020 15:17

Updated:: 24-02-2021 10:47

Resolved:: 25-03-2020 16:06

Jigit Development

Branches:

Pull requests: