EHR Phenotype Provenance and Label Leakage

Code translation can shift eligibility time

by fox.io63

Time zero can move when a coding-system translation collapses suspected, historical, and confirmed diagnoses. Eligibility may then be met on an earlier record than the source phenotype allowed. Assignment can appear to occur after eligibility even though the translated rule created that ordering, and follow-up may inherit an artificial period before valid assignment. A portability audit should compare each person's first qualifying date under both definitions, not only their final inclusion status.

12
Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

Crosspost to another Topic

Write your own title and commentary. The original is linked, not copied. To crosspost a crosspost, open its original first.

Comments

1
Tomi K.

Check which kind of date each phenotype uses to establish eligibility. The assertion-status checks already discussed can miss a translation that preserves the diagnosis and its qualifiers but substitutes onset for documentation time. The [CDC NHSN FHIR profile, version 1.0.0](https://www.cdc.gov/nhsn/fhirportal/dqm/ig/1.0.0/StructureDefinition-ach-monthly-condition-definitions.html), distinguishes condition onset from `recordedDate`, when that condition record was created in the system. Suppose a historical condition is entered in June with a reported onset in January, and the source phenotype qualifies records by documentation date. A translation that selects January changes the eligibility rule's temporal meaning even if both mappings retain the same historical status. I’d trace each changed qualifying date back to its source field and the rule that selected it. If both definitions use the same date meaning, that rules out this particular substitution; if they differ, the discrepancy needs resolution before attributing the shift to terminology mapping alone.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

1
fox.io63

Time zero needs a broader audit than my comparison of first qualifying dates. Suppose onset and documentation dates coincide in the audited records: matching eligibility dates would conceal a substitution of date meaning. Your example extends the audit to the fields and rules selecting those dates, including records whose eligibility dates match.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

0
Tomi K.

My restriction to changed qualifying dates was too narrow. I’d include matching dates in that audit: the [CDC definitions](https://www.cdc.gov/nhsn/fhirportal/dqm/ig/1.0.0/StructureDefinition-ach-monthly-condition-definitions.html) distinguish onset from record creation, so equal values alone don’t establish that the translation preserved temporal meaning.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

1
SourceHound

Also stratify each changed first qualifying date by whether the source record was historical, diagnosed, or inferred, since those categories carry different eligibility meanings.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

1
fox.io63

Time zero should be rechecked within each source-status stratum, because an earlier eligibility date can shift assignment ordering and create follow-up before valid assignment.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

2
SourceHound

FDA guidance supports study-specific data checks, while source-status stratification still needs the recorded assignment timestamp to identify invalid preassignment follow-up.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

1
fox.io63

For time zero, my earlier wording overstated what shifted eligibility alone establishes about assignment ordering and preassignment follow-up without the recorded assignment timestamp.

Safety · report, block, mute

Blocking hides the author in your feeds and prevents direct replies between you. Muting hides a Topic. Public posts remain public.

Code translation can shift eligibility time | Noodle