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


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

The HL7 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?

An HL7 FHIR Connectathon is an event that is centered on developing the HL7 FHIR Specification including 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 HL7 FHIR Connectathon Approach

The HL7 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 HL7 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 FHIR 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.

Participate as a Track Lead:

Anyone is welcome to submit a Track Proposal for an HL7 FHIR Connectathon. HL7 International hosts three main Connectathons annually typically held the weekend prior to the Working Group Meeting; however, the virtual format has slightly altered that pattern. Track Proposals are generally accepted from 12 weeks prior to 6 weeks prior to the Connectathon and are reviewed by the FHIR Management Group. 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

Join the Connectathon as a Participant to test the HL7 FHIR Specification or an Implementation Guide:

Interested in attending a Connectathon? Be sure to register prior to the event! Registration typically opens about 12 weeks prior to the event, and more information about registration and track participation is available 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

  • Is the purpose of the IG clearly explained?
  • Have roles and use cases been defined?
  • Does the IG have the appropriate dependencies? Is it reinventing existing content?
  • Do the artifacts fit appropriately into the defined scope? 
  • Check stated Realm
  • Check kind of IG – what expectations arise?

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
  • Characterize 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 - elements should be 0..0 only if the inclusion of that element would be an error
    • Check must support (and check it’s meaning is defined)
    • Check Terminology Binding – extensible and preferred binding pose challenges for searching
  • For each sliced element (including extensions), assure the generic short and definition have been replaced with real definitions
  • Any orphan profiles?

Step #6: Extensions

Any extensions? For each extension:

  • Is there a standard extension that could be used?
  • Has the context of use been set (associating the extension with the type of resource it can be used with)
  • If a simple extension, has the data type of the value been appropriately constrained? Has the extension's extension been set to 0..0?
  • Has the short and definition of the extension been set? (These are appear in the profile, so they are important)

Step #7: Value Sets / Code Systems

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

Step #8: Examples

  • Check that all examples validate against profiles
  • Check that examples have all information required for the use case
  • Where there are slices, examples should populate every slice. Check that the QA report to see if the slices were uniquely distinguishable.

Step #9: 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.


Initial Review


SpaceSectionPageLocation in New SpaceNeeds Review (Y/N)Recommendations from Initial Review

Reviewed with FMG


Review comments from FMGStatus of changesFMG Member(s) to help with review and updateReview Notes
NWas not moved over from wiki, however seems to be completely outdated.

NWas not moved over from wiki, but page is only a link to the HL7 confluence calendar page.

NWas not moved over from wiki but is essentially a blank page

YWas not moved over from wiki. Unsure if content is current

YHas links to project information from the FHIR Repository Process Project. Unsure if needed on confluence

YSeems to be out of date. Mostly asking questions for things that appear to have been answered already.

YUnsure whether this should be brought over/updated or not

YUnsure whether this should be brought over/updated or not

YDoes not appear to be represented in confluence. If it is not, recommend adding it

2021-09-15ConfluenceAdministrationKnown Issues with the published FHIR Specifications
YSeems unnecessary with JIRA. Recommend removal.

2021-09-15ConfluenceAdministrationGovernance Process
YOutdated information. Either needs update or removal

2021-09-15ConfluenceAdministrationFHIR Trademark PolicyQuick LinksYShould be reviewed to make sure information is current. I believe it is.

2021-09-15ConfluenceAdministrationFHIR Product Director PageGovernanceYAssuming this is the only place to find this information, it might need an update from Grahame but otherwise is fine.

2021-09-15ConfluenceAdministrationFHIR Product Director Position Description
YWith the above page, this seems redundant. Additionally, it reads more like a job posting.

2021-09-15ConfluenceAdministrationFHIR Management GroupGovernance - CommitteesYOnly links to the actual FMG page and back to the wiki. Should be removed

2021-09-15ConfluenceAdministrationDSTU2 Ballot to Final breaking changes
YUnless there is some important reason for these to remain, they seem out of place.

2021-09-15ConfluenceAdministrationDSTU2 Technical Correction 1 Tasks
YSee above

2021-09-27ConfluenceDesignersResource Proposals
Ythe Resource Proposals by Category section seems to list several labels that aren't related to Resource Proposals

2021-09-27ConfluenceDesignersResource Types
YCould potentially be restructured so that every listed Resource Type could be a subpage and discussion around the Resource Type could be in the comments. Unlikely to be worth the effort though.

2021-09-27ConfluenceDesignersResource Authoring

2021-09-27ConfluenceDesignersFHIR Spreadsheet Authoring

2021-09-29ConfluenceDesignersGuide to Designing Resources
YReview if all necessary content has been moved over from If it has, remove the Todo text.

2021-09-29ConfluenceDesignersManaging Overlap Between Resources
YThis section only has a background, and a note to migrate more content. That is also all the content on the wiki page.

2021-09-29ConfluenceDesignersResource Considerations

2021-09-29ConfluenceDesignersFHIR Build Process

2021-09-29ConfluenceDesignersHL7 Process for Publishing a FHIR IG

2021-09-29ConfluenceDesignersFHIR Implementation Guide Process Flow

2021-09-29ConfluenceDesignersIG Proposals
YThe IG Proposals by Category section seems to list several labels that aren't related to IG proposals

2021-09-29ConfluenceDesignersProfile Proposals
YThe Profile Proposals by Category section seems to list several labels that aren't related to Profile proposals.

2021-09-29ConfluenceDesignersFHIR Profile and IG Balloting

2021-09-29ConfluenceDesignersFHIR Implementation Guides - Planned Balloting/Publishing

2021-09-29ConfluenceDesignersFHIR Implementation Guide Publishing Requirements

2021-09-29ConfluenceDesignersHL7 QA process for FHIR IGs
YI believe this is up to date, but I'm not certain.

2021-09-29ConfluenceDesignersIG Templates
YDoes this need to be its own page? Or could it be part of another page?

2021-09-29ConfluenceDesignersImplementation Guide Parameters

2021-09-29ConfluenceDesignersIG Publisher Documentation

2021-09-29ConfluenceDesignersFHIR Liquid Profile

2021-09-29ConfluenceDesignersFHIR IG PackageList doco

2021-09-29ConfluenceDesignersNPM Package Specification

2021-09-29ConfluenceDesignersFHIR Package Cache

2021-09-29ConfluenceDesignersFHIR Profile Authoring
YOut of date information.

2021-09-29ConfluenceDesignersFHIR Spreadsheet Profile Authoring
YIs this out of date too?

2021-09-29ConfluenceDesignersFHIR Tooling Ecosystem

2021-09-29ConfluenceDesignersFHIR Tools Registry
YAre there any more tools to add to this list?

2021-09-29ConfluenceDesignersProfile Tooling

2021-09-29ConfluenceDesignersGIT Conflict Resolution Documentation

2021-09-29ConfluenceDesignersSMART Web Messaging

2021-09-29ConfluenceDesignersFHIR Package Registry User Documentation
YThis page should be completed and corrected if necessary and then the warning that it is incomplete can be removed.

2021-09-29ConfluenceDesignersFHIR IG QA Monitoring

2021-09-29ConfluenceDesignersFHIR Core FMM Support

2021-09-29ConfluenceDesignersProcess for Publishing a FHIR Implementation Guide (for non-HL7 IGs)
N Documentation
NGrahame created this page on the 24th. So it's definitely up to date. (wink)

NDoesn't currently need an update but probably will in the future.

ConfluenceImplementersChange Requests
YThis page seems redundant with the main page on submitting specification feedback (Specification Feedback) Could just be replaced by a link to that page from the main FHIR space. Community Expectations

ConfluenceImplementersClinicians on FHIR
YJust links to the PC Clinicians on FHIR page. Should just be a link to that page from the main FHIR space.

ConfluenceImplementersConformance QA Criteria

ConfluenceImplementersDigital Signatures
YOld content (claims to be around coming to a resolution for a gforge tracker

ConfluenceImplementersEndpoint directory implementations

ConfluenceImplementersFHIR Cheatsheets

ConfluenceImplementersFHIR Code of Conduct

3 options:

  1. Reproduce the HL7 code of conduct on the page itself
  2. Remove the page and link to the HL7 code of conduct from the main FHIR space.
  3. Leave the page as is.

ConfluenceImplementersFHIR Community Process

ConfluenceImplementersFHIR Intellectual Property Rules

ConfluenceImplementersFHIR Maturity Model

ConfluenceImplementersFHIR Rules for Asking Questions
YSuggest changing page name to "FHIR Guidelines for Asking Questions"

ConfluenceImplementersGetting Involved
YNeeds text for the two "... to do ..." sections

ConfluenceImplementersIGs from other Organizations
YLast updated in 2019. Either needs updating or scrapping.

ConfluenceImplementersImplementer Support
YLast updated in 2019. Some links to wiki content.  Seems to have overlap with other pages, especially FHIR Rules for Asking Questions

ConfluenceImplementersInterversion Compatibility
YAccording to the comments in 2019 this page is linked to in the FHIR spec. If that is still the case then either the page and the reference should be dropped or the page should be updated with whatever appropriate information is required.

ConfluenceImplementersMailing List Instructions
YUnsure if this page is really needed

ConfluenceImplementersMigrating OIDs to FHIR
YLow priority. I think this content is up to date but I'm unsure.

ConfluenceImplementersOpen Source Implementations

ConfluenceImplementersPosting the FHIR specification on
YLow priority. Content seems up to date, but I'm unsure.

ConfluenceImplementersPublic FHIR Validation Services

ConfluenceImplementersPublic Test Servers

ConfluenceImplementersR2-R3 Transformations
YPage either needs updating or scrapping

ConfluenceImplementersR3-R4 Transformations
YPage says that the page has not yet been migrated from the wiki, though also correctly notes that the wiki page has no information on it at all.  Either needs content or scrapping

ConfluenceImplementersTesting Platforms
YLast edited in 2019. I don't know if there are any updates needed but I don't think so?

ConfluenceImplementersUsing the FHIR Mapping Language

ConfluenceImplementersUsing the FHIR Validator

ConfluenceImplementersRegistering Code Systems
YPage needs to be developed.  Alternatively dropped in favour of UTG or HTA pages?

ConfluenceImplementersSMART on FHIR server implementations

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

  • No labels