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

The Consent framework should be a reusable infrastructure element rather than being re-defined in domain-specific APIs/IGs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • current
    • Pharmacy
    • (many)
      Consent Workflows
    • Hide

      The consent-related content in the Specialty Medication Enrollment FHIR IG doesn't involve  patient approval for actual release or transfer of patient data, but instead focuses on the workflow for obtaining patient consent for activities associated with fulfilling their specialty medication prescription.

       

      Show
      The consent-related content in the Specialty Medication Enrollment FHIR IG doesn't involve  patient approval for actual release or transfer of patient data, but instead focuses on the workflow for obtaining patient consent for activities associated with fulfilling their specialty medication prescription.  
    • Frank McKinney / John Hatem : 6-0-0

    Description

      While the need for a consent framework is understandable, it should be addressed globally across FHIR. Ideally this specification will provide guidance to implementers on how to address privacy and data segmentation to Specialty Medication Enrollment based on specifications that CBCC and Security WGs have already created. If the existing specifications are insufficient, it would be useful to propose a new work item/proposal to CBCP to address the missing capabilities. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            ioana13 Ioana Singureanu
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: