Difference between revisions of "FHIR publishing requirements"
| Line 12: | Line 12: | ||
*Role of publishing | *Role of publishing | ||
| + | Publishing in conjunction with Tooling is looking to relieve the core FHIR team members of the responsibility of the routine publication and maintenance of the FHIR specification. In conjunction with appropriate resources from HQ it will be the responsibility of publishing and tooling to ensure publication of official FHIR specifications. It will also be their responsibility to ensure access to various versions of the FHIR specification as it progresses in development. | ||
*Role of HQ | *Role of HQ | ||
Revision as of 19:17, 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 a 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 to develop new resources and enhance existing ones.
- Role of publishing
Publishing in conjunction with Tooling is looking to relieve the core FHIR team members of the responsibility of the routine publication and maintenance of the FHIR specification. In conjunction with appropriate resources from HQ it will be the responsibility of publishing and tooling to ensure publication of official FHIR specifications. It will also be their responsibility to ensure access to various versions of the FHIR specification as it progresses in development.
- 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
