FHIR Profiling overview
summary
Overview of FHIR profiling shows what a profile actually is: a StructureDefinition that constrains resources or data types, uses canonical URLs for stable identity, and relies on FHIRPath expressions for complex constraints. Tooling demonstrated includes the Forge editor, IG Publisher/IG Builder and npm-style FHIR packages for distribution. Servers validate instances against profiles, generate snapshots from differentials, and can dynamically install packages and search-parameters. Examples: nationality as an extension, CapabilityStatement advertising supported profiles, and Simplifier as a public registry.
AI-written summary · about
chapters (40)
- 0:00Introduction
- 0:40Michel Rutten
- 1:13Topics
- 2:00Why profiling
- 2:40Part of a profile
- 6:21Compatability
- 6:50Operations
- 7:20Custom searches
- 7:56Capability statement
- 8:52Structure map
- 9:35Implementation guide
- 10:27UML diagram
- 10:53FHIR structure definition
- 11:39FHIR bootstrap
- 12:27canonical URL
- 14:06profile example
- 14:32profile definition
- 15:25data type vs resource
- 16:30layering
- 17:58structure definition
- 18:55element definition
- 19:53complex constraints
- 23:21versioning
- 24:27breaking changes
- 25:52differential and snapshot
- 27:32authoring profiles
- 28:21professional tools
- 29:17Forge
- 30:10Extensions
- 30:56Finding an extension
- 32:02Extensions on all elements
- 34:32Types of extensions
- 35:32Packages
- 37:37Package Server
- 37:59Package Client
- 38:24Implementation Guides
- 40:59IG Builder
- 42:15CMS World
- 42:56HL7 Registry
- 44:03Markdown editor
