Tasks
Flow Defined
When viewing a patient record, some of the links point to the Task listing - a list of forms and/or records that have already been submitted for a patient. These tasks are grouped according to the phase of pregnancy or logical groups.In Zcore, each grouping is called a "flow."
Sample Perinatal Flows in ZEPRS:
- History/Dating
- Problem or Labour Visit
- Postnatal/Delivery Summary
- Ultrasound
Sample Legal Care Flows (TIMS):
- Intake
- Docket
Task Listing Logic
The Task list uses logic entered in the Administrative interface to list only the forms necessary for this particular type of patient. The form property MaxSubmissions affects how forms are listed in the Task list. For example in the ZEPRs application, the Newborn Evaluation form is set for the Delivery Summary flow, is a "Newborn only" form, and has MaxSubmissions set to 1.
Detail from Admin:Form list:
This means that when you view the Delivery Summary task list, you will see a link to the Newborn Evaluation if that form has already been submitted; however, a link to the form will not be displayed, since that form will have already reached its MaXSubmissions of 1.
When viewing the Mother's record, you will not see a link to the Newborn Eval. form because the form is set as Newborn only. (You will see a link to the Newborn eval record, but this is a due to extra code to enable this convenience.)
ZEPRS-specific code
The following code adds the Newborn/s to the mother's Delivery Summary task list:
Task newbornEvalTask = TaskListDAO.getNewbornTask(conn, newborn.getId());
(See code in TaskList class for full logic.)
The classes or files associated with the task listing are patient_records/patient_tasks.jsp and the PatientTaskAction and TaskList classes.
- Printer-friendly version
- Login to post comments
- PDF version