Clinicians spend significant non-productive time in handling disparate healthcare applications individually. As the amount of mobile healthcare apps increase, so will this non-productive time.
We offer a solution that saves time for the clinicians by synchronizing context and supporting workflows between their applications. As an added benefit this also reduces the risk of adverse incidents.
A typical example is a clinician having a workflow involving three applications: an Electronic Health Record (EHR), a PACS and a LIMS (Laboratory Information Management System). The context manager ensures that when the clinician change to a new patient in one of the applications e.g. the EHR then the PACS and the LIMS application are also made to switch to this new patient. This accomplishes two primary goals:
1. Patient safety is increased since the clinician cannot mistakenly work with different patients in the different application, and
2. Time is saved since the manual step of switching between and synchronizing applications is automated.
This is an example of a use case for the Context Manager and the powerful abstraction it provides. There are numerous other use cases, that the Sirenia Context Manager readily supports.
An action within a shared context is an addition to synchronization of context. An action triggers a specific function in one application from another application. This can for example be a navigational action, where a user in the EHR executes a function to go to a specific page in another application e.g. the PACS and set the current patient in focus. This is typically followed by a focus-shift action where the targeted application – the PACS - is put in focus for the user.
In other words a contextual action will glue applications together on a functional level while context synchronization glue applications together on a semantic / data level.