All Collections
Phonebar
Advanced Tips
Technical Specifications - Phonebar
Technical Specifications - Phonebar

Technical Information for IT Teams.

Updated over a week ago

How it works

The Phonebar links the core telephony platform to the clinical system making the day to day use of the phone system much more efficient

Inbound calling patients will be identified before the call is answered, their patient record can be opened in the clinical system with a single click

Outbound calling and SMS from the active patient record is also present as well as filing of multiple communications directly to the patient record

Clinical Integration

The Phonebar communicates with the clinical system platform through their secure integration API

The clinical system will respond back to the application with patient information. It will then provide the on screen functionality to make communication with the patient quicker and more efficient

Accreditations and Data Security

  • ISO 27001

  • NHS DSP Toolkit

  • Business Continuity Disaster Plan

  • X-on DPIA

  • Clinical Safety System and Officer in place

  • Annual security/penetration testing

  • NHS IM1 programme assurance/SCAL

  • DCB 0129

Application Integration

The Phonebar is installed on each PC that wants to make use of the integration

When our platform targets a phone call at a telephone within the practice, we also send information to the application on the associated PC over HTTPS

The application will then use the secure API to gather data from the clinical system and display notifications on the PC screen about the person calling in

User Access

The integration features are accessed only when a valid staff login to the clinical system is detected, this then allows our application to retrieve minimal patient data from the clinical system via the accredited partner API

The app does not access any data without an authenticated clinical system user being present

Communication

All communication data is stored on X-on's cloud platform which is a set of 3 data centres (Tier 3 ) for maximum redundancy and resilience

For different activities our application will be notified of the event e.g. a new incoming phone call

This will then trigger the application on the surgery PC to call the clinical system API in order to retrieve further information. Some of this information e.g. a patient's name and date of birth, will immediately be displayed within the desktop application

Installation

Installation can take place either using a Regular installer for individual PCs and Laptops or via Group Policy using an MSI installer

Updates

The web based monitoring, reporting and management portals are, by nature, updated centrally in the cloud with no activity on the practice network or PCs

The integration software is updated periodically. It will check for updates itself and update automatically with no practice staff or engineer input

Minimum System requirements:

For the latest Desktop application we recommend Windows 10, i3 processor as a minimum, 4Gb RAM, 2GB disk space. The application will work on any screen resolution and in normal operational bandwidth

A Softphone voice call uses around 30kbps in bandwidth and a video call uses around  4Mbps is recommended

When a PC receives an upgrade

Provided a version of Surgery Connect is installed X-on can upgrade remotely at any time, the PC/PCs in question need to be restarted for the update to take effect

When a new PC or laptop is introduced Surgery Connect will need to be installed. For a whole surgery use the MSI Installer and for an individual PC or laptop use the Regular Installer. Admin rights will be required to download the file

See our Installation Guides

Did this answer your question?