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

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/mvdzel/ehrsfm-fhir-r5/ and changes regularly. See the Directory of published versions

Requirements: CP.3.5 Acknowledge/Amend Other Provider Documentation (Function)

Official URL: http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.3.5 Version: 2.1.1
Standards status: Normative Active as of 2025-12-13 Computable Name: CP_3_5_Acknowledge_Amend_Other_Provider_Documentation

Review and indicate or amend other caregiver notes as permitted.

Description I:

Scan/review notes from physicians, nurses, technicians and other members of the health care team (e.g., Respiratory Therapist, Physical Therapist). Annotate for disparities, make additions/amendments and import when desired and permitted.

Criteria N:
CP.3.5#01 SHOULD dependent

The system SHOULD provide the ability to tag documentation by another clinician as read according to scope of practice, organizational policy, and/or jurisdictional law.
CP.3.5#02 MAY dependent

The system MAY provide the ability to tag agreement or disagreement with documentation by another provider according to scope of practice, organizational policy, and/or jurisdictional law.
CP.3.5#03 SHALL dependent

The system SHALL provide the ability for a user (e.g., supervising clinician) to annotate regarding his/her role in advising, and/or providing direct care according to scope of practice, organizational policy, and/or jurisdictional law.
CP.3.5#04 SHOULD dependent

The system SHOULD provide the ability to capture and render a co-signature of documentation according to scope of practice, organizational policy, and/or jurisdictional law.
CP.3.5#05 MAY dependent

The system MAY provide the ability to capture the approval of documentation that was captured by another user according to scope of practice, organizational policy, and/or jurisdictional law.