Difference between revisions of "FHIR Connectathon 6"
(Created page with "== Introduction == This page describes the sixth FHIR connectathon that will be held on Saturday May 4 and the morning (9am - 12.30pm) of Sunday May 5 2013 in Atlanta, Georgia...") |
|||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | This page describes the sixth FHIR connectathon that will be held on Saturday May | + | This page describes the sixth FHIR connectathon that will be held on Saturday May 2 and the morning (9am - 12.30pm) of Sunday May 3 2013 in Phoenix Arizona prior to the HL7 Working Group Meeting (see http://www.hl7.org/events/wgm052014/). |
===Location=== | ===Location=== | ||
| − | + | To be determined | |
== Themes == | == Themes == | ||
Revision as of 04:05, 24 February 2014
Contents
Introduction
This page describes the sixth FHIR connectathon that will be held on Saturday May 2 and the morning (9am - 12.30pm) of Sunday May 3 2013 in Phoenix Arizona prior to the HL7 Working Group Meeting (see http://www.hl7.org/events/wgm052014/).
Location
To be determined
Themes
This connectathon will have 3 separate themes
Basic patient scenarios that will be tested
The patient resource is reasonably well defined, and these scenarios are intended for a user new to FHIR to interact with it at a basic level. It will include scenarios that cover:
- search
- 'CRUD'
- history
- extensions
Document scenarios
These scenarios are to test and validate the document management capability of FHIR. The document resource (either as a separate endpoint or using bundles) is less 'exercised' than patient resources, and is more complex. These scenarios are intended for people who have some familiarity with FHIR already, and also have the purpose of validating that the overall design of FHIR documents is fit for purpose. Some of the scenarios assume the use of the xdsEntry2 resource to store and retrieve documents, others will act directly against document resource endpoints.
Specification evolution
These are scenarios that are used by the core team to test assumptions made when developing the specification itself. They are intended for those with a good understanding of FHIR, and who don't mind the constant change that occurs during these scenarios.
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
Enrollment
If you or your company are interested in participating in the connectathon, please do the following.
- Read 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.
- Send an email expressing interest to any of the Connectathon Planning team below. Be sure to include a link to your product's website (if available) and to state which scenarios your product will be engaged in.
Space at the venue is limited to 30 attendees, so please register your interest 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
- a 'mini-showcase' session where participants can demonstrate their work to the group, if they choose.
Connectathon Planning Team
- David Hay, Orion Health
- Brian Pech, Kaiser Permanente
- Grahame Grieve, Health Intersections Pty Ltd
Registered Participants
- Health Intersections / Grahame Grieve.
- Furore / Ewout Kramer.
- Gordon Point Informatics / Lloyd McKenzie.
- Orion Health / David Hay.
