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.5.5",
"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.5.5#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 integrate the PHR system with other systems (e.g., a laboratory Information System, Radiology System, Pharmacy System, or Hospital Information System) according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.5.5#02</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 exchange discrete information (e.g., problem list, medication, and/or allergy information) with an integrated system data repository.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.5.5#03</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 exchange clinical documents with an integrated system Clinical Document Repository.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.5.5#04</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 exchange information with systems that are integrated with the PHR system using heuristics that are defined by, and according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n\n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/PHRSFMR2-TI.5.5",
"version" : "0.1.0",
"name" : "TI_5_5_System_Integration",
"title" : "TI.5.5 System Integration (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" : "Within a given organization (for example, an institution, facility , or integrated care-delivery network), a PHR system may be directly integrated with other systems (for example, a laboratory Information System, Radiology System, Pharmacy System, or Hospital Information System). Conversely, a PHR system may access these other systems indirectly by integrating with a system that serves as the central routing mechanism for the organization. For example, the PHR system may be integrated with the Hospital Information System which then routes the PHR system's orders to a laboratory , pharmacy, or radiology service.\r\n\r\nDepending on the type of information that is exchanged within an integrated-system environment, certain heuristics may be needed that will help govern the information exchange process.",
"statement" : [
{
"key" : "PHRSFMR2-TI.5.5-01",
"label" : "TI.5.5#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to integrate the PHR system with other systems (e.g., a laboratory Information System, Radiology System, Pharmacy System, or Hospital Information System) according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"key" : "PHRSFMR2-TI.5.5-02",
"label" : "TI.5.5#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to exchange discrete information (e.g., problem list, medication, and/or allergy information) with an integrated system data repository."
},
{
"key" : "PHRSFMR2-TI.5.5-03",
"label" : "TI.5.5#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to exchange clinical documents with an integrated system Clinical Document Repository."
},
{
"key" : "PHRSFMR2-TI.5.5-04",
"label" : "TI.5.5#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY exchange information with systems that are integrated with the PHR system using heuristics that are defined by, and according to scope of practice, organizational policy, and/or jurisdictional law."
}
]
}