IRS watchdog, CTO at odds over testing ACA-linked systems
- By Adam Mazmanian
- Sep 08, 2015
The IRS oversees about $2 billion of IT systems connected with the Affordable Care Act, including data systems used to confirm enrollment in health insurance for tax purposes and to determine eligibility for premium subsidies, which are paid directly to insurance carriers but tabbed as advance tax credits connected with individuals and families receiving coverage.
According to a report from the Treasury Inspector General for Tax Administration, ACA connected systems at the IRS, in particular the Coverage Data Repository, which serves as the authoritative source of enrollment data for the IRS, need to be tested on an interagency basis with the federal and state exchanges where coverage is purchased.
The TIGTA audit report, dated June 2, 2015, and released Sept. 8, determined that IRS was increasing risks to systems development, management controls and security by not completing testing of new systems releases internally, before moving on to interagency testing. The audit report also found that planned interagency testing with federal and state exchanges was not completed before the start of the 2015 tax filing season.
"It is imperative that the IRS ensures that all its information technology projects, including those associated with the implementation of the [ACA], are capable of performing the tasks they are designed to perform," J. Russell George, Treasury Inspector General for Tax Administration, said in a statement.
IRS CTO Terrence Mulholland pushed back against two key TIGTA recommendations in the report. In comments dated April 14, 2015, he said that the CDR system is tested in conjunction with the Data Hub, an ACA system that pings various government databases with queries to determine eligibility for coverage under the health care law.
The CDR, Mulholland wrote, is tested to see if it receives data from the Data Hub and replies appropriately, but direct testing between CDR and federal or state exchanges is not necessary because those systems do not directly connect. Mulholland also said that the IRS, which uses agile methodology in systems development, reserves the right to decide whether release-level testing of IRS systems and interoperability tests should be conducted in sequence, or overlap.
"Without this flexibility, development, test, and deployment efforts would have been severely hampered," Mulholland wrote.
Adam Mazmanian is executive editor of FCW.
Before joining the editing team, Mazmanian was an FCW staff writer covering Congress, government-wide technology policy and the Department of Veterans Affairs. Prior to joining FCW, Mazmanian was technology correspondent for National Journal and served in a variety of editorial roles at B2B news service SmartBrief. Mazmanian has contributed reviews and articles to the Washington Post, the Washington City Paper, Newsday, New York Press, Architect Magazine and other publications.
Click here for previous articles by Mazmanian. Connect with him on Twitter at @thisismaz.