Uploaded image for project: 'MedMij Standaarden'
  1. MedMij Standaarden
  2. MM-997

"additionalSource" extension cannot be applied on Consent resource

Details

    • Wijzigingsverzoek
    • Status: Gesloten
    • 3
    • Resolution: Resolved
    • 2019.01 - Maart 2020
    • None
    • Nee
    • BgZ, Basisgegevens GGZ, BgLZ
    • FHIR
    • 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.
    • Change context of consentAdditionSources extension from "Consent.source[x]" to "Consent"
    • 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

          Activity

            People

              edelman@nictiz.nl Pieter Edelman
              edelman@nictiz.nl Pieter Edelman
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jigit Development

                  Branches:
                  Pull requests: