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-AS.2",
"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>Capture and management of patient administrative information across locations in order to support care, including directories, and/or registries.</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>A patient directory/registry may contain information including, but not limited to: full name, residence or physical location, alternate contact person, primary phone number, and relevant health status information. Various views of Patient Registry or Directory information may constructed to accommodate various user's needs. Examples of specific directory views are presented in the following functions.</p>\n<p>The patient administrative information also includes patient location information (within a facility as well as home care location(s)); as well as the patient's registration in healthcare programs.</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>AS.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\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 provide the ability to harmonize a patient's demographic information with an external system (e.g., a centralized registry or health information exchange) triggered by clinical or administrative events (e.g., arrival of a new patient, reappearance of a past patient at a given facility, or periodic synchronization of health information).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2#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 transmit a notification to an external system (e.g., an external Client Registry or a Personal Health Record System) that a patient's demographic information was modified.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2#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 tag patient information with the current status (e.g., active, admitted, inactive, or discharged).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2#04</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 manage the administrative status and location of the patient during care within a facility. (e.g., waiting to see a provider, admitted, holding, waiting for nurse, waiting for consultant, or on the way to the Operating Room).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.2",
"version" : "0.14.0",
"name" : "AS_2_Manage_Patient_Demographics__Location_and_Synchronization",
"title" : "AS.2 Manage Patient Demographics, Location and Synchronization (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" : "Capture and management of patient administrative information across locations in order to support care, including directories, and/or registries.",
"purpose" : "A patient directory/registry may contain information including, but not limited to: full name, residence or physical location, alternate contact person, primary phone number, and relevant health status information. Various views of Patient Registry or Directory information may constructed to accommodate various user's needs. Examples of specific directory views are presented in the following functions.\n\nThe patient administrative information also includes patient location information (within a facility as well as home care location(s)); as well as the patient's registration in healthcare programs.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2-01",
"label" : "AS.2#01",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to harmonize a patient's demographic information with an external system (e.g., a centralized registry or health information exchange) triggered by clinical or administrative events (e.g., arrival of a new patient, reappearance of a past patient at a given facility, or periodic synchronization of health information)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2-02",
"label" : "AS.2#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to transmit a notification to an external system (e.g., an external Client Registry or a Personal Health Record System) that a patient's demographic information was modified."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2-03",
"label" : "AS.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to tag patient information with the current status (e.g., active, admitted, inactive, or discharged)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2-04",
"label" : "AS.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage the administrative status and location of the patient during care within a facility. (e.g., waiting to see a provider, admitted, holding, waiting for nurse, waiting for consultant, or on the way to the Operating Room)."
}
]
}