This wiki has undergone a migration to Confluence found Here

20171209 OO FHIR conCall

From HL7Wiki
Revision as of 20:19, 7 December 2017 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 770-657-9270, Passcode: 398652

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

Date: 2017/12/9
2015 - 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
Dan Rutz
X Rob Hausam
Andrea Pitkus
X Kirk Schaper
Marti Velezis
X Bob Milius
Elliot Silver

  • Roll Call


Agenda

Trackers discussed and voted on

  1. 14149 Clarify use of "comments" in Media and ImagingStudy Medium Nobody Elliot Silver
    • persuasive Eric Haas/Jose Costa-Teixeira: 4-0-0
  2. 14146 Review MediaSubtype value set and code systems Medium Nobody Elliot Silver
    • see tracker follow up notes - contact submitter for more feedback.
  3. 14145 Media.type is too restrictive Medium Nobody Elliot Silver
    • persuasive with mod - Eric Haas/Jose Costa-Teixeira: 4-0-0
  4. 14144 Align Media with Observation Medium Nobody Elliot Silver
    • persuasive with mod - Eric Haas/Jose Costa-Teixeira: 4-0-0
  5. 13334 Media should be moved to O&O ownership Medium Nobody Elliot Silver
    • email Elliot torequest this tracker be withdrawn


Trackers

Trackers sorted by topic

Vitals Profile

(reviewed with Argonaut Community as well since tied to USCore)

  • 13801 Vital signs profiles - Body Height (Ardon Toonstra) None
    • reviewed with Argonaut/US Core Community decided to keep. see tracker notes. OO vote pending.
  • 13652 Observation requires Vital Signs Profile support which requires LOINC%2C which is too strict (Erik Moll) Not Persuasive In Person
    • reviewed with Argonaut/US Core Community decided would need to support in US anyway
    • outcome of LOINC/Device meeting - discussion about creating a mapping table between the LOINC vital signs codes and IEEE vitals codes that could be published as FHIR Concept Maps.
Workflow Related
  • 11217 Thoughts on combining SupplyRequest%2C DeviceUseRequest and VisionPrescription - 2016-09 core %23371 (Riki Merrick)
New Profiles
  • 12913 Create a profile for %22Patient characteristics%22 (Lloyd McKenzie) None
    • Are we ready for this?
  • 13938 Add phsyical activity profiles like vitals (Harri Honko) None
    • See Harry's Finnish Profiles
Media Related
Observation
SeviceRequest
  • 14038 how to represent add-ons (Eric Haas) None
    • Discussed - more an issue of using existing specimen or some existing thing since is a convenience for the client or practitioner rather than a reason as in a reflex or a follow-up based on earlier result. example: I forgot to order a Free T$ when ordering a bunch of tests. So I call ask to 'add-on" a free T4 so that a new sample does not have to be drawn. Hence reasonReference is not appropriate.
    • Next Step Eric to create a scenario and walk through the options...
Other =
  • 14142 ProcedureRequest -Harmonize DeviceUseStatement with MedicationStatement (Francois Marcary) None

QA

QA criteria link: http://wiki.hl7.org/index.php?title=FHIR_Conformance_QA_Criteria#StructureDefinition_-_Resource_definition

1. a) OK

1. b) Media is Imaging Study

1. c) don't use for other events such MedAdmin that been defined resources

1. d) Ask about where it should be defined have definition but not in introduction


2. a) add more component per tracker -add example for core characteristics and physical activity (steps or sleep)* note where overlap with condition - e.g Preg Obs

b) fix links from xml to html in example_csv

3. a) RIM Rob take a look - lower priority

b) review mappings

4. a) follow up with Lloyd on whether FHIR code systems need to be V3 for codeable as he asserted

   also follow up on NINF and PINF definitions with devices for data absent reason.  (check in IEEE spec Swapna?)


Back to OO_on_FHIR