How and when to use FHIR Terminology Service API's
summary
Describes using the FHIR Terminology Service API to power real UIs and analytics by calling operations such as expand (administrative gender returns 4 codes; medication status returns 3), validate-code (checks codes like 38362002 for dengue or flags mismatched display text for 13644009), and translate (maps retired “bronze diabetes” to “diabetes mellitus due to hemochromatosis” via concept maps). Examples use a custom Australian jurisdictions code system and reference the Anto server as a deployable terminology backend.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:25Why FHIR Terminology
- 3:10Use Cases
- 6:07Terminology Overview
- 9:39Terminology Operations
- 10:42Data Entry
- 12:25Expand
- 15:08Expand Example
- 17:52Analysis
- 19:30Validation
- 20:15Validate Code
- 23:49Code Lookup
- 27:04Closure Example
- 27:48Mapping
- 28:54Translate
- 30:45Example
- 33:16Terminology Resources
- 34:17Code System Resources
- 37:44Code System Concepts
- 39:23Value Sets
- 41:23Concept Maps
- 41:43Terminology Servers
- 43:33Virtual Tables
- 44:20Things I havent covered
- 45:01Tools
