FHIR Connectathon 19

From HL7Wiki
Jump to: navigation, search

Introduction

This page describes the Nineteenth FHIR Connectathon that will be held on Saturday/Sunday Sept. 29 - 30 2018 at the host hotel, Hyatt Regency Baltimore Inner Harbor, Baltimore, MD prior to the Sept. 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

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

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

Enrollment

If you or your company are interested in participating in the connectathon, please do the following.

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:

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

The FHIR Experience – An Immersive Hands-On Training Program - September 2018 WGM

This is a two-day, hands-on FHIR training program being offered at the September 2018 WGM on Wednesday October 3rd and Thursday October 4th. It is designed to

  • empower students with the knowledge, skills, and confidence to implement HL7 FHIR applications
  • make informed decisions about FHIR technology, and
  • prepare for the FHIR Proficiency Certification Exam.

Theoretical material is blended with hands-on activities so that students are able to apply what they learn throughout the two-day experience.

The first day is devoted to evaluating and applying the base FHIR standards through hands-on interaction with FHIR servers. Base standards topics include: FHIR Resources, RESTFUL API , transactions, operations, messages, documents, services, batch, bulk transfer, storage, Conformance and Terminology.

The second day focuses on reviewing and utilizing the FHIR implementation guides. Students will gain insight and hands-on experience with the US Core (Argonaut) and Provider Directory Implementation Guides.

The program culminates with a summative review of the two-day training through interactive preparation for the FHIR Proficiency Exam.

The Tutorial will Benefit:

  • Anyone interested in connecting his or her system/app to FHIR- or Argonaut- enabled EHRs or systems or who is implementing FHIR technology.

Upon Completion of This Tutorial, Students Will Be Able To:

  • Explain FHIR fundamental concepts
  • Implement API calls using Postman and FHIR server sandboxes.
  • Describe FHIR Implementation Guides and Profiles
  • Construct simple JavaScript applets that securely query clinical data using FHIR implementation guides.
  • Recall the required competencies and structure of the FHIR Proficiency certification exam
  • Identify gaps in FHIR proficiency by completing practice exam questions

Prerequisites

  • Participants in this program should either first take the Introduction to FHIR course or, at a minimum, review HL7 FHIR summaries in the FHIR specifications.
  • Participants are expected to be comfortable with technology and computer use. Prior knowledge of JavaScript and HTML will be useful.


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.

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



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

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.