This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201901 IG Development and Exchange"
Jump to navigation
Jump to search
| Line 54: | Line 54: | ||
:Precondition: Use existing ig.json, StructureDefinition, template etc. files | :Precondition: Use existing ig.json, StructureDefinition, template etc. files | ||
:Success Criteria: Successfully publish an IG locally | :Success Criteria: Successfully publish an IG locally | ||
| + | |||
| + | ===Use a tool to create and run the R3 IG Publisher to publish an IG=== | ||
| + | :Action: Create an ImplementationGuide profile, create profile StructureDefinitions, and run the IG publisher using a tool (Trifolia on FHIR) | ||
| + | :Precondition: None | ||
| + | :Success Criteria: Successfully publish an IG in a tool | ||
| + | :Bonus point: Export IG files from tool into GitHub and run continuous integration build to publish IG on HL7 site | ||
===Use a tool to create and run the R4 IG Publisher to publish an IG=== | ===Use a tool to create and run the R4 IG Publisher to publish an IG=== | ||
Latest revision as of 18:24, 13 January 2019
IG Development and Exchange
Submitting WG/Project/Implementer Group
FHIR IG Developers
Justification
The development and exchange of FHIR IG specifications is an important and not widely understood aspect of FHIR profile development.
Track Lead
Sarah Gaunt
- Email: sarah.gaunt@lantanagroup.com
Expected participants
- Sarah Gaunt - Lantana Consulting Group
- Dave DeRoode - Lantana Consulting Group
- Sean McIlvenna - Lantana Consulting Group
- Richard Esmond - PenRad, Inc.
- Reinhard Egelkraut - HL7 Austria; CGM Clinical Austria
Roles
IG Publisher
The IG Publisher is the tool used to publish a FHIR IG
Scenarios
Manually run the R3 IG Publisher to publish an IG using already existing resources etc.
- Action: Run the IG publisher (cmd line or GUI)
- Precondition: Use existing ig.json, StructureDefinition, template etc. files
- Success Criteria: Successfully publish an IG locally
Manually run the R4 IG Publisher to publish an IG using already existing resources etc.
- Action: Run the IG publisher (cmd line or GUI)
- Precondition: Use existing ig.json, StructureDefinition, template etc. files
- Success Criteria: Successfully publish an IG locally
Use a tool to run the R3 IG Publisher to publish an IG using already existing resources etc.
- Action: Run the IG publisher using a tool (Trifolia on FHIR)
- Precondition: Use existing ig.json, StructureDefinition, template etc. files
- Success Criteria: Successfully publish an IG locally
Use a tool to run the R4 IG Publisher to publish an IG using already existing resources etc.
- Action: Run the IG publisher using a tool (Trifolia on FHIR)
- Precondition: Use existing ig.json, StructureDefinition, template etc. files
- Success Criteria: Successfully publish an IG locally
Use a tool to run the R4 IG Publisher to publish an IG
- Action: Run the IG publisher using a tool (Trifolia on FHIR)
- Precondition: Use existing ig.json, StructureDefinition, template etc. files
- Success Criteria: Successfully publish an IG locally
Use a tool to create and run the R3 IG Publisher to publish an IG
- Action: Create an ImplementationGuide profile, create profile StructureDefinitions, and run the IG publisher using a tool (Trifolia on FHIR)
- Precondition: None
- Success Criteria: Successfully publish an IG in a tool
- Bonus point: Export IG files from tool into GitHub and run continuous integration build to publish IG on HL7 site
Use a tool to create and run the R4 IG Publisher to publish an IG
- Action: Create an ImplementationGuide profile, create profile StructureDefinitions, and run the IG publisher using a tool (Trifolia on FHIR)
- Precondition: None
- Success Criteria: Successfully publish an IG in a tool
- Bonus point: Export IG files from tool into GitHub and run continuous integration build to publish IG on HL7 site
