HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

Requirements: TI.1.8 Patient Privacy and Confidentiality (Function)

Page standards status: Informative
Statement N:

Enable the enforcement of the applicable jurisdictional and organizational patient privacy rules as they apply to various parts of a PHR-S through the implementation of security mechanisms.

 Description I:

Patients' privacy and the confidentiality of PHRs are violated if access to PHRs occurs without authorization. Violations or potential violations can impose tangible economic or social losses on affected patients, as well as less tangible feelings of vulnerability and pain. Fear of potential violations discourages patients from revealing sensitive personal information that may be relevant to diagnostic and treatment services. Rules for the protection of privacy and confidentiality may vary depending upon the vulnerability of patients and the sensitivity of records. Strongest protections should apply to the records of minors and the records of patients with stigmatized conditions. Authorization to access the most sensitive parts of a PHR is most definitive if made by the explicit and specific consent of the patient. Please see the definition of masking in the glossary.

Organizational practices related to privacy and security jurisdictional laws could be called into question during a legal proceeding. Adherence to applicable laws supports the credibility and trustworthiness of the organization.

 Criteria N:
TI.1.8#01 dependent SHALL

The system SHALL provide the ability to maintain compliance with requirements for patient privacy and confidentiality according to scope of practice, organizational policy, and/or jurisdictional law (e.g., US HIPAA Privacy Rules, US Federal Conditions of Participation for Medicare/Medicaid Providers).
TI.1.8#02 SHALL

The system SHALL conform to function TI.1.1 (Entity Authentication).
TI.1.8#03 SHALL

The system SHALL conform to function TI.1.2 (Entity Authorization).
TI.1.8#04 SHALL

The system SHALL conform to function TI.1.3 (Entity Access Control).
TI.1.8#05 SHALL

The system SHALL conform to function TI.1.5 (Non-Repudiation).
TI.1.8#06 SHALL

The system SHALL conform to function TI.1.6 (Secure Data Exchange).
TI.1.8#07 SHALL

The system SHALL conform to function TI.2 (Audit).
TI.1.8#08 dependent SHALL

The system SHALL provide the ability to maintain varying levels of confidentiality according to patient preferences, user role, scope of practice, organizational policy, and/or jurisdictional law.
TI.1.8#09 dependent SHALL

The system SHALL provide the ability to mask parts of the electronic health record (e.g., medications, conditions, sensitive documents) from disclosure according to patient preferences, user role, scope of practice, organizational policy, and/or jurisdictional law.
TI.1.8#10 dependent SHALL

The system SHALL provide the ability to unmask (override a mask) in emergency or other specific situations in accordance with users' role, and according to scope of practice, organizational policy, and/or jurisdictional law.
TI.1.8#11 dependent SHOULD

The system SHOULD provide the ability to maintain indicators (flags) to health record users that content has been masked in accordance with users' role, and according to scope of practice, organizational policy, and/or jurisdictional law.
TI.1.8#12 conditional SHALL

IF the system allows a user to unmask (override a mask) in an emergency or other specific situation, THEN the system SHALL provide the ability to capture the reason for unmasking or overriding the mask.
TI.1.8#13 SHALL

The system SHALL provide the ability to manage patient consents to, or restrictions against, any access to data.
TI.1.8#14 dependent SHALL

The system SHALL provide the ability to manage a privacy policy according to patient preferences, user role, scope of practice, organizational policy, and/or jurisdictional law.
TI.1.8#15 dependent SHALL

The system SHALL provide the ability to control access by specified user(s) to a particular patient health record either by inclusion or exclusion according to patient preferences, user role, scope of practice, organizational policy, and/or jurisdictional law.