Balloting and Publication Process The FHIR publication process applies to both publication of the base standard (e..g FHIR STU 3.0 and any balloted FHIR implementation guides. The goal is to create a static view of all FHIR artifacts associated with the ballot for review and comment. The process requires that the specific artifacts stay static (other than changes applied during the comment reconciliation and disposition process) during the entire ballot process. This needs to be done without impacting the ability to continue to evolve the base standard create new implementation guides. Prior to ballot, the system will provide for: Selection and creation of a static version of all artifact that will be balloted together (“ballot contents”) Publishing the ballot contents so HL7 member can review and provide ballot comments during the comment portion of the process. Each item in the ballot contents shall have a unique designation to permit specific comments that clearly identify the particular FHIR artifact and the individual that is the subject of the comment. “element” As part of the comment and comment resolution process Each comment shall be attributed to the comment author and shall be associated, here possible with unique target of the comment. The system shall automatically allow for aggregation of comments by: Author Artifact Type of comment Categories provided for selection as part of the comment process Status (provisional, submitted, in process, withdrawn, disposed, applied, …) The system shall support recording dispositions and pointing directly to their application in the specific FHIR artifacts where possible The authoring system shall be used to apply the updates to the affected FHIR artifacts. (This includes the ability to validate and test as frequently as required) The system shall provide the ability for the comment author (or any other authorized user else) to review the disposition of their / specific comments and trance the result directly to the modified artifact (including documentation).
Balloting and Publication Process The FHIR publication process applies to both publication of the base standard (e..g FHIR STU 3.0 and any balloted FHIR implementation guides. The goal is to create a static view of all FHIR artifacts associated with the ballot for review and comment. The process requires that the specific artifacts stay static (other than changes applied during the comment reconciliation and disposition process) during the entire ballot process. This needs to be done without impacting the ability to continue to evolve the base standard create new implementation guides. Prior to ballot, the system will provide for: Selection and creation of a static version of all artifact that will be balloted together (“ballot contents”) Publishing the ballot contents so HL7 member can review and provide ballot comments during the comment portion of the process. Each item in the ballot contents shall have a unique designation to permit specific comments that clearly identify the particular FHIR artifact and the individual “element” that is the subject of the comment. As part of the comment and comment resolution process Each comment shall be attributed to the comment author and shall be associated, here possible with unique target of the comment. The system shall automatically allow for aggregation of comments by: Author Artifact Type of comment Categories provided for selection as part of the comment process Status (provisional, submitted, in process, withdrawn, disposed, applied, …) The system shall support recording dispositions and pointing directly to their application in the specific FHIR artifacts where possible The authoring system shall be used to apply the updates to the affected FHIR artifacts. (This includes the ability to validate and test as frequently as required) The system shall provide the ability for the comment author (or any other authorized user else) to review the disposition of their / specific comments and trance the result directly to the modified artifact (including documentation).
HL7_International_Repository_Governance_Process_and_Requirements_August_2017_V4.02.docx