Statement N:

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.

 Actors:
ehr Criteria N:
AS.3.2.1#01 dependent SHOULD

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 dependent SHOULD

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 dependent SHOULD

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 dependent MAY

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 dependent MAY

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.
<status value="active"/> <date value="2025-04-04T11:04:36+11:00"/> <publisher value="HL7 International / Electronic Health Records"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/ehr"/> </telecom> </contact> <description value="Maintain the Consents and Authorization directives/statements from the patient's PHR."/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> <display value="World"/> </coding> </jurisdiction> <purpose value="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."/> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="EHRSFMR2-AS.3.2.1-01"/> <label value="AS.3.2.1#01"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <key value="EHRSFMR2-AS.3.2.1-02"/> <label value="AS.3.2.1#02"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="EHRSFMR2-AS.3.2.1-03"/> <label value="AS.3.2.1#03"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="EHRSFMR2-AS.3.2.1-04"/> <label value="AS.3.2.1#04"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="EHRSFMR2-AS.3.2.1-05"/> <label value="AS.3.2.1#05"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <key value="EHRSFMR2-AS.3.2.1-06"/> <label value="AS.3.2.1#06"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="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."/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <key value="EHRSFMR2-AS.3.2.1-07"/> <label value="AS.3.2.1#07"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="The system MAY provide the ability to render Consents and Authorizations."/> </statement> </Requirements>