Using EVVE to Support Fact-of

Report
Dialogue with Leadership
EVVE, Fact-of-Death, and the DMF
Rose Trasatti Heim
NAPHSIS Project Manager
June 5, 2013 Phoenix, Arizona
Background
•
Value of Public DMF impacted due to decline in coverage of death records
•
Jurisdictions have current/complete set of their death records
•
NAPHSIS/Jurisdictions contacted by Public DMF users
•
NAPHSIS convened a Fact-of-Death (FOD) Working Group
•
NAPHSIS adopted a policy to allow use of EVVE for death queries for
administrative purposes, including to non-governmental entities
•
Recommend use of EVVE as FOD query solution
•
Protects confidentiality of the jurisdiction’s death data
•
Promotes a query approach vs. sharing/distributing death files
•
Developed EVVE Business Model and Marketing Plan
•
Merged the FOD WG into the EVVE Committee
Business Model/Marketing Plan Recommendations
•
•
Leverage Insurance Settlement Momentum
•
Need to more rigorously identify owners of unclaimed assets
•
Contact ACLI – American Council of Life Insurers
•
Determine business needs/requirements of Insurance Industry
Explore partnership with a corporation
•
•
NAPHSIS to identify expectations of partnership, working relationship
Develop an EVVE FOD pricing model
•
Customers will have regularly recurring transaction volume with low match
rate
EVVE FOD Customers
•
Life Insurance Agencies
•
•
Unclaimed Property Settlement Compliance
Financial Institutions
•
Unclaimed Property Settlement Compliance, Credit Bureaus
•
Pension Management Companies
•
Federal/State/Local Governments
•
Department of State, Treasury Department, Secretary of State/voter registration
•
Law Enforcement/Courts – purge warrant list
•
Direct Mailing Marketing Groups – purge mailing lists
•
Medical Researchers/Hospitals/Oncology Programs – track former
patients/study subjects
EVVE Vital Records Implementation
Alaska
Death Queries
May 2013
1890
Washington
Montana
North Dakota
2000
VT
Minnesota
2006
New York City
Wisconsin
Wyoming
South Dakota
Michigan
Nebraska
1935
2000
NJ
2000
Indiana
Ohio
1959
1954
Illinois
DE
1980
WV
Kansas
1905
Virginia
Missouri
Arizona
DC
N. Carolina
Tennessee
New Mexico
Oklahoma
1947
S. Carolina
2000
2005
1959
Texas
2004
2001
1951
Arkansas
MS
Guam
MD
Kentucky
2000
2000
Northern Mariana
Islands
CT
Pennsylvania
Colorado
California
RI
Iowa
Utah
2000
MA
New York
1960
1979
Nevada
Maine
1997
Oregon
Idaho
NH
Georgia
Alabama 1964
2000
LA
Florida
2005
Hawaii
1896
American Samoa
On-line with EVVE for death queries (27)
The year referenced indicates death data availability for EVVE verifications
On-line with EVVE but for birth queries only
U.S. Virgin Islands
Puerto Rico
EVVE Death Data Fields
•
•
•
•
•
•
•
•
Name – First and Last (required), Middle and Suffix (optional)
Gender – required
Date of Birth – required
Date of Death – required
Father’s Last Name – optional
File Date and/or File Number (one of these fields is required)
Social Security Number – required
•
Either 9 digits or 9 digits with hyphens
•
Maybe variety for unknown and none – all 0’s or all 9’s
Place of Birth (State 2 character FIPS code) – required
•
Two character state FIPS code if born in the U.S. or Canada.
•
Outside the U.S./Canada use ZZ, Unknown, use XX
EVVE FOD Queries
•
Requester does not know if the person of interest is deceased, and if so
where and when they died
•
Utilize the EVVE Broadcast Query feature
•
Jurisdictions control query access to their death data
•
Broadcast Query sent to all participating jurisdictions
•
Can be a ‘batch’ of broadcast queries or a ‘single’ broadcast query
•
Pricing will be different from verification/certification queries
•
NAPHSIS needs to develop pricing structure
•
Propose using NTIS pricing concept as a starting point – Each customer
has Annual Subscription fee for queries
DOS Death Match Pilot
• Proof-of-concept for death broadcast queries and death matching
• Five participating jurisdictions
• Jurisdictions adding SSN and POB fields
• NAPHSIS implementing enhancement to incorporate SSN/POB
•
Once complete, EVVE-SI module needs to be upgraded
• DOS will pull queries for each jurisdiction
•
Include a mix of known deaths as well as persons still alive
• Queries will be run through EVVE in broadcast mode
• Actual query results will be compared to expected results for
evaluation
Proposed EVVE Broadcast Death Query Logic
• Requester is required to provide FN, LN, DOB, Gender
• Highly recommended that they provide POB and/or SSN
• Requester may not have POB and SSN fields so they are
considered optional fields – if entered they will be used to match
• Broadcast results will identify each jurisdiction queried and the
results
•
If SSN was used in the query and they get a match on all fields they can
have confidence in the match
•
If SSN was not used, confidence in a match will be lower and they should
follow up to make sure the match was on their person of interest
•
Match can return place of death and date of death
EVVE Enhancements Needed to support FOD Queries
•
•
Add SSN and POB fields to death query logic
Incorporate lessons learned from DOS death match pilot
•
•
•
•
Does current broadcast query submission and response logic need to
be streamlined for high volume?
Will we need fuzzy matching logic, or can we retain exact match
concept?
Incorporate broadcast pricing model
In discussions with current DMF customers to understand business
needs
•
TBD enhancements as a result of discussions
Steps Needed
•
Jurisdictions need to be online with EVVE for Death Queries
•
Jurisdiction laws/statutes support administrative use of EVVE for FOD
Queries
•
NAPHSIS needs to establish FOD query pricing model
•
Identify and implement system enhancements needed to support high
volume FOD queries
•
Explore any potential legal issues, disclaimers needed
•
Develop standard contracts for EVVE FOD customers
•
Modify MOAs with jurisdictions
•
Streamline the onboarding of new customers
•
Marketing and outreach to FOD query customers
Contact Information
Rose Trasatti Heim
NAPHSIS Project Manager
301-563-6001
[email protected]
www.naphsis.org

similar documents