1. VIEWS II: Motivation and Plans for a Revised Validation Service
VSCP Project Directors Monthly Conference Call
November 12, 2014
National Center for Health Statistics
Place Descriptor Here

2. VIEWS II: Motivation and Plans for a Revised Validation Service
Introduction
Review of the VIEWS I Application
Motivation for a new version
Results of the VIEWS II Working Group Meeting
Implementation Plans & Rollout Schedule
EDRS Expectations in Using VIEWS
Conclusion and Discussion

3. Validation and Interactive Edits Web Service
What is views
Validation and Interactive Edits Web Service
An application running on a web connected computer that allows Electronic Death Registration Systems to validate the entered cause-of-death in real time.

4. What problems motivated VIEWS’ creation?
Unacceptable levels of inaccurate or insufficient cause-of-death information
High percentage of mortality records not coded electronically by the DVS automated coding system
Rejected records require manual intervention and possible query back to jurisdiction delaying the coding process.
About, 350K (out of 2.5M) records annually are rejected
32% of these are due to spelling or unrecognized terms

5. Types of Validations That Are Available
Uncommon Words
Spell Checker
Data Validations (Date Formats, Line Lengths,…)
Ambiguous Abbreviations
Rare Causes
Causes of Public Health Surveillance Interest
Cause of Death Agreement with Age and/or Sex
Trivial or Ill-defined Causes

6. Jurisdictions Have the Option to Control What Types of Validations That Are Executed
EDRS configuration panel used at NCHS to test various VIEWS validations.
In this example, Abbreviations, Spelling, and Rare Cause are to be validated.

7. Example Cause Items to be Validated

8. The EDRS Applications Should be Configured to Indicate and Describe Identified Problems

9. Messages Returned by VIEWS

10. Issues Identified with the VIEWS Implementation
Errors were Identified in the medical dictionary
Inability of jurisdictions to configure messages and other responses
Inadequate quality testing of VIEWS I
Lack of proper documentation
Poor communications between NCHS and jurisdictions and vendors
Rules and dictionaries were hardcoded into application

11. the views ii working group Recommendations
Develop a web enabled application accessible to authorized jurisdiction staff
Allows jurisdiction specific configuration changes
Changes will be immediately in the VIEWS service Test server
Jurisdiction will be required to validate additions and changes
Test changes against the Service test server
Changes must be confirmed in the Configuration module before they will be promoted to Production

12. Recommendations (Continued)
Develop unique message reference codes
Include in returned validation messages
Allows jurisdictions to customize message wording
Simplify jurisdiction specific notification s
Surveillance conditions
Rare causes

13. Recommendations (Continued)
General notification distribution list
Editable by each jurisdiction
VIEWS service status:
SERVICE DOWN / UP
SERVICE OFFLINE
Notices announcing new updates ready
For testing
In production

14. Implementation Plans & Rollout Schedule
Application Development
Currently in Progress
User Acceptance Testing (UAT)
Begins Mid Jan, 2015
Secure Authority to Operate (ATO) & National Rollout
End of March, 2015

15. EDRS Expectations in Using VIEWS
Send and receive validation request messages
Present validation responses to user
Identify offending field
For responses that provide replacement values, provide feature that allows user to select and replace offending text
Includes Abbreviations, Misspellings and Rare words
Resubmit for validation after user changes
Record whether certificate has been validated and final status
VIEWS / Electronic Death Record System – Expectations in using VIEWS II Requirements Document

16. Questions Will VIEWS II be backwards compatible?
Will EDRS applications be required to use the VIEWS service?
Can we be part of the evaluation team?

17. Conclusion and Discussion
Contacts:
David Johnson – –
Rajesh Virkar – –