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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

HL7 FHIR CONNECTATHON 25

WILL BE VIRTUAL!

****UNDER CONSTRUCTION*****

Kick Off Monday, September 14th at 4:00 PM

View the full schedule and links here.


The contact for this event is Sandy Vance who can be reached at sandy.vance@aegis.net or +1.614.273.5916

Announcements:


7/1/20 Please submit your track proposal prior to July 21, 2020 so that we have plenty of time for pre-connectathon planning calls!

Helpful Links:

HL7 Pre Connectathon Survey

Con Man App

Connectathon Manager Orientation Video

Click HERE to Register! 

Track Leads:

Plan a Track! by clicking here. Track Proposals are due July 21, 2020.

Track Lead information sessions will be held on Thursday, July 23rd and Thursday, August 20th.

Participate!

If you or your company are interested in participating in the connectathon, please do the following:

  1. Read the Connectathon version of the FHIR Specification and the FHIR FHIR home page if you haven't already done so, to become familiar with the concepts.
  2. Read the Track descriptions found in the drop down list on the left under Tracks for Connectathon 24.
  3. Complete the HL7 Pre Connectathon Survey (coming soon) for each member of your team to indicate their primary track.

Contact Sandy Vance at sandy.vance@aegis.net if you have questions.

Connectathon Planning Team

Work Group Meetings

HL7 WGMs are where a lot of the development work on FHIR happens. Numerous work groups will be considering FHIR change proposals, working on FHIR profiles and resources, and debating other aspects of FHIR implementation. There will also be meetings of the FHIR Management Group discussing policies relating to FHIR. There are often ad-hoc meetings at breakfast, lunch and after-hours to discuss items of interest such as tooling, new domains, particular technical issues, etc.

You can take a look at the HL7 Confluence Pages related to specific work groups to get a sense of the breadth of discussions that will be taking place.

Participating in the WGM is a good way to get involved in the FHIR Community, form relationships and influence how the standard evolves.


Proposals due by : July 21, 2020

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.

Tracks: 



Track Lead Resources

Track Orientation

Please plan to host a track orientation 30-60 minute webinar. If you would like help with scheduling, recording, and posting the Go To Meeting for this orientation contact  sandy.vance@aegis.net with your preferred time. Otherwise - be sure to record and post it to your track page in confluence.]

Outcomes Reporting

Each track lead will be expected to participate in developing the track report out for the participants of their track.

Guidelines for report out:

  • 1 paragraph summary: what was the track trying to achieve
  • 1 list of participants (with logos if you have time and energy)
  • 1 paragraph: notable achievements
  • 1-2 screenshots if relevant and interesting and/or links to further information about implementations/achievements
  • 1 paragraph: discovered issues / questions (if there are any)
  • 1 paragraph: now what?



Recently Updated

  • No labels