Promising Practices Promising PracticesPromising Practices
A forum for government's best ideas and most innovative leaders.

Can Protected Data Be Shared to Improve Services?

ARCHIVES
Mmaxer/Shutterstock.com

“Start with what you have,” is the advice consultants recommend to organizations that are just launching performance measurement initiatives. Now the Office of Management and Budget has issued guidance encouraging agencies to use existing program data in new ways.

The Obama administration has championed open data by encouraging agencies to make a wider range of statistical information available to the public. The philosophy is “information is a valuable national resource and strategic asset.” To that end, OMB has issued directives and created Data.gov, a centralized website for public data.

But what about administrative data that cannot be publicly shared because of privacy or security reasons? Agencies collect and use administrative data for the basic operations of government programs. For good reason, government records of individuals’ tax, Social Security earnings, health insurance and other benefit information cannot and should not be shared publicly. In fact, there are strict laws in place to safeguard these kinds of data.

Sharing Non-Public Data

Can protected data at least be shared between federal agencies -- if stripped of individual identifiers -- so they can be used to improve services? So far, this has been difficult. Each agency has been left to interpret whether it can share its data, and under what circumstances.

Laws allow certain kinds of sharing, but in many cases, constraints -- real or perceived -- have meant that one agency has to survey individuals or businesses for information that has already been collected by another agency. This has resulted in costly and duplicative efforts for government, businesses and citizens.

During the past five years, OMB has advocated sharing statistical information among agencies for evidence-based analyses that support better program decisions -- without new and costly data collection efforts. The Housing and Urban Development, for example, has worked with the Veterans Affairs Department to share data about homeless veterans to better target services. This joint effort has reduced veteran homelessness by 25 percent since 2010.

OMB’s New Guidance

Last week, OMB quietly released a significant piece of guidance that provides agencies the following practical advice on how to share non-public administrative data in responsible ways that protect confidentiality:

  • Foster collaboration across program and statistical agencies. An earlier OMB memo required agencies to develop an inventory of data sets they collect and maintain. Agency leaders should “communicate the importance of identifying those administrative data sets with great potential for statistical use” and highlight their existence to relevant statistical agencies.
  • Adhere to data stewardship practices that safeguard data. OMB outlines a set of principles that allow agencies “to maintain public trust in their ability to appropriately handle identifiable information.” Examples include certifying procedural safeguards and eliminating identifiable information when the data are no longer needed.
  • Documenting quality control measures for statistical agencies. The directive says “program agencies should provide the technical documentation or other assistance that statistical agencies or components require to adequately assess the quality of a particular data set.” Sometimes, OMB notes, program agencies might be able to make their data more useful by making changes to how they collect or report it.
  • Foster clearly written interagency agreements for data sharing. Agencies should employ interagency agreements to the document terms and conditions for when and how non-public data should be shared. OMB’s guidance includes a helpful checklist of what should be included in such an agreement, but also encourages agencies to “seek the advice of their counsel before signing.”

Next Steps

No OMB memo would be complete without a requirement for agencies to report on their progress. Agencies must report to OMB no later than June 30 on what processes they have put in place to implement the guidance. The directive provides a helpful outline of what that report should contain:

  • A copy of whatever communication the department head sent out to staff to tell them this is important stuff.
  • List at least three data sets identified as having the “highest potential statistical value” -- including data sets at other agencies -- and the status of any requests to use the data.
  • Identify any barriers to sharing data with other agencies for statistical purposes.

So, if another agency has data that would be useful to your meeting your mission, you now have the permission slip to ask for it -- for statistical purposes, that is.

(Image via Mmaxer/Shutterstock.com)

John M. Kamensky is a Senior Research Fellow for the IBM Center for the Business of Government. He previously served as deputy director of Vice President Gore's National Partnership for Reinventing Government, a special assistant at the Office of Management and Budget, and as an assistant director at the Government Accountability Office. He is a fellow of the National Academy of Public Administration and received a Masters in Public Affairs from the Lyndon B. Johnson School of Public Affairs at the University of Texas at Austin.

FROM OUR SPONSORS
JOIN THE DISCUSSION
Close [ x ] More from GovExec
 
 

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download
  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

    Download
  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

    Download
  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

    Download
  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

    Download
  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

    Download

When you download a report, your information may be shared with the underwriters of that document.