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

Clarification on EHR requirements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Data Segmentation for Privacy (FHIR)
    • 0.1 [deprecated]
    • Security
    • Background
    • 2.3.3
    • Hide

      Agree with your comment: while this is true for outgoing security labels, wouldn't an EHR have to implement it when consuming security labeled data? Aren't security labels applicable for the display of information within the EHR? This statement seems incomplete.  We will clarify that EHRs and other systems, such as apps, and HIE have to be able to receive and respect security labels if required by policy.

      Show
      Agree with your comment: while this is true for outgoing security labels, wouldn't an EHR have to implement it when consuming security labeled data? Aren't security labels applicable for the display of information within the EHR? This statement seems incomplete.  We will clarify that EHRs and other systems, such as apps, and HIE have to be able to receive and respect security labels if required by policy.
    • Suzanne Webb / Carie Hammond: 7-0-0
    • Clarification
    • Non-substantive
    • 0.1 [deprecated]

    Description

      Section 2.3.3 says "Security labeling does not have to be implemented in the EHR system" and while this is true for outgoing security labels, wouldn't an EHR have to implement it when consuming security labeled data? Aren't security labels applicable for the display of information within the EHR? This statement seems incomplete. Please clarify if EHRs have to be able to receive and respect security labels.

      Attachments

        Activity

          People

            k.connor Kathleen Connor
            craig.newman Craig Newman
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: