<< Click to Display Table of Contents >> Emergency Room |
The following example is a simplified version of an Emergency room, where a patient arrives with a particular condition and the people involved in the case will work to make the patient feel better. This Emergency room does not consider admitting someone in the hospital. This would be handled sending the patient in an ambulance to another clinic.
Scope: the process starts when a patient arrives to the ER, and ends when a treatment is in place to heal the patient.
The Emergency room process depicts an example of the use of Bizagi 11 features and options to take advantage of the Experience Design concept, to best address unstructured processes.
Unstructured processes are those which you may catalog as highly unpredictable or dynamic, mainly because these processes may involve at some point a very large number of possible alternatives in the workflow.
It represents how the Stakeholders (knowledge workers) are able to make decisions to define the flow of a case, that cannot be predicted beforehand.
The scope of the Emergency room case is the attendance of a patient.
Through Experience Design you will be able to make the most of: Empowering knowledge workers, presenting a personalized user experience, and using contextualized BPM capabilities, among others.
Note: this is not a complete emergency room process; it would require more extensive definitions.
The complete documentation of this process can be found within its Bizagi Modeler file (.bpm). From there, you can generate a Word document with all its information.
Identify the general process and milestones
Identify the general process, or happy path, providing a high level business description of what will be automated. Identify the most common outcomes (in this first stage do not include exceptions) and the stages of the case, or milestones.
The milestones of the Bizagi ER are:
-Triage and registration
-Examination
-Tests
-Treatment
-Transfer patient to clinic for surgery
-
Not all milestones will have to be reached in a case instance. In fact, several are mutually exclusive. Some may be revocable: even when the milestone has been reached, the case stakeholders can decide that on second thoughts it is not reached after all.
Stakeholders
Bizagi 11 presents a Work portal which allows knowledge workers to make informed decisions, such as when to start a process or update data, boosting agility and productivity.
Various stakeholders can be associated with the case. However, each stakeholder may directly or indirectly influence the case. Not all stakeholders listed have to be involved with every instance of the case.
Identifying Stakeholders is important to be able to personalize their experience.
-Doctor
-Nurse
External Stakeholders (usually are evaluated to be or not to be included as part of the automation)
-Patient
Experience design
In Bizagi Studio each Stakeholder has their experience designed in the Experience Designer menu. Each tab (Actions, My Stuff, Search) has a definition according to each user’s available options.
Keep in mind that to enable a group to be available in My Stuff section, the Stakeholder must have a Direct or indirect collection to an entity.
Thus, the Nurse for instance, has a collection to Medical Equipment. That way, each Nurse will own one or more equipment, and will be able to view them in the Work portal, and manage them if there are actions available to manage them.
Manage Stakeholders
As you download this template, make sure you have created at least one user per Stakeholder and have configured them in the Admin option of the Work Portal. If you don't have one user per Stakeholder, this template will not work.
Go to the Admin option and for each Stakeholder create a new record, by creating a new user and filling in all additional required information.
Keep in mind that to manage Stakeholders in the Work Portal we have already defined the management forms for them. These forms will display what information to be shown and requested when configuring a user as a Stakeholder.
In Studio we defined a Display form that depicts the columns of the Stakeholder’s main view.
And an Add and Edit form, that relate how a Stakeholder record is added and edited.
Identify Activities, what Stakeholders can do
This involves the activities the stakeholders can initiate and other case related operations they can perform, categorizing their allowed interactions with the Work that will be enabled for them.
Defining if Activities are mandatory under certain circumstances or are available but executed at the Stakeholder’s discretion will help categorize an activity as an Action available as part of an unstructured process.
Many activities in a case are not always available for execution. Only when certain milestones are reached in the case or specific conditions are met, will the activity be applicable. Activities can be withdrawn: when they are no longer relevant, they should not be presented to stakeholders.
Stakeholder |
Activity description |
When can this action/activity be performed |
Comments |
---|---|---|---|
Nurse |
Patient registration and Triage |
When in shift, as a patient arrives |
The nurse searches for a patient and then includes a date and time of arrival |
Choose Triage category |
When performing a triage |
||
Send a Patient to surgery |
When performing a triage |
||
Update Patient’s information |
Anytime |
||
Monitor health |
In night shifts |
Monitor blood pressure and other |
|
View / manage medical equipment |
Anytime |
||
Doctor
|
Examine patients: Very urgent, urgent and standard |
When patients are in the waiting room and doctor is someone who attends patients |
|
Request laboratory or radiology exams |
When examining patients |
Exams should be updated automatically if one or more are included in the supported exams list |
|
Review exams |
When patients have been sent for exams |
Only available when all exams have been performed |
|
Take blood sample |
|||
Perform radiology procedure |
|||
Send to surgery |
When examining patients and when reviewing exams |
||
View medical equipment |
Anytime |
||
Send equipment to repair |
Anytime |
Several pieces of equipment can be sent at once |
|
Patient |
View Exams, Triage and Doctors |
Anytime |
|
Search Doctors |
Anytime |
Identify Actions, Activities, Contexts and Data
Nurse
Activity description |
Context |
Availability |
Action / Activity |
---|---|---|---|
Patient registration and Triage |
When in shift, as a patient arrives |
Via Search for patients, always available |
Action: Start Triage to launch Emergency process |
Choose Triage category |
When performing the triage |
Mandatory |
Activity: Triage |
Send a Patient to surgery |
When performing a triage |
Mandatory |
Activity: Triage |
Update Patient’s information |
Always without the need of being in a particular case |
At discretion |
Action: Update info |
Monitor health |
In night shifts |
At discretion |
Collection in My Stuff Action: Add monitoring / Add collection item: |
View allocated equipment |
Always without the need of being in a particular case |
Through the data records in My Stuff |
Collection in My stuff |
Data description |
Context |
Availability |
Action / Activity |
---|---|---|---|
Patients |
Always |
Via Search for patients, |
Action: Start Triage to launch Emergency process |
Medical equipment |
Always |
Always available |
|
Health monitoring |
In night shifts |
Mandatory |
Activity: Add monitoring |
Doctor
Activity description |
Context |
Action / Activity |
Activity description |
---|---|---|---|
Examine patients reviewing triage level: Very urgent, urgent and standard |
When patients are in the waiting room and doctor is someone who attends patients |
Mandatory |
Activity: Examine patient |
Request laboratory or radiology exams |
When examining patients |
At discretion |
Action within Examine patient |
Review exams |
When requested exams have been finished |
Mandatory |
Activity: Review exams |
Take blood sample |
When allocated |
Mandatory |
Activity: Take blood sample within Blood test process |
Perform radiology procedure |
When allocated |
Mandatory |
Activity: Perform radiology within Radiology process |
Send to surgery |
When examining patients and when reviewing exams |
At discretion |
Activity within Examine patient Activity within Review exams |
Repair equipment |
Anytime |
At discretion |
Batch action in My Stuff |
Data description |
Context |
Availability |
Action / Activity |
---|---|---|---|
Patients |
Always |
Via Search for patients, |
Action: Start Triage to launch Emergency process |
Medical equipment |
Always |
Always available |
Action: Start a repair process including one or more equipments |
Patient
Data description |
Context |
Availability |
Action / Activity |
---|---|---|---|
Doctors, Exams, Triage |
Always |
Via My Stuff, only to view |
None |
After reviewing the actions available, we can create the structure of a core process and processes that will be launched via Actions to support the case structure.
The process starts with a patient arriving at the ER. A nurse examines the Patient and determines the scale of the emergency. The patient continues to a medical examination by a doctor, or is sent to surgery.
The doctor can request the exams needed to identify the illness.
The requested exam’s processes are launched, as part of the ER case. As all exams are finished, the Review Exams activity is enabled.
The patient can be dismissed after the exams review or sent to surgery.
Main process: Triage
Exams processes (supporting processes for unstructured management):
Data Model
The process entity of the Triage process is “Triage” which has all the attributes and relationships necessary to save main case information.
There are three Stakeholders created, that have their Experience designed to give a unique Work portal for each one:
Doctor
Patient
Nurse.
Heritage configuration
Several process entities are supporting the case, that make part of the Medical exams available. Medical exams are built using a Hierarchical model, that allow us to use the polymorphic launcher in the Examine Patient activity.
Constructors
TO be able to display the Polymorphic launcher in the Work portal, each of the supporting exams processes need a Constructor defined. That is, a definition of how a record of each entity is built. For this template we used a processes for all of them. Thus, a constructor is defined for:
Bilirubin, Blood chemistry, Tomography, Ultrasound and X-ray.
In Bizagi Studio the Constructor wizard was used, and a process was defined for each one.
Templates
When browsing over data, either regarding results of data searches or lists of information which are part of My stuff, you may customize the information displayed for these resulting records.
By default, Bizagi uses a basic template that chooses random attributes of the entity to which a record belongs to.
We have defined data templates for the most relevant entities: Patient, Doctor, each of the Exams entities and Triage.
Triggers and Conditional activity
Conditional activities are used in processes to enable of disable activities according to a data condition in the process. In this template, we use the Review Exams Conditional activity:
When all exams are finished, the Review exams activity should be enabled, but not before.
The condition to enable or disable the conditional activity is set in the fourth step of the process wizard, Define Expressions, as show below.
To set the Triage.Examsready attribute to true or false and thus enable or disable the activity, we use a Trigger.
First, we use an expression at the end of all Exams processes, stating they are finished. When each of them is finished, the Trigger is launched and analyzed:
If the exam is indeed finished, the Trigger performs an expression Event to review if all related Exams of the Triage case have been finished.
If at least one of them is not finished, the Triage.Examsready attribute will remain in false.
However, as soon as they are all finished, the Triage.Examsready attribute will be true and the Review exams conditional activity is enabled and allocated to the doctor.
Last Updated 9/28/2022 11:21:32 AM