FHIR Registry & Packages
summary
Shows exactly how a FHIR package is built, versioned and published: a gzipped tarball ( .tgz ) that contains a single package folder with a package.json manifest and all conformance resources in JSON plus optional examples, and how semantic versioning and dependencies keep sets coherent (example: US Core hl7.fhir.us.core v3.2.0). Demonstrates installing from the official registry and API ecosystem (packages.fire.org / Simplifier feeds), creating packages with tooling and IG Publisher, validating locally, and using .NET and Java pipelines. Good if you want hands‑on packaging and publishing steps.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:44About the speaker
- 1:28Session overview
- 2:53Why use FHIR packages
- 8:10What are FHIR packages
- 11:01Package structure
- 13:06Finding packages
- 16:37Package registry API
- 18:23Installing packages
- 19:45Building on packages
- 20:49Creating packages
- 21:53Naming packages
- 23:19Semantic versioning
- 26:33Publishing packages
- 27:55Summary
- 28:38Q&A session
- 1:15:16Second session introduction
- 1:16:19Publishing with Simplifier
- 1:20:31Project lifecycle
- 1:21:34Creating project
- 1:23:16Simplifier overview
- 1:25:04Exploring projects
- 1:28:11Tutorial setup
- 1:36:37Adding resources
- 1:39:59Setting dependencies
- 1:41:48Uploading resources
- 1:43:37Creating IG
- 1:45:24Editing IG
- 1:47:09Enhancing IG
- 1:57:43Publishing package
