Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt
namereleaseNotes

Wednesday 28th Feb 2024

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.

Wednesday 21st Feb 2024

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

Thursday 8th Feb 2024

Feature updates

1. Contact details CSV now includes all phone number types

...

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

...

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

...

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

...

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

...

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.

...