PROBLEM_LIST

Description: |
The PROBLEM_LIST table contains data from patients' problem lists in the clinical system. The data in this table reflects the current status of all problems on the patient's problem list. In the clinical system, each problem is marked as active until it becomes (and is marked) Resolved or Deleted. At that point, by default, it will not be displayed in the application. However, any problem ever entered on this list is stored in the database and will exist in this table. Deleted and resolved problems can be viewed in the application by simply marking a checkbox to show them. Note that deleted and resolved problems can be restored by undeleting them (an option in the application). When a deleted problem is restored, its status is changed to active and the deleted date is returned to null.

Primary Key

Column Name | Ordinal Position |
--- | --- | ---
PROBLEM_LIST_ID | 1 |

Column Information

| Name | Type | Discontinued? |
--- | --- | --- | --- | ---
1 | PROBLEM_LIST_ID | NUMERIC | No |
The unique ID of this Problem List entry.
2 | DX_ID_DX_NAME | VARCHAR | No |
The name of the diagnosis.
3 | DESCRIPTION | VARCHAR | No |
The display name of the problem. Only contains data if the default display name is changed.
4 | NOTED_DATE | DATETIME | No |
Represents the first possible date that a problem could have been noted/onset on. By default, this is the problem's date of entry into the problem list. The intent of this field is to allow users to change this date to the date the problem was first diagnosed if that is different than the entry date. A problem's noted date is documented as a fuzzy date, meaning that it can capture approximate date data ("2012", "1/2012") or exact data ("3/5/2012"). This column captures the earliest date of the effective range. See NOTED_END_DATE for the latest counterpart. For example, if 2012 is documented in hyperspace, then NOTED_DATE will be 1/1/2012 and NOTED_END_DATE will be 12/31/2012.
5 | RESOLVED_DATE | DATETIME | No |
The date the problem was resolved in calendar format.
6 | DATE_OF_ENTRY | DATETIME | No |
This is the date the specific problem was last edited (i.e., a change was made, either in status, priority, etc.).
7 | ENTRY_USER_ID | VARCHAR | No |
The unique ID of the system user who last edited the problem in the patient’s Problem List. This ID may be encrypted.
8 | ENTRY_USER_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
9 | PROBLEM_CMT | VARCHAR | No |
The preview text (first characters) of the Overview note entered for a Problem List entry.
10 | CHRONIC_YN | VARCHAR | No |
This column indicates whether or not this problem is flagged as chronic.
May contain organization-specific values: No
Category Entries:
No
Yes
11 | SHOW_IN_MYC_YN | VARCHAR | No |
Indicates whether this problem will be displayed in Epic's Patient Portal, MyChart.
May contain organization-specific values: No
Category Entries:
Yes
No
12 | PROBLEM_STATUS_C_NAME | VARCHAR | No |
The category value associated with the problem’s current state: Active, Resolved, or Deleted. NOTE: Historical information regarding status changes can be viewed from within the application.
May contain organization-specific values: No
Category Entries:
Active
Resolved
Deleted
13 | CLASS_OF_PROBLEM_C_NAME | VARCHAR | No |
The category value associated with additional information for the problem, such as Acute, chronic, minor, and so on.
May contain organization-specific values: Yes
14 | PRIORITY_C_NAME | VARCHAR | No |
The category value associated with the relative severity of the problem. Problems can be given a priority (e.g., high, medium, or low). This field shows the category value associated with the current priority level assigned to a problem.
May contain organization-specific values: Yes
15 | OVERVIEW_NOTE_ID | VARCHAR | No |
This item is a link to the note record that contains the overview note pertaining to this problem record.
16 | STAGE_ID | NUMERIC | No |
The unique ID of the cancer stage record associated with the entry in the patient’s Problem List.
17 | PROBLEM_TYPE_C_NAME | VARCHAR | No |
The problem type for this problem.
May contain organization-specific values: No
Category Entries:
MEDICAL
NURSING
Hospitalization
18 | CREATING_ORDER_ID | NUMERIC | No |
The order ID of the order that created the problem.
19 | NO_STAGE_REASON_C_NAME | VARCHAR | No |
For a problem that could be staged, stores the reason why it was not staged.
May contain organization-specific values: Yes
20 | NO_STAGE_COMMENT | VARCHAR | No |
For a problem that could be staged, stores a free-text comment explaining why the problem was not staged.
21 | NO_STAGE_USER_ID | VARCHAR | No |
For a problem that could be staged, stores the user who chose not to stage it.
22 | NO_STAGE_USER_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
23 | NO_STAGE_DTTM | DATETIME (UTC) | No |
For a problem that could be staged, stores the instant when a user flagged it to not be staged.
24 | TREAT_SUMM_STATUS_C_NAME | VARCHAR | No |
Stores the treatment summary status for this problem.
May contain organization-specific values: No
Category Entries:
Has Treatment Summary
Treatment Summary Not Needed
25 | NOTED_END_DATE | DATETIME | No |
Represents the last possible date that a problem could have been noted/onset on. A problem's noted date is documented as a fuzzy date, meaning that it can capture approximate date data ("2012", "1/2012") or exact data ("3/5/2012"). This column captures the latest date of the effective range. See NOTED_DATE for the earliest counterpart. For example, if 2012 is documented in hyperspace, then NOTED_DATE will be 1/1/2012 and NOTED_END_DATE will be 12/31/2012. Note that the value may be empty, even if NOTED_DATE is populated
26 | REL_GOALS_PROBLEM_LIST_CSN_ID | NUMERIC | No |
Stores the CSN (contact serial number I.E. unique contact identifier) of the last related goals contact that was edited.
27 | REL_GOALS_INST_DTTM | DATETIME (Local) | No |
Stores the instant of the last related goals contact that was edited.
28 | PROB_STAGE_STATUS_C_NAME | VARCHAR | No |
Flag to indicate whether this problem has been staged or marked as no stage required.
May contain organization-specific values: No
Category Entries:
Has Stage
No Stage Required
29 | DIAG_START_DATE | DATETIME | No |
Represents the earliest possible date that a problem could have been diagnosed on. The latest possible date is stored in DIAG_END_DATE. If these values are the same, then the date is exact rather than fuzzy. For a problem or condition affecting a patient, the diagnosis date is defined as the date when a qualified professional first recognized the presence of that condition with sufficient certainty, regardless of whether it was fully characterized at that time. For diseases such as cancer, this may be the earliest date of a clinical diagnosis from before it was histologically confirmed, not the date of confirmation if that occurred later.
30 | DIAG_END_DATE | DATETIME | No |
Represents the last possible date that a problem could have been diagnosed on. The earliest possible date is stored in DIAG_START_DATE. If these values are the same, then the date is exact rather than fuzzy. For a problem or condition affecting a patient, the diagnosis date is defined as the date when a qualified professional first recognized the presence of that condition with sufficient certainty, regardless of whether it was fully characterized at that time. For diseases such as cancer, this may be the earliest date of a clinical diagnosis from before it was histologically confirmed, not the date of confirmation if that occurred later.