Coordinate Translation Protocol¶
Translation protocol — instantiates Local-Chart Atlas Modeling
Turns the transition between two charts into an executable rule that converts one chart's vocabulary, units, and statuses into another's.
The Coordinate Translation Protocol is the executable transformation that actually moves a case from one chart's coordinate system into another's. Where a seam ledger lists that two charts overlap, this protocol performs the crossing: it declares what each side's symbols mean and specifies, field by field, how a value in chart A becomes the corresponding value in chart B. Its defining move is to make translation precise and runnable — every unit, status, category, or role on one side has a stated rule for its counterpart on the other, so a person or system can carry a case across the seam without improvising. It is the transition map turned into a working converter; it does not catalogue all the seams of the atlas, and it does not test its own fidelity.
Example¶
A hospital network exchanges records between a system that codes diagnoses in ICD-10-CM and analytics tools built on SNOMED CT — two locally-valid clinical vocabularies with different structures. Free-hand translation would be dangerous: the concepts do not line up one-to-one, and a wrong map can turn a benign finding into a billable disease. So the informatics team builds a Coordinate Translation Protocol. It first declares each side's vocabulary — what an ICD-10-CM code denotes, what a SNOMED CT concept denotes — then specifies the mapping rule for each: exact matches where they exist, "map to the nearest broader concept" where SNOMED is finer, and an explicit no-safe-map verdict where a code has no faithful counterpart, which routes the case to human review rather than guessing.
A clinician moving a patient summary into the analytics chart runs it through the protocol: "type 2 diabetes with diabetic nephropathy" converts cleanly; a rare combined code hits the no-safe-map rule and is flagged, not silently coerced. The protocol did not decide whether the two charts overlap — that was already known — it decided, executably and reproducibly, how to cross.
How it works¶
- Declare both vocabularies. State what each chart's symbols mean — units, statuses, categories, roles — because a translation cannot be specified until each side says what it holds.
- Specify field-level rules. For every source symbol give its target: exact map, computed conversion, coarsening to a broader concept, or an explicit "no faithful map."
- Make the no-map case explicit. Where no honest counterpart exists, the protocol says so and routes to review, rather than forcing a value.
- Keep it directional and inspectable. A→B and B→A are stated separately (they are rarely simple inverses), so each direction can be read, run, and audited on its own.
Tuning parameters¶
- Strictness — exact-only versus permitted lossy approximations; strict rules refuse more crossings but never silently distort, loose rules always return a value at the cost of hidden error.
- Coarsening policy — whether a finer source concept maps up to a broader target or is refused; coarsening keeps flow moving but discards granularity.
- No-map handling — fail-closed to human review versus fail-open to a default; fail-closed is safer, fail-open is faster and riskier.
- Directional symmetry — whether the reverse map is required to be a true inverse or is authored independently; independent directions handle real asymmetries but must be maintained in pairs.
When it helps, and when it misleads¶
Its strength is that it makes a crossing reproducible and reviewable: the same case always translates the same way, and the rules can be read and challenged rather than living in someone's head. Naming the no-map case is what keeps it honest — it is a mechanism that can say "these two charts do not correspond here" instead of manufacturing a false equivalence, which is the essence of semantic interoperability[n1] done responsibly.
Its failure mode is confident coercion: a mapping that always returns some target value can quietly convert "unknown" into a specific wrong answer, and the tidy output hides the loss. The classic misuse is trusting the forward map without ever checking that a case survives a round trip through it. The guarding discipline is to keep no-map and lossy verdicts visible in the output and to hand the protocol to a round-trip test rather than assuming a rule that reads sensibly actually preserves meaning.
How it implements the components¶
local_coordinate_vocabulary— it requires and records each chart's declared symbols, units, and statuses; without these declarations no rule can be written.transition_map— it is the transition map made executable: the field-by-field conversion that carries a case from one chart's coordinates to another's.
It does not inventory every overlapping pair in the atlas — the overlap_region catalogue and its global_invariant_set columns are Overlap Transition Table's — and it does not verify its own fidelity: the seam_consistency_check belongs to Round-Trip Consistency Test, which drives cases through this protocol to measure what it loses.
Related¶
- Instantiates: Local-Chart Atlas Modeling — it is the working converter that realizes a single seam's transition map.
- Sibling mechanisms: Overlap Transition Table · Round-Trip Consistency Test · Chart Atlas Map · Boundary Case Path Trace · Local Model Ensemble with Gating · Manifold Learning Diagnostic · Neighborhood Preservation Probe · Geodesic or Path-Distance Audit · Atlas Stewardship Review
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Coordinate Translation Protocol operates as a repeatable ordered procedure or handoff sequence that coordinates action because it turns the transition between two charts into an executable rule that converts one chart's vocabulary, units, and statuses into another's.
Independent corroboration: The frozen evidence defines Coordinate Translation Protocol as 'Turns the transition between two charts into an executable rule that converts one chart's vocabulary, units, and statuses into another's', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Vocabulary-control and interoperability practice established maintained crosswalks that preserve meaning across terminologies and classification schemes.
Related originating lineages:
- Computer Science & Software Engineering — Executable adapters, validation, and bidirectional mapping logic make the protocol operational.
- Mathematics — Transition maps and coordinate transformations supply the formal analogy of preserving identity across representations.
Review resolution: Vocabulary and classification crosswalks are most directly rooted in library and information science. Computer science makes them executable and mathematics supplies the transition-map formalism, so the generic protocol is an encyclopedia synthesis rather than a purely mathematical mechanism.
Attribution caveat: The mechanism extends mathematical transition-map language into an executable semantic interoperability protocol.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- U.S. National Library of Medicine: SNOMED CT to ICD-10-CM mapping project
- NLM: SNOMED CT to ICD-10-CM Map Technical Specifications
Notes¶
[n1] Semantic interoperability is the ability of two systems to exchange information such that the meaning — not just the bytes — is preserved. Maintained mappings between clinical terminologies such as ICD-10-CM and SNOMED CT are a standing real-world example; a translation protocol is the artifact that carries the meaning across. ↩