161573009

SNOMED CT concept 161573009 is "H/O: cardiac anomaly" (FSN: History of cardiac anomaly (situation)). It sits in the situation semantic tag.

H/O: cardiac anomaly maps to 2 ICD-10 codes: Z87.7, Z87.74.

H/O: cardiac anomaly is grouped under UMLS CUI C0455576. UMLS CUIs let you bridge between SNOMED CT and other terminologies (ICD-10, ICD-11, LOINC, RxNorm).

H/O: cardiac anomaly is in the SNOMED CT "situation" semantic tag. Semantic tags partition the terminology by what kind of clinical idea each concept represents (finding, disorder, procedure, body structure, substance, and so on).

SNOMED CT is the world's most comprehensive clinical terminology, with around 350,000 active concepts covering diseases, findings, procedures, body structures, and substances. It is the recommended terminology for EHR problem lists in many countries.

SNOMED CT describes clinical meaning. ICD-10 (and ICD-10-CM) describes billing categories. The SNOMED to ICD-10-CM map (maintained by NLM) gives one or more ICD codes per SNOMED concept. We expose those mappings on each concept page and through the cross_references field on the API.

Browsing the directory is free for anyone with a browser. Programmatic access (the /v1/reference/snomed-ct/* endpoints) needs an API key. Free tier covers low-volume hobby use; paid tiers cover production traffic.

Either type the ID or a term into the search bar above, or call GET /v1/reference/snomed-ct/{concept_id}. Both paths return the same data: FSN, preferred term, semantic tag, synonyms, and cross-maps to ICD-10, ICD-11, UMLS, LOINC, and RxNorm where they exist.

We rebuild against the most recent US Edition release on each NLM publication cycle. Concept IDs and FSNs are stable across builds; new concepts and retirements are reflected within days of an upstream release.

Yes for any production use. SNOMED International controls licensing through national affiliates (NLM in the US). The free tier here is for evaluation. Paid plans assume the customer holds a valid affiliate license or is using an exempted use case.