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-11-15 WGM
    • all please review and add where indicated or edit as needed
    • We already have these posted but will vote next week
  • https://confluence.hl7.org/display/OO/2023-09-21+Main
    • Motion to accept as distributed.  Kathy Walsh, Riki Merrick
      • Against: 0; Abstain: 0; In favor: 12

OO Project Proposal Triage

• None

Topics

• COW IG Proposal
  • Clinical Order Workflow (COW)
  • Not yet ready.  Still needs some updates from Jose Costa-Teixeira and then needs to be voted on by OO (if enough quorum/attendance could happen during COW call).
• Anatomic Inventory and Person Characteristics Project PSS-2280
  • Have some input from Canadian Sex and Gender and some other interested parties
  • Target is May 2025 ballot
  • Needs a lot more work
  • Need more international participants
  • Need to find the correct link to Grahame’s starting material for organ inventory
• v2-FHIR JIRA Question
  • IG build is getting better, but are now tackling observation jiras
    • Some have been decided, but need vote
    • Others need to be dispositioned
    • What time would be good to bring these to more folks outside of the V2-FHIR mapping call?
  • OO on FHIR call on Tuesday October 3, 2-3 PM ET
  • Hans to forward list of items to OO-Co-chairs and Craig
• Panel Discussion Update
  • Background info
    • https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Laboratory.20Report.20-.20Representing.20Panels
      • Only got input from 1 implementer
    • (for more background see here: https://chat.fhir.org/#narrow/stream/179256-Orders-and-Observation-WG/topic/Usage.20of.20panel.20of.20Observations)
    • Option A:
      • Using observation as a grouper (via observation.hasMember) within one DR that represents to overall report
    • Option B:
      • Using DiagnosticReport to represent 1 ordered panel
  • In Europe need to have a document approach for the overall report, using composition to organize the elements with one or more sections, so that the signature nature of the CDA can be retained
  • At WGM there seemed to be a strong leaning towards option B
  • In Europe they are currently use CDA for lab reports, which has the ability to sign the document, so in FHIR that is currently done as a FHIR composition
  • We could add an extension to DR for legal authenticator to represent the document in FHIR, which would make it more consistent to get the data across the same way
  • How to order DR sections – that would still be handled by pointing to composition to represent
  • FHIR document:
    • First resource is composition, bundle type = document all resources must be findable from the composition (which is backwards from how we want to reference from DR to composition to arrange the pieces – SD WG was ok with that, but Grahame does not consider just reverse linkages to
  • Option B is what the larger EHR-s vendors have
  • Using observation for grouping has been discussed for reflex testing
  • Original intent of DiagnosticReport is what the laboratory sends
  • Panel is an orderable test with many observations
    • Some of those observations can also be ordered separately
  • Can a panel be part of another panel?
    • OrderSets – that is for convenience of the physician
  • V2-FHIR mapping equivalent:
    • ORC to ServiceRequest and task
    • OBR to ServiceRequest (when in an order message) and DiagnosticReport (when in a result message), which would result in multiple DiagnosticReports in the FHIR translation
    • OBX to observation
    • Have more discussion around this in OO on FHIR calls
  • Seems we may end up with different solutions at a country level, which we should try to avoid
  • IPS is at a higher level
  • Next steps:
    • Put back on the agenda main call next week and have longer discussion on OO on FHIR in 2 weeks 10/10 2-3 PM ET
    • FHIR document representation clarification
    • Option A or Option B

Adjourned 2:02 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

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