In EMIS Web Clinical Services, Cross Organisation Appointment Booking and GP Connect Booking are two methods for booking appointments across organisations, but they differ in functionality, scope, and integration. Below is a detailed comparison of the two, including their pros and cons.
Cross Organisation Appointment Booking
Description
- Cross Organisation Appointment Booking is a feature within EMIS Web that allows organisations using EMIS Web to book appointments directly into each other’s systems.
- It is designed for organisations within the same shared EMIS Web ecosystem, such as GP practices, community services, or federations.
How it Works
- Organisations must have a data-sharing agreement in place.
- Appointments are booked directly into the EMIS Web system of the receiving organisation.
- Users can view and manage appointments in real time, provided they have the necessary permissions.
Pros
- Seamless Integration: Works natively within the EMIS Web ecosystem, ensuring smooth functionality and minimal setup for EMIS Web users.
- Real-Time Updates: Appointments are updated in real time, reducing the risk of double bookings or scheduling errors.
- Shared Records: If data-sharing agreements are in place, clinicians can access shared patient records, improving continuity of care.
- Customisation: Organisations can configure appointment slots to suit their needs and control access to specific services.
Cons
- Limited to EMIS Web Users: Only works between organisations using EMIS Web, limiting its applicability in mixed-system environments.
- Dependency on Data Sharing: Requires robust data-sharing agreements, which can be time-consuming to establish.
- Complex Permissions: Managing permissions and ensuring compliance with data protection regulations can be challenging.
- Scalability: May not be ideal for large-scale, national-level appointment booking.
GP Connect Booking
Description
- GP Connect Booking is a national NHS initiative that allows appointment booking across different clinical systems (e.g., EMIS Web, SystmOne, Vision).
- It is part of the GP Connect programme, which aims to improve interoperability between different healthcare systems.
How it Works
- GP Connect uses APIs to enable appointment booking between organisations, regardless of the clinical system they use.
- It is designed to support national programmes like NHS 111, extended access services, and vaccination clinics.
Pros
- Interoperability: Works across different clinical systems, making it ideal for mixed-system environments.
- National Scope: Supports large-scale initiatives like NHS 111 and vaccination programmes, enabling a unified approach to appointment booking.
- Standardised Approach: Uses NHS Digital’s GP Connect APIs, ensuring consistency and compliance with national standards.
- Improved Access: Patients can book appointments through services like NHS 111 or the NHS App, improving accessibility.
- Patient is automatically registered within the PCN hub upon being booked rather than having to be manually registered
Cons
- Complex Setup: Requires technical integration and configuration of GP Connect APIs, which can be resource-intensive.
- Additional Administrative steps to follow, including the setup of an organisational group within both the practice and PCN hub’s EMIS systems.
- Limited Customisation: Organisations have less control over how appointment slots are displayed and managed compared to Cross Organisation Booking.
- Smart Cards: The system also requires the user to be signed into the practice system using a smart card to complete a GP Connect Booking
- Reliance on National Infrastructure: Dependent on the availability and performance of GP Connect APIs, which may occasionally experience downtime.
- Data Access Limitations: While GP Connect allows appointment booking, it may not provide the same level of access to shared patient records as Cross Organisation Booking.
- ARRS Roles: Majority of ARRS Roles are not supported by GP Connect, and therefore cannot be used as Session Holders in EMIS Appointment Books
Key Differences
| Feature | Cross Organisation Appointment Booking | GP Connect Booking |
|---|---|---|
| System Compatibility | EMIS Web only | Works across multiple clinical systems (e.g., EMIS, SystmOne, Vision) |
| Scope | Local or regional | National |
| Integration | Native to EMIS Web | Requires GP Connect API setup |
| Data Sharing | Requires EMIS Web data-sharing agreements | Limited to appointment booking; patient record sharing may require additional setup |
| Use Cases | Federations, local shared services | NHS 111, vaccination clinics, extended access services |
| Customisation | High | Limited |
Which to Choose?
Cross Organisation Appointment Booking
- Best for organisations that are all using EMIS Web and have established data-sharing agreements.
- Ideal for local or regional collaborations, such as GP federations or community services.
GP Connect Booking
- At local level saves admin time and is more accurate (identifying correct patient)
- Best for organisations in mixed-system environments or those participating in national programmes.
- Ideal for large-scale initiatives like NHS 111 or vaccination clinics, where interoperability is critical.
Summary
- Cross Organisation Appointment Booking is more suitable for localised, EMIS Web-specific collaborations with a focus on shared records and real-time updates.
- GP Connect Booking is better for national or mixed-system environments, prioritising interoperability and accessibility over customisation.
The choice depends on the specific needs of the organisation, the systems in use, and the scale of the appointment booking requirements.
Digital PCN HUB Optimisation 