Description I:

When a clinician fills out an assessment, data entered is matched against data already in the system to identify potential linkages and optimize patient care. For example, the system could scan the medication list and the knowledge base to see if any of the symptoms are side effects of medication already prescribed. Important diagnoses could be brought to the doctor's attention, for instance ectopic pregnancy in a woman of child bearing age, or appendicitis in a geriatric patient who has abdominal pain.

Criteria N:
CPS.3.2#01 SHOULD

The system SHOULD provide the ability to analyze assessment data entered during the encounter against health evidence based standards and best practices.
CPS.3.2#02 MAY

The system MAY analyze health data and patient context-driven assessments in terms of practice standards, and render notifications (e.g., of possible additional testing, possible diagnoses, or adjunctive treatment).
CPS.3.2#03 SHOULD

The system SHOULD provide the ability to analyze assessment data against data in the patient-specific problem list.
CPS.3.2#04 SHOULD

The system SHOULD provide the ability to manage care setting specific templates.
CPS.3.2#05 MAY

The system MAY provide the ability to render alerts based on patient-specific clinical data (e.g., age for neonates, pediatrics, geriatrics; conditions for impaired renal function; medication).
CPS.3.2#06 SHOULD

The system SHOULD provide the ability to maintain integrated, chief complaint -driven documentation templates.
CPS.3.2#07 SHOULD

The system SHOULD provide the ability to maintain integrated, diagnosis-driven documentation templates.
CPS.3.2#08 SHOULD

The system SHOULD provide the ability to maintain integrated, disposition-driven documentation templates.
<status value="active"/> <date value="2025-12-19T08:44:27+00:00"/> <publisher value="HL7 International / Electronic Health Records"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/ehr"/> </telecom> </contact> <description value="Offer prompts based on patient-specific data at the point of information capture for assessment purposes."/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="US"/> </coding> </jurisdiction> <purpose value="When a clinician fills out an assessment, data entered is matched against data already in the system to identify potential linkages and optimize patient care. For example, the system could scan the medication list and the knowledge base to see if any of the symptoms are side effects of medication already prescribed. Important diagnoses could be brought to the doctor's attention, for instance ectopic pregnancy in a woman of child bearing age, or appendicitis in a geriatric patient who has abdominal pain."/> <derivedFrom value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CPS.3.2"/> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-01"/> <label value="CPS.3.2#01"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to analyze assessment data entered during the encounter against health evidence based standards and best practices."/> <derivedFrom value="CPS.3.2#1"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-02"/> <label value="CPS.3.2#02"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="The system MAY analyze health data and patient context-driven assessments in terms of practice standards, and render notifications (e.g., of possible additional testing, possible diagnoses, or adjunctive treatment)."/> <derivedFrom value="CPS.3.2#2"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-03"/> <label value="CPS.3.2#03"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to analyze assessment data against data in the patient-specific problem list."/> <derivedFrom value="CPS.3.2#3"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-04"/> <label value="CPS.3.2#04"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to manage care setting specific templates."/> <derivedFrom value="CPS.3.2#4"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-05"/> <label value="CPS.3.2#05"/> <conformance value="MAY"/> <conditionality value="false"/> <requirement value="The system MAY provide the ability to render alerts based on patient-specific clinical data (e.g., age for neonates, pediatrics, geriatrics; conditions for impaired renal function; medication)."/> <derivedFrom value="CPS.3.2#5"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-06"/> <label value="CPS.3.2#06"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to maintain integrated, chief complaint -driven documentation templates."/> <derivedFrom value="CPS.3.2#6"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-07"/> <label value="CPS.3.2#07"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to maintain integrated, diagnosis-driven documentation templates."/> <derivedFrom value="CPS.3.2#7"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-CPS.3.2-08"/> <label value="CPS.3.2#08"/> <conformance value="SHOULD"/> <conditionality value="false"/> <requirement value="The system SHOULD provide the ability to maintain integrated, disposition-driven documentation templates."/> <derivedFrom value="CPS.3.2#8"/> </statement> </Requirements>