HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative
HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative
HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions
| Page standards status: Normative |
{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-TI.3",
"meta" : {
"profile" : [
🔗 "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"language" : "en",
"text" : {
"status" : "extensions",
"div" : "<div xml:lang=\"en\" xmlns=\"http://www.w3.org/1999/xhtml\" lang=\"en\">\n \n \n <div id=\"description\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>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.</p>\n<p>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.</p>\n</div></div>\n \n \n \n <div id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></div>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#01\n </td>\n <td style=\"padding-left: 4px;\">\n SHALL\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>The system SHALL provide the ability to manage internal registry services and directories.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#02\n </td>\n <td style=\"padding-left: 4px;\">\n SHALL\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>The system SHALL provide the ability to exchange information with external registry services and directories.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#03\n </td>\n <td style=\"padding-left: 4px;\">\n SHALL\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>The system SHALL provide the ability to exchange information securely with external registry services and directories.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#04\n </td>\n <td style=\"padding-left: 4px;\">\n SHALL\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>The system SHALL conform to function <a href=\"Requirements-PHRSFMR2-TI.5.1.html\">TI.5.1</a> (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#05\n </td>\n <td style=\"padding-left: 4px;\">\n SHOULD\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>The system SHOULD capture and render local registry services and directory information through standards-based interfaces.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#06\n </td>\n <td style=\"padding-left: 4px;\">\n SHOULD\n \n <span style=\"border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>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.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#07\n </td>\n <td style=\"padding-left: 4px;\">\n SHOULD\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>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.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#08\n </td>\n <td style=\"padding-left: 4px;\">\n MAY\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>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.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#09\n </td>\n <td style=\"padding-left: 4px;\">\n MAY\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>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.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#10\n </td>\n <td style=\"padding-left: 4px;\">\n MAY\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>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.</p>\n</div>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n TI.3#11\n </td>\n <td style=\"padding-left: 4px;\">\n MAY\n \n \n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n <div><p>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.</p>\n</div>\n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "normative"
},
{
"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",
"name" : "TI_3_Registry_and_Directory_Services",
"title" : "TI.3 Registry and Directory Services (Function)",
"status" : "active",
"date" : "2025-12-07T09:26:53+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."
}
]
}
IG © 2023 EHR WG.
Package hl7.ehrs.uv.phrsfmr2#2.0.1 based on FHIR 5.0.0.
Generated
2025-12-07
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change