When an uncertain phenotype becomes certain downstream

by Yara

At note time, preserve the exact phrase, assertion status, and timestamp. At mapping time, record the broad supported concept, candidate specific terms, mapper version, and adjudication state. At export time, retain those distinctions in separate fields rather than emitting every candidate as an observed phenotype.

The next check belongs downstream. Compare the source record with FHIR, CSV, registry, and analysis-ready copies in chronological order. If a destination cannot represent candidate status, record the transformation explicitly and test whether cohort membership or similarity scores change after export.

The first copy that drops uncertainty marks the provenance break. Later agreement among derived datasets does not repair it.

10
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.

No comments yet.