Source: https://confluence.hl7.org/pages/diffpagesbyversion.action?pageId=66939176&selectedPageVersions=15&selectedPageVersions=14
Timestamp: 2020-06-06 14:24:23
Document Index: 215180836

Matched Legal Cases: ['art 2002', 'art 2', 'art 2002', 'art 2', 'art 2002', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2', 'art 2']

Page Comparison - FHIR US Regulatory Security Labeling IG Proposal (v.14 vs v.15) - FHIR - Confluence
Sponsor: Security WG January 7, 2020
Publishing Lead: Mohammad Jafari/John Moehrke
Cosponsor: CBCP WG Dec 10, 2019 Approval of encompassing Cross Paradigm CUI 32 CFR Part 2002, 42 CFR Part 2, and Title 38 Section 7332 Security Labeling IGs PSS
FHIR Security Labels (Resource.meta.security)
FHIR GitHub
Security WG Confluence site - for discussion, draft content, reference material
US/security-label-regs
Security WG, Veterans Health Administration, eHealth Exchange, and Sequoia Project intend to provide ongoing support of this Implementation Guide.
Defines how systems that must comply with CFR 32 Part 2002 Controlled Unclassified Information (CUI); 42 CFR Part 2 for certain confidential substance use disorder information; and Title 38 Section 7332 using FHIR, in particular on use of computable and interoperable security labels to represent these policies.
The FHIR US Regulatory Security Labeling IG specifies how Senders and Receivers can comply with CFR 32 Part 2002 Controlled Unclassified Information (CUI); 42 CFR Part 2 for certain confidential substance use disorder information; and Title 38 Section 7332 using FHIR security labels to indicate originator and recipient obligations to comply with these policies. These laws dictate that recipients must comply with specified confidentiality protections for governed sensitive information in accordance with purpose of use limitations, obligations, and prohibitions.
Transforms between FHIR and V2 or CDA security labels are provided.
Includes a FHIR Trust Contract profile with Labeling Capability Statements for real time verification that sender/receiver are bound under agreements such as eHealth Exchange DURSA or RCE rules.
EHR Vendor participants in eHealth Exchange and trading partners of VHA and DOD
HL7 Healthcare Privacy and Security Classification System (HCS), HL7 v2.9 Security Label segments, DS4P CDA IG, FHIR DS4P Project (under development) and FHIR Security Module including the Security Label guidance.
Develop consensus Security Label codes for CUI, Part 2 or Section 7332 label.
See Cross Paradigm CUI, Part 2, and 7332 Structure and current prototype for preliminary work.
How a custodian or sender determines whether a Resource needs a CUI, Part 2 or Section 7332 label.
How a sender determines the High-Water Mark security label on a Bundle when (1) all bundled Resources have the same security labels; (2) when bundled Resources have different or no CUI, Part 2 or Section 7332 security labels.
How as receiver appropriately handles Bundle and Resource labels.
Develop Trust Contracts with capability statements about:
A sender's ability to determine the correct CUI, Part 2 or Section 7332 security labels to assign to Resources and to the Bundle as the High-Water Mark.
A receiver's ability to consume, persist, enforce, display CUI, Part 2 or Section 7332 security labels
How a sender determines whether a receiver is capable of consuming, persisting, enforcing, and displaying CUI, Part 2 or Section 7332 security labels using Trust Contract capability statements.
Dependency on the FHIR DS4P IG for foundational use cases, actors, operations, and interactions.
March 1, 2020 - Submit May NIB for FHIR Security Label IG STU 1 ballot
July 5, 2020 - Submit NIB for FHIR Security Label IG with FHIR Security Label Trust Contract and Transforms across syntaxes for STU 2 ballot
July 21, 2020 - Submit Sept Connectathon track proposal to demonstrate FHIR Security Labels with FHIR Security Label Trust Contract and Transforms across syntaxes
{"serverDuration": 242, "requestCorrelationId": "86896c26999c07f2"}