Finding an OMOP Concept's Standard Mapping via WebAPI
Reference notes on OMOP’s standard-concept mapping, one level below the usual explanation. For why OMOP forces everything through standard concepts in the first place, see Michael Wornow’s STARR-OMOP post, which walks the same ICD-9 → SNOMED example (427.31 → 313217) via concept_relationship. The question these notes answer: given a non-standard OMOP concept, which standard concept does it actually resolve to, does that standard concept have any patients in this data, and how do you find out, concretely, at the level of the exact tables, one real row, and the actual WebAPI SQL/JSON? ...