Difference between revisions of "FHIR publishing requirements"
| Line 6: | Line 6: | ||
*Role of FMG | *Role of FMG | ||
| − | + | As of Spring 2014, FMG has overall responsibility of ensuring that the FHIR specification is developed | |
and published in smooth and timely fashion. That new resources are being developed properly and reviewed | and published in smooth and timely fashion. That new resources are being developed properly and reviewed | ||
appropriately and that existing resources are updated as necessary during the current (as 2014) draft standard for trial use (DSTU) stage of FHIR's evolution. It also coordinates with appropriate subject matter work groups | appropriately and that existing resources are updated as necessary during the current (as 2014) draft standard for trial use (DSTU) stage of FHIR's evolution. It also coordinates with appropriate subject matter work groups | ||
Revision as of 19:10, 15 March 2014
Page to capture issues regarding publishing the FHIR specification.
FHIR publishing process
- Role of FMG
As of Spring 2014, FMG has overall responsibility of ensuring that the FHIR specification is developed and published in smooth and timely fashion. That new resources are being developed properly and reviewed appropriately and that existing resources are updated as necessary during the current (as 2014) draft standard for trial use (DSTU) stage of FHIR's evolution. It also coordinates with appropriate subject matter work groups
- Role of publishing
- Role of HQ
Current FHIR publication process
How to build the current specification for publication
Document the current process
The current process is monolithic
Involves batch files and java
---
Suggestions for long term FHIR publication process
Depends on target build (ballot, development, or connectathon)
Would it be useful to modularize, to support incremental builds?
Is the current process able to be modularized?
Other links
