"What monitoring does this medicine need?" looks like a single question and is answered, in practice, across four or five sources: a general monograph's summary, the exact product's authorised warnings, a specialist society's recommendation, the local shared-care protocol that allocates who does what, and the patient-specific factors that modify all of it. That distribution is not bureaucratic accident, each layer knows something the others do not, and the skill is assembling them into one defensible plan quickly. Here is the assembly method, with worked examples.
The main resources, and what each knows
Start with the applicable NICE or specialist guideline for the clinical pathway. Use SPS monitoring advice where a relevant topic exists, and inspect the exact SmPC for authorised warnings and product-specific monitoring. Where shared care applies, the local document defines ownership, frequency, thresholds and actions. iatroX Medicines can orient the search and link to sources, but the final plan must reflect the patient, product, local agreement and responsible clinical team.
Before starting: the baseline logic
Every monitoring plan begins before the first dose, and the same checklist assembles it: the baseline tests the sources above specify; contraindications and cautions checked against this patient; the comorbidities that change surveillance; interactions screened, including over-the-counter and herbal; pregnancy status where relevant; and, the item that fails most often in real systems, an explicit answer to who will own ongoing monitoring, especially across the primary-secondary care boundary, which is precisely what shared-care documents exist to settle.
During treatment: intervals and exceptions
Ongoing monitoring has a routine layer, the standard interval for the standard patient, and an exceptions layer that matters more: tightened surveillance for higher-risk patients; re-checking around intercurrent illness, the dehydrating gastroenteritis that changes renal handling; responding to trends rather than single values; and the symptom triggers that demand reassessment ahead of schedule. A plan that specifies the routine and names the exceptions is a monitoring plan; a plan that specifies only the interval is a calendar.
Worked example: apixaban
The apixaban clinical page frames the domains and links the sources: baseline and periodic attention to full blood count, liver function, urea and electrolytes, weight and creatinine clearance; ongoing review of bleeding, anaemia, adherence, interactions and whether the indication continues; and closer surveillance with older age, frailty or renal impairment, exactly the patients in whom DOACs concentrate. SPS's DOAC monitoring guidance supplies the practical schedule, the SmPC the product's authorised wording, and the local anticoagulation pathway the ownership; the assembled plan then survives both the deteriorating-renal-function scenario and the audit.
Worked example: long-term nitrofurantoin
Repeated or prophylactic courses convert an ordinary antibiotic into a monitoring case. The nitrofurantoin clinical page sets the frame: renal function, with product-specific wording that differs between preparations; liver function; and vigilance for the long-term pulmonary, hepatic, neurological and haematological toxicity that makes duration itself the risk factor. The local UTI guidance answers whether the continuing indication remains valid, which is the question long-term prescriptions most need asked; MHRA communications are worth checking for exactly this class of slow-burn toxicity; and the documented plan includes the safety-netting symptoms that trigger early review. A shorter version of the same logic covers prolonged amoxicillin, renal and liver function and full blood count on the radar, with INR attention where relevant companions are in play, via the amoxicillin clinical page.
Frequently asked questions
Who is responsible when shared care has not been formalised?
The prescriber, which is the uncomfortable answer that makes shared-care documents worth insisting on before amber-drug prescribing transfers; your formulary's key and the LMC's position both bear on it: /blog/how-to-find-use-local-nhs-formulary.
Do stable long-term patients really need the routine interval?
The routine interval is the evidence-informed default, and stability earns its keep in the exceptions layer, not by abandoning surveillance; deviations should be deliberate, documented decisions.
Where do point-of-care monitoring questions go out of hours?
SPS for the practical answer, the SmPC for the authorised one, and the on-call pharmacist when the two need reconciling for this patient tonight.
How should monitoring be handled for patients who decline blood tests?
As a documented shared decision: the risks of unmonitored treatment explained, alternatives considered, the decision and safety-netting recorded, and the plan revisited rather than abandoned. The sources define the standard; deviation from it is a clinical judgement that must be visible in the record, not an omission discovered at audit.