TASKS

Understanding Tasks

My experience in building

• 12 years building iView • 15 years building tasks • 15 years building the Firstnet application • 15 years building powerforms

Introduction:

Your experience

Objective:

 History of the task  What is a task?  How is a task created?  How are tasks documented  MPTL and SPTL  CareCompass  Docset  Importance of completing tasks  Designing of the task  Building of a task

Care Transformation developed the original orders and tasks and continues today with the Nursing Informatics.

There were original 295 tasks for PatCare, RT & RT/RN shared, and tasks were needed to be associated to them. Today there are numerous tasks for every position, which does not include medications.

Done/not done tasks were developed for brief documentation that was not associated with a form

History:

Chart details was the task associated to a form. The first task was the Admission Health Profile.

Docset charting did not come about until iView was implemented

What is a Task?

 A task is a listing of activities to be completed for the care of a patient---- a “to do” list of things needing to be done

How is a Task Created?

Rules can generate tasks without an order

Task gets its functionality from the order or rule

Orders generate tasks

An example:

Tasks Documentation

Tasks can be satisfied by charting on a form/Docset from the task on the CareCompass, or task list (SPTL MPTL) or ED Launchpoint

Tasks can be charted as either “done” or “not done”

An order is placed for insert peripheral IV

The order places the insert peripheral IV task in CareCompass or on the single patient task list.

Example of relationship between an order, a task and a Docset

The nurse clicks on the task,which is associated to the peripheral IV Docset

The nurse completes the charting on the Docset, and the order and task is completed.

The Multi-Patient Task List (MPTL) is accessible from the Organizer

MPTL has functionality related to orders which are department and position specific The Single-Patient Task List (SPTL) is accessible from a selected patient’s chart.

MPTL and SPTL

On the SPTL, the tasks are related to the patient

CareCompass

 CareCompass

 Organize

 Prioritize

 Plan patient care

Importance of completing tasks:

 If the tasks are not completed (i.e. charted) in a timely manner, they go into an “overdue” status on the task list.  Tasks are controlled by retention time, which is the amount of time that an uncharted active task will remain on the task list.  Once a task has met its defined retention time, the status updates to “ dropped ” which means:  The task is no longer viewable and cannot be charted  A task “dropping” will not then update the order status and will leave an uncompleted order on the profile that must be cancelled  “Dropped” tasks will slow the speed of the system

 What is the name of the order that the task is connected to? (the task is usually the name of the order)  Overdue time  Retention time  Can the task be rescheduled  Who is charting the task  What is the task being connected to (form, done/not done, or Docset)

Design a task: what I need

Questions

This Photo by Unknown Author is licensed under CC BY

Demonstration on how to build a task

Copyright ©1997-2002 Cerner Corporation, Kansas City, Missouri.

Reference