Versions Compared

Old Version 24

changes.mady.by.user Joanne Crean

Saved on

compared with

New Version Current

changes.mady.by.user Joanne Crean

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel2
outlinefalse
stylenone
typelist
printablefalse

Overview

Backend development after ES Expand to display data types, starting with test results and measurementsFormatting the layout

  • Improving multi team user and patient registration process

    • Organisations can

    Q4 (Sep - Dec) 2023

    Q1 (Jan - March) 2024

    Q2 (April - June) 2024

    Currently working on

    Will work on next

    Later

    Advanced questionnaires

    Send/retrieve via FHIR APIs

    • View questionnaire in patient’s inbox

    • Search parameters supported for FHIR APIs

    • Rename Consultations to Questionnaires

    • Send advanced questionnaires from the UI to individual patients

    • Export advanced questionnaire responses from the UI

    • Edit completed questionnaires

    • Professionals and carers can answer questionnaires for patients

    • Patients can initiate a questionnaire

    GP data

    • Send questionnaires from the UI to all patients in a team

    • Improve screens for sending questionnaires - will include warning when sending to many patients

    • Improve screen for downloading questionnaire responses

    • Patients can initiate an advanced questionnaire

    • Edit completed questionnaires

    • Professionals and carers can answer questionnaires for patients

    GP data

    • Mapping GP data to FHIR Resources

    • Development to display GP conditions, medications, allergies

    • Update our EMIS Extract Service integration following the latest EMIS ES schema changes

    • Go live with conditions, medications, appointments

    • in PKB UI after completing witness testing: EMIS

    • Web first, then TPP SystmOne.

    • Make more

    • GP data available via our FHIR API: immunisations, allergies, procedures, observations.

    • Link carers to patients

    • Make documents/letters available via FHIR API

    • Display more data from GP record in PKB record

    SMS support

    • Expand the phone number fields to allow users to add four distinct telephone number typesReferral letter triggers SMS invitation to register via NHS Login

      • development work

    • Referral letter triggers SMS invitation to register via NHS Login

      • go live

    • Questionnaire triggers SMS to patient

    • Appointment reminders sent via SMS (likely to continue to 2025)

    NHS App Wales

    • PKB in NHS App Wales

      • PKB core development completedNHS App development

    • PKB in NHS App Wales

      • NHS Login development

    • PKB in NHS App Wales

      • Whitelisting organisations to use NHS Login in Wales

    • PKB in NHS App Wales

      • Working with NHS Login to switch on for pilot organisation in Wales

    NHS App Wayfinder

    • Patients get NHS App message and corresponding push notification when they have a new or updated appointment in PKBWayfinder -

      • Backend work

    • Patients get NHS App message and corresponding push notification when they have a new or updated appointment in PKB

      • Go-live

    • Restrict appointment messaging to at least 72 hours before appointment time

    • Ensure Wayfinder appointment screens match the latest NHS App designs

    • Wayfinder - Patients can see when they have new documents on the Wayfinder screens

    Performance improvements and

    FHIR migration

    • Conditions. Medications, Appointments migrated and shown in UI

    APIs

    • Performance improvements and preparatory work required to onboard new customers

    • Allow patients to change privacy labels for data received via FHIR APIs.

    • Preparatory work required to onboard new customers

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

      • Documents meta-data

    • Make more data types available in aggregated FHIR store for extraction via FHIR API, e.g. immunisations, allergies, procedures.

    • Essential infrastructure improvements

    • Documents metadata migration

    • Observations (tests, measurements) migration 

    Plans

    • Plans Support break-the-glass for conditions, appointments, medications.

    Plans

    • Plans can have sections that cannot be edited by patients

    • Plans can be locked so that patients cannot edit them

    • Minor improvements to

    • Plans

    • display

    Email notifications

    • Patients can unsubscribe from email notifications that are not time sensitive

    • Organisations using our HL7 API to remove patients from teams can turn off email notifications about the discharge eventWe will address issues with demographic

    • Patients can unsubscribe from email notifications

    Identity and access management

    • One email address can be used for multiple roles

    • Registration improvements for administrative users (professionals, coordinators, organisations administrators, privacy officers)

    • Patients can give 3rd parties permission to pull a subset of their data from the aggregated FHIR store

    • that are not time sensitive

    • Email notifications about plans added to records via HL7 will be sent to unregistered patients

    • Fix issue causing demographic email notifications to be sent for metadata changes

    Identity and access management

    • Organisations can pull data for their patients from the PKB aggregated FHIR store via FHIR API

    • Patients can grant access to applications to pull their data from the PKB aggregated FHIR store via FHIR API

    • Improve patient registration process

    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.

    ...

    1.5 million patients already log in using NHS login and this number is increasing by 1000 patients each day. This integration lets us easily give these patients their GP data without the patient needing to supply additional information.

    This integration will initially be available initially for patients in England. 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. Some patients are already getting GP data Some patients in England are already 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 will de-duplicate GP data in a patient’s record if they are receiving it from more than one source.

    What are we building?

    ...

    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 get 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? 

    • EMIS will go-live first, then SystmOne.

    • Initially will show conditions, medications and appointments in the UI.

    • Will make other data types available via FHIR API: immunisations, allergies, procedures, observations.

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

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    ...

    Later

    ...

    • Backend development

    ...

    • Mapping GP data to FHIR Resources

    • Development to display GP conditions, medications, allergies

    ...

    Roadmap

    Currently working on

    Will work on next

    Later

    • Go live with conditions, medications, appointments in PKB UI after completing witness testing: EMIS ES Web first, then TPP SystmOne.

    • Expand to display Make more data types, starting with test results and measurementsGP data available via our FHIR API: immunisations, allergies, procedures, observations.

    • Link carers to patients

    Advanced questionnaires

    ...

    • Make documents/letters available via FHIR API

    • Display more data from GP record in PKB record

    Advanced questionnaires

    ...

    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.

    ...

    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 via FHIR API since Q4 2024.

      • Currently working on UI trigger and response retrieval.

    • Questionnaires can be edited after submission or completed by another user for the patient, e.g. carer.

    • Patient’s can initiate an online consultation with their team via a questionnaire.

    How are we rolling it out? 

    We’re introducing Advanced Questionnaires in phases so that teams can start using it as soon as the features they need are available.

    ...

    • sending and downloading responses from the PKB UI

      • Will support sending to individual patients first and then whole teams.

    • editing questionnaires after a patients submits

    • allowing patients to initiate an online consultation using a questionnaire

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

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    ...

    Later

    ...

    • Send questionnaires and pull responses via FHIR API

    • Registered and unregistered patients can answer questionnaires from their email notification

    ...

    Support search parameters for pulling responses via FHIR API

    ...

    Roadmap

    Currently working on

    Will work on next

    Later

    • Rename Consultations to Questionnaires

    • Send advanced questionnaires from the UI to individual patients

    • Export advanced questionnaire responses from the UI

    • Send questionnaires from the PKB UI

    • Download responses from the PKB UI

    • Edit questionnaires after they have been submittedto all patients in a team

    • Improve screens for sending questionnaires - will include warning when sending to many patients

    • Improve screen for downloading questionnaire responses

    • Patients can initiate an advanced questionnaire

    • Edit completed questionnaires

    • Professionals and carers can answer questionnaires for patientsPatients can ‘Start consultation’ to answer questionnaire

    Sending SMS notifications

    ...

    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 via SMS to increase their registration rates.

    What are we building?

    PKB will text patients encouraging them to register using NHS login when they get new data from their providers.

    The SMS service is run through gov.notify and organisations can decide if they want to use this pathway for notifications. All patients will continue to get email notifications. 

    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. 

    ...

    • referral letters

    • questionnaires

    • appointment reminders

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    ...

    Later

    ...

    • Expand the phone number fields to allow users to add four distinct telephone number types.

    Roadmap

    Currently working on

    Will work on next

    Later

    • Referral letter triggers SMS invitation to register via NHS Login

      • go live

    • Questionnaire triggers SMS to patient

    • Appointment reminders sent via SMS (likely to continue to 2025)

    NHS App Wales

    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 are we building?

    Patients will be able to navigate to their PKB record from the NHS App Wales. They can log in via NHS Login.

    ...

    This work will also allow patients in Wales to log in to PKB via NHS Login again.

    How are we rolling it out? 

    Once we have NHS Login approval to go live, we will switch it on for a pilot organisation.

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    ...

    Later

    ...

    Roadmap

    Currently working on

    Will work on next

    Later

    • PKB in NHS App Wales

      • PKB core development completedWhitelisting organisations to use NHS Login in Wales

    • PKB in NHS App Wales

      • Working with Whitelisting organisations to use NHS Login to switch on for pilot organisation in Wales

    NHS App England - Wayfinder notifications and messaging

    Why is this a priority?

    The NHS App is working with acute NHS Trusts to enable patients to securely view summary details of their referrals and scheduled appointments within the NHS App. If an organisation is taking part in this programme (Wayfinder), patients will find any upcoming appointments from that organisation in the NHS App in the Appointments section.

    The Wayfinder programme has set mandatory features for Patient Engagement Portals (PEPs) to continue participating in the programme. The first feature we’ll work on is sending patients push notifications and messages in the NHS App when they have new data.

    What are we building?

    When a patient gets a new or updated appointment. They will receive a push notification in the NHS app and will have a message in the NHS App telling them that a new appointment has been added.

    ...

    In the future, we will repeat this for other data that we add to the Wayfinder programme, for example documents and questionnaires.

    How are we rolling it out? 

    Once built and signed off by the Wayfinder team, we will roll out to a single trust as a First Of Type and then roll it out for the other organisations participating in the Wayfinder programme .

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    Roadmap

    Currently working on

    Will work on next

    Later

    • Patients get NHS App message and corresponding push notification when they have a new or updated appointment in PKBPatients get NHS App message and corresponding push notification

      • Go-live

    • Restrict appointment messaging to at least 72 hours before appointment time

    • Ensure Wayfinder appointment screens match the latest NHS App designs

    • Wayfinder - Patients can see when they have a new or updated appointment in PKBWayfinder documentsnew documents on the Wayfinder screens

    FHIR APIs

    Why is this a priority?

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

    What are we building?

    Organisations can already send their data as FHIR Resources to PKB. We are transitioning our system to a FHIR-native architecture, one datatype at a time. Once we have mapped, migrated and aggregated a data type it is available to view in our web application and our read-only FHIR API. 

    How are we rolling it out? 

    Conditions, medications and appointments have been migrated and can already be seen in our UI. 

    ...

    The remaining data types will be sequenced depending on customers’ abilities. We prioritise releasing the most data to the most patients.

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    ...

    Later

    ...

    • Conditions. Medications, Appointments migrated and shown in UI

    ...

    • Performance improvements and preparatory work required to onboard new customers

    ...

    Allow patients to change privacy labels for data received via FHIR APIs.

    ...

    Roadmap

    Currently working on

    Will work on next

    Later

    • Make more data types available in aggregated FHIR store for extraction via FHIR API, e.g. immunisations, allergies, procedures.

    • Essential infrastructure improvements

    • Documents metadata migration

    • Observations migration (tests, measurements) migration 

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

    Identity and Access Management (IAM)

    Why is this a priority?

    We want organisations and patients to be able to access their data via our APIs. To do this, we need to authenticate and authorise their usage.

    This work enables us to support scenarios that have been requested by users for a long time, e.g. various multi-factor authentication options, integration with other authentication systems like Active Directory, allowing multiple roles for the same person. Thus, it makes it easier for us to integrate with products that patients are already using to manage their health.

    What are we building?

    • Granular access control, e.g. patients can allow an app to have read-only access to certain data only

    • Multiple user roles

    • Improve multi-factor authentication (MFA) options

    How are we rolling it out? 

    We will be working this project iteratively starting with organisation-level access and then patient-level access to their own data. After that we will focus on organisations being able to access data.

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    ...

    Later

    ...

    • One email address can be used for multiple roles

    • Registration improvements for administrative users (professionals, organisations administrators, coordinators, privacy officers)

    ...

    • Continue registration improvements for administrative users

    ...

    • Patients can give 3rd parties permission to pull a all or a subset of their data from the aggregated FHIR store

    • Improving experience of multi-team users

    ...

    • Organisations can pull their data from the aggregated FHIR store

    • Improve patient registration

    Feature improvements

    Roadmap

    Currently working on

    Will work on next

    Later

    • Organisations can pull data for their patients from the PKB aggregated FHIR store via FHIR API

    • Patients can grant access to applications to pull their data from the PKB aggregated FHIR store via FHIR API

    • Improve patient registration process

    Feature improvements

    Throughout the year, we will continue to make minor improvements to the user interface for patients and professionals. These changes are planned regularly so we only plan three months ahead.

    What are we currently working on? 

    Plans

    Teams will be able to add sections to their plans that cannot be edited by patients. They will also have the option to lock plans so that they cannot be edited by patients.

    Email notifications

    Patients will be able to unsubscribe from email notifications that are not about time-sensitive information. We are aware that patients often find email notifications about demographic updates confusing so we are exploring solutions to improve their experience.

    When will this be available?

    ...

    Q4 2023

    ...

    Now (Q1 2024)

    ...

    Next (Q2 2024)

    Roadmap

    Currently working on

    Will work on next

    Later

    Plans

    • Plans can have sections that cannot be edited by patients

    • Plans can be locked so that patients cannot edit them

    • Formatting Minor improvements to the Plans layoutdisplay

    Email notifications

    • Patients can unsubscribe from email notifications that are not time sensitive

    • Organisations using our HL7 API to remove patients from teams can turn off email notifications about the discharge event

    • We will address issues with demographic email notificationsEmail notifications about plans added to records via HL7 will be sent to unregistered patients

    • Fix issue causing demographic email notifications to be sent for metadata changes

    Platform maintenance

    We dedicate engineering resources to platform maintenance to ensure the stability and reliability of our services. This includes ongoing updates, optimisations, and enhancements to our infrastructure to provide a seamless user experience. One goal that we are working towards is being able to release new versions of Patients Know Best without downtime for users and API customers. Additionally, we are prioritising security measures to safeguard our platform and protect user data from potential threats and vulnerabilities.