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

FHIR Connectathon 12

From HL7Wiki
Jump to navigation Jump to search


(This page is under construction and contains information that is still subject to update and correction.) This page describes the twelfth FHIR Connectathon that will be held on Saturday May.7 (9am - 5pm++) and the morning (9am - 12.30pm) of Sunday May 8, 2016 in Montreal, Quebec prior to the HL7 Working Group Meeting (see


The meeting will be held at the host hotel, LE CENTRE SHERATON MONTRÉAL HÔTEL, Montreal, Quebec .

Important notes:

  • Please note lunch is not included for Sunday with the Connectathon registration fee.


The following are the themes for the Connectathon. Each item links to the original proposal, with the coordinators name and email on the linked page. More details on each track appear in this document.

Unlike previous connectathon, all of the tracks described will be available. To assist with management on the day, participants are *strongly encouraged* to add their name to the participants tab of the Tracking Spreadsheet as soon as possible.

Connectathon Organization

The connectathon will be held over 2 days - the Saturday and Sunday prior to the HL7 Working Group Meeting.

Saturday is a full day, and is intended for participants to test and develop software in an informal way. Test servers will be available (actually, they are already - FHIR Test Servers ), but some participants may bring other servers along depending on the actors they are fulfilling. Sunday is the morning only, and has 2 parts:

  • the formal testing part
  • a mini-showcase where participants can demonstrate their work to the others

Each stream has a coordinator. The nominated coordinator's responsibilities:

  • In the lead up to the connectathon: track participants, respond to queries about scenarios, connect participants to each other
  • During the connectathon act as a test mediator / progress tracker
  • track emergent issues that should be fed back to the committees

Connectathon Planning Team


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

Space at the venue is limited, so please register as soon as possible. Preference will be given to those who are actually participating in the technical event, but observers are welcome if space permits.

For any queries, either contact a member of the planning team, or post your question in the FHIR list server

Registered Participants

see the Tracking Spreadsheet

Test servers

see the Tracking Spreadsheet

These are the STU3 servers we are aware of:

Connectathon track scenarios

This section lists the scenarios that are proposed for each track.

Note that this track - as with all tracks - will use the candidate 'STU3 candidate' version of FHIR as described here. If you've been to a connectathon before and done this track, then you may need to change your code, as there have been many important changes to the specification.

Track 1 C-CDA on FHIR

Track 2 CDS Enablement Services

Track 3 CDS Hooks

Track 4 Conditional Reference

Track 5 CQF on FHIR

Track 6 Data Access Framework

Track 7 Declarative Mapping

Track 8 FHIR Genomics

Track 9 Structured Data Capture

Track 10 Financial Mgt.

Track 11 Lab Orders

Track 12 the PATCH proposal

Track 13 Patient track

Track 14 Provider Directories & Scheduling

This track will attempt to extend on the track from connectathon 11, where we will expand the scope to the earlier stages of Service Provider Directory questioning, scheduling, and then the transition into Encounters.

If you are familiar with HPD, then we would like to encourage your participation.

We will have at least 1 large FHIR dataset available (from MiHN - Thanks Jeff(s))

Track 15 SMART-ca on FHIR

Track 16 Terminology Services

Track 17 Workflow

Servers (Supporting the messaging interoperability paradigm)

Should I come only for the Connectathon?

Coming for the connectathon alone has value - many implementers have attended just for the Saturday/Sunday and been happy. However, if you're already on-site, there's a lot of other FHIR-related activities to participate in that may further increase your return on investment (see the list of tutorials at the bottom of this page)

FHIR User Group

Subsequent to the actual connectathon (i.e. Sunday PM) the "Application Implementation and Design (AID)" HL7 User Group will meet to discuss FHIR implementation approaches and design patterns. You're invited to share your 'lessons learned' with others in the FHIR implementation community, or to listen to other FHIR implementers.

  • See AID Sunday PM Agenda for details.
  • Please contact Rene Spronk to get hold of a slot on the AID agenda - we do appreciate you sharing your ideas and experiences.

FHIR Tutorials

There are 4 tutorials scheduled through-out the week

  • Mon pm - Introduction to FHIR
  • Tue am - FHIR for Architects
  • Tue pm - FHIR for Specifiers
  • Wed am - Intro to FHIR Development

Detailed descriptions are available in the Event brochure

Working Group session

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. As well, there will be meetings of the FHIR Governance Board and 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.

The final agenda won't be determined until very close to the meeting (and will evolve somewhat throughout the course of the week), however you can take a look at the [[1]] from the May WGM to get a sense of the breadth of discussions that will be taking place. FHIR runs full bore from Monday to Friday (capping off with the clinical connectathon on Friday), so regardless of what days you're present, there will likely be something of interest.

Participating in the WGM is a good way to get a sense of the people involved in building the spec, to form relationships, to get more deeply involved in the FHIR community and to influence how the standard evolves.


Track x - TrackName

Results by track

how many completed each track - clients & servers

Key learnings

what changes to the spec resulted from the connectathon?

Changes next time

Does the track need to be repeated next time? (Remember, there are lots to do!) If so, what would be changed?

Overall comments

anything else - what worked, what didn't could the overall organization be changed

== =

Other References