IM1 is the interface mechanism that lets a third party system connect to GP clinical systems in England. If your product needs to read a patient's GP record, pull data out in bulk, or write something back into the record, IM1 is how that happens.

It comes in two parts. Pairing covers reading and bulk extraction. Transactional covers writing back. Most products need one or the other, some need both, and which you need changes the cost and the timeline considerably.

Getting through it means a set of prerequisites, a Supplier Conformance Assessment List describing exactly what your product does with the data, a licence agreed with each system supplier, development against a mock interface, two phases of testing, witness testing, and assurance sign off. Only then does NHS England issue a recommendation to connect.

The part people underestimate is that the system suppliers are separate commercial organisations with their own queues and their own terms. NHS England assurance and a supplier licence are two different gates, and you need both.

No. Classification and clinical safety are done by specialists we work with. DCB0129 in particular needs a named Clinical Safety Officer who signs personally, so it is never something a consultancy does on your behalf in the abstract.

What we do is decide what is needed, bring in the right person, manage them, and keep it aligned with everything else. You can also contract them directly if you prefer, and we will introduce you at no charge.

It depends where your customers are. The two principal GP systems in England are EMIS Web, now under Optum, and SystmOne from TPP. They are not evenly spread, so the answer usually comes down to which regions have said they want you.

A common pattern is to pair with one, prove the model, then find the next customer is on the other and the work starts again. Worth deciding deliberately rather than by accident.

The system suppliers charge for parts of the process, and there are ongoing costs once you are live. The amounts vary by mechanism and by supplier, and they change. We will give you current figures for your specific case rather than a number on a website that goes stale.

The larger cost is usually your own engineering time and the months of elapsed calendar, not the fees.

Longer than most teams plan for, and it varies a lot by product. Much of the variance sits in waiting on other organisations, and in how quickly your own team produces the documentation.

We will give you a realistic range for your case in the assessment rather than a generic number.

It helps, and usually less than people expect. A pilot shows the product works. It does not create a purchasing route, and pilot data is often not the evidence a commissioner will ask for when it comes to buying at scale.

We see a lot of companies with good pilot results and no way to convert them. Worth checking which position you are in before building the next year around it.

Not necessarily. Some companies reach the market through an existing assured integration engine, connecting under someone else's assurance rather than obtaining their own. That is faster and cheaper up front, with real trade offs on control, commercials and how you are seen by buyers.

Both routes are legitimate. We will tell you which one fits and what it costs you later.

A Supplier Conformance Assessment List. It is the document that sets out exactly what your product does, what data it touches, and how it behaves, and it is what the assurance is granted against.

It matters more than it sounds. Your assurance is scoped to what the SCAL says. If the product later does something the SCAL does not describe, you are outside your assurance and need a formal change process.

Yes. NHS England requires a formal Request for Change with an updated SCAL where an assured product has evolved from its original use case, and specifically calls out integration of AI as a trigger for that.

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

IM1 is an England mechanism. Scotland, Wales and Northern Ireland have their own arrangements and their own system landscapes, so a product assured in England does not automatically travel.

If your plan assumes UK wide coverage, that is worth examining early, because it affects both cost and the size of the market you are describing to investors.

NHS England has said there are no current plans to decommission it, and that the long term future is under consideration with no confirmed alternative or timescale. Plan on the basis that it is the route today.

Mostly early stage. Companies with a product that works, a customer or two interested, and no in house experience of NHS assurance. That is where the sequencing mistakes get made and where they are cheapest to fix.

We also work with established suppliers adding a second system supplier, or making a change to a product that is already assured.