PatientProblemHistory
This table contains data relating to the history of problems from patients' problem lists in the clinical system.
| Column Name | Type | Description |
|---|---|---|
| PhysicalDeploymentOwnerIdentifier | VARCHAR | ID of the physical deployment owner for this record. Physical owners will be where the data is hosted, either on the cross-over server or the owner deployment. |
| ProblemOverviewNotePreviewText | VARCHAR | The preview text (first characters) of the Overview note entered for a Problem List entry. |
| ShowInPatientPortalIndicator | VARCHAR | Indicates whether this problem will be displayed in Epic's Patient Portal, MyChart. |
| HistoricalIsChronicFlag | VARCHAR | This column indicates whether or not this problem was flagged as chronic as of this historical event. |
| LastRelatedGoalContactSerialNumber | NUMERIC | Stores the CSN (contact serial number I.E. unique contact identifier) of the last related goals contact that was edited. |
| HistoricalProblemDisplayName | VARCHAR | The historical display name of the problem. Only contains data if the default display name is changed. |
| ProblemStagingStatusIndicator | INTEGER | Flag to indicate whether this problem has been staged or marked as no stage required. |
| HistoricalProblemEncounterContactSerialNumber | NUMERIC | Contact Serial Number (CSN) of the patient encounter where this historical problem list was documented. |
| CreatingOrderId | NUMERIC | The order ID of the order that created the problem. |
| LastDiagnosisDate | DATETIME | 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. |
| ProblemStagingExclusionReason | INTEGER | For a problem that could be staged, stores the reason why it was not staged. |
| LastPresentOnAdmissionIndicator | INTEGER | This column has the history of the present on admission indicator, which indicates if a hospital problem was present on admission or not. |
| ProblemHistoryUrgencyLevel | INTEGER | The category value associated with the level of urgency of the problem at the time this history event was recorded. |
| NoStagingTimestamp | DATETIME | For a problem that could be staged, stores the instant when a user flagged it to not be staged. |
| HistoricalProblemStatusValue | INTEGER | The category value associated with the problem's state: Active, Resolved, or Deleted as of this historical event. |
| ProblemHistoryLineNumber | INTEGER | Used to identify the particular problem within the historical problems |
| FirstNotedDate | DATETIME | 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. |
| ProblemDiagnosisStartDate | DATETIME | 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. |
| ProblemDisplayName | VARCHAR | The display name of the problem. Only contains data if the default display name is changed. |
| ProblemListHistoryWorkflowModuleCategory | INTEGER | History for item 151. The category value corresponding to the Problem List Manager workflow that added/edited the problem. This is usually the same as the internal ID. If you use IntraConnect, this is the Community ID (CID). |
| ProblemListDiagnosisIdentifier | NUMERIC | The unique ID of the diagnosis record associated with the entry in the patient’s Problem List. Note: This is NOT the ICD9 diagnosis code. It is an internal identifier that is typically not visible to a user. |
| IsHistoricalPrincipalProblemFlag | VARCHAR | This column indicates whether or not this problem was flagged as the principal problem as of this historical event. |
| HistoricalProblemOverviewComment | VARCHAR | The historical preview text (first characters) of all the Overview notes entered for a Problem List entry. |
| LogicalDeploymentOwnerIdentifier | VARCHAR | ID of the logical deployment owner for this record. Logical owners show the deployment where the record was created but doesn't represent if the record is a part of version skew. |
| ProblemOverviewNoteIdentifier | VARCHAR | This item is a link to the note record that contains the overview note pertaining to this problem record. |
| LastModifiedDate | DATETIME | This is the date the specific problem was last edited (i.e., a change was made, either in status, priority, etc.). |
| DiagnosisEarliestPossibleDate | DATETIME | Represents the earliest possible date that a problem could have been diagnosed on at a particular edit. The latest possible date is stored in HX_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. |
| ProblemTreatmentSummaryStatus | INTEGER | Stores the treatment summary status for this problem. |
| LastRelatedGoalsEditInstant | DATETIME | Stores the instant of the last related goals contact that was edited. |
| HistoricalNotedEndDate | DATETIME | Represents the historical value of 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 HX_NOTED_DATE for the latest counterpart. For example, if 2012 is documented in hyperspace, then HX_NOTED_DATE will be 1/1/2012 and HX_NOTED_END_DATE will be 12/31/2012. Note that the value may be empty, even if HX_NOTED_DATE is populated |
| ExternalProblemIdentifier | VARCHAR | Store the external ID for a problem list LPL record |
| IsChronicFlag | VARCHAR | This column indicates whether or not this problem is flagged as chronic. |
| PhysicalDeploymentOwnerIdentifier | VARCHAR | ID of the physical deployment owner for this record. Physical owners will be where the data is hosted, either on the cross-over server or the owner deployment. |
| ProblemCurrentState | INTEGER | 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. |
| ProblemRecordArchivedIndicator | VARCHAR | Indicates whether the Problem List record is archived at the record level. |
| HistoricalProblemSeverityPriorityCode | INTEGER | 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 priority level assigned to a problem when this action was taken. |
| ProblemStageHistoryIdentifier | NUMERIC | This column holds the history of all stages ever associated with this problem. |
| LastEditWorkflowModule | INTEGER | The category value corresponding to the Problem List Manager workflow that last added/edited the problem. This is usually the same as the internal ID. If you use IntraConnect, this is the Community ID (CID). |
| ProblemPriorityLevel | INTEGER | 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. |
| ProblemListIdentifier | NUMERIC | The unique ID of this Problem List entry. |
| PatientIdentification | VARCHAR | The unique ID of the patient record for this row. This column is frequently used to link to the PATIENT table. |
| LastPossibleDiagnosisDate | DATETIME | Represents the last possible date that a problem could have been diagnosed on at a particular edit. The earliest possible date is stored in HX_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. |
| Problem | NUMERIC | The unique ID of the cancer stage record associated with the entry in the patient’s Problem List. |
| ProblemLastNotedDate | DATETIME | 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 |
| ProblemClassification | INTEGER | The category value associated with additional information for the problem, such as Acute, chronic, minor, and so on. |
| LogicalDeploymentOwnerIdentifier | VARCHAR | ID of the logical deployment owner for this record. Logical owners show the deployment where the record was created but doesn't represent if the record is a part of version skew. |
| HistoricalProblemFirstNotedDate | DATETIME | Represents the historical value of the first 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 earliest date of the effective range. See HX_NOTED_END_DATE for the latest counterpart. For example, if 2012 is documented in hyperspace, then HX_NOTED_DATE will be 1/1/2012 and HX_NOTED_END_DATE will be 12/31/2012. |
| LastEditorUserIdentifier | VARCHAR | The unique ID of the system user who last edited the problem in the patient’s Problem List. This ID may be encrypted. |
| ProblemStageExclusionComment | VARCHAR | For a problem that could be staged, stores a free-text comment explaining why the problem was not staged. |