This wiki has undergone a migration to Confluence found Here

20180220 OO FHIR conCall

From HL7Wiki
Revision as of 20:28, 20 February 2018 by Ehaas (talk | contribs) (Created page with "{|border="1" cellpadding="2" cellspacing="0" | width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 OO on FHIR (for Orders and Observations)''' <br/> '''Cal...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
HL7 OO on FHIR (for Orders and Observations)

Call in details:
Phone: +1 515) 739-1430, Passcode: 294586

Join the meeting at:
https://join.freeconferencecall.com/ord

Date: 2018/02/20
02:00 PM (Eastern Time, GMT -04 DST)
Quorum = chair + 4 yes


scope="col" Co chairs Chair Notetaker
Riki Merrick
Rob Hausam X
Lorraine Constable
Patrick Lloyd
KD Nolan
Hans Buitendijk


Attendees
X Eric Haas
Hans Buitendijk
X Jose Costa-Teixeira
X Dan Rutz
X Rob Hausam
Andrea Pitkus
X Kathy Walsh
Marti Velezis
Bob Milius
Elliot Silver
X Lou Bedor
X Lisa Anderson

  • Roll Call


Agenda

As a reminder we are only a couple of weeks away from submitting changes for the Normative ballot and quickly running out of time. We will focus on the remaining OO trackers. The tracker "themes" are:

  1. Stuff to defer
  2. Subject and Focal Subject: actice discussion on zulip here: https://chat.fhir.org/#narrow/stream/implementers/topic/Proposal.20to.20= make.20Observation.20Subject.20Reference(any)
  3. DiagnosticReport...What is it good for
  4. Workflow related changes (with emphasis on work :-))- if we have time will be reviewing this.

(this list excludes Workflow , BioloigcallyDerivedProduct, EntryDef and ObsDef related trackers as they will be discussed on their resective subcomittee calls.)

Proposed Block 3 items - need to publish Block Vote by Thursday

Comment Submitters

  • Casey McGruder
  • Cooper Thompson
  • David Hay
  • Eric Haas
  • Francois Macary
  • Rick Geimer
  • Eric Haas
  • Francois Macary
  • Riki Merrick

Line Items

  1. 15089 Consider+whether+ServiceRequest.performer+should+be+0..%2A (Cooper Thompson= ) - OK as written
  1. 15515 %22Specimen+collection+method%22+value+set+needs+cleanup (Francois Macary) Not Persuasive - updated text and OK
  1. 13521 Add+%27declined%27+to+the+valueset+http%3A%2F%2Fhl7.org%2Ffhir%2Fdata-absen= t-reason (David Hay) Persuasive - Rob H is working on this and will pre-apply need community input too. will remove 'human' from descriptions.
  1. 15088 Add+supporting+use+cases%2Fexamples+to+support+boundaries+with+ImagingStudy (Eric Haas) Persuasive - Dan R to provide examples.
  1. 15162 Add+Practitioner+and+PractitionerRole+to+Observation.subject (Rick Geimer) - Reached out to PA and CQI is MeasureReport in scope for this and what are the use cases specifically. will reach out to commenters for specific use cases ... may defer.
  1. 15526 Add+LOINC+guidance+for+pattern+3 (Eric Haas) Persuasive - Rob H to edit, make 3.prefer LOINC or SNOMED , remove reference to LOINC parts and add reference to LOINC answer codes.
  1. 15566 Nonfunctional+hyperlink+-+Device+Resource (Casey McGruder) Persuasive - preapplied
  1. 11217 Thoughts+on+combining+SupplyRequest%2C+DeviceUseRequest+and+VisionPrescrip= tion+-+2016-09+core+% (Riki Merrick) Considered for Future Use -defer
  1. 14038 how+to+represent+add-ons (Eric Haas) -defer
  1. 14142 Harmonize+DeviceUseStatement+with+MedicationStatement (Francois Macary) -defer




Other Trackers to Discuss

Comment Submitters

Other Trackers to Discuss

  • Comment Submitters
  • Lloyd McKenzie
  • Mark Kramer

Line Items

  1. 14443 Observation.subject+is+too+narrow (Lloyd McKenzie) In Person
  2. 14450 OO+resources+do+not+have+a+clean+Workflow+report (Lloyd McKenzie)
  3. 14863 Add+Observation.focalPoint+-+2018-Jan+Core+%23203 (Mark Kramer) In Person
  4. 15521 Add+%22supportingInformation%22+as+either+a+core+element+or+standard+extension+to+DiagnosticReport (Lloyd McKenzie)
  5. 15522 Allow+DiagnosticReport.result+to+be+RiskAssessment+too (Lloyd McKenzie)


Subject and Focal Subject:

Although it may be convenient for some to represent everything with an Observation - that is not the current scope of Observation. These proposals represent marked departures from current scope of Observation and the very philosophy behind FHIR is to build a base set of FHIR resources to "define a small amount of highly-focused data". My opinion is that these are important and overirding considerations when discussing these trackers. For Observation to remain on the path to a normative resource, the scope of Observation cannot be radically expanded as suggested in the tracker proposals.

background: Also OpenEHR archetypes describing Evaluation vs Observation http://www.openehr.org/ckm/

Offline discussion lead to Zulip posting to implementers for feedback:

https://chat.fhir.org/#narrow/stream/implementers/subject/Proposal.20to.20make.20Observation.20Subject.20Reference(any)

Will need to discuss on the March 1 Call and vote either way.



Back to OO_on_FHIR