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


The FHIR community is an open, welcoming community that respects all members.

The FHIR project is committed to providing a community that welcomes new members and provides a pathway to education about FHIR and full integration into the community.

Connectathons are a key part of our community engagement!

What is a Connectathon?

A Connectathon is an event that is centered on developing the HL7 FHIR Specification includin g resources, profiles and implementation guides. The purpose of a Connectathon is to prove that the specification is complete and facilitate FHIR implementation guide maturity.

The FHIR Connectathon Approach

The FHIR Community Vision is to enable Health Interoperability through the use of FHIR and use that to deliver improvements in healthcare provision throughout the world. HL7 FHIR Connectathon participants come together several times per year to work alongside vendor peers, healthcare providers and administrators, and the individuals and organizations that actually wrote the HL7 FHIR specification. Test tools like and others are made available for developers to rapidly learn to implement the standard and validate their conformance to the specification and mature implementation guides. The FHIR Community Vision is highly reliant on the building a specification for healthcare APIs that is highly reusable. The fact that an implementation guide can be re-used at many deployments drives down the time and costs and drives up quality of health data for all.

FHIR Resources and implementation guides that are early in their maturity are more open for debate. When multiple stakeholders come together and find that their code does not interoperate, either one of them did not interpret the specification or IG correctly or it could mean that the FHIR documentation was not complete enough. Thus the FHIR specification is often improved during Connectathon and depends on transparency in the work that happens during these events.

What happens at connectathon stays at connectathon!

Connectathons are a safe place for everyone to fail forward. Connectathon testing with peer organizations is good for developers and for the HL7 FHIR standard. Connectathons offer developers a better place to fail than at a customer site. Customers expect to use products, not participate in debugging. By allowing product vendors to practice interoperability in a Connectathon setting, vendors can come to resolution and inform the specification evolution so that true interoperability can be enabled.

Out of Cycle HL7 Connectathon Criteria for Approval by the FHIR Management Group

  • needs to be sponsored by HL7 International or an affiliate, and approved by FMG.

  • Must submit names of the coordinator and technical lead for the connectathon

  • Need to have at least one person familiar with FHIR

  • Persons should have participated in a prior connectathon, having an implementation, etc…

  • Remains a judgment call from FMG for now

  • Identify what version of the spec on which they will draw,

  • Need to assert if they have requirements for a frozen version of the spec and what other requirements they have.

  • Describe the scenarios to execute

  • Comments from experience will be DSTU comments.

How to Particpate in a Connectathon

As a Track Lead:

Anyone is welcome to submit a Track Proposal for an HL7 FHIR Connectathon. HL7 International hosts three main Connectathons per year, typically held the weekend before the Work Group Meeting. Track Proposals are generally accepted from 12 weeks prior to 6 weeks prior to the Connectathon and are reviewed by the FHIR Management Group before the event. To find the track proposal deadline and the associated track template, review and watch the Connectathon ## Event Page for the Track Proposal Template and specific event details including Track Lead Orientation.

To Get Started Review the following: 

Track Lead Resources

Track Lead Responsibilities

Connectathon Track Process

As a Participant:

If you are interested in attending a Connectathon you can register any time before the event. Registration typically opens when the associated Work Group Meeting Registration goes live. You can always find information about registration and track participation on the specific Connectathon ## Event Page below:

Location: Atlanta Marriott Marquis hotel (same as the HL7 Working Group Meeting occurring September 14-20)

Date of Training Workshops: September 11-13 2019

Training will occur 1-5pm on Wednesday and 9-5pm on Thursday and Friday

The FHIR Implementation Guide (IG) Workshop is for a series of three restricted, limited space workshops targeting IG publishers and new ballot reviewers.  All attendees will be nominated in advance by the FHIR Core team.  

The FHIR Core Team hasn’t identified a list of invitees yet, but if you’d like to suggest names to be included to the waiting list, just let us know and we’ll inform you when more details are available.

Entries below should select the appropriate workshops desired:

Workshop 1: Implementation Guide Creation (Wednesday afternoon and all day Thursday)
Workshop 2: Terminology considerations (Friday morning)
Workshop 3:  Implementation Guide Ballot Review Best Practices (Friday afternoon)

  • Indicates application email received by Wayne Kubick
NameOrganizationEmailWorkshop 1:
IG Creation

Workshop 2: Terminology Considerations

Workshop 3:
IG Ballot Review Best Practices
Linda Michaelson Optumlinda.michaelsen@optum.comXX
Email from Linda (to Wayne Kubick): 

Yes, please put me on this list.  I am copying in my Da Vinci team to promote me for the workshop – I am a co-lead on several workgroups and would like to be able to at least help in this process. From a scheduling perspective, when do you think it will be held? Linda

Lisa Nelson*MaxMDlnelson@max.mdXXXRecommended by Wayne. Lisa has a candidate who is willing to learn and offer significant in kind contributions for creation and review.  
Cheng Lui*MaxMD
XXXRecommended by Lisa
Benjamin Flessner

Recommended by Sean McIlvenna
George DixonAllScripts

XRecommended by Sarah Gaunt
Emma JonesAllScripts

XRecommended by Sarah Gaunt
John Hatem

XRecommended by Melva Peters
Andrew StatlerCernerAndrew.Statler@cerner.comX

Recommended by Sean McIlvenna
Reuben Daniels
Recommended by Sarah Gaunt
Micheal Lawley
Recommended by Sarah Gaunt
Smita HastackSamvit

XRecommended by Lloyd McKenzie
Robinette Renner

Recommended by Lloyd McKenzie
Rik Smithies
XRecommended by Lloyd McKenzie
Linda MichaelsenOptumlinda.michaelsen@optum.comX
XRecommended by Bryn Rhodes (Duplicate of Row 1)
Patrick WernerMOLIT Institutpw@molit.euXXX
José Costa Teixeira XXX
John Moehrke* XXXRecommended by José 

CDISC has a couple of people they'd like to send - need named individuals; and CDISC hasn't been participating in IG creation or ballot reviews.
Oliver Egger*ahdis / hl7 swtzerland

Christine (Christi) Denney
Christi_d@lilly.comXXXRecommended by BR&R and Trisha Simpson.  Author of 1 IG from BR&R for Sept 2019.  Will be assisting with IG development for Research.
Craig NewmanAltarumCraig.Newman@altarum.orgXXXIs working on Reference implementations and would like to attend (Recommended by Dave Pyke)
Becky AngelesCarradorabecky.angeles@carradora.comXXXWas the originator of the eLTSS project and would like to attend (Recommended by Dave Pyke)
Sheridan CookGevityscook@gevityinc.comXXXFormerly w/ MiHIN, lots of experience doing IG-type work w/ v2, has now done v3 publisher work with FHIR (Recommended by Lloyd McKenzie)
Joee GarciaGevity

XDeveloper/analyst who's been helping Lloyd with IG creation & review (Recommended by Lloyd McKenzie)
John BenderONCjohn.bender@hhs.govXXXRecommended by Matt Rahn and Wayne Kubick.
Paul KnappKnapp
Jamie ParkerCaradorrajamie.parker@carradora.comX
XRecommended by Dave Pyke
Scott Gordon FDAGideon.Gordon@fda.hhs.govXXXRequest to Wayne
Keith Boone*

Kathleen Connor*VA/Book Zurman Inc.kathleen_connor@comcast.netxxxRequest sent to Wayne. Already have worked on FHIR build for FM/Security but need refresher on build especially for work on FHIR DS4P IG. starting in Sept. But may not need if 101.  Wayne indicates that there's no space until Feb. Not going to AU.  Maybe in May 2020 if needed.
Ben McAlister*Cernerben.mcalister@cerner.comxxx
Corey Smith*

Yan Heras*

AbdulMalik Shakir*

xxApproved and confirmed by Wayne
May TerryMITREmayT@mitre.orgx
xApproved and confirmed by Wayne.

The following checklist can be used as a template for performing an Implementation Guide review – it guides the overall process for the review.

This slide deck gives details for reviewing FHIR IGs: 2019-09 FHIR IG Review.pptx

To use this checklist, copy the content to a Word Document for each IG Review.

Step #1: Orientation / Conceptual

  • Check stated Realm
  • Check kind of IG – what expectations arise?
  • Summarise what this IG does (is it clear from stated scope?)
  • Check stated dependencies – if stated
  • Check for missing appropriate dependencies 

Step #2: Orientation / Technical

  • Read note to balloters (if present)
  • Check history notes
  • Check qa.html

Step #3: Orientation / Approach

  • Check kinds of exchanges
  • APIs
  • Document
  • Messaging (o Check messaging protocol)
  • Make list of kinds of information exchanged
  • Check consistent with realm core expectations
  • Make list of actors described in system
  • Characterise as Producer | Consumer | Repository

Step #4: Capability Statement

  • Check resources exposed. For each resource
  • Check Interactions
  • Check Search Parameters
  • Modifiers 
  • Chaining
  • Combinations
  • Conformance expectations clear
  • Check System Profile
  • Check Use case Profiles
  • Check Global Profiles

Step #5: Profiles

Check resources/profiles exposed. For each resource

  • Check Text Summary – human to human
  • Check Differential as summary (consistent with text summary?)
  • Check what other related profiles exist in other IGs
  • For each element in the differential:
    • Check definitions – changed? Needs to be changed?
    • Check any mappings added
    • Check cardinality
    • Check must support (and check it’s meaning is defined)
    • Check Terminology Binding
  • Any orphan profiles?

Step #6: Extensions

Any extensions? For each extension:

  • Check context of use
  • check related extensions
  • For each element in the differential:
  • (as above)

Step #7: Value Sets / Code Systems

  • Check Copyright (externally sourced content)
  • Check Versioning
  • For code systems: something that needed to be defined?

Step #8: Specific Requirements

  • For each:
    • Defined / described?
    • Requirements described?
    • Do you agree?
  • Security
  • Error Handling
    • Specifying correct behaviour for operational failures
    • Mechanisms for handling erroneous data
  • Audit / Provenance
  • Consent / Privacy
  • Test Cases / Conformance testing support
  • Safety Issues (check)

Orphaned pages in this Confluence Space:

Log of work on migration of FHIR space

JoshJoshua Procious added a comment - 2019-10-29 10:04

The reference to the FHIR Governance Board on this page: is to the wiki as it hasn't been migrated to Confluence.

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-29 10:06

Two pages in the Confluence FHIR space "Connectathon 13" and "Connectathon 14" were deleted and NOT migrated due to them being included in the archive page listing "Previous Connectathons"

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-30 11:28 - edited

I have create the page FHIR Build Process as it was not in Confluence and seemed to be the primary link in multiple documents.
I created the page FHIR Profile Authoring and migrated from the referenced pages on the wiki.
I have created the page FHIR Profile and IG Balloting from the referenced pages on the wiki.
I have created the page FHIR Implementation Guide Authoring from the referenced pages on the wiki.

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-30 12:06 - edited

What is the guidance for how FHIR wants to handle the current Resource proposals on the WIKI?
Page on confluence here:

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-30 03:51 - edited

Created page FHIR Package cache per requested migrated pages table:

Create page FHIR IG PackageList doco per requested migrated pages table:

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-31 09:53

FHIR Profile Considerations page on wiki is blank
This link was intentionally left out of the FHIR Profile Proposal Template.

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-31 10:33

FHIR IG Proposal template was overwritten in the wiki with data so no instructions were present.

The respective template in Confluence was populated with standard fields and general instructions but no guiding instructions per field.

Permalink Edit Delete
JoshJoshua Procious added a comment - 2019-10-31 01:03

I have create the IG Proposals and Profile Proposals pages in confluence.

Combined with the Resource proposals pages, they jointly use templates I've created in Confluence based on wiki templates.
Converting the blue text to cloaks in confluence and then listeners by label.

Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

FHIR Bulk Data Access Implementation Guide

2. Standards Material/Document

Errata STU Extension

3. Date of Request

Oct 12, 2020

4. Use Period

5. Reason for extension, timeline, and actions

Implementation activity still occurring, planning ballot in 2021.

6. Original Publication Date

Aug 22, 2019

7. End date of the current STU period

Aug 21, 2020

8. Length of the requested extension

18 months

9. Review Process

10. HL7 Work Group making this request and date

FHIR-I approved publication on 7/13 and additional publication error triggered secondary approval on 10/12 (

10a. Requesting WG Date

Oct 12, 2020

11. URL of approval minutes

12. HL7 Product Management Group

12a. Management Group Date of Approval

13. URL of approval minutes

14. Is the artifact ready for final publication?


15. If not ready, please describe remaining steps.

16. Tool name used to produce the machine processable artifacts in the IG

FHIR IG Publisher

17. The name of the “IG artifact” within the context of the above mentioned tool.

18. Balloted Name of the standard for which request is being made

19. Requested name for published standard

20. If CMET, list IDs balloted

21. Project Insight Number


22. Document Realm


23. Ballot cycle in which the document was successfully balloted

24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

25. Affirmative

26. Negative

27. Abstentions

28. Not Returned

29. Total in ballot pool

30. Date on which final document/standards material was supplied to HQ

31. URL of publication material/ SVN repository

32. Publishing Facilitator

Dan Gottlieb

33. Special Publication Instructions

34. URL of ballot reconciliation document

35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop?

36. Substantive Changes Since Last Ballot?

37. Product Brief Reviewed By

FHIR-I (no updates made to product brief)

38. Date Product Brief Reviewed

39. Has the Product Brief changed?


Product Brief

Product Brief

40. Family

41. Section

42. Topic

43. Please Describe the Topic

44. Product Type

Implementation Guide

45. Parent standard

46. Parent Standard Status


47. Update/replace standard

48. Common name/search keyword

49. Description



These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

51. Vendors

52. Providers

53. Benefits

54. Implementations/Case Studies

55. Development Background

The bulk of the content for this page has yet to be migrated from

  • No labels