|
Name |
Type |
Discontinued? |
|
1 |
MESSAGE_ID |
VARCHAR |
No |
|
|
|
The unique ID used to identify a web based chart system message record. |
|
|
2 |
LINE |
INTEGER |
No |
|
|
|
The line number used to identify each row of read data associated with an individual web based chart system message record. |
|
|
3 |
TASK_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
A category value corresponding to the type of the current message task. Example types are Appointment and Questionnaire. Link to the ZC_MYC_TASK_TYPE table to get the task names. |
May contain organization-specific values: No |
Category Entries: |
Appointment |
Questionnaire |
Hx Questionnaire |
E-Visit Payment Request |
|
|
4 |
TASK_TYPE_ORD_NUM |
INTEGER |
No |
|
|
|
This is the message task type ordinal number. It is used in conjunction with TASK_TYPE_C and indicates if a given message task is the first, second, third etc., of a given message type to be attached to the message. For example, if there were three Appointment tasks and two Questionnaire tasks attached to a given web based chart system message, the first Appointment would have a TASK_TYPE_ORD_NUM of 1, the second Appointment would have a TASK_TYPE_ORD_NUM of 2, and the third Appointment would have a TASK_TYPE_ORD_NUM of 3. Similarly, the first Questionnaire task would have a TASK_TYPE_ORD_NUM of 1 and the second Questionnaire task would have a TASK_TYPE_ORD_NUM of 2. |
|
|
5 |
TASK_DISPLAY_NAME |
VARCHAR |
No |
|
|
|
This is the display name of the task (what the patient will see in web based chart system). |
|
|
6 |
TASK_COMP_DATE |
DATETIME (Attached) |
No |
|
|
|
This stores the instant the message task was completed. If the task has not been completed, this item is blank. |
|
|
7 |
TASK_COMP_WPR_ID |
VARCHAR |
No |
|
|
|
The ID of the person who completed the task. |
|
|
8 |
TASK_SCHED_APPT_REQUEST_ID |
NUMERIC |
No |
|
|
|
The appointment request order IDs linked to this message as a scheduling task for the patient |
|
|