This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20160128 OO FHIR conCall"
Jump to navigation
Jump to search
(→Agenda) |
m (→Agenda) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 61: | Line 61: | ||
** DiagnosticOrder (DO)event complex element (Jose C-T) | ** DiagnosticOrder (DO)event complex element (Jose C-T) | ||
***stemming from workflow discussion could replace this complex structure in DO with the Idea is that Order/OrderResponse(aka Task, Action etc) generate versions of the Request Resource (or new instances of Request Resource )instead of having several 'events' | ***stemming from workflow discussion could replace this complex structure in DO with the Idea is that Order/OrderResponse(aka Task, Action etc) generate versions of the Request Resource (or new instances of Request Resource )instead of having several 'events' | ||
| − | |||
| − | |||
| − | |||
** Proposed dispositions for .comment build warnings | ** Proposed dispositions for .comment build warnings | ||
| − | ** look at #7622 for context | + | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9346 9346] - DataElement QA generated warning that need to determine if .comment is string or annotation type (Eric Haas) None |
| − | ** new gForge comment for Specimen note | + | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9347 9347] DiagnosticReport QA build error -decision whether .image.comment should be 0..1 string or 0..* Annotation (Eric Haas) None |
| − | keep all comments as strings for oo block vote before sending to mnm. | + | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9348 9348] Specimen QA generated warning that need to determine if Collector.comment is string or annotation type (Eric Haas) None |
| − | + | *[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9345 9345] QA generated warning that need to determine if .comment is string or annotation type (Eric Haas) Persuasive | |
| − | + | *** look at #7622 for context | |
| + | *** add new gForge comment for Specimen note 0..* Annotation - [#9392] | ||
| + | ***keep all comments as strings for oo block vote before sending to mnm. | ||
** Proposed disposition for remaining Device comments | ** Proposed disposition for remaining Device comments | ||
Latest revision as of 23:37, 28 January 2016
| HL7 OO on FHIR (for Orders and Observations) Call in details: |
Date: 2016/01/28 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 | |
| X | Jose Costa-Teixicara |
| Dan R | |
| Cooper Thomas | |
| Kamalini | |
| X | Mark Jones |
| X | Rob Hausam |
| Margaret D | |
Agenda
- Roll Call
- Agenda Check
- Minutes from
- Agenda
- DiagnosticOrder (DO)event complex element (Jose C-T)
- stemming from workflow discussion could replace this complex structure in DO with the Idea is that Order/OrderResponse(aka Task, Action etc) generate versions of the Request Resource (or new instances of Request Resource )instead of having several 'events'
- Proposed dispositions for .comment build warnings
- DiagnosticOrder (DO)event complex element (Jose C-T)
*9346 - DataElement QA generated warning that need to determine if .comment is string or annotation type (Eric Haas) None *9347 DiagnosticReport QA build error -decision whether .image.comment should be 0..1 string or 0..* Annotation (Eric Haas) None *9348 Specimen QA generated warning that need to determine if Collector.comment is string or annotation type (Eric Haas) None *9345 QA generated warning that need to determine if .comment is string or annotation type (Eric Haas) Persuasive
- look at #7622 for context
- add new gForge comment for Specimen note 0..* Annotation - [#9392]
- keep all comments as strings for oo block vote before sending to mnm.
- Proposed disposition for remaining Device comments
Balloters •Eric Haas•Michelle Miller
*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 *9111 fix example add more udi examples (Eric Haas) None *8926 Provide Clearer guidance for UDI components (Eric Haas) Persuasive *8929 extensions for GUDID data elements (Eric Haas) Persuasive
- Other Comments if time permits
- 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
© 2015 Health Level Seven® International
