DOCS_RCVD_PROBS
Description:
This table stores problems received from outside sources.

Primary Key
Column Name Ordinal Position
DOCUMENT_ID 1
CONTACT_DATE_REAL 2
LINE 3

Column Information
Name Type Discontinued?
1 DOCUMENT_ID NUMERIC No
This item stores the Received Document record ID.
2 CONTACT_DATE_REAL FLOAT No
A unique contact date in decimal format. The integer portion of the number indicates the date of contact. The digits after the decimal distinguish different contacts on the same date and are unique for each contact on that date. For example, .00 is the first/only contact, .01 is the second contact, etc.
3 LINE INTEGER No
The line number for the information associated with this contact. Multiple pieces of information can be associated with this contact.
4 CONTACT_DATE DATETIME No
The date of this contact in calendar format.
5 PROB_REF_ID VARCHAR No
This item stores the unique reference identifier associated with the problem.
6 PROB_NAME VARCHAR No
This item stores the problem name sent by the external source.
7 PROB_ID_DX_NAME VARCHAR No
The name of the diagnosis.
8 PROB_DAT_NOT_DT DATETIME No
This item stores the problem noted date.
9 PROB_DAT_RSLV_DT DATETIME No
This item stores the problem resolved date.
10 PROB_PRIORITY VARCHAR No
This item stores the priority of the problem.
11 PROB_PRIORITY_ID_C_NAME VARCHAR No
This item stores the mapped problem priority category ID.
May contain organization-specific values: Yes
12 PROB_IS_CHRONIC_YN VARCHAR No
This item is set if the problem is chronic.
May contain organization-specific values: No
Category Entries:
No
Yes
13 PROB_STATUS VARCHAR No
This item stores the problem status.
14 PROB_STATUS_ID_C_NAME VARCHAR No
This item stores the mapped problem status category value.
May contain organization-specific values: No
Category Entries:
Active
Resolved
Deleted
15 PROB_SRC_LPL_ID NUMERIC No
This item stores the ID of the source problem.
16 PROB_TYP_OF_CHNG_C_NAME VARCHAR No
This item stores the type of change associated with the problem.
May contain organization-specific values: No
Category Entries:
Receive
Edit
Delete
17 PROB_SRC_DXR_CSN NUMERIC No
This item will store the contact serial number of the received document record that owns the instance of this problem.
18 PROB_OVRD_LPL_ID NUMERIC No
This item stores the record identifier of the local problem that this external problem should be grouped with.
19 PROB_COMMENTS_ID VARCHAR No
This item stores the identifier of the Notes (HNO) record that stores problem comments.
20 PROB_LAST_UPD_DTTM DATETIME (UTC) No
This item stores the date and time when the problem was last updated by the external system.
21 PROB_PT_SRC_APP_C_NAME VARCHAR No
If this problem is a patient-entered problem (i.e. Received Documents type = 25), this item stores the application which was used to edit the problem for the contact (e.g. MyChart or Welcome). If blank, this is assumed to be MyChart.
May contain organization-specific values: Yes
Category Entries:
MyChart
Welcome
22 PROB_DT_NOTED_NF_C_NAME VARCHAR No
This item stores the nullFlavor value from the effectiveTime low node in a received CDA document.
May contain organization-specific values: No
Category Entries:
No Information
Invalid
Derived
Other
Negative infinity
Positive infinity
Un-encoded
Masked
Not applicable
Unknown
Asked but unknown
Temporarily unavailable
Not asked
Sufficient quantity
Trace
Not present
User Selected
23 PROB_DT_RESOLV_NF_C_NAME VARCHAR No
This item stores the nullFlavor value from the effectiveTime high node in a received CDA document.
The category values for this column were already listed for column: PROB_DT_NOTED_NF_C_NAME
24 PROB_STATE_C_NAME VARCHAR No
This item stores the value from the statusCode node for a problem entry in a received CDA document.
May contain organization-specific values: No
Category Entries:
Other
Normal
Aborted
Active
Cancelled
Completed
Held
New
Suspended
Nullified
Obsolete
25 PROB_STATUS_ENTRY_C_NAME VARCHAR No
This item stores the value from the status entryRelationship node in a received CDA document. This item itself is not the status of the problem.
May contain organization-specific values: No
Category Entries:
Active
Inactive
Resolved
26 PROB_HIST_STATUS_C_NAME VARCHAR No
The item indicates whether the problem is current or historic.
May contain organization-specific values: No
Category Entries:
Current
Historical
Inactive
Discontinued
Deleted
27 PROB_HIST_DATE DATETIME No
This item stores the date that the historical status for this problem is valid through. After this date, the historical status needs to be rechecked.
28 PROB_SRC_WPR_ID VARCHAR No
Stores the ID of the MyChart user who edited the problem for the contact.
29 PROB_EVENT_IDENT VARCHAR No
This item stores the ID of the event that is associated with a problem. In cases where there are multiple encounters that link to a problem, the earliest encounter is represented here.
30 PROB_DUP_LPL_ID NUMERIC No
Stores the Problem List ID of an internal problem that is a duplicate of this row in the Received Document.
31 PROB_PAT_ENC_CSN_ID NUMERIC No
Stores the contact serial number of the encounter that the problem was added on
32 PROB_DX_LATERALITY_C_NAME VARCHAR No
The laterality category ID for the problem.
May contain organization-specific values: Yes
Category Entries:
Side unknown
Left
Right
Bilateral
Never
Possible
Always
Not determined
33 PROB_ANATOMICAL_LOC_CODE VARCHAR No
The anatomical location code of the problem.
34 PROB_ANATOMICAL_LOC_DISP_NAME VARCHAR No
The anatomical location display name of the problem.
35 PROB_OVERVIEW_NOTE_ID VARCHAR No
The unique ID of the Note for the overview note of this problem.
36 PROB_COMMENTS_CHECKSUM VARCHAR No
This item stores the checksum of the Overview note and most recent Assessment and Plan Note along with the creation instant of the most recent Assessment and Plan Note in UTC and the Author's first and last name of the Assessment and Plan note. The format of the data is "checksum C127 instant C127 first C127 last". C127 is character 127. There are no spaces between the data elements.
37 PROB_FILTER_REASON_C_NAME VARCHAR No
Stores the reason why an external problem should be filtered from the composite record
May contain organization-specific values: No
Category Entries:
Claim Derivation: Procedure Code Inclusion/Exclusion List
Claim Derivation: Missing Provider
Claim Derivation: Sensitive Diagnosis
Claim Derivation: Missing Procedure Start Date
Claim Derivation: Excluded Procedure Modifier
Source Organization Unknown
Source Organization Mismatch
Source Organization Is Self
Clinical Note Type Exclusion List
Clinical Note Missing Service Instant
Clinical Note Missing Last Filed Instant
Clinical Note Missing Author Name
Dispense Cancellation
Same Day as Internal Encounter
Missing or Invalid Binary URL
Filtered or Missing Source Note
DocumentReference Status not Current
Claim Derivation: Excluded Linked Diagnoses
Claim Derivation: Missing Encounter Start Date
Entered In Error
FHIR resource contained an invalid category
Condition verification status is no longer confirmed
Condition is no longer valid for this patient due to age or sex
FHIR resource has an invalid start date
Encounter FHIR resource is missing the type element
FHIR resource is missing the status element
Encounter FHIR resource is missing the class element
Encounter FHIR resource contained an unrecognized status code
Encounter FHIR resource contained a status code for a future encounter
Encounter FHIR resource contained a class code for a future encounter
FHIR resource has a future start date
FHIR resource does not have a status of completed
FHIR resource is missing the code element
Diagnosis is missing a link to an encounter
FHIR resource contains a reference to encounter not in the system
FHIR resource contained a patient reference not matching the searched for patient
Immunization FHIR Resource is missing the vaccineCode element or did not contain a CVX code
FHIR Resource is missing an effective date/time
FHIR resource contained an invalid status
Observation FHIR resource is linked to a filtered Condition FHIR resource
SDOH Assessment contains no questions
Missing required data for data type
Claim Derivation: Missing face-to-face services
38 PROB_DX_MIN_DATE DATETIME No
This column represents the earliest possible date that a problem could have been diagnosed on. The latest possible date is in PROB_DX_MAX_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.
39 PROB_DX_MAX_DATE DATETIME No
This column represents the last possible date that a problem could have been diagnosed on. The earliest possible date is in PROB_DX_MIN_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.