Loading...
Loading...
Found 3 Skills
Use SNOMED CT's semantic attribute relationships to answer clinical questions. Finds concepts by relationship attribute (finding site, causative agent, associated morphology, procedure site), navigates the IS-A hierarchy, and composes property-filtered ValueSets. Use when the user asks things like "all disorders of the heart", "all procedures on the kidney", "all conditions caused by bacteria", "subtypes of hypertension", "symptoms of X", "complications of X", or any query that involves clinical relationships between concepts rather than simple text search.
Map a code from any clinical terminology (ICD-10-CM, LOINC, RxNorm) to its SNOMED CT equivalent in order to unlock SNOMED's rich semantic attribute relationships. Use when the user has a code in a non-SNOMED system and wants to explore related concepts, find clinically adjacent codes, understand the semantic meaning, or build a SNOMED-based ValueSet from a non-SNOMED starting point. Always propose this when a user asks about relationships or "what is related to X" and the code is not already in SNOMED.
Build clinically meaningful ValueSets using the property filter system of each code system: SNOMED CT (attribute relationships + hierarchy), LOINC (CLASS/CLASSTYPE/STATUS/ORDER_OBS), RxNorm (TTY + ingredient relationships), ICD-10-CM (parent hierarchy), and UCUM (physical quantity). Use when the user wants to define a ValueSet by clinical criteria rather than enumerating codes manually, or when they ask "give me all X codes" for a code system.