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

Publication Build: This will be filled in by the publication tooling

## Requirements: RI.1.1.19.1 Evidence of Record Entry Merge Event (Function)

Page standards status: Informative

Statement N:

Maintain Evidence of Record Entry Merge Event

Description I:

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

Actors:
ehr Criteria N:

RI.1.1.19.1#01 | SHALL | The system SHALL audit each occurrence when Record Entries are merged (e.g., same patient, multiple sets of record entries).
RI.1.1.19.1#02 | SHALL | The system SHALL capture identity of the organization where Record Entries are merged.
RI.1.1.19.1#03 | SHALL | The system SHALL capture identity of the patient who is subject of merged Record Entries.
RI.1.1.19.1#04 | SHALL | The system SHALL capture the identifier for the source set of Record Entries.
RI.1.1.19.1#05 | SHALL | The system SHALL capture the identifier for the target set of Record Entries.
RI.1.1.19.1#06 | SHALL | The system SHALL capture identity of the user merging Record Entries.
RI.1.1.19.1#07 | SHALL | The system SHALL capture identity of the system application which merged Record Entries.
RI.1.1.19.1#08 | SHALL | The system SHALL capture the type of Record Event trigger (i.e., merge).
RI.1.1.19.1#09 | SHALL | The system SHALL capture the date and time Record Entries are merged.
RI.1.1.19.1#10 | SHALL | The system SHALL capture identity of the location (i.e., network address) where Record Entries are merged.
RI.1.1.19.1#11 | MAY | The system MAY capture the rationale for merging Record Entries.
RI.1.1.19.1#12 | MAY | The system MAY capture the data, document or other identifier for merged Record Entries.