|
Name |
Type |
Discontinued? |
|
1 |
NOTE_ID |
VARCHAR |
No |
|
|
|
The unique ID of the notes record. |
|
|
2 |
PATIENT_ID |
VARCHAR |
No |
|
|
|
The patient associated with the coding query. |
|
|
3 |
CCR_EMP_ID |
VARCHAR |
No |
|
|
|
The user who created the coding query. |
|
|
4 |
CCR_EMP_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
5 |
CCR_NOTE_DT_TIME |
DATETIME (Local) |
No |
|
|
|
The date and time the coding query created. |
|
|
6 |
CCR_NOTE_SUMMARY |
VARCHAR |
No |
|
|
|
The subject line (free text) of the coding query. |
|
|
7 |
CCR_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The status of the coding query. |
May contain organization-specific values: No |
Category Entries: |
Query Pending |
Query Sent |
Response Received |
Completed |
Deleted |
Reassigned |
Deactivated |
|
|
8 |
CCR_HOSP_ACCT_ID |
NUMERIC |
No |
|
|
|
The hospital account associated with the coding query. |
|
|
9 |
QUERY_WORKFLOW_C_NAME |
VARCHAR |
No |
|
|
|
The workflow type category number for the query. NULL or 0 is returned for a coding query. |
May contain organization-specific values: No |
Category Entries: |
Coding Query |
CDI Query |
Coding Documentation Deficiency |
PB Coding Query |
|
|
10 |
PAT_ENC_CSN_ID |
NUMERIC |
No |
|
|
|
The unique contact serial number for the patient contact associated with this coding query. This number is unique across all patient encounters in your system. If you use IntraConnect, this is the Unique Contact Identifier (UCI). |
|
|
11 |
COD_QRY_HNO_TYP_C_NAME |
VARCHAR |
No |
|
|
|
The coding query type category number for the query. |
May contain organization-specific values: Yes |
Category Entries: |
All Other |
|
|
12 |
CDI_QRY_HNO_TYP_C_NAME |
VARCHAR |
No |
|
|
|
The clinical documentation improvement (CDI) query type category number for the query. |
May contain organization-specific values: Yes |
Category Entries: |
All Other |
|
|
13 |
CODING_DOC_DFI_ID |
NUMERIC |
No |
|
|
|
The unique ID of the deficiency which is associated with a documentation query. This column is frequently used to link to the DFI_DETAILS table. |
|
|
14 |
CODING_DOC_CREATE_C_NAME |
VARCHAR |
No |
|
|
|
The creation method category ID for the documentation query. |
May contain organization-specific values: No |
Category Entries: |
Automatic Deficiency Creation |
Manual Deficiency Creation |
Added to Existing Deficiency |
|
|
15 |
CCR_ASSN_TO_POOL_ID |
NUMERIC |
No |
|
|
|
The pool to whom the documentation query was sent. |
|
|
16 |
CCR_ASSN_TO_POOL_ID_REGISTRY_NAME |
VARCHAR |
No |
|
|
|
The name of the In Basket registry in the HIP master file. |
|
|
17 |
CCR_OUTCOME_C_NAME |
VARCHAR |
No |
|
|
|
The query outcome category ID for the query. This indicates the conclusion of the query (recipient agrees, disagrees, or doesn't respond). |
May contain organization-specific values: Yes |
Category Entries: |
Recipient Agreed – Documentation Updated |
Recipient Agreed – Documentation Not Updated |
Recipient Disagreed |
Recipient Did Not Respond |
Auto Completed - Provider Response Received |
Auto Completed - Query Still Outstanding |
|
|
18 |
RESP_USER_ID |
VARCHAR |
No |
|
|
|
To store the provider's ID whose response to a query satisfies the query sender. |
|
|
19 |
RESP_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
20 |
QRY_RESP_NOTE_ID |
VARCHAR |
No |
|
|
|
Holds the note ID of the note used to respond to a coding/CDI query. |
|
|
21 |
QRY_RESP_SMRTTXT_ID |
VARCHAR |
No |
|
|
|
Specifies the smart text to use to populate a new note in response to a query. |
|
|
22 |
QRY_RESP_SMRTTXT_ID_SMARTTEXT_NAME |
VARCHAR |
No |
|
|
|
The name of the SmartText record. |
|
|
23 |
DOC_QRY_REP_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
Indicates the reporting workflow of the query based on the presence of an attached deficiency. Use this instead of workflow value when breaking CDI and Coding queries out by whether they are a documentation query as well. |
May contain organization-specific values: No |
Category Entries: |
Coding Query |
CDI Query |
Coding Documentation Query |
CDI Documentation Query |
|
|
24 |
CCR_UPD_INST_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The instant that the query was updated, in UTC time. |
|
|
25 |
CCR_NOTE_INST_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The date and time the coding query was created, in UTC time. |
|
|
26 |
QRY_SUGG_RESP_NOTE_CSN_ID |
NUMERIC |
No |
|
|
|
The unique contact serial number (CSN) of the suggested response note linked to the query. |
|
|
27 |
QRY_PEND_NOTE_CSN_ID |
NUMERIC |
No |
|
|
|
The unique contact serial number (CSN) of the note pended by the provider responding to a query. |
|
|
28 |
QRY_SUGG_REJECT_REASON_C_NAME |
VARCHAR |
No |
|
|
|
The reason a query suggestion was rejected and not shown to a provider. |
May contain organization-specific values: No |
Category Entries: |
Other |
Not Supported |
Low Impact |
Already Documented |
Not Acted On |
|
|
29 |
QRY_IS_AI_SUGG_YN |
VARCHAR |
No |
|
|
|
Whether this query is suggested by an AI. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
30 |
PB_CODING_QUERY_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
This item stores the actual type of PB coding query, which the user can choose when composing a new PB coding query. |
May contain organization-specific values: Yes |
Category Entries: |
All Other |
|
|
31 |
BASE_CODING_RECORD_CSN_ID |
NUMERIC |
No |
|
|
|
The Coding/CDI review that captures the pre-query state of codes. |
|
|
32 |
IMPACT_CODING_RECORD_CSN_ID |
NUMERIC |
No |
|
|
|
The Coding/CDI review that captures the post-query state of codes. |
|
|
33 |
QRY_AI_SUGG_REASON |
VARCHAR |
No |
|
|
|
The reason the AI query was suggested. |
|
|
34 |
QRY_SUGG_FEEDBACK |
VARCHAR |
No |
|
|
|
User provided feedback for the query suggestion. |
|
|
35 |
QRY_AI_SUGG_SRC_C_NAME |
VARCHAR |
No |
|
|
|
The source of what created the reason for the AI query suggestion. |
May contain organization-specific values: No |
Category Entries: |
AI |
Epic |
|
|