Development and Testing Strategies
summary
Explains that FHIR provides concrete tooling—Happy, Java/.NET validators, Inferno, Touchstone, Cynthia and terminology servers—and makes specific claims: use a reference implementation for parsers and object models, profiles are rules not types (so code generators should produce facades or factory constructors), and you should validate only fields you depend on to avoid breaking production. Recommends filling out data (clinical safety checklist: 42 items), notes testing gaps (no standard for test patient IDs, servers testable but clients aren’t), and flags security checks for XHTML/markdown.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:23The Layers of FHIR
- 2:11Storage
- 5:16Reference Implementations
- 8:36Generating Object Code (AST)
- 12:07What about Profiles?
- 19:34Strategies for Working with Resources
- 24:57FHIR & Clinical Safety
- 26:40Transport: RESTful API
- 27:19Code Generation Options
- 29:40Multiple Implementation Guides
- 36:14Validator
- 37:39Example Data
- 40:52Testing Issues
- 42:29Testing Servers
related talks
21mAll you need to know about FHIR validation
40mTest driven development I: Introduction
47mLeveraging test-driven development with FHIR implementations
29mTooling
23mMaking the Healthcare Developer Experience
46mUsing clinFHIR to learn and develop FHIR solutions
50mIntroduction to FHIR
45mTest Driven Development II: Advanced