Case study · Data standards

One source of truth for every data element

A health data team had no single source of truth for its data elements, and no one owned the definitions. We built a cloud registry that gave every element one owner, one current version and a clear mapping to national standards.

Client: Next Level Health Innovations
Role: Design, build and rollout
Built with: Knack · cloud database
Standards: FHIR · USCDI · SNOMED CT · LOINC

100%of data elements under version control

50%faster data review

4national standards mapped in one place

✳ Data Element RegistryIllustrative screen

All elementsNeeds reviewApprovedSearch elements…

Element	FHIR path	Standard	Version	Status
Patient date of birth	`Patient.birthDate`	LOINC 21112-8	v3	Approved
Primary language	`Patient.communication`	USCDI v3	v2	In review
Lab test result	`Observation.value`	LOINC 2345-7	v4	Approved
Immunization code	`Immunization.vaccineCode`	CVX	v1	Draft
Diagnosis	`Condition.code`	SNOMED CT	v2	Approved

Data standards · Next Level Health InnovationsWhich version of this field is current?100%of data elements under version controlRead the story ↓

Their challenge

No single source of truth, and no owner for the definitions

The same data element was defined in several places, and no one was responsible for keeping those definitions in step. Two people could hold two different versions of the same field. Reviews dragged because every check started with finding the latest copy, and nothing recorded who had approved what.

Our approach

One source of truth, built for the people using it

Inventory. Gathered every element from every file and agreed a single definition for each.
Model. Designed the registry in Knack: elements, versions, mappings and reviewers, all linked.
Map. Matched each field to FHIR, USCDI, SNOMED CT and LOINC, so the data speaks the language other systems expect.
Control. Set role-based permissions so editors propose, reviewers approve, and every change keeps its history.

Final result

Reviews in half the time, with nothing lost

Every element now has one owner, one current version and a full history. Reviewers work from a single queue instead of chasing files, which cut data review time by half. When a partner asks how a field maps to a national standard, the answer is already there.

What this means for you

Who owns your data definitions?

If your team argues about which definition is right, waits on reviews, or can't show how fields map to FHIR or USCDI, the same approach works for you. It can be built on Knack, Dynamics 365 or your own stack.

Book a call about your data ↗See data & reporting