Data environment for OpenSAFELY
ID | RM201 |
|---|---|
Version | 1.0.0 |
Type | Roadmap Item |
Frameworks |
Title | Data environment for OpenSAFELY |
|---|---|
Description | GP system Supplier data environment Standard for OpenSAFELY |
Date Added | Oct 26, 2023 |
Standards and Capabilities | |
Change Route | Managed Capacity - Other |
Change Type | New |
Status | Draft |
Publication Date | TBC |
Effective Date | TBC |
Incentives / Funding | TBC |
Incentive / Funding Dates | TBC |
Background
Some Foundation Suppliers have been working with OpenSAFELY during the pandemic providing a data environment containing a full set of pseudonymised data for their respective estates. The OpenSAFELY Standard is intended to formalise provision of this environment for ongoing use.
Outline Plan
This change is initially for Foundation Suppliers who have already implemented a data environment. For other Foundation Suppliers and New Market Entrants (NMEs) the outline plan is TBC.
Summary of Change
OpenSAFELY: New Interoperability Standard added |
|---|
ID | Requirement | Level |
|---|---|---|
OS01 | Implement and maintain the latest specification version of the data environment for OpenSAFELY 
| MAY |
Patient Information Maintenance - GP: MAY Epic added |
|---|
E00623 - OpenSAFELYAs the Authority I want the Solution to provide a data environment for OpenSAFELY So that pseudonymised data can be accessed for research and analysis Acceptance criterion 1: access a data environment for OpenSAFELYGiven the Solution has provided OpenSAFELY with an environment When OpenSAFELY selects to access data within the environment Then the data in the environment is accessed E00623 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
|
Full Specification
The updated Patient Information Maintenance - GP Capability and the new OpenSAFELY Standard will be added at a later date. Proposed changes can be viewed in the Summary of Change above.
Assurance Approach
OpenSAFELY will evaluate the set-up of each Supplier environment to determine whether it meets the OpenSAFELY Standard.
The Epic will be assessed as part of the Capability Assessment phase and this will be a high level assessment based on the Acceptance Criteria defined.