FHIR community process: as an IG developer or implementer
summary
Preview of a formal FHIR Community Process (FCP) that standardizes how Implementation Guides get produced: a public registry, a required project proposal (scope, license, dependencies, maintenance, security), mandated publication at a canonical URL and a QA Report with zero errors goal, and an FCP registry of participants. Governance includes a Coordination Committee (~15 reps) and co-chairs, optional fees for non‑affiliates, HL7 projects auto‑compliant, and a checklist of milestones, version strategy, testing/reference implementation encouragement, and transfer/maintenance obligations.
AI-written summary · about
chapters (13)
- 0:00Introduction to FHIR community process
- 1:08What is the FHIR Community Process
- 3:38Purpose and benefits of FCP
- 5:21Role of HL7 in FCP
- 7:14Guidelines for FCP participants
- 8:37Project development cycle in FCP
- 11:35Quality assurance and versioning
- 11:59FCP governance structure
- 13:26Participant responsibilities
- 14:32Affiliates and FCP participation
- 15:17FCP vs ANSI process differences
- 16:21Next steps and approval process
- 17:06Q&A session
related talks
46mCreate an Implementation Guide with FHIR Shorthand
40mFHIR 5
31mPublishing a FHIR specification
43mGlobal Implementations with the International Patient Access
43mNavigating the FHIR Community
46mInternational Patient Summary (IPS) - Moving from Specification to Implementation
46mCreate an Implementation Guide with FHIR Shorthand
43mEnglish introduction to FHIR