ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-06-01 |
{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-TI.5.5",
"meta" : {
"profile" : [
🔗 "http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support the integration of the EHR system with related systems.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Within a given organization (for example, an institution, facility , or integrated care-delivery network), an EHR system may be directly integrated with other systems (for example, a laboratory Information System, Radiology System, Pharmacy System, or Hospital Information System). Conversely, an EHR 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 EHR system may be integrated with the Hospital Information System which then routes the EHR system's orders to a laboratory , pharmacy, or radiology service.</p>\n<p>Depending 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.\nExample:\nFor example, an immunization order and a hearing test should be cancelled for a patient who recently died; a heuristic algorithm should manage that cancellation request from the EHR system to interested members within the integrated network. Another example is that certain information imported into a care plan should be exported to some members of the care team, while other members of the care team might only receive a notice that the new information exists.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \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 <i>dependent</i>\n \n \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 EHR 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 </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 \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 </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 \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 </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 <i>dependent</i>\n \n \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 EHR 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 </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.5.5",
"version" : "0.14.0",
"name" : "TI_5_5_System_Integration",
"title" : "TI.5.5 System Integration (Function)",
"status" : "active",
"date" : "2024-06-01T08:34:10+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Support the integration of the EHR system with related systems.",
"purpose" : "Within a given organization (for example, an institution, facility , or integrated care-delivery network), an EHR system may be directly integrated with other systems (for example, a laboratory Information System, Radiology System, Pharmacy System, or Hospital Information System). Conversely, an EHR 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 EHR system may be integrated with the Hospital Information System which then routes the EHR system's orders to a laboratory , pharmacy, or radiology service.\n\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.\nExample:\nFor example, an immunization order and a hearing test should be cancelled for a patient who recently died; a heuristic algorithm should manage that cancellation request from the EHR system to interested members within the integrated network. Another example is that certain information imported into a care plan should be exported to some members of the care team, while other members of the care team might only receive a notice that the new information exists.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-TI.5.5-01",
"label" : "TI.5.5#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to integrate the EHR 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."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-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."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-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."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-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 EHR system using heuristics that are defined by, and according to scope of practice, organizational policy, and/or jurisdictional law."
}
]
}