Search loading...


Explore and Make use of Nationally Defined Messaging APIs


Community pharmacy giving a vaccination

Use case for community pharmacy giving a vaccination

Brief description

A community pharmacist can be asked to give vaccinations either as part of a local service (example: flu vaccination) or as a private service (example: travel vaccinations). There are certain allergies and conditions a pharmacist should check to ensure the vaccination they are giving is safe and appropriate for the patient. These checks can be assisted through access to the patient record.

Use case justification

Clinical and administration:

  • Access to accurate information at the point of care reducing the opportunity for errors to occur.
  • Reduction in transcription between systems and paper to IT, leading to a reduction in prescribing errors.
  • Reduction in clinical time wasted, away from the patient, collecting and collating information.
  • Reduction in clinical time wasted, away from the patient, manually updating IT systems.
  • Reducing the paper flow through departments by utilising the system workflow to manage tasks using staff time efficiently.


  • Security of patient information is maintained and improved through the reduction of paper-based ‘patient identifiable documents’ in use within departments.
  • Increased patient/clinician time due to reduction in clinician time spent collecting and transcribing information away from the patient.
  • Increased patient safety due to the reduction in manual transcription errors.
  • Better patient experience as they are not being asked for information which should already be available to the pharmacist.

Primary actors

  • Pharmacist
  • Pharmacy system
  • GP Connect
  • GP clinical system

Secondary actors

  • Patient


  • Patient attends a community pharmacist for a vaccination.


  • The patient’s details have been verified and entered on the pharmacy system upon attendance.
  • The pharmacist has the correct/appropriate system access rights.
  • The patient’s GP has agreed to share patient information via GP Connect.
  • The patient allows this shared information to be viewed/used by the pharmacist.
  • Electronic interactions between pharmacy system/GP Connect/GP clinical system have been correctly configured.


  • On success
    • The patient’s medical record is made available to the pharmacist.
  • Guaranteed
    • The pharmacist will treat the patient based on the information available.

Basic flow with alternative and exception flows

Step Description
Step 1 Patient attends the pharmacy.
Step 2 The pharmacist identifies need to establish the patient’s medication history.
Step 3 The pharmacist accesses the pharmacy system to retrieve GP patient record history. The pharmacy system requests the GP patient record from GP Connect.
Step 4 GP Connect requests GP patient record from the GP clinical system.
Step 5

GP clinical system provides the GP patient record to GP Connect.

The GP patient record will include:

  • Allergies

    • Check if allergic to vaccination ingredients (example: egg)

  • Vaccinations (outside scope of current release)

    • Check vaccination has not already been given and not expired

  • Conditions/Problems (outside scope of current release)

    • Check the patient is not immunosuppressed as some vaccinations are unsafe

Step 6 GP Connect presents the GP patient record to the pharmacy system.
Step 7 The pharmacy system presents the GP patient record to the pharmacist.
Step 8 The pharmacist uses the information to assist in determining if the vaccination is safe and appropriate.

All content is available under the Open Government Licence v3.0, except where otherwise stated