Safe administration – with pre-procedure risks, consent, and safety checks recorded
Appropriate monitoring – linking indication, symptoms, and blood test review
Correct coding – for both loading and maintenance courses
Continuity of care – standardised documentation across repeated appointments
Pre-procedure checks – risks, consent, 6 safety checks
Administration details – injection reason, treatment stage, route/site, needle size
Post-procedure documentation – outcome, advice, sharps disposal, Yellow Card if required
It also includes B12-specific sections:
Reason for therapy (pernicious anaemia, dietary deficiency, post-gastrectomy, other)
Symptoms reviewed (fatigue, neuropathy, cognitive changes, or none)
Blood tests checked/reviewed
Treatment stage (loading vs maintenance course)
Where a Local Enhanced Service exists, a section will automatically appear at the top of the template.
This ensures correct coding and claiming for B12 injection activity.
You do not need to search for or open a separate LES template.
Risks discussed (pain, bleeding, infection, allergic reaction, fainting)
Consent obtained and recorded
Injection given under PGD or PSD
6 safety checks completed
Vaccine cold chain confirmed (if relevant)
Record when B12 injections are started or stopped (coded appropriately)
Document whether the injection is part of a loading course or maintenance course
Site: left/right deltoid or thigh
Needle size (optional text entry)
Confirm injection given as prescribed and tolerated
Outcome: no reaction, faintness, pain/swelling, allergic reaction
Sharps disposed of safely
Aftercare advice documented
Yellow Card submitted if adverse reaction suspected
Always record the reason for B12 therapy – this is important for audit and coding.
Review and document symptoms at each appointment – particularly fatigue, neuropathy, or cognitive changes.
If starting treatment, clearly record loading course vs maintenance course.
Use the LES section (where available) for activity recording – it appears automatically.
For long-term maintenance, consider adding a recall/future action to support continuity.