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

Rename Restriction profile to Consent

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US National Directory Attestation and Verification (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • NatlDirEx Restriction
    • Hide

      Restriction is appropriately named.  It is intended to restrict access and not to provide "consent". Security labels do not provide the necessary context to permit control to be linked to specific DUA items.

      Show
      Restriction is appropriately named.  It is intended to restrict access and not to provide "consent". Security labels do not provide the necessary context to permit control to be linked to specific DUA items.
    • Bob Dieterle / Cooper Thompson: 7-0-0

      The 'Restriction' profile adds an unneeded level of abstraction, which makes implementation more difficult. The 'restriction' terminology should refer to security labels in the Consent.provision.provision.securityLabel field. Additionally, the profile should enforce a double level provision model, so as to preserve compatibility with Consent resources acquired via Advanced Directives and other sources.

      Pull Request:
      https://github.com/HL7/fhir-directory-attestation/pull/62

      Preview:
      https://build.fhir.org/ig/HL7/fhir-directory-attestation/branches/43-rename-restriction/

            Unassigned Unassigned
            awatson1978 Abigail Watson
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: