This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "20160519 OO FHIR conCall"

From HL7Wiki
Jump to navigation Jump to search
()
()
 
(3 intermediate revisions by the same user not shown)
Line 35: Line 35:
 
|||Riki M
 
|||Riki M
 
|-
 
|-
| ||Hans Buitendijk  
+
|X ||Hans Buitendijk  
 
|-
 
|-
 
|||Jose Costa-Teixicara
 
|||Jose Costa-Teixicara
Line 45: Line 45:
 
| ||Kamalini
 
| ||Kamalini
 
|-
 
|-
|||Mark Jones
+
|X||Lloyd McKenzie
 
|-
 
|-
 
|X||Rob Hausam
 
|X||Rob Hausam
 
|-
 
|-
| ||Margaret D
+
|X ||Andrew Quinn
  
 
|}
 
|}
Line 60: Line 60:
  
 
* Update on SDC on FHIR (Lloyd)
 
* Update on SDC on FHIR (Lloyd)
* Review outstanding Trackers for DataElement ( hopefully Lloyd and possibly Clem can join)
+
**2 parallel guide
 +
**#Questionnaire/QuestionnaireAnswer
 +
**#Maintaining and Curating DEs
 +
**Mechanism for prepopulation of QuestionnaireAnswer using the DataElement resource. But to date there has not been a lot of uptake.  Concern about information loss going through DE.  Recent updates to QuestionnaireAnswer now allow direct mappings in the resource bypassing DataElement.
 +
**Data element curation: In research would like a lot consistency even when the data is coming from a wide variety of sources ( e.g. case reporting, registries).  Thus the need for data element curation.  ***Not that many that actually do this '5-10' in USA.
 +
**Master files and DE (note this not main use case for SDC but is for the Resource)
 +
***Still a WIP.
 +
***Other stuff going onin FHIR that is competing with using DataElement for Master Files -"logical model" (resource that not intended to be sent over the wire) discussion about using structuredefintion and notion of DE getting subsumed by this is a continuing conversation.  Difficult to resolve the notion of using a StructureDefintion for a data element.
  
 +
*Next Steps:
 +
**OO - lab master files:  **direct relationship between observation and DataElement through
 +
*** In Scope : lab
 +
*** Out of Scope: procs, meds, locations
  
'''DataElement''' -  To be covered on May 19th OO on FHIR call
 
  
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6095 6095] styleSensitive isn't clear enough (Lloyd McKenzie) None
+
*Discussion of creating lab master in FHIR baed on looking at the v2 EDOS IG data elements as a presumptive model
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7248 7248] 2015May core #308 - Various opinions on data element (Clem McDonald) None '''In Person'''
+
 
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6316 6316] Dataelement is insufficient for Master Files (Eric Haas) Not Persuasive
+
  Execution/performance piece = New Resource (answers the how do submit and prerequisites)
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8884 8884] Need extension for min valueSet for DataElement.element.mapping.language (Lloyd McKenzie) Persuasive
+
    possibly could be used for precedures too
 +
    links to
 +
    - specimen piece = DE
 +
    - cost= piece
 +
    - linkto DateElement  = Type of data and  description, normal range, terminolog (stuff that would normally reside in a database field or questionnaire question.)
 +
   
 +
    profiling piece- how profile libraries fit in - context of filler and placer
 +
 
 +
 
 +
  Data Element means different things to different people ( e.g. a code  vs a field in a V2 message )
 +
  LOINC is a mini data element and commonality and overlap with a field in V2.
 +
 
 +
 
 +
* Reviewed outstanding Trackers for DataElement ( hopefully Lloyd and possibly Clem can join)
 +
 
 +
 
 +
 
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6095 6095] styleSensitive isn't clear enough (Lloyd McKenzie) PUNT TO FHIRI
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7248 7248] 2015May core #308 - Various opinions on data element (Clem McDonald) None '''In Person''' CREATE a logical model in FHIR to flesh out and see if that answer his questions
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=6316 6316] Dataelement is insufficient for Master Files (Eric Haas) CREATE a logical model in FHIR to flesh out
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8884 8884] Need extension for min valueSet for DataElement.element.mapping.language (Lloyd McKenzie) PUNT TO VOCAB
  
 
==Minutes==
 
==Minutes==

Latest revision as of 19:32, 19 May 2016

HL7 OO on FHIR (for Orders and Observations)

Call in details:
Phone: +1 770-657-9270, Passcode: 398652

Join the meeting at:
https://join.me/vernetzt.us

Date: 2016/05/19
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
X Hans Buitendijk
Jose Costa-Teixicara
Dan R
X Jonathan Harber
Kamalini
X Lloyd McKenzie
X Rob Hausam
X Andrew Quinn

  • Update on SDC on FHIR (Lloyd)
    • 2 parallel guide
      1. Questionnaire/QuestionnaireAnswer
      2. Maintaining and Curating DEs
    • Mechanism for prepopulation of QuestionnaireAnswer using the DataElement resource. But to date there has not been a lot of uptake. Concern about information loss going through DE. Recent updates to QuestionnaireAnswer now allow direct mappings in the resource bypassing DataElement.
    • Data element curation: In research would like a lot consistency even when the data is coming from a wide variety of sources ( e.g. case reporting, registries). Thus the need for data element curation. ***Not that many that actually do this '5-10' in USA.
    • Master files and DE (note this not main use case for SDC but is for the Resource)
      • Still a WIP.
      • Other stuff going onin FHIR that is competing with using DataElement for Master Files -"logical model" (resource that not intended to be sent over the wire) discussion about using structuredefintion and notion of DE getting subsumed by this is a continuing conversation. Difficult to resolve the notion of using a StructureDefintion for a data element.
  • Next Steps:
    • OO - lab master files: **direct relationship between observation and DataElement through
      • In Scope : lab
      • Out of Scope: procs, meds, locations


  • Discussion of creating lab master in FHIR baed on looking at the v2 EDOS IG data elements as a presumptive model
 Execution/performance piece = New Resource (answers the how do submit and prerequisites)
   possibly could be used for precedures too
   links to
   - specimen piece = DE
   - cost= piece
   - linkto DateElement  = Type of data and  description, normal range, terminolog (stuff that would normally reside in a database field or questionnaire question.)
    
    profiling piece- how profile libraries fit in - context of filler and placer 
 
 
 Data Element means different things to different people ( e.g. a code  vs a field in a V2 message )
 LOINC is a mini data element and commonality and overlap with a field in V2.
 
 
  • Reviewed outstanding Trackers for DataElement ( hopefully Lloyd and possibly Clem can join)


  • 6095 styleSensitive isn't clear enough (Lloyd McKenzie) PUNT TO FHIRI
  • 7248 2015May core #308 - Various opinions on data element (Clem McDonald) None In Person CREATE a logical model in FHIR to flesh out and see if that answer his questions
  • 6316 Dataelement is insufficient for Master Files (Eric Haas) CREATE a logical model in FHIR to flesh out
  • 8884 Need extension for min valueSet for DataElement.element.mapping.language (Lloyd McKenzie) PUNT TO VOCAB

Minutes

Next Steps

Actions (Include Owner, Action Item, and due date)
Next Meeting/Preliminary Agenda Items

2015mmdd_OO_FHIR_concall


Back to OO_on_FHIR