/
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 there 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.

 

Q2(July - Sep) 2025

Currently working on

Will work on next

Later

 

Q2(July - Sep) 2025

Currently working on

Will work on next

Later

GP data

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

  • Make documents available in aggregated store

    • Design work

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

  • Make documents/letters available in aggregated store

    • Set-up new document store.

      • This will be used for both documents that we will migrate from our existing database and for GP documents.

      • This set-up work will run until early 2026.

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

    • Observations (including Procedures and Diagnostic Reports)

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

    • Immunisations

    • Allergies

  • Make documents/ letters available in aggregated store

    • Pull GP documents and make available via FHIR API.

  • 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.

  • Data recategorisation

    • Ensure GP data are correctly categorised into the most appropriate FHIR resources.

  • Carer record via PFS (proxy access)

  • User interface refinement work:

    • Adding last updated information into the UI for users

    • Improving error messages

    • EMIS appointment booking updates to use same credentials

Population Health Management (PHM) Engine

  • Clinical trials banner live and shown on Inbox, Tests, Imaging, Medicines, Appointments

  • Changed button text on banner to ‘Choose what to share’

  • Project work temporarily paused for other projects until late 2025.

  • Banner for medicines optimisation rules.

Will not work on this until after Accessibility work.

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

Advanced questionnaires

  • Prof message shows as unread when the patient replies to a questionnaire.

  • Carers can answer questionnaires for patients.

  • Patients can initiate a questionnaire (start consultation)

    • Backend work done.

  • Support table view CSV export of responses (same format as existing simple questionnaires CSV).

  • Patients can initiate a questionnaire (start consultation)

    • User interface work and release

  • Patients can initiate a questionnaire (start consultation)

    • Support for profs in teams without team-based messaging enabled

    • Add option to set which questionnaires patients can start.

  • Carers can initiate questionnaires.

  • Remove limit (500) for the number of questionnaire responses that can be returned in CSV export or via FHIR API.

    • Will achieve this by supporting pagination.

This work won’t start until after the Wayfinder Questionnnaires project:

  • Email notification feature enhancement:

    • Multi-team profs can open questionnaire responses from email notifications

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

  • Send advanced questionnaires to whole teams (mass questionnaires)

    • includes warning when sending to many patients

  • 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

SMS support

  • Advanced questionnaire triggers SMS to patient

    • Works at org level

  • SMS URL shortener introduced to reduce SMS message length

  • Configuration options for SMS for advanced questionnaires:

    • Team-level config

    • Registered patients option

Won’t pick up until after Wayfinder MIV2 work:

  • Appointment reminders sent via SMS

NHS App England

  • Ensure Wayfinder appointment screens match the latest NHS App designs for mental health appointments.

    • Added appointment status.

  • Support for Single-Point-of-Contact

    • Lets organisations set a single-point-of-contact on their appointments

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

    • NHS App notifications & messages for PKB messages

    • Mobile optimisation for PKB Events & Messages screen

  • Questionnaires available via Wayfinder NHS App screens

  • Wayfinder MIV2

    • Improve stats reporting for Wayfinder team

  • Documents via Wayfinder NHS App screens

    • Dependent on Document store work & document migration

  • Add encounter type to appointments (inpatients etc)

NHS Wales App

  • PKB in NHS Wales App

    • Live with first organisation

  • PKB in NHS Wales App

    • Wider rollout

 

 

UI uplift work

 

 

Will not start until after the medicines optimisation banner work.

  • Accessibility

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

 

Other feature updates

  • Organisations can delete (and undelete) data from their integrations via the UI to correct errors.

    • Released team level configuration

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

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

  •  UI adaptations for Canadian users

FHIR migration and API

  • Made carer information available via FHIR 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

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

    • Observations - preparing:

      • Tests

      • Measurements

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

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

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

  • Data migrations continued

    • Prepare and migrate:

      • Observations

        • Symptoms

      • Documents

    • Migrate:

      • Allergies

      • Journal

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

    • Observations - Tests

  • Data migrations continued

    • Observations

      • Imaging

    • Plans

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

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

  • Essential architecture changes to speed up data aggregation and UI display.

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

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

  • Support for patient creation.

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

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

Order tbd:

  • Patients can write to their record via FHIR API

  • Patients can authorise apps via NHS login

  • Multi-factor authentication uplift

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

Becoming cloud agnostic

  • PKB can be deployed independent of a specific cloud service provider.

 

 

 

Platform maintenance

 

  • 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.

2.5 million patients already 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 - 337,042 patients, North West London Data Discovery Service - 2.4 million patients. These integrations will remain active. We de-duplicate GP data in 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 are we building?

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

  • Once a patient logs in with NHS login once, their record will be pulled and will be 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 demographics, conditions, medications, allergies, appointments, test results, measurements, 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.

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

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

Roadmap

Currently working on

Will work on next

Later

Currently working on

Will work on next

Later

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

  • Make documents/letters available in aggregated store

    • Set-up new document store.

      • This will be used for both documents that we will migrate from our existing database and for GP documents.

      • This set-up work will run until early 2026.

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

    • Observations (including Procedures and Diagnostic Reports)

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

    • Immunisations

    • Allergies

  • Make documents/letters available in aggregated store

    • Set-up new document store.

      • This will be used for both documents that we will migrate from our existing database and for GP documents.

      • Migrate existing documents (does not include docs from GP systems).

  • Make documents/ letters available in aggregated store

    • Pull GP documents and make available via FHIR API.

  • 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.

  • Data recategorisation

    • Ensure GP data are correctly categorised into the most appropriate FHIR resources.

  • Carer record via PFS (proxy access)

  • User interface refinement work:

    • Adding last updated information into the UI for users

    • Improving error messages

    • EMIS appointment booking updates to use same credentials

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 wellbeing. 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.

We have built the core rules engine so that we can create rules and now support clinical trial recruitment. We will gradually add support for other actions, such as prompting about medication reviews, and automatically adding care plans to records.

What are we building?

The first milestone for this project was letting organisations contact patients who are eligible for their clinical trials. After that we will expand the scope to include other types of rules.

How are we rolling it out?

Organisations can already reach eligible patients for their clinical trials. Next we will expand to other types of rules, such as medicines optimisation. Please speak to your account manager if you are interested to learn more about this work.

Currently working on

Will work on next

Later

Currently working on

Will work on next

Later

  • Project work temporarily paused for other projects until late 2025.

  • Banner for medicines optimisation rules.

Will not work on this until after Accessibility work.

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

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, for example 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.

    • In progress.

  • Questionnaires can be completed by another a carer.

    • Available for questionnaires sent to patients. Will next make available for patient-initiated questionnaires.

  • 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.

Roadmap

Currently working on

Will work on next

Later

  • Patients can initiate a questionnaire (start consultation)

    • User interface work and release

  • Patients can initiate a questionnaire (start consultation)

    • Support for profs in teams without team-based messaging enabled

    • Add option to set which questionnaires patients can start.

  • Carers can initiate questionnaires.

  • Remove limit (500) for the number of questionnaire responses that can be returned in CSV export or via FHIR API.

    • Will achieve this by supporting pagination.

This work won’t start until after the Wayfinder Questionnnaires project:

  • Email notification feature enhancement:

    • Multi-team profs can open questionnaire responses from email notifications

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

  • Send advanced questionnaires to whole teams (mass questionnaires)

    • includes warning when sending to many patients

  • Further UX refinements:

    • link expiry/

      revoke questionnaires sent-in-error

    • 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

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

    © Patients Know Best, Ltd. Registered in England and Wales Number: 6517382. VAT Number: GB 944 9739 67.

    This API specification and design is licensed under a Creative Commons Attribution 4.0 International License.