Below is the roadmap for  2019, updated January 2019. (Click to see the previous version). As usual, we adjusted priorities in response to the feedback of early adopter customers and we dug deeper into the details of each feature. 

The feature category of the PKB blog has details on the features we've released. The PKB blog also has archives of past roadmap postings

For questions about any of the features below please contact us. And if you are a developer, we're hiring!

Our developers' work is in four different streams:

  1. tighter integration with General Practice electronic health records software
  2. onboarding more professionals more quickly
  3. modernising our user interface and its underlying programming interface
  4. security improvements across the system

The picture below shows these improvements graphically (printable PDF here). You should interpret this as you do the London Underground map i.e. not for how close stations are to each other but a rough order of the stations in a line. So below we have not put down the delivery dates of individual features – some features take a lot longer than others – but a rough order of the order of features in a development stream. Security improvements are woven into every one of the other three streams.

GP EHR integ

By the end of 2018 PKB received data from GPs about more than 100,000 patients, and during 2019 we expect to receive millions of patients' records from GP systems. At the same time, health economies are switching from using PKB to show hospital data to showing all data from GP, hospital, and other institutions looking after the same patient. So PKB is investing heavily in GP integration, to show more data more quickly, and to allow transactions in PKB instead of GP portals.

One organisation sends data on behalf of many

At the moment any organisation can send its own data into PKB through the HL7 APIs. Imperial College Healthcare's Community cardiology and respiratory services send data from SystmOne into PKB using this HL7 API.

GPs can use this API to send data from their local CSV extracts. But GPs usually lack the IT resources to manage this.

Larger organisations working with the GPs – such as their local hospital or commissioning support unit – can do this work on behalf of the GPs. But sending each GP's data through a separate HL7 connection is burdensome.

The new HL7 API will allow aliasing, i.e. sending the data from multiple organisations in one connection, maintaining the source organisation information for each data point.

As PKB has gained regional contracts, including NHS Sustainability and Transformation Plan regions, Local Health and Care Record Exemplar areas, and national integrations, this functionality allows customers to send PKB more data more efficiently through centralised feeds.

Patient book GP appointment from PKB into EMIS

At the moment patients receive their hospital appointment information through the PKB HL7 API. Later in the year (see below) PKB will also show GP appointment information from EMIS.

Seeing appointments is one of the most popular features for patients. But patients also want to book appointments. And PKB's regional customers – using PKB as a true patient portal across GP and hospital – need the appointment booking to avoid using their GP portals and their hospital portals.

PKB and DrDoctor are completing their hospital appointment booking integration through the NHS Test Bed 2 programme in London.

The new GP appointment booking integration allows a patient logged into PKB to see available slots from their EMIS-using GP surgery, and then to directly choose and book. The patient can also change or cancel their GP appointments.

PKB imports EMIS data more quickly

At the moment PKB receives data about 300,000 patients from EMIS-using GP practices.

The data arrives overnight and PKB makes the data available through the user interface and the programming interface. PKB also notifies registered patients about the arrival of the new data from their GP. But in the next 12 months PKB's existing contracts mean 10x as much data will arrive. Furthermore, users in emergency departments want to see as much data as quickly as possible as they are work 24/7.

The improved EMIS import processing will show data more quickly. This through optimising data ingestion, skipping past data errors, and allowing processes to run on parallel servers.

PKB imports more EMIS data

At the moment PKB receives demograhics, diagnoses, medications and allergies about all patients in an EMIS-using General Practice.

The data arrives overnight and PKB makes the data available through the user interface and the programming interface. PKB also notifies registered patients about the arrival of the new data from their GP. But customers and patients want to see more data from EMIS.

The new EMIS import processing will show appointments, consultations, referrals, test results, immunisations, and symptom observations. The patient can book, change and cancel appointments (see above). And unlike the GP portal Patient Online which releases test results manually and on a patient-by-patient basis, PKB releases test results automatically and at scale. The real-time release of test results is one of the most popular features for patients, and the automation of results release frees up GP and receptionist time.

Unfortunately free text narrative in consultations and care plans is still not available because EMIS – like all GP EHR vendors – does not release these.

Professional onboarding

Professional clicks less and sees more

Organisation's software automates more tasks for more data through integration APIs

Third-party software checks patient registration status through HL7 A19 query

Third-party software deletes or updates documents through HL7

Organisation restricts professionals' access to NHS Health and Social Care Network IP addresses

Organisation newly treating patient automatically receives decryption keys from organisations already treating the patient

Interface modernisation

PKB's developers are upgrading our graphical user interface as well as the application programming interface (API) through which the GUI shows, adds and edits data from the patient's record. The new API complies with the new FHIR standard, and is more stable and secure. Most significantly, PKB is using this FHIR API to power the GUI, so third-party developers can rely on the same FHIR capabilities as PKB's developers are using themselves. We are excited about the possibilities of this for third-party developers and health economies to rely on the PKB record for openness and compliance with standards.

Professional sees an overview of the patient in the timeline view




Patient home screen

Professional home screen

Better email notifications to the patient

Security expansion

Mohammad Al-Ubaydli,
Feb 13, 2019, 9:37 PM