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

Elaborate on privacy and security requirements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Health Care Surveys Reporting Content Implementation Guide (FHIR)
    • 0.1.0
    • Public Health
    • (many)
    • Hide

      The IG Security section in the Capability Statement will be modified to identify the different sub-sections of FHIR Security Guidance that are applicable to the health care survey use cases and will use the format suggested as appropriate.

      Show
      The IG Security section in the Capability Statement will be modified to identify the different sub-sections of FHIR Security Guidance that are applicable to the health care survey use cases and will use the format suggested as appropriate.
    • Becky Angeles / Craig Newman : 27-0-0
    • Enhancement
    • Compatible, substantive

    Description

      I do not see a call out for privacy and security to specify how data will be handled to de-identify or protect the data extracts for these purposes-The rest of the IG looks well thought out and reasonable-the implementers will have to provide feedback on the ETL process and other proposed technical solutions to improve the expected efficiency of the process and improve performance over time. There is a great example in the FHIR_IG_RAD_DOSE_R1_D1_2022JAN table of contents that includes a section for Security in ChII as well as a glossary in Chi-these should both be included in a style guide for IGs and documents in general as the privacy/security and acronym references are often buried in SHALL statments where, for the critical nature of protecting patient information (HIPAA does not relieve that requriement by the way)-as well as dealing with acronyms for readers ready reference-improvements are easily made and ignoring them puts an undue burden on the implementers

      (Comment 3 - imported by: Chris Shawn)

      Attachments

        Activity

          People

            nageshbashyam Nagesh Bashyam
            klsalzman Keith Salzman
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: