Proposals due by : 4/3/20
To enter a track proposal, go to the ellipsis next to the Create button at the top of this page, click show more, and select the Track Proposal Template. Once you name your page, click publish in the bottom right corner. For more information on how to use a template to set up a new page click here.
The FHIR standards development process uses a philosophy of constant implementation to make sure that the standard is implementable in the real world. A key element of realizing this mindset is a FHIR Connectathon at each HL7 Working Group Meeting. The event is typically held on the Saturday and Sunday prior to the meeting and allows participants to test or develop software in an informal way. Test FHIR servers are available and some participants bring other servers along depending on the actors they are fulfilling.
The principles associated with connectathons can be found here.
Test servers are available (FHIR Test Servers ), but some participants may bring other servers along depending on the actors they are fulfilling.
Each track has a coordinating Track Lead. Please review Track Lead responsibilities.
BE PREPARED TO COMPLETE THE FOLLOWING:
Submitting WG/Project/Implementer Group
Justification and Objectives
What’s the purpose of hosting this connectathon track? What do you hope to achieve?
This track will use what version of FHIR.
Clinical input requested (if any)
Does your track have a need for input from the clinical community? If so, what are the needs?
(used to help guide seating arrangements and possibly drive track consolidation)
Proposed Track Lead
Name, email. Track leads must be registered users on http://chat.fhir.org
Who do you expect to be present? How many do you expect to attend?
A webinar will be hosted on date at time to share further participation information about this track.
Describe each type of system that could participate in the track
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Describe the different scenarios participating systems can engage in during the conenctathon. Each scenario should provide sufficient description that participants can appropriately construct their software in advance to prepare to interoperate during the connectathon.
Scenario Step 1 Name
Indicate any test scripts that will be used to help verify system behavior
Security and Privacy Considerations
Identify any expectations around security (e.g. will TLS, mutual-TLS, OAuth, etc. be required to participate