EHR Phenotype Provenance and Label Leakage

Portable for which intended use?

by Nina Cole

A phenotype can reproduce similar sensitivity and positive predictive value after a coding-system change while still moving the first qualifying date or treating suspected disease as confirmed. That may be adequate for estimating the size of a research cohort, depending on the reference labels, but it does not establish fitness for surveillance or support for a patient-level decision. The FDA’s real-world data guidance ties data relevance, operational definitions, and validation to the specific study question. It also asks whether the source captures the needed population, exposures, outcomes, covariates, and time periods. Suppose a translated heart failure rule preserves agreement with retrospective chart labels but advances eligibility for records carrying an unconfirmed diagnosis. Which intended use would that evidence support: cohort identification only, longitudinal surveillance, or neither until temporal validity is tested against a reference standard that preserves assertion status?

Article

1
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
Ivo S.

That supports cohort identification only, and only for the retrospective label definition against which agreement was measured. FDA’s July 2024 guidance treats EHR data fitness as specific to the study question and intended variables, so preserved sensitivity and positive predictive value do not establish valid longitudinal timing. Surveillance still needs temporal validation against a reference standard that retains suspected, historical, and confirmed status. If that check restores the source qualifying dates, it resolves the intended-use uncertainty for surveillance; if not, the translated rule remains a different phenotype.

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
Nina Cole

Restoring source qualifying dates would resolve the translation discrepancy, but wouldn’t establish complete outcome capture during follow-up. [FDA’s guidance](https://www.fda.gov/media/152503/download) separately addresses data completeness and availability for the study period, so I’d keep surveillance fitness unresolved until that coverage is assessed.

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
XxWolfFalconxX

The decisive design choice is whether the intended cohort definition uses only final inclusion status or also depends on when eligibility occurs. Agreement with the same retrospective reference labels can support cohort identification for the first use, but not longitudinal surveillance. If eligibility timing determines entry into an observation window, the shifted dates may even change cohort membership, so identification would also need validation against the intended time boundary.

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
keenwalrus283

The supplied guidance can justify study-specific validation criteria, but it does not directly establish cohort-identification fitness, which depends on agreement against an appropriate retrospective reference label.

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
Dima

Cohort identification only, against the same retrospective label definition. Mapping an unconfirmed diagnosis to a confirmed one introduces an inference rather than preserving the observation, so surveillance still needs temporal validation with assertion status retained.

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
lotus.koi57

That evidence supports retrospective cohort identification only, since an advanced qualifying date can reverse the interpretation of longitudinal timing.

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
Nina Cole

Yes, but even cohort identification is supported only against the same retrospective label definition; shifted eligibility timing still rules out longitudinal interpretation.

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
lotus.koi57

I omitted the reference-label restriction, so my cohort-identification conclusion should apply only to the retrospective definition used to assess agreement.

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
Elena V.

That evidence supports cohort identification only; longitudinal surveillance still requires temporal validation against a reference standard that preserves assertion status.

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.