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

Difference between revisions of "20160421 OO FHIR conCall"

From HL7Wiki
Jump to navigation Jump to search
()
Line 3: Line 3:
 
'''Call in details: <br>Phone: +1 770-657-9270, Passcode: 398652 '''<br/>
 
'''Call in details: <br>Phone: +1 770-657-9270, Passcode: 398652 '''<br/>
 
'''Join the meeting at: <br>https://join.me/vernetzt.us''' <br/>
 
'''Join the meeting at: <br>https://join.me/vernetzt.us''' <br/>
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2016/04/21 '''<br/> '''2015 - 02:00 PM (Eastern Time, GMT -04 DST)'''
+
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2016/04/28 '''<br/> '''2015 - 02:00 PM (Eastern Time, GMT -04 DST)'''
 
|-
 
|-
|colspan="3" align="center" style="background:#f0f0f0;"| Quorum = chair + 4 '''yes'''
+
|colspan="3" align="center" style="background:#f0f0f0;"| Quorum = chair + 4 '''no'''
 
|}
 
|}
  
Line 35: Line 35:
 
|||Riki M
 
|||Riki M
 
|-
 
|-
|X ||Hans Buitendijk  
+
| ||Hans Buitendijk  
 
|-
 
|-
|X||Jose Costa-Teixicara
+
|||Jose Costa-Teixicara
 
|-
 
|-
 
| ||Dan R
 
| ||Dan R
Line 60: Line 60:
  
  
#* Review Device QA criteria for FMM proposal - not done
+
* Review Device QA criteria for FMM proposal - not done
# [http://hl7-fhir.github.io/supplyrequest.html SupplyRequest] and [http://hl7-fhir.github.io/device.html/supply delivery SupplyDelivery]
+
* Review outstanding Trackers for WGM
  
 +
Topic:
 +
'''Workflow'''  Mon Q 3-4 is Workflow discussion.  Will await outcome of Workflow Group before addressing these items:
  
'''Look at boundaries between SupplyRequest, [http://hl7-fhir.github.io/deviceuserequest.html  DeviceUseRequest], and [http://hl7-fhir.github.io/visionprescription.html VisionPrescription] Resources'''
 
  
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=5304 5304] Jan 2015 Ballot Comment #183 (David Tao) Considered for Future Use
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=5468 5468] Jan 2015 Ballot Comment #404 (Riki Merrick) Considered for Future Use
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7756 7756] 2015May core #1077 - Document Order Request/Response pattern (Keith Boone) Considered for Future Use
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8445 8445] Allow Order source to be a Patient (David Hay) Considered for Future Use
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8478 8478] replace element names .source and .target with .Placer and .Filler (Clem McDonald) Considered for Future Use
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8755 8755] add an orderType to support workflow variations (Jose Costa) Considered for Future Use
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8756 8756] Create an extension for a dynamically calculated workflow status (Jose Costa) Considered for Future Use
  
 +
'''DiagnosticOrder'''
  
The boundary Supply-DeviceUseRequest would be the same as between Supplyand medicationOrder (and others): The latter is for the patient-specific order, specifying part of a treatment.
+
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9187 9187] flatten out Diagnostic Order, move specimen collection to ProxcedureRequest (Eric Haas) None
If, to provide for that, any supply/resupply has to be done (e.g. bulk resupply of stock) then we use the SupplyRequest. Meaning that the Supply can be used to order a bunch of devices to refill stock, but not implying a treatment.
+
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9852 9852] Add timing atttributes to DiagnosticOrder (Hans Buitendijk) Persuasive with Mod
{| class="wikitable"
 
|-
 
|
 
 
 
Patient-specific treatment-related
 
|
 
DeviceUse
 
|-
 
|
 
 
 
Bulk supply, treatment-independent
 
|
 
Supply.
 
|}
 
 
 
There is a gray zone where both resources wculd work. e.g. from an order, the clinic purchasing department decides to order that device for that patient from the manufacturer. It's a patient-specific order, but may not contain the details for the treatment (for example: the name may be conveyed for labeling purposes) this could be Supply.
 
 
 
 
 
This leads to question Whether SupplyRequest should reference Patient element or just use the reason resource generically  [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9861 #9861]
 
 
 
 
 
Likely need a special request comment/annotation on the resource as well. [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9862 #9862]
 
 
 
 
 
VisionPrescription not needed the custom detail should be attribute of ordered item DeviceUseRequestdevice  (i.e. Device) but this is a Device specialization (Profile) or Resource or separate resource is an open question for FMG.
 
 
 
especially for common stuff like , glasses, hearing aid, teeth, and prothetics.
 
 
 
'''As well as [http://hl7-fhir.github.io/device.html/supply delivery SupplyDelivery] and [http://hl7-fhir.github.io/device.html/medication dispense Medication Dispense]''''
 
 
 
How is Delivery different from Dispense?
 
 
 
Workflow
 
  | Requests: MedicationOrder, DeviceUseRequest, SupplyRequest
 
  | Delivery: SupplyDelivery,
 
  | Dispense:  MedDispense  (here is med - take this BID etc....),  '`no DeviceDispense``, SupplyDispense not needed?
 
  |  Admin/Use:
 
  V
 
 
 
NOTE: Inconsistent use of request resources between different WG. ( no DeviceDispense ) - Bring up at FMG
 
 
 
 
 
Wheelchair example :  delivery = dispense?  Delivery - act of sending not necessay of being received. vs Dispense Patient get it.
 
 
 
'''Other Notes'''
 
 
 
*From and to location missing in SupplyRequest [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9863 #9863]
 
 
 
*From location missing in SupplyDelivery[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9863 #9863]
 
 
 
 
 
*There should be separate instances of SupplyDelivery for each way point
 
**.destinations where supply sent to, this is like a rreport of something sent to location A which is either an intermediate or final destination.
 
**Issue brought on whether SupplyDelivery's.destination changes the resource statuses meaning
 
**Suggest that Task indicates fulfilment of request not the SupplyDelivery
 
 
 
 
 
 
 
 
 
 
 
===xxxRequest comparison===
 
 
 
{| class="wikitable"
 
|-
 
|
 
'''RequestResource'''
 
 
 
|
 
'''RequestResource'''
 
 
 
| colspan="6" |
 
'''Template'''
 
 
 
|-
 
|
 
'''SupplyRequest''' Inventory
 
 
 
|
 
'''DeviceUseRequest'''Clinical Use
 
 
 
|
 
'''Name'''
 
 
 
|
 
'''Flags'''
 
 
 
|
 
'''Card.'''
 
 
 
|
 
'''Type'''
 
 
 
|
 
'''W5'''
 
 
 
|
 
'''Description & Constraints'''
 
 
 
|-
 
|
 
identifier
 
 
 
|
 
identifier
 
 
 
|
 
identifier   
 
 
 
|
 
S
 
 
 
|
 
0..*
 
 
 
|
 
Identifier
 
 
 
|
 
id
 
 
 
|
 
Business identifier for request/order
 
 
 
|-
 
|
 
 
 
 
 
|
 
 
 
 
 
|
 
basedOn
 
 
 
|
 
S
 
 
 
|
 
0..*
 
 
 
|
 
Reference()
 
 
 
|
 
 
 
 
 
|
 
Request fulfilled by this request
 
 
 
|-
 
|
 
 
 
 
 
|
 
 
 
 
 
|
 
parent
 
 
 
|
 
S
 
 
 
|
 
0..1
 
 
 
|
 
Identifier
 
 
 
|
 
 
 
 
 
|
 
Composite request this is part of
 
 
 
|-
 
|
 
status
 
 
 
|
 
status
 
 
 
|
 
status
 
 
 
|
 
!S
 
 
 
|
 
1..1
 
 
 
|
 
code
 
 
 
|
 
status
 
 
 
 
 
draft | active | suspended
 
  
|-
 
|
 
  
 +
'''DiagnosticReport'''
  
|
+
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9038 9038] Culture (James Agnew) None
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9671 9671] DiagnosticReport - add support for linking reports together (Michelle Miller) None
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9859 9859] combine DiagnostReport.conclusion and DiagnostReport.codeDiagnosis (Eric Haas) None
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9206 9206] DiagnosticReport element to include textual narrative of the diagnostic assessment (Sean Moore) Not Persuasive
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9433 9433] Observation.issued and DiagnosticReport.issued (Hans Buitendijk) Not Persuasive
  
  
|
+
'''Observation'''
category
 
  
|
+
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9375 9375] Remove invariant from Observation.component.code (Michelle Miller) None
!S
+
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9774 9774] Create required core profile for Vital Sign (Eric Haas) None '''In Person'''
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9857 9857] change Observation.category from Example to Extensible (Eric Haas) None
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9880 9880] element for indicated who or what changes the status (Hans Buitendijk) None
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9433 9433] Observation.issued and DiagnosticReport.issued (Hans Buitendijk) Not Persuasive
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9543 9543] Multieple Observation Categories (Hans Buitendijk) Not Persuasive
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9676 9676] Add Observation.component.interpretation (Michelle Miller) Persuasive with Mod
  
|
 
1..1
 
 
|
 
CodeableConcept
 
 
|
 
class
 
 
 
proposal | plan | orig. order | encoded +
 
 
|-
 
|
 
    orderedItem
 
 
(reference to Medication|Substance|Device)
 
 
 
 
|
 
Device (reference)
 
 
|
 
code
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
CodeableConcept
 
 
|
 
what
 
 
|
 
What’s being requested/ordered
 
 
|-
 
|
 
  patient
 
 
(Is this need for supply can use reason for this since not a patient specific resource)
 
 
 
 
|
 
Subject( should be Patient)
 
 
|
 
subject
 
 
|
 
S
 
 
|
 
1..1
 
 
|
 
Reference(Patient | Group? | ??)
 
 
|
 
<nowiki>who.fo</nowiki>cus
 
 
|
 
Individual the service is ordered for
 
 
|-
 
|
 
(use cases? Billing?)
 
 
|
 
encounter
 
 
|
 
context
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
Reference(Encounter | EpisodeOfCare)
 
 
|
 
context
 
 
|
 
Encounter or Episode during which request was created
 
 
|-
 
|
 
<nowiki>when.co</nowiki>de
 
 
when.schedule
 
 
 
 
|
 
Priority,
 
 
 
 
timingTiming,
 
 
 
 
timingDateTime,
 
 
 
 
timingPeriod
 
 
|
 
<nowiki>occurrence[x]</nowiki>
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
dateTime| Period| Schedule?
 
 
|
 
<nowiki>when.pl</nowiki>anned
 
 
|
 
When service should occur
 
 
|-
 
|
 
date
 
 
|
 
recordedOn
 
 
orderdedOn ( more of a Task thingy)
 
 
|
 
authored
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
dateTime
 
 
|
 
<nowiki>when.re</nowiki>corded
 
 
|
 
When the request transitioned to being actionable
 
 
|-
 
|
 
source
 
 
|
 
 
 
|
 
requester
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
Reference(Device | Patient | Practitioner | RelatedPerson | Organization?)
 
 
|
 
<nowiki>who.au</nowiki>thor
 
 
|
 
Who/what is requesting service
 
 
|-
 
|
 
 
 
|
 
 
 
|
 
performerType
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
CodeableConcept
 
 
|
 
<nowiki>who.pe</nowiki>rformer
 
 
|
 
Desired type of performer for service
 
 
|-
 
|
 
  supplier
 
 
 
 
|
 
 
 
|
 
performer
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
Reference(Practitioner | Organization | Patient | Device | RelatedPerson)
 
 
|
 
<nowiki>who.pe</nowiki>rformer
 
 
|
 
Desired performer for service
 
 
|-
 
|
 
  reasonCodeableConcept,reasonReference
 
 
 
 
|
 
Indication, PRNreason ( really more of  a protocol thingy)
 
 
|
 
<nowiki>reason[x]</nowiki>
 
 
|
 
S
 
 
|
 
0..1
 
 
|
 
CodeableConcept | Reference(??)
 
 
|
 
why
 
 
|
 
Why is service necessary?
 
 
|-
 
|
 
 
 
 
 
 
|
 
 
 
|
 
supportingInfo
 
 
|
 
 
 
|
 
0..*
 
 
|
 
Reference(Any)
 
 
|
 
 
 
|
 
Additional information to be used in fulfilling request
 
 
|-
 
|
 
 
 
|
 
Notes
 
 
|
 
note
 
 
|
 
 
 
|
 
0..*
 
 
|
 
Annotation
 
 
|
 
 
 
|
 
Comments made about the service request
 
 
|-
 
|
 
Kind (e.g. central stock, non-stock)
 
 
|
 
 
 
|
 
 
 
|
 
 
 
|
 
 
 
|
 
 
 
|
 
 
 
|
 
 
 
|-
 
 
 
 
|
 
 
From and to location missing in SupplyRequest need for logistics
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|}
 
  
 +
'''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
 +
*[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
 +
*[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
  
 +
'''BodySite'''
  
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7250 7250] 2015May core #310 - Body site should be a code, not a type or resource (Clem McDonald) Not Persuasive '''In Person'''
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7342 7342] 2015May core #532 - There should be at least 2 types of body sites indicated. targetBodySite and approachBody site (Corey Spears) Not Persuasive
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7475 7475] 2015May core #770 - Complext structure or data type needed for BodySite (not resource) (Tom Oniki) Not Persuasive
 +
*[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7577 7577] 2015May core #868 - Recommend changing this to a "common structure" that could be used for Condition.site, etc. (Ioana Singureanu) Not Persuasive
  
  
#* Jose C-T proposals
+
* Connectathon review
# Review outstanding Trackers
+
#* [http://wiki.hl7.org/index.php?title=201605_Data_Access_Framework_(DAF) DAF LabResults] - not covered
# Connectathon review
 
#* [http://wiki.hl7.org/index.php?title=201605_Data_Access_Framework_(DAF) DAF LabResults]
 
  
 
==Minutes==
 
==Minutes==

Revision as of 21:48, 28 April 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/04/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
Hans Buitendijk
Jose Costa-Teixicara
Dan R
X Jonathan Harber
Kamalini
Mark Jones
X Rob Hausam
Margaret D


  • Review Device QA criteria for FMM proposal - not done
  • Review outstanding Trackers for WGM

Topic: Workflow Mon Q 3-4 is Workflow discussion. Will await outcome of Workflow Group before addressing these items:


  • 5304 Jan 2015 Ballot Comment #183 (David Tao) Considered for Future Use
  • 5468 Jan 2015 Ballot Comment #404 (Riki Merrick) Considered for Future Use
  • 7756 2015May core #1077 - Document Order Request/Response pattern (Keith Boone) Considered for Future Use
  • 8445 Allow Order source to be a Patient (David Hay) Considered for Future Use
  • 8478 replace element names .source and .target with .Placer and .Filler (Clem McDonald) Considered for Future Use
  • 8755 add an orderType to support workflow variations (Jose Costa) Considered for Future Use
  • 8756 Create an extension for a dynamically calculated workflow status (Jose Costa) Considered for Future Use

DiagnosticOrder

  • 9187 flatten out Diagnostic Order, move specimen collection to ProxcedureRequest (Eric Haas) None
  • 9852 Add timing atttributes to DiagnosticOrder (Hans Buitendijk) Persuasive with Mod


DiagnosticReport

  • 9038 Culture (James Agnew) None
  • 9671 DiagnosticReport - add support for linking reports together (Michelle Miller) None
  • 9859 combine DiagnostReport.conclusion and DiagnostReport.codeDiagnosis (Eric Haas) None
  • 9206 DiagnosticReport element to include textual narrative of the diagnostic assessment (Sean Moore) Not Persuasive
  • 9433 Observation.issued and DiagnosticReport.issued (Hans Buitendijk) Not Persuasive


Observation

  • 9375 Remove invariant from Observation.component.code (Michelle Miller) None
  • 9774 Create required core profile for Vital Sign (Eric Haas) None In Person
  • 9857 change Observation.category from Example to Extensible (Eric Haas) None
  • 9880 element for indicated who or what changes the status (Hans Buitendijk) None
  • 9433 Observation.issued and DiagnosticReport.issued (Hans Buitendijk) Not Persuasive
  • 9543 Multieple Observation Categories (Hans Buitendijk) Not Persuasive
  • 9676 Add Observation.component.interpretation (Michelle Miller) Persuasive with Mod


DataElement - To be covered on May 19th OO on FHIR call

  • 6095 styleSensitive isn't clear enough (Lloyd McKenzie) None
  • 7248 2015May core #308 - Various opinions on data element (Clem McDonald) None In Person
  • 6316 Dataelement is insufficient for Master Files (Eric Haas) Not Persuasive
  • 8884 Need extension for min valueSet for DataElement.element.mapping.language (Lloyd McKenzie) Persuasive

BodySite

  • 7250 2015May core #310 - Body site should be a code, not a type or resource (Clem McDonald) Not Persuasive In Person
  • 7342 2015May core #532 - There should be at least 2 types of body sites indicated. targetBodySite and approachBody site (Corey Spears) Not Persuasive
  • 7475 2015May core #770 - Complext structure or data type needed for BodySite (not resource) (Tom Oniki) Not Persuasive
  • 7577 2015May core #868 - Recommend changing this to a "common structure" that could be used for Condition.site, etc. (Ioana Singureanu) Not Persuasive


  • Connectathon review

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