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

20170406 OO FHIR conCall

From HL7Wiki
Revision as of 19:24, 6 April 2017 by Ehaas (talk | contribs)
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:

Date: 2017/04/06
2015 - 02:00 PM (Eastern Time, GMT -04 DST)
Quorum = chair + 4 no

Co chairs Chair Notetaker
Riki Merrick
Rob Hausam X
Lorraine Constable
Patrick Lloyd
Ken McKaslin
Hans Buitendijk

X Eric Haas
Riki Merrick
Hans Buitendijk
Jose Costa-Teixicara
Dan Rusk
Jonathan Harber
David Burgess
Lloyd McKenzie
X Rob Hausam
Andrea Pitkus
Francois Marcary
Robert Dieterle
Marti V
Ron Shapiro
Kathy Walsh
Todd Cooper
Cindy Johns
Bob Miius

  • Roll Call
  • Agenda
  1. Trackers for DiagnosticReport.
    1. 9433 Observation.issued and DiagnosticReport.issued (deferred)
    2. 12240 update micro+susceptibilty examples
    3. 13169 change performer role binding to v3 partiicpation type with strength of extensible
  2. Review what missing from use cases and keeping this resource from progressing to FMM = 4
 e.g.,  how to represent complex AP reporting using DR vs other options.

Tracker 13169

Since only RH and I present, decided to focus on vocab related tracker

From original GForge that triggered the performer type identified:

  1. responsible
  2. author
  3. verifier
  4. etc.

From V3 participation type code system have

* RESP	responsible party
* AUT	author (originator)
* VRF	verifier

Propose create as a starter valueset as extensible

Rob to start chat on Zulip to clarify the FHIR-wide guidelines for using V3 codes vs creating friendlier FHIR codes.

See notes in tracker.

Looking at categoy codes in ProcedureRequest vs DiagnosticReport vs Observation

Issue raised by Grahame re the ProcedureRequest.category codes and suggested that they should be more like Observation.category.

See comparison chart media:Compare-cats.xlsx here

DR and Obs should be the same - existing tracker #11963

Looking at procedure categories on Google led to ICD-10PCS and CPT which were not helpful.

Need to establish the use case for why the procedure category would change operational behavior? It was introduced as part of merging DiagnosticOrder and ProcedureRequest to enable backwards compatability and if there was a need to differentiate the orders. It is also useful for searching.

AP Reporting

See example report


  1. DR.presentedForm as pdf etc
    • simplest
    • unstructured
  2. Sections in Composition ( ie a static document )
  3. Create and reference Observations in DR.results
    • Possibly narrative-only or .valueString
    • LOINCs...
  4. New elements in DR
    • Draft mappings to see gaps in DR and what is needed

Back to OO_on_FHIR