Crosswalks & hierarchies
This capability is arriving. Mappings between internal and external code sets become governed objects with owners, versions, and history, instead of spreadsheets that age quietly on a shared drive.
Crosswalks between any two code sets, versioned and stewarded.
Unmapped codes surface as findings rather than silent gaps.
Hierarchies for rollups live under the same governance as the codes themselves.
Map
Stewards build or import the crosswalk, and every unmapped code shows as an open item.
Govern
Changes go through review and land as new versions, with the old mapping preserved.
“What happens when a code has no mapping?”
It shows as a finding with an owner. Absence is failure here like everywhere else on the platform, so a gap never reads as a pass.
“Can we import the crosswalks we maintain today?”
Yes. They land as claims, and validation shows where they disagree with the data before anything relies on them.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.