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
 
(27 intermediate revisions by the same user not shown)
Line 7: Line 7:
  
 
The meeting will be held on the hosted Skype meeting call.
 
The meeting will be held on the hosted Skype meeting call.
 +
 +
Active Connectathon Calls all times PST
 +
 +
8am to 2pm Main call  1-800-406-9547 ID= 730216  https://meet.cambiahealth.com/david.degandi/V8P6SHWD
  
 
== Important notes:==
 
== Important notes:==
Line 16: Line 20:
 
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.
 
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.
  
*[http://wiki.hl7.org/index.php?title=201605_Patient_Track_Proposal Patient track]
+
*[http://wiki.hl7.org/index.php?title=Virtual_Patient_Track_Proposal  Virtual Patient track]
  
To assist with management on the day, participants are *strongly encouraged* to add their name to the participants tab of the QQQQ [https://docs.google.com/spreadsheets/d/1gAnNmyurFDopLYJakQOtXWYGxvuoiDn49n8qRI5mlb4/edit?usp=sharing Tracking Spreadsheet] as soon as we get oneQQQQ.
+
To assist with management on the day, participants are *strongly encouraged* to add their name to the [https://docs.google.com/document/d/1Y1KOIF_i1f18wBliWDkh5rXEWjDOBIP_DOolrsa88Z4/edit?usp=sharing Tracking Document].
  
 
== Connectathon Organization ==
 
== Connectathon Organization ==
  
 
The connectathon will be held over 1 day.
 
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 - '''[http://wiki.hl7.org/index.php?title=Publicly_Available_FHIR_Servers_for_testing FHIR Test Servers]'''  ), but some participants may bring other servers along depending on the actors they are fulfilling.
+
It is intended for participants to test and develop software in an informal way. Test servers will be available (actually, they are already - '''[http://wiki.hl7.org/index.php?title=Publicly_Available_FHIR_Servers_for_testing FHIR Test Servers]'''  ).
Sunday is the morning only, and has 2 parts:
 
  
* the formal testing part
+
This is the first FHIR Virtual Connectathon.
* a mini-showcase where participants can demonstrate their work to the others
 
  
Each stream has a coordinator. The nominated coordinator's responsibilities:
+
The connectathon will start Wednesday July 13 at 11AM and run until 4PM EST with a wrap up from 4PM to 5PM.
* In the lead up to the connectathon: track participants, respond to queries about scenarios, connect participants to each other
+
Dave DeGandi will facilitate and host a Skype meeting with screen share from 11AM to 5:00PM EST, his will be the “Main Call” for the connectathon.  It will be open mic where people can ask questions, share lessons, successes and address the entire group.
* During the connectathon act as a test mediator / progress tracker
+
 
* track emergent issues that should be fed back to the committees
+
We will dynamically break out topic discussion threads as needed, these will be Cambia hosted lync meetings with chat, audio and screen share.  People can join the threads which interest them.  The Main call and the active break out thread discussions information will be maintained on the [https://docs.google.com/document/d/1Y1KOIF_i1f18wBliWDkh5rXEWjDOBIP_DOolrsa88Z4/edit?usp=sharing Tracking Document].
  
 
== Connectathon Planning Team ==
 
== Connectathon Planning Team ==
Line 39: Line 41:
  
 
*[mailto:jin.yang@cambiahealth.com Jin Yang], Cambia Health Solutions
 
*[mailto:jin.yang@cambiahealth.com Jin Yang], Cambia Health Solutions
 +
*[mailto:ravindra.kondiparthi@cambiahealth.com Ravi Kondiparthi], Cambia Health Solutions
  
 
= Enrollment =
 
= Enrollment =
Line 45: Line 48:
 
*Read the '''[http://hl7.org/fhir/2016May Connectathon version of the FHIR Specification]''' and the '''[[ FHIR | FHIR wiki ]]''' if you haven't already done so, to become familiar with the concepts.
 
*Read the '''[http://hl7.org/fhir/2016May Connectathon version of the FHIR Specification]''' and the '''[[ FHIR | FHIR wiki ]]''' if you haven't already done so, to become familiar with the concepts.
 
*Read the '''scenario descriptions''' below.   
 
*Read the '''scenario descriptions''' below.   
*[http://www.hl7.org/events/wgm052016/ Register to attend the WGM], and make sure to select the Connectathon option when you do
+
*[http://www.hl7.org/events/virtualconnectathon072016/ Register to attend], and make sure to select the Connectathon option when you do
 
*Optionally add your details below (in the 'Registered Participants' section) to indicate the scenarios you intend to participate in
 
*Optionally add your details below (in the 'Registered Participants' section) to indicate the scenarios you intend to participate in
 
   
 
   
Line 53: Line 56:
  
 
== 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 ==
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]
  
 
= Connectathon track scenarios =
 
= Connectathon track scenarios =
 
This section lists the scenarios that are proposed for each track.  
 
This section lists the scenarios that are proposed for each track.  
  
'''Note that this track - as with all tracks - will use the candidate 'STU3 candidate' version of FHIR as described [http://hl7.org/fhir/2016May/index.html here].''' If you've been to a connectathon before and done this track, then you may need to change your code, as [http://hl7.org/fhir/2016May/history.html#history there have been many important changes to the specification].
+
'''Note that this track - as with all tracks - will use the 'DSTU2' version of FHIR as described [http://hl7.org/fhir/2016May/index.html here].''' If you've been to a connectathon before and done this track, then you may need to change your code, as [http://hl7.org/fhir/2016May/history.html#history there have been many important changes to the specification].
 
 
=== Track 1  C-CDA on FHIR ===
 
*[http://wiki.hl7.org/index.php?title=201605_C-CDA_on_FHIR_Connectathon_Proposal C-CDA on FHIR]
 
 
 
=== Track 2 CDS Enablement Services ===
 
*[http://wiki.hl7.org/index.php?title=201605_CDS_Enablement_Services CDS Enablement Services]
 
 
 
=== Track 3 CDS Hooks ===
 
*[http://wiki.hl7.org/index.php?title=201605_CDS_Hooks_Connectathon_Track_Proposal CDS Hooks]
 
 
 
=== Track 4 Conditional Reference ===
 
*[http://wiki.hl7.org/index.php?title=201605_Conditional_Reference_Connectathon_Proposal Conditional Reference]
 
 
 
=== Track 5 CQF on FHIR ===
 
*[http://wiki.hl7.org/index.php?title=201605_CQF_on_FHIR_Connectathon_Track_Proposal CQF on FHIR]
 
 
 
=== Track 6 Data Access Framework ===
 
*[http://wiki.hl7.org/index.php?title=201605_Data_Access_Framework_(DAF) Data Access Framework]
 
 
 
=== Track 7 Declarative Mapping ===
 
*[http://wiki.hl7.org/index.php?title=201605_Declarative_Mapping Declarative Mapping]
 
 
 
=== Track 8 FHIR Genomics ===
 
*[http://wiki.hl7.org/index.php?title=201605_FHIR_Genomics_on_FHIR_Connectathon_Track_Proposal FHIR Genomics]
 
 
 
=== Track 9 Structured Data Capture ===
 
*[http://wiki.hl7.org/index.php?title=201605_FHIR_Structured_Data_Capture Structured Data Capture]
 
 
 
=== Track 10 Financial Mgt. ===
 
*[http://wiki.hl7.org/index.php?title=201605_Financial_Track_Proposal Financial]
 
 
 
=== Track 11 Lab Orders ===
 
*[http://wiki.hl7.org/index.php?title=201605_LabOrder Lab Orders]
 
 
 
=== Track 12 the PATCH proposal ===
 
*[http://wiki.hl7.org/index.php?title=201605_PATCH_Connectathon_Track_Proposal PATCH proposal]
 
 
 
=== Track 13 Patient track ===
 
*[http://wiki.hl7.org/index.php?title=201605_Patient_Track_Proposal Patient track]
 
 
 
=== Track 14 Provider Directories & Scheduling ===
 
*[http://wiki.hl7.org/index.php?title=201605_ServicesDirectoryAndScheduling_Track Provider Directories & Scheduling]
 
''This track will attempt to extend on the track from connectathon 11, where we will expand the scope to the earlier stages of Service Provider Directory questioning, scheduling, and then the transition into Encounters.''
 
 
 
''If you are familiar with HPD, then we would like to encourage your participation.''
 
 
 
''We will have at least 1 large FHIR dataset available (from MiHN - Thanks Jeff(s))''
 
 
 
=== Track 15 SMART-ca on FHIR ===
 
*[http://wiki.hl7.org/index.php?title=201605_SMART-ca_on_FHIR SMART ca on FHIR]
 
 
 
=== Track 16 Terminology Services ===
 
*[http://wiki.hl7.org/index.php?title=201605_Terminology_Services_Track_Proposal Terminology Services]
 
 
 
=== Track 17 Workflow ===
 
*[http://wiki.hl7.org/index.php?title=201605_Workflow Workflow]
 
 
 
 
 
 
 
 
 
  
 +
=== Track 1 Virtual Patient track ===
 +
*[http://wiki.hl7.org/index.php?title=Virtual_Patient_Track_Proposal  Virtual Patient track]
  
 
== Servers ==
 
== Servers ==
  
 
http://wiki.hl7.org/index.php?title=Version_2_-_FHIR_Mapping_Scenarios (Supporting the messaging interoperability paradigm)
 
http://wiki.hl7.org/index.php?title=Version_2_-_FHIR_Mapping_Scenarios (Supporting the messaging interoperability paradigm)
 
= 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 "[[AID|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.
 
*See [[AID_201605_Meeting_in_Montreal|AID Sunday PM Agenda]] for details.
 
*Please contact [mailto:rene.spronk@ringholm.com Rene Spronk] to get hold of a slot on the AID agenda - we do appreciate you sharing your ideas and experiences.
 
 
== FHIR Tutorials ==
 
There are 4 tutorials scheduled through-out the week
 
* Mon pm - Introduction to FHIR
 
* Tue am - FHIR for Architects
 
* Tue pm - FHIR for Specifiers
 
* Wed am - Intro to FHIR Development
 
Detailed descriptions are available in the [http://www.hl7.org/documentcenter/public_temp_DE20E5DD-1C23-BA17-0CDA8127B0953885/brochures/wgm/HL7_WGM_20160310.pdf Event brochure]
 
 
== 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 [[http://wiki.hl7.org/index.php?title=FHIR_Agenda_2014605_WGM|agenda]] from the May 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 =
 
= Outcomes =
  
  
== Track x - TrackName ==
+
== Track 1 - Virtual Patient Track ==
  
 
===  Results by track ===
 
===  Results by track ===
Line 173: Line 95:
 
==
 
==
 
=
 
=
 
  
 
= Other References =
 
= Other References =

Latest revision as of 18:51, 13 July 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.

Active Connectathon Calls all times PST
8am to 2pm Main call  1-800-406-9547 ID= 730216   https://meet.cambiahealth.com/david.degandi/V8P6SHWD

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

This is the first FHIR Virtual Connectathon.

The connectathon will start Wednesday July 13 at 11AM and run until 4PM EST with a wrap up from 4PM to 5PM. Dave DeGandi will facilitate and host a Skype meeting with screen share from 11AM to 5:00PM EST, his will be the “Main Call” for the connectathon. It will be open mic where people can ask questions, share lessons, successes and address the entire group.

We will dynamically break out topic discussion threads as needed, these will be Cambia hosted lync meetings with chat, audio and screen share. People can join the threads which interest them. The Main call and the active break out thread discussions information will be maintained on the Tracking Document.

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, and make sure to select the Connectathon option when you do
  • Optionally add your details below (in the 'Registered Participants' section) to indicate the scenarios you intend to participate in

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 Document

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 1 - Virtual Patient 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