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

Difference between revisions of "FHIR Connectathon 15"

From HL7Wiki
Jump to navigation Jump to search
Line 19: Line 19:
* [ Workflow Track]
* [ Workflow Track]
* [ CDS Hooks]
* [ CDS Hooks]
* [ Clinical Reasoning]
* [ CQF in FHIR]
* [ DAF]
* [ Device Integration]
* [ FHIR Genomics]
* [ FHIR Genomics]
* [ Payer Extract]
* [ Provider Directories and Scheduling]
* [ Structured Data Capture]
* [ Attachments]
* [ C-CDA on FHIR]
* [ Financial Management]
* [ Patch]
* [ Patient track (recommended for beginners)]
* [ Terminology]
(Track leads to add links)
(Track leads to add links)

Revision as of 15:58, 21 March 2017


(This page is under construction and contains information that is still subject to update and correction.) This page describes the Fifteenth FHIR Connectathon that will be held on Saturday March 6 (9am - 5pm++) and the morning (9am - 12.30pm) of Sunday March 7, 2017 in Madrid, Spain prior to the May HL7 Working Group Meeting.


The meeting will be held at the host hotel, Madrid Marriott Auditorium Hotel & Conference Center

Important notes:

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


The following are the tracks for the Connectathon. Each item links to the original proposal, with the coordinators name and email on the linked page. View the link for details.

(Track leads to add links)

Connectathon Organization

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

It will be based on the STU3 verion of the spec - currently located at [1] but will move to [2] when finalized

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 the track leads can demonstrate representative 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.

  • Read the Connectathon version of the FHIR Specification and the FHIR wiki if you haven't already done so, to become familiar with the concepts.
  • Read the scenario descriptions below.
  • Register to attend the WGM, and make sure to select the Connectathon option when you do
  • Optionally (but highly recommended) fill in the tracks and roles in which you are intending to participate in the spreadsheet (Note: link to be supplied)

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

(Note: link to be supplied)

Test servers

(Note: link to be supplied)

These are the STU3 servers we are aware of:

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 (link TBD) for details.
  • Please contact Andy Stechishin to get hold of a slot on the AID agenda - we do appreciate you sharing your ideas and experiences.

FHIR Tutorials

There are 5 FHIR tutorials scheduled through-out the week

  • Mon pm - Introduction to FHIR (spanish)
  • Mon pm - FHIR for clinicians (english) - Includes an introduction. Bring your laptop as there will be exercises!
  • Tue am - FHIR for Architects (english)
  • Tue pm - FHIR for Specifiers (english)
  • Wed am - FHIR for Developers (english)

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 [[3]] from the May 2014 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.

Outcomes (for co-ordinators)

The following outcomes will be recorded for each track

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