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

Administrivia

Approve Minutes

• • 2023-09-07 Main

    • Motion to accept as updated/published.  JD Nolen, David Barwin
      • Against: 0; Abstain: 0; In Favor: 12
  • 2023-09-11-15 WGM
    • all please review and add where indicated or edit as needed
    • To be posted by 9/29

OO Project Proposal Triage

• None for today

Today's Topics

• USCDI Comments
  • were submitted
• ISA Comments
  • CPT-PLA were submitted
  • if any others would need to get on the agenda ASAP
• FHIR R6
  • Will have 2-3 for comment ballots before normative starts
  • Use priority list (https://confluence.hl7.org/pages/viewpage.action?pageId=161078076#id-2023050812WGM-R6Planning) to determine focus and then the dashboards to tackle.
  • See if we can focus on getting block votes together on open jiras – in special calls prep, then vote on main
  • Implementer survey on where we want feedback on for normative resources
    • Need to pull this together ASAP
  • Regardless if a resource is marked as normative, implementers expect ALL R6 content be normative
  • Basically the privilege of not following the normative rules will go away with R6
  • So we will need to time box and focus on major topics and patterns.
• WGM Recap
  
  • Meeting Highlights
    • Families JIRA – OO Families/Household/Workplace/Event JIRAs page has been updated with Patient Care resources;
      • Scope changed to include workplace and events
      • For some actor roles group makes sense, not for others
      • FHIR-I is setting up a taskforce to make this consistent
        • OO indicated that our analysis of OO owned resources be considered by tis group
        • This group should include reps from all WGs that have affected resources
        • TSC may review this once the work is completed
      • need to pull from notes prior to sharing this with the Task Force that will be pulled together to discuss this across FHIR Resources
    • See Information Modeling from CG - re: MolecularState Resource (along with Sequence)
    • Backport Extension - January 2024 ballot
    • Gender Harmony Cross Paradigm IG publication request went to TSC, some planning around future maintenance
    • Reviewing the minutes by quarter
      • 9.1 comments related to use of OBX will be discussed in V2 Management – Fridays 11 AM – will coordinate with submitter and V2 Management co-chair on the date for this meeting
    • GC introduced new resource alongside sequence called molecularState
    • Did some FHIR ticket prep work – these will be in a block vote for next OO main call – Marti will review these to find candidates
    • Jan WGM is 4 days - there is discussion on being on UTG+5
• Panel Discussion Update
  • Goal is to have just one option
    • Currently there are 2 options:
      • Option A = observation.code has panel code and all members are in the observation.hasMember
      • Option B = Panel code in DiagnosticReport.code
    • Both options support reflex testing
    • In option B you are losing the option to use composition for overall report structure = represented form and overall report status
    • Should DiagnosticReport be a specialization of composition to resolve this, so that you could use the composition
    • You would need to have separate compositions for each DiagnosticReport and that should be different from the
  • Will continue on this topic tomorrow on the lab call
  • Jose will revive the zulip thread of specialization on observation = parameterized resources
• COW call:
  • can we find a new call time, so Jose can join?
  • BPM+ could join at current COW call time
• Characteristics Project - Next week

Adjourned 2:03 PM ET

Any updates?

UP-44 -no value set content defined for v2 table 963 value set 

• Leaving UP-44 open for now – so that the new tickets and this one can be linked

• V2 Dashboard

FHIR Discussion Topics: 

Block Vote Pulled JIRA

JIRA Triage

The following are draft pages to organize and author content for each of our health care product resources: 

• BiologicallyDerivedProduct
• Devices
  • some work by devices WG
  • do we need to differentiate lab devices (pre/post- analytical devices from analytical devices in the lab)?
  • Need to decide to what level of detail this page should go, or if we need this then how to document some of this content = may not belong here, but rather on the device related resource pages
• Nutrition Product
• VisionPrescription

OO Resource Coverage

• Need to discuss developmental roadmap for each of the OO resources for R6
• Added R6 planning to WGM agenda
• Need to discuss what needs to be done prior to WGM to prep for discussions
• Add Resource reorg comments to module pages

Notes

• Marti revised related resource for each topic area to where the resources align to current modules
• Definitional resources were in workflow (pattern is still there) but those are now in administrative – Marti and Jose to take off-line