Finding and distributing FHIR knowledge artifacts
summary
Updated registry indexes FHIR packages hosted as npm style tgz files with a package.json manifest and JSON resources, imported from feeds by a Simplifier backend and exposed at packages.fire.org. Tools like IG Publisher, Firely tooling and FHIR Terminal produce packages automatically, names follow region.organization.subject and versions use semantic versioning. CRMI work adds on demand bundle assembly and a $dependencies operation for artifact repositories. Organizations can run private npm servers to curate packages and enforce IP and distribution rules.
AI-written summary · about
chapters (13)
- 0:00Introduction to FHIR knowledge artifacts
- 1:05What are knowledge artifacts
- 2:33Content vs conformance IGs
- 3:57Ways to distribute artifacts
- 5:42Finding FHIR packages
- 8:53Package registry vs IG registry
- 10:18What is a FHIR package
- 13:05Creating and publishing packages
- 15:15Naming and versioning packages
- 17:41Live demo of package creation
- 19:47Private and public packages
- 21:34Distributing specialized bundles
- 22:36Q&A and closing remarks
