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

Difference between revisions of "Virtual FHIR Connectathon"

From HL7Wiki
Jump to navigation Jump to search
Line 53: Line 53:
  
 
== Registered Participants ==
 
== Registered Participants ==
see the [https://docs.google.com/spreadsheets/d/1gAnNmyurFDopLYJakQOtXWYGxvuoiDn49n8qRI5mlb4/edit?usp=sharing Tracking Spreadsheet]
+
see the [https://docs.google.com/document/d/1Y1KOIF_i1f18wBliWDkh5rXEWjDOBIP_DOolrsa88Z4/edit?usp=sharing Tracking Document]
  
 
== Test servers ==
 
== Test servers ==

Revision as of 21:47, 31 May 2016

Introduction

(This page is under construction and contains information that is still subject to update and correction.) This page describes the first FHIR Virtual Connectathon that will be held on Wednesday July 13 (11am - 5pm++ EST) hosted by Cambia.

Location

The meeting will be held on the hosted Skype meeting call.

Important notes:

  • Please note virtual pizza will be provided.

Themes

The following are the themes for the Connectathon. Each item links to the original proposal, with the coordinators name and email on the linked page. More details on each track appear in this document.

To assist with management on the day, participants are *strongly encouraged* to add their name to the Tracking Document.

Connectathon Organization

The connectathon will be held over 1 day. It 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 the morning only, and has 2 parts:

  • the formal testing part
  • a mini-showcase where participants can demonstrate their work to the others

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

see the Tracking Document

Test servers

see the Tracking Spreadsheet

Connectathon track scenarios

This section lists the scenarios that are proposed for each track.

Note that this track - as with all tracks - will use the 'DSTU2' version of FHIR as described here. If you've been to a connectathon before and done this track, then you may need to change your code, as there have been many important changes to the specification.

Track 1 Virtual Patient track

Servers

http://wiki.hl7.org/index.php?title=Version_2_-_FHIR_Mapping_Scenarios (Supporting the messaging interoperability paradigm)

Outcomes

Track x - TrackName

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