1 / 15

CAIR Interface Presentation

CAIR Interface Presentation. CCALAC NEXTGEN USER GROUP JULY 24, 2014. Important Contact Info. For Stage 2 MU, your contact is: Eric Dansby CAIRDataExchange@cdph.ca.gov

najwa
Download Presentation

CAIR Interface Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CAIR Interface Presentation CCALAC NEXTGEN USER GROUP JULY 24, 2014

  2. Important Contact Info For Stage 2 MU, your contact is: Eric Dansby CAIRDataExchange@cdph.ca.gov CAIR State Help Desk Hours: Monday - Friday 8:00AM - 5:00PMPhone: 800-578-7889Fax: 888-436-8320 Email: cairhelpdesk@cdph.ca.govWebsite: www.cairweb.org Website Region VII: http://www.immunizelink.org/index.htm

  3. What are the requirements for Stage 2 MU?

  4. Measure Specifics

  5. Five Steps to MU Compliance • EHR Upgrade • HL7 2.5.1 • SOAP messaging protocol 2014 90-day reporting can begin

  6. Step 1: Register at http://cairweb.org/imp/ • Registration is at the Site level and includes NPI address, contact, and other general health center information • Choose submission type: • Direct from EHR • Via a distinct Sending Facility (e.g. HIO, vendor/EHR data warehouse, health plan data warehouse, or other data aggregator) • Act as a Sending Facility (e.g. Health Information Exchange) • A secure email will contain Site credentials as well as information on the follow-up steps your Site must take to prepare for data exchange with CAIR

  7. Step 2: Pretesting • Work with your EHR vendor to obtain the proper flat file, called VXU (Immunization Messages) • Inform your vendor and upgrade project manager of your timeline for submitting the message. Let the vendor know you expect their timely support in resolving any error messages (days not weeks) • Submit the message to the the CAIR message validation tool: https://igsstag.cdph.ca.gov/CAIRHL7WebValidator/ • From what we know there is one CAIR rep to assist several regions. His preferred manner of communication is email • CAIR HL7 2.5.1 is the preferred language spec found at: http://cairweb.org/images/docs/CAIR_HL7v251_Spec_for_web.pdf • You will need to resubmit until you receive an auto response from CAIR that your test message was successful

  8. Step 3: Test Submission • You should use the same message format that passed the Pre-testing • You then install a CDPH Client Certificate in order to use SOAP web services (required) by CAIR http://cairweb.org/images/docs/SOAPUI_Instructions.pdf • Now, submit to: http://cairweb.org/imp/ • Failed test will produce an auto response with diagnostic information. As before you will need your EHR vendor’s support to trouble shoot and resolve before you can move to the next step

  9. Step 4: Message Validation • You must enter message validation within the first 60 days of the reporting period • There are 2 components to validation: • Proper formatting of the message • Data quality • Once 50 unique and successful test messages with appropriate data quality have been sent from your EHR, CAIR will move the organization from the test environment to production • You must confirm message success and continue resolving errors in order to move to the next step • You must receive an official notification from CAIR that you have successfully passed Message Validation

  10. Step 5: Ongoing Submission • CAIR recommends daily submission of the VXU messages • You must enter the Ongoing Submission step within 60 days of your reporting period or providers will fail MU Stage 2 • We recommend you move into Ongoing Submission within 30 days • You must correct and resubmit failed messages • What is your expected frequency of submission and who is responsible to submit for all or each of your 2014 MU Stage 2 providers? • How will you work with your EHR provider for timely resolution of failed messages?

  11. Common Issues • EHR interface to CAIR still under development • Does not apply to NextGen • Use of SOAP protocol is not widely tested • Wait time for vendor to implement interface • Not a part of the upgrade • Understanding recovery steps for correcting rejected messages • E.g. CVX/ CPT codes not matching • Obtaining timely vendor support for rejected messages • Limited CAIR resources for our region and expectation of high volume for Q4 but especially December

  12. Which CAIR interface product is right for you? NextGen Rosetta Immunization Interface E-MedApps SevaExchange Interface • Can send HL7, HTTPS, FTP, Flat Files and other file formats • Can send Real time or batch files to Registries • ONC Certified • Can meet stage 2 requirements • SevaXchange sends real-time updates to CAIR of immunizations • Can send HL7, CCD/CCDA, XML, flat files, and custom format files • ONC Certified “EHR Module Ambulatory” • Can be configured to send real-time or batch file messages on a custom schedule • Can meet stage 2 requirements Both interfaces are sufficient for meaningful use. Perhaps consider which organization you feel is best able to meet your timeline, support needs, and budget.

  13. Key points • Begin the process today (if you have not already done so) • Registration can and should be done before your upgrade • Registration is done at the site level • CAIR and your vendors are the best resources for troubleshooting failed messages • Leverage CCALAC for common themes and discovered solutions

  14. Questions?

More Related