This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201901 IG Development and Exchange"

From HL7Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 10: Line 10:
 
The development and exchange of FHIR IG specifications is an important and not widely understood aspect of FHIR profile development.
 
The development and exchange of FHIR IG specifications is an important and not widely understood aspect of FHIR profile development.
  
−
==Related tracks==
+
==Track Lead==
−
 
 
−
 
 
−
==Proposed Track Lead==
 
 
Sarah Gaunt
 
Sarah Gaunt
 
:Email: sarah.gaunt@lantanagroup.com
 
:Email: sarah.gaunt@lantanagroup.com
Line 19: Line 16:
 
==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==
−
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
 
<!-- 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 -->
−
===Role 1 Name===
+
===IG Publisher===
−
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
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
  
−
===Scenario Step 1 Name===
+
===Use a tool to create and run the R3 IG Publisher to publish an IG===
−
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Create an ImplementationGuide profile, create profile StructureDefinitions, and run the IG publisher using a tool (Trifolia on FHIR)
−
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: None
−
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: Successfully publish an IG in a tool
−
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: Export IG files from tool into GitHub and run continuous integration build to publish IG on HL7 site
  
−
<!-- Provide a description of each task -->
+
===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

TestScript(s)

Security and Privacy Considerations

Retrieved from "https://wiki.hl7.org/w/index.php?title=201901_IG_Development_and_Exchange&oldid=164582"