HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative

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

## Requirements: AS.3.2.1 Manage Consents and Authorizations from a PHR (Function)

Official URL: http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.3.2.1 | Version: 2.1.1
Standards status: Normative Active as of 2025-12-13 | Computable Name: AS_3_2_1_Manage_Consents_and_Authorizations_from_a_PHR

Maintain the Consents and Authorization directives/statements from the patient's PHR.

Description I:

Provide the ability to manage Consents and Authorizations from a Personal Health Record including manage access control for individual elements of records to which the Consent or Authorization applies.

Criteria N:

AS.3.2.1#01 | SHOULD dependent | The system SHOULD provide the ability to manage Consents and Authorizations from a Personal Health Record according to scope of practice, organizational policy, and/or jurisdictional law.
AS.3.2.1#02 | SHOULD | The system SHOULD provide the ability to render the identity and relationship (e.g., Dr. Smith, primary care physician or Jane Doe, sister-in-law) of the person(s) for which the Consent or Authorization applies.
AS.3.2.1#03 | SHOULD dependent | The system SHOULD provide the ability to manage access control to the patient's information as specified by the Consent or Authorization according to scope of practice, organizational policy, and/or jurisdictional law.
AS.3.2.1#04 | SHOULD dependent | The system SHOULD provide the ability to manage access control for the section(s) of the patient's record to which the Consent or Authorizations applies according to scope of practice, organizational policy, and/or jurisdictional law.
AS.3.2.1#05 | MAY dependent | The system MAY provide the ability to manage access control for individual elements of records to which the Consent or Authorization applies according to scope of practice, organizational policy, and/or jurisdictional law.
AS.3.2.1#06 | MAY dependent | The system MAY provide the ability to manage access control for the time period within which the Consent or Authorization applies according to scope of practice, organizational policy, and/or jurisdictional law.
AS.3.2.1#07 | MAY | The system MAY provide the ability to render Consents and Authorizations.