startthat.work home

IS-03 Common data model harmonisation (OMOP (Observational Medical Outcomes Partnership) common data model; data harmonisation)

Transforms source datasets into one shared structure and vocabulary so that the same analysis runs on each and produces a standardised dataset with a coverage report.

Integrate across sourcesEvidence: DocumentedPreparation technique, runs in step 5.2Strongest statement: describe

What it does

Transforms source datasets into one shared structure and vocabulary so that the same analysis runs on each. Artefact: a standardised database. Read concept coverage, unmapped records (concept identifier 0) and capture differences between sources.

When to use it

Use when you must run one analysis across several datasets that record the same domain in different formats.

When it does not fit

Fits when a domain standard exists. Misfit: many source values have no standard concept, or sources capture events differently. Only the OMOP instance was read; questionnaire harmonisation was not.

Result format

The result is a standardised database in one shared structure and vocabulary, with a report of concept coverage, the unmapped records (concept identifier 0) and the capture differences between sources.

Requirements on the material

PropertyRequirement typeRequirement
StructureApplies in some casesrequires=structured; requires=semi-structured
Content typeAlways appliesrequires=tabular
Unit of analysisAlways appliesrequires=record; requires=dataset
Level of detail availableAlways appliesrequires=record-level
Number of sourcesAlways appliesrequires=two or more
Appraises source credibilityApplies in some casesno

Not restricted on: Variable types, Time structure, How the sample was chosen, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialnone
Additional sources neededreference structure
Not for (rules)none
Not for (text)Many source values have no standard concept, or sources capture events differently. Only the OMOP instance was read; questionnaire harmonisation was not.

Choosing and ordering

Kind of techniquePreparation technique, runs in step 5.2
Phase tagverify and prepare
Other phase tagsnone
Kind of findinggap; difference
Question answeredwhat
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetproceed with limit stated

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: deterministic.

StakesCheckPerson involvedCounts as a different method
exploratoryinput validationnoneno
decision-informinginput validationnoneno
decision-informingspot checkoptionalno
high-stakesinput validationnoneno
high-stakesspot checkoptionalno
high-stakesindependent reviewneededno
high-stakesprovenance lognoneno

Failure modes and limits

Model suitabilitymodel plus code
Typical model failureMaps source values to the wrong standard concept and does not report unmapped records.
Error sourcesinput data; data transformation
Certainty limitsCertainty drops with a high share of unmapped values and differences in what each source records (indirectness and inconsistency).

Evidence and tag basis

Documented. No observational database captures all events equally well, and source values are not harmonised across sources. (Book of OHDSI, Common Data Model)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.