FHIR Connectathon 20

Introduction

This page describes the Twentieth FHIR Connectathon that will be held on Saturday/Sunday Jan. 12 - 13 2019 at the host hotel, Hyatt Regency San Antonio on the Riverwalk, San Antonio, TX prior to the Jan. HL7 Working Group Meeting.

The contact for this event is Sandy Vance at sandra.vance@aegis.net or 614-273-5916

Helpful Links

Con Man App

Connectathon Manager Orientation Video

Tracking Spreadsheet

Break Out Room Schedule

Outcomes Reporting

Important notes

• Please be sure to fill out our [hr/Z6CZSWR PRE CONNECTATHON SURVEY] so that we know how many people will be in what track!

• Track Planning and Orientation should be well under way. If you have not already, please be sure to create orientation slides for your track using the HL7 FHIR Connectathon 18 Track Orientation Template.

• Connectathon will be based on the the R4 ballot candidate, unless stated otherwise in the track proposals.

• Schedule Break Out Rooms HERE!

Tracks

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.

• Bulk Data
• Care Planning and Management
• CDS Hooks
• Clinical Genomics
• Clinical reasoning
• Coverage Requirements Discovery (CRD)
• Direct/Certificates
• Documents
• Financial Track
• Evidence Based Medicine (EBM)
• FHIRcast
• IG development and exchange
• Patient Track
• Subscriptions
• International Patient Summary
• Order Catalog
• Public Health
• Questionnaire
• Terminology Services
• LOINC to In Vitro Diagnostic (LIVD)

Connectathon Organization

The connectathon will be held over 2 days - Saturday Sept 29 9AM - 10PM and Sunday Sept 30 9AM - 5PM, prior to the HL7 Working Group Meeting.

Saturday is an extended day (9AM - 10PM), and is intended for participants to test and develop software in an informal way. Test servers are available (FHIR Test Servers ), but some participants may bring other servers along depending on the actors they are fulfilling. Sunday is also a full day. The actual programme is still being confirmed, but will likely involve concurrent break-out sessions for demonstrations and discussions of specific topics.

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

• Grahame Grieve, Health Intersections Pty Ltd
• David Hay, Orion Health
• Sandy Vance, HL7 Connectathon Administrator, AEGIS.net

Enrollment

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
• Complete the HL7 FHIR Pre-Connectathon Survey (Link available SOON!) 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 sandra.vance@aegis.net, a member of the planning team, or post your question in the FHIR list server

Tracking application

The tracking tool ConMan (stands for Connectathon Manager) is used by some tracks to record testing outcomes. Check with the tracks for details.

It is helpful to register your name even if your track is not using the tool as it has contact details of the participants. (When you load the page, click the 'Register new person' to add your details).

Note that you must still enroll at the event, as described above

Test servers

These are the STU3 servers we are aware of:

• Health Intersections: http://test.fhir.org/r3
• HAPI / University Health Network: http://fhirtest.uhn.ca/baseDstu3
• Vonk: http://vonk.furore.com
• AEGIS.net, Inc.: http://wildfhir.aegis.net/fhir3-0-1
• Telstra Health(HealthConnex): http://sqlonfhir-stu3.azurewebsites.net/fhir
• Intelligent Medical Objects (IMO): https://fhir-terminology-demo.e-imo.com/api/swagger
  • Please contact teamhotel@imo-online.com for username and password
• Knapp Consulting Inc.: http://www.pknapp.com:8081/con19 (Financial Track)
• Apelon (Terminology Service): http://fhir.ext.apelon.com:7080/dts/fhir/ and Demo Page at http://fhir.ext.apelon.com:7080/DtsOnFhirDemo/logon/Logon.action
  • Through a collaboration with the American Medical Association, the Current Procedural Terminology (CPT®) is now available for use in FHIR development efforts through the Apelon DTS on FHIR® service. Authentication is required. Please send an email to support@apelon.com for a user/pass. Please note that use of CPT® for production or commercial purposes through this service is prohibited.
• HSPC: http://sandbox.hspconsortium.org
• SMART (app launcher with r2 and r3 servers) https://launch.smarthealthit.org
• Ontoserver (Terminology Service): https://ontoserver.csiro.au/stu3-latest
• Tukan FHI Server http://fhir.tukan.online/
• Terminz (NZ Terminology Service): http://its.patientsfirst.org.nz/RestService.svc/Terminz
• Cerner: https://fhir-open.stagingcerner.com/r4/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/

FHIR Tutorials

• There are 12 FHIR tutorials scheduled through-out the week

• (Tues. AM) Introduction to HL7 FHIR
• (Tues. AM) Designing and Architecting HL7 FHIR Solutions
• (Tues. PM) Introduction to HL7 FHIR for Software Developers
• (Tues. PM) HL7 FHIR for Clinicians and Decision Makers
• (Tues. PM) HL7 FHIR Profiling
• (Wed. AM) HAPI on FHIR
• (Wed. AM) Clinical Documents on HL7 FHIR
• (Wed. PM) Understanding and Using Terminology in HL7 FHIR
• (Wed. PM) Clinical Genomics Using HL7 FHIR
• (Thur. AM) HL7 FHIR for Clinical and Administrative Workflows
• (Thur. PM) Driving Health Information Exchange Using XDS with CDA and FHIR
• (All day - Wed. & Thurs.) FHIR Experience

Detailed descriptions are available in the Event Brochure

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.

• Tutorials on the FHIR Proficiency Exam can be found in HL7's Education on Demand site: https://www.pathlms.com/hl7.

• The exam can be taken either online or at one of 900 HOST centers of HL7's testing service Kryterion. More details can be found at http://www.hl7.org/implement/certification.cfm?ref=nav.

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.

Outcomes (for coordinators)

Outcomes Reporting

Guidelines for report out:

• 1 paragraph summary: what was the track trying to achieve
• 1 list of participants (with logos if you have time and energy)
• 1 paragraph: notable achievements
• 1-2 screenshots if relevant and interesting and/or links to further information about implementations/achievements
• 1 paragraph: discovered issues / questions (if there are any)
• 1 paragraph: now what?

Other References

• Other FHIR Connectathons:
  • 1st FHIR Connectathon (8 Sept. 2012 - Baltimore MD, USA)
  • FHIR Connectathon 2 (12/13 Jan. 2013 - Phoenix AZ, USA)
  • FHIR Connectathon 3 (4/5 May 2013 - Atlanta GA, USA)
  • FHIR Connectathon 4 (21/22 Sept. 2013 - Cambridge MA, USA)
  • FHIR Mini Connectathon (Oct. 2013 - Sydney, Australia)
  • FHIR Connectathon 5 (18/19 Jan. 2014 - San Antonio TX, USA)
  • FHIR Connectathon 6 (3/4 May. 2014 - Phoenix, Arizona, USA)
  • FHIR Connectathon 7 (September. 2014 - Chicago, IL, USA)
  • FHIR Connectathon 8 (January 2015 - San Antonio, TX, USA)
  • FHIR Connectathon 9 (May 2015 - Paris, France)
  • FHIR Connectathon 10 (Oct 2015 - Atlanta GA, USA)
  • FHIR Connectathon 11 (Jan 2016 - Orlando, FL, USA)
  • FHIR Connectathon 12 (May 2016 - Montreal, Canada)
  • FHIR Connectathon 13 (September 2016 - Baltimore, MD, USA)
  • FHIR Connectathon 14 (January 2017, San Antonio, USA)
  • FHIR Connectathon 15 (May 2017 - Madrid, Spain)
  • FHIR Vendor's Mini Connectathon (4./5. July 2017, Berlin, Germany)
  • FHIR Connectathon 16 (September 2017 - San Diego,CA, USA)
  • FHIR Connectathon 17 (January 2018, New Orelans, USA)
  • FHIR Connectathon 18 (May 2018, Cologne, Germany)

Sept. 2018 Track Proposal Submissions are due July 11, 2018. Please complete the template found at the track Proposal link AND contact Sandy Vance immediately if you are interested in making a late submission.

FHIR_Connectathon_Track_Process.

Return to the FHIR Main Page