Accepted for/Published in: JMIR Research Protocols
Date Submitted: Jun 28, 2024
Open Peer Review Period: Jul 17, 2024 - Sep 11, 2024
Date Accepted: Dec 19, 2024
(closed for review but you can still tweet)
Conversion of sensitive data to Observational Medical Outcomes Partnership (OMOP) Common Data Model: Protocol for the development and use of Carrot.
ABSTRACT
Background:
The use of data standards is low across the healthcare system and therefore to undertake international research it is usually required to convert data to a common data model. One such model is the Observational Medical Outcomes Partnership (OMOP) Common Data Model. It has gained significant traction across researchers and those who have developed data platforms. The Observational Healthcare Data Sciences and Informatics (OHDSI) partnership manage OMOP and provide many open-source tooling to assist those with data to convert their data to the OMOP CDM. The challenge, however, is in the skills, knowledge, know-how and capacity within teams to convert their data to OMOP. The European Health Data Evidence Network (EHDEN) provided funds to allow data owners to bring in external resource to do the required conversions and therefore creating a once in time conversion of data. The Carrot software is a new set of open-source tools designed to help address these challenges while not requiring data access by external resources.
Objective:
Data protection rules are increasing and privacy by design is a core principle under the European and UK legislations related to data protection. Our aims for the Carrot software were to have a standardised mechanism for managing the data curation process, capturing the rules used to convert the data, and creating a platform that can re-use rules across projects to drive standardisation of process, improve the speed, and without compromising on quality. Most importantly, the privacy by design approach was to deliver this approach without requiring those creating the rules to have access to any of the data.
Methods:
The software was developed utilising Agile approaches and mixing both the software engineers with data engineers who would ultimately use the system. Experts in OMOP were utilised to ensure the approaches were correct. An incremental release programme was initiated to ensure we delivered continuous progress.
Results:
Carrot has been delivered and has been used on a project called CO-CONNECT to assist in the process of allowing datasets to be discovered via a federated platform. It has been used to create over forty five thousand rules and over 5 million of patient records have been converted. This has been achieved while maintaining our principles of ensuring this can be achieved with no access to the underlying data by the team creating the rules. It has also facilitated the re-use of existing rules, with the majority of rules being re-used rather than manually curated.
Conclusions:
Carrot has demonstrated how it can be utilised alongside existing OHDSI tools with a focus on the mapping stage. In the CO-CONNECT project it successfully managed to re-use rules across datasets. The approach is valid and brought the benefits expected with future work continuing to optimise the generation of rules.
Citation
Request queued. Please wait while the file is being generated. It may take some time.
Copyright
© The authors. All rights reserved. This is a privileged document currently under peer-review/community review (or an accepted/rejected manuscript). Authors have provided JMIR Publications with an exclusive license to publish this preprint on it's website for review and ahead-of-print citation purposes only. While the final peer-reviewed paper may be licensed under a cc-by license on publication, at this stage authors and publisher expressively prohibit redistribution of this draft paper other than for review purposes.