...

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

...

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

...

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

...

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

...

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.

...