Search loading...


Explore and Make use of Nationally Defined Messaging APIs


Import patient record for a private hospital

Use case for import patient record for a private hospital

Brief description

Upon admission to or attendance at a private hospital it is necessary to record the patient’s current medications, allergies, diagnosis and conditions on the local clinical system. This is currently very difficult for private hospitals as they do not have access to NHS systems such as the Summary Care Record (SCR).

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 clinician.

Primary actors

  • Clinician
  • Hospital system
  • GP Connect
  • GP clinical system

Secondary actors

  • Patient


  • Patient is admitted to or attends a private hospital for treatment.


  • The patient’s details have been verified and entered on the hospital system upon admission/attendance.
  • Hospital staff have 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 hospital staff.
  • Electronic interactions between hospital system(s)/GP Connect/GP clinical system have been correctly configured.


  • On success:
    • Clinical information is imported and recorded against the local patient record.
  • Guaranteed:
    • A full history of medications, allergies, diagnosis and conditions is recorded on the hospital system.

Basic flow with alternative and exception flows

Step Description
Step 1 Patient attends/admitted to hospital.
Step 2 Clinician identifies need to establish the patient’s medication history.
Step 3 Clinician accesses the hospital system to retrieve GP patient record history. Cerner 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:

  • Medications

  • Allergies

  • Diagnosis

  • Conditions

Step 6 GP Connect presents the GP patient record to the hospital system.
Step 7 The hospital system saves a copy of the GP patient record directly.
Step 8 The hospital system presents an integrated view of GP patient record to the clinician for review with the patient.
Step 9 Clinician reviews and updates GP patient record with patient/patient proxy.

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