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
  • Reviewed the key points for the 2023-05-08-12 WGM 
    • See R6 planning discussion for the priorities to reach Normative for OO Resources
    • See Device related discussions for additional work that needs to be completed
    • BDP and Nutrition were not discussed 
• BDP
  
  • BDP Transformations
    • FHIR-41111 - New values in valueSet biologically-derived-product-status
      • Reviewed the proposed change
      • Added"dispensed" 
        • Defined as: biologically derived product has been dispensed to a patient at this time – changed to: the BDP has been transferred from the custodian to the patient, clinician, or system responsible for the clinical application
        • canonical map to busy-unavailable
        • can add extensions for the actual to/from - in the context of the responsible party (system, person, etc)

      • This is only an example value set for the resources, there still may be other statuses for use cases (e.g., Blood banks have additional status values in use today)

      • Need to add something for when the product has been associated to a patient
        • "allocated" - the biologically derived product is reserved and/or crossmatched for a patient (note these are a subset to unavailable); this may be confused with actual "dispense" 
        • In medication - "when prepared" and "when handed over" - these are date/time datatypes
        • Patient/RelatedPerson/Provider - picks up the medication - this is also when handed over"
        • Automated dispensing systems - delivery from system - when prepared; when nurse grabs it from the system it is "when handed over"
        • "when handed over" is then considered dispensed
        • Added "allocated"
          • defined as: associated with a patient
          • canonical map to ....to pick up next time
      • Updated both of those status codes in the JIRA ticket and will resume the discussion on May 22 after the WGM when we resume meetings.
      • Check how we are using allocated and dispensed in other locations in FHIR - during the May WGM

      • 5/22/2023 - BDP Status Notes

        • MedicationDispense and BDP Dispense are aligned
        • Align DeviceDispense - it is focused on allocation of the device; do we need to be consistent in each of the Dispense Resources with the value set for status?  
        • Definition of "Dispense" for logistics and healthcare use - ISO definition is available for use
        • Action: We will take a vote on this ticket next time (June 5)
        • Also need to look at the consistent use of "status" across resources – in the case of Dispense Resources the "status" is not of the resource itself, but the business status as with the Product Resources.  Will create a JIRA for this to consider across resources.  There may be a rationale to keep the Dispense Resources as is – they all follow the same pattern that the "status" is of the dispense event.

Next meeting:  June 5, 2023

------------Adjourned at 4:03PM EDT---------------

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