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

Difference between revisions of "FHIR Connectathon 16"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
 
(33 intermediate revisions by 12 users not shown)
Line 1: Line 1:
 +
[[Category:FHIR Connectathons]]
 +
== Introduction ==
 +
(This page is under construction and contains information that is still subject to update and correction.)
 +
This page describes the Sixteenth FHIR Connectathon that will be held on Saturday Sept. 9 and the morning  of Sunday Sept. 10, 2017 in San Diego, CA, USA prior to the [http://www.hl7.org/events/working_group_meeting/2017/09/ Sept. HL7 Working Group Meeting].
  
[[Category:201709_FHIR_Connectathon_Track_Proposals|Sept 2017 Proposals]]
+
===Location===
__NOTOC__
 
=Track Name=
 
  
==Submitting WG/Project/Implementer Group==
+
The meeting will be held at the host hotel, Hyatt Regency La Jolla at Aventine.
<!-- Who is asking for this track? -->
 
  
==Justification==
+
== Important notes:==
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
  
==Proposed Track Lead==
+
* '''Please note lunch is included for Sunday with the Connectathon registration fee.
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
'''
See [[Connectathon_Track_Lead_Responsibilities]]
+
* Connectathon Demonstration Meeting Link: https://www.gotomeet.me/LloydMcKenzie
  
==Expected participants==
+
== Tracks ==
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
  
==Roles==
+
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.
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
===Role 1 Name===
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 
  
==Scenarios==
+
*[http://wiki.hl7.org/index.php?title=201709_CDS_Hooks CDS Hooks]
<!-- What will be the actions performed by participants? -->
+
*[http://wiki.hl7.org/index.php?title=201709_Clinical_Research Clinical Research]
 +
*[http://wiki.hl7.org/index.php?title=201709_Clinical_Reasoning Clinical Reasoning]
 +
*[http://wiki.hl7.org/index.php?title=201709_Consumer_Centered_Data_Exchange Consumer Centered Data Exchange]
 +
*[http://wiki.hl7.org/index.php?title=201709_DevicesOnFHIR  Devices on FHIR]
 +
*[http://wiki.hl7.org/index.php?title=201709_Genomics Genomics]
 +
*[http://wiki.hl7.org/index.php?title=201709_Implantables_Tracking Implantables Tracking]
 +
*[http://wiki.hl7.org/index.php?title=201709_LastN_Query_Track LastN Query track]
 +
*[http://wiki.hl7.org/index.php?title=201709_MHD_STU3 MHD STU3]
 +
*[http://wiki.hl7.org/index.php?title=201709_Patient_Reported_Observations Patient Reported Observations]
 +
*[http://wiki.hl7.org/index.php?title=201709_Patient_Track Patient Track (not just for beginners)]
 +
*[http://wiki.hl7.org/index.php?title=201709_Provider_Directories_and_Scheduling Provider Directories & Scheduling]
 +
*[http://wiki.hl7.org/index.php?title=201709_Terminology_Services_Track Terminology Services track]
 +
*[http://wiki.hl7.org/index.php?title=201709_Attachments Attachments]
 +
*[http://wiki.hl7.org/index.php?title=201709_Care_Plan Care Plan]
 +
*[http://wiki.hl7.org/index.php?title=201709_FHIR_Documents FHIR Documents]
 +
*[http://wiki.hl7.org/index.php?title=201709_FHIR_Subscriptions FHIR Subscriptions]
 +
*[http://wiki.hl7.org/index.php?title=201709_Financial_Management Financial Management]
 +
*[http://wiki.hl7.org/index.php?title=201709_ProcedureRequest Procedure Request]
  
===Scenario Step 1 Name===
+
=== Outcomes ===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
  
<!-- Provide a description of each task -->
 
  
==TestScript(s)==
+
[https://docs.google.com/spreadsheets/d/1BoJHpwneS48kZO-uUXpP2ADZATaqPlkg7vg8M5xOMLA/edit?usp=sharing Link to the tracking spreadsheet]
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested.
 
These should be committed to SVN under trunk/connectathons/[connectathon]
 
-->
 
  
==Security and Privacy Considerations==
+
== Connectathon Organization ==
<!-- Optional (for initial proposal): Address the topic of Privacy and Security.  
+
 
* What Authentication/Authorization will be used (e.g. SMART on FHIR (OAuth), HEART (UMA/OAuth), IHE IUA (OAuth), generic OAuth, generic SAML, mutual-Auth-TLS), or explicitly indicate that it is out of scope and left to implementations.
+
The connectathon will be held over 2 days - the Saturday and Sunday prior to the HL7 Working Group Meeting.
* What Privacy Consent management will be used? When the Consent Resource is used, define how.
+
 
* What Audit Logging will be used? When the AuditEvent Resource is used, define expectations of what events will be logged and what each AuditEvent will contain.
+
It will be based on the STU3 version of the spec - located [here http://hl7.org/fhir/STU3/index.html].
* How will Provenance be used? Provenance use should be mandated when data is imported from other systems, so as to track that source of that data. Provenance should be used when data is authored by unusual sources, such as the Patient themselves or devices.  
+
 
* How will security-labels be used? Security-labels are meta tags used to classify the data into various confidentiality, sensitivity, and integrity classifications. These security-labels are then available for use and available for access control decisions.
+
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 - '''[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.
I am happy to help: JohnMoehrke@gmail.com -- security co-chair
+
Sunday is the morning only, and has 2 parts:
-->
+
 
 +
* the formal testing part
 +
* a mini-showcase where the track leads can demonstrate representative work to the others
 +
 
 +
Each stream has a coordinator. The nominated coordinator's [http://wiki.hl7.org/index.php?title=Connectathon_Track_Lead_Responsibilities 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 ==
 +
*[mailto:david.hay25@gmail.com David Hay], Orion Health
 +
*[mailto:brian.pech@kp.org Brian Pech], Kaiser Permanente
 +
*[mailto:grahame@healthintersections.com.au Grahame Grieve], Health Intersections Pty Ltd
 +
 
 +
= Enrollment =
 +
 
 +
If you or your company are interested in participating in the connectathon, please do the following.
 +
*Read the '''[http://hl7-fhir.github.io/index.html 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. 
 +
*[http://www.hl7.org/events/working_group_meeting/2017/09/ 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 [http://lists.hl7.org/fhir FHIR list server]
 +
 
 +
== Registered Participants ==
 +
 
 +
[https://docs.google.com/spreadsheets/d/1wkOBIuR-q_IbBcc8uc3zeT1kivC_7_j5KDVf8unjIfE/edit?usp=sharing Link to sign up spreadsheet]
 +
 
 +
 
 +
== Test servers ==
 +
(Note: link to be supplied)
 +
 
 +
 
 +
These are the STU3 servers we are aware of:
 +
* Health Intersections:  http://test.fhir.org/r3
 +
* HAPI / University Health Network:  http://fhirtest.uhn.ca/baseDstu3
 +
* Vonk: http://vonk.furore.com
 +
* AEGIS.net, Inc.: http://wildfhir.aegis.net/fhir3-0-1
 +
* Telstra Health(HealthConnex): http://sqlonfhir-stu3.azurewebsites.net/fhir
 +
* Knapp Consulting Inc.: http://www.pknapp.com:8081/con13 (Financial Track)
 +
* Apelon (Most recent build): http://fhir.ext.apelon.com:7080/dtsserverws/fhir and Demo Page at http://fhir.ext.apelon.com:7080/DtsOnFhirDemo/logon/Logon.action
 +
**Through a collaboration with the American Medical Association, the Current Procedural Terminology (CPT®) is now available for use in FHIR development efforts through the Apelon DTS on FHIR® service. Authentication is required. Please send an email to support@apelon.com for a user/pass. Please note that use of CPT® for production or commercial purposes through this service is prohibited.
 +
* HSPC: http://sandbox.hspconsortium.org
 +
 
 +
= 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 201709 Meeting in San Diego|AID Sunday PM Agenda]] for details.
 +
*Please contact [mailto:andy.stechishin@gmail.com Andy Stechishin] to get hold of a slot on the AID agenda - we do appreciate you sharing your ideas and experiences.
 +
 
 +
== 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 [http://www.hl7.org/events/working_group_meeting/2017/09/tutorials.cfm 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 [[http://wiki.hl7.org/index.php?title=FHIR_Agenda_2014605_WGM|agenda]] 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 =
 +
 
 +
* Other FHIR Connectathons:
 +
** 1st [[FHIR Connectathon]] (8 Sept. 2012 - Baltimore MD, USA)
 +
** [[FHIR Connectathon 2]] (12/13 Jan. 2013 - Phoenix AZ, USA)
 +
** [[FHIR Connectathon 3]] (4/5 May 2013 - Atlanta GA, USA)
 +
** [[FHIR Connectathon 4]] (21/22 Sept. 2013 - Cambridge MA, USA)
 +
** FHIR Mini Connectathon (Oct. 2013 - Sydney, Australia)
 +
** [[FHIR Connectathon 5]] (18/19 Jan. 2014 - San Antonio TX, USA)
 +
** [[FHIR Connectathon 6]] (3/4 Jan. 2014 - Phoenix, Arizona, USA)
 +
** [[FHIR Connectathon 7]] (September. 2014 - Chicago, IL, USA)
 +
** [[FHIR Connectathon 8]] (January 2015 - San Antonio, TX, USA)
 +
** [[FHIR Connectathon 9]] (May 2015 - Paris, France)
 +
** [[FHIR Connectathon 11]] (Jan 2016 - Orlando, FL, USA)
 +
** [[FHIR Connectathon 12]] (May 2016 - Montreal, Canada)
 +
** [[FHIR Connectathon 13]] (September 2016 - Baltimore, MD, USA)
 +
** [[FHIR Connectathon 14]] (January 2017, San Antonio, USA)
 +
**[[FHIR  Connectathon 15]] (May 2017 - Madrid, Spain)
 +
 
 +
[[Category:FHIR Connectathons]]
 +
 
 +
 
 +
 
 +
 
 +
[[Category:FHIR Connectathon Track Proposals|2s]]
 +
Sub category of [[:Category:FHIR Connectathon Track Proposals|FHIR Connectathon Track Proposals]] for the current connectathon: September 2017 [[FHIR_Connectathon_16|Connectathon 16]]
 +
 
 +
Proposals due by : June 7, 2017
 +
 
 +
Go to prior connectathon proposals: [[:Category:201701 FHIR Connectathon Track 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]].
 +
 
 +
[[FHIR|Return to the FHIR Main Page]]
 +
 
 +
[[FHIR_Genomics|FHIR Genomics]]

Latest revision as of 16:34, 3 January 2018

Introduction

(This page is under construction and contains information that is still subject to update and correction.) This page describes the Sixteenth FHIR Connectathon that will be held on Saturday Sept. 9 and the morning of Sunday Sept. 10, 2017 in San Diego, CA, USA prior to the Sept. HL7 Working Group Meeting.

Location

The meeting will be held at the host hotel, Hyatt Regency La Jolla at Aventine.

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

Link to the tracking spreadsheet

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 the morning only, and has 2 parts:

  • the formal testing part
  • a mini-showcase where the track leads can demonstrate representative 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.

  • 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