Patient language reaches interpreter matching before the session starts

Interpreter matching should begin with the patient's language, not with a coordinator searching for it by hand.

The language-services provider already had professional interpreters and a working interpretation platform. The missing information was inside the hospital patient record. Until that information could be retrieved, the assignment workflow depended on a separate check and the service could not fit cleanly into hospital operations.

We connected the patient record to the interpretation workflow. The patient's recorded language can be retrieved and used to support interpreter matching before the session starts. It is a small change in the interface between systems, but it changes what the coordinator can do with confidence.

Client background

Our client is a language-services provider working with hospital teams and professional human interpreters. The company needed its existing service to work with the information hospitals already held about the patient.

Patient language is not just a profile detail. It affects access to the interaction, the suitability of the interpreter and the time required to organise the session. If the information is not available to the matching workflow, the service team has to find it elsewhere or ask the patient again.

Business challenge

The matching process had a fragmented starting point. The request for an interpreter was in one workflow, the patient's language in another record and the list of available interpreters in a third place.

That separation creates avoidable work. Someone has to confirm the language, look for a suitable interpreter, check availability and then carry the result back into the session workflow. A missing or delayed check can mean the right person is not assigned early enough.

The provider also needed the integration to support its commercial goal. Hospital customers expect a language service to fit the patient journey, not ask staff to maintain a manual bridge between the chart and the interpreter request.

Implementation

We built a structured connection between the patient record and the interpretation workflow. Patient language can be retrieved as part of the service, then used to support assignment of the appropriate interpreter.

The session note follows the same integration path into the patient's record after the interaction. That creates a complete loop: information from the chart helps organise the service, and information from the service returns to the chart.

The integration uses FHIR, a standard for exchanging structured healthcare records, and was piloted across five hospital systems. The client's existing interpretation platform stayed in place. The new workflow added context to it rather than requiring the provider to build a second matching operation for every hospital environment.

The matching result remains a support for the person responsible for the assignment. Retrieving a patient's language does not remove the need to check availability, suitability or the details of the request. It removes a manual information gap before those decisions are made.

Why it was difficult

The patient's language is sensitive information and the patient record is a controlled environment. The integration had to retrieve the right information for the right workflow without turning a hospital record into a loose data feed.

The service also had to work across multiple hospital environments. A matching workflow that only works in one test record is not enough for a provider seeking to serve hospital customers. The pilot had to demonstrate a repeatable path from patient information to interpreter assignment and back to the chart.

The key design choice was to preserve context. The assignment should carry the source record and the session should leave a structured note. That makes the workflow easier to review when somebody asks why an interpreter was selected or what was recorded after the call.

Value delivered

• Patient language can be retrieved to support interpreter matching before the session.
• Coordinators have less manual searching between the patient record and the interpretation service.
• Interpretation session notes can return to the patient's record after the interaction.
• The existing interpretation platform remains in place.
• The workflow was piloted across five hospital systems.
• The provider gained an integration pattern that makes its service more useful to hospital teams.

The outcome is not “automation” for its own sake. It is a better starting point for the person organising the session and a more complete record for the people responsible for the patient's care.

What this means for your business

If a decision depends on information stored in another system, every manual lookup is a chance for delay, error or an incomplete record. The first useful integration is often the one that retrieves the missing context before the next person has to act.

The same pattern applies to an insurer matching a claim to a policy, a lender checking an application or a professional-services firm assigning a matter to the right specialist. Put the relevant context into the workflow, keep the source visible and leave the decision with the person responsible for it.

Related: Workflow integration · Interpreter operations · Digital health and NHS suppliers