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
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
|||
(6 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
[[Category:201901_FHIR_Connectathon_Track_Proposals|Jan2019 Proposals]] | [[Category:201901_FHIR_Connectathon_Track_Proposals|Jan2019 Proposals]] | ||
__NOTOC__ | __NOTOC__ | ||
− | + | IG Development and Exchange | |
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
− | + | FHIR IG Developers | |
==Justification== | ==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== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
+ | * 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== | ==Roles== | ||
− | |||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | ||
− | === | + | ===IG Publisher=== |
− | + | The IG Publisher is the tool used to publish a FHIR IG | |
+ | |||
==Scenarios== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
+ | ===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: | + | :Action: Create an ImplementationGuide profile, create profile StructureDefinitions, and run the IG publisher using a tool (Trifolia on FHIR) |
− | :Precondition: | + | :Precondition: None |
− | :Success Criteria: | + | :Success Criteria: Successfully publish an IG in a tool |
− | :Bonus point: | + | :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 | ||
==TestScript(s)== | ==TestScript(s)== |
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