FHIR Repository Process

Return to FHIR Main Page

Working Document

Repository Governance Process and Requirements

Meeting Information

• Project calls: Weekly, Wednesday from noon to 1pm Eastern
  • Telephone Number: 1-650-479-3208 Meeting Number (access code) 809 854 683
  • WebEx: https://enablecare.webex.com/enablecare/j.php?MTID=ma1350283e5a2341bc53a911c6c2c44dc
    • Click on this link to add to your Outlook calendar: https://enablecare.webex.com/enablecare/j.php?MTID=m62bbf1a13d18d53672f61b66bdafb632
  • Listserv for this project: FHIRREGISTRY

Meeting Agendas / Meeting Minutes

• Link to FHIR Repository Process Project Agenda and Minutes stored on GForge
  • 2016-09-07 FHIR Repository Process Pjt Agenda and Minutes

Project Documents

• Link to working documents/wiki pages
• Link to project GForge
• Link to reference documentation on GForge, HL7 Web site WG Documents/Presentations page, or external web pages

Project Information

Link to Project 1058 - FHIR Repository Process and Requirements, Phase 1 in the HL7 Project Insight Searchable Database

• Brief description of project:The FHIR specification, community development process, and supporting tooling are starting to reach maturity. As the FHIR specification approaches its third STU Publication, we need to ensure clarity about how the development of standards and stable implementation guides will occur, especially in the US realm. This phase 1 project is intended to addresses the need to design and implement a policy that creates confidence and direction around pilots and productions in the areas of specification development, maintenance and adoption. This project will address the requirements and implementation steps to ensure we address the following needs: - Specification Development Process - identify how specifications - either of or in the US realm - are developed, and how requirements divergence between them are resolved, along with a governance process which provides quality, predictability and consistent management of the specification artifacts. - A Specification Publication Process - identify how and where specifications are published - both the final rendered form, and the technical resources that support them - FHIR Repository Management Process - identify how HL7 manages the life cycle, access control, and approval process for the technical resources associated with implementation guides in the US realm along with a repository for extensions, profiles, Implementation Guide and value sets (including a list of functional requirements of the repository) - FHIR Specification Maturity Process - identify how specifications migrate through a maturity process from initial draft to a final (normative?) form, and how this relates to the above processes. - Standard specification for submission of extension, profiles and value sets to a FHIR repository. - FHIR Repository version process. Address the requirements to create versions of extension, value sets and profiles that are 'published' to the repository. Requirements may vary by maturity level. - A US Regulatory Process - clarify how all these processes above inter-relate to US regulatory requirements. - A Governance process which the tooling and processes should support with quality, user-friendly, predictability and consistent management of the repository. - NOTE: The actual validation and repository tools are out of scope, this PSS is about the HL7 process for the use of and business requirements for validation and repository of FHIR resources, extensions, profiles & IGs. - The balloted templates repository requirements document will be reviewed.

• Link to project scope statement: Project 1058 in the HL7 Project Insight Searchable Database

Sponsor: FHIR Management Group (FMG)

Co-Sponsors:

• Attachments Work Group
• Clinical Interoperability Council Work Group
• Electronic Health Records Work Group
• Electronic Services and Tools Work Group
• FHIR Governance Board
• Modeling and Methodology Work Group
• Templates Work Group
• Vocabulary Work Group

Status

• If balloting, list ballot name/cycle/link
• If in DSTU, link to DSTU comments page
• If in development, link to in progress
• Some projects explicitly list objectives from scope statement and status for each

Issues/Hot Topics

• List issues or link to issues tracking repository (wiki pages or GForge)

Categorization

To include your Project Page in a category listing, just include a statement like [[Category:Active_Projects]]