This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "September 29, 2011 Behavioral Health CCD Project Conference Call"

From HL7Wiki
Jump to navigation Jump to search
m (Created page with "= Financial Management Working Group Meeting= Return to FM WG Wiki ---- ==Attendees== * [mailto:Kathleen.Connor@comcast.ne...")
 
m
Line 17: Line 17:
 
#* '''[http://gforge.hl7.org/gf/download/trackeritem/2045/8703/HL7PSS-BehavioralHealthDAMandCCDv1.docx Behavioral Health CCD implementation guide (BH CCD) project]''' to commence soon. The requirements analysis will be balloted in January. "HL7 Behavioral Health Domain Analysis Model, Messages, and CDA Profiles for Financial Management WG at Project Insight # 800 and TSC Tracker # 2045.  Cosponsored by CBCC and SDWG, the Behavioral Health CCD project is intended to evaluate the currency and comprehensiveness of HL7 Behavioral Health and Social Service standards against emergent requirements in the US  Realm."  
 
#* '''[http://gforge.hl7.org/gf/download/trackeritem/2045/8703/HL7PSS-BehavioralHealthDAMandCCDv1.docx Behavioral Health CCD implementation guide (BH CCD) project]''' to commence soon. The requirements analysis will be balloted in January. "HL7 Behavioral Health Domain Analysis Model, Messages, and CDA Profiles for Financial Management WG at Project Insight # 800 and TSC Tracker # 2045.  Cosponsored by CBCC and SDWG, the Behavioral Health CCD project is intended to evaluate the currency and comprehensiveness of HL7 Behavioral Health and Social Service standards against emergent requirements in the US  Realm."  
 
#** Please use the following pool to specify which day/time slot we should select for the '''weekly''' project meeting: [http://www.doodle.com/behprcx8tby8y85z use this Doodle poll to select the appropriate time slot]
 
#** Please use the following pool to specify which day/time slot we should select for the '''weekly''' project meeting: [http://www.doodle.com/behprcx8tby8y85z use this Doodle poll to select the appropriate time slot]
 +
==Action Items==
 +
#Kathleen
 +
#*Create the [http://wiki.hl7.org/index.php?title=Behavioral_Health_CCD_Project_Resources Behavioral Health CCD Project Resources wiki page] containing resource links
 +
#*Outreach to Rick Howard
 +
#Ioana
 +
#* Draft outline for the Domain Analysis Model in the modeling tool (RSA 8.0)
 +
#Nik Garifalos
 +
#* Provide state contacts and/or additional state behavioral health core data sets information
 +
#Madan (assisted by Erin)
 +
#*Prepare high level project plan with milestones and target dates
 
==Minutes==
 
==Minutes==
----
+
'''Housekeeping'''
Housekeeping
 
 
----
 
----
 
*[http://www.hl7.org/documentcenter/public/wg/fm/minutes/2011%2009%20_FM_WGM_Minutes_San%20Diego_Draft.docx Minutes] from the September Working Group Meeting have been posted on the [http://wiki.hl7.org/index.php?title=Financial_Management#FM_September_2011_WGM_Agenda_and_Meeting_Minutes Financial Management].  They will be approved during the next FM conference call on October 6th.
 
*[http://www.hl7.org/documentcenter/public/wg/fm/minutes/2011%2009%20_FM_WGM_Minutes_San%20Diego_Draft.docx Minutes] from the September Working Group Meeting have been posted on the [http://wiki.hl7.org/index.php?title=Financial_Management#FM_September_2011_WGM_Agenda_and_Meeting_Minutes Financial Management].  They will be approved during the next FM conference call on October 6th.
Line 28: Line 37:
 
*The biweekly Financial Management work group call will continue every other Thursday as planned (next meeting: October 6th at 2 PM Eastern)
 
*The biweekly Financial Management work group call will continue every other Thursday as planned (next meeting: October 6th at 2 PM Eastern)
 
----
 
----
Madan provided an overview of the Behavioral Health CCD project
+
'''Overview of the Behavioral Health CCD project'''
 
----
 
----
*'''Background''':
+
'''Background''':
**This project stems from a need on the part of the Arizona department of XXXXX to capture patient demographic and assessment data from Behavioral Health providers in their community network.
+
*This project stems from a need on the part of the Arizona department of XXXXX to capture patient demographic and assessment data from Behavioral Health providers in their community network.
 
**The current approach is using a fixed-length file which is not easily extensible
 
**The current approach is using a fixed-length file which is not easily extensible
 
***When a new field is required, an existing field (of sufficient length) must be dropped to allow the new field to be added in its place. (The file has now been modified from its original state of around 168 fields to about 55)
 
***When a new field is required, an existing field (of sufficient length) must be dropped to allow the new field to be added in its place. (The file has now been modified from its original state of around 168 fields to about 55)
Line 38: Line 47:
 
**In addition to replacing the data capture approach, this project could help Behavioral Health providers who are otherwise eligible for the Meaningful Use program to exchange a relevant CCD and enable them to claim those dollars  
 
**In addition to replacing the data capture approach, this project could help Behavioral Health providers who are otherwise eligible for the Meaningful Use program to exchange a relevant CCD and enable them to claim those dollars  
 
*This was recently approved as an HL7 project, and the next step is to gather and analyze the relevant behavioral health data sets and requirements, including code sets from the VA, DOD, SAMHSA and others, as well as any public health reporting requirements that have been included in Meaningful Use.
 
*This was recently approved as an HL7 project, and the next step is to gather and analyze the relevant behavioral health data sets and requirements, including code sets from the VA, DOD, SAMHSA and others, as well as any public health reporting requirements that have been included in Meaningful Use.
*'''Scope and High-Level Timeline''':
+
'''Scope and High-Level Timeline''':
 
**Domain Analysis Model (DAM) – for ballot in January 2012
 
**Domain Analysis Model (DAM) – for ballot in January 2012
 
**Implementation Guide based on the DAM – constraining the CCD (with additional templates possibly) – for ballot in March (or May?) 2012
 
**Implementation Guide based on the DAM – constraining the CCD (with additional templates possibly) – for ballot in March (or May?) 2012
 
*'''Next Steps ''':
 
*'''Next Steps ''':
*
+
*Develop the project plan – milestones
 +
*Divide the work into two or three buckets
 +
#Map Arizona core data to CCD, focusing on C32 components (medications, problems, results, etc.) – taking into account that we will review the recent CDA Consolidation ballot for the latest pertinent information.  Demonstrates early value in that it shows we can create a BH profile for Meaningful Use
 +
#*Outreach to other community Behavioral Health providers to incorporate additional sets of requirements
 +
#*Ensures that the requirements are comprehensive
 +
#**Most states have a code data set based in part on SAMHSA reporting requirements
 +
#Capture workflow as it impacts creation of data
 +
#*Data captured in BH provider’s EHRs ends up in state and federal (e.g., SAMHSA) reports
 +
#Review vocabulary requirements for Meaningful Use and map to the Behavioral Health data sets, looking for gaps
 +
#*Where there are gaps, work with LOINC and IHTSDO (SNOMED-CT) to determine if new values need to be assigned
 +
#*Create bindings to value sets
 +
#Develop Implementation Guide
 +
Discussion
 +
*Mapping to standard terminologies is quite a significant task.  Madan has a couple of subject matter experts on the core data sets who can assist by helping to understand the core data sets:
 +
**Daniel Crow
 +
**Mike Sheldon
 +
*We first need to ensure that the CCD can support the conceptual message that you are trying to replace (legacy flat file); then once that is confirmed, can we put values from standardized terminologies to those data
 +
*Nik Garifalos (FEI) will provide contact information and/or core data sets from the 19 states that are supported by FEI. 
 +
**The state core data sets overlap with the ([http://oas.samhsa.gov/dasis.htm#teds2 TEDS],[ http://www.samhsa.gov/co-occurring/topics/data/nom.aspx NOMS] and [http://www.samhsa.gov/dataoutcomes/urs/ URS] data set requirements)
 +
*Mary Kay suggested outreach to Rick Howard, who is the current MITA co-chair for Medicaid requirements
 +
**Rick is a big supporter of build once, re-use
 +
**The challenge in getting Rick’s involvement is that MITA 3.0 is scheduled to start its implementation
 +
***They will be releasing a complete area at a time with a 30-day review period.  First set to be released in October: Provider, Member
 +
** Contact Aaron Karjala, Deputy CIO, Oregon State Health Authority [http://www.mmisconference.org/mmis_archives.htm from 2011 MMIS Attendee list], as he has expressed interest in this area and the need to combine Behavioral Health data with their Medicaid data (where unlike Arizona, they can.  AZ doesn’t have a data sharing agreement to do so)
 +
*Mary Kay also suggested that the high level Next Steps discussed above should be documented and placed on a wiki page so all the resources are in one place.
 +
*Madan will assume lead role as project manager, and due to an internal deadline has a vested interest in advancing the project as quickly as possible
 +
**Erin Fitzsimmons will work with Madam offline to assist with some of the project management tasks
 +
Next meeting scheduled for: Wednesday, October 5, 1:00 PM Eastern
 +
*+1 770-657-9270, Code: 451256
 +
*Please join the web meeting: https://www1.gotomeeting.com/join/1675057 Meeting ID: 167-505-736
  
 
Return to [[Financial_Management#FM_Conference_Meeting_Minutes|FM WG Wiki]]
 
Return to [[Financial_Management#FM_Conference_Meeting_Minutes|FM WG Wiki]]
 
[[Category:Financial_Management]]
 
[[Category:Financial_Management]]
 
[[Category:Meeting_Minutes]]
 
[[Category:Meeting_Minutes]]

Revision as of 23:17, 4 October 2011

Financial Management Working Group Meeting

Return to FM WG Wiki


Attendees

Agenda Topics

  1. (5 min) Roll Call, approve minutes (on next Financial Management WG conference call, 10/6), call for agenda items
  2. (15 min) Project updates
    • Behavioral Health CCD implementation guide (BH CCD) project to commence soon. The requirements analysis will be balloted in January. "HL7 Behavioral Health Domain Analysis Model, Messages, and CDA Profiles for Financial Management WG at Project Insight # 800 and TSC Tracker # 2045. Cosponsored by CBCC and SDWG, the Behavioral Health CCD project is intended to evaluate the currency and comprehensiveness of HL7 Behavioral Health and Social Service standards against emergent requirements in the US Realm."

Action Items

  1. Kathleen
  2. Ioana
    • Draft outline for the Domain Analysis Model in the modeling tool (RSA 8.0)
  3. Nik Garifalos
    • Provide state contacts and/or additional state behavioral health core data sets information
  4. Madan (assisted by Erin)
    • Prepare high level project plan with milestones and target dates

Minutes

Housekeeping


  • Minutes from the September Working Group Meeting have been posted on the Financial Management. They will be approved during the next FM conference call on October 6th.
  • A new weekly call on Wednesday's at 1 PM Eastern was established to focus on the Behavioral Health project going forward.
  • The biweekly Financial Management work group call will continue every other Thursday as planned (next meeting: October 6th at 2 PM Eastern)

Overview of the Behavioral Health CCD project


Background:

  • This project stems from a need on the part of the Arizona department of XXXXX to capture patient demographic and assessment data from Behavioral Health providers in their community network.
    • The current approach is using a fixed-length file which is not easily extensible
      • When a new field is required, an existing field (of sufficient length) must be dropped to allow the new field to be added in its place. (The file has now been modified from its original state of around 168 fields to about 55)
    • The new approach proposes to use an HL7 structure. Originally planned to use Version 2, but further analysis based on the Arizona Dept of Health Services Behavioral Health Demographic and Outcome Data Set User Guide (DUG) revealed we could use the CCD and extend it based on the A_BillableSocialService_Universal (COCT_RM610000UV06) CMET (Common Message Element Types)from the 2011 Normative edition of Version 3.
      • The BillableSocialService CMET provides detailed information on social services, required to support billing information for an Invoice, Pre-Determination, Coverage Extension or Authorization. The CMET also supports the conveyance of the health, socio-economic, and functional assessment information about the client who is the subject of the social service to augment the clinical services information typically conveyed about a patient.
    • In addition to replacing the data capture approach, this project could help Behavioral Health providers who are otherwise eligible for the Meaningful Use program to exchange a relevant CCD and enable them to claim those dollars
  • This was recently approved as an HL7 project, and the next step is to gather and analyze the relevant behavioral health data sets and requirements, including code sets from the VA, DOD, SAMHSA and others, as well as any public health reporting requirements that have been included in Meaningful Use.

Scope and High-Level Timeline:

    • Domain Analysis Model (DAM) – for ballot in January 2012
    • Implementation Guide based on the DAM – constraining the CCD (with additional templates possibly) – for ballot in March (or May?) 2012
  • Next Steps :
  • Develop the project plan – milestones
  • Divide the work into two or three buckets
  1. Map Arizona core data to CCD, focusing on C32 components (medications, problems, results, etc.) – taking into account that we will review the recent CDA Consolidation ballot for the latest pertinent information. Demonstrates early value in that it shows we can create a BH profile for Meaningful Use
    • Outreach to other community Behavioral Health providers to incorporate additional sets of requirements
    • Ensures that the requirements are comprehensive
      • Most states have a code data set based in part on SAMHSA reporting requirements
  2. Capture workflow as it impacts creation of data
    • Data captured in BH provider’s EHRs ends up in state and federal (e.g., SAMHSA) reports
  3. Review vocabulary requirements for Meaningful Use and map to the Behavioral Health data sets, looking for gaps
    • Where there are gaps, work with LOINC and IHTSDO (SNOMED-CT) to determine if new values need to be assigned
    • Create bindings to value sets
  4. Develop Implementation Guide

Discussion

  • Mapping to standard terminologies is quite a significant task. Madan has a couple of subject matter experts on the core data sets who can assist by helping to understand the core data sets:
    • Daniel Crow
    • Mike Sheldon
  • We first need to ensure that the CCD can support the conceptual message that you are trying to replace (legacy flat file); then once that is confirmed, can we put values from standardized terminologies to those data
  • Nik Garifalos (FEI) will provide contact information and/or core data sets from the 19 states that are supported by FEI.
  • Mary Kay suggested outreach to Rick Howard, who is the current MITA co-chair for Medicaid requirements
    • Rick is a big supporter of build once, re-use
    • The challenge in getting Rick’s involvement is that MITA 3.0 is scheduled to start its implementation
      • They will be releasing a complete area at a time with a 30-day review period. First set to be released in October: Provider, Member
    • Contact Aaron Karjala, Deputy CIO, Oregon State Health Authority from 2011 MMIS Attendee list, as he has expressed interest in this area and the need to combine Behavioral Health data with their Medicaid data (where unlike Arizona, they can. AZ doesn’t have a data sharing agreement to do so)
  • Mary Kay also suggested that the high level Next Steps discussed above should be documented and placed on a wiki page so all the resources are in one place.
  • Madan will assume lead role as project manager, and due to an internal deadline has a vested interest in advancing the project as quickly as possible
    • Erin Fitzsimmons will work with Madam offline to assist with some of the project management tasks

Next meeting scheduled for: Wednesday, October 5, 1:00 PM Eastern

Return to FM WG Wiki