FHIR Data Segmentation for Privacy
0.2.0 - STU 1 Ballot

This page is part of the FHIR Data Segmentation for Privacy (v0.1.0: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Security Label DS4P Home Page

Introduction

This IG provides guidance for applying security labels in FHIR. Security labels are used in access control systems governing the collection, access, use, and disclosure of the target FHIR Resource(s) as required by applicable organizational, jurisdictional, or personal policies. Using security labels is an essential part of the share with protection paradigm by enabling sharing information after assigning the security labels that specify how the information can be used and subject to what restrictions.

Technical Overview

This provides guidance in the following areas:

Assigning Security Labels

The IG describes how to select a security label based on the HL7 Privacy and Security Healthcare Classification System (HCS) label adjudication algorithms, the value in establishing consensus on a default security label for representing policies or consent directives within an exchange ecosystem, and the value of establishing default security labels for information exchanged within the Trust Framework of a policy domain.

Consuming Security Labels

The IG describes how an Access Control System can use security labels to filter responses to person- or population-based queries and pushed disclosures that meets the following criteria:

  • Authorization Requirements specifying control over whether or not a client’s request for access to person- or population-level FHIR resources will be permitted.

  • Filtering Requirements specifying, at a more fine-grained level, what resources will appear in the response to a request to access personal or population-level FHIR resources. This includes approaches to filtering for the minimum necessary information based on policy.

  • Transformation Requirements specifying the requirements for applying functions or algorithms on the response to a request to access personal or population-level FHIR resources. Such algorithms modify and transform the content of a resource per applicable privacy/security policies and/or data subject’s(s’) consent directive.

  • Provenance Requirements specifying the recording and consumption of provenance information in releasing or receiving personal or population-level FHIR resources.

Structure of meta.security and Extensions

The IG describes how to structure meta.security to meet the HL7 Healthcare Privacy and Security Classification System syntactic and semantic rules and convey computable and interoperable policy within a policy domain based on Trust Contracts with binding capability statements.

It also defined a set of extensions to enable specification of the manner in which security label “privacy marks” are rendered, e.g., per CUI requirements; reference policy, contract, or consent directive instances; indicate the authority responsible for the assigned security label; and indicate whether a label has been upgraded, downgraded, or declassified, and the party responsible for doing so.

Walk-Through

The main sections of this IG are: