This is the basic client data "tree" (although the default view is a
series of tabs, as shown in this screen shot).
The upper-level tabs are for Per-Client information, Per-Client Healthcare information and Per-Client-Program information (a client admitted to multiple programs will have a program table for each program). In this example the client has been admitted into the "Residential Treatment Center" program.
The second-level tabs may be customized for each provider. These second-level tabs contain all the data screens used to add, edit, view and delete information.
In this example, the "Documents" multi-entry data screen has been placed under the main tab "Client Information" and under the sub-heading "Client Information".
This is the first screen worth of the Incident form.
Incidents reported in this form are tied to the other clients entered into the "Student(s) Involved" multi-list as well as the "Student Witness(es)" multi-list (not shown). Once entered under one client, the other clients involved will have similar incident entries (less the client-specific information).
Incidents may also be associated with Medication PRNs as well as Medical Services (both shown later).
This is the user-managed, completely customizable client assessment scales testing (CAST) module.
Each answer option to a question or evaluative statement is worth a certain number of points, at the completion of each test section a total score and an average are calculated (items answered "Not Applicable" are not taken into account for the average score).
In this example questions are worth 1 to 5 points each.
Here is the Prospective Treatment Plan screen, used to define plan, problems associated with each plan and step-wise treatments for each problem.
Used as an efficient way to track client progress through a PTP as opposed to long progress notes alone.
The Medical Service / Consult screen is used to track specific services performed on a client by a medical / clinical operation.
Associated with each service entry is a diagnosis and each service may be associated with an incident.
This example has been associated with incident 182.
The Medications screen can track both on-going prescriptions as well as PRNs (new and standing orders).
Like the Medical Services, Medications may be associated with incidents.
If Medications require the scheduling Medical Procedures, the system will check for these rules and create medical procedure appointments for the client automatically upon saving a Medication entry.
The Appointment Calendar is one of multiple modules lying outside of the client data tree (though it may be called from within the client data tree).
Here is a screenshot taken while creating a recurring appointment (akin to MS Outlook's "recurring series" feature). Recurring rules may be created in four ways: By Weekday, Daily, By Day Count, By Anniversary. Additionally these rules may be marked to allow (or not allow) weekend days (this check box is not show).
Built-in to the Appointment Calendar is a conflict warning and avoidance process. This is especially useful when entering long-term recurring appointments.
Here is the appointment calendar, having been filled in for November 2006 with the recurring appointment shown in the previous screenshot.
The "<R>" indicates the appointments as part of a recurring series, the start time is indicated and the "CFCo" is the system encoding of the appointment type (managed by the provider, not by TESCO). The smudge would be the client's name (or "group" in the case of multiple clients, the names of whom would be listed in mouse-over pop-up text).
The upper-level tabs are for Per-Client information, Per-Client Healthcare information and Per-Client-Program information (a client admitted to multiple programs will have a program table for each program). In this example the client has been admitted into the "Residential Treatment Center" program.
The second-level tabs may be customized for each provider. These second-level tabs contain all the data screens used to add, edit, view and delete information.
In this example, the "Documents" multi-entry data screen has been placed under the main tab "Client Information" and under the sub-heading "Client Information".
This is the first screen worth of the Incident form.
Incidents reported in this form are tied to the other clients entered into the "Student(s) Involved" multi-list as well as the "Student Witness(es)" multi-list (not shown). Once entered under one client, the other clients involved will have similar incident entries (less the client-specific information).
Incidents may also be associated with Medication PRNs as well as Medical Services (both shown later).
This is the user-managed, completely customizable client assessment scales testing (CAST) module.
Each answer option to a question or evaluative statement is worth a certain number of points, at the completion of each test section a total score and an average are calculated (items answered "Not Applicable" are not taken into account for the average score).
In this example questions are worth 1 to 5 points each.
Here is the Prospective Treatment Plan screen, used to define plan, problems associated with each plan and step-wise treatments for each problem.
Used as an efficient way to track client progress through a PTP as opposed to long progress notes alone.
The Medical Service / Consult screen is used to track specific services performed on a client by a medical / clinical operation.
Associated with each service entry is a diagnosis and each service may be associated with an incident.
This example has been associated with incident 182.
The Medications screen can track both on-going prescriptions as well as PRNs (new and standing orders).
Like the Medical Services, Medications may be associated with incidents.
If Medications require the scheduling Medical Procedures, the system will check for these rules and create medical procedure appointments for the client automatically upon saving a Medication entry.
The Appointment Calendar is one of multiple modules lying outside of the client data tree (though it may be called from within the client data tree).
Here is a screenshot taken while creating a recurring appointment (akin to MS Outlook's "recurring series" feature). Recurring rules may be created in four ways: By Weekday, Daily, By Day Count, By Anniversary. Additionally these rules may be marked to allow (or not allow) weekend days (this check box is not show).
Built-in to the Appointment Calendar is a conflict warning and avoidance process. This is especially useful when entering long-term recurring appointments.
Here is the appointment calendar, having been filled in for November 2006 with the recurring appointment shown in the previous screenshot.
The "<R>" indicates the appointments as part of a recurring series, the start time is indicated and the "CFCo" is the system encoding of the appointment type (managed by the provider, not by TESCO). The smudge would be the client's name (or "group" in the case of multiple clients, the names of whom would be listed in mouse-over pop-up text).
