Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build
Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-01-31 |
{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-TI.3",
"meta" : {
"profile" : [
🔗 "http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage internal registry services and directories.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to exchange information with external registry services and directories.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to exchange information securely with external registry services and directories.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[TI.5.1]] (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD capture and render local registry services and directory information through standards-based interfaces.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.3#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><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></span>\n \n\n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/PHRSFMR2-TI.3",
"version" : "0.1.0",
"name" : "TI_3_Registry_and_Directory_Services",
"title" : "TI.3 Registry and Directory Services (Function)",
"status" : "active",
"date" : "2024-01-31T14:45:34+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "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" : [
{
"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."
},
{
"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."
},
{
"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."
},
{
"key" : "PHRSFMR2-TI.3-04",
"label" : "TI.3#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[TI.5.1]] (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories."
},
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
},
{
"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."
}
]
}