'Pairing integration' is the process that allows any supplier to integrate their system with any principal clinical system through an interface mechanism.
The four principal clinical system suppliers on the GPSoC framework are TPP SystmOne, EMIS Web, InPS Vision and Microtest Evolution.
Each must provide an 'interface mechanism' for use by 3rd party systems to support integration between the principal system and specialist applications, such as for document management or appointments.
Interface mechanisms enable separate systems to:
- read patient information
- extract information in bulk
- and enter data into the other system.
The interface mechanisms which Principal Clinical system suppliers provide under GPSoC must comply with the Authority Requirements. [535.85KB] .
Any supplier can apply to 'pair' their service with any principal clinical system.
To access the GPSoC Pairing Integration Process [394.38KB] , suppliers must first complete a PIQ entry form [2.51MB] . Suppliers must complete the GPSoC assurance process for each pairing.
The five stages of pairing integration and documentation related to each stage
The GPSoC Pairing Integration Supplier List [50.86KB] shows suppliers that have received approval to enter the pairing integration process, as at 26 January 2017.
The suppliers listed in the table below have been awarded the mid-way milestone, Permission to Engage (PTE), and are moving through the process towards the final milestone, Full Roll-out Approval (FRA). The following pairings should be completed in the coming months:
|Service or product||Provided by||Pairing with||Under Lot||Date awarded PTE||Date awarded FRA||Status|
|DocMan||PCTI||TPP||1||30 April 2015||To be confirmed||In testing|
|HealthShare Health Connect||Intersystems||Vision||3||10 August 2015||Expected May 2017||In testing|
|My RightCare v3||My RightCare||EMIS||None*||18 August 2015||23 November 2015||Live|
|My RightCare v3||My RightCare||TPP||None*||18 August 2015||19 August 2016||Live|
|eRA (eRefferal) Toolkit||Black Pear Software||TPP||2||19 August 2015||14 July 2016||Live|
|Medibooks||Total Billing Solutions||TPP||None*||26 August 2015||3 February 2016||Live|
|Audit+||Informatica (formerly BMJ)||EMIS||2||9 September 2015||Expected March 2017||In testing|
|SQL Suite||Apollo Medical||EMIS||2||5 October 2015||27 May 2016||Live|
|SQL Suite||Apollo Medical||TPP||2||11 November 2015||6 October 2016||Live|
|Enlighten E4||Jayex Technology Limited||TPP||None*||12 November 2015||27 July 2016||Live|
|i-Patient||PAERS||EMIS||1||13 November 2015||4 August 2016||Live|
|myGP (Patient Care Messaging)||iPlato||EMIS||1||13 November 2015||Expected March 2017||In testing|
|Clinical Support||MSD||EMIS||2||12 February 2016||To be confirmed||In testing|
|myGP (Patient Care Messaging)||iPlato||TPP||1||25 February 2016||To be confirmed||In testing|
|i-Patient||PAERS||TPP||1||25 February 2016||March 2017||Live|
|Ullman||Wiggly Amps||TPP||1||25 February 2016||March 2017||Live|
|SQL Suite||Apollo Medical||Vision||2||10 March 2016||Expected February 2017||In testing|
|Frontdesk||Informatica||EMIS||2||18 June 2015||Expected March 2017||In testing|
|Ullman||Wiggly Amps||EMIS||1||25 February 2016||Expected May 2017||On hold|
|i-Patient||PAERS||Vision||1||9 September 2016||Expected July 2017||In testing|
|Data Access Service||East London Discovery Project||EMIS||None*||13 October 2016||3 January 2017||Live|
|DIMEC||DIMEC App||EMIS||None*||24 October 2016||Expected February 2017||In testing|
* These services aren't available under the GPSoC Frameworks, so a separate contracting mechanism must be used.