Help Needed: Integrating GP Connect into AI Task‑Generation App for Clinicians

[Awais_Iqbal]

I’m a doctor, building an AI‑assisted task‑generation app aimed at reducing clinical workload by automatically analysing a patient’s medical record (via GP Connect) to surface clear, safe, actionable tasks for clinicians. The vision is to create a lightweight “clinical Task Assistant” that supports medication reviews, monitoring reminders, abnormal result follow‑up, chronic disease actions and safety alerts—without adding extra clicks or workflow burden.

I need support , guidance and collaboration from anyone with experience integrating GP Connect (structured record, observations, problems, meds, encounters, documents) and navigating the CIS2/SSP/SDS onboarding process. If you know this or interested in working together on this—I’d really appreciate your insights and guidance. Thanks!

[Awais_Iqbal]

┌──────────────────────────┐
│ Clinician (User) │
│ Uses App (Web/Mobile) │
└────────────┬─────────────┘
│
▼
┌──────────────────────────────┐
│ CIS2 Authentication │
│ (OIDC + PKCE workforce login)│
└────────────┬──────────────────┘
│
Auth token │
▼
┌──────────────────────────────────────────┐
│ App Backend │
│ • Session management │
│ • Audit logging │
│ • FHIR client modules │
│ • AI orchestration │
└───────────────┬──────────────────────────┘
│
│ 1. Identify patient
▼
┌─────────────────────────────┐
│ PDS FHIR API │
│ (NHS number + Demographics)│
└───────────────┬─────────────┘
│ NHS No + ODS code
▼
┌──────────────────────────┐
│ SDS (Directory) │
│ Find GP endpoint (ASID) │
└──────────────┬───────────┘
│ endpoint URL
▼
┌────────────────────────────┐
│ SSP (Spine Proxy) │
│ Secures & authorises calls │
└───────────────┬─────────────┘
│
▼
┌────────────────────────────────┐
│ GP Connect FHIR API (Practice)│
│ • Structured Record │
│ • Meds / Problems / Obs │
│ • Encounters / Documents │
└───────────────┬────────────────┘
│ FHIR Bundles
▼
┌──────────────────────────────┐
│ App Backend (Processing) │
│ • Parse FHIR → JSON │
│ • Build patient full dataset │
└──────────────┬──────────────┘
│
▼
┌──────────────────────────────────────┐
│ AI Clinical Task Engine │
│ • Identify risks │
│ • Generate actionable tasks │
│ • Monitoring / meds / safety flags │
└──────────────┬──────────────────────┘
│
▼
┌──────────────────────────┐
│ Clinician Task UI │
│ Clear actions to review │
└──────────────────────────┘

[mayfield.g.kev (Kev Mayfield)]

I’ve worked on several of those components. Some of them are quite lengthy (dev time 1 week - project admin 6 months)

If possible I would seek out someone who has experience of the admin side over the tech. The tech is relatively straight forward.

[mayfield.g.kev (Kev Mayfield)]

Note: GP Connect doesn’t support write access. As we were only working with a couple of GP practices we chose IM1 instead which includes writeback.

IM1 doesn’t scale well, it’s designed for individual GP practice only.

I kept our design open and it can be found here https://virtually-healthcare.github.io/ The workflow diagram is pathway not tech focused but it does appear to be similar.

Note my use of FHIR is same as US/EU view, not the more bespoke GP Connect/ NHS England version.
It is aimed at community level version of your app, i.e. it is designed to scale across multiple EPRs and is known as IHE Patient Care Coordination

[pacharanero (Marcus Baw)]

Thanks @mayfield.g.kev for helping with @Awais_Iqbal’s query. Kev is our local expert and one of the few with practical battle-hardened experience who is willing to talk about this stuff on an internet forum.

A couple of pointers I can add:

I collected this with LLM help, it may assist in compare-and-contrast of the various options:

A Simple Guide to GP System Integration Options

GP System Integration Mechanisms - A Guide for External Integrators This was written by an LLM based on conversations I had with it over a period of time and research done via web and offline documents. Current as of March 2026. The developer.nhs.uk site was decommissioned on 2 March 2026; some GP Connect spec links now point to UK Gov Web Archive copies. I thought it might be beneficial to post it here where others can read and learn from it. Sadly NHS England’s documentation is quite focused …

This article was pretty good

Understanding the NHS IM1 Transaction, Bulk, and Patient APIs: A...

and there is an official NHS Developers forum where you can ask questions

NHS England Developer Community

[thomaseyles]

Hi @Awais_Iqbal

GP Connect Access Record Structured or HTML should do the job. Note, you don’t receive all data points that you would, say, through IM1. I found GP Connect somewhat flaky, in their use case acceptance and the fact they pause/sunset APIs overnight. Access Record should be fine though.

• CIS2 - Not actually needed, but recommended for clincian auth. The CIS2 is great and helpful over email. There are two methods of authentication, separate and combined, combined being easier. You need a sandbox and prod CIS account. I have a number of Yubikeys set up for sandbox.
• PDS - This is a prerequisite as you will need to confirm the NHS number prior to any GP Connect call you make. Easy API and good team.
• SDS - No separate assurance or work needed here. You will undertake all necessary evidence during your GP Connect SCAL.

If you haven’t already, sign up and start your on-boarding process here: Log in to NHS Digital developer account GP Connect being the outlier its not on DOS for some reason.

GP Connect will be the biggest challenge/delay. They’ll scrutinise your AI and where you’re storing/processing data.