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: TI.3 Registry and Directory Services (Function)

Page standards status: Informative

Statement N:

Enable the use of registry services and directories to uniquely identify, locate and supply links for retrieval of information related to:

- patients and providers for healthcare purposes;
- payers, health plans, sponsors, and employers for administrative and financial purposes;
- public health agencies for healthcare purposes, and- healthcare resources and devices for resource management purposes.

Description I:

Registry and directory service functions are critical to successfully managing the security, interoperability, and the consistency of the health record data across an EHR-S. These services enable the linking of relevant information across multiple information sources within, or external to, an EHR-S for use within an application. This applies to directories/registries internal to the EHR-S as well as directories/registries external to the EHR-S. Transmission may occur automatically or manually and may include small or large amounts of data. Directories and registries support communication between EHR Systems and may be organized hierarchically or in a federated fashion. For example, a patient being treated by a primary care physician for a chronic condition may become ill while out of town. The new provider's EHR-S interrogates a local, regional, or national registry to find the patient's previous records. From the primary care record, a remote EHR-S retrieves relevant information in conformance with applicable patient privacy and confidentiality rules.

An example of local registry usage is an EHR-S application sending a query message to the Hospital Information System to retrieve a patient's demographic data.

Actors:
ehr Criteria N:

TI.3#01 | SHALL | The system SHALL provide the ability to manage internal registry services and directories.
TI.3#02 | SHALL | The system SHALL provide the ability to exchange information with external registry services and directories.
TI.3#03 | SHALL | The system SHALL provide the ability to exchange information securely with external registry services and directories.
TI.3#04 | SHALL | The system SHALL conform to function TI.5.1 (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories.
TI.3#05 | SHOULD | The system SHOULD capture and render local registry services and directory information through standards-based interfaces.
TI.3#06 | conditional SHOULD | IF the system communicates with external registry services and directories (i.e., external to an EHR-S), THEN the system SHOULD capture and render information using standards-based interfaces.
TI.3#07 | SHOULD | The system SHOULD provide the ability to determine the unique identity of a patient through the use of internal, and/or external registry services or directories.
TI.3#08 | MAY | The system MAY provide the ability to determine links to healthcare information regarding a patient through the use of internal, and/or external registry services or directories.
TI.3#09 | MAY | The system MAY provide the ability to determine the unique identity of a provider through the use of internal, and/or external registry services or directories.
TI.3#10 | MAY | The system MAY provide the ability to determine the identity of payers, health plans and sponsors for administrative or financial purposes through the use of internal, and/or external registry services or directories.
TI.3#11 | MAY | The system MAY provide the ability to determine the identity of employers for administrative or financial purposes through the use of internal, and/or external registry services or directories.