Owl Studios
NHS route to market

Good products fail in the NHS for boring reasons.

Not because the technology is wrong, and usually not because the clinical case is weak. They fail because the steps were done in the wrong order, or because one was skipped and nobody noticed until it was expensive. We have watched it happen from inside the NHS system suppliers and from inside the companies trying to get in. We know what order it goes in.

The problem

Nobody sells you the map.

There are regulatory consultants who will do your MHRA classification. Clinical safety officers who will write your safety case. Procurement specialists who know the frameworks. Integration people who know IM1. Every one of them will sell you their step, competently.

What kills companies is not knowing which step comes first, which ones they did not need, and what each one costs in time they have not budgeted. We have seen companies with real published outcome data from real NHS trusts run out of money before anyone could buy them, because the order was wrong.

A pilot or two proves the idea. It does not get you deployed. What gets you deployed is a route, and a route is a sequence.

The route

Six things stand between you and being bought.

Not all of them apply to every product. Working out which ones do not apply to you is a large part of the value.

01
Classification

Are you a medical device?

What you claim the product does decides how it is regulated. Get this wrong early and the evidence you gather afterwards is aimed at the wrong target.

Specialist partner, we manage it
02
Clinical safety

DCB0129 and the hazard log

A named Clinical Safety Officer, a safety case and a live hazard log. Not paperwork for the end. Nothing else moves without it.

Specialist partner, we manage it
03
Information governance

DSPT, DPIA and DTAC

The assessment every NHS buyer will run at you covering clinical safety, data protection, security, interoperability, usability and accessibility.

Owl Studios
04
Route to purchase

Frameworks and buying routes

Wanting to buy you is not the same as being able to. Without a purchasing route, a keen clinician cannot get you past their own finance team.

Owl Studios
05
Integration

IM1 and the GP record

Reading from, extracting from and writing back into GP clinical systems. It is the plumbing, but completing it also puts you on a public NHS England list, which buyers use as proof you can be deployed.

Owl Studios
06
Evidence

Proving it works, to their standard

Pilot data and the evidence a commissioner asks for are usually different things. Knowing which one is being asked of you saves a lot of wasted work.

Owl Studios, with clinical input

We hold the plan and stay accountable for all of it. Where a step needs a specialist, we bring in someone we have worked with and manage them. You get one contract and one person to call, not four suppliers and a spreadsheet.

How we work

Three ways in, depending on where you are.

01

Route to market assessment

Fixed price / Two weeks

You tell us what you are building, what you claim it does, and who has said they want it. We go through all six steps and tell you which apply, in what order, what each will cost in money and time, and what you can skip.

You get a written plan you can put in front of a board or an investor, with the sequence and the numbers in it.

A fair share of the companies we run this for are told to wait, or told the route they were planning is the expensive one. That is the answer more often than anyone selling you a single step will say.

02

Route to market programme

Retainer

We run the plan. One contract, one accountable party. We deliver the integration, governance and evidence work ourselves, and bring in specialists for classification and clinical safety, managed by us and priced through us.

If you would rather contract the specialists directly, we will introduce you and charge nothing for it. Some clients prefer that. It is a fair question to ask.

Retained rather than fixed price, because the timeline depends on queues that belong to other organisations. Anyone quoting a fixed price for an assurance process is pricing in a margin for that risk, and you are paying for it.

03

Build

Day rate or by the project

Sometimes the route is not the problem and the product is. We build that too. Data platforms, integrations, reporting, clinical workflow, the unglamorous back end. Twenty years of it, most of it in health.

We also work outside health. Health is what we are known for, not the only thing we do.

Why us

We have seen this from the other side of the table.

Almost everyone advising on NHS integration has only ever seen it from the outside, as a supplier trying to get through.

Graham Downhill led the partner product team at EMIS and ran the IM1 programme there from a technical product point of view. That is the other side of the table. It means knowing why a submission gets bounced before it gets bounced, and how a principal supplier actually reads a request rather than how the guidance says they should.

He has also been through onboarding several times as a customer, for multiple products. Products he has built appear on NHS England's published list of suppliers who have completed IM1 assurance, which is a better reference than a case study we wrote about ourselves.

Product Director for Data and Analytics at EMIS Health / CEO at Promatica Digital / earlier work at Medicalchain

Straight answer

When you should not start yet.

We would rather tell you this now than take your money.

No confirmed deployment site

If no practice, trust or ICB has committed to taking the product, there is nothing to integrate into yet. Get that commitment first. It makes every step after it easier and cheaper.

Product claims are not yet fully defined

What you claim the product does decides whether it is regulated as a medical device, and that decides what evidence you need. If the claim changes later, the work is done again.

Less than six months of funding

Much of the elapsed time is spent waiting on NHS England and the system suppliers. Running out part way through means paying for an assurance you never finish.

A simpler route may be available

Not every product needs IM1, and not every product is a medical device. Worth checking before committing to the expensive version.

A note on AI

Passing IM1 does not mean your AI has been assured.

NHS England is explicit that IM1 pairing does not include AI specific technical assurance. Assessment of the models, the algorithms and the associated risks sits outside the process, and until further guidance is issued, deploying organisations are responsible for that assurance locally.

Two consequences. First, getting through IM1 does not mean your AI has been assured, and the organisation deploying you will eventually ask. Second, if you already have an assured product and you are adding AI to it, that is a change to your assured use case and it needs a formal Request for Change with an updated SCAL.

Plenty of companies are walking into both without knowing. If that sounds like you, it is worth an hour of conversation.

Before you ask

Questions about IM1 and GP integration.

What IM1 actually is, whether you need EMIS or SystmOne or both, what it costs beyond our fees, what a SCAL is and why it constrains you later, and what changes when you add AI to a product that is already assured. Plain answers, no sales copy.

Start here

Tell us what you are building.

A short conversation now is worth months later. No pitch, and if the honest answer is that you are not ready, we will say so.

This website uses strictly necessary cookies only. We do not track visitors, serve advertising, or share your data with third parties. For more information, please see our Cookies Policy. View more
Cookies settings
Accept
Decline
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Privacy Policy Last updated: 30/06/2026

    1. Who we are Owl Studios is a trading name of Owl Insights Ltd, a company registered in England and Wales. We are the data controller for personal data collected through this website. You can reach us at hello@owl-studios.co.uk. Our ICO registration number is  ZC180714.
    1. What this policy covers This policy explains what personal data we collect through owl-studios.co.uk, how we use it, and the rights you have. It does not cover other websites we link to, which have their own policies.
    1. The information we collect Information you give us If you email us or use the contact details on this site, we receive your name, your email address, and whatever you choose to tell us about your enquiry or project.
Technical information Like most websites, our hosting provider automatically records basic technical data such as your IP address, browser type, and the pages you view. This is used to keep the site secure and running. Fonts This site loads the Inter typeface from Google Fonts. To serve the font, Google may receive your IP address. Cookies See our Cookies Policy for detail on the cookies this site uses.
    1. How we use your information, and our lawful bases We use your information to:
respond to your enquiry and discuss possible work (our legitimate interest in handling enquiries, or taking steps at your request before entering a contract); provide and manage any services you engage us for (performance of a contract); keep the website secure and working properly (legitimate interest); meet legal, tax, and regulatory obligations (legal obligation). We do not use your information for automated decision-making or profiling, and we do not sell it.
    1. Who we share it with We do not sell your personal data. We share it only with the providers who help us run the business, under appropriate terms. These currently include our website hosting provider, our email provider (Microsoft, supplied through GoDaddy), and Google (for fonts). Some providers may process data outside the UK. Where they do, we rely on appropriate safeguards, such as the UK approved transfer mechanisms.
    1. How long we keep it We keep enquiry correspondence for as long as we need it to deal with your enquiry, and for a reasonable period afterwards in case you get back in touch. Where we take on work, we keep records for as long as needed to deliver the service and to meet legal, tax, and accounting requirements. We do not keep personal data for longer than necessary.
    1. How we protect it We take reasonable technical and organisational measures to keep your information secure and to limit who can access it. No transmission over the internet is ever completely secure, but we work to protect the data you share with us.
    1. Your rights Under UK data protection law you have the right to access a copy of your data, ask us to correct it, ask us to delete it, restrict or object to how we use it, and, in some cases, receive it in a portable format. Where we rely on your consent, you can withdraw it at any time. To exercise any of these, email hello@owl-studios.co.uk.
If you are unhappy with how we have handled your data, you can complain to the Information Commissioner's Office at ico.org.uk. We would appreciate the chance to put things right first, so please do contact us. Contact Questions about this policy or your data: hello@owl-studios.co.uk. Changes to this policy We may update this policy from time to time. The date at the top shows when it was last changed.

Cookies Policy

Last updated: 30/06/2026

1. What cookies are

Cookies are small text files a website can store on your device. They are widely used to make sites work, to remember preferences, and to understand how a site is used.

2. How we use cookies

We keep this to a minimum. This website does not use advertising or tracking cookies.

Strictly necessary cookies

The site runs on WordPress, which may set a small number of essential cookies, mainly for people who log in to manage the site. As an ordinary visitor browsing the site, you are not asked to sign in and are not tracked.

Fonts

The Inter typeface is loaded from Google Fonts. Google Fonts does not set cookies, but serving the font means Google receives your IP address. See our Privacy Policy for more.

Analytics

We do not currently use analytics. [If you add a tool such as a privacy-friendly analytics service, list it here, and where it sets non-essential cookies, add a consent banner so visitors can accept or decline before it runs.]

3. Consent

Strictly necessary cookies do not require consent. Any non-essential cookies, for example analytics or marketing, require your consent before they are set. If we ever introduce them, we will ask for your consent through a banner first.

4. Managing cookies

You can control and delete cookies through your browser settings, and set your browser to block cookies or warn you when a site tries to set one. Blocking essential cookies may affect how some websites work. General guidance is available at ico.org.uk and aboutcookies.org.

5. Contact

Questions about cookies: hello@owl-studios.co.uk.
Save settings
Cookies settings