HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - 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: RI.1.1.6.1 Evidence of Record Entry Output/Report Event (Function)

Official URL: http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.1.1.6.1 Version: 2.1.1
Standards status: Normative Active as of 2025-10-31 Computable Name: RI_1_1_6_1_Evidence_of_Record_Entry_Output_Report_Event

Maintain Evidence of Record Entry Output/Report Event

Statement N:

Maintain Evidence of Record Entry Output/Report Event

Description I:

Evidence of Record Entry Output/Report Event includes key metadata, ensures health record integrity (and trust) and enables record audit.

Criteria N:
RI.1.1.6.1#01
SHALL

The system SHALL audit each occurrence when an output (e.g., report, screen shot) is generated from Record Entry content.
RI.1.1.6.1#02
SHALL

The system SHALL capture identity of the organization where output/report is generated from Record Entry content.
RI.1.1.6.1#03
SHALL

The system SHALL capture identity of the patient who is subject of the Record Entry(ies) populating the output/report generated.
RI.1.1.6.1#04
SHALL

The system SHALL capture identity of the user who generated the output/report of Record Entry content.
RI.1.1.6.1#05
SHALL

The system SHALL capture identity of the system application from which the output/report is generated.
RI.1.1.6.1#06
SHALL

The system SHALL capture the type of Record Event trigger (i.e., output/report).
RI.1.1.6.1#07
SHALL

The system SHALL capture the date and time the output/report is generated.
RI.1.1.6.1#08
SHOULD

The system SHOULD capture identity of the location (i.e., network address) where the output/report is generated.
RI.1.1.6.1#09
MAY

The system MAY capture the rationale for generating the output/report.
RI.1.1.6.1#10
MAY

The system MAY capture the data, document, or other identifier for the output/report generated.
RI.1.1.6.1#11
 dependent
SHALL

The system SHALL capture when a Record Entry content output/report occurrence is known to be a disclosure, according to scope of practice, organizational policy, and/or jurisdictional law.
RI.1.1.6.1#12
SHOULD

The system SHOULD capture known and applicable permissions regarding Record Entry content output/reported including confidentiality codes, patient consent authorizations, privacy policy pointers.