Imagine two organisations storing the same kinds of documents in two different filing cabinets.

The first cabinet has many very specific drawers. The second uses fewer, broader categories. Both systems work, but they organise the same reality differently.

Now imagine taking one document from the first cabinet and asking:

Where does this belong in the second one?

That is where translation comes in.

A ConceptMap describes how the drawers in one system relate to the drawers in another. Translation uses those relationships for one specific source code and returns one or more possible target codings.

Sometimes the answer is straightforward. One drawer has a clear equivalent in the other cabinet.

Sometimes several destinations are possible. And sometimes the second cabinet simply does not contain a drawer that preserves everything the first one expressed.

The document can still be filed. But part of the distinction that determined its original place may disappear.

This is why terminology translation is not simply replacing one code with another.

A detailed clinical concept may map to a broader classification because that is exactly what is needed for reporting. A local code may have several possible targets depending on context. And sometimes there is no sufficiently equivalent concept at all.

The translation may therefore be technically successful without the source and target meaning exactly the same thing.

That does not make the translation wrong.

It means the relationship matters.

Was the target equivalent? Broader? Narrower? Was additional context needed to decide? A good mapping makes those differences explicit rather than hiding them behind a destination code.

Because once that translated code moves downstream into reporting, analytics, research or another clinical system, it can easily begin to look like the original meaning was always that precise.

It wasn’t necessarily.

The ConceptMap tells us how the filing systems relate.
Translation asks where this particular document can go.

And perhaps the most important part of translation is not that we always find a destination, but that we understand what happened to meaning on the way there.

Moving a code is easy.
Preserving its meaning is harder.

Next week: Terminology Binding

Where does an information model meet clinical meaning?

#SemanticWeekly #ConceptMap #SemanticInteroperability #HealthInformatics