Archiving a Project Dataset
PURPOSE
This SOP describes how Project Datasets are archived at the end of a project when the data is no longer required for the purposes of the project, but may be required for future research use, review, reference or audit.Â
RESPONSIBILITIES
ROLE | RESPONSIBILITY |
HIC Client |
|
Leadership Team |
|
SCOPE
This SOP covers Approved Projects. This data includes, but is not limited to:Â
Pseudonymised (e.g., PROCHI’d) data released to the TRE, including both archiving of the original copies of the files released to researcher, and researcher altered versions.Â
Code and reports developed by Approved Data Users.Â
Any other files present in the TRE.
PROCEDURE
Identify Dataset
Once the Approved Project has reached its end date, as shown within the PM System, HIC will liaise with the HIC Client to ensure that they are finished with the data.Â
If HIC Client is not finished with the data, the end date will be updated accordingly within the PM System which will extend the HIC Clients TRE account expiry.
Archive Dataset
If the HIC Client confirms that their Approved Project is completed the Project Dataset will be archived.
Deidentified project data, as released to TRE may also be archived.
Monitor Archived Dataset
Archived data is held for a period of 10 years unless otherwise specified in any agreements.
The potential use of the dataset will be reviewed by the Leadership Team after 10 years, in consultation with the original HIC Client where possible and a decision will be made to either:Â
Delete the dataset, including all back-ups, orÂ
Extend the archive periodÂ
APPLICABLE REFERENCES
For Definitions see HIC ISMS Glossary
Information Security Policy
DOCUMENT CONTROLS
Process Manager | Point of Contact |
---|---|
Chris Hall |
Revision Number | Revision Date | Revision Made | Revision By | Revision Category | Approved By | Effective Date |
---|---|---|---|---|---|---|
1.0 | 01/01/24 | Moved SOP to Confluence from SharePoint and updated into new template | Bruce Miller and Symone Sheane | Superficial | Governance Co-Ordinator: Symone Sheane | 10/01/24 |
1.1 | 04/04/24 | Updated Roles and Responsibilities | Bruce Miller | Superficial | Governance Co-Ordinator: Symone Sheane | 5/04/24 |
1.2 | 10/04/24 |
| Symone Sheane | Superficial | Governance Co-Ordinator: Symone Sheane | 10/04/24 |
1.3 | 19/04/24 |
| Symone Sheane | Superficial | Governance Co-Ordinator: Symone Sheane | 19/04/24 |
1.4 | 30/04/24 |
| Bruce Miller | Superficial | Governance Co-Ordinator: Symone | 30/04/24 |
1.5 | 02/05/24 |
| Bruce Miller | Superficial | Governance Co-Ordinator: Symone Sheane | 02/05/24 |
1.6 | 16/10/24 |
| Symone Sheane/Chris Hall/Jenny Johnston | Superficial | Chris Hall | 16/10/24 |
1.7 | 18/11/24 |
| Symone Sheane | Material | Leadership | 18/11/24 |
Copyright Health Informatics Centre. All rights reserved. May not be reproduced without permission.
All hard copies should be checked against the current electronic version within current versioning system
prior to use and destroyed promptly thereafter. All hard copies are considered Uncontrolled documents.