Consent basis

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Community-Based Care and Privacy
    • Consent
    • Hide

      Create Consent.Rule as a 0..1 data type uri with the description "The computable policy that is the basis of this consent for which the exceptions apply."

      Update Consent.Policy to 0..* and indicate that is a uri reference to a resource that is the regulations/form/legal requirement.

      Constraint added that at least one of Consent.Rule or Consent.Policy must exist

      Show
      Create Consent.Rule as a 0..1 data type uri with the description "The computable policy that is the basis of this consent for which the exceptions apply." Update Consent.Policy to 0..* and indicate that is a uri reference to a resource that is the regulations/form/legal requirement. Constraint added that at least one of Consent.Rule or Consent.Policy must exist
    • John Moehrke/Kathleen Connor: 16-0-2
    • Enhancement
    • Non-compatible
    • DSTU2

      There is a need to indicate regulations for which the Consent is covering. That is the basis of the Consent rules.

      The use-case is more driven by query for existing consents related to regulation X. For example, find the consents for Patient Y, that cover USA 42 CFR Part 2.

      This element is not often needed, so an extension would be fine. Would be good to see if other regions have similar need.

      I originally understood that the existing extension consent-basis was for this purpose, but this extension seems to be for some other need, and is specific to exceptions.

            Assignee:
            Unassigned
            Reporter:
            John Moehrke
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: