Introduction to profiling
summary
Profiling produces concrete StructureDefinition constraints and a packaged ImplementationGuide with canonical URLs that implementers consume; examples include added extensions, fixed identifier systems, tightened cardinalities and FHIRPath rules that require conditional checks. Tooling demonstrated: the forge editor (Windows-only), publication and registry via simplifier, and automation with the fireli terminal and npm packages; servers validate instances against the package and you must document what must-support means because it is a behavioral pact, not a machine-enforced requirement.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 2:27Agenda
- 3:14Why profiling
- 5:05Conformance resources
- 5:28Structure definition
- 6:01Operations definition
- 7:07Search parameters definition
- 8:13Capability statement
- 9:00Structure map
- 9:40Implementation guides
- 11:04Implementation guide visualization
- 11:30Fire Core specification
- 12:09Canonical URL
- 14:20Profiles
- 15:12Layered derived profiles
- 16:54Structure definitions
- 17:28Element definitions
- 18:22Profiling resource types
- 21:10Should support flag
- 22:16Complex constraints
- 24:38Extensions
- 27:12Packages
- 27:55Forge
- 28:59Official registries
- 29:51Private projects
- 30:43simplifier
- 32:11profiling tools
- 32:36modeling sessions
- 33:47QA
- 36:05Implementation Guide
- 38:12Distribution
- 39:44Core Profiles vs Resources
- 41:18Best Practices
- 42:57Must Support
