Skip to main content

Terminology Service — Service Risk Register

Status: populated Owner: TBD Last updated: 2026-04-18 Companion: Service Template · 11 risks-and-tradeoffs

1. Risk Register

Risk IDRiskLikelihoodImpactOwnerMitigationStatus
RISK-TERM-01Licensed data not available at deployment — LOINC/SNOMED/RxNorm licenses not obtained or ETL not run; service starts with empty concept tableLowCriticalPlatform OpsReadiness probe blocks traffic until concept count > threshold; ETL job must complete before rollout; deployment runbook documents data procurement stepsOpen
RISK-TERM-02Licensed terminology data committed to source repo — developer accidentally includes copyrighted SNOMED RF2 or RxNorm RRF filesLowHighEngineering Lead.gitignore rules for all known licensed file types; pre-commit hook scans for licensed data file signatures; periodic audit of git logOpen
RISK-TERM-03Stale drug interaction data — drug interaction or contraindication table not updated when licensing source publishes safety-critical severity changesMediumHighClinical Safety OfficerQuarterly ETL update schedule enforced; terminology.etl.last_success_age metric alerts after 7 days; ETL run documented as compliance obligationOpen
RISK-TERM-04Full-text search index bloat after large import — GIN index grows excessively; search latency breaches SLOMediumMediumPlatform SREPost-import REINDEX CONCURRENTLY in ETL job; search latency alert fires at 500ms; index maintenance runbook in placeOpen
RISK-TERM-05Tenant custom concept duplicate of global concept — tenant admin creates a concept that shadows a global SNOMED/LOINC code, causing lookup inconsistenciesLowMediumEngineering LeadUniqueness index enforces (tenant_id, system, code) uniqueness; API returns 409 CONFLICT if tenant code matches an existing global code in the same systemOpen
RISK-TERM-06Cache stampede on Redis eviction — simultaneous expiry of hot concept keys causes thundering herd against PostgreSQLMediumMediumPlatform SRETTL jitter (±5%) on cache write; Redis SETNX-based locking for expensive $expand computations; Redis capacity right-sized for hot concept setOpen
RISK-TERM-07Offline edge snapshot outdated — edge deployment runs with terminology snapshot > 6 months old; drug interaction severity changes missedMediumHighPlatform OpsSnapshot age limit enforced (12 months hard stop); alert on edge instances running snapshot older than 6 months; quarterly snapshot generation scheduleOpen
RISK-TERM-08Afghanistan SNOMED affiliate license lapse — MoPH affiliate license not renewed; SNOMED data cannot be legally used or updatedLowHighMoPH / LegalLicense renewal tracked in compliance calendar; minimum 6-month advance notice required; fallback to ICD-10-CM if SNOMED unavailableOpen

2. Open Questions

  • Confirm the clinical knowledge source vendor for drug interaction data (Multum vs. DrugBank vs. NDF-RT) — affects licensing model and ETL format.
  • Clarify whether ICD-10-AM (Australian adaptation used regionally) needs to be added alongside ICD-10-CM for Afghan private hospital tenants.