Difference between revisions of "201901 IG Development and Exchange"

From HL7Wiki
Jump to navigation Jump to search
Line 33: Line 33:
 
==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
  
 +
===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
 +
 +
===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
 +
 +
===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
 +
 +
===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
  
 
===Scenario Step 1 Name===
 
===Scenario Step 1 Name===

Revision as of 22:51, 12 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.

Related tracks

Proposed 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

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 Name

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

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

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

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

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

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)

Security and Privacy Considerations