EHRS-FM IG

ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build

Publish Box goes here

Requirements: CP.1.4 Manage Problem List (Function)

Active as of 2024-08-12
Statement N:

Create and maintain patient-specific problem lists.

 Description I:

A problem list may include, but is not limited to chronic conditions, diagnoses, or symptoms, injury/poisoning (both intentional and unintentional), adverse effects of medical care (e.g., drugs, surgical), functional limitations, visit or stay-specific conditions, diagnoses, or symptoms. Problem lists are managed over time, whether over the course of a visit or stay or the life of a patient, allowing documentation of historical information and tracking the changing character of problem(s) and their priority. The source (e.g., the provider, the system id, or the patient) of the updates should be documented. All pertinent dates are stored, including date noted or diagnosed, dates of any changes in problem specification or prioritization, and date of resolution. This might include time stamps, where useful and appropriate. The entire problem history for any problem in the list is viewable.

 Criteria N:
CP.1.4#01 SHALL

The system SHALL provide the ability to manage, as discrete data, all active problems associated with a patient.

 Satisfied by:
  1. https://hl7.org/fhir/condition.html
CP.1.4#02 SHALL

The system SHALL capture, maintain and render a history of all problems associated with a patient.
CP.1.4#03 SHALL

The system SHALL provide the ability to manage the status of each problem (e.g., active, inactive, resolved).

 Satisfied by:
  1. https://hl7.org/fhir/R5/condition-definitions.html#Condition.clinicalStatus
CP.1.4#04 SHALL

The system SHALL provide the ability to manage relevant dates including the onset date and date(s) of problem status change (e.g., inactivation or resolution date).
CP.1.4#05 SHALL

The system SHALL provide the ability to manage information about the chronicity duration (e.g., chronic, acute/self-limiting) of a problem.
CP.1.4#06 SHOULD

The system SHOULD provide the ability to manage information regarding the information source (i.e. informant) of the problem.
CP.1.4#07 SHALL

The system SHALL conform to function [[RI.1.1.17]] (Deprecate/Retract Record Entries) to enable the inactivation or deprecation of a problem.
CP.1.4#08 MAY

The system MAY provide the ability to update an inactive problem in order to re-activate it.
CP.1.4#09 SHOULD

The system SHOULD provide the ability to render the list in a user-defined sort order.
CP.1.4#10 SHALL

The system SHALL provide the ability to render only active problems.
CP.1.4#11 SHOULD

The system SHOULD provide the ability to link one or more problem(s) in the Problem list to encounters.
CP.1.4#12 MAY

The system MAY provide the ability to link one or more problem(s) in the Problem List to medications.
CP.1.4#13 MAY

The system MAY provide the ability to link one or more problem(s) in the Problem list to orders.
CP.1.4#14 MAY

The system MAY provide the ability to link one or more problem(s) in the Problem list to medical equipment.
CP.1.4#15 MAY

The system MAY provide the ability to link one or more problem(s) in the Problem list to prosthetic/orthotic devices.
CP.1.4#16 MAY

The system MAY provide the ability to link one or more problem(s) in the Problem list to notes.
CP.1.4#17 SHALL

The system SHALL provide the ability to link orders, medical equipment, prosthetic/orthotic devices, and medications to one or more codified problems.
CP.1.4#18 SHALL

The system SHALL provide the ability to capture free text problems and render them in a manner that distinguishes them from coded problem entries.
CP.1.4#19 SHALL

The system SHALL tag and render an indicator that interaction checking will not occur against free text problems.
CP.1.4#20 SHALL

The system SHALL provide the ability to capture a problem into the problem list using standardized coding schemas (e.g., ICD or SNOMED).
CP.1.4#21 SHALL

The system SHALL provide the ability to manage free text comments associated with the problem.
CP.1.4#22 MAY

The system MAY provide the ability to manage the severity of a problem using a standards based classification scheme.
CP.1.4#23 SHOULD

The system SHOULD provide the ability to link actions taken and outcomes with a problem.
CP.1.4#24 dependent MAY

The system MAY provide the ability to manage problems for known genetically based illnesses (e.g., single allele carrier status of a genetic trait or disease) according to scope of practice, organizational policy, and/or jurisdictional law.
CP.1.4#25 dependent MAY

The system MAY provide the ability to manage a known single allele carrier status of a genetic trait or disease according to scope of practice, organizational policy, and/or jurisdictional law, and subject to patient's preferences and consent.
CP.1.4#26 SHOULD

The system SHOULD provide the ability to manage the linking of problems on the problem list, i.e., creating hierarchies or nestings within the problem list.