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

• BDP
  • Any updates on the BiologicallyDerivedProductDispense Resource Proposal
    • Review status - in FMG eVote at the moment
    • Question/Comment from Lloyd – would like there to be an assessment of whether this could be combined with the existing MedicationDispense or DeviceDispense
      • Previous discussion and decision was to keep them separate based on the scope of Biologically derived products that all don't fit into the existing MedicationDispense and/or DeviceDispense resources.  Dispense is slightly different in each of the product resources.
      • Resource proposal annotated with a clarification (see below)

        •  Notes for discussion only (to be removed as part of final approval):

          • We have BDP and Medication, yet for (xyz)Dispense we would combine.  That does not make senses.
          • Medication would have to be expanded beyond medication (considering that not all BDPs are not medications).  While blood transfusion could, mothers milk would not, and other BDP-s would also not be medications.  The characteristics of autologous or not (originRelationshipType) are unique to BDP, not Medication or Device.  
          • Devices are not medications, although some may facilitate back-and-forth based on jurisdiction.
          • This has been discussed to date between OO and Rx and to date not resulted in any combination.
• Nutrition-Review and Vote on dispositions: 
  • FHIR-32293 - Resource NutritionProduct should provide better examples
    • A resource should be allocated mid-January 2023 that can help with examples
    • Updates? 
      • James shared the following: https://interoperabilityandstandards-nutritionproduct-client-93q8wj.streamlit.app/
    • Need a value set for "NutritionProduct.category" - e.g., USDA
    • Ingredients
      • the sample for Skippy Peanut Butter has a string of ingredients instead of an array of individual ingredients
      • If the intent is just to access the list of ingredients, each ingredient may not need to be enumerated, but if you need to provide an amount – the array could be used to share a recipe.
      • Should there be an Ingredient Summary element? To allow the string of ingredients and not individual  OR separate 
      • the sample for "Centrum Adults" 
        • Vitamins - Medications versus NutritionProduct?
        • Supplement? 
    • James will update the samples to enumerate the Skippy PB with individual ingredients
    • James will create a JIRA ticket for additional element for the summary of ingredients as text (i.e., it is not a codeable concept). 
      • Marti to connect with James to set up account/create first JIRA
    • Add to agenda for the next Teleconference 1/23/2023
  • FHIR-37965 - Group identifier for NutritionOrder
    • Add groupIdentifier as requested to follow the request pattern
    • Motion to find Persuasive:
      • Add groupIdentifier as requested to follow the request pattern and make it searchable (i.e., add search parameter).
      • Marti Velezis / Jose Costa Teixeira: 9-0-0
      • Assigned to Jose Costa-Teixeira 
  • FHIR-37975 - How to capture nutrition intake in R4?
    • Use the Basic resource and extensions
    • Posted to Zulip for guidance from FHIR-I if this should be the correct approach.
    • Note – this was also discussed at the WGM with same recommendation.

    • Motion to find Not persuasive with modification: 

      • We suggest that the implementation team creates a profile on Basic in R4 to mimic NutritionIntake as much as possible and then when R5 comes around to adopt to switch to R5 NutritionIntake.  See discussion: https://confluence.hl7.org/pages/viewpage.action?pageId=139660361#id-2022091923WGM-Wednesday-Q1:MeetingNotes

      • Marti Velezis / Jose Costa Teixeira: 7-0-2
      • Assigned to Olivia Bellamou-Huet 
• ServiceRequest - groupIdentifier
  • Look for other OO resources with group identifier pattern 
  • Marti to submit JIRAs as necessary for discussion next time

• Meeting adjourned at 4:02PM EST

Next meeting:  January 23, 2023 (after January 2023 WGM)

--------For future meetings---------

• Discuss at Next Meeting: 
  •  Nutrition
    • FHIR-32294 - Does NutritionIntake resource exist?
      • The resource exists – need to check why this is still open
      • At the time of ballot the resource may not have been included in JIRA Spec.  It was added (by John D.L. Nolen).
      • Suggest it be closed now that it an be located in JIRA and is in the CI Build.
• Discuss at WGM
  • Device-related tickets
    • Device
      • Device - Device Definition Parent/HasPart
        • Move this forward with Device.parent and DeviceDefinition.hasPart
      • FHIR-38870  - All request resources should support the fields from the request pattern
      • FHIR-39173  - Consider new datatype for instantiatesCanonical/instantiatesUri
      • Device Usage (http://build.fhir.org/deviceusage.html)
        • FHIR-39046  - Critical use cases for Device(Dispense)
      • DEV Follow-up Topics
        • Device - Device Definition Parent/HasPart
          • Move this forward with Device.parent and Device.hasPart
        • FHIR-39046  - Critical use cases for Device(Dispense)
          • Need to pull some of the uses cases into the DEV on FHIR group for discussion (e.g., Representation of a web based application as a source of information (i.e. is the browser instance or the server the source, I expect the server).; Devices representing CDS algorithms; Imaging equipment.
        •  Device.specialization
          • See: Device/Definition Specialization - DEV did not meet last week to discuss final recommendation
        • Device Settings   
          • FHIR-39322 - Device.property definition overlaps with DeviceMetric and Observation
          • FHIR-39501 - Clarify whether others can create Device setting observations
          • FHIR-39244 - Add example of and/or guidance on how to associate device settings with clinical observations. See ticket FHIR-38917
          • FHIR-38917 - Add example of and/or guidance on how to associate device settings with clinical observations

--------end of call--------

INVENTORY BACKLOG