FHIR Profiling: Overview & Introduction
summary
Explains how FHIR profiling produces machine-readable constraints (structureDefinitions, elementDefinitions) used for validation, code/UI generation and publication; demonstrates tooling like Forge and Simplifier, the HL7 registry and package-based distribution (NPM-style) for dependencies; details canonical URLs, differential vs snapshot exchange, and mandatory vs optional extensions with the race/ethnicity example; replaces XPath with FHIRPath for readable cross-format constraints and shows how validators resolve profiles and implementation guides during runtime.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:19Why do we need profiling?
- 2:38FHIR Conformance Resources
- 4:00Structure Definition
- 6:52Capability Statement
- 8:51FHIR Conformance Module
- 9:34Used to define the FHIR core spec
- 14:06Layered Profiles
- 16:54Complex constraints
- 18:26Referring to a profile
- 19:48Versioning - non breaking changes
- 20:29Versioning -breaking changes
- 20:46Differential vs. Snapshot
- 21:54Authoring Profiles
- 24:09Defining an extension
- 24:47Using an extension in a resource
- 26:27Primitive Extensions
- 28:53FHIR Package Manager
- 29:13Dependencies
- 29:59Implementation Guide Resource
- 32:24Implementation Guides & FHIR Packages
- 32:42Authoring implementation Guides
- 34:03Authoring & Publication Workflows
- 37:37SIMPLIFIER.NET Implementation Guides
- 38:19FHIR Profiling Exercises
