Skip to end of metadata
Go to start of metadata

Time:

Coordinates:

Attendees

Name Affiliation
Rob HausamHausam Consulting
Andrea PitkusUniversity of Wisconson
Matt Ellrod
Ralf HerzogRoche
JD NolenChildren's Mercy Hospital
Lorraine ConstableConstable Consulting
Hans BuitendijkCerner
Marti VelezisSonrisa / FDA
David BurgessLabCorp
Molly MalaveyAMA
Nancy SpectorAMA
Dan RutzEpic
Becky GradlAcademy of Nutrition and Dietetics
Freida HallQuest Diagnostics




Chair: Hans Buitendijk

Scribe: Hans Buitendijk

Agenda:

  • Minutes 
    • 2020-09-21-25 
      • Missing administration quarter
      • Links to be completed.  Co-chairs need to check.
    • 2020-10-01 - Motion to accept as published, JD Nolen, Rob Hausam
      • Against: 0; Abstain: 2; In Favor: 10

  • PSS
    • Supplemental Guide for C-CDA Attachments
      • Need to ask why this is going to the Admin SD: scope/need did not change.  Project was already approved by TSC.  Only dates seem to change that can be accommodated by a simple fix and new NIB.  If substantially changing scope would be helpful to clarify that.
    • Presentation on PSS-1664 - Interoperability of Advance Directives (in FHIR)
      • PSS-1664 - Getting issue details... STATUS
      • Suggestion to start with interested party and move to co-sponsor if changes needed. 
      • On the other hand it is not yet clear how/when to use OO resources which would require more discussion and perhaps benefit from co-sponsorship.
      • Other groups to consider are SOA consent project and BPM+ effort.
      • Motion to become co-sponsor with periodic updates and in particular a design review to understand how OO resources are to be used.  Lorraine Constable, Andrea Pitkus.
        • Clarified periodic is to be based on progress and focus and particularly during design and as part of OO calls.
        • Against: 0; Abstain: 1; In Favor: 10
  • Radiology Pathology Concordance Reporting (CAP/ACR )
    • Need for a concordance report.  It appears that this is about guidance on how to communicate about a concordance report process and the resulting report 
    • If the general process is that an imaging report and diagnostic report are effectively "blended" into a third report that combines materials, references, etc. don't we have another DiagnosticReport (+ Composition as needed) to represent that?  What is the need for another IG?
    • Suggestion is that perhaps examples of such a concordance report would be helpful to ensure DiagnosticReport + Composition can handle that output, while the application creating it (with or without user intervention) does what it does based on the reports provided as input.
    • Next step is to finish the DiagnosticReport and Composition discussion/decision on how to use them together, or blend, using concordance reporting as an example to validate completeness and ability to support as well.
    • Explore whether one or more concordance report examples are sufficient to then be included in the resource definitions, or that a separate IG is needed as well.  Andrea has a bone marrow example, and there are others to be considered.
    • JD Nolen to drive OO on FHIR call to resolve this, starting next week.
    • There is another issue to still clarify better when to use an Observation vs. when to use a DiagnosticReport.  That is to be picked up by OO on FHIR as well.


  • Upcoming OO-BR&R Calls
    • Monday, October 12 – 2-3pm ET – Specimen/Sample
    • Monday, October 12 – 3-4pm ET -  Substance/SubstanceDefinition/PacagedProductDefinition
    • Tuesday, October 13 – 4-5pm ET – Observations on manufacturing process, e.g., quality control
    • First two are on the OO Zoom, and the third will use the BR&R Zoom
    • Hans Buitendijk to send reminder.

  • v2 Change Requests - Next Week
  • Project updates - Not discussed
    • Nutrition
      • Met this week (9/30/2020)
      • Reviewed updating DAM scope, aligning with MCC E care plans (PC is sponsoring) 
      • Meeting
        • Every other Wednesday 2-3 ET
      • Project page link: Nutrition
    • Specimen DAM
    • FHIR - OO on FHIR
      • No meeting next week
      • Meeting
        • Every Tuesday 2 - 3 PM ET
      • Project page link: FHIR
    • AUC - NO UPDATE
      • IHE needs to update Volume IV to reflect CMS vocabulary.
      • Also needs to consider alternative use of ORU to clarify how OBX could be used, plus mapping to FT1.
      • CDSM connection is still proprietary, interest to get CDS Hooks/Standards.
      • Change to the name of the LOINC Code. 
    • CIMI/Concept Modeling - NO UPDATE
      • Co-chair will meet to discuss the future of the group – Lorraine will check what’s up
    • DME - NO UPDATE
      • Need to sort out Post-Acute Orders vs. DME (as in NIB).
      • Check with Bob Dieterle.  Needed before publication.
      • Project Page Link: DME Project
    • Healthcare Product: Device/DeviceDefinition/UDI
      • UDI DAM in ballot recon
      • 17 items in discussion 
      • BR&R - meeting October 12th on substance, substance definition, package products definition  
      • Resource Proposal Updates
      • Meeting: Every Monday 3 -4 PM ET
    • V2+  NO UPDATE
      • Still need to look at open tickets and message structure issues (debate continues) 
      • Meetings:
        • Every other Friday, 9-10am ET
      • Project Page Link: V2+
    • V2-to-FHIR 

    • US Realm Lab (eDOS/LOI/LRI) 
      • Frieda updating documents for publication 
    • Product Grid – no update, is not needed this cycle
      • Possible review at WGM  
      • Co-chair meeting to re-group.
      • Need to still review the status of our standards in the product grid: http://hl7.org/implement/standards/product_matrix.cfm?ref=nav
        • Status definitions - Riki to follow up to see where those are in the grid - here are the ones given to TSC:
          • active, planned use or in use, future maintenance release
            • stable, in use, generate feedback, not active
            • review, not updated in foreseeable future
            • deprecated - deprecated - no further work planned - if not already using, it is not recommended to be implemented