Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-43036

Issues with Consent definition in Exchange Capability Statements

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • National Directory of Healthcare Providers and Services (NDH) (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • NDH Exchange Base Expanded Server Capability Statement
      NDH Exchange Base Server Capability Statement
      NDH Exchange Capability Statement
    • Hide

      Since Restriction (Consent) can be queried independently of the resource to which it applies, we will add search parameters to the exchange capability statement (the same as in the base resource definitions.

      27.93.1.1 change

      The restriction resource is always encompassed within the resource instance that requires restriction.

      to

      A resource instance that contains restricted elements will always have the relevant restriction resource(s) as contained resources.  However, restriction resource(s) can be queried independently of a resource instance. 

       

      Show
      Since Restriction (Consent) can be queried independently of the resource to which it applies, we will add search parameters to the exchange capability statement (the same as in the base resource definitions. 27.93.1.1 change The restriction resource is always  encompassed within the resource instance that requires restriction . to A resource instance that contains restricted elements will always have the relevant restriction resource(s) as contained resources.   However, restriction resource(s) can be queried independently of a resource instance.   
    • Robert Dieterle / David Pyke: 8-0-0
    • Enhancement
    • Non-compatible

      Issues with Consent in CapabilityStatement-ndh-exchange-server

      Versioning Support: remove or use no version.

      • According to FHIR R4, Contained resources SHALL NOT contain meta.versionId, meta.lastUpdated, or meta.security.
      • Additional guidance in R5 - Regarding history, it's possible to point to a contained resource within a version of the containing resource (via [type]/[id]/_history/[version]#[containedId]), but it's not possible to refer to a version of a contained resource (i.e. this is invalid: [type]/[id]#[containedId]/_history/[version])

      Reference policy: Remove reference policy for Consent.

      • When resolving references, references are resolved by looking through the 'container' resource - the one that contains the other resources. Since there are no nested contained resources, there is only one container resource.
      • References to contained resources are never resolved outside the container resource. Specifically, resolution stops at the elements Bundle.entry.resource and Parameters.parameter.resource, but not at DomainResource.contained.

      Interactions: Remove Interactions (read, search-type, vread, history-instance, history-type.

      • The resource does not exist outside of the container resource.

      Add Documentation: It may help to add documentation in the CapabilityStatement under CapabilityStatement.rest.resource.documentation that indicates that the resource SHALL only be a contained resource and that is not available outside of the container resource.

      See Contained Resources in R4: https://hl7.org/fhir/R4/references.html#contained
      See Contained Resources in R5: It is explained more in R5 and there is nothing contradictory to R4. https://hl7.org/fhir/references.html#contained

            Unassigned Unassigned
            ricklisseveld Rick Lisseveld
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: