GP Connect: retired

Retire the GP Connect Standard.

New Standard added, see Full Specification.

New Standard added, see Full Specification.

New Standard added, see Full Specification.

New Standard added, see Full Specification.

New Standard added, see Full Specification.

Patient Information Maintenance - GP: Epics E00179, E00180 and E00440 updated

E00179 - GP Connect - Access Record

As a Health or Care Professional

I want to enable access to Patient information for other Healthcare Organisations via GP Connect

So that Patient information can be accessed by other Healthcare Organisations

Acceptance criterion 1: provide access to GP Patient Information as a HTML view

Given there is Patient data to be shared for a Patient

When the Health or Care Professional at another Healthcare Organisation selects information from the Patient’s GP Record

Then the Patient information is displayed as a HTML view

Acceptance criterion 2: provide access to GP Patient Information relating to Medications and Allergies

Given there is Patient data to be shared for a Patient

When the Health or Care Professional at another Healthcare Organisation selects information from the Patient’s GP Record

Then the structured Medication and Allergies data for the Patient is displayed

E00180 - GP Connect Messaging - Send Document

As a Health or Care Professional 

I want to receive Patient consultation notes from other Healthcare Organisations

So that Patient consultation notes from other Healthcare Organisations can be stored in Electronic Patient Records (EPRs)

Acceptance criterion 1: view Patient Consultation Summary Reports sent via GP Connect Messaging

Given that Patient consultation notes have been sent to the Healthcare Organisation

When the Health or Care Professional selects to view a Patient’s consultation notes received via GP Connect Messaging

Then the Patient’s consultation notes are displayed

E00440 - GP Connect - Update Patient Record

As a Health or Care Professional

I want to receive structured clinical updates for Patients from other Healthcare Organisations

So that structured clinical updates from other Healthcare Organisations can be stored in Electronic Patient Records (EPRs)

Acceptance criterion 1: view received structured clinical updates

Given that structured clinical updates for a Patient have been sent to the Healthcare Organisation

When the Health or Care Professional selects to view the Electronic Patient Record (EPR)

Then the received Patient encounter information is displayed

And the received Patient observations are displayed

And the received Patient medications are displayed

Appointments Management - GP: E00226 updated

E00226 - GP Connect - Appointments Management

As a Health or Care Professional

I want to enable booking of Appointments for Patients at the GP Practice by other Healthcare Organisations via GP Connect

So that Appointments can be booked for Patients by other Healthcare Organisations

Acceptance criterion 1: share Appointment availability data with other Healthcare Organisations

Given the Health or Care Professional is permitted to manage Appointment availability data

When the Health or Care Professional selects to share Appointment availability data with other Healthcare Organisations using GP Connect

Then Appointment availability data is shared with other Healthcare Organisations

Acceptance criterion 2: Appointment booking at my GP Practice by other Healthcare Organisations

Given there is Appointment availability data to be shared with other Healthcare Organisations

When the Health or Care Professional at another Healthcare Organisation selects to book an Appointment at the GP Practice on behalf of a Patient using GP Connect

Then the Appointment is booked at the GP Practice

Cross-Organisation Appointment Booking: E00438 updated

E00438 - manage Appointments for Patients/Service Users at other Health or Care Organisations

As a Health or Care Professional

I want to manage Appointments for Patients/Service Users at other Health or Care Organisations

So that Patients/Service Users can access services provided by other Health or Care Organisations

Acceptance criterion 1: book Appointment for a Patient/Service User at another Health or Care Organisation

Given the Health or Care Professional is permitted to manage Appointments for Patients/Service Users at other Health or Care Organisations

When the Health or Care Professional selects to book an Appointment for a Patient/Service User at another Health or Care Organisation

Then the Appointment is booked for that Patient/Service User

Acceptance criterion 2: view Appointment for a Patient/Service User at another Health or Care Organisation

Given the Health or Care Professional is permitted to manage Appointments for Patients/Service Users at other Health or Care Organisations

When the Health or Care Professional selects to view an Appointment for a Patient/Service User at another Health or Care Organisation

Then the Appointment is displayed for that Patient/Service User

Acceptance criterion 3: amend Appointment for a Patient/Service User at another Health or Care Organisation

Given the Health or Care Professional is permitted to manage Appointments for Patients/Service Users at other Health or Care Organisations

When the Health or Care Professional selects to amend an Appointment for a Patient/Service User at another Health or Care Organisation

Then the Appointment is amended for that Patient/Service User

Acceptance criterion 4: cancel Appointment for a Patient/Service User at another Health or Care Organisation

Given the Health or Care Professional is permitted to manage Appointments for Patients/Service Users at other Health or Care Organisations

When the Health or Care Professional selects to cancel an Appointment for a Patient/Service User at another Health or Care Organisation

Then the Appointment is cancelled for that Patient/Service User

Interoperability Standard: updated

Capability-specific interoperability Standards

This section details the interoperability requirements which are associated with each Capability. 

Some interdependencies between individual interface Standards exist. Creating a compliant implementation requires implementing all the required dependent interface Standards, as detailed in the 'Dependencies' column.

Suppliers need to comply with all of the requirements that are associated with the Capability/Capabilities which the Supplier is offering. 

Foundation Capabilities

Patient Information Maintenance - GP

GP Connect Access Record API

• GP Connect Access Record HTML (Provider requirements)

• GP Connect Access Record Structured (Provider requirements)

• Personal Demographics Service (PDS) 

GP Connect Messaging Send Document

GP Connect Send Document (Receiver requirements)

• Generic FHIR Receiver

• Interoperability Toolkit (ITK) - ITK3 Messaging Distribution

• Messaging Exchange for Social Care and Health (MESH)

• Generic FHIR Receiver

GP Connect Update Record

GP Connect Update Record Standard (Receiver requirements)

• Interoperability Toolkit (ITK)

• Interoperability Toolkit (ITK) - ITK3 Messaging Distribution

• Messaging Exchange for Social Care and Health (MESH)

• Personal Demographics Service (PDS) * or Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.

Appointments Management - GP

GP Connect Appointments API

GP Connect Appointment Management (Provider requirements)

• Personal Demographics Service (PDS) *

Or 

• Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by PIM Solution, either via API to PIM Solution, or as a shared application resource if delivered as part of the same Solution.

• Personal Demographics Service (PDS) * or Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.

Capabilities to support new ways of working

Cross-organisation Appointment Booking

GP Connect (Appointments)

GP Connect Appointment Management (Consumer requirements)

• Personal Demographics Service (PDS) *

Or 

• Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by PIM Solution, either via API to PIM Solution, or as a shared application resource if delivered as part of the same Solution.

• Personal Demographics Service (PDS) * or Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.

Unified Care Record

GP Connect (Access Record) 

• GP Connect Access Record HTML (Consumer requirements)

• GP Connect Access Record Structured (Consumer requirements)

• Personal Demographics Service (PDS) *

Or 

• Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by PIM Solution, either via API to PIM Solution, or as a shared application resource if delivered as part of the same Solution.

• Personal Demographics Service (PDS) * or Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.

Medicines Optimisation

GP Connect (Access Record) (Medication FHIR Resources)

GP Connect Access Record Structured (Consumer requirements)

• Personal Demographics Service (PDS) * or Spine Mini Services

*May be sourced indirectly by existing PDS interface provided by a Patient Information Maintenance - GP Solution, either via API to this Solution, or as a shared application resource if delivered as part of the same Solution.