| Package | hl7.ehrs.uv.ehrsfmr2 |
| Type | Requirements |
| Id | EHRSFMR2-RI.1.3 |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/ehrsfmr2/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2-RI.1.3.html |
| URL | http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.1.3 |
| Version | 2.1.1-ballot |
| Status | active |
| Date | 2025-05-13T15:11:00+00:00 |
| Name | RI_1_3_Record_States |
| Title | RI.1.3 Record States (Header) |
| Realm | uv |
| Authority | hl7 |
| Description | Manage Record States |
| Purpose | Record Entries may reside in various states that must be managed. An important underlying principle for managing record states is the need to retain Record Entries that have been viewed for patient care purposes even if the Entry has not been completed or attested. This principle has important legal impact because it provides an account of what the provider viewed and relied on for clinical decision-making. For example, if Record Entry content was available in pending state and a clinician used the information to make decisions, it is important to retain the pending version even after the final version was available. Determining if Record Entry content was used for patient care may be challenging. Access logs could provide a mechanism to determine if the information was used. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage Record States
Record Entries may reside in various states that must be managed. An important underlying principle for managing record states is the need to retain Record Entries that have been viewed for patient care purposes even if the Entry has not been completed or attested. This principle has important legal impact because it provides an account of what the provider viewed and relied on for clinical decision-making. For example, if Record Entry content was available in pending state and a clinician used the information to make decisions, it is important to retain the pending version even after the final version was available. Determining if Record Entry content was used for patient care may be challenging. Access logs could provide a mechanism to determine if the information was used.
FHIR{
"resourceType": "Requirements",
"id": "EHRSFMR2-RI.1.3",
"meta": {
"profile": [
"http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMHeader"
]
},
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "ehr"
}
],
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.1.3",
"version": "2.1.1-ballot",
"name": "RI_1_3_Record_States",
"title": "RI.1.3 Record States (Header)",
"status": "active",
"date": "2025-05-13T15:11:00+00:00",
"publisher": "HL7 International / Electronic Health Records",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description": "Manage Record States",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"purpose": "Record Entries may reside in various states that must be managed. An important underlying principle for managing record states is the need to retain Record Entries that have been viewed for patient care purposes even if the Entry has not been completed or attested. This principle has important legal impact because it provides an account of what the provider viewed and relied on for clinical decision-making. For example, if Record Entry content was available in pending state and a clinician used the information to make decisions, it is important to retain the pending version even after the final version was available. Determining if Record Entry content was used for patient care may be challenging. Access logs could provide a mechanism to determine if the information was used."
}