Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees


Present

Name

Affiliation

  •   
Enablecare
  •   
Viet NguyenStratametrics
  •   
Ulrike MerrickVernetzt, LLC 
  •   
Anupam ThakurBCBSFL
  •   
Corey SpearsInfor
  •   
BCBSAL
  •   
Casenet
  •   
Holly WeeksRegence
  •   
Jeffrey DanfordAllscripts
  •   
Joseph QuinnOptum
  •   
Laurie BurckhardtWPS Health Solutions
  •   
Lindee ChinEdifecs
  •   
Lisa R. NelsonMaxMD
  •   
Linda MichaelsenOptum
  •   
Mark TaylorReady Computing
  •   
Peter Muir
  •   
Rajesh GodavarthiMCG Health
  •   
Samir JainReady Computing
  •   
Sreenivas MallipeddiMCG Health
  •   
Susan BellileAvaility
  •   
Susan LangfordBCBST
  •   
Tony BensonBCBSAL
  •   
Yan WangMaxMD
  •   
Jeanie SmithBCBSFL
  •   
Rachel E. FoersterCAQH Core
  •   
Mary Kay McDanielCognosante
  •   
Greg LindenLinden Tech Advisors
  •   
Eric Haas
  •   
Anthem
  •   
Dawn PerreaultBCBSM
  •   
Jennell Stewart
  •   
Kat RuizUNC Health
  •   
Michael GouldIBC
  •   
Tony Laurie
  •   
Karen L. ZapataAnthem
  •   
Ann GallagherOptum
  •   
eClinical Works
  •   
Frank HoneVeradigm
  •   
BCBS AL
  •   
Lynn PerrineLantana
  •   
Nancy BeavinHumana
  •   

  •   
Ralph Saint-PhardHealow
  •   
Serafina Versaggi
  •   
Seth ParadisHealow
  •   
Sheryl TurneyAnthem
  •   
Todd Johnson
  •   
Julie MaasEMR Direct
  •   
Duane WalkerBCBSM
  •   
Epic
  •   
Jennifer CurryRegence
  •   
Regence
  •   
David DeGandiCambia
  •   
Cigna
  •   
Kate ReesCambia
  •   
TIBCO
  •   
UHC
  •   
Ric LIghtHumana
  •   
TorQuailla AultmanNC.gov
  •   
Chris JohnsonBCBS AL
  •   
Cigna
  •   
Anna MeisheidCMS
  •   
Gino Canessa
  •   

  •   
Scott Stuewe
  •   
HealthLX
  •   
HealthLX
  •   

  •   

  •   
Tracy M. FitzgibbonRegence
  •   
Jordan StoreyRegence
  •   
Jonas
  •   
Kayla SuaProvidence
  •   
EMR Direct
  •   
Sasha Volkov
  •   

  •   
Providence
  •   

  •   
Roland GamacheAHRQ
  •   

  •   
Rim Cothren
  •   
Eric SullivanInnovalon
  •   
Jason
  •  

  •  
Michelle Hunt
  •  
Dacarba
  •  
Cedars-Sinai
  •  
Rob WilmotCerner
  •  

Minutes Approved as Presented 

...

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Decision Link(if not child)
ManagementReview ANSI Anti-Trust Policy



Ballot and Connectathon Schedule

Recap Alerts IG Goals
  • Not doing a full V2 mapping for all scenarios
  • Covering minimally required information for Admits and Discharges
  • Common object of exchange for push/unsolicitied notifications and subscriptions
    • Should be same regardless of reason for alert
    • Enough information for receiver to determnine if alert is of interest
    • Enough information for receiver to ask for more information 


FHIR Messaging - Collected Questions
  • FHIR experts
    • Riki reached out to Rene
    • Also will post on fhir.chat.org
  • Created a Zulip stream - has been moved to the Messaging stream
  • What do vendors support?


Rationale for Revisiting Approach to Alerts
  • FHIR Messaging intended to handle communications between organizations who don't have business relationships with each other
  • Any technical differences between approaches?
    • Concept of addressing a message to it's final receipient using Messaging (MessageHeader type of information)
    • Transport mechanism doesn't have to be a RESTful interface
  • Content model - same information using MessageHeader as the first resource to define the event/content
  • Communication is intended to be a record of a communication, not the communication itself - though it has been used to be the communication itself
  • Messaging was intended to be the 'wrapper' for a message going somewhere
  • May test Communication and Messaging in Connectathon
  • Not advocating that someone switch from V2 messaging to what we're doing
    • We're not trying to map V2 to FHIR
    • External, inter-organizational broadcast that an event has occurred - not replacing any internal infrastructure
    • This is a way of extending event notifications for non-connected parties without needing to put in place V2 messaging infrastructure
    • Few payers have a V2 connection with every single provider that sees one of their members
    • If payer is notified via V2 message that patient was admitted, this would be the way the payer would notify the PCP or other members of the care team
    • Notification of other future events don't have an existing infrastrucutre except for ADT, public health, lab
  • When we implement the Alerts IG, will we meet the Transitions of Care HEDIS measure?
    • Measuring that the PCP or ongoing care provider was notified of the admission
    • If the sender doesn't know who the members of the care team are, they can send the notification to the HIE or to the payer, who could then send to patient's care team
    • If discharging institution sends notice to HIE saying patient has been discharged, and HIE sends to care team - what documentation is needed that this has occurred?
    • Would need to look at the metadata required in the measure - guessing this doesn't include all the data needed
    • Communication is best if you have both ends identified - sender and receiver
    • If sending to HIE, Messaging or Communication, we don't know if the intended receiver got the notification
    • If a significant part of what we're doing is to keep a record of what happened, then may need to use Communication to satisfy that need
    • Messaging may be mechanism going from point A to point B, but Communication to keep a record that we did it?
    • Gini McGlothin to follow up with Ben Hamlinto ask him to weigh in
  • There are likely other measures that might have implications
  • IG should restrict transport paradigm - SHOULD use FHIR $process-message operation
    • May become SHALL in the future


Review FHIR Messaging Artifact
  • Communication allows you to have more recipients
    • MessageHeader doesn't have Patient or Related Person (you can't delcare the patient as a receiver)
  • MessageHeader.Focus is limited - subject line of an email, trigger event, what's being changed
    • Focus doesn't tell you what's in the bundle
  • MessageDefinition - defines what's in the message (particular bundle) and what's in the focus
  • MessageHeader doesn't point to all the reosurces in the bundle


Connectathon Planning
  • Test script requirements to be updated to test Communication and Messaging
  • Still planning on August 28th and Sept 4th for Virtual Connectathon - both approaches may not be available for the 28th 

ManagementNext Agenda

Adjournment
Adjourned at at 1:02pm ET

Supporting Documents

Outline Reference

Supporting Document

Minute Approval
Meeting PPT Presentation
Messaging Using FHIR Resources

https://www.hl7.org/fhir/messaging.html

FHIR Messaging Video

 https://vimeo.com/171533785

Virtual Connectathon Recorded Kick-Off Presentation2019-07-31 12.05 Da Vinci - Alerts_ Notifications_Virtual Connectathon Presentation.mp4
Alerts Implementation Guidehttp://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html

...