1 / 26

EVVE 101

EVVE 101. Rose Trasatti NAPHSIS Project Manager The NAPHSIS/NCHS Collaboration Past Successes and Future Challenges Salt Lake City, UT June 3 rd – 7 th , 2007. What is EVVE™?. Electronic Verification of Vital Events Message based query system

chloe
Download Presentation

EVVE 101

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. EVVE 101 Rose Trasatti NAPHSIS Project Manager The NAPHSIS/NCHS Collaboration Past Successes and Future Challenges Salt Lake City, UT June 3rd – 7th, 2007

  2. What is EVVE™? • Electronic Verification of Vital Events • Message based query system • Authorized users have a single interface to generate a query to any participating vital records jurisdiction throughout the country

  3. What is EVVE? • NAPHSIS national clearinghouse (hub) • Standard Internet-based XML Vital Event Transaction (VET) • Knowledge database for jurisdiction rules and data availability/mapping • Transaction log of exchanges of requests and responses between users and the jurisdictions via the hub • Management and billing reports

  4. What are the benefits of EVVE? • Protects against potential fraudulent activities • Improves customer service • Facilitates rapid access to accurate and verifiable vital record data • Supports the future of business within the vital records offices • Integrates easily with current legacy systems • Safeguards the confidentiality of data • Offers a secure mechanism for communication between agencies and vital records offices

  5. EVVE Query Types • Birth Verification • Applicant has a certified copy of the birth certificate in their possession • Birth Certification • Applicant does NOT have a certified copy of the birth certificate • Death Verification • Applicant has a certified copy of the decedent’s death certificate in their possession • Death Certification • Applicant does NOT have a certified copy of the decedent’s death certificate

  6. Birth Verification • Required Fields • Registrant First Name • Registrant Middle Name • Registrant Last Name • Registrant Date of Birth • Registrant Jurisdiction of Birth • Either Date Filed or File Number • Optional Fields • Date Filed if File Number required • File Number if Date Field required

  7. Birth Certification • Required Fields • Registrant First Name • Registrant Middle Name • Registrant Last Name • Registrant Date of Birth • Registrant Gender • Registrant Jurisdiction of Birth • Mother’s Maiden Surname • Optional Fields • Father’s Surname

  8. Query Logic • EVVE queries for an exact match • If no exact match then EVVE executes alternate queries • Soundex searches • Last Name replacements • Remove Day • Adjust Year • Switch Gender • Switch Month/Day • Remove fields

  9. Query Response • Query Return Code • If return code indicates a match and data available • File Number • Data Modified Indicator • Deceased Indicator

  10. Query Return Codes • Match • Indication of birth record marked deceased • No-Match on one required field • Problem with First Name • Problem with Last Name • Problem with Date of Birth • Problem with Date Filed • Problem with File Number • Problem with Mother’s Maiden Surname • Problem with Gender • No-Match on more than one required field • Other (time out, no data for that year, etc.)

  11. EVVE Birth Verification Process – DMV Office AAMVA GATEWAY EVVE HUB 3. BC Verification Request 8. BC Verification Response • 2. At DMV office clerk processes application • Clerk enters DL/ID info • Clerk enters data from Birth Certificate 4. BC Verification Request 1. Driver License Applicant with a Birth Certificate 7. EVVE verification response (match or no-match) VR WEB SERVER EVVE-SI Module Log File 6. SQL results 5. SQL query statements VR EVVE Data Base Vital Records Agency No-Match Analysis

  12. EVVE Birth Certification Process – Medicaid Office EVVE-ui EVVE HUB 3. BC Certification Request 8. BC CertificationResponse 4. BC CertificationRequest 2. At Medicaid office, clerk uses the EVVE-ui module to enter birth information provided by the applicant 1. Medicaid Applicant without a Birth Certificate 7. EVVE Certificationresponse (match or no-match) VR WEB SERVER EVVE-SI Module Log File 6. SQL results 5. SQL query statements VR EVVE Data Base Vital Records Agency No-Match Analysis

  13. EVVE Pilot with SSA • SSA • Birth/Death Verifications/Certifications • August 2002 – December 2003 • Participating Vital Records Offices • California, Colorado, Hawaii, Iowa, Minnesota, Mississippi, Missouri, Oklahoma • SSA Local Offices in 26 states

  14. EVVE Pilot with AAMVA/DMVs • AAMVA • Birth Verifications • May 2004 – ongoing • Vital Records Offices • Iowa, Minnesota, Missouri, Montana, North Dakota, South Dakota • DMV Offices • Iowa, South Dakota, North Dakota

  15. AAMVA EVVE Pilot Observations • Birth Verification match rates on average(03/01/06 – 03/31/07) • Iowa: 84% match rate • Minnesota: 91% match rate • Missouri: 72% match rate • Montana 86% match rate • North Dakota: 91% match rate • South Dakota: 94% match rate • Response times • Range from 3.3 to 8.3 seconds

  16. EVVE Pilot with Medicaid • Medicaid Offices • Birth Certifications • February 2007 – ongoing • Vital Records Offices • Iowa, Missouri, Montana, North Dakota, South Dakota • Medicaid Offices • South Dakota

  17. Medicaid EVVE Pilot Observations • Birth Certification match rates on average(02/01/07 – 04/30/07) • Iowa: 30% match rate • Missouri: 81% match rate • Montana 50% match rate • North Dakota: 78% match rate • South Dakota: 50% match rate • Response times • Average 3 to 5 seconds

  18. No Match Analysis • NAPHSIS works with the vital records offices on no-matches • Vital records offices work with their sister-agency offices on no-matches • Data quality problems with birth records • Date Filed field • Missing on IA pre-1965 records • Generational ID part of Last Name field • Name parsing errors • Data entry errors by DMV users • Incorrectly provided information entered by Medicaid users • Identify training improvements • Identify query algorithm improvements for the EVVE system

  19. NAPHSIS Involvement with EVVE • Established relationships with all vital records jurisdiction data sources • Single point of contact • Standard-setting mechanisms in place to provide commonality across unique jurisdiction characteristics • Clear recognition of the various jurisdiction laws governing vital records access and use of these records

  20. Implementing EVVE • NAPHSIS will establish a roll-out plan • NAPHSIS will develop MOUs • User agencies • Incorporate EVVE into their business processes • Develop user interface to enter query data and display query response or use the EVVE-ui application • Train users

  21. Implementing EVVE – Activities at the Vital Records Offices • Participate in conference call for EVVE project • Establish an EVVE database • NAPHSIS/EVVE vendor install EVVE-SI module on web server at the jurisdiction • Purchase web server if necessary • Determine connection method between EVVE hub and EVVE-SI module • SSL with authentication – purchase digital certificate • VPN – purchase VPN hardware • Identify IT support • To-date has ranged from 48 to 229 hours • Mainframe vs. relational database • VPN connection versus SSL with authentication • Identify vital records staff support for no match analysis and data quality evaluation

  22. Vital Record Offices – Data Preparation for EVVE • Need to automate birth records back to 1935 • Establish a central database • 85% of birth records back to 1935 in electronic format • Perform data cleanup and quality improvements to legacy birth records • Standardize birth records in EVVE-compliant format • Match birth and death records to mark deceased • Within the jurisdiction and between jurisdictions

  23. AAMVA APHSA CMS DHS DoS DOT/NHTSA NAPHSIS NCHS OPM SSA EVVE Advisory Committee

  24. EVVE Advisory Committee • Ensure NAPHSIS, the jurisdictions, and users are working in concert together to rollout a nationwide EVVE system • Identified additional EVVE functional requirements • Developed a proposed nationwide pricing model

  25. Conclusion • Legislation promotes the EVVE concept • Intelligence Reform and Terrorism Prevention Act • Real ID Act • NAPHSIS and its membership want to see EVVE become a nationwide system • Federal agencies • Sister agencies • Making EVVE successful requires cooperation and partnership-building relationships • Between NAPHSIS and agencies • Between each jurisdiction vital records office and their respective agencies

  26. Contact Information Rose Trasatti EVVE Project Manager NAPHSIS Headquarters (301) 563-6007 rtrasatti@naphsis.org www.naphsis.org

More Related