/
Current Roadmap

Patients Know Best Resource Hub | Deploy | Developer | Trust Centre | Manual | Research | Education | Release Notes

Current Roadmap

Overview

This table summarises our current roadmap. It shows recently completed work, what we are working on now, what we will work on next and the projects that we are planning beyond that.

The "Later" column of the roadmap is for work that is planned but not yet fully defined. As our understanding grows and priorities shift (ours, customer-driven, or regulatory), the timing and scope of these projects may change. Projects are listed together but will be sequenced strategically, for example, when their dependencies have been completed. Their order of execution will be determined closer to their start date.

 

Q1 (Jan - March) 2026

Currently working on

Will work on next

Later

 

Q1 (Jan - March) 2026

Currently working on

Will work on next

Later

GP data

  • Update GP data feed after NHS ODS code API depreciation.

  • Support data deletions for patient requests to delete GP data

  • Essential enhancements to ensure we can scale smoothly as user demand increases.

  • Make more GP data available in aggregated FHIR store for API extraction:

    • Observations

      • Adding laboratory category to Tests

      • Tests - SystmOne html parsing

        • Data not previously structured so we needed to transform it.

  • Updates to consent screens.

  • Make more GP data available in aggregated FHIR store for API extraction:

    • Immunisations

    • Allergies

  • Data recategorisation

    • Procedures, Immunisations and Conditions categorised into the most appropriate FHIR resources

  • Display more data from GP record in PKB record

    • Will be done as part of FHIR data migrations. See FHIR sections below for more information on plan.

  • SystmOne past conditions categorised as Conditions

  • Observation classification

    • Add more categories to identify Observation type, e.g. Measurements.

  • Create Medication resource for referenced medications

  • GP Documents added to records.

  • Carer record via PFS (proxy access)

  • User interface refinement work:

    • Adding last updated information into the UI for users

    • Improving error messages

Advanced questionnaires

  • Carers can start an advanced questionnaire on behalf of a patient they care for

  • Questionnaires accessible in NHS App via Wayfinder (See Wayfinder below)

  • Support for archiving & assigning questionnaires

  • Performance improvements for organisations retrieving questionnaire responses

  • Refactor AQS so that its authentication & authorisation is unified with fhirwall

  • Follow-up work for patients initiating a questionnaire (start consultation)

  • Send advanced questionnaires to whole teams (mass questionnaires)

    • includes warning when sending to many patients

Order of work TBD, some of this may not be prioritised in 2026:

  • Remaining work to reach feature parity with simple questionnaires

    • Remind button

    • Support for privacy label changes

  • Bug fixes:

    • Multi-team profs cannot open responses

    • Inbox text not translated

    • Email notification will be sent for amendments made by a professional

    • CSV export does not contain groups

  • Further UX refinements:

    • link expiry/

      revoke questionnaires sent-in-error

    • questionnaire reminders

    • don’t allow questionnaires to be sent to deceased patients

  • Professionals can answer questionnaires for patients

  • Further work on editing questionnaires to show past versions

    • exploratory phase

Notification services, includes SMS support

  • NHS App notifications & messages (N&M) for PKB messages, Advanced Questionnaires & documents (See NHS App)

  • Appointment reminders via email notification

    • Emails will be sent 7 days and 2 days before the appointment

  • NHS App Wayfinder notifications & messsges for Advanced Questionnaires

  • SMS URL shortener to reduce SMS message length

  • Scoping work to transition to NHS Notify so that we understand

  • Appointment reminders via:

    • N&M

    • SMS - need to scope NHS Notify

  • Configuration options for SMS for advanced questionnaires:

    • Team-level config

    • Registered patients option

FHIR migration and API

  • Made more data types available in aggregated FHIR store for extraction via FHIR API

  • Data migrations to allow existing data to be extracted via FHIR API:

    • Introduced dry run process to let us test migrations before doing them.

    • Ready for migration:

      • Allergies

      • Journal

  • UI link-up to show data from aggregated FHIR store:

    • Adding Immunisations page to show patient immunisations sent via FHIR API

  • Data migrations to allow existing data to be extracted via FHIR API:

    • Observations - preparing:

      • Tests

  • UI link-up to show data from aggregated FHIR store:

    • Observations - Tests

  • Make more data types available in aggregated FHIR store for extraction via FHIR API

  • Support for patient creation via FHIR API.

  • Essential architecture changes to speed up data aggregation and prevent the queue from being blocked.

  • Data migrations continued

    • Prepare and migrate:

      • DocumentReference

      • Observations

        • Measurements

        • Symptoms

    • Migrate:

      • Allergies

      • Journal

  • UI link-up to show data from aggregated FHIR store:

    • Observations - Tests

      • continued

  • Data migrations continued

    • Prepare and migrate:

      • Observations

        • Measurements

        • Symptoms

        • Imaging

    • Plans

  • Validator for incoming data so customers can tell if their data is going to aggregate when sending to PKB

  • UI link-up to show data from aggregated FHIR store:

    • Symptoms, Tests, Measurements, Imaging, Documents, Allergies, Journal, Procedures(order tbd)

  • Support break-the-glass for conditions, appointments, medications in PKB UI.

  • Org network migration to FHIR.

FHIR API support for Documents

  • Set-up new document store.

    • Design work and project started.

  • Set-up new document store.

    • Includes backend work to end documents via Wayfinder for NHS App DQM screens (See NHS App)

  • DocumentReference migration

    • Migrate existing document metadata to FHIR

  • Migrate documents themselves and create link to them from DocumentReference

    • Build transformer

    • Build document URL and access

 

  • Support for GP documents

NHS App England

  • Uplift for PKB messages due to ‘Events and messages' jump-off removal:

    • NHS App notifications & messages (N&M) for PKB messages, Advanced Questionnaires & documents

  • Mobile optimisation for PKB Events & Messages screen

  • Questionnaires available via Wayfinder NHS App screens

  • Wayfinder N&M for Questionnaires

  • Wayfinder Inpatient & Daycase appointment uplift for Wayfinder

    • Includes adding encounter type to appointments

    • UI update to display appointment type

  • Wayfinder - Documents

    • UI link-up work to display document via Wayfinder NHS App DQM screens.

  • Wayfinder UI uplift

    • Mental health

    • Community appointments

    • Acute appointments

  • Wayfinder - Documents available via Wayfinder

    • Continued

  • Wayfinder N&M for Documents

  • Wayfinder MIV2 (Statistics reporting)

    • Scoping work

  • Wayfinder MIV2

    • Improve stats reporting for Wayfinder team

NHS Wales App

  • PKB in NHS Wales App

    • Live with first organisation

 

 

 

Population Health Management (PHM) Engine

  • Project work temporarily paused to prioritise NHS App Wayfinder integration.

  • Project work temporarily paused to prioritise NHS App Wayfinder integration.

  • Banner for medicines optimisation rules.

  • Other rule-based actions - tbd, e.g. plan added to record, message in inbox.

UI uplift work

  • Mobile optimisation for PKB Events & Messages screen

  • Improvements to the PDF viewer.

  • General accessibility improvements

  • Accessibility

    • Navigation update so that PKB can be used with a screen-reader.

    • Waiting on resources from Wayfinder work.

 

Other feature updates

  • Support for national identifiers to allow a national id to be selected for a team, instead of deducing it from the selected country.

  • Canada specific adaptations, for example removal of 'Add devices' button as this feature not supported.

  • Add new justification criteria for professionals accessing patient records to cover cases where they require access for investigations

  • Hide the "send message" for people who do not have a clinician that they can message.

  • Removal of legacy "discuss" buttons for patients

 

 

Identity and access management

  • Patients can authorise 3rd parties to read their data from the aggregated FHIR store

  • Patients can authorise 3rd parties to pull their data from the aggregated FHIR store

    • Adding support for multi-factor authentication

  • Patients can authorise apps via NHS login

  • Implementing streamlined autentication

  • Multi-factor authentication & UI uplift

  • Removing the need for patients to create PKB login details registering via NHS login

    • + Removing manual data entry for patients when registering via NHS login

  • Streamlining account linking for patients using third-party apps

  • Multi-factor authentication UI uplift

    • Continued

  • Support for federated access via the OpenID Connect (OIDC) protocol.

Order tbd:

  • Patients can write to their record via FHIR API

  • More granular permissions for 3rd party apps, e.g. only grant access to read certain data types.

  • Professionals can authorise 3rd parties to pull their data from the aggregated FHIR store

  • Unify integrations management so clients only need one set of credentials for REST-API, FHIR upstream, FHIR aggregator, FHIR facade.

Platform maintenance

 

  • No downtime releases

  • No downtime releases

 

Features

GP data for patients in England

Why is this a priority?

We want every patient to automatically have data from their GP in their PKB record.

Our integrations with EMIS Web and TPP SystmOne use NHS login to link a patient to their GP practice to retrieve their data. As soon as they log in with NHS login, they will have their GP data in their PKB record.

Over 3.5 million patients now have their GP data in their record via this integration. By using NHS Login, patients can easily get their GP data without needing to supply additional information.

This integration is currently available for patients in England. Some patients in England are also getting GP data added to their PKB record, or will get it from integrations set-up at an organisation level: EMIS Extract Service, North West London Data Discovery Service. These integrations will remain active. We de-duplicate GP data in the user interface for a patient’s record if they are receiving it from more than one source.

We would like to expand this to other countries once they have the national infrastructure in place to allow us to build something similar there. Patients in the Netherlands can already get their GP data in their PKB record as PKB is a certified personal health environment (PGO) in the Netherlands.

What have we built?

  • Integrating with EMIS Web and TPP SystmOne via the NHS IM1 programme.

  • Once a patient logs in with NHS login once, their record is pulled and then regularly updated from that point. No further action is required by the patient.

  • GP practice does not need to enable the integration with PKB, but does need to have online services enabled.

  • Will populate records with demographics, conditions, medications, allergies, appointments, test results, measurements, procedures, immunisations, documents & carer information/proxy records. Data types will be added in phases.

  • Data will be stored in FHIR format.

How are we rolling it out? 

  • We currently show conditions, medications and appointments in the UI.

  • We are working on making other data types available via FHIR API: observations, procedures, immunisations, and allergies.

  • Will then gradually add more data to the UI as we migrate those data types to FHIR or add new screens in PKB. 

Advanced Questionnaires

questionnaire branching.png

Why is this a priority?

Organisations use online questionnaires as a quick and convenient way to communicate with and gather information from their patients. Organisations can send questionnaires to large groups of patients, for example, to monitor waiting lists, or to individual patients to assess them pre-operation. Improving questionnaires has been our most common customer request for the last few years.

Unregistered patients can answer a questionnaire before registration and will have the option to register once they’ve submitted their answers, so sending questionnaires can also increase registration rates.

This project moves our questionnaires to FHIR storage so it contributes to our migration to a FHIR native architecture.

What are we building?

  • Questionnaires with an improved user experience and new features such as support for branching, scoring, capturing coded data, images.

    • Live since Q4 2023.

  • Advanced questionnaires can be sent to registered and unregistered patients. Unregistered patients can register with NHS login after completing the questionnaire.

    • Live since Q3 2024.

  • Questionnaires can be edited after submission

    • Live since Q4 2024.

    • Further work on this feature is currently being scoped.

  • Data from Questionnaires, e.g. coded scores, are aggregated and stored in other parts of the patients record. This will allow us to ultimately show the data in other parts of the record or use it as part of our patient activation work.

    • Available via API since Q1 2025.

    • UI depends on FHIR migration work for Observations.

  • Patients can initiate a questionnaire via start consultation.

    • Available since Q4 2025.

  • Questionnaires can be completed by another a carer.

    • Available since Q1 2026

  • Questionnaires can be sent to all patients in a team.

    • Starting after Wayfinder Questionnaires.

How are we rolling it out? 

Teams can move to advanced questionnaires now, once the features that they need have been developed.

You can read more about the Advanced Questionnaires roadmap and rollout in our wiki.

Sending notifications from our new notifications service

image-20250128-103602.png

Why is this a priority?

PKB notifications have been limited to email. SMS has been a priority for organisations because they often have more verified phone numbers than email addresses for their patients. Organisations can thus reach more patients using a combination of email and SMS to increase their registration rates.

What have we built?

Organisations can send an SMS to patients encouraging them to register when they get new data from their providers. They can also send notifications about new datapoints, such as Advanced Questionnaires. The SMS service is run through gov.notify and organisations can decide if they want to use this pathway for notifications. All patients with an email on record will continue to get email notifications as a fallback.

What are we building?

PKB will support appointment reminders, sent via email first, then Wayfinder Notifications & Messages and finally SMS.

How are we rolling it out? 

We added support for different phone number types so that we can store mobile phone numbers for patients to send SMS notifications to. 

Then we introduced SMS prompts for a patient to register when they receive new referral letters. We then added support for sending SMS notifications about new advanced questionnaires at an organisation level.

Next, will introduce email reminders about upcoming appointments.

Standardised data sharing (FHIR API)

Why is this a priority?

In order to achieve our mission of providing all patients with a copy of their data, PKB needs to enable partners and users to exchange data seamlessly. Our strategy to achieve this is to standardise on FHIR APIs.

What are we building?

We are transitioning our system to a FHIR-native architecture. Organisations can already send their data to customer-specific FHIR endpoints and retrieve that data via our aggregated FHIR endpoint. We are now mapping and migrating our existing data to FHIR and connecting our user interface to the aggregated FHIR database.This mapping, migrating and UI link up work is being done one datatype at a time. We are also filling in gaps around patient creation and retrieval that will allow our FHIR API customers to streamline their development process so that they do not need to use other PKB APIs to send and retrieve their patients' data via FHIR.

How are we rolling it out? 

When a customer wants to send new FHIR data, we are adding aggregation and retrieval support for that. Simultaneously, we are migrating our existing data, one datatype at a time. Once a data migration has happened, this data can be retrieved by via the FHIR aggregated store.

NHS App England

Why is this a priority?

The NHS App is working with acute NHS Trusts in England to enable patients to view their health data. Organisation can enable jump-off points from the NHS App to allow patients to view their PKB record. They can also enable PKB for the Wayfinder programme, allowing patients to securely view summary details of their scheduled appointments within the NHS App. PKB is supporting the NHS Apps work to ensure that patients accessing PKB from the NHS App will have an optimal user experience.

What are we building?

For the Wayfinder programme:

  • When a patient gets a new or updated appointment, they receive a message in the NHS app with an associated push notification, informing them of the appointment or update.

    • Complete

  • Appointments for patients from mental health organisations can be viewed via the Wayfinder screens

    • Complete

  • When a patient is sent an advanced questionnaire, they can access it via the Wayfinder screens

    • Complete

  • Wayfinder Notifications & Messaging for questionnaires

    • In Progress

  • Support for inpatient appointments by supporting encounter class with appointments

    • In Progress

  • When patients get a new document they can access it via the Wayfinder screens

    • In Progress

  • Update to our reporting capabilities for the programme

For organisations with PKB enabled in the NHS App:

  • Patients will get messages with associated push notifications in the NHS App when they have a new message, document or questionnaire in PKB. The contents of the NHS App message will link them to their PKB record.

    • In progress

How are we rolling it out? 

As each feature is ready, it will be trialled with one organisation before being made generally available. This project shares developers with the notification service and PHM work, so we will be alternating between projects.

NHS Wales App

Why is this a priority?

Over 50% of our users are logging in to PKB via the NHS App. NHS App is being used by 31 million people in England, and so it’s an important route for patients to access their PKB record. We want to continue working with the NHS App in other parts of the UK.

What have we built?

Patients can navigate to their PKB record from the NHS Wales App. They can log in via NHS login.

IMG_7404.jpg

This work will also allow patients in Wales to log in to PKB via NHS login if their trust has been approved to use NHS loginb by DHCW.

How are we rolling it out? 

This has been switched on for a pilot organisation. It can be extended to other organisations.

Population Health Management (PHM) engine

Why is this a priority?

This year, we are introducing automated actions that will allow organisations to reach their patients at scale and give them actionable steps they can take to manage their health.

Patient activation is about empowering patients to take an active role in managing their health and well-being. This concept is central to PKB's mission. For us, that means building a system that gives patients access to their health data, tools to take action, and educational resources.

Our initial focus was on access to health records, working with organisations and governments to integrate data from various healthcare providers, including hospitals, GP practices, into one record and on providing tools for patients to engage, such as questionnaires, care plans and symptom trackers.

We can now focus on automated actions and population health management as tools to personalise the patient experience. Organisations will be able to set rules to match patients, based on coded data in their records, and set actionable steps for those patients. Patients will see a prompt with the action in their record. This reduces the need for manual work by healthcare professionals and ensures that patients receive timely and relevant information. For example, a rule could be set to find patients who are eligible for a hospital’s clinical trial and those patients will be prompted to provide consent for the team to contact them about it.