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 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CP.3.3"/>
<meta>
<profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<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>Create, addend, amend, correct, authenticate, maintain, present and close, as needed, transcribed or directly-entered clinical documentation and notes.</p>
</div></span>
<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>Clinical documents and notes may be unstructured and created in a narrative form, which may be based on a template, graphic, audio, etc. The documents may also be structured documents that result from the capture of coded data. Each of these forms of clinical documentation is important and appropriate for different users and situations. To facilitate the management and documentation on how providers are responding to incoming data on orders and results, there may also be some free text or formal record on the providers' responsibility, and/or standard choices for disposition, such as Reviewed and Filed, Recall Patient, or Future Follow Up. The system may also provide support for documenting the clinician's differential diagnosis process.</p>
</div></span>
<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>
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#01</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture and render clinical documentation as 'structured', and/or 'unstructured' data.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#02</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD present documentation templates (structured or free text) to facilitate creating documentation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#03</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to present existing documentation within the patient's EHR while creating new documentation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#04</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to link documentation with specific patient encounter(s) or event(s) (e.g., office visit, phone communication, e-mail consult, laboratory result).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#05</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to render the list in a user-defined sort order.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#06</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to link clinical documents and notes to one or more problems.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#07</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to update documentation prior to finalizing it.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#08</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to tag a document or note as final, according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#09</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to render all author(s) and authenticator(s) of documentation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#10</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to render designated documents based on metadata search and filter (e.g., note type, date range, facility, author, authenticator and patient).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#11</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY provide the ability for providers to capture clinical document process disposition using standard choices (e.g., reviewed and filed, recall patient, or future follow-up).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#12</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to capture, maintain and render the clinician's differential diagnosis and the list of diagnoses that the clinician has considered in the evaluation of the patient.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#13</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to render clinical documentation using an integrated charting or documentation tool (e.g., notes, flow-sheets, radiology views, or laboratory views).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#14</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to capture clinical documentation using specialized charting tools for patient-specific requirements (e.g., age - neonates, pediatrics, geriatrics; condition - impaired renal function; medication).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#15</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to capture, maintain and render transition-of-care related information according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#16</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to tag the status of clinical documentation (e.g., preliminary, final, signed).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#17</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to tag and render lists of patients requiring follow up contact (e.g., laboratory callbacks, radiology callbacks, left without being seen).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#18</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to capture patient follow-up contact activities (e.g., laboratory callbacks, radiology callbacks, left without being seen).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#19</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to save partially completed clinical documentation (i.e., without signature) for later editing and completion.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#20</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to save partially completed clinical documentation, THEN the system SHALL render this documentation only to the authorized users (e.g., author or author's supervisors).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#21</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to save partially completed clinical documentation, THEN the system SHOULD provide the ability to tag unsigned documentation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CP.3.3#22</span>
</td>
<td style="padding-left: 4px;">
<i>conditional</i>
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to save partially completed clinical documentation, THEN the system SHOULD render a notification at specified intervals to the author.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CP.3.3"/>
<version value="0.14.0"/>
<name value="CP_3_3_Manage_Clinical_Documents_and_Notes"/>
<title value="CP.3.3 Manage Clinical Documents and Notes (Function)"/>
<status value="active"/>
<date value="2024-06-01T08:34:10+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Create, addend, amend, correct, authenticate, maintain, present and close, as needed, transcribed or directly-entered clinical documentation and notes."/>
<purpose
value="Clinical documents and notes may be unstructured and created in a narrative form, which may be based on a template, graphic, audio, etc. The documents may also be structured documents that result from the capture of coded data. Each of these forms of clinical documentation is important and appropriate for different users and situations. To facilitate the management and documentation on how providers are responding to incoming data on orders and results, there may also be some free text or formal record on the providers' responsibility, and/or standard choices for disposition, such as Reviewed and Filed, Recall Patient, or Future Follow Up. The system may also provide support for documenting the clinician's differential diagnosis process."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-01"/>
<label value="CP.3.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture and render clinical documentation as 'structured', and/or 'unstructured' data."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-02"/>
<label value="CP.3.3#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD present documentation templates (structured or free text) to facilitate creating documentation."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-03"/>
<label value="CP.3.3#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to present existing documentation within the patient's EHR while creating new documentation."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#4"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-04"/>
<label value="CP.3.3#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link documentation with specific patient encounter(s) or event(s) (e.g., office visit, phone communication, e-mail consult, laboratory result)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-05"/>
<label value="CP.3.3#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render the list in a user-defined sort order."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-06"/>
<label value="CP.3.3#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link clinical documents and notes to one or more problems."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-07"/>
<label value="CP.3.3#07"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to update documentation prior to finalizing it."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-08"/>
<label value="CP.3.3#08"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to tag a document or note as final, according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#8"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-09"/>
<label value="CP.3.3#09"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render all author(s) and authenticator(s) of documentation."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#9"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-10"/>
<label value="CP.3.3#10"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render designated documents based on metadata search and filter (e.g., note type, date range, facility, author, authenticator and patient)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#11"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-11"/>
<label value="CP.3.3#11"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability for providers to capture clinical document process disposition using standard choices (e.g., reviewed and filed, recall patient, or future follow-up)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#14"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-12"/>
<label value="CP.3.3#12"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain and render the clinician's differential diagnosis and the list of diagnoses that the clinician has considered in the evaluation of the patient."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.1.8.5#15"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-13"/>
<label value="CP.3.3#13"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render clinical documentation using an integrated charting or documentation tool (e.g., notes, flow-sheets, radiology views, or laboratory views)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-14"/>
<label value="CP.3.3#14"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture clinical documentation using specialized charting tools for patient-specific requirements (e.g., age - neonates, pediatrics, geriatrics; condition - impaired renal function; medication)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-15"/>
<label value="CP.3.3#15"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain and render transition-of-care related information according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-16"/>
<label value="CP.3.3#16"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to tag the status of clinical documentation (e.g., preliminary, final, signed)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-17"/>
<label value="CP.3.3#17"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to tag and render lists of patients requiring follow up contact (e.g., laboratory callbacks, radiology callbacks, left without being seen)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-18"/>
<label value="CP.3.3#18"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture patient follow-up contact activities (e.g., laboratory callbacks, radiology callbacks, left without being seen)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-19"/>
<label value="CP.3.3#19"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to save partially completed clinical documentation (i.e., without signature) for later editing and completion."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-20"/>
<label value="CP.3.3#20"/>
<conformance value="SHALL"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to save partially completed clinical documentation, THEN the system SHALL render this documentation only to the authorized users (e.g., author or author's supervisors)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-21"/>
<label value="CP.3.3#21"/>
<conformance value="SHOULD"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to save partially completed clinical documentation, THEN the system SHOULD provide the ability to tag unsigned documentation."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CP.3.3-22"/>
<label value="CP.3.3#22"/>
<conformance value="SHOULD"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to save partially completed clinical documentation, THEN the system SHOULD render a notification at specified intervals to the author."/>
</statement>
</Requirements>