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
  • DeviceDispense FHIR Resource Proposal
    • Need to complete work on the resource proposal prior to next WGM
    • Add again for next time.
  • Workplan for working group - 5 meetings until WGM
    • Updated WGM agenda and added topics to our meeting schedule (see above)
    • Modules - We will discuss BDP, Device and NutritionProduct in this forum to ensure consistency across healthcare products; Work to sync with any medication specific patterns or workflow topics.  Nutrition group can do work on their calls and raise issues to bring back to our calls (esp. to harmonize across product resources.
• JIRA Tickets
  • BDP
    • FHIR-40286 - Retracted by David (see ticket for comments) - this is FYI only
    • FHIR-40397
      • Align product code search parameters (see proposed disposition)

      • Suggest that the search parameter: 

        code

        token

        The definition / type of the device (code)

        Device.definition.concept

        update with the following: 

        code

        token

        The definition / type of the device (code)

        Device.type | Device.definition.concept | Device.definition.reference.classification.type

        to be consistent with the other HCP Resources.

        Also need to update: 

        type

        token

        The type of the device

        Device.type | Device.definition.reference.classification.type

        Also need to discuss: 

        Given that Device.definition as codeableReference allows for a codeableConcept for Device which duplicates the Device.type and pass-thru of Device.definition.reference.classification.type - should Device.definition be limited to Reference(DeviceDefinition)?

      • Updated proposed disposition, but still needs further discussion.
  • DeviceAssociation
    
    • Need to complete assessment of Device associations across all of the Resources that referenced device that may need to track the association.
    • See listing below in Inventory Backlog
  • Nutrition
    • Resuming calls on April 12, 2023
    • Project team can work on Nutrition Product, and raise any cross-resource issues back to this group.
  • VisionPrescription
    • Need to plan for analysis of VisionPrescription, added a Confluence page: Module: VisionPrescription
    • Note this was bumped to FMM3
    • Ne to prep for joint meeting with FM at May2023 WGM

Next meeting:  April 3. 2023

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

Did not get to the following: 

• Device
  • FHIR-40384
    • Need to distinguish device-created from transcribed observations
  • FHIR-40335 
    
    • Clarify use of Observation.subject, .device, and .focus for devices
  • Where do we include AI/ML and DTx into our scope
• 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).