Connecting for Health National Clinical Leads Roadshow

1
Connecting for Health National Clinical Leads
Roadshow

• Effective Clinical Engagement
• Alan Hassey (Joint GP IT Committee)

2
GP2GP messaging project

• The General Practice to General Practice (GP2GP)
  patient health record transfer solution is
  required to support the electronic component of a
  general practice patient health record being
  transferred to a new practice when a patient
  registers with a new practice for primary health
  care.
• Deployment of GP2GP software to 478 practices
  planned by end March 2007

3
GP2GP v1.0 implementation

• Beyond Early Adopters
• 755 record transfers so far
• TATD Thu 19 Oct
• Emis rollout to 1st 50 practices this week
• Emis training started 23 Oct gt 300 by year end
• 1st Emis go-live 30 Oct
• 500 go-live (478 confirmed) by end March 2007
• Includes 60 InPS systems
• (future rollout will be v1.1)

4
GP2GP v1.1 implementation

• Software fixes underway
• DMS work with Emis InPS
• InPS TATD scheduled 30 Oct
• Emis TATD scheduled 20 Nov
• TPP hazard workshop 31 Oct
• Croydon interoperability pilot from 9 Nov
• 28 Nov go-live for InPS
• 6 Jan 2007 go-live for Emis
• Feb for InPS ltgt Emis exchanges

5
GP2GP Issues

• Max message size 5MB
• gt99 of messages within this limit
• Spine upgrade 2007 delayed (to Nov 07)
• Message size
• Message inter-operability
• Document management systems
• InPS gt testing Q1 2007
• Emis gt no date yet
• iSoft compliance testing ? March 2007

6
Common Assurance Process

• In February 2006, CfH setup the CAP Project with
  two main objectives.
• To refresh the NHS requirements for GP systems,
  previously published under the Requirements for
  Accreditation (RFA) scheme and
• Develop a unified assurance process to help
  improve the quality of IT systems delivered by
  existing suppliers to the NHS.
• Single process for testing/assurance to cover the
  three sets of requirements for GP computer
  systems (RFA, QOF and NCRS compliance). The new
  process will be used to support the assurance of
  solutions delivered by Existing Systems Providers
  (ESPs) and is called the Common Assurance Process
  (CAP)
• Key stakeholder support involvement

7
CAP-GP modules

• Common Assurance Process (CAP-GP)
• Core functionality
• Information governance
• Practice related organisations
• Patient demographics registration
• Patient scheduling
• Patient record management
• Analysis reporting facilities
• Legacy EDI
• Data Transfer Service (DTS)
• EDIFACT messages
• NHAIS links (IOS)
• Pathology reports
• The Module structure for GP systems requirements,
  supports the GPSoC scheme.

8
CAP future

• The CAP GP Procedure was approved at the CAP
  Steering Committee on 12th October for
• formal distribution to GPSoC Suppliers
• the basis for the CAP GP Phase 1 trial in support
  of the Summary Record Early Adopter Project
• The CAP team are now working with the GPSoC team
  to ensure a smooth transition from current
  processes to CAP GP for all Suppliers
• ESP CAP Generally
• ESP CAP will eventually be applicable for ESPs in
  all care settings. The CAP team are currently
  developing an implementation approach and plan to
  achieve this.
• The terms of reference of the CAP Steering
  Committee will be reviewed as part of this
  planning activity

9
Why we need CAP

• Implementing Policy
• carrot stick
• Data fit for sharing
• Single route to accredit systems for GPSoC
• Implementation of standards
• Snomed CT
• DMD
• DMS
• Level playing field for LSPs ESPs

10
Bringing it all together
11
CfH - useful links

• GP2GP
• http//www.connectingforhealth.nhs.uk/delivery/pro
  grammes/gp2gp
• GPSoC
• http//www.connectingforhealth.nhs.uk/gpsoc
• CAP-GP