GDS Data Architecture
Data Sharing Principles
- Overview
- 1. Treat data as an asset
- 2. Federate first
- 3. Prepare for Once Only
- 4. Reuse sharing solutions
- 5. Support automation
- 6. Design for all data stakeholders
- 7. Use common standards for sharing
- 8. Share data transparently
- 9. Share data lawfully and ethically
- 10. Secure shared data proportionately
Capability Model
3. Prepare for Once Only
Statement
We minimise the number of times that users are required to give the same data to different parts of the public sector, aiming to achieve “Once Only” over time.
Why does this matter?
The Blueprint for Modern Digital Government lists establishing a “Once Only” rule as a priority reform. The rule states that if citizens have provided information to one service, it can be reused by others with appropriate safeguards.
The Once Only rule is underpinned by a federated approach to real-time data sharing across the public sector. Successfully applied, Once Only will reduce the “time tax” on citizens reporting changes to their circumstance across multiple public services and reduce the potential for administrative error and confusion. In addition, the rights of data subjects are easier to protect where only a single version of a dataset exists in a data ecosystem, as responding to requests for subject access or change is easier with fewer copies to maintain.
More broadly, commitment to the Once Only rule signals a perception shift about the future of public service delivery and aligns with the vision of a modern digital government where departments deliver collectively to save people time and stress.
How do we do this?
Relevant work in progress:
- Data Sharing Sandbox
- Data Access Patterns
Overall, we should contribute to the Once Only programme and prepare to adopt Once Only solutions as they emerge.