Page tree
Skip to end of metadata
Go to start of metadata

Chair:  Ulrike Merrick

Scribe: Dana Marcelonis
 

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. Fitzgibbon
  •  
Jordan StoreyRegence
  •  
Jonas
  •  
Kayla SuaProvidence
  •  

  •  
Sasha Volkov

Minutes Approved as Presented 


This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."


Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

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



Ballot and Connectathon Schedule

Alerts Implementation Guide Update
  • FMG did not approve Alerts IG proposal last week, and recommended some changes
    • Limited scope to admit and discharge scenarios
    • Future scenarios will be collaborating with HL7 working groups focusing on those resources
    • IG for this round only focusing on push - FMG suggested using Operation, so that's what we're doing
    • Note to balloters - will support subscription in future, but will take into account what Argonaut is doing and align with that project
  • CDS call today re: IG - no negative comments thus far, will vote to move it forward for ballot next week
  • FMG meeting again at 4pm ET to get IG proposal approved


Alerts IG Review:  http://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html
  • Alerts Bundle Profile
    • Clarified that status is the status of the communication, not the event
    • Alert gives you information that an event occurred, but not all the information related to the event
      • Alert gives you enough information to act upon it, and optionally retrieve more information, but this workflow is not included in this IG
    • Alerts Bundle Profile includes Communication, Patient, Encounter
  • JSON examples are included in the IG
  • Use Cases section
    • Applying framework to a specific use case - admit/discharge
    • In future framework can expanded upon to be used for other use cases
  • Alert Endpoint Profile
    • Endpoint/address to find additional information
    • May contain an authorization token
  • Can have multiple alerts in a single operation - can be same patient or different patients
  • Notes to balloters
    • Reliable delivery
    • Error handling
  • Must Support
    • If you have it in your system, you have to send it
    • Send only what the recipient needs
      • Assuming that intermediaries/clearinghouses have this information
      • Intermediary might send something different from what it gets because the end user shouldn't see all the information
    • IG should be clear re: what is/not required - today's problem is that everybody does alerts differently - we should try to tighten this up in future versions of the IG
      • Framework is generic, but in use case section we could nail it down further
      • HL7 has cross-paradigm storyboard - lighter version of care plan analysis model - this is place where unique situation (e.g., meals on wheels or ACO) would be defined
      • IG is clear on what you must send as the sender to the recipient; however, as the recipient you may be connected via intermediary instead of directly connected, and this is where different needs may be defined
      • This should be clarified in the IG
      • Note to balloters re: should we be more specific in defining the intermediary scenario
      • Da Vinci deployment membership category was added so that intermediaries, etc. can be more involved
      • First iteration of IG is Minimum Viable Product (MVP)
  • Expand note to balloters re: Intermediaries
    • Make sure that recipients of the same type/category receive the information in the same way (different types of recipients may receive different information)
  • Security section
    • Expecting comments on this - needs to be fleshed out more
  • Eric Haas needs to change title of IG - not a ballot for comment, it's STU ballot
  • One value set included in IG - Communication Topic
    • Can we map from V2 to this?
    • Corresponds to Encounter Class Codes
    • Could do a concept map in FHIR - would be a good ballot comment if needed
    • If I have a FHIR alert and a V2 alert, how can we compare/map for statistical purposes?
      • Draft mapping that Cambia had provided
      • V2 to FHIR mapping project
    • Concept map vs. structure map (structure of a V2 segment and maps to FHIR resources)
    • Goal of this work is not to do a structure map - this is already being done in V2 to FHIR workgroup effort - this is intended to be a lighter weight effort to let someone know that an admit/discharge has occurred


Connectathons

September Ballot Sign-Up Reminder
  • September Ballot sign-up closes Aug 8th
  • Da Vinci IGs: Alerts, Payer Coverage Decision Exchange, Prior Authorization Support, Documentation Templates & Rules, and PDex Directory

ManagementNext Agenda

Adjournment
Adjourned at 12:57pm ET

Supporting Documents

Outline Reference

Supporting Document

Minute Approval
Meeting PPT PresentationDa Vinci Presentation 20190724Alerts-Notification.pptx
Alerts Implementation Guidehttp://build.fhir.org/ig/HL7/davinci-alerts/branches/master/index.html
FHIR Subscription Presentationhttps://docs.google.com/presentation/d/1FyX_6Nx1_NStXwJkgQ_ujSo_qf0ELQ9LNtrtpbb5Kpg/edit?usp=sharing
Draft Alert Data Mapping - Communication & Detected IssueAlerts/Notifications Mapping
Page to collect Data Element RequirementsAdmit / Discharge Alert Requirements
Page to collect Glossary TermsAlerts/Notifications Glossary Terms


Action items


Create Decision from template