Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Just-released news from the Washington Post about the Department of Veterans Affairs violating federal contracting rules to pay for medical care and supplies was only the latest acknowledgement of fraud, waste and abuse in government. Why is this occurring, and what can we do to stop it?
In this case, and many others like it, the purchasing rules are documented but not followed. Why? Surely there are some cases of fraud—purchasers knowingly violating the rules. I suspect—some might say naively—that this is a small part of the problem. But it’s more likely that the rules are too complex or tedious to follow, as the Post article suggests.
Fortunately, there is a solution that addresses both problems: automate the enforcement rules using a Business Rules Management System (BRMS). A BRMS can be bolted onto purchasing systems and enforce business rules across every purchase transaction. Simply put, a purchase will not go through that does not adhere to the rules.
Why is this not happening today? Most organizations attempt to automate their business rules by programming them into the application code of their systems. But this approach takes far too long to implement and modify business rules. In the case of purchasing rules, where there are hundreds of thousands of items to purchase, with both pricing and new items updated daily, it’s not possible to keep up with the rate of change. Changes to code take weeks or months using traditional programming techniques.
But rapid change is where a BRMS shines. Changes to rules in a BRMS take minutes or hours to implement, and can be made by subject matter experts without requiring changes to code. Only this way can we keep up with the pace of changing rules.
BRMS are being adopted at an increasing pace by government. In order to comply with the Affordable Care Act, most states have adopted a BRMS as a part of their benefits eligibility and health insurance exchange systems. In an honorable display of wisdom, the Center for Medicaid and Medicare (CMS) actually required the use of a BRMS, in order to gain access to enhanced federal funding to support these new systems. Let’s apply this lesson to other areas of government, and reign in fraud, waste and abuse.
Dr. Mark Allen is a Progress General Manager, dedicated to advancing business automation and passionate about applying technology to improve the world. In 2000, he founded Corticon, later acquired by Progress in 2011. Under his leadership, Corticon became a leading independent business rules platform with hundreds of customers in diverse industries such as financial services, government, healthcare and insurance. Prior to founding Corticon, Dr. Allen developed rules-based systems to help physicians make better patient care decisions. Dr. Allen has a B.S. in Applied Physics from Columbia University, and an M.D. from the University of California Los Angeles.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.