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

HL7 FHIR CONNECTATHON 22

September 14, 2019 9:00 AM - 10:00 PM  &  September 15, 2019 9:00 AM to 5:00 PM

 at the Atlanta Marriott Marquis in Atlanta, Georgia.

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

Announcements:

Plan a Track! by clicking here. Track Proposals are due July 31, 2019.

Early Bird Registration is available through Saturday, August 24, 2019.

View Connectathon Information Session Slides HERE.

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 wiki 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 22.
  3. Register to attend the WGM, and make sure to select the Connectathon option when you do
  4. Complete the HL7 FHIR Pre-Connectathon Survey  for each member of your team to indicate their primary track.

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

For any queries, either contact Sandy Vance at sandy.vance@aegis.net, a member of the planning team, or post your question in the FHIR list serve.

Helpful Links:

HL7 FHIR Pre-Connectathon Survey 

Con Man App

Connectathon Manager Orientation Video

Break Out Room Schedule


Connectathon Planning Team

FHIR Tutorials

  • There are several FHIR tutorials scheduled through-out the week and a full list can be found by clicking the word "Tutorials" in the upper right corner of the Event Brochure which can be found here.

FHIR Proficiency Exam

  • The FHIR proficiency test allows test takers to demonstrate their knowledge and understanding of the specification. This is a basic proficiency test, not a professional credentialing test. It will be multiple choice, multi-select, and true/false and based on the STU3 specification and not on field knowledge. Those who pass the test will receive the FHIR Proficiency Certificate, a Certificate of Knowledge.

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 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.

You can take a look at the Event Brochure to get a sense of the breadth of discussions that will be taking place.

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.


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
Comments
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
benjamin@redoxengine.com


Recommended by Sean McIlvenna
George DixonAllScripts

george.dixon@allscripts.com



XRecommended by Sarah Gaunt
Emma JonesAllScripts

emma.jones@allscripts.com



XRecommended by Sarah Gaunt
John Hatem
jnhatem@hotmail.com

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

Recommended by Sean McIlvenna
Reuben Daniels
reubendaniels@gmail.com
X
Recommended by Sarah Gaunt
Micheal Lawley
Michael.Lawley@csiro.au
X
Recommended by Sarah Gaunt
Smita HastackSamvit Solutionsshastak@samvit-solutions.com

XRecommended by Lloyd McKenzie
Robinette Renner
raley@nmdp.orgX

Recommended by Lloyd McKenzie
Rik Smithies
rik@smithies.netX
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
jose.a.teixeira@gmail.com XXX
John Moehrke*
johnmoehrke@gmail.com 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

(X)X
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

jgarcia@gevityinc.com

X
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 Consultingpknapp@pknapp.com
XXSelf-nominated
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*





Mark KramerMITREmkramer@mitre.org
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 #6: Value Sets / Code Systems

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

Step #7: 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)



The bulk of the content for this page has yet to be migrated from http://wiki.hl7.org/index.php?title=FHIR

  • No labels