This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR publishing requirements"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
''Current FHIR publication process'' | ''Current FHIR publication process'' | ||
| − | [[FHIR_Build_Process | current | + | [[FHIR_Build_Process | wiki page discussing how to build current specification]] |
| + | |||
| − | |||
[[File:publishing_FHIR_Spring2014.png|graphic of current fhir publication process]] | [[File:publishing_FHIR_Spring2014.png|graphic of current fhir publication process]] | ||
| Line 43: | Line 43: | ||
Other links | Other links | ||
| − | + | [[FHIR_Registry_Requirements| page describing FHIR registry requirements]] | |
| − | + | [[FHIR_web_hosting_requirements | page describing FHIR web hosting requirements]] | |
Revision as of 18:59, 15 March 2014
Page to capture issues regarding publishing the FHIR specification.
FHIR publishing process
- Role of FMG
- Role of publishing
- Role of HQ
Current FHIR publication process
wiki page discussing how to build current specification
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
page describing FHIR registry requirements
page describing FHIR web hosting requirements
