20151211 OO FHIR conCall
| HL7 OO on FHIR (for Orders and Observations) Call in details: |
Date: 2015-12-11 2015 - 02:00 PM (Eastern Time, GMT -04 DST) | |
| Quorum = chair + 4 yes | ||
| Co chairs | Chair | Notetaker | |
|---|---|---|---|
| Riki Merrick | X | X | |
| Rob Hausam | |||
| Lorraine Constable | |||
| Patrick Lloyd | |||
| Ken McKaslin | |||
| Hans Buitendijk |
| Attendees | |
|---|---|
| X | Eric H |
| X | Riki M |
| X | Paul K |
| X | Jose C-T |
| X | Dan R |
| X | Cooper Thomas |
| X | Kamalini |
| X | Mark J |
Agenda
- Roll Call
- Agenda Check
- Minutes from
'Deferred Trackers to discuss connectathon
- Review Tracker Items - Device resource: [1]
*8925 add UDI string HRF formats to Identifer type codes (Eric Haas) None *8944 Add boundary clarification to indicate whether medical supplies are Devices or Medications (Michelle Miller) None *8926 Provide Clearer guidance for UDI components (Eric Haas) Persuasive *8929 extensions for GUDID data elements (Eric Haas) Persuasive *7254 2015May core #373 - UDI doesn't identify repository/jurisdiction (Paul Knapp) Persuasive with Mod In Person
Device resource: [2]
- Review Tracker Items - Order/OrderResponse: [3]
*6264 change name of Order/OrderResponse to reflect that is workflow
- Connectathon
- AOB (Any Other Business)
Minutes
Connectathon planning – deadline is next week
No changes to resources affecting testing (like renaming the Order / OrderResponse resource, but will not be applied by then)
WIKI PAGE LINK Asked Rene Spronk if interested in adding messaging track to this. reviewed actors and test scenario and script
- Step 1: Create order and then store in order management on EHR-S
- Step 2: Send the order out to the lab (Rob H is building the lab server to receive the order)
- Can be a RESTFUL create on the lab server, or could be a message creation
- Only difference is the endpoint of where the order ends up
- The LIS then can accept the order or not – that is a second resource = the Order that groups multiple requests for different places – that is the requisition = Order Resource
- 1 order with 3 things, one 1 can do, 1 for lab B and 1 to lab C – create 2 separate orders, one for each lab
- Test 1:
- Order for one test to one source
- Test 2:
- Order for one test to one source PLUS the order resource
- Test 3:
- Order for more than one test to more than one source
- Test 1:
FHIR server is so that it can be shared
- Server is used as internally storage system – use the client like a browser or between organizations as public entities
- 1 server for order status = submitted, = completed, = canceled?
- Accept the order, and then send the result back – match for patient, order number etc.
- Order to fulfillment system
- Aim for single server test right now
So far no one signed up for specimen collection – the test case currently ignores the specimen collection
It only becomes a workflow for specimen collection to gather multiple orders to collect the right amount of specimen
Should we still add the requisition (Order/OrderResponse) to the single element order?
- Not that different when doing the simplest use case
Step 1A – what if the order is not saved somewhere UNTIL it goes out (because the resource is not created until the order is complete?
Next Steps
| Actions (Include Owner, Action Item, and due date) | |||
| Next Meeting/Preliminary Agenda Items |
Back to OO_on_FHIR
© 2015 Health Level Seven® International
