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 Notes

• JIRA Tickets on Families/Households:

  • https://chat.fhir.org/#narrow/stream/179280-fhir.2Finfrastructure-wg/topic/Representing.20Family.20in.20Group.20resource
  • Grahame indicated that there is a draft on how to update Group (not yet approved) on how to be able to reference a family:https://build.fhir.org/ig/HealthIntersections/fhir-playground/StructureDefinition-public-health-group.html. 
  • We want to clarify whether "household" would be progresses as well given it could be considered a potential performer.  Hans to add to Zulip. - Marti added to Zulip today
  • OO now needs to look at the resources to determine whether any attributes need to be expanded to include Group enabling referencing a household or family.  OO on FHIR will pick it up.

• • Today's progress

    JIRA	Resource	Element(s)	Response
    FHIR-41410	Service Request	performer	Add Group: Any member of the family could perform the ServiceRequest whether it be a one time event or recurring.
    FHIR-41406	DocRef	author	Add Group: Members of a family may have authored collectively, similar to the care team.
    FHIR-41405	Observation	performer	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-41394	Task	owner, requester, requestedPerformer and performer.actor	Add Group
    FHIR-41395	Transport	requester	Add Group to .requester Need to evaluate performerType; owner for family  Add JIRA for Transport.requester to include CareTeam (Yanick added FHIR-41568)
    FHIR-41415	InventoryItem	InventoryItem.instance.subject	Add Group to InventoryItem.instance.subject  Need to consider other resources for InventoryItem.instance.subject such as Practitioner, CareTeam, etc.
    FHIR-41414	SupplyDelivery	subject receiver	TBD Change Patient to Subject  Subject should include a Reference to Patient, Group, Organization Add Reference to Group to Receiver
    FHIR-41413	DeviceUsage	patient	TBD
    	DeviceDispense	subject performer.actor	TBD
    FHIR-41411	NutritionIntake	reporter performer.actor	TBD Nutrition is able to have a subject of group, but the reporter cannot be a family (=group) nor performer.actor. This seems like an oversight

Next time:

• • FHIR-41448
  • Added Missing CareTeam in DeviceAssociation: FHIR-41567 to be discussed next time
  • FHIR-41568
  • FHIR-41241   
  • FHIR-41186       
  • FHIR-41002

Next Meeting: July 18, 2023

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