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 MINUTES

• Administrative
• Module Work
  • No other comments, until Marti's updates.
• JIRA tickets
  • BDP 

    • Service Request tickets that relevant to the current BDP backlog

      • https://jira.hl7.org/browse/FHIR-38818
      • Reference: https://github.com/IHE/pharm-supply/blob/master/input/fsh/delivery.fsh#L11
      • SupplyDelivery should be profiled (one above) for shipped and received; and an additional elements to described
      • Need to show direct linkage between what is requested, shipped and received.
      • We will resume the discussion next time and work on how this should look to reconcile concerns raised in the JIRA ticket for accounting for all products shipped and received.
      • Suggestion to not mix the dispatch and the receipt/reconciliation in one SupplyDelivery resource, rather to have two resources SupplyDispatch and SupplyReceipt.
      • How does that sync with pharmacy?  Also noting that "dispense" either means "assigned to a patient" vs. "shipped to a patient".
      • We clarified that MedicationDispense is also just focused on "assigned to a patient" and any transportation would be a separate from the dispense.
      • Option 1:
        • Keep SupplyDelivery and add .stage(dispatch|receipt), enhance status for appropriate values for each stage and add a reference from receipt to dispatch.
      • Option 2:
        • Split SupplyDelivery into SupplyDispatch and SupplyReceipt and include SupplyDispatch a reference to SupplyReceipt.  Possibly remove an attribute that is not applicable to the resource at hand.
      • Paul and John to prep a list on attributes that are applicable for Receipt vs. Dispatch based on which we can then determine whether that points to using a single resource with two stages, or two resources.
      • Will continue the discussion in two weeks or as soon as ready thereafter.

Meeting adjourned

• • Other ServiceRequest tickets:
    • FHIR-34194 -Add businessEvent extension
    • FHIR-34205 -Add ServiceRequest.status values
      • Has disposition – more discussion needed?
      • Does it need larger review ?  If yes -- suggest adding it to block vote (if yes - add grouping = "OO-FHIR-Block-Vote" and "August-2023"?
    • FHIR-34207 -Add attribute to document confirmation
      • Has disposition – more discussion needed? 
      • Does it need larger review ?  If yes -- suggest adding it to block vote (if yes - add grouping = "OO-FHIR-Block-Vote" and "August-2023"?
    • FHIR-31589 -Clarify ServiceRequest.supportingInfo can't be 'questions'
  • Device
    • FHIR-41597 -codeableReferences in DeviceDefinition missing valueset bindings
    • FHIR-40289 -Solve device conformance to standard "options"
  • Procedure (from Pt Care)
    • FHIR-33390

Any follow-up from: 

• Need to work with DEV group on the following: 
  • FHIR-40291 -Update the device specification example valueset to cover additional uses
  • FHIR-41413 - Need to bring to DEV
    • DeviceDispense.performer.actor
      • Recommendation is to Remove Patient and RelatedPerson if DEV is ok with that resolution
      • If so - this could be a new JIRA

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).