This wiki has undergone a migration to Confluence found Here

Difference between revisions of "FHIR Connectathon 11"

From HL7Wiki
Jump to navigation Jump to search
 
(38 intermediate revisions by 7 users not shown)
Line 14: Line 14:
 
== Themes ==
 
== Themes ==
  
The following are the themes for the Connectathon (each item links to the original proposal).
+
The following are the themes for the Connectathon. Each item links to the original proposal, with the co-ordinators name and email in brackets. More details on each track appear in this document.
  
 +
The patient track is designed for those new to FHIR, and can generally be completed by thos who can code, but have little or no familiarity with FHIR. The other tracks are more specialist in nature, and will generally require some prior work to complete.
 +
 +
* [http://wiki.hl7.org/index.php?title=201601_Patient Patient]
 +
* [http://wiki.hl7.org/index.php?title=201601_FHIR_Terminology_Services Terminology Services]
 
* [http://wiki.hl7.org/index.php?title=201601_CDS_on_FHIR_Connectathon_Track_Proposal CDS on FHIR]
 
* [http://wiki.hl7.org/index.php?title=201601_CDS_on_FHIR_Connectathon_Track_Proposal CDS on FHIR]
 
* [http://wiki.hl7.org/index.php?title=201601_Data_Access_Framework_(DAF) Data Access Framework (DAF)]
 
* [http://wiki.hl7.org/index.php?title=201601_Data_Access_Framework_(DAF) Data Access Framework (DAF)]
Line 23: Line 27:
 
* [http://wiki.hl7.org/index.php?title=201601_MHD Mobile Health Documents (MHD)]
 
* [http://wiki.hl7.org/index.php?title=201601_MHD Mobile Health Documents (MHD)]
 
* [http://wiki.hl7.org/index.php?title=201601_PATCH_Connectathon_Track_Proposal Patch]
 
* [http://wiki.hl7.org/index.php?title=201601_PATCH_Connectathon_Track_Proposal Patch]
* [http://wiki.hl7.org/index.php?title=201601_Patient Patient]
+
* [http://wiki.hl7.org/index.php?title=201601_Scheduling Provider Directories and Scheduling]
* [http://wiki.hl7.org/index.php?title=201601_Scheduling Scheduling]
+
* [http://wiki.hl7.org/index.php?title=201601_Structured_Data_Capture Structured Data Capture (SDC)] [https://join.skype.com/DrdrSm8sqlDi Join skype thread]
* [http://wiki.hl7.org/index.php?title=201601_Structured_Data_Capture Structured Data Capture (SDC)]
 
* [http://wiki.hl7.org/index.php?title=201601_FHIR_Terminology_Services Terminology Services]
 
  
Unlike previous connectathon, all of the tracks described will be available. To assist with management on the day, participants are *strongly encouraged* to add their name to the participants tab of the [https://docs.google.com/spreadsheets/d/1d3c4Uqi3QZNjMrO2e6HRwuq-zXA8-ibk0efNqY4Rds8/edit?usp=sharing tracking spreadsheet] as soon as possible.
 
  
 +
Unlike previous connectathon, all of the tracks described will be available. To assist with management on the day, participants are *strongly encouraged* to add their name to the participants tab of the [https://docs.google.com/spreadsheets/d/1d3c4Uqi3QZNjMrO2e6HRwuq-zXA8-ibk0efNqY4Rds8/edit?usp=sharing tracking spreadsheet] as soon as possible.
  
 
== Connectathon Organization ==
 
== Connectathon Organization ==
Line 54: Line 56:
  
 
If you or your company are interested in participating in the connectathon, please do the following.
 
If you or your company are interested in participating in the connectathon, please do the following.
*Read the '''[http://hl7.org/fhir 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/2016Jan 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/wgm092014/ Register to attend the WGM], and make sure to select the Connectathon option when you do
 
*[http://www.hl7.org/events/wgm092014/ Register to attend the WGM], and make sure to select the Connectathon option when you do
Line 64: Line 66:
  
 
== Registered Participants ==
 
== Registered Participants ==
see the [https://docs.google.com/spreadsheets/d/1d3c4Uqi3QZNjMrO2e6HRwuq-zXA8-ibk0efNqY4Rds8/edit?usp=sharing Tracking Spreadsheet]
+
see the [https://docs.google.com/spreadsheets/d/1d3c4Uqi3QZNjMrO2e6HRwuq-zXA8-ibk0efNqY4Rds8/edit?usp=sharing Tracking Spreadsheet] (Wrong link)
  
 
== Test servers ==
 
== Test servers ==
see the [https://docs.google.com/spreadsheets/d/1d3c4Uqi3QZNjMrO2e6HRwuq-zXA8-ibk0efNqY4Rds8/edit?usp=sharing Tracking Spreadsheet]
+
see the [https://docs.google.com/spreadsheets/d/1d3c4Uqi3QZNjMrO2e6HRwuq-zXA8-ibk0efNqY4Rds8/edit?usp=sharing Tracking Spreadsheet] (wrong link)
  
== 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 'DSTU-2.1 candidate' version of FHIR as described [http://hl7.org/implement/standards/FHIR-Develop/ 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/implement/standards/FHIR-Develop/history.html#history there have been many important changes to the specification].
+
'''Note that this track - as with all tracks - will use the candidate 'DSTU-2.1 candidate' version of FHIR as described [http://hl7.org/fhir/2016Jan/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/2016Jan/history.html#history there have been many important changes to the specification].
  
 
=== Track 1 - Patient ===
 
=== Track 1 - Patient ===
  
Coordinator: [mailto:david.hay25@gmail.com David Hay]
+
Coordinator: [mailto:bpostlethwaite@healthconnex.com.au David Hay]
  
 
If creating a client, this track should require minimal work in advance of the connectathon, though at least a bit of playing is recommended.  If creating a server, advanced preparation will be required, but this scenario should somewhat limit the effort involved.
 
If creating a client, this track should require minimal work in advance of the connectathon, though at least a bit of playing is recommended.  If creating a server, advanced preparation will be required, but this scenario should somewhat limit the effort involved.
Line 117: Line 119:
 
* [http://fhirblog.com/2014/06/29/c-fhir-client/ .net client sample].
 
* [http://fhirblog.com/2014/06/29/c-fhir-client/ .net client sample].
  
 +
=== Track 2 - Terminology Services ===
  
=== Track 2 - Terminology Services ===
 
 
Coordinator: [mailto:rrhausam@gmail.com Rob Hausam]  (There is a dedicated skype chat for terminology services - Contact Rob to be included - skype id rhausam)
 
Coordinator: [mailto:rrhausam@gmail.com Rob Hausam]  (There is a dedicated skype chat for terminology services - Contact Rob to be included - skype id rhausam)
 +
* [http://wiki.hl7.org/index.php?title=201601_FHIR_Terminology_Services#Roles FHIR Terminology Services (Roles)]
 +
* [http://wiki.hl7.org/index.php?title=201601_FHIR_Terminology_Services#TestScripts Test Scripts]
  
==== Service Providers ====
+
==== Terminology Servers ====
 +
*Health Intersections (http://54.226.90.249/open or https://54.226.90.249/closed)
 +
*Apelon
 +
*Lantana (FHIR services on Trifolia)
 +
*CSIRO
 +
*NLM (FHIR services on VSAC) - https://vsac-qa.nlm.nih.gov/fhir/ValueSet
 +
**[http://wiki.hl7.org/index.php?title=201601_NLM_VSAC_server_info further info]
 +
*IMO (FHIR services on IMO ProblemIT)
  
For service providers, implement the following operations from http://hl7.org/fhir/2015May/terminology-service.html:
+
=== Track 3 - CDS on FHIR ===
* $expand
+
* [http://wiki.hl7.org/index.php?title=201601_CDS_on_FHIR_Connectathon_Track_Proposal#Scenarios CDS on FHIR]
* $validate-code (note: there's a set of typos on the terminology service page where this operation is called "validate" but its actually "validate-code" - editorial oversight)
 
* $lookup
 
* $translate (note: there's a typo on the terminology service page where the example has '$validate' not '$translate')
 
  
Service providers are not required to implement all this functionality - it's a lot to do. For new implementers, start at the top and work down (generally)
+
=== Track 4 - Data Access Framework  ===
 +
* [http://wiki.hl7.org/index.php?title=201601_Data_Access_Framework_(DAF)#Scenarios Data Access Framework (DAF)]
  
(note for participants in the first terminology services connectathon: this stream builds on the previous connectathon by adding $lookup and $translate)
+
=== Track 5 - Financial Management ===
 +
* [http://wiki.hl7.org/index.php?title=201601_Financial_Management#Scenarios Financial Management]
  
There's a fairly specific test script with detail descriptions of scenarios at http://gforge.hl7.org/svn/fhir/trunk/connectathons/Paris2015/tx_test_script.xml (for anonymous access, use 'anonymous' with our email as a password). Implementers are not required to implement the full script and pass those particular tests, though it is encouraged to be able to do so
+
=== Track 6 - Clinical Genomics ===
 +
* [http://wiki.hl7.org/index.php?title=201601_FHIR_Genomics#Scenarios FHIR Genomics]
  
note about the test script: you need a version of Sprinkler to execute it (details to be provided). It looks like a resource, and there is a proposal to actually add it as a resource. On the other hand, we'll be considering alternative proposals in Paris as well as that format. Or you can use any other kind of http based test service; there's nothing magic there.
+
=== Track 7 - Lab Order Services ===
 +
* [http://wiki.hl7.org/index.php?title=201601_LabOrderLabReport#Scenarios Lab Order Services]
  
==== Client Consumers ====
+
[http://fhirblog.com/2015/12/17/orders-in-fhir/ fhirBlog: workflow]
  
Any one of
+
=== Track 8 - MHD ===
* do a value set expansion of one of the value sets in the spec
+
* [http://wiki.hl7.org/index.php?title=201601_MHD#Scenarios Mobile Health Documents (MHD)]
* validate a code using the spec against a FHIR value set, a v2 value set, or LOINC or snomed CT
 
* look up a display for a code (most appropriate for v2/FHIR conversion)
 
  
At least one server supports all these operations (http://fhir-dev.healthintersections.com.au). Other servers, including the Apelon server (http://fhir.ext.apelon.com:8081/DtsOnFhirDemo) will support some of those operations
+
=== Track 9 - PATCH  ===
 +
* [http://wiki.hl7.org/index.php?title=201601_PATCH_Connectathon_Track_Proposal#Scenarios Patch]
  
 +
=== Track 10 - Provider Directories and Scheduling ===
 +
* [http://wiki.hl7.org/index.php?title=201601_Scheduling#Scenarios Scheduling] ( [mailto:bpostlethwaite@healthconnex.com.au Brian Postlethwaite])
 +
''This track will attempt to extend on the track from connectathon 10, 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 11 - SDC ===
 +
* [http://wiki.hl7.org/index.php?title=201601_Structured_Data_Capture#Scenarios Structured Data Capture (SDC)] ([mailto:lmckenzie@gevityinc.com Lloyd McKenzie])
  
 
== 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)
 
[[Publicly Available FHIR Servers for testing]]
 
  
 
= Should I come only for the Connectathon? =
 
= Should I come only for the Connectathon? =
Line 158: Line 177:
 
== FHIR User Group ==
 
== 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.  
 
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 201510 Meeting in Atlanta|AID Sunday PM Agenda]] for details.  
+
*See [[AID 201601 Meeting in Orlando|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.
 
*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.
  
Line 175: Line 194:
  
 
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.
 
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 =
 +
 +
 +
== Track 1 - Patient ==
 +
 +
===  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
 +
 +
 +
== Track 2 - Terminology Services ==
 +
 +
== Track 3 - CDS on FHIR ==
 +
 +
===  Results by track ===
 +
 +
'''CDS Hooks'''
 +
 +
3 servers implemented the CDS Hooks specification and 10 clients implemented a CDS Service.
 +
 +
===  Key learnings ===
 +
 +
'''CDS Hooks'''
 +
 +
There was great discussion around prefetching of the FHIR data. Additionally, our experience at the Connectathon led to discussions around how CDS Services advertised their FHIR data needs as well as what hooks they want to subscribe to. Finally, several small bugs were found in the CDS Hooks documentation.
 +
 +
=== Changes next time ===
 +
 +
'''CDS Hooks'''
 +
 +
We intend to repeat the CDS Hooks track at the next Connectathon to further work through the specification. Whereas the first CDS Hooks Connectathon track was focused more on seeing if there was support for CDS Hooks and seeing what use cases others may have, our next Connectathon will focus on refining the specification and fleshing out aspects that are unclear (eg, prefetching, conformance, etc).
 +
 +
=== Overall comments ===
 +
 +
'''CDS Hooks'''
 +
 +
We were thrilled at the broad support and interest from implementors for CDS Hooks. For the next Connectathon, we expect as many participants and will be leverage our existing CDS Hooks community to advertise and promote the Connectathon track.
 +
 +
== Track 4 - Data Access Framework  ==
 +
 +
== Track 5 - Financial Management ==
 +
 +
== Track 6 - Clinical Genomics ==
 +
 +
== Track 7 - Lab Order Services ==
 +
 +
== Track 8 - MHD ==
 +
 +
== Track 9 - PATCH  ==
 +
 +
== Track 10 - Provider Directories and Scheduling ==
 +
===  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
 +
 +
== Track 11 - SDC ==
 +
 +
  
 
= Other References =
 
= Other References =

Latest revision as of 14:14, 27 April 2016

Introduction

(This page is under construction and contains information that is still subject to update and correction.) This page describes the tenth FHIR Connectathon that will be held on Saturday Jan.9 (9am - 5pm++) and the morning (9am - 12.30pm) of Sunday Jan 10, 2015 in Orlando, Florida prior to the HL7 Working Group Meeting (see http://www.hl7.org/events/wgm012016/).

Location

The meeting will be held at the host hotel, Hyatt Regency Orlando, Orlando Florida .

Important notes:

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

Themes

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

The patient track is designed for those new to FHIR, and can generally be completed by thos who can code, but have little or no familiarity with FHIR. The other tracks are more specialist in nature, and will generally require some prior work to complete.


Unlike previous connectathon, all of the tracks described will be available. To assist with management on the day, participants are *strongly encouraged* to add their name to the participants tab of the tracking spreadsheet as soon as possible.

Connectathon Organization

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

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 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 Spreadsheet (Wrong link)

Test servers

see the Tracking Spreadsheet (wrong link)

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 candidate 'DSTU-2.1 candidate' 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 - Patient

Coordinator: David Hay

If creating a client, this track should require minimal work in advance of the connectathon, though at least a bit of playing is recommended. If creating a server, advanced preparation will be required, but this scenario should somewhat limit the effort involved.

Pre-requisites: none


1. Register a new patient

  • Action: (Patient Demographics consumer) creates a new patient and save to Patient Service. The client can assign the Id.
  • Precondition: Patient does not exist in service prior to action
  • Success Criteria: Patient created correctly on server (use browser to inspect Patient)
  • Bonus point: The Patient resource has an extension

>>Note: the requirement for the client to assign the Id has been relaxed. However, if the server assigns the Id, then the client will need to be able to retrieve the Id from the server response or by a patient query.

2. Update a patient

  • Action: (Patient Demographics consumer) updates the patient created in scenario #1 and updates to Patient Service. The patient is retrieved by Id.
  • Precondition: Patient has been created
  • Success Criteria: Patient updated on server (use browser to inspect Patient)
  • Bonus Point #1: Update a patient that has extensions, but leaving the extension untouched.
  • Bonus Point #2: Update a patient that has extensions, and update the extension also.

3. Retrieve Patient history

  • Action: (Patient Demographics consumer) searches the patient Service for the history of a Patient
  • Precondition: There is a patient that has at least one update
  • Success Criteria: Patient's history displayed in interface. (use browser query Patient Service)
  • Bonus point: The UI allows the user to display previous versions of the Patient

4. Search for a patient on name

  • Action: (Patient Demographics consumer) searches the patient Service for patients with a given name
  • Precondition: Patients with that name have been created
  • Success Criteria: patients displayed in interface. (use browser query to confirm)

Some help links:

Track 2 - Terminology Services

Coordinator: Rob Hausam (There is a dedicated skype chat for terminology services - Contact Rob to be included - skype id rhausam)

Terminology Servers

Track 3 - CDS on FHIR

Track 4 - Data Access Framework

Track 5 - Financial Management

Track 6 - Clinical Genomics

Track 7 - Lab Order Services

fhirBlog: workflow

Track 8 - MHD

Track 9 - PATCH

Track 10 - Provider Directories and Scheduling

This track will attempt to extend on the track from connectathon 10, 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 11 - SDC

Servers

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 "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 Sunday PM Agenda for details.
  • Please contact 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 WGM 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 [[1]] 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

Track 1 - Patient

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


Track 2 - Terminology Services

Track 3 - CDS on FHIR

Results by track

CDS Hooks

3 servers implemented the CDS Hooks specification and 10 clients implemented a CDS Service.

Key learnings

CDS Hooks

There was great discussion around prefetching of the FHIR data. Additionally, our experience at the Connectathon led to discussions around how CDS Services advertised their FHIR data needs as well as what hooks they want to subscribe to. Finally, several small bugs were found in the CDS Hooks documentation.

Changes next time

CDS Hooks

We intend to repeat the CDS Hooks track at the next Connectathon to further work through the specification. Whereas the first CDS Hooks Connectathon track was focused more on seeing if there was support for CDS Hooks and seeing what use cases others may have, our next Connectathon will focus on refining the specification and fleshing out aspects that are unclear (eg, prefetching, conformance, etc).

Overall comments

CDS Hooks

We were thrilled at the broad support and interest from implementors for CDS Hooks. For the next Connectathon, we expect as many participants and will be leverage our existing CDS Hooks community to advertise and promote the Connectathon track.

Track 4 - Data Access Framework

Track 5 - Financial Management

Track 6 - Clinical Genomics

Track 7 - Lab Order Services

Track 8 - MHD

Track 9 - PATCH

Track 10 - Provider Directories and Scheduling

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

Track 11 - SDC

Other References