Introduction to FHIR Profiling
summary
FHIR’s conformance layer uses StructureDefinition, ValueSet and extensions so implementers can tighten or add rules to core resources; profiles can make optional fields mandatory (example: identifier and name become required and mustSupport), bindings point to value sets, and complex rules use FHIRPath expressions validated by FHIR-aware validators. Tooling is central: use Forge, FSH (FHIR Shorthand) or Simplifier.net (backing registry.fire.org and package feeds) rather than hand-editing; the 80/20 rule explains why many extras become extensions rather than core.
AI-written summary · about
chapters (12)
- 0:00Welcome and introduction
- 1:04Why FHIR profiling is needed
- 3:17Conformance layer overview
- 17:32Layered profiles explained
- 18:37Structure definition basics
- 21:27Extensions in FHIR
- 24:41Complex constraints
- 26:49Must support fields
- 27:52Profile validation
- 28:35Registries and repositories
- 31:06Tooling for profiles
- 33:10Q&A session
