All you need to know about FHIR validation
summary
Survey of FHIR validation tools with concrete tradeoffs: SUSHI applies ~60 validation rules but skips slice membership and terminology checks, the IG Publisher produces a QA report that also validates terminology and links, and the Java validator is the gold standard covering narrative, terminologies, instance vs definition checks. .NET validator and Simplifier provide web-based checks; Inferno and ClinFHIR offer web front ends; Hammer runs .NET and Java side by side to show differences. Runtime validation can check referential integrity, may call terminology servers, and often adds milliseconds of latency.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:01Validating a resource
- 0:18Forge
- 1:20SUSHI
- 3:01IG Publisher
- 4:44Java Validator
- 6:05NET Validator
- 6:49Hammer
- 7:44Simplifier
- 8:38Other tools
- 9:24TouchStone
- 10:19ONC's API Test Kit
- 11:52Validating as a client
- 13:23Validating as a server
- 14:19Contact
related talks
46mDevelopment and Testing Strategies
45mAccelerate Quality: Building FHIR that Meets Federal Mandates
44mFHIR API Testing with Inferno
39mFHIR Server Certification with Inferno
40mTest driven development I: Introduction
45mTest Driven Development II: Advanced
35mPassing the Inferno G10 tests with your FHIR server
17mFHIR up your tests: Integration tests