ANSI 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: August 8, 2023

Time: 2PM

Coordinates:  Join Zoom meeting: | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)








Note - we repurposed this time to pick up the LIVD discussion - please review meeting minutes here: 2023-08-08 OO - LIVD

Tentative for the next two week we will be discussing LIVD.

Next Meeting: August 29, 2023

-- Next time----

Families/Housholds - Need to finalize next time

JIRA ResourceElement(s)Response
FHIR-41410   Service Requestperformer

Add Group: Any member of the family could perform the ServiceRequest whether it be a one time event or recurring.

7/18 - The CareTeam should perform the Service.  The CareTeam resource allows for Family/Household to be described in the best way possible (e.g., category, name and/or participants if known).

Pick up here today
FHIR-41406  DocRefauthorAdd Group: Members of a family may have authored collectively, similar to the care team.
FHIR-41405  Observationperformer

Add Group: Members of a family may have authored collectively, similar to the care team.

Note: Observation.performer is normative and this will add an option not previously available

FHIR-41394TaskownerAdd Group
requesterAdd Group
requestedPerformerAdd Group
performer.actorAdd Group

Add Group to .requester

Need to evaluate performerType; owner for family 

Add JIRA for Transport.requester to include CareTeam (Yanick added FHIR-41568)


Add Group to InventoryItem.instance.subject 

Need to consider other resources for InventoryItem.instance.subject such as Practitioner, CareTeam, etc.





  • Change Patient to Subject 
  • Subject should include a Reference to Patient, Group, Organization
  • Add Group a
  • DeviceUsage.informationSource 
    • Add Group for Family


  • DeviceDispense.subject
    • Add Group for Family


  • DeviceDispense.receiver
    • Add Group for Family

    • Remove Patient and RelatedPerson (Add a new JIRA)
    • We are NOT adding Group


  • OO notes that on the BDP Dispense resource there is no attribute that would indicate a reference to the family (or household) as the dispense is always to the intended patient who is to receive the BDP as a treatment/procedure.


GG - Nutrition is able to have a subject of group, but the reporter cannot be a family (=group) nor This seems like an oversight




Backlog Issues

  • FHIR-38985
    • WGM Work: FHIR-38985 - What happens if the definition deviates from the Observation? TRIAGED
      • With the removal of Instantiates[x] from Observation - this issue will be moved to the extension
      • Extension definition will need to be updated: 
        • If inconsistent - an error can be thrown
        • From OO resources - the deviation can be added as a rule/constraint
        • Review of Extensions - on the stats page – GG to send this out again
        • 5/15 - will give GG a week to get back to us on this action item
  • FHIR-38833
    • This ticket was reopened after R5 publication
    • Added to the FHIR-I session at WGM on Thursday Q2
    • See if we can get FHIR-I to add another time slot for Rob to participate
    • WGM Work: FHIR-38633 - Target Awareness Element or Extension TRIAGED
      • For R5 the proposal for an extension was to get some experience with the requirement; we should reconsider the proposed disposition 
      • Should this be "Communication" instead of a separate extension that was proposed for R5
        • Actual communication with the patient should use the Communication resource.
          • user (patient/clinician) acknowledges the communication by marking the action in a system
        • Flag the awareness of the patient b/c that the information was presented to the patient but there is no systematic acknowledgment
        • Lesser fidelity communications – push the communication but receipt is unknown (e.g., "null" flavor)
        • Need to raise across resources on how to capture 
      • 5/15 - will give GG a week to get back to us on this action item

  • FHIR-19253
    • Not inclined to change .code to 1..* but need to discuss how to handle the use case of multiple imaging studies with one diagnostic report. 
    • WGM topic for PC and II joints