The system SHALL provide the ability to manage all problems associated with a PHR Account Holder.

The system SHALL provide the ability to manage a history of all problems associated with the PHR Account Holder according to user preference, organizational policy, and/ or jurisdictional law (e.g., a PHR-Account-Holder desires to delete the history of a problem after three years but a federal law indicates that the record cannot be deleted before seven years).

The system SHALL provide the ability to capture the date that the problem was documented.

The system SHOULD provide the ability to capture the chronicity (e.g., chronic or acute/self-limiting) of a problem.

The system SHALL provide the ability to capture the source, date and time of all updates to the problem list.

The system SHOULD provide the ability to manage the deactivation of a problem according to organizational policy and/or jurisdictional law.

The system SHOULD provide the ability to manage the reactivation of a previously deactivated problem.

The system SHOULD provide the ability to render inactive or resolved problems (e.g., so that a list of childhood earaches (that are no longer problematic for the adult) can be quickly viewed).

The system SHOULD provide the ability to render the problem list based on a manually-specified order.

The system SHOULD provide the ability to link episode, encounters, orders, interventions, including medications and/or other treatments, and/or notes with one or more problems.

The system MAY provide the ability to manage the consolidation or grouping of multiple problems or related problems under a single problem.

IF problems are combined or consolidated, THEN the system SHOULD maintain any links with episode encounters, orders, interventions, including medications and/or other treatments, or notes previously set.

The system SHOULD provide the ability for the PHR Account Holder to annotate problems.

The system MAY provide the ability to capture a priority, importance, rank, and/or severity score for problems as defined in a classification scheme.

IF the system provides the ability to score problems in a classification scheme, THEN the system SHALL conform to function RI.1.1 (Record Lifecycle) to define classification schemes.

The system SHOULD provide the ability to render a problem list ordered by importance or severity of the problems.

The system SHOULD provide the ability to present a problem list truncated by the number of entries.

The system MAY provide the ability to link regimen therapy taken (either provider-initiated or PHR Account Holder initiated) and outcomes with a problem. For example, the PHR Account Holder may link the use of St. John's Wort and jogging with the problem of severe migraine headaches.

The system MAY tag and render an indication that automated logic will not be applied against problems that were entered in free-text format. For example, the system discloses that it will not examine a free-text description of the PHR Account Holder's migraine headaches (or allergies) with respect to the PHR Account Holder's medication list.

The system MAY conform to PH.5.4 (Integration with Third Party Clinical Decision Support Services) to analyze possible changes to health conditions across multiple factors (e.g., if a woman becomes pregnant she might need to temporarily limit the amount of tuna consumed that have high levels of mercury; or a person who gains an great deal of weight might need to resume taking insulin or adjust the dose of Levothyroxine taken).