Growing Convenet’s NHS-approved API into a robust health data ecosystem in the UK
Convenet founders Andrew Bailey and Chris Turner met at Keele University where they were brought together on a project as “forced friends.” Years later, working on different sides of the UK healthcare system, they both became frustrated by the lack of interoperability slowing down patient record retrieval and prescription management. Together they founded Dimec, a prescriptions app that integrated with GP and Pharmacy systems in the UK before founding Convenet, an NHS Spine-integrated API. We spoke with Andrew, Chris, and Grant Murphy-Herndon, Head of UK Business Operations, about Convenet and some of the challenges involved in bringing Datavant technology to the UK. Interested in joining their team? Datavant is hiring across roles in the UK.
Datavant acquired Convenet in 2022. What does Convenet do?
Convenet is a single API running on RESTful JSON that connects to 100% of England’s General Practitioner (GP) systems and the UK National Health System (NHS) Spine. We also enable connections to dozens of 3rd-party services, including pharmacies, care homes, and remote medical consultation services. In other words, we have an extremely robust service providing identified, consented patient record retrieval.
This is very similar to Datavant’s Identified Switchboard. Tell us about the structure of the UK healthcare system and how it is you’re able to connect to 100% of UK GPs.
Interoperability is challenging in both countries, but in that regard, the UK benefits from a nationalized effort by the NHS to digitize patient records. All patients in England and Wales are listed in the NHS Spine, a central database of patients and patient demographics: first and last name, DOB, postal code, address, NHS Number (a 10-digit number like a US Social Security Number), registered GP, and chosen pharmacy. Also, there are only 3 Electronic Health Record (EHR) systems in the UK: EMIS Health, SystmOne, and Cegedem, which manages INPS Vision. Compare that to the US, where the average health system deals with 18 different EMR providers.
Convenet integrates with all four entities, connecting GPs to the 3 EMR providers and the Spine. So in the US, if Datavant knows the patient and knows the provider, then the patient’s health record can be located and transmitted to another provider, which is to say, a scenario involving a known patient and known provider. But because of our integration with the NHS Spine, Convenet has the power to connect any patient to any provider even if we don’t know where that patient received treatment, a scenario involving a known patient and unknown provider — a very powerful feature of the API.
We’re using the Convenet infrastructure as a starting point to rebuild Datavant’s entire US infrastructure in the UK.
You’re in the process of a major build-out of your platform and hiring a significant cohort of UK-based engineers for this. Now that Convenet is part of Datavant, why can’t Convenet simply unroll Datavant’s Switchboard in the UK?
At a high level, this comes down to the differences between HIPAA privacy rules and GDPR (General Data Protection Regulations) privacy rules. HIPAA is vague by design. GDPR, which covers the EU as well as 14 other territories, is strict but clear. Building according to GDPR rules is in some ways more straightforward but doesn’t allow for a simple redeployment of the Switchboard.
As an example, consider the concept of de-identified data. HIPAA has a category of data that qualifies as “de-identified” by way of either its Safe Harbor guidelines or its Expert Determination guidelines, which also include provisions for re-identification. This is the environment for which Datavant’s tokenization has been designed. GDPR does not include the concept of “de-identified” data. Under GDPR, data can be “anonymized” or “pseudo-anonymized.” If it is anonymized, then it is truly anonymized and there is no way to link the data back to an individual. Under this condition, tokenized data is a very vigorous form of “pseudo-anonymous data,” but does not count as anonymized precisely because one token still does refer to one patient.
What are some implications of the distinction between “de-identified” and “pseudo-anonymous”?
If we want to tokenize patient data for pseudo-anonymous use cases under GDPR, we can only do so with patient consent. HIPAA demands patient consent for transfer of identified data, but not for de-identified data. Personal data can move around within the GDPR member countries, but no UK patient data can hit American servers. We don’t even want patients with UK-based email addresses interacting with the US portal.
Further, GDPR is a set of guidelines for all types of personal data and addresses the right to be forgotten, or right to erasure. For example, if you “delete” your Instagram account (in a non-GDPR market such as the US), and then go back to it a year later and sign in with the same credentials, you’ll find that your data is still there: the account was inactive but not actually “deleted.” As we are rebuilding the Datavant infrastructure in the UK, we must also build a mechanism that allows patients to be absolutely forgotten. From an engineering standpoint, this means maintaining a log to prove that an individual who has requested to be forgotten has actually been deleted throughout our system, and building a mechanism to deliver the evidence of deletion to a user after they have been deleted.
Finally, there is the issue of data provenance. If a patient does consent to have their data tokenized as part of a clinical trial, Datavant must be able to tell that person what we know about them. We must be able to say “Andrew is X specific token and he was located in Y datasets, which were linked on Z occasions.” We must always know exactly where all data is coming from and be able to reconcile all patients back to any tokens that were used to de-identify them.
Essentially, you could say that we’re using the Convenet infrastructure as a starting point to rebuild Datavant’s entire US infrastructure in the UK.
Our goal is not to lock down data, but to facilitate its flow in a safe, privacy-preserving, compliant manner.
What are some of the next steps for “Datavant-UK”?
There are a few major goals. We need to build an encryption platform in the UK that deals with patient data in a GDPR compliant manner. Also, we have a single API with all of the necessary connections, but we need to build the end-to-end interface and user experience for the API.
A longer range goal is to get GDPR-compliant tokenized data running in the UK so that we can integrate RWD with clinical research and trials, as is happening already in the US. And along those lines, we’re building a “Get My Health Records” button so that any user can pull their entire set of digital health records regardless of where they are stored. If Datavant has the power to find those records, we should be able to return them to patients. Our goal is not to lock down data, but to facilitate its flow in a safe, privacy-preserving, compliant manner.
More generally, our commitment to being an infrastructure layer means that we are growing partnerships across the ecosystem. We are innovating new products while also connecting to legacy products. We’re working from a standpoint of looking for problems within the system that need solving and trying to reverse engineer solutions. As Convenet and Datavant grow, our infrastructure will allow for the growth of companies that do not yet exist, conducting business that was not previously possible. Because we are an even smaller and more nimble wing of Datavant, we aim to be a spotlight of innovation. We hope to use the work done in the UK as an exemplar of how this work can be done.
Many thanks to Andrew, Chris, and Grant for the interview.
Andrew Bailey and Chris Turner have backgrounds in Pharmacy, and previously co-founded Dimec, a prescriptions app that integrated with GP and Pharmacy systems in the UK. Together they founded Convenet.
Andrew Bailey is currently Head of UK Engineering. Connect with Andrew via Linkedin.
Chris Turner is currently Head of UK Product. Connect with Chris via Linkedin.
Grant Murphy-Herndon has a background in economics and strategy and is currently Head of UK BizOps. Connect with Grant via Linkedin.
Interview compiled/edited by Nicholas DeMaison.
Considering joining the Datavant team? We’re hiring remotely across teams and at a variety of levels (junior / mid / senior) in the UK. We would love to speak with any potential new Datvanters who are nice, smart, and get things done, and want to build the future tools for securely connecting health data and improving patient outcomes.
.svg)
