Using Terminology Services: further steps
summary
FHIR adds two underused operations: $closure builds and maintains a client-side transitive closure table so an app can cache subsumption results instead of repeatedly querying a terminology server, improving performance for large code systems (SNOMED ~500k concepts can expand to ~5–6M closure rows). Demo uses Postman against an Australian terminology server (Michael Lally / Jim Steele) returning ConceptMap payloads and populating a local DB (demo ended up with nine cached rows); servers signal when reinitialization is required. $find-matches is low‑maturity with poor server support and unclear use cases.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:50Rob Hausam
- 1:42Terminology changes
- 3:39Overview
- 5:17Goal
- 7:38Questions
- 14:33Why use it
- 21:30Do you really need it
- 24:38transitive closure table
- 29:16Example
- 30:34Demo
- 32:51Closure Table
- 38:15Local Data
- 43:28Find Matches
- 44:40Outro
related talks
41mMastering FHIR Terminology: Navigating advanced services
47mIntroduction to terminology
42mSNOMED CT with FHIR
24mRising trends in national FHIR Terminology services
30mIntroduction to SNOMED with FHIR
43mFollow the Yellow-Brick Code (A Terminology journey)
43mAdvanced Search
50mTerminology mapping and translation – ConceptMap updates in FHIR R5