Why do ADHD services have an IT gap in the first place?
Because the service model outgrew the tooling: ADHD services scaled on generic telehealth stacks, video plus forms plus a calendar, and that stack cannot carry what makes this category distinctive, which is longitudinal, dose-linked, evidence-grade records over a Schedule 2 prescribing cycle. A dermatology consultation is an episode; ADHD titration is a programme, running weeks to months, generating a dose decision, a set of observations and a fresh controlled drug prescription every cycle, feeding eventually into a shared care handover that a sceptical GP will read line by line. It assumes the regulatory picture from our scrutiny analysis and the rulebook from the Schedule 2 dispensing guide.
Three pressures make the gap expensive now. Shared care acceptance, the sector's commercial choke point, turns substantially on whether the GP receives a legible, structured titration record rather than a PDF of appointment notes, so record quality is now revenue. The scrutiny environment means the question "show me the physical assessment, the baseline observations and each dose decision" is being asked by commissioners and will be asked by inspectors, and a service that answers it from a searchable record is a different regulatory proposition from one that answers it from an inbox. And the dispensing tempo, a new prescription and dispensing episode per patient per month with no repeats, is a workflow volume problem that manual coordination between clinic and pharmacy simply drops things through, exactly the drops that become the incidents.
What does the system actually need to do?
It needs to carry the patient from booking to dispensed medicine and back around the monthly loop, with every clinically significant datum structured, dated and attributable. The criteria, stated vendor-neutrally so you can score anything against them:
| Criterion | Why it matters in an ADHD service | What to ask any vendor |
|---|---|---|
| Bookings and scheduling | Assessment, titration reviews and annual reviews are a recurring cadence, not ad hoc appointments | Can services, availability and automated reminders be configured per appointment type? |
| Structured clinical assessment | The NICE-standard assessment, including physical and cardiovascular history, must be captured as evidence, not prose | Are assessments configurable, completed by the patient online and stored against the record? |
| Titration tracking over time | Dose, response, side effects and observations per cycle, comparable across cycles | Can fields be added, updated at each review and tracked longitudinally? |
| Monitoring and recalls | Baseline and ongoing observations, with recalls that fire rather than rely on memory | Are results recordable against the patient, with reminders driving review and recall dates? |
| Notes and attribution | Every decision dated and owned, readable months later by a GP or an inspector | Are notes timestamped, attributed and unalterable after the fact? |
| Prescription workflow | A fresh Schedule 2 prescription each cycle, generated, transmitted and tracked, never lost in email | How does a prescription move from decision to the dispensing pharmacy, and where is its status visible? |
| Dispensing and labelling | Dispensing against the prescription with compliant labels including cautionary wording | Is dispensing in-platform with label printing, or a separate system to reconcile? |
| Controlled drug support | Schedule 2 stock demands register discipline; software support reduces the parallel-process burden | What CD functionality exists today, and what is roadmap with dates? |
| Audit trail and access control | Individual logins, role-based access, every view and change logged | Show me the audit log and the permission model |
| Website embedding | The assessment is the front door; re-keying from web forms is where data quality dies | Can clinical assessments embed directly on our website? |
| Supplier diligence layer | The system holds special category data for a clinical service | DCB0129 clinical safety documentation, UK/EEA hosting, signed DPA, breach notification terms |
Two of those rows do most of the differentiating. Titration tracking is the one generic telehealth stacks fail structurally, because a form platform captures a snapshot while titration is a series, and the test is whether cycle three's observations sit comparably beside cycle one's. And the supplier diligence row is the one founders skip at speed and regret at inspection; it is the same six-question layer set out in our patient data security briefing and DCB0129 for pharmacy software buyers, and it applies to whichever vendor wins.
How does Dataforge PMR answer these criteria?
Dataforge PMR runs the loop in one platform, which is the structural answer before any feature answer: the assessment the patient completes, the prescriber's notes and decisions, the monitoring fields, the reminders and the dispensing all live on one patient record with one audit trail, so the shared-care pack and the inspection answer are queries, not archaeology projects.
Walked in workflow order. The Bookings module carries the service catalogue, availability and automated reminders, so the titration cadence is scheduled rather than chased. Clinical assessments are completed by the patient online and embed directly on the clinic's website, landing structured in the record instead of arriving as a PDF to re-key. Titration is carried as custom fields within the assessment framework, added to fit the service's own protocol, then updated and tracked over time, which is precisely the longitudinal series the shared-care GP wants to see: dose, date, response, observations, cycle by cycle. Monitoring results are recorded against the patient and reminders drive the recalls, review dates and reorder prompts that a monthly Schedule 2 tempo demands. Prescribing support runs on comprehensive drug data with clinical decision support flagging interactions, contraindications and duplicates at the point of decision. Notes carry the attributed clinical narrative. And dispensing closes the loop in the same platform, with drug label printing including cautionary wording, so the pharmacy side of the service works from the same record the clinical side wrote.
On controlled drugs, stated the way we would want any vendor to state it to us: a controlled drugs register module is scheduled for release at the end of 2026, and until then the CD register runs as a disciplined parallel process alongside the platform, which is a fully inspectable position provided the process is owned and run, as covered in the handling guide.
On the diligence layer, Dataforge PMR answers the questions we tell buyers to ask everyone: DCB0129 clinical safety documentation, a signed data processing agreement, UK and EEA hosting, individual role-based logins and full audit trails.
What will no software fix?
Governance, and it is worth saying in an article that sells software. A system makes good practice cheap and visible; it does not create the practice. The physical assessment leg of a remote pathway is a service design decision the software records, not one it performs. Prescriber verification at the pharmacy, the day-one shortfall decision in a shortage, the shared care conversation with a hesitant GP and the superintendent's ability to justify every SOP are human accountabilities that the record supports and cannot replace.
"Treat any vendor who implies the software is the compliance as telling you something about the vendor."
The right sequence for a founder is therefore the one this cluster of articles keeps repeating: design the clinical pathway to the standard first, then buy the system that makes the standard effortless to evidence. The structural questions upstream of the system, including whether clinic and pharmacy belong under one roof, are the subject of our forthcoming piece on the clinic-plus-pharmacy model.
Key takeaways
- Much of the 2026 scrutiny of ADHD services is a records problem: titration, monitoring and physical assessment evidence that generic telehealth stacks cannot carry.
- Shared care acceptance now turns substantially on record quality, which makes structured titration data revenue, not admin.
- Score any system against the eleven criteria in the table, with titration-over-time and the supplier diligence layer as the differentiators most vendors fail.
- The monthly Schedule 2 tempo means prescription generation, transmission and dispensing must be workflow with visible status, not email.
- Dataforge PMR runs the loop in one audit-trailed platform: embedded assessments, custom titration fields tracked over time, monitoring with recall reminders, drug data with decision support, notes and dispensing with label printing.
- The controlled drugs register module lands at the end of 2026; until then the register is a parallel process, and any vendor's CD claims deserve the same dated precision.
- Software makes good governance cheap to evidence; it does not substitute for the pathway design, verification and accountability that remain human.
FAQs
Score us against the table.
If you are building or scaling an ADHD service, the fastest way to test the criteria in this guide is against a live system: a 30-minute Dataforge PMR walkthrough covers the embedded assessment, the titration fields, the reminder engine and the dispensing loop, and we will tell you plainly where the platform ends and your governance begins.
Book a 30-minute demo