Anti-Trust Policy:  Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).

Meeting Details

Date: March 20, 2023

Time: 3PM ET

Coordinates:  Join Zoom meeting: https://zoom.us/j/5100467805 | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)

Attendees: 

Hans Buitendijk, JD Nolen, Paul Ashford, Rob Hausam, Donna Pertel, Elliot Silver, Jose Costa Teixeira, Karen Moniz, Nancy Spector, Marti Velezis

AGENDA

  • Administrative
    • DeviceDispense FHIR IG Proposal
    • JIRA Clean-up
  • Status on JIRA Tickets
  • AOB
  • Next Meeting

LINKS TO JIRA - HCP DASHBOARDS

HCP_Backlog - FOR REVIEW (includes Nutrition resources)

HCP_Ballot Related - JIRA that need to be completed by R5 (many of these are related to Normative content)

HCP_Work In Progress - Items that need to be updated in the build and/or QA for completion

Discussion Topic Pages

  • VisionPrescription ???

Module Pages

The following are draft pages to organize and author content for each of our health care product resources: 

Upcoming Topics/Due Dates

Date

Topics

March 26, 2023Final IG Content
March 27,  2023
  • Resume JIRA for R5 STU changes to CI Build 
April , 3, 2023
April 10, 2023
April 17, 2023
April 24, 2023
May 1, 2023
May 6-May 12

HL7 Connectathon,  WGM, WGM+ in New Orleans

Unscheduled Discussions

Action Items

Instructions: Type your task here, using "@" to assign to a user and "//" to select a due date

Action Item


MEETING MINUTES

  • Administrative
    • FHIR-26827 - Getting issue details... STATUS
      • This request is no longer needed because this has been added in R5 and can be pre-adopted as an extension in R4 (i.e., extension is no longer needed in R5)
      • Need to reopen and mark no change required
      • Reopen
        • Marti Velezis / Jose Costa Teixeira: 8-0-0
      • Not Persuasive  
        • Marti Velezis / Jose Costa Teixeira: 8-0-1
    • FHIR-38634 - Getting issue details... STATUS
      • This has been pre-applied and published in R5
      • Consider adding disposition and mark pre-applied
      • Motion to find Persuasive
        • Marti Velezis / Hans Buitendijk : 9-0-0
    • FHIR-39552 - Getting issue details... STATUS
      • This has been pre-applied and published in R5
      • Consider adding disposition and mark pre-applied
      • Motion to find Persuasive
        • Marti Velezis / Han Buitendijk : 9-0-0
    • FHIR-15922 - Getting issue details... STATUS
      • Comment: DeviceDispense.basedOn pointing to DeviceRequest should satisfy the use case I was dealing with back when I created this tracker. You can close it out. 
      • Mark Reject Request and Resolved - No Change Required
        • Hans Buitendijk / Marti Velezis : 9-0-0
    • FHIR-37951 - Getting issue details... STATUS
      • This has been pre-applied and published in R5
      • Consider adding disposition and mark pre-applied
      • Motion to find Persuasive
        • Marti Velezis / Jose Costa Teixeira : 9-0-0
    • FHIR-34376 - Getting issue details... STATUS
      • This has been pre-applied and published in R5
      • Consider adding disposition and mark pre-applied
      • Note: The Clinical module home page still lists ServiceRequest in their Index; ServiceRequest is assigned to Workflow.
      • Motion to find Persuasive
        • Marti Velezis / Jose Costa Teixeira : 9-0-0
    • FHIR-40094 - Getting issue details... STATUS
    • FHIR-40435 - Getting issue details... STATUS
      • This has been fixed (no longer see instances of "F H I R" in the Device and DeviceDefinition resources) 
      • Mark either reject request and/or pre-applied
      • Motion to find Persuasive
        • Marti Velezis / Elliot Silver : 9-0-0
  • JIRA Tickets
    •  BDP
      • FHIR-40286
        • ServiceRequest should include the product element defined with the Request pattern

        • David Barwin Would the new ServiceRequest.orderDetail address your use case? 
          • Specifically .orderDetail.parameterFocus already allows you to include the BDP
          • Would you be able to specify the required orderDetail.parameter.code and orderDetail.parameter.value as well?
          • We noted that the short descriptions and definitions would need to be updated to make it clear.
          • We will follow up with David and bring it back.

Next meeting:  March 27. 2023

--------end of call at 4PM EST--------

Did not get to discuss the following issues: 

  • Device
    • FHIR-40384
      • Need to distinguish device-created from transcribed observations
    • FHIR-40335 
      • Clarify use of Obvervation.subject, .device, and .focus for devices
  • Nutrition
    • Any updates?
  • VisionPrescription
    • Need to plan for analysis of VisionPrescription, add confluence page??
  • Cross-cutting
    • FHIR-40631
      • Some OO requests need basedOn to RequestOrchestration
      • NutritionOrder (was NutritionRequest), ServiceRequest (Diagnostic/Procedure/ReferralRequest), VisionPrescription

INVENTORY BACKLOG

Note these are issues that we did not have time to discuss, or already have been discussed, but may not be ready for disposition (i.e., waiting for input or additional work needs to be completed).

SOURCE 

ISSSUE/TOPIC FOR DISCUSSION

NOTES

BiologicallyDerivedProduct
  • FHIR-40286 - ServiceRequest should include the product element defined with the Request pattern
  • FHIR-40397 - Align product code search parameters
  • Added to today's agenda.
NutritionProduct
  • FHIR-32756 - request-insurance extension needs more context given in the description
  • Waiting for Jose Costa-Teixeira  to respond to comments; this should be included in a future call (August 8 or 15)
  • FHIR-19516 - Substantive workflow changes for OO resources
  • Needs to be assigned (Status = Resolved Change Required)
NutritionOrder
  • TBD

NutritionIntake
  • TBD

Device

  • Pending additional review
DeviceDefinition
  • FHIR-31750 - Complement Valueset-identifier-type for Device identifiers 

  • Approved; Updating UP-232
  • Examples
  • Search Parameters
  • Mappings (TBD)
  • Need to complete work on Device Definition to make it consistent with or address variations from Device resource
DeviceDispense
  • TBD

DeviceRequest

  • FHIR-26429  - Consider adding extension to allow fuzzy timing for DeviceRequest.occurrence

  • Note - Robert Hausam there is an outstanding question in comments for you - also see under Service Request.

  • Need update from OO on FHIR

  • FHIR-26948 - Create examples for prosthetics (e.g. glasses, lenses) in DeviceRequest; Comment added for Jose - Pending
  • See topic below (Device Request and VisionPrescription)
  • Device Request and VisionPrescription
VisionPrescription

DeviceUse
  • Will be kept open until UDI IG has addressed these and can confirm it covers it.
ServiceRequest


SupplyDelivery
  • FHIR-38818 - Clarify SupplyDelivery for shipment vs reception

Product Pattern
  • Need Jose Costa-Teixeira and Carl Leitner on the call.
  • Is there a benefit to have definition for BDP, in blood bank with ordering is one (and maybe only example).