Page tree
Skip to end of metadata
Go to start of metadata

Track Lead to Do List:Connectathon Timeline
1Create Track Proposal using HL7 provided template on the ConnectathonXX Event Confluence Page6 weeks prior
2Identify Scenarios for track (part of IG development)8 weeks prior
3Identify Operations for track (part of IG development)8 weeks prior
4Identify Resource/Profiles for track (part of IG development)8 weeks prior
5Prepare test data for track and prepare TestScripts8 weeks prior
6Submit scenarios to AEGIS for test scripts (using AEGIS Test Script Requirements Template) or define your own TestScripts using the FHIR TestScript Resource6 weeks prior
7

Identify any changes/updates that need to be made to Reference Implementation if one already exists, and communicate to Reference Implementation Developer


8Identify test servers4 weeks prior
10

Update track proposals with clarifications/changes learned via scenario, test script, and data preparation


11Record a Track Orientation call with the stakeholders for each track
12

Bi-weekly/ weekly recurring calls with community leading up to Connectathon per track


13

Identify track participants to connect to Touchstone


14

Conduct Touchstone training or share recorded session

Follow up on participant account setup


15

Establish Zulip stream/communication channel


16

Review test scripts in Touchstone and provide feedback to AEGIS (new scenarios/test scripts may not be accommodated at this time)

2 weeks prior
17Publish test scripts2 weeks prior
18During -Connectathon
19Complete Connectathon Track Report from template on Connectathonxx Confluence PageDay 2 of Connectathon
20

Revise Implementation Guide/Scenarios based on Connectathon learnings

  • Enter JIRA tickets

21

Revise test scripts based on Connectathon learnings

2 weeks post Connectathon
22

Re-evaluate Test Scripts prior to next Connectathon

In next cycle


Connectathon Artifacts

  • No labels