Roadmap

This page explains the current roadmap. (Click to see the previous version). This work aligns with our 2020-2023 product strategy. Our roadmap is reviewed monthly so that we can make sure we’re always building the right features for our users and customer organisations.

The roadmap is divided into the work that our development teams are currently working on and the work that scheduled to begin once the current projects have been completed. This is a living roadmap and will be updated when we have new plans to share.

Our prioritisation is guided by feedback from our customers. We also conduct user-research with our patient and professional users in order to continuously improve our platform for our users.

Subscribe to our blog to receive updates on what’s being released each month. The feature category of the PKB blog has details on the features we're releasing.

Now

Our development teams are currently working on the following functionality.

Integrations

NHS Login

Record creation and registration

A patient without a PKB record can create their PKB record and self-register using the NHS Login. Patients can use PKB to enter their own data without waiting for a health care provider to release data and see data about them as soon as a provider integrates with PKB.

Team-specific self-registration with NHS login

We are updating the team self-registration pages on our UK server with a button to register using NHS login. Patients will be able to use their NHS login to verify their identity and register for a PKB record. Unlike the main PKB web site’s NHS login registration, the team page links the patient to the team. Teams can use this for self-referrals, e.g. for maternity and physiotherapy teams working with patients whose identity has already been verified. This also allows private providers and charities to onboard patients with NHS login.

HL7 APIs

Add patient to new team

We are expanding our HL7 API to enable patients to be added to teams at any time. This will work for any organisation regardless of the organisation that created the patient’s record originally (our APIs had previously only supported adding patients to a team when creating their records). Institutions will be able to add patients to teams by adding the alias for the appropriate team(s) in the ZTM segment of A28 & A31 messages. More information can be found in our blog.

Send data on behalf of a virtual organisation

We will allow partners to send data on behalf of organisations that are not existing PKB customers. This will make it possible for patients to get data from their care providers, even if that care provider will not be

FHIR APIs

Demographics POST

Customers will be able to instruct PKB to create records via the FHIR API. If email addresses are included, patients will be invited to register. The spec for this API has been published.

NHS App

Download attachments

Patients using the NHS App to access their PKB record will be able to download attachments from the app. Currently, it’s not possible to view attachments in PKB from the NHS App.

EMIS extract service restart

PKB will be creating patients and receiving allergies, diagnoses and medications from GP practices using EMIS Web again. Additionally, patients attending a GP practice using EMIS Web will have details of the exact vaccine product they were administered in the 'Medicines' section of their record.

User-interface changes

Library uplift

We will be improving the user experience in the library section to make it easier for teams to set this up and maintain it for their patients.

Measurements

We will be using standard units when displaying measurement data. We’ve received feedback from customers that the measurement units from connected devices are not always optimal so we will ensure that standard units are used instead of the device’s default units.

We'll also be fixing an issue with how steps from Fitbit are displayed so that we use a cumulative daily total as opposed to displaying multiple data points each day.

Reporting

Weekly project report

We will be making a weekly project report available for customers. This report will allow customers to review the progress of their deployment workstreams. It will include data about creation, registration, clinical engagement, integrations and support desk metrics. On a weekly basis, organisations can see the change in figures for the last week, overall totals and a summary of the last three months.

This report will give organisations the information they need to support decision-making about actions that will help them to reach their goals. The report will also highlight the teams that are most successfully using PKB with their patients so that clinical teams can learn from each other to improve their processes.


Next

This section lists the next work-streams that our developers will focus on.

Integrations

Measurements from EMIS extract service

We will process a subset of measurements from the EMIS extract service. This means measurements taken at the GP practice will be available in a patient's record. We will publish more information about the exact measurements when work on the specifications is complete.

Vaccinations

A new 'Vaccinations' section will be added under the Health tab in PKB. Initially, this will include a patient’s vaccination history if their GP practice uses EMIS Web.

Our blog contains more information.

User-interface changes

Accessibility

Website navigation

PKB is committed to meeting WCAG standards. The first changes we will make will be to the navigation bar of the patient view. Our Accessibility Statement has been published in our user manual.


Care plan exports

We will be extending the care plan export functionality to allow a professional to initiate an export of care plan responses.

Adding data to records

Add tests

We're updating the 'Add tests' form to make it easier to select a test and add results for that test. Currently our form includes a panel of tests but the new form will allow single tests to be selected.

Add symptoms

The add symptoms page will have a drop-down list of symptoms so that the user no longer needs to scroll.