Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Release notes (1).png

Thursday 10th October 2024

Feature updates

1. Supporting information text on test result pages

We have updated the text in the “Important' section of the test results page to include ‘The healthcare professional who requested the test will review these results and can discuss them with you at your next visit.’.

Screenshot 2024-10-04 at 16.15.49.png

2. Two-factor authentication usability improvement

If a user enters a two-factor authentication code from their authenticator application just after a new token has been generated, it will now be accepted. We extended the validity window to make it easier for users to manage their two-factor authentication. You can read about setting up two-factor authentication in our manual.

3. Advanced questionnaires can be added without a release

Advanced questionnaires can now be created, updated and linked to clinical teams without a PKB release. To arrange for an advanced questionnaire to be built or added to your team, speak with your Customer Success Project Manager.

4. Advanced questionnaire email notifications

Clinical teams using the $send-questionnaire-request operation can now suppress the email notifications sent to patients when a questionnaire request is sent. To suppress the email notification, the notificationFlag parameter can be added to the API call. For example API calls, see our advanced questionnaires API spec.

Bug fixes

1. Ampersand display on ‘View appointment’ page

We have resolved an issue that prevented the correct display of ampersands (&) in the appointment name within the navigation menu.

Screenshot 2024-10-07 at 16.00.41.png

2. Advanced questionnaires ‘author’ field now refers to the patient, not the sending team

The ‘author’ field on a QuestionnaireResponse now references the patient who completed the questionnaire, not the team that sent it. This fixes a discrepancy between our implementation and the spec for the FHIR QuestionnaireResponse resource.

  • No labels