Thursday 8th Feb 2024

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

Tuesday 6th Feb 2024

Bug fix

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

Wednesday 31st Jan 2024

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.

Monday 29th Jan 2024

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.

Wednesday 24th Jan 2024

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.

Wednesday 17th Jan 2024

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.

Thursday 11th Jan 2024

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