What makes an ADHD service's software needs different?
Two things: the tempo and the series. The tempo first. Schedule 2 rules permit no repeats, so treatment runs on a monthly cycle of prescription generation, transmission, dispensing and delivery — per patient, indefinitely. Even a modest service is running hundreds of controlled drug jobs a month through whatever coordination layer it owns. Then the series. Titration is not an appointment but a programme: dose, response, side effects and observations per cycle, comparable across cycles. The value of cycle five's record depends entirely on whether it sits structurally beside cycle one's. Generic telehealth stacks capture snapshots; this category runs on sequences. This article applies the general case made in the IT gap article to the specific buying decision, in the records climate covered in our scrutiny analysis.
Around those two sit the category's specific loads, all covered in the compliance companion pieces. Private prescriptions go on FP10PCD with prescriber identifiers and monthly NHS Business Services Authority submission, per the Schedule 2 dispensing guide. The physical assessment and baseline evidence are what the 2026 scrutiny centres on. The shortage environment demands stream-aware patient records, per the handling guide. And in the shared-care handover, a structured longitudinal record is now measurably the difference between GP acceptance and refusal. A service whose titration history lives in appointment-note PDFs is not just inefficient. In the current climate it is under-evidenced.
What are the criteria for ADHD clinic pharmacy software?
Score any vendor, including us, against this table:
| Criterion | Why it matters for ADHD services | What to ask any vendor |
|---|---|---|
| Bookings on a cadence | Assessment, titration reviews and annual reviews recur; missed reviews are the failure pattern | Configurable appointment types with automated reminders? |
| Structured clinical assessment | The NICE-standard assessment, cardiovascular history included, must exist as evidence | Patient-completed online, embeddable on the clinic's website, stored structured? |
| Titration as a longitudinal series | Dose decisions per cycle, comparable across cycles, legible to a GP months later | Can fields be added to fit our protocol, then updated and tracked over time? |
| Monitoring and recalls | Baseline and ongoing observations, with recalls that fire | Results recordable against the patient, reminders driving review dates? |
| Prescription workflow at tempo | A fresh Schedule 2 prescription monthly, per patient, with visible status | How does a prescription move from decision to dispensing, and where does its status live? |
| Dispensing with labelling | Every monthly supply labelled with the required particulars and cautionary wording | In-platform dispensing with label printing? |
| Controlled drug support | Register discipline at monthly-cycle volume is the hidden staffing cost | What exists today, what is roadmap, with dates? |
| Shared-care output | The handover pack is the commercial choke point | Can the titration and monitoring history be produced as a legible record for a GP? |
| Audit trail and attribution | Every dose decision dated and owned, for GPs, inspectors and worse | Individual logins, role-based access, unalterable attributed notes? |
| Supplier diligence layer | Special category data in a clinical system | DCB0129 documentation, UK/EEA hosting, signed DPA, breach terms |
Two rows separate the field. Titration-as-series is the one form-based platforms fail structurally. The shared-care output row is the one almost no vendor is asked about — and every ADHD service lives or dies by it. Ask both in writing and keep the answers.
How does Dataforge PMR answer each criterion?
In the order the patient moves. The Bookings module carries the service catalogue, availability and automated reminders. That makes the assessment-titration-review cadence scheduled machinery rather than chased diary work. The clinical assessment is completed by the patient online and embeds directly on the clinic's website, landing structured in the record. That is where the NICE-standard baseline, cardiovascular history included, becomes evidence rather than an attachment. Titration is carried as custom fields within the assessment framework: added to fit the service's own protocol, then updated at each review and tracked over time. The result is exactly the cycle-by-cycle series — dose, date, response, observations — that a shared-care GP wants to read and an inspector wants to query. Monitoring results are recorded against the patient, with reminders driving the recalls, review dates and reorder prompts a monthly Schedule 2 tempo demands. The reorder prompt matters more in this category than any other, because the shortage environment punishes late reordering and the law permits no bridging. Prescribing support runs on comprehensive drug data, with clinical decision support flagging interactions, contraindications and duplicates. Notes carry the attributed clinical narrative, timestamped and owned. Dispensing closes the monthly loop in the same platform, with drug label printing including cautionary wording, on the same audit trail as the clinical record. That is what makes the shared-care pack a query across one system rather than an assembly job across three.
On controlled drugs: a controlled drugs register module is scheduled for release at the end of 2026. Until then the register runs as a disciplined parallel process with named ownership per session. That position is fully inspectable, and we state it plainly because vendor candour on CD functionality is itself a selection signal. On the FP10PCD leg, the monthly NHSBSA submission is a paper process by design. The system's contribution is the supply record and job status behind it, not the submission itself.
And on the diligence layer, Dataforge PMR answers the standard this site sets for everyone: DCB0129 clinical safety documentation, a signed data processing agreement, UK and EEA hosting, individual role-based logins and full audit trails. The standard itself is set out in the patient data security briefing.
What should the decision process look like?
Buy against the monthly loop, because the loop is the business. Write your cycle first — assessment to titration review to prescription to dispensing to delivery to reorder prompt — annotated with your projected patient count. Then make every candidate walk it on real screens. Where does cycle three's dose decision live? How does the GP pack come out? What fires when a review is missed? What does the prescription's status look like mid-cycle? Put the two hard questions, CD functionality and shared-care output, in writing to every vendor and keep the replies. Run the diligence layer as a gate before commercial talks. And price the total honestly: the licence, plus the parallel processes any system leaves running, plus the cost of the records you cannot produce. In this category specifically, a declined shared-care agreement is lost recurring revenue.
"An unevidenced titration series in the current climate is risk with a subscription attached."
Hold every vendor, ourselves included, to one design principle. The record that satisfies the GP, the inspector and the incident review should be a by-product of running the service, never a project. That is what one platform across the clinic-plus-pharmacy structure buys. It is also why the structural decision in the clinic-plus-pharmacy model and the systems decision in this article are really one decision made twice.
Key takeaways
- An ADHD service runs on a monthly Schedule 2 tempo and a titration series. Its PMR must carry both natively, or the coordination layer becomes spreadsheets.
- Score vendors against the ten criteria. Titration-as-a-longitudinal-series and shared-care output are the questions that separate clinical platforms from telehealth stacks.
- Dataforge PMR carries the loop in one audit-trailed platform: bookings on a cadence, embedded structured assessments and custom titration fields tracked over time. Add monitoring with recall and reorder reminders, drug data with decision support, and dispensing with cautionary-label printing.
- The Dataforge PMR CD register module ships at the end of 2026. Until then the register runs as a named parallel process. We state that plainly because dated candour is what you should demand of every vendor.
- Shared-care acceptance is the sector's commercial choke point. A structured, attributed, longitudinal record is the strongest lever a service controls.
- Buy against your written monthly loop. Get the hard answers in writing, and price the records you cannot produce as the cost they are.
Sources and further reading
FAQs
Run the loop.
The fastest test of this article is the live loop. A 30-minute Dataforge PMR walkthrough runs an assessment through titration fields, a monitoring recall, a dispensing and the audit trail behind them. We will show you exactly where the platform ends and your parallel processes begin.
Book a 30-minute demo