Author: Josh Kroman, Chief Operating Officer
When a health system moves its healthcare translation services to a new vendor, the contract changes hands and the accountability stays where it was. If a surveyor, a regulator or a plaintiff’s attorney later asks why a discharge instruction said one thing in English and something different in Spanish, the question lands on the program owner inside the organization. It does not land on whoever held the contract the month the file was produced.
That is why the handover deserves more attention than the pricing round that preceded it. Most of what makes a language program work day to day sits in assets the outgoing vendor has been maintaining on your behalf, and those assets are easiest to lose at the exact moment nobody has time to go looking for them.
A mature program accumulates more than finished files. By the time a contract comes up for renewal, a vendor is usually holding six things that took years to build:
Transitions rarely fail on the big, obvious items. They fail on four quieter ones.
A translation memory handed over as a raw export from an unnamed tool version, with no segmentation rules and no language codes, imports badly or not at all. The new vendor does what any vendor would do with an unusable file, which is set it aside and translate from scratch. You pay a second time for content you already own.
Three spreadsheets turn up with three different dates and no owner. If your team cannot point to one file and say this is the approved terminology, the new vendor will make its own calls, and six months later your materials will carry two different Spanish renderings of the same department name.
A patient-facing translation a pharmacist signed off on looks identical, in a file folder, to one that went out without review. When the distinction is not recorded anywhere the new vendor can read, everything gets treated as unverified and the clinical review cycle runs again on material that already passed it.
Language access documentation is usually held by whoever did the work. During a transition, responsibility for the months on either side of the cutover often belongs to nobody. That gap tends to be discovered later, by someone asking for it.
Five things do not transfer, whatever the contract says:
Who owns the translation memory? Whoever the contract says owns it. Many language services agreements are silent on the point, and silence tends to favor the party holding the file. If your agreement does not address memory and terminology ownership directly, that is worth raising before the renewal conversation rather than during the exit.
How long does a vendor transition take? It depends almost entirely on the condition of the assets rather than the size of the program. A health system with a current glossary, an importable memory and documented review status can move in weeks. One reconstructing terminology from finished PDFs should plan on months.
Do we have to retranslate everything? No, provided the memory and terminology transfer in usable form and prior review status is documented. Retranslation becomes the default only when the new vendor cannot tell what has been approved.
What about interpreting? Interpreting carries its own continuity problem. Scheduling history, credential records and the patient-facing familiarity built up in smaller language communities all live with the incumbent. Ask for the scheduling record and the credential documentation as part of the handover, not after it.
The strongest position in a vendor transition is the one you build before you need it: a current glossary, an exportable memory, documented review status and a named owner. Organizations that keep those four things in order tend to find that changing vendors is an administrative exercise. Organizations that do not tend to find out how much of their program was living in someone else’s system.
If you are weighing a change and want to know what condition your assets are in, Talk to a Specialist.