Presentation Transcript

1. EVIDENCE BASED PROGRAM INTEGRITY
2. WHO ARE WE?
3. WHAT WE DO MyDHR RISE CAPS Builder Online Citizen Access Portal for Alabama Food Assistance Program Case management system for the Alabama Office of Radiation Control Custom business rules engine and workflow builder and manager
4. A FEW OF OUR CLIENTS
5. WHAT’S THE PROBLEM?
6. TRACK RECORD OF INTEGRITY 20% 96% payment errors are actually due to underpayment. accuracy rate in benefit payments. Considerably higher than most major benefit programs. 96% 4%
7. WHAT’S THE PROBLEM? SAVINGS OVERPAYMENT $117 MILLION / MONTH IN OVERPAYMENT OF BENEFITS IN THE US POTENTIAL SAVINGS OF $1.4 BILLION / YEAR NATIONWIDE MEALS MEALS ENOUGH TO FEED 135,252 FAMILIES OF 4 FOR AN ENTIRE MONTH ENOUGH TO PROVIDE 592 MILLION MEALS
8. WHAT DOES IT LOOK LIKE?
9. 01. DIVERSITY OF DATA Don’t rely on a single source of data Ensure data is easy to add New data can be added to the system through a powerful user interface. This creates a system that prevents stagnation through frequent updates. This system pulls data from multiple sources such as the US Census and state FNS records.
10. US CENSUS ALDHR FNS MANY MORE
11. 02. EMPOWER, DON’T REPLACE Value the experience of your users Capture user feedback to improve prediction As users interact with the system, capture their input and use it to improve analysis over time. The system should display data in a way that allows users to “follow their hunches”. The system should support, not replace the user.
12. 03. BE FLEXIBLE The world changes at a rapid pace Embrace the diversity of your users The system should provide tools to implement changes in an efficient manner. The more high-level the interface the better, you should limit the involvement of “super hero programmers” when possible. People interact with the world in many ways. Don’t force a user to use your system through a single view. Instead, allow many different means of exploring the system.
13. 04. PROVIDE GUIDANCE Don’t assume users are data scientists Guide users to making good decisions on how they visualize and interact with the data. Just because they can do it, doesn’t mean they should.
14. 05. BE APPROACHABLE Use concepts familiar to users Spend significant effort on user experience Use interface design elements, terminology and functionality that is familiar to the end users. Avoid complex jargon when designing the system. The most accurate predictive system in the world is useless unless people use it. Special effort should be spent on improving the “everyday” user’s experience.
15. 06. ANOMALY OVER FRAUD Fraud implies negative intent Identify and communicate subtle differences While it is imperative that data is monitored for invalid and fraudulent activity, looking for what is different versus what is bad allows the system to identify issues that can provide value in improving society. As transactions and data change based on a variety of factors, ensure system users are alerted in a timely manner. ANOMALY CAUSED BY OIL SPILL
16. Keep the “human in the loop” Look for anomalies, not fraud” Make it flexible,approachable and sustainable Combine analysis with prevention
17. caps.ua.edu 205-348-6835 csims@cs.ua.edu @UACAPS UACAPS