Wednesday 20th March 2024

Feature updates

1. Updates to the ‘Manage profile’ screen

In preparation for adding four new phone number types to the ‘Manage profile’ screen next week, we have made some changes to the page. We have added a white background and now use new checkbox and radio components to align with our UI guidelines. Additionally, an "Address" subheading has been introduced to enhance navigation on the page, and the naming of the screen has been generalised as ‘Profile’.

2. Updates to the ‘Register patient’ screen

The register patient screen now uses the new checkbox component

3. Updates to Coordinator ‘To activate’ screen

We have removed phone numbers & Skype IDs from the ‘To activate’ Coordinator screen.

4. Updates to FHIR data from multiple sources

We have added a configurable option to prioritise certain sources of FHIR data over others, to aid in prevention of duplicated data from multiple sources.

Bug fixes

1. Issue inviting a deactivated team professional as a non-institutional professional

We have resolved an issue that previously prevented a patient from inviting a deactivated team professional as a non-institutional professional, when the professional had been deactivated from a team that the patient is part of.

Bug fixes

1. REST API - Multi-team professional issue granting access to 3rd Parties

We have fixed an issue that was preventing professionals in multiple teams from successfully granting access to 3rd-party systems via our REST API.

2. New error message for users trying to view a plan they do not have access to

We have resolved an issue which was causing professionals and carers to see an error page if they did not have the correct privacy label to view the plan when accessing a plan link that was shared by a patient via a message. We have now added an error message to notify the user why they cannot view the plan.

Feature updates

1. Patients can answer advanced questionnaires from their record

Patients can see advanced questionnaires that have been sent via the $send-questionnaire-request API in the ‘Events & messages’ section of their record. Patients can respond to new requests, continue with answers that they’ve saved, and view their answers to submitted questionnaires.

2. Non-institutional professional role

The non-institutional professional role is now separate from the team professional role. A professional will choose the relevant role from the team selector to find their patient list for each role. 

This means that:

• In the non-institutional professional role, a professional can search for patients they are caring for as an individual professional.

• In the team professional role, a professional can search for patients in that team or organisation.

• If a patient invites a team professional as a non-institutional professional, the patient will not be added to the professional’s clinical teams automatically. 

• If a team professional is deactivated from all of their teams, they will not automatically become a non-institutional professional. They will not be able to log into PKB until they are invited to a new team or invited as a non-institutional professional.

Bug fixes

1. Ordering of test results

We have fixed an issue that caused the order of test results to display from oldest to newest on the ‘View result’ page. We now display the newest results at the top.

2. Removing hyperlinks to sections not being tracked in plans

We have resolved an issue which caused the monitoring section in care plans to show hyperlinks to the tests, measurements and symptoms pages even when those items were not being tracked in the plan.

3. Advanced questionnaires can be answered when logged in

We have fixed an issue which caused a page crash when opening an advanced questionnaire from the notification email if the patient was logged in. Patients will now be taken straight to the questionnaire, without having to give their date of birth, when they click the link while logged in.

Feature updates

1. Removing the ‘Call patient’ feature

We have removed the 'Call patient' feature from the professional view as it had some usability issues and usage has been minimal.

2. Plans now always have hyperlinks to the data being monitored in a plan

If a plan tracks measurements, tests or symptoms in the monitoring section of a plan, we now show a hyperlink to go to the corresponding section of a patient’s record, regardless of whether data is stored for that data type.

3. Plan export columns updated

The ‘All’ and ‘Latest’ plan exports now contain the same columns.

Bug fixes

1. ‘All’ plan export now exports all plans

We have resolved an issue that meant the 'All' export would only show the latest set of answers in the plan for each patient. The 'All’ export now contains all versions of the selected plan template.

Technical improvements

We have made some performance improvements to reduce the loading time for test results.

Feature updates

1. Updating Access log to show entries for appointment, medication and diagnosis data.

We have updated the patient ‘Access log’ to display entries for when a professional views appointments, medications and diagnoses data in a patient’s record. These are the data types that have been retrieved from our FHIR store.

Bug fixes

1. Plan export ‘EnteredBy’ field now shows the user that entered the value in the plan 

We have resolved an issue that caused the ‘EnteredBy’ field to be set to “Not available”. The plan export ‘EnteredBy’ field now shows the user that entered the value in the care plan. For more information on care plan exports please see https://manual.patientsknowbest.com/professional/plans.

2. Removing unregistered professionals from appointment messaging

We have resolved an issue that caused team professionals who had not yet completed their registration to be included as recipients of their team’s appointment messages.

3. Performance improvements to prevent queues in processing FHIR data

We have implemented a fix to prevent infinite redelivering of messages in our aggregator when a dual practitioner ID is detected. This will prevent delays in processing and displaying FHIR data (appointments, diagnoses, medications).

Feature updates

1. Contact details CSV now includes all phone number types

When coordinators download the patient consent preferences on the ‘Consent’ tab, the CSV file now includes additional columns for mobile, work, home and other phone numbers as PKB now supports multiple phone number storage. We will be bringing the user interface inline with these changes in the next few weeks. You can read more about the upcoming changes to phone numbers in our recent blog https://blog.patientsknowbest.com/2024/02/02/support-for-multiple-phone-numbers/ .

2. Minor updates to the user interface when a deactivated professional is in a message thread

We have updated the deactivated professional warning shown when the deactivated professional is the only participant in the thread from red to orange to be in line with our warning style message. We have also changed the ‘Deactivated professional’ title in information pop-up to lower case.

Bug fixes

1. Page crashes no longer occur when there is an error deleting a diagnosis

We have resolved an issue that caused a page crash if an error occurred when a patient attempted to delete a diagnosis from their record. The patient will now be directed back to the Diagnoses page and will see an error message.

Bug fix

We have resolved an issue which prevented adding an existing registered institute user, such as a coordinator, to a new role.

New features

1. Care plans

When discussing a care plan with a professional or carer a link to the care plan will be automatically added to the ‘Message’ field.

Feature updates

1. ‘Add many patients’ CSV template

We have added new columns to the ‘Add many patients’ CSV template to allow coordinators to add phone numbers for their patients. We have added columns for each phone number type:

• Mobile number

• Home number

• Work number

• Other number

These phone numbers will be stored in PKB upon upload. We are finalising User Interface changes to display these stored numbers and this update is scheduled to go live in the next 2 weeks. You can access the new CSV template and read more about adding patient records via CSV on our manual.

2. FHIR API - Conditions

When both an abatement date and onset period end date are provided for Conditions sent via our FHIR API, the abatement date will be prioritised as the end (resolution) date. This complies with the FHIR R4 specification for Conditions.

3. FHIR API - Data route

A route is now displayed in the UI for data sent via our FHIR API. This is displayed as ‘Received via Integration (FHIR)’.

Bug fixes

1. Carer - patient ethnicity

We have resolved an issue to ensure that a carer can see the ethnicity on the patient summary and demographics page of the patient’s record.

2. Deactivated professionals

When deactivated from a team, professionals will no longer be able to see messages in their inbox that were sent to them from patients or professionals while they were in that team.

Bugs

1. Advanced questionnaires

We have fixed a bug that meant the team that sent an advanced questionnaire, via the $send-questionnaire-request operation, was not mapped to the generated FHIR QuestionnaireResponse resource. The team is now mapped to the ‘author’ field of the FHIR QuestionnaireResponse resource.

Feature updates

1. Advanced questionnaires - Privacy label

Clinical teams that trigger advanced questionnaires via the $send-questionnaire-request FHIR operation will now see their team’s privacy label on the ServiceRequest that is returned in the response.

2. Privacy Officer & Organisation Administrator update

Privacy Officers and Organisation Administrators can now link their account with other institution roles they hold on PKB. This allows them to use the same email address for each role. These users with multiple roles will now see a team selector in the top right of the header to switch role or team..

Bugs

1. Handling of multi-team professionals in FHIR store

We have resolved an issue that intermittently occurred when a professional role was assigned to multiple teams. The issue resulted in a blocking error that caused delays in processing new and updated appointment information from our FHIR store.

2. Granting access to REST API clients

We have resolved an issue for multi-role users granting access to REST API clients. Users with multiple roles in the same team can now grant access to REST API clients.

Feature updates

1. MedMij - data deletions

Patients in the Netherlands can delete data that they requested from their care providers. This is a mandatory requirement to comply with the MedMij standard. Previously, deletion was only supported for data that was sent to PKB via the HL7 API, as this was the only route that we received data for users in the Netherlands. We have now extended support for this feature to data sent to PKB via the FHIR API.

Bugs

1. Multi-team professionals - deactivation

We have fixed a bug that prevented professionals who were linked to multiple teams from accessing their patients if they had been deactivated from at least one of their teams.

2. FHIR API - time zone handling

We have fixed a bug with time zone handling for the FHIR API. Previously, if an organisation sent data via our FHIR API without specifying a time zone, the time shown for that data would be in the organisation’s default time zone. In this scenario, the time zone a user set in their record wasn’t being used. The time shown for these data points will now be determined by the time zone set in the user’s record.

Feature updates

1. REST API

We have made a number of technical improvements to creating or updating a professional via our REST API. This includes resolving an issue when inviting an existing professional.

2. Update to the ‘Latest’ view of test results

We have updated the display of test results, so that if multiple results of the same test type are received under different panel profiles, we now group and display the test type in a single section on the ‘Latest’ test result page.

3. Advanced questionnaires

Organisations can now send advanced questionnaires to patients using a national identifier (e.g. NHS number). Previously, patients could only be sent advanced questionnaires using the patient’s FHIR ID. See the advanced questionnaires API spec for an example API call using NHS number.

4. Advanced questionnaires

QuestionnaireResponse resources generated from advanced questionnaires now contain the public ID of the patient that completed the questionnaire.

Bugs

1. FHIR Demographic updates - Email address handling

We have added a missing check when email addresses are added to records via our FHIR demographic service. Previously, the system was not checking to see if the newly added email was already present on another record which could have prevented affected users from logging in, this change prevents the issue occurring.

For full history please see pkbstatus.com history