ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - CI Build

Publish Box goes here

Requirements: CPS.1.1 Manage a Patient Record (Function)

Active as of 2024-11-23
Statement N:

Manage a single logical record for each patient.

 Description I:

A single record is needed for legal purposes, as well as to organize it unambiguously for the provider. Health information is captured and linked to the patient record. Static data elements as well as data elements that will change over time are maintained. The patient is uniquely identified, after which the record is tied to that patient. Combining information on the same patient, or separating information where it was inadvertently captured for the wrong patient, helps maintain health information for a single patient. In the process of creating a patient record, it is at times advantageous to replicate identical information across multiple records, so that such data does not have to be re-entered. For example, when a parent registers children as new patients, the address, guarantor, and insurance data may be propagated in the children's records without having to re-enter them.

 Criteria N:
CPS.1.1#01 SHALL

The system SHALL manage a single logical record for each patient.
CPS.1.1#02 SHALL

The system SHALL provide the ability to determine the unique identity of a patient and link the record to a single patient.
CPS.1.1#03 SHALL

The system SHALL provide the ability to manage a record for a patient when the identity of the patient is unknown.
CPS.1.1#04 dependent SHOULD

The system SHOULD provide the ability to tag a record when the identity of the patient is unknown according to scope of practice, organizational policy, and/or jurisdictional law.
CPS.1.1#05 SHALL

The system SHALL provide the ability to manage more than one patient identifier for each patient record.
CPS.1.1#06 dependent SHALL

The system SHALL link key patient identifier information (e.g., system ID, medical record number) to each patient record according to scope of practice, organizational policy, and/or jurisdictional law.
CPS.1.1#07 SHOULD

The system SHOULD provide the ability to determine and render a patient by an alias and link the record to a single patient.
CPS.1.1#08 SHALL

The system SHALL provide the ability, through a controlled method, to integrate or link information for an individual patient upon recognizing the identity of the patient (e.g., if portions of a record were not yet integrated or linked because the patient's identity was not yet known, or a temporary identity (an alias) was being used, or there were duplicate records).
CPS.1.1#09 SHALL

The system SHALL provide the ability to tag the information as erroneous in the record of the patient in which it was mistakenly associated and render that information as erroneous in all renderings (i.e., outputs) containing that information.
CPS.1.1#10 SHALL

IF health information was mistakenly associated with a patient, THEN the system SHALL provide the ability to link the health information with the correct patient and tag that health information as erroneous in the mistakenly associated patient's record.
CPS.1.1#11 SHALL

The system SHALL render appropriate health information that has been tagged as erroneous in a patient's record (e.g., identify as erroneous when rendering or render in audit logs only).
CPS.1.1#12 SHALL

The system SHALL provide the ability to render parts of a single patient's record using a primary identifier (e.g., Unique patient identifier, encounter number), secondary identifiers (e.g., Social Security Number), or other information, or combination of information, which are not identifiers, but could be used to help identify the patient (e.g., name or Date of Birth).
CPS.1.1#13 SHALL

The system SHALL provide the ability to tag as obsolete, inactivated or nullified, to store in archives and to remove a patient's record in accordance with local policies and procedures, as well as applicable laws and regulation.
CPS.1.1#14 MAY

The system MAY provide the ability to auto-populate identical data to all records of related patients.
CPS.1.1#15 SHOULD

The system SHOULD provide the ability to capture anonymized patient registration.
CPS.1.1#16 SHOULD

The system SHOULD provide the ability to link the mother's and neonate's medical record numbers.
CPS.1.1#17 SHALL

The system SHALL provide the ability to render patient records based on previous names.
CPS.1.1#18 SHOULD

The system SHOULD provide the ability to link several patients that have some common demographics.