Details
-
Change Request
-
Resolution: Persuasive
-
Highest
-
FHIR Data Segmentation for Privacy (FHIR)
-
0.1 [deprecated]
-
Security
-
Background
-
2.3.2
-
-
Beth Pumo/Mohammad Jafari: 3-0-0
-
Enhancement
-
Non-substantive
-
Yes
-
current
Description
Perhaps cite to some of the successful implementations? While I don’t know if the following providers use security labels as outlined in this IG or other methods of segmentation like Consent2Share, Lahey Health in Mass; Otter Tail County Collab in Minnesota, Be Healthy Partnership ACO each presented on their data segmentation implementations at ONC’s 3rd Interoperability Forum in August 2019. If these examples don’t fit the bill, I still think it could be helpful to include one or two that have implemented security labeling to the extent possible
Existing Wording:
#patient-safety - While a clinician may initially not be able to see certain sensitive information based on the patient’s decision to withhold themit, this information can still be used by Clinical Decision Support (CDS) systems to assess potential risks to patient safety (e.g. drug-to-drug interactions) and alert the clinician with warnings. Clinicians can request break-the-glass access to override such controls based on reasonable risks to patient safety as a result of warnings from a CDS. Security labeling provides the technological infrastructure which enables such application of the CDS system
Attachments
Issue Links
- is voted on by
-
BALLOT-13120 Negative - Celine Lefebvre : 2020-May-DS4P R1 STU
- Balloted