20160204 OO FHIR conCall
| HL7 OO on FHIR (for Orders and Observations) Call in details: |
Date: 2016/02/04 2015 - 02:00 PM (Eastern Time, GMT -04 DST) | |
| Quorum = chair + 4 no | ||
| Co chairs | Chair | Notetaker | |
|---|---|---|---|
| Riki Merrick | |||
| Rob Hausam | |||
| Lorraine Constable | |||
| Patrick Lloyd | |||
| Ken McKaslin | |||
| Hans Buitendijk |
| Attendees | |
|---|---|
| X | Eric Haas |
| Riki M | |
| Paul K | |
| Jose Costa-Teixicara | |
| Dan R | |
| X | John Moehrke |
| Kamalini | |
| X | Mark Jones |
| X | Rob Hausam |
| Margaret D | |
Agenda
- Roll Call
- Agenda Check
- Minutes from
- Agenda
- Proposed disposition for remaining Device comments
Balloters •Eric Haas•Michelle Miller
pulled
*8925 add UDI string HRF formats to Identifer type codes
HRF v AIDC resolutions : ascii control characters can cause systems to croak, X12 can't support, Jose has use case - where item scanned natively and not examined - issue with Device.type being 1..1,
example HRF -(01)ABC123(10)140127(123)ABCGSF AIDC - ]d2010761234500255210D567<GS>17160530
Need to discuss offline further with Paul, Jose and others before bringing back for vote. I am reluctant to exclude a format from standard even though is problematic. (not our fault)
Discussed and created resolution for:
*9111 fix example add more udi examples (Eric Haas) None *8929 extensions for GUDID data elements (Eric Haas) Persuasive
Added new comments
*9449 add extension to Device for HCT/IP and map to corresponing udi component in mapping. (Eric Haas) Persuasive
Propose for Next weeek review and propose actual wording for ( also a Device QA task to review comments and descriptions ) expecially in light of the changes from udi to udiCarrier.
*8926 Provide Clearer guidance for UDI components (Eric Haas) Persuasive
- AOB (Any Other Business)
Minutes
Next Steps
| Actions (Include Owner, Action Item, and due date) | |||
| Next Meeting/Preliminary Agenda Items |
Back to OO_on_FHIR
