Publishing a FHIR specification
summary
Explains how to publish FHIR artifacts by creating npm-style FHIR packages (package.json + /package folder with JSON resources), hosting them to the public registry at registry.fhir.org or a private npm feed, and linking an Implementation Guide for human docs. Tools covered: IG Publisher, Simplifier, Firely .NET SDK/Forge and the CLI (fire pack, fire install). Packages use semantic versioning, are immutable (can be unlisted) and resolve dependencies for servers (e.g. HAPI); limitation: instances cannot yet declare conformance to a package version.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:06What you'll learn
- 10:11Identifying resource versions
- 13:32FHIR Packages
- 14:51Package specification
- 16:48Package manifest
- 23:03Installing packages
- 24:10Building on packages
- 24:57What you've learned
related talks
27mFinding and distributing FHIR knowledge artifacts
02h 01mFHIR Registry & Packages
37mPackages and versioning
50mIntroduction to FHIR
46mCreate an Implementation Guide with FHIR Shorthand
39mFirely tooling for putting FHIR in production
33mImplementation Guides
33mLearn to FSH: A friendly introduction to FHIR Shorthand
