Recorded in partnership with ViVE, this episode features Liz Ashall-Payne, founding chief executive of ORCHA, in conversation with Mindbowser CEO Ayush Jain. Liz started as a clinician in complex pediatric care, frustrated that she could see only six patients in a day, and spent years on lean methodology in the NHS before seeing health apps as a way to widen access. The obstacle, she found, was trust: by her count there are around 365,000 digital health technologies, and only about 20% of those ORCHA has assessed meet the quality criteria you’d expect.
ORCHA borrowed its model from drug distribution: evaluate, train the workforce, build digital formularies, prescribe by text message, and keep re-evaluating so faulty products can be recalled. Liz explains the four buckets every assessment framework covers, why reviews must be proportionate to risk, and how long each stage takes. For teams building health apps, her point is plain: most compliance gaps come from not knowing the rules. She closes with lessons for young health tech professionals: fall in love with the problem, not the solution.
Liz’s starting point was simple: if everyone has a smartphone and there are thousands of health apps, why can’t everyone have access to healthcare when they need it? What she saw instead was a trust problem. She says there are now about 365,000 digital health technologies, five million people download a health app every day, and only around 20% of the technologies ORCHA has assessed meet the quality criteria you’d expect. So ORCHA copied the way drugs reach patients: licensing to prove safety and effectiveness, training prescribers, a reference like the Orange Book or the British National Formulary, and a prescribing infrastructure that tracks where each product has gone. ORCHA evaluates, trains the workforce, builds bespoke digital health formularies, lets clinicians prescribe by text message, and re-evaluates continuously so a product can be recalled if a fault is found.
ORCHA horizon-scanned compliance requirements across the countries it works in and found they fall into four buckets: data security, data privacy, clinical and professional assurance, and user experience and accessibility. Because so many questions repeat, ORCHA built an international baseline that Liz says covers around 70% of any digital health assessment framework, then adds market-specific criteria such as the NHS DTAC. The review runs as a set of gateways: if a product is a medical device without the relevant certification, there’s no point asking about HIPAA or GDPR. And it has to be proportionate. A diagnostic mole tracker that shares data opens every question; a digital recipe book that holds no data needs far fewer. That’s the same logic behind FDA risk classes for mobile health apps.
Requests come from governments, health systems, suppliers, investors and accelerators, and ORCHA also runs a daily global data scrape and prioritizes the most downloaded technologies, because if people are using them, someone needs to know they’re safe. A rapid assessment of basic fundamentals takes about 30 minutes. The international baseline can take up to three hours, depending on the product’s functions and risk, with experts brought in only for their part. The DTAC layer adds another day. The back and forth with suppliers takes longest, and Liz is clear about why: gaps rarely exist because a supplier doesn’t want to comply, but because they didn’t know what the rules were.
Liz’s first lesson for people entering health tech is to get obsessed with the problem, because the solution will keep changing. When she started, AI wasn’t a thing; now it can feed into the same goal of widening access. Her other lessons: find people who are brilliant where you aren’t, treat anyone working toward the mission as a collaborator rather than a competitor, build resilience (she compares hard periods to a waterfall, turbulent but followed by calmer, deeper water), and practice gratitude. Kal Patel of BrightInsight made a related point on this show about leading with regulatory, privacy, security and quality management before talking innovation.
How are you? Welcome to the HealthTech with Purpose podcast. How are you today?
Very well, thank you. How are you?
Yes, doing great as well, and I’m really looking forward to this podcast episode, because I have been following ORCHA for some time, and you are doing some fantastic work. So I’m finally able to meet the heroes behind the whole company. Let’s get started right away.
Yes, please, that sounds great.
Good. For our viewers, why don’t you start with a bit of an introduction to ORCHA, what you do, and also a bit more about yourself? Let’s start with those questions first.
Of course. My name is Liz Ashall-Payne, and I’m the founding chief exec at ORCHA. I started my work in healthcare nearly 25 years ago, when I trained and started working in complex pediatric care as a clinician. For me, 25 years ago, my big passion was that I wanted to help people. Of course, I was really excited about my first day in clinic when I started to see patients, but at the end of that first day I felt really frustrated, because I’d only been able to see six patients, and I knew there were a lot of patients waiting for access to my knowledge, support and interventions. That started my passion and my frustration: how can we provide more access to healthcare for more people?
Now, this was before we had access to technology. I didn’t have a computer on my desk, and I certainly didn’t have a smartphone in my pocket. But I got interested in lean methodology and quality improvement, stripping out waste so that we could release time to care, and we did some really transformational things right across the NHS (National Health Service), in most types of health and care services you can imagine. But of course you can only run so fast, and that’s when you need to start looking at innovation and new ways of [inaudible].
It was around 10, maybe 12 years ago that technology really started to emerge as an enabler for us to do that. Of course, the smartphone was born, and we all started to use smartphones for lots of different parts of our lives. We also started to see the rise of digital health and health apps. Around 30,000 health apps were available to us, and I thought, very simplistically: if everybody has a smartphone and we have lots of health apps, why don’t we just put the two things together, and we can all have access to healthcare whenever we need it?
But of course it’s not that simple. Fast forward a few years, and I started to work internationally, across Europe and North America, supporting system leaders to think about how they could use digital health to improve population and patient health outcomes. What I saw were some real barriers to adoption. At this time there were about 165,000 health apps, so it had massively accelerated, and we were missing the opportunity. There were a few reasons for that missed opportunity, and the biggest was trust. People didn’t know which technologies they should trust.
Fast forward another few years to where we are now: we have access to 365,000 technologies, and ORCHA has completed nearly 25,000 assessments and evaluations of those technologies. Our research shows that only around 20% meet the quality criteria you would expect. What we also know is that every day, five million people download a health app. So for those five million people, most are finding unsafe and unregulated technologies that shouldn’t really be used, and we’ve got a massive missed opportunity.
Now, there are lots of other problems in the adoption of digital health, and I basically got obsessed with those challenges and how we could resolve them to embrace the opportunity. Where else in healthcare are we distributing interventions safely and effectively? The obvious thing to think about is drug distribution. We’ve all been prescribed a drug. But before we get prescribed that drug, it goes through a licensing process to make sure it’s safe and effective; that’s about building trust. Would-be prescribers are then trained in these drugs, and it forms part of the curriculum, so not everybody can prescribe a drug; you have to be a prescriber. Then in the USA you have the Orange Book, and here in the UK we have the British National Formulary, which is a book that tells you about the drugs and the contraindications. And then we have a prescription infrastructure that allows a doctor to prescribe a drug to a patient, and that’s about tracking where the drug has gone and following reimbursement.
That was the basis for the founding of ORCHA. What we do at ORCHA is evaluate. We then distribute that information into training and workforce development. We then create bespoke digital health formularies, so that would-be prescribers of technology can search, view and understand any risks or side effects, and then prescribe it by text message to their patient. We also don’t evaluate just once; we continuously re-evaluate, because once a technology has been prescribed, you need to know which technology has gone where, and if a fault is found in future, you need to be able to recall it. We started our work in the NHS, and I’m very proud to say we’re now working in 13 different countries across Europe, the Middle East, North America and Australasia.
Okay, okay. That’s pretty much the whole world.
Most of it, right? But we’re going to give it a go.
It definitely sounds like a big responsibility you’ve taken on. Just like the analogy you used: there’s that whole checking process for drugs, but for technology, hundreds and thousands of applications are added to the Play Store every day, and there’s a high chance that not all of them are as good as they claim and could actually be problematic for the end user. So let’s go deeper on this, especially the kinds of checks you do. What makes you approve or not approve these apps? And are there frequently found issues that have led to app failures, where you see it and you already know where it’s going?
Yeah, yeah, of course. I’m going to try to describe it at a high level, but if anybody listening is interested, we can provide volumes of data and information on this topic, so do reach out.
The first thing to say is that globally we’ve started to see the rise of digital health assessment frameworks. This is basically the coordination and compiling of regulations, compliance and best practice standards into a list of criteria, and the idea is that if you meet the criteria, that jurisdiction can trust you. It might even be state by state, as is the case in America, but all of these bodies or jurisdictions have standards and compliance requirements.
Now, because we work in lots of different countries, we’ve horizon-scanned all the compliance requirements globally, and predominantly they fall into four buckets. The first is data security, the second is data privacy, the third is clinical and professional assurance, and the fourth is user experience and accessibility. Those are the four big buckets. And globally, when you look at the requirements for digital health technologies, quite a lot of them are the same. In fact, the majority of questions people are trying to answer are the same, because there are only so many questions you can ask of a digital health technology.
So what we’ve done at ORCHA is coordinate that into an international baseline. The international baseline assessment process covers around 70% of any digital health assessment framework globally. We do the evaluation across those four areas, looking at the questions everybody wants the answer to. Of course, there are some really basic fundamentals in there. A very simple example would be: is this technology a medical device? If it is, does it have the relevant certification? If the answer is no, we need to stop the evaluation, because there’s no point going on to understand whether the technology is HIPAA (Health Insurance Portability and Accountability Act) compliant or GDPR (General Data Protection Regulation) compliant if it hasn’t got this basic, underpinning fundamental. So we take technologies through a process of gateways for compliance.
Once they’ve achieved the international baseline, we ask: which vertical, which area or market are you interested in working in? Here in the UK, the NHS has something called the DTAC (Digital Technology Assessment Criteria), which is their digital health assessment framework. So 70% is covered by the international baseline, and then there are some additional criteria very specific to the NHS, predominantly around clinical safety and data security. The technology then goes through those additional requirements and gets DTAC approved, and this is ongoing compliance.
What’s really interesting is that in those additional requirements we’re also starting to see convergence. The clinical safety element, which was born here in the UK within the NHS, has now been adopted in New Zealand, and it’s starting to be adopted in other countries. So we’re seeing more convergence at that enhanced layer.
Now, you asked what the areas are that people are missing. Of course, what we’re talking about here is health and healthcare, and we as end users, and the systems, are nervous about things like data security. What’s happening with my data? Where is it going? Where is it being held? Am I consenting to share it? All of that has to be taken into consideration. And of course, if a technology interoperates and shares data into clinical environments, that’s another set of questions we need to [inaudible].
Then within healthcare, there are lots of requirements around clinical and professional assurance. I talked about clinical safety, but further to that, clinical evidence of effectiveness is absolutely critical. A product might be safe, but is it actually going to do what it says it’s going to do?
The final thing I’d say is that not all these questions are relevant to all digital health technologies. There’s a whole spectrum of risk when we talk about digital health. At one end of the spectrum you’ll have a digital therapeutic that may diagnose you: it may be a mole tracker that scans for skin cancer. That is a highly complex, highly regulated product. At the other end of the spectrum you might have a digital recipe book, which is basically the equivalent of a book in an app. It’s low risk: it doesn’t hold data, push data or share data, and it’s not of clinical risk. So the way you assess and apply the criteria also has to be proportionate.
So how does a typical assessment work? What kind of team composition is ideal, and how long does an assessment take, if you can share more about that? Let’s start with that, and then I have a part two, if that’s all right.
Yeah, that’s absolutely fine. I talked about the gateways. The first thing is: how do we pick which technologies to assess next? We work with lots of government bodies who ask us to assess and evaluate technologies before they engage with them. We also work with a lot of different parts of the healthcare system globally, and we get asked to assess technologies to make sure they’re compliant. We also get asked by the suppliers, the digital health technology suppliers: they want to know whether their product has met the market requirements, so they’ll come to us. And we have investors come to us, and anybody who’s got an accelerator: they want to check whether they’re backing the right technologies, ones that are safe and effective.
So we have people coming to us, but we also go out to the marketplace. We do a global data scrape every single day, and through that we bring in information about the wide world of health apps, digital health and digital therapeutics. We’re looking at what’s new to the market and what’s been most downloaded, and if we have capacity to do additional assessments, we assess the most downloaded technologies. The reason for that is that if people are using them, we need to know if they’re safe. That’s the first thing to say, and it’s all very heavily data driven.
The next thing to say is that we’ve built a review engine, and that data goes into our review engine. It’s still a manual process, but we’ve built technology that enables us to assess proportionately and repeatedly. When a technology first comes in, we look at what it does, what functions and features it has, and what risk profile that means. I used two examples: for a diagnostic that interoperates its data, all the questions open up; for a digital recipe book, we’re asking a lot fewer questions. So the time is directly correlated to the risk of the product.
Then we take it through these stages. The first stage is a rapid assessment looking at basic fundamentals, and that process takes about 30 minutes. If a product hasn’t met that, we stop, contact the supplier and advise them on the gaps, and when they update and change, we proactively take it through to the next level. The next level is the international baseline, and depending on the product’s functions, features and risks, that second level can take up to three hours. We have human people reviewing technologies and still handing off to experts, but we only hand off to experts for the part they’re expert in, and they then feed that information back into the review engine.
The final section then depends on the jurisdictional requirements. The DTAC here in the UK takes us an additional day to complete. Quite often there’s some back and forth with a supplier, because quite often there will be gaps, and the reason there are gaps isn’t because anybody wants to not be compliant. It’s because they didn’t know what the rules were in the first place. So we continuously feed back a gap analysis, the supplier completes it, and on we go. So the lag time can make it a much longer process.
Mm-hmm. Okay, okay. So tell me more about your business model. For these assessments, are health organizations or hospitals your biggest customers, asking you to assess? Or are these companies building a product who come to you to get it assessed? And if it’s companies, at what stage do they usually come in: at an early stage, so they can course correct, or when they want to launch and go enterprise?
Yeah, really good question. We have three basic offers. The first is ORCHA Assure. This is when we’re testing and evaluating technologies. We have a number of partners we work with: government bodies, suppliers, healthcare systems, employers. Anybody who wants to check whether a product is safe can come to us, and we’ll engage with them. We also do quite a lot of that work in life sciences now, because big pharma is really interested in this space. So that’s the first thing, ORCHA Assure.
The second thing we do is ORCHA Activate. This is the creation of digital health libraries and formularies, and engagement with the workforce, predominantly working with healthcare providers. A healthcare provider has a population they want to distribute great technologies to, and we work with the teams, the doctors, nurses and therapists, to train them and provide them with the infrastructure to pick and prescribe the technology to that patient.
The third thing we have is ORCHA Insights. We have really unique data about the world of digital health and how it’s changing over time: which technologies are compliant, according to which areas; which technologies are being picked and prescribed; what the conversion rate is, and how that’s changing over time. Who’s interested in that? Well, for a start, we’re interested in it at ORCHA, because we use that data to feed research, since there are still a lot of questions in this space. But other people are interested in this data too. We work with regulators, for example, who want data on what’s compliant and what’s not. We also work with healthcare systems who say, “We’re interested in engaging along a cardiovascular disease pathway or a diabetes pathway. What’s out there? How is the world changing? What’s the size of the opportunity, and which technologies are doctors most engaging with?” So the Insights space is quite interesting. We’ve worked with a lot of research organizations, regulators, life sciences and big pharma, healthcare systems, and digital health suppliers, because they quite often want to know what’s different about their product and what the competitive landscape is.
Makes sense, makes sense. I’d like to change gear a bit, more toward Liz the leader. Liz, can you share with us what inspires you about being in health tech, and some of your own stories or anecdotes, whether they happened at ORCHA or in your past experiences in healthcare?
Yeah, of course. So, what inspires me. We all get asked a question when we’re about 16 or 17, and that question is: what is it you want to be? You’re normally at school, and somebody at school will say, “What job do you want to do?” It’s a really tricky question. I’ve got a 17-year-old who’s been asked that question all the time. I had no idea what job I wanted to do, but I knew fundamentally what I was interested in and what my passion was, and that’s still the same today. My passion is that I want to help people. That was naturally why I got interested in working clinically.
But of course, what I’ve seen over time is that we can help more people by doing things differently. As a clinician, I can only see one patient at a time, whereas with what we’re doing now, distributing safe technology, we can help millions of people all at the same time. So that’s my big passion.
And of course, right now healthcare systems across the world are really struggling, in crisis. We see the post-pandemic challenges around mental [inaudible]: more people are experiencing anxiety, stress and depression, waiting lists have skyrocketed, and there’s the impact on healthcare systems of people attempting suicide and self-harm. Actually, there are lots of amazing technologies we can get to people right now to help them immediately, while they’re waiting, struggling or in crisis. That’s one use case.
Another example would be people waiting for elective surgery. Those people are waiting for operations, and they might be in pain, not sleeping well, or not exercising. Let’s provide these people with technologies to get them as fit and well as possible for that surgical intervention, because then post-surgery they’re going to have better health outcomes. And that’s also where digital health can help: rehabilitation. We don’t have enough physiotherapists and occupational therapists, and even if you’ve got access to a physiotherapist or an occupational therapist, it’s likely to be once a week. What about all the other time? Well, a digital health package can help, and you can have access to your interventions on your phone when you need them. So you can hear that I’m really passionate about wanting to help more people have access to healthcare when they want it and when they need it. That’s my underlying [inaudible].
Great. And I think that passion really is required. Whatever you do, if you know your passion, everything else becomes a journey toward it, and you [inaudible] the challenges you would otherwise face.
There was a part two to my question that I’d like to come back to. Since you’ve had this experience of working in health tech in various roles and companies, and you have such an accomplished career, are there any learnings or anecdotes you’d like to share, especially for young health tech professionals who are just getting started, seeing digital health from day one, and seeing how things are changing, maybe with generative AI as a solution as they start? Share some wisdom.
Yeah, sure, no problem. I’ve had lots and lots of lessons learned, and I’m sure I’ve got plenty more to come, which is part of the excitement of the journey: you learn every day.
My first lesson is that if you want to get involved in this space, you have to have passion, and you have to be really clear about the problem you’re trying to solve. You have to fall in love with that problem, because that is the passion and the drive that will get you up every day to work toward a solution. But don’t get wedded to the solution. Get wedded to the problem, because your solution will keep changing. As you’ve just described, new opportunities are emerging around AI, for example, and when I started, AI wasn’t even a thing. The problem I’m trying to solve is how we help more people have access to healthcare through [inaudible], and now we have the opportunity to feed AI into that. If I had got wedded to the solution, I would never change the solution. So get obsessed with the problem, and get really passionate about dealing with it and driving it forward.
My second lesson is to find amazing people to work with. You can’t be great at everything, so be honest with yourself about what you’re brilliant at and what you’re not, and then find people who are brilliant at the things you’re not good at, so you can work collaboratively. And that’s another lesson: always work in partnership. We quite often get asked, “Who are your competitors?” I don’t see that as a reality. Anybody who’s interested in this area, who can help us achieve our mission of improving lives and achieving sustainable healthcare for everybody, I want to work with them, whether they’re doing the same thing or not. So collaboration is king, working with different parts of the system to really solve that problem.
I’m just going to say two other lessons; as I said, I’ve got a lot of lessons. One of them is all about resilience. You’ll have days that are really difficult, weeks that are really difficult, and sometimes months that are really difficult. That is, unfortunately, life. But how do you build resilience? For me, I have an analogy I use, which is a waterfall. I’m really fortunate: I live very close to the countryside, where there are lots of lakes and streams, and when I walk I quite often see small waterfalls. When you look at a waterfall, it’s very turbulent, a fast body of water coming over, and it can feel like that sometimes at work. But the thing to recognize is that there is always an after the waterfall, and after the waterfall it is calm again, and deeper. That’s because you learn most when you go through turbulent times. So when I’m going through a turbulent time, I know it will end. I don’t know when it’s going to end, but when it does, it will become calm again, and the water will be deeper.
And then my final lesson is to be really grateful. I’ve got massive amounts of gratitude: gratitude for the people I work with, gratitude for being able to try something different, and gratitude for the partners, the collaborators and the people we work with. I think being really grateful again helps you build resilience and then focus on what needs to happen next.
And I believe that in the bigger scheme of things, all the lessons you mentioned are valid, and they eventually all connect together. When you have that passion and you act on it every day, you start seeing those threads connect: resilience, courage, everything starts connecting together. So thank you so much, Liz. This has really been a master class, with so much wisdom you’ve shared with us. Really good, and thank you so much for taking the time.
No, thank you for inviting me. It’s my pleasure.
At the time of recording (ViVE 2023; published May 2023), Liz Ashall-Payne was the founding chief executive of ORCHA, the Organisation for the Review of Care and Health Apps, which evaluates digital health technologies against quality criteria, builds digital health formularies for health systems, and helps clinicians recommend and prescribe approved apps. She began her career nearly 25 years earlier as a clinician in complex pediatric care, spent years leading lean and quality improvement work in the NHS, and then worked internationally with system leaders on digital health adoption before founding ORCHA in 2015. By her account ORCHA had completed nearly 25,000 assessments and was working in 13 countries across Europe, the Middle East, North America and Australasia.
Building a health app that has to clear HIPAA, a health system security review or a formulary review? Tell us what you’re building and we’ll show you how we’d approach it.
Partner with us to design, build, and scale digital solutions that drive better outcomes.
Global Tech Teams LLC, 525 Washington Blvd, Industrious at Newport Tower, Jersey City, NJ 07310, United States.
Let’s discuss your goals, workflows, and next steps in a focused consultation call.