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 MINUTES

• JIRA Tickets
  • PACIO Topic - re: Service Request (David Hill )
    • Use of US Core Service Request vs Consent for Treatment to express patient advance care preferences as part of the PACIO Advance Directives Interoperability IG.
    • 
    • Originally used goal for preferences, but then decided to use observations
    • At WGM had more discussion and going back
      • Preference = what, without how to do it = use goal
      • when explicit about how = use ServiceRequest
      • but then were told to use Consent for treatment
        • R5 has more attributes, the scope no longer incudes advanced directives, but the category vocabularies support it
        • IG is based on R4, so would have to use extensions to support the R5 attributes needed for
        • data creates the flexibility to have different resources referenced
          • Problem may be that it references a procedure, that isn’t truly a procedure that has happened
        • Zulip chat: https://chat.fhir.org/#narrow/stream/179280-fhir.2Finfrastructure-wg/topic/ServiceRequest.2Eintent.20ValueSet
      • what codes are in consent.purpose?
        • ADD LINK (V3 purposeOfUse)
      • problem is that the use case is hypothetical
      • is this similar to transport (documentation of vs. actually making this happen)
        • use task to operationalize it
      • For discussion slides from Dave Hill
      • We think ServiceRequest is not a good fit
      • Next steps:
        • use consent (and maybe ServiceRequest) and model the different advanced directives they want to cover to see how well it fits
• IG proposal:
  • Updates made to the Clinical Order Workflow (COW) IG Proposal which is still in the "pending' state.
  • Action item from 4/28: Please review the IG proposal and make any comments on the proposal with any related IGs and/or additional use cases
    • No comments added to that meeting page with suggestions
    • Need to determine when the IG proposal will be submitted
    • Leave the ? after Immunization / medication – take out pharmacy related references
    • Does inventory fit into “clinical” order?, though the same principal should also apply to inventory, but those are not clinical
    • Add BPM+ to involved parties
    • Add SDOH Clinical Care IG and Gravity project code extensions as content source
    • Examples:
      • Ordering DME post hospitalization
      • Ordering medically appropriate home delivered-meals post hospitalization
    • Next steps:
      • Review and bring back next week

Next meeting: June 2, 2023

JIRA Backlog (time permitting)

Chat history