Background
Medical interpretation is coordination under time pressure. A request arrives, a qualified interpreter has to be found and assigned, the session has to happen, and the quality of it has to be defensible afterwards.
Run manually, that is a dispatcher with a phone and a spreadsheet — and it stops scaling long before demand does.
The challenge
Assignment is not a queue. The right interpreter for a request depends on language pair, clinical specialism, and availability at that moment — and getting it wrong in a medical context is not a scheduling inconvenience.
Quality assurance was the second requirement, and the one usually skipped. In healthcare the organisation has to be able to evidence what happened in a session, not merely that one occurred.
Interpreters also do not work at desks. Anything that required them to be at a computer to accept or manage work would not survive contact with how the job is actually done.
Our approach
We automated assignment against the attributes that actually decide it — language pair, specialism, availability — so the dispatcher stops being the bottleneck and becomes the exception handler.
Quality assurance was built into the workflow rather than added as a review step afterwards, because a QA process that depends on someone remembering to run it does not produce evidence when evidence is needed.
The Flutter companion app exists because interpreters are mobile. Accepting work, managing a session, and completing it happen on a phone, while the enterprise portal remains the place the operation is administered and reported from.
What we delivered
- Enterprise portal for administration, oversight, and reporting
- Flutter companion app for interpreters working in the field
- Automatic assignment by language pair, specialism, and availability
- Quality assurance built into the workflow, not bolted on afterwards
- Reporting dashboards for operational oversight
- API layer connecting portal, app, and reporting
Stack
The outcome
Assignment runs automatically against real qualifying criteria, interpreters manage their work from a phone, and the organisation can report on and evidence what happened.
It is the studio’s proof that a delivery is not just a web build: a portal, a native mobile app, and the API layer between them, designed as one operational system.