This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "FHIR Repository Process"

From HL7Wiki
Jump to navigation Jump to search
Line 9: Line 9:
 
==Project Information==
 
==Project Information==
  
−
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1058 Project 1058 - FHIR Repository Process and Requirements, Phase 1 in the HL7 Project Insight Searchable Database]
+
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1058 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
 
*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
 
*Name the project facilitators, (add contact info if desired)
 
*Name the project facilitators, (add contact info if desired)

Revision as of 17:39, 7 September 2016

Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information

Return to Main Page - include link to return to Work Group main page or wiki page who sponsored the project

This template was developed using examples from other project pagess: Annotated ECG, BRIDG as DAM, Canonical Pedigree, DCM for Dev, EHR Interop, EHR RM-ES, Oncology EHR, RPS, Templates registry, SPL, VMR

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
  • Name the project facilitators, (add contact info if desired)
  • Link to project scope statement: Project 1058 in the HL7 Project Insight Searchable Database

Meeting Information

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


Project Documents


Categorization

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

Retrieved from "https://wiki.hl7.org/w/index.php?title=FHIR_Repository_Process&oldid=125318"