Scheduling (in conjunction with the Event Processor) handles most of the automated actions, reminders, alerts, and escalations in the System. Since Scheduling, Alert, and Escalation functions are generic objects, they can be assigned to any Identity (an individual, an individual’s possessions, a device, a service, or a facility).

 

This is a useful feature for assigning tasks and collecting events for any object in the System (facility maintenance, facility security, general equipment maintenance /calibration, service contracts, leak detection and other sensors, etc.). Different parts of an organization can have their own Identities (and roles) with Scheduling, Alerts, and Escalation to individuals or roles and verification/logging of each event’s lifecycle.

 

Scheduling supports standard scheduling, plus role based assignments (to handle shifts and time off), audit/metrics (or accountability and process improvement), and delta scheduling (for predefined tasks taking place after an event).

 

The scheduling function has a defined Object Interface that is available to other functions and Apps. For example, the scheduler can be automatically updated when a monitoring device is configured, a service is scheduled,  monitoring activities are defined, an on-line appointment is made, a device is activated or used, and just regular scheduled events.

 

 Scheduled events are acknowledged with estimated time of completion, to help support escalations and alerts. Scheduled events are closed, and follow-ups and transfers can all be created of a scheduled event. Scheduled events can have instructions and embedded tasks (e.g. verification of a treatment) to help in the performance of the task, and reduce mistakes.

 

Role (and Shift) Based Scheduling

 

Role Based Scheduling is an important concept in the System. It supports individuals, as well as specific roles that a person or group would have during a specific period of time. This allows for the assigning of tasks and escalations to “pseudo individuals” that can change based on the person’s role and shift at the time the service is required.

 

Role based scheduling and escalations are an important set of rules governing organizations, as well as the Military and Disaster Preparedness. The System supports simple tools to assign roles, escalations, and shifts, which are used to perform the lookups for assigning/reassigning tasks, and sending alerts and escalations.  Examples of roles could be 3^rd_floor_nurse, nurse_supervisor, maintenance, security, guardian, <an individual’s name>, etc.

 

They are all just objects with certain attributes. Roles can be defined to finer detail, allowing location based task assignments to aid in efficiency and workflow. Schedules and To-Dos can have floating priorities based on original priority, location, expected time to service, and lateness of task.

 

For independent individuals, pseudo roles are not necessary and if a scheduled event required escalation, then there would only be need or two people notified. For small clinics, retirement homes/communities, assisted living centers, community organizations, etc. some pseudo roles would be helpful. For hospitals, large clinics, and Disaster/Relief operations, roles can be of great importance.

Scheduling can also be defined off of predefined events, that can be pre-populated and kickoff an entire series of tasks based on the execution of the event. For example, In the area of Disaster Preparedness, all of the tasks and escalations that would be generally required, could be preset and stored, to be triggered on a Training or actual Disaster/Outage. This is also valuable for training and demos. Series of tasks can also be canceled.

 

The following is a list of some unique uses of the Scheduling/Event Features

• Simple scheduling, reminders, alerts and escalations of events (take a test, review data, give medicine, missed medicine or treatment, check patient (call or onsite, etc.)

• Monitoring the safety of an individual living alone with just their smartphone (not using their smart phone in 24 hours)

• Monitoring the safety of an individual living alone using motion or cameras (no movement by 10:00Am, not leaving the bathroom for 45 min, not taking medicine or eating, etc.)

• Other individual monitoring (not taking blood pressure as desired, checking weight, etc.)

• Follow-ups (concern by a personal service provider or call center, results of a test, no response to a call, etc.)

• Since a Facility, Area, Department, Group, or piece of equipment can also be assigned Identities… scheduling, reminders, alerts and escalations of events can also be managed <automated requests  and report issues in real-time>

  • Scheduled (e.g. maintenance, equipment calibration /service, audit, etc.)

  • Unscheduled (e.g. maintenance, repair, security, water leak or other monitoring device, etc.)

  • Linkage and support for the in-house dispatch system

 

Predefined Delta Tasks (executable Schedule Task Lists)

 

Role Based Scheduling is not dependent on specific individuals, which allows “executable Schedule Task Lists” to be created in advance and then loaded in the future into a System Schedule. These can be defined with a delta offset from the current time, or delta plus a next available shift. This is a powerful tool to support Demos, Training, and Critical Operations.

• The feature  can be used to set up a predefined Scenario, to help guide, track, measure and audit  training or an actual event (e.g. response to a disaster or outage, where you are basically preloading all required tasks in the Operations Manual in advance)

• The feature can be used to create social activities/games where scheduled events can be preloaded and people assigned to the different roles.

• In conjunction with Data Recording and Playback (raw data and events), there are many different practical and situational Training and Demos available

 

Workflow

 

Workflow follows out of the tools and features of the Scheduling Services, but it does require the proper setup of the Roles, Shifts, and Escalation Rules. These are not difficult to do, and the system would come with some default setups (based on use-case) for the administrator to modify.  Here are some of the ways that Scheduling Services helps with workflow.

• Get the task to the right person/group

• Allow people to accept and/or forward tasks to others

• Can use # of currently assigned tasks or current location for different priority tasks

• It is “shift aware” to assign or reassign higher priority tasks to another shift (still supports direct assignments to individuals or individual groups that are not forwarded… unless there is automatic forwarding or an OoO)

• Allow people to create follow-up actions or escalations (on the spot)

• Automatic escalation if tasks are not accepted or completed within a provided time parameter

 

Process Improvement

 

Process improvement and reducing errors is an integral part of the System. As you can see from the Workflow Section (above), the System already makes sure that the right people are assigned, tasks can be manually or automatically be re-assigned, and escalations and follow-ups are performed as needed. This is an improvement in itself.

 

Each action creates an event log entry that can then be used for audit, accountability, metrics, and process/workflow improvement.  The Scheduler has a RFID/QR code reader, which aids in the logging of information (e.g. room, patient, device, treatment, billing code, etc.) that also verifies the action and helps prevent mistakes. Comments can be added to each entry from pick-lists or entered by the individual or device.

 

Each action in the System creates an event.  Events contain information such as Event ID, Master ID, System, Priority, Action, Source, Object, Individual assigned, Role, Date, Time, Txt, Application Link, Follow-up, and Comment. Using Event Log searches, there is a wide variety of information and metrics that can be obtained on a general, group, shift, and individual basis. These metrics can help an organization change their processes and procedures, change staffing, and/or modify their System Roles and Escalations Rules. It is envisioned that the System includes canned and ad hoc tools to analyze the events and provide the necessary metrics.

 

Some examples:

• Find out how many (and/or what kind of assignments) are assigned (and/or completed, accepted, forwarded, escalated) by Group (and/or shift, individual)

• Lean 6 Sigma spaghetti diagrams to trace the working paths of individuals or groups within a typical shift

• Evaluation of an individual going through training

• Evaluation of Process Improvement Goals for an individual or Group (verify a change is better, or individual initiatives tied to bonuses)

• Evaluation the success and deficiencies in a group emergency training (e.g. training exercise for a disaster or outage)

• Identify peak and slow times for Group (and/or shift, individual)

• Identify downtime of certain types or specific pieces of equipment or facility

• Average time to respond to an event

• Time to complete an task

• Number of escalations per shift

 

Escalations

 

Escalations are an important part of the System. They can provide an urgency, follow-up, and verification for issues that need it, as well as make sure that things do not fall through the cracks. Escalations are used throughout the System for Devices, Services, and Applications.

 

Escalations are any events that need an additional notification to a person, group, or even machine-to-machine. They can be setup and assigned in the “Schedule Role” rules and/or be part of the event that triggers the escalation.

• An Action not being taken (not acknowledging a task, not completing a task)

• An Event Happening (a receipt of an event log entry <new data, a device trigger>)

• An Analysis Trigger (correlation of data that requires a response)

• A Scheduled Priority Event

 

Automation

 

The System is designed to provide as much automation as possible. The use of Roll based Schedules and Escalations provides a significant part of that automation. A lot of this has already been described above, but there are other cases.

For example, let’s look at a person living in a residence that needs a little extra help (age, partial dementia, Alzheimer’s, disability, etc.). The system is designed to provide verbal, auditable sounds, and visual reminders and instructions to an individual (and escalate to the individual or someone else as defined for the individual). There interactions would be interactive with any required follow-ons and escalations as needed

• Simple schedule and motion based events like the person has not gotten up in 2 hours (or not gotten out of bed by 9:00AM, been in the bathroom for over 30 min, treatment, etc.)… Are you OK… would you like me to check again later or contact someone?

• Your favorite show is about to come on, would you like it turned on or recorded for later (the System can also look for shows they could be interested in and remind them they have recordings available)

• You visitor XXX should be here in 30 minutes

• You did not receive your call from XXX, would you like me to send them a message?

• Sensor checks, like your house is below XX degrees, would you like the heat turned on?