FHIR Connectathon 6
- 1 Introduction
- 2 Themes
- 3 Connectathon Organization
- 4 Enrollment
- 5 Connectathon Planning Team
- 5.1 Registered Participants
- 5.2 Connectathon tracks
- 5.2.1 Track 1 - Patient
- 5.2.2 Track 2 - Questionnaire
- 5.2.3 Track 3 - Experimental
- 5.3 Servers
- 5.4 Post-connectathon activities
This page describes the sixth FHIR connectathon that will be held on Saturday May 3 and the morning (9am - 12.30pm) of Sunday May 4, 2014 in Phoenix Arizona prior to the HL7 Working Group Meeting (see http://www.hl7.org/events/wgm052014/).
NOTE: This is a placeholder page - further details will be added, particularly details of the scenarios closer to connectathon.
To be determined
This connectathon will have 3 separate themes
Basic patient scenarios that will be tested
The patient resource is 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:
The Questionnaire resource is a structured set of questions and their answers. The Questionnaire may contain questions, answers or both. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying questions.
It's primary use is to facilitate the capture of information via forms based interfaces, which can then be used to generate and/or update more specific resources.
Here is some extra information on Questionnaires:
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.
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
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, 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
- Health Intersections / Grahame Grieve.
- Furore / Ewout Kramer.
- Gordon Point Informatics / Lloyd McKenzie.
- Orion Health / David Hay.
This section lists the scenarios that are proposed for this connectathon. More detail will be added when approved. The scenarios are grouped according to two tracks. Track 1 is for those new to FHIR and requires minimal preparation in advance of the connectathon (at least for client applications). Track 2 is for those with some experience with the use of FHIR (or willing to devote up-front time to connectathon preparation) and exercises a more complete set of behavior designed to reflect a full production experience.
Track 1 - Patient
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.
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: patients 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)
Track 2 - Questionnaire
1. Retrieve a completed Questionnaire Instance
- Action: Download a completed Questionnaire and display to the user
- Precondition: completed Questionnaires exist on the server
- Success Criteria: A rendition of the Questionnaire is presented
- Bonus point: Allow the user to display all the completed questionnaires for a given user and select one to display
- Bonus point: Allow the Questionnaire to be presented in a different format (like a mobile device)
2. Retrieve a Questionnaire Template
- Action: Download a Questionnaire defined as a template, and render a User Interface from it
- Precondition: Questionnaire templates exist on the server
- Success Criteria: A User Interface matching the Questionnaire is presented
- Bonus point: Provide a list of templates for the user to select from
- Bonus point: Choose a template that references an external (or contained) ValueSet, and use the ValueSet contents to display a selection list
3. Save a Questionnaire Instance
- Action: Complete a Questionnaire and save it to a server
- Precondition: Questionnaire template previously downloaded
- Success Criteria: The completed Questionnaire can be retrieved and displayed
- Bonus point: Pre-populate the Questionnaire from information that already exists in the client system
4. Create a Questionnaire template
- Action: Create a new Questionnaire as a template and save it to a server
- Precondition: None
- Success Criteria: The Questionnaire can be retrieved and used to generate a completed Questionnaire instance
- Bonus point: Implement a template that uses some of the standard extensions - like show/hide...
5. Generate resources
- Action: Create external resources from a completed Questionnaire
- Precondition: completed Questionnaire send to server
- Success Criteria: The Questionnaire and the resources generated from it can be retrieved from the server
- Bonus point: There is a reference to the external resource in the Questionnaire.
- Bonus point: There is a reference to the Questionnaire from the generated resource in some way.
Note: This scenario could be server or client initiated
6. Pre-populate a questionnaire
- Action: Return a questionnaire instance pre-populated with information referenced in a provided CCDA Document
- Precondition: CCDA Document and Questionnaire definition exist. Concept map indicates linkage between document data elements and Questionnaire definition
- Success Criteria: A partially-populated questionnaire instance is returned containing appropriate data from the supplied document
- Bonus point: Do the same thing with data drawn from a FHIR document
Track 3 - Experimental
Will depend on what attendees want to do...
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.