Packages and versioning
summary
Packages group related FHIR conformance resources so one package version replaces many per-profile versions, using the NPM model with package.json manifest and semantic versioning (major.minor.patch) and allowing minor-range flexibility for upgrades. A package server/registry (for example simplifier package registry) hosts compressed JSON content; package clients resolve dependencies into a local package client cache and install transitive packages, letting validators and servers enforce a named scope instead of chasing individual profile versions.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:43Conformance Resources
- 3:14Problems with versioning
- 5:02Scope
- 11:46What is a package
- 15:09What do packages solve
- 17:30What packages look like
- 21:08Use case dependencies
- 24:45Package Registry
- 28:51State of Packages
- 34:50Question
related talks
02h 01mFHIR Registry & Packages
27mFinding and distributing FHIR knowledge artifacts
31mPublishing a FHIR specification
40mVersioning
41mThe Future of JavaScript Package Management
36mThe Role of Package Managers as Partners in License and Attribution Compliance
25mMaintaining your company’s open-source ecosystem
45mNext Gen Package Management