|
Name |
Type |
Discontinued? |
|
| 1 |
TASK_ID |
VARCHAR |
No |
|
|
|
| The unique identifier for the task record. |
|
|
| 2 |
DESC_FOR_PAT_OVRIDE |
VARCHAR |
No |
|
|
|
| A descriptive name for instances of this task that is written specifically for a given patient. |
|
|
| 3 |
NAME_FOR_PAT_OVRIDE |
VARCHAR |
No |
|
|
|
| A descriptive name for instances of this task at LTK level that is written specifically for patients. |
|
|
| 4 |
START_OFFSET_DAYS |
INTEGER |
No |
|
|
|
| Number of days to offset the start date from the task assignment or the anchor event date. |
|
|
| 5 |
START_OFFSET_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
| The type of start date offset (e.g., before/after). |
| May contain organization-specific values: No |
| Category Entries: |
| Before |
| After |
|
|
| 6 |
SOURCE_LTT_UTC_DTTM |
DATETIME (Local) |
No |
|
|
|
| Stores the instant the task template (LTT) was assigned which resulted in tasks (LTK) being created. |
|
|
| 7 |
CALCULATED_RESUME_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
| When resuming a paused task, this will be its start instant if no start date is specified. |
|
|
| 8 |
FLO_THRESHOLD_VALUE |
NUMERIC |
No |
|
|
|
| Threshold value for flowsheet based task completion. |
|
|
| 9 |
TSK_DISCONTINUE_REASON_C_NAME |
VARCHAR |
No |
|
|
|
| Describe the reason of the discontinued patient-assigned task. |
| May contain organization-specific values: No |
| Category Entries: |
| Discontinued by Provider |
| Finished |
| Discontinued through OPA |
| Resolved by Provider |
| Discontinued by Patient |
| Discontinued by Chart Correction |
| Patient Deceased |
| Discontinued by Medication Reminder Pause Anchor Event Action |
| Discontinued by Unanchor Behavior |
| Discontinued by Past Start Date Behavior |
|
|
| 10 |
ENSURE_DELIVERY_C_NAME |
VARCHAR |
No |
|
|
|
| Determines the scheduling behavior of this anchored task when its start date falls in the past. |
| May contain organization-specific values: No |
| Category Entries: |
| Start immediately |
| Skip in-between occurrences |
| Don't start |
| Resolve task as discontinued |
|
|
| 11 |
EFQ_OVRIDE_CYL_LEN |
INTEGER |
No |
|
|
|
| If there is a frequency override specified, this item will contain the length of a relative specified type cycle. For all other specified types this value will be ignored (and should be empty). |
|
|
| 12 |
EFQ_OVRIDE_DAY_TYP |
INTEGER |
No |
|
|
|
| Specifies what the numeric values in the frequency override days columns represent. If it is 1 then the listed days are relative days. If it is 2 then the listed days are weekdays. Any other value has no meaning. |
|
|
| 13 |
DURATION |
INTEGER |
No |
|
|
|
| Determines the number of days this recurring task should go on for relative to its start date. |
|
|
| 14 |
TASK_NOTE_ID |
VARCHAR |
No |
|
|
|
| The note (HNO) ID that is attached to the task (LTK) record. |
|
|
| 15 |
DECISION_TRACKER_ID |
NUMERIC |
No |
|
|
|
| Stores the linked decision, if one exists, for this task |
|
|
| 16 |
REQ_DOC_NOT_ATTRIBUTED_RSN_C_NAME |
VARCHAR |
No |
|
|
|
| The did not attribute reason category ID for the required documentation task. This indicates the reason that the task was not attributed to any users. |
| May contain organization-specific values: No |
| Category Entries: |
| Could Not Find Any Appropriate Users |
| Already Completed Before Evaluation |
|
|
| 17 |
USED_FOR_OUTREACH_YN |
VARCHAR |
No |
|
|
|
| Indicates whether a checklist task is used for outreach or not. 'Y' indicates that the checklist task is used for outreach. 'N' or NULL indicates that the checklist task is not used for outreach. |
| May contain organization-specific values: No |
| Category Entries: |
| No |
| Yes |
|
|
| 18 |
PAT_ASGN_TASK_PAT_ENC_CSN_ID |
NUMERIC |
No |
|
|
|
| If this task is anchored to an anchor target of type Hospital Discharge, then this item stores the contact serial number associated with the admission. |
|
|
| 19 |
SC_SUPPORT_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
| The category value of the support & service type that triggered the generation of this task |
| May contain organization-specific values: Yes |
|
|
| 20 |
SC_SUPPORT_TYPE_START_DATE |
DATETIME |
No |
|
|
|
| The start date of the support & service type that triggered the generation of this task |
|
|
| 21 |
REFERRAL_ID |
NUMERIC |
No |
|
|
|
| The referral that this target is tracking. |
|
|
| 22 |
USED_FOR_C_NAME |
VARCHAR |
No |
|
|
|
| The category number which identifies the purpose for which the task is used. |
| May contain organization-specific values: No |
| Category Entries: |
| Target |
| Outpatient Care Plan |
| Outreach |
| Case Review |
| Checklist |
| Medication Therapy Problem |
|
|
| 23 |
CREATE_INST_LOCAL_DTTM |
DATETIME (Local) |
No |
|
|
|
| The instant at which the task was created, in local time. This item is the local equivalent of the CREATION_UTC_DTTM column, which is in UTC. |
|
|
| 24 |
LINKED_PAT_ID |
VARCHAR |
No |
|
|
|
| This column contains the patient linked directly or indirectly to the task record. This differs from column PAT_ID in table IP_WORKLIST in that this column also contains patients linked indirectly to a task, through a patient CSN (I LTK 215) or an episode (HSB) (I LTK 53100 or I LTK 81110). To find only patients linked directly to a task, use column PAT_ID in table IP_WORKLIST. |
|
|
| 25 |
CREATE_USER_ID |
VARCHAR |
No |
|
|
|
| User that created the task. |
|
|
| 26 |
CREATE_USER_ID_NAME |
VARCHAR |
No |
|
|
|
| The name of the user record. This name may be hidden. |
|
|
| 27 |
OUTREACH_OUTCOME_C_NAME |
VARCHAR |
No |
|
|
|
| Outcome of an outreach task |
| May contain organization-specific values: Yes |
| Category Entries: |
| Completed Successfully |
| Unable to Reach |
| Skipped |
|
|
