This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "FHIR Connectathon 17"

From HL7Wiki
Jump to navigation Jump to search
Line 19: Line 19:
  
 
*[http://wiki.hl7.org/index.php?title=201801_Patient_Track Patient Track (not just for beginners)]
 
*[http://wiki.hl7.org/index.php?title=201801_Patient_Track Patient Track (not just for beginners)]
 +
*[http://wiki.hl7.org/index.php?title=201801_Terminology_Services_Track Terminology Services Track]
  
 
=== Outcomes ===
 
=== Outcomes ===
−
 
−
 
  
 
== Connectathon Organization ==
 
== Connectathon Organization ==

Revision as of 19:14, 17 October 2017

Introduction

(This page is under construction and contains information that is still subject to update and correction.) This page describes the Seventeenth FHIR Connectathon that will be held on Saturday/Sunday Jan 27-28 2018 in New Orleans, Louisiana, USA prior to the Jan. HL7 Working Group Meeting.

Location

The meeting will be held at the host hotel, Hilton New Orleans Riverside.

Important notes:

  • Please note lunch is included for Sunday with the Connectathon registration fee.

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.

Outcomes

Connectathon Organization

The connectathon will be held over 2 days - the Saturday and Sunday prior to the HL7 Working Group Meeting.

It will be based on the STU3 version of the spec - located [here http://hl7.org/fhir/STU3/index.html].

Saturday is a full day, and is intended for participants to test and develop software in an informal way. Test servers will be available (actually, they are already - 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.

  • 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
  • Optionally (but highly recommended) fill in the tracks and roles in which you are intending to participate in the spreadsheet (Note: link to be supplied)

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

For any queries, either contact a member of the planning team, or post your question in the FHIR list server

Registered Participants

Link to sign up spreadsheet


Test servers

(Note: link to be supplied)


These are the STU3 servers we are aware of:

Should I come only for the Connectathon?

Coming for the connectathon alone has value - many implementers have attended just for the Saturday/Sunday and been happy. However, if you're already on-site, there's a lot of other FHIR-related activities to participate in that may further increase your return on investment (see the list of tutorials at the bottom of this page)

FHIR User Group

Subsequent to the actual connectathon (i.e. Sunday PM) the "Application Implementation and Design (AID)" HL7 User Group will meet to discuss FHIR implementation approaches and design patterns. You're invited to share your 'lessons learned' with others in the FHIR implementation community, or to listen to other FHIR implementers.

FHIR Tutorials

  • There are 9 FHIR tutorials scheduled through-out the week
  • (Mon. PM) Introduction to HL7 FHIR
  • (Mon. PM) HAPI on FHIR
  • (Tues. AM) FHIR for Architects
  • (Tues. PM) FHIR for Specifiers
  • (Tues. PM) Driving Health Information Exchange Using XDS with CDA and FHIR
  • (Wed. AM) Introduction to FHIR Development
  • (Wed. AM) FHIR Proficiency Exam Preparation
  • (Wed. PM) Understanding and Using Terminology in HL7 FHIR
  • (Thur. AM) C-CDA on FHIR
  • (Thur. PM) Precision Medicine via FHIR: From Design to Deployment

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.
  • There will be a tutorial to help prepare for the exam:
    • (Wed. AM) FHIR Proficiency Exam Preparation
  • The exam will be held on Thursday in the afternoon.

Working Group session

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. As well, there will 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.

The final agenda won't be determined until very close to the meeting (and will evolve somewhat throughout the course of the week), however you can take a look at the [[1]] from the May 2014 WGM to get a sense of the breadth of discussions that will be taking place. FHIR runs full bore from Monday to Friday (capping off with the clinical connectathon on Friday), so regardless of what days you're present, there will likely be something of interest.

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)

The following outcomes will be recorded for each track

Results by track

how many completed each track - clients & servers

Key learnings

what changes to the spec resulted from the connectathon?

Changes next time

Does the track need to be repeated next time? (Remember, there are lots to do!) If so, what would be changed?

Overall comments

anything else - what worked, what didn't could the overall organization be changed


Other References

Sub category of FHIR Connectathon Track Proposals for the current connectathon: September 2017 Connectathon 16

Proposals due by : June 7, 2017

Go to prior connectathon proposals: May 2017 Connectathon Proposals

Use this page to submit proposals for tracks for inclusion in the , 2017 connectathon. These proposals will be reviewed and prioritized by the FMG as per the FHIR_Connectathon_Track_Process.

Return to the FHIR Main Page

FHIR Genomics

Retrieved from "https://wiki.hl7.org/w/index.php?title=FHIR_Connectathon_17&oldid=147717"