Difference between revisions of "FHIR Connectathon 20"

From HL7Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 3 users not shown)
Line 28: Line 28:
 
[https://docs.google.com/spreadsheets/d/1Th0-qhD4u5XTrFt7QeK25xeHxrbC5sF4AU4VTdGxaj0/edit#gid=477899808 Break Out Room Schedule]
 
[https://docs.google.com/spreadsheets/d/1Th0-qhD4u5XTrFt7QeK25xeHxrbC5sF4AU4VTdGxaj0/edit#gid=477899808 Break Out Room Schedule]
  
[https://drive.google.com/file/d/1pY-hecSFOMPrzHfAoqOwv_PDBjAtZdvp/view Outcomes Reporting]
+
[https://docs.google.com/document/d/1Z9JDmZZYncNKDM6Q7ja10-Yw8c3Mz-tCVHJunxBYhEw/edit?usp=sharing Outcomes Reporting]
  
 
[http://wiki.hl7.org/images/3/36/FHIR_Overview_Connectathon_20.pdf FHIR Overview PDF Presentation Saturday Morning Breakout]
 
[http://wiki.hl7.org/images/3/36/FHIR_Overview_Connectathon_20.pdf FHIR Overview PDF Presentation Saturday Morning Breakout]
Line 110: Line 110:
 
** R4 - http://wildfhir.aegis.net/fhir4-0-0
 
** R4 - http://wildfhir.aegis.net/fhir4-0-0
 
** R3 - http://wildfhir.aegis.net/fhir3-0-1
 
** R3 - http://wildfhir.aegis.net/fhir3-0-1
* Telstra Health(HealthConnex): http://sqlonfhir-stu3.azurewebsites.net/fhir
+
* Telstra Health(HealthConnex):
 +
** STU3 server: http://sqlonfhir-stu3.azurewebsites.net/fhir
 +
** R4 server: http://sqlonfhir-r4.azurewebsites.net/fhir
 +
** R4 vhdir demo server: https://vhdir-demo.fhir.org/fhir
 
* Intelligent Medical Objects (IMO): https://fhir-terminology-demo.e-imo.com/api/swagger  
 
* Intelligent Medical Objects (IMO): https://fhir-terminology-demo.e-imo.com/api/swagger  
 
** Please contact teamhotel@imo-online.com for username and password
 
** Please contact teamhotel@imo-online.com for username and password
Line 123: Line 126:
 
* Cerner: https://fhir-open.stagingcerner.com/r4/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/
 
* Cerner: https://fhir-open.stagingcerner.com/r4/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/
 
* Helios Software: http://r4.heliossoftware.com:8080
 
* Helios Software: http://r4.heliossoftware.com:8080
 +
* CMS Blue Button Sandbox: http://sandbox.bluebutton.cms.gov
 +
** Documentation available at https://bluebutton.cms.gov
 +
* Elsevier: http://elsevier.demo.elsevierfhir.com/fhir/metadata
  
 
== FHIR Tutorials ==
 
== FHIR Tutorials ==
Line 145: Line 151:
 
   
 
   
  
[https://drive.google.com/file/d/1pY-hecSFOMPrzHfAoqOwv_PDBjAtZdvp/view Outcomes Reporting]
+
[https://docs.google.com/document/d/1Z9JDmZZYncNKDM6Q7ja10-Yw8c3Mz-tCVHJunxBYhEw/edit?usp=sharing Outcomes Reporting]
  
 
Guidelines for report out:
 
Guidelines for report out:

Latest revision as of 05:29, 29 January 2019

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


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

Helpful Links

Con Man App

Connectathon Manager Orientation Video

Break Out Room Schedule

Outcomes Reporting

FHIR Overview PDF Presentation Saturday Morning Breakout

FHIR Testing and Touchstone PDF Presentation Saturday Morning Breakout

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 Jan 12 9AM - 10PM and Sunday Jan 13 9AM - 5PM, prior to the HL7 Working Group Meeting.

Saturday is an extended day (9AM - 8PM), 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 track 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 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.

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



Track Proposals were due in November. 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