FHIR Connectathon 3
- 1 Introduction
- 2 Themes
- 3 Connectathon Organization
- 4 Enrollment
- 5 Connectathon Planning Team
- 5.1 Registered Participants
- 5.2 Actors
- 5.3 Scenarios
- 5.4 Scenarios from previous connectathon for review
- 5.5 Servers
- 5.6 Other References
This page describes the third FHIR connectathon that will be held on Saturday May 4 and the morning (9am - 12.30pm) of Sunday May 5 2013 in Atlanta, Georgia prior to the HL7 Working Group Meeting (see http://www.hl7.org/events/wgm052013/).
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:
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.
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' session where participants can demonstrate their work to the group, if they choose.
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
Connectathon Planning Team
- Health Intersections / Grahame Grieve.
- Furore / Ewout Kramer.
- Gordon Point Informatics / Lloyd McKenzie.
- Orion Health / David Hay.
- YouCentric / Andy Stechishin, Dennis Rodriguez, Lorraine Constable - patient scenarios
- NProgram / Rik Smithies - patient scenarios
- Blue Wave / Hugh Glover - client actors
- HealthFire / Jean Duteau & Joginder
- Chuck Jaffe / Observer
- Robert Hausam / Observer
- Lantana / Dale Nelson - document / observer
- (remote) Brett Esler / Patient Provider, Document Repository, Patient Demographics Feed
- Odysseas Pentakalos / Observer
- Patient Consumer
- this actor uses the patient/person information in a document registry to provide patient search/context
- Patient provider
- a server that stores patient resources
- Document Creator
- an actor that can create a FHIR document
- Document Consumer
- this actor extends Patient Consumer to search, retrieve and display patient-related documents
- Document Repository
- this actor provides server support for patient, person, XdsEntry, XdsFolder resources + Binary resources. For a bonus, XdsEntry2 should also be supported
- Document Registry
- this actor subscribes to one or more repositories using atom feeds for patient/person/XdsEntry/XdsFolder + bonus: XdsEntry2
- Patient demographics feed
- This actor generates creates/updates/link/unlink for patient and person information (default for this, person and patient example resources from the specification)
- Document provider
- This actor pushes documents to a repository and/or a registry (for the purposes of the connectathon, the registry ignores binaries)
- XDS Bridge
- This is a document provider that functions by accepting XDS.b submission sets, and converting them to FHIR batches
List of proposed scenario's
This section lists the scenarios that are proposed for this connectathon. More detail will be added when approved
1. Register a new patient
- Action: (Patient Demographics consumer) creates a new patient and save to Patient Service. The client assigns 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
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: Patients with that name have been created
- 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)
document / xds scenarios
- search for documents from xds registry (xdsEntry2) for a patient
- update an exsting document
- show document versions
- create and submit a new document
? do we also want scenarios directly against a /document endpoint rather than /xdsentry2 ?
Scenarios from previous connectathon for review
Register a patient
- Action: (Patient Demographics feed) creates or updates patient and person to (Document Registry)
- Precondition: Patient/Person does or does not exist on Document Registry (both conditions)
- Success Criteria: Patient/Person updated correctly on server (use browser to inspect person and patient)
- Bonus #1: testing for patient linking/unlinking
Submit a document
- Action: (Document Provider) creates or updates documents to (Document Repository)
- Precondition: Document Does not exist on document repository
- Precondition: Patient/Person already exists on registry
- Success criteria: document updated correctly on server (use browser to inspect) (check folders as well)
- bonus: use XdsEntry2
Find a patient
- Action: (Patient Consumer) searches and finds a patient record on (Document Registry). Search by name, gender, date of birth
- Success Criteria: patients can be found and displayed
Find a document
- Action: (Document Consumer) searches and finds documents on (Document Repository) or (Document Registry). Search by code, type, author, folder
- Action: (Document Consumer) retrieves document
- Success Criteria: documents can be found, retrieved, an displayed
- Last Connectathon: FHIR Connectathon 2 (Jan 12/13, 2013)