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.1 Originate/Retain Record Lifecycle Event (Function)

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

Originate and Retain Record Entry (1 instance)

Statement N:

Originate and Retain Record Entry (1 instance)

Description I:

Occurs when an agent causes the system to: a) initiate capture of potential record content, and b) incorporate that content into the storage considered a permanent part of the health record.

Reference: ISO 21089-2018, Section 15.1.

Criteria N:
RI.1.1.1#01
SHALL

The system SHALL provide the ability to capture (originate) a Record Entry instance corresponding to an Action instance and context.
RI.1.1.1#02
SHALL

The system SHALL capture a unique instance identifier for each Record Entry.
RI.1.1.1#03
SHALL

The system SHALL capture the signature event (e.g., digital signature) of the origination entry Author, binding signature to Record Entry content.
RI.1.1.1#04
SHALL

The system SHALL provide the ability to capture both structured and unstructured content in Record Entries.
RI.1.1.1#05
SHALL

The system SHALL provide the ability to capture Record Entries from information recorded during system downtime.
RI.1.1.1#06
SHOULD

The system SHOULD provide the ability to integrate Record Entries from Information recorded during system downtime.
RI.1.1.1#07
SHALL

The system SHALL provide the ability to capture the date/time an Action was taken or data was collected if different than date/time of the Record Entry.
RI.1.1.1#08
SHOULD

The system SHOULD capture metadata that identifies the source of non-originated Record Entry (e.g., templated, copied, duplicated, or boilerplate information).
RI.1.1.1#09
MAY

The system MAY provide the ability to tag unstructured Record Entry content to organize it according to need, for example, in a time-related fashion or by application-specific groups (such as photographs, handwritten notes, or auditory sounds), or by order of relative importance.
RI.1.1.1#10
MAY

The system MAY capture and maintain a Record Entry encoded as a standards-based data object (e.g., HL7 Continuity of Care, other HL7 CDA R2 Document, ISO 13606 artifact).
RI.1.1.1#11
MAY

The system MAY capture and maintain a standards-based data object to mirror (be duplicate and synchronous with) internal Record Entry representation.