Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

"additionalSource" extension cannot be applied on Consent resource

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:

This should be changed to:

Verduidelijking van 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.

Proposed solution (NL)

Change context of consentAdditionSources extension from "Consent.source[x]" to "Consent"

Proposed solution (EN)

None

Release notes (NL)

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.

Release notes (EN)

None

Activity

Show:

Vincent Goris March 25, 2020 at 3:06 PM

Wijziging gepubliceerd en ticket gesloten.

Pieter Edelman March 12, 2020 at 2:27 PM

Wijzigingen staan klaar in branch .

Resolved
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Informatiestandaard onderdelen

FHIR-package

Information standard

BgZ
Basisgegevens GGZ
BgLZ

Fix versions

Priority

Better Excel Exporter

Created March 12, 2020 at 2:17 PM
Updated January 12, 2024 at 12:52 PM
Resolved March 25, 2020 at 3:06 PM