Every admission in plain sight, from request to bed.
An example of a patient admission run in Bridge: administrative and medical steps in their own hands, deadlines in view, and a record of who did what.
| Case | For | Current step | Status |
|---|---|---|---|
| ADM-0519 | Patient 0519 | Medical review | Running |
| ADM-0518 | Patient 0518 | Assign a bed | Due soon |
| ADM-0516 | Patient 0516 | Check identity and coverage | Running |
| ADM-0512 | Patient 0512 | Specialist opinion | Incident |
| ADM-0507 | Patient 0507 | Patient admitted | Completed |
Sample data
The example: a patient admission.
An example drawn in BPMN and run on Camunda 8. Your own process will differ; what Bridge brings to each step stays the same.
- Admission requestFormio form
- Check identity and coverageAdmissions office
- Medical reviewNurseA case is here
- Specialist opinion needed?Yes: Specialist opinion · No: Assign a bed
- Specialist opinionSpecialist
- Assign a bedBed manager
- Patient admitted
How each step looks in Bridge.
Admission request
Start · Formio form
The admission request form starts the process, its fields mapped to process variables with no code.
Check identity and coverage
User task · Admissions office
The admissions office sees the request in its inbox, sorted by the planned admission date.
Medical review
User task · Nurse
The medical review is its own task for the nursing role, separate from the administrative steps.
Specialist opinion needed?
Decision
The rule that calls for a specialist can live in a decision table built in Bridge.
Specialist opinion
User task · Specialist
The specialist gets the case with the review beside it, and only when the rule asks for it.
Assign a bed
User task · Bed manager
The bed manager's form is prefilled from the earlier steps, and the SLA tracker warns if the admission date is at risk.
Patient admitted
End
The admission closes with every step and every change on record.
What a hospital asks of the workflow.
- Dates that hold
- Tasks sit in deadline lanes, the SLA tracker warns at the threshold you set, and the workload view shows who is holding what.
- Who changed what, and when
- Every action is in the audit trail with who, what, when and the outcome, and variables are tracked from the request onward.
- Medical and administrative work apart
- Medical and administrative steps are tasks for different groups: a task given to a group only appears for people whose role carries it.
Questions care providers ask first
Does Bridge come with this workflow?
No. It is an example of what a care provider can build in Bridge's BPMN designer, or sync from an existing Camunda 8 cluster. Our consulting team has built Formio and Camunda integrations for healthcare providers.
Can staff see only the patients they work with?
A task given to a group in the workflow only appears for people whose role carries that group, and each person sees the tasks they hold. Tell us your access rules in a demo and we will show how they map to roles.
Where is patient data kept?
Tell us your hosting and data-residency requirements with your trial or demo request, and we will confirm the setup that fits.
Other sectors
By role
Run your admissions in Bridge.
Start a free trial with your own Bridge organisation, or book a 30-minute demo around a workflow like yours.