Introduction to Profiling
summary
Overview of the FHIR conformance layer: profiles are StructureDefinitions that constrain core resources (cardinality can be tightened but required core elements cannot be made optional), extensions are defined as StructureDefinitions with explicit contexts, and packages are zipped sets of conformance resources while an implementation guide adds human-readable docs and examples. Tools shown and recommended: Forge for authoring and consuming packages, Simplifier.net as a public registry and package host, and the importance of a unique StructureDefinition canonical URL for resolvable profiles and validation.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:25FHIR Profiling Overview
- 4:50FHIR Conformance Resources
- 6:26Operation Definition
- 7:40SearchParameter
- 9:07Capability Statement
- 10:46Structure Map
- 13:15Conformance Module
- 13:58Used to define the FHIR core spec
- 18:53Layered Profiles
- 21:04Structure Definition
- 23:07Profiling a resource type
- 25:45Example of a profile (us-core-patient)
- 28:47Referring to a profile
- 31:13Extensions
- 33:19Defining an extension
- 34:37FHIR Package
- 35:23Forge Package Manager
- 36:14Official HL7 FHIR registries
- 39:41Profiling tools
- 40:14What's next?
