| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | PHRSFMR2-TI.3 |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-TI.3.html |
| URL | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.3 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | TI_3_Registry_and_Directory_Services |
| Title | TI.3 Registry and Directory Services (Function) |
| Authority | hl7 |
| Description | 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. |
| Purpose | Registry and directory service functions are critical to successfully managing the security, interoperability, and the consistency of the health record data across a PHR-S. These services enable the linking of relevant information across multiple information sources within, or external to, a PHR-S for use within an application. This applies to directories/registries internal to the PHR-S as well as directories/registries external to the PHR-S. Transmission may occur automatically or manually and may include small or large amounts of data. Directories and registries support communication between PHR 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 PHR-S interrogates a local, regional, or national registry to find the patient's previous records. From the primary care record, a remote PHR-S retrieves relevant information in conformance with applicable patient privacy and confidentiality rules. An example of local registry usage is a PHR-S application sending a query message to the Hospital Information System to retrieve a patient's demographic data. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Enable the use of registry services and directories to uniquely identify, locate and supply links for retrieval of information related to:
Registry and directory service functions are critical to successfully managing the security, interoperability, and the consistency of the health record data across a PHR-S. These services enable the linking of relevant information across multiple information sources within, or external to, a PHR-S for use within an application. This applies to directories/registries internal to the PHR-S as well as directories/registries external to the PHR-S. Transmission may occur automatically or manually and may include small or large amounts of data. Directories and registries support communication between PHR 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 PHR-S interrogates a local, regional, or national registry to find the patient's previous records. From the primary care record, a remote PHR-S retrieves relevant information in conformance with applicable patient privacy and confidentiality rules.
An example of local registry usage is a PHR-S application sending a query message to the Hospital Information System to retrieve a patient's demographic data.
| 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 a PHR-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. |
FHIR{
"resourceType": "Requirements",
"id": "PHRSFMR2-TI.3",
"meta": {
"profile": [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "ehr"
}
],
"url": "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.3",
"version": "2.0.1-ballot",
"name": "TI_3_Registry_and_Directory_Services",
"title": "TI.3 Registry and Directory Services (Function)",
"status": "active",
"date": "2025-04-03T15:15:30+00:00",
"publisher": "EHR WG",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description": "Enable the use of registry services and directories to uniquely identify, locate and supply links for retrieval of information related to:\r\n- patients and providers for healthcare purposes;\r\n- payers, health plans, sponsors, and employers for administrative and financial purposes;\r\n- public health agencies for healthcare purposes, and- healthcare resources and devices for resource management purposes.",
"purpose": "Registry and directory service functions are critical to successfully managing the security, interoperability, and the consistency of the health record data across a PHR-S. These services enable the linking of relevant information across multiple information sources within, or external to, a PHR-S for use within an application. This applies to directories/registries internal to the PHR-S as well as directories/registries external to the PHR-S. Transmission may occur automatically or manually and may include small or large amounts of data. Directories and registries support communication between PHR 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 PHR-S interrogates a local, regional, or national registry to find the patient's previous records. From the primary care record, a remote PHR-S retrieves relevant information in conformance with applicable patient privacy and confidentiality rules.\r\n\r\nAn example of local registry usage is a PHR-S application sending a query message to the Hospital Information System to retrieve a patient's demographic data.",
"statement": [
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-01",
"label": "TI.3#01",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to manage internal registry services and directories."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-02",
"label": "TI.3#02",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to exchange information with external registry services and directories."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-03",
"label": "TI.3#03",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to exchange information securely with external registry services and directories."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-04",
"label": "TI.3#04",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL conform to function [TI.5.1](Requirements-PHRSFMR2-TI.5.1.html) (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-05",
"label": "TI.3#05",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD capture and render local registry services and directory information through standards-based interfaces."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-06",
"label": "TI.3#06",
"conformance": [
"SHOULD"
],
"conditionality": true,
"requirement": "IF the system communicates with external registry services and directories (i.e., external to a PHR-S), THEN the system SHOULD capture and render information using standards-based interfaces."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-07",
"label": "TI.3#07",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "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."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-08",
"label": "TI.3#08",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "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."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-09",
"label": "TI.3#09",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "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."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-10",
"label": "TI.3#10",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "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."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
}
],
"key": "PHRSFMR2-TI.3-11",
"label": "TI.3#11",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "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."
}
]
}