# Help Needed: Integrating GP Connect into AI Task‑Generation App for Clinicians **Category:** [NHS Spine & APIs Support](https://openhealthhub.org/c/nhs-spine/25) **Created:** 2026-03-28 20:18 UTC **Views:** 18 **Replies:** 5 **URL:** https://openhealthhub.org/t/help-needed-integrating-gp-connect-into-ai-task-generation-app-for-clinicians/2959 --- ## Post #1 by @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! --- ## Post #2 by @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 │ > └──────────────────────────┘** --- ## Post #3 by @mayfield.g.kev 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. --- ## Post #4 by @mayfield.g.kev 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 --- ## Post #5 by @pacharanero 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: https://openhealthhub.org/t/a-simple-guide-to-gp-system-integration-options/2961 This article was pretty good https://6b.health/insight/understanding-the-nhs-im1-transaction-bulk-and-patient-apis-a-non-technical-overview/ and there is an official NHS Developers forum where you can ask questions https://developer.community.nhs.uk/ --- ## Post #6 by @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: https://identity.prod.api.platform.nhs.uk/realms/developer-identity/protocol/openid-connect/auth?client_id=digital-onboarding-service&redirect_uri=https%3A%2F%2Fonboarding.prod.api.platform.nhs.uk%2Fsignin-oidc&response_type=code&scope=openid%20profile&code_challenge=18UyjnKf-acRlpXv-PGHG9Tqx9j-9SXoj_U8nByhaWc&code_challenge_method=S256&response_mode=form_post&nonce=639111049571527970.NTUxNzRlODktMmFjYi00NzMzLWI4NWYtMTU3OThmZDdmY2MwNmVhYmJmZjMtODc0Mi00N2ViLWJlMzAtZDViNzJhZGE2ZDYx&state=CfDJ8Ii__JOTqCdIql-avcJPGppS6nDeVyaMAkjPrAtf63PkmA5yw4_nHo_Lij3hR4js2-ibqBRivc5VmjXvkSLLKOf25MQbLZ33UcBb8Z-n15WdTXpSh9-7zoi4l23k_AzsJjVrfR6PdP-f32ajF5aWGRY74uky6Ny6_laedKrEIt205sSJk34PJhtp51N2hvp53AZWVsmkMytdEgRKqb42nAyy2z8jeKosC5p8AqdFKcIqbAyCk77BMMgii6y0-YZIY3HuTbE0t0n-C81zFW2EnqxYo1x8oZ9XaXsJZiXXDPz42reQTUbUrNR0EsiEFpB8_f8rF6Sc-6a-PhXqOGi_OvngHStcN9zl0RWQSHrZXunuX8dH2hIrPKFAdvhCT07dyfcIc66s9ZMO2pRWYefiyCc3U2eNl2QfAjGonSf_fnKuplZIqi9NOmvO6nuYUBjFtnrWO6q9oeZRqZsdrMgzVDWAxyUqXp0K9gA4F4pTJurtf6ZyHMcVAGuMjKN95iJPR5PXY5-vG0vmRS21aFqcSpFE-\_COeOstl9McKC2V7dPgtMYHFYldlD69TPN0_YvvAbBoAZ2HfIhGAvx4ZpGTf1M&x-client-SKU=ID_NETSTANDARD2_0&x-client-ver=6.10.0.0 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. --- **Canonical:** https://openhealthhub.org/t/help-needed-integrating-gp-connect-into-ai-task-generation-app-for-clinicians/2959 **Original content:** https://openhealthhub.org/t/help-needed-integrating-gp-connect-into-ai-task-generation-app-for-clinicians/2959