Wednesday 5th June 2024

Feature updates

1. New document type: 'Referral acknowledgement letter'

We have added 'Referral acknowledgement letter' to the list of supported document types. Documents can be sent to PKB in an HL7 MDM T02 message.

2. Source info will now show the entered date (MSH-7) for all data types

The source info popup will now show the entered date (MSH-7) for all data sent via our HL7 API. Previously, the date that the data point was processed (i.e. the persisted date) was shown for some data types.

3. No email notifications will be sent for documents older than 7 days

Patients will no longer receive email notifications when a document is sent to them via an HL7 MDM T02 message if the document timestamp (TXA-4.1) is older than 7 days. For more information please see What notifications do patients receive? and MDM T02: Send a document.

Feature updates

1. QuestionnaireResponse endpoint now supports date range

The advanced questionnaires QuestionnaireResponse endpoint now supports date ranges using the authored search parameter. This allows users to return all QuestionnaireResponses that were completed between two dates.

Instructions for how to structure these searches can be found in our dev wiki.

Feature updates

1. Multi-factor authentication for all user types

We now support multi-factor authentication (MFA) for all user types, including privileged users such as coordinators. Users can enable or disable additional MFA via the ‘Authenticator’ tab on the ‘Profile’ page. For more information please see our manual.

2. HL7 ZTM-2 acknowledgement responses

A meaningful error response (AR) will now be returned when a ZTM-2 segment contains an alias for a team that doesn’t exist. ZTM-2 segments containing an alias for a team that the patient is not currently in are now accepted.

3. Advanced questionnaires - Canonical URLs

QuestionnaireResponse resources generated from advanced questionnaires will now contain a canonical URL in the questionnaire field. This canonical URL is a version-specific identifier for the Questionnaire that the QuestionnaireResponse was generated from. Organisations will use this to determine which version of a Questionnaire a set of answers relates to.

Bug fixes

1. Consent walkthrough for patients in the Netherlands

Patients in the Netherlands will now be taken through the consent pages on their first login after setting up 2FA. This means that teams can now use advanced consent questions.

2. Rejection of invalid PKB ID when creating a patient HL7 API

We have resolved an issue when creating a new patient via our HL7 ADT A28 endpoint if an invalid PKB ID is included in the PID segment, this will now be rejected with the following response 'A patient with the provided PKB ID could not be found.'

3. HL7 ZTM soft-matching

We have resolved an issue which prevented existing patients from being added to / discharged from teams when there is a mismatch in soft-matching. Patients will now be added to / discharged from the team(s) provided in the ZTM segment.

4. Error inviting team professional as individual professional

We have fixed an issue where there was a page crash if a patient invited a team professional as an individual professional when the professional already had access to their record as both a professional and a coordinator on one of their teams. Now the patient will see a message telling them that the professional already has access to their record as a team professional.

Technical improvements

1. We have made performance improvements for coordinators downloading patient contact details. For more information please see download contact details.

Feature updates

1. Link to view record has been added to the discharge email notification

Discharge email notifications, which are sent when patients are discharged from a team, now contain a link for the patient to log in and view their previous teams on the ‘Past invitations’ tab.

2. QuestionnaireResponse endpoint now supports the _include parameter

The advanced questionnaires QuestionnaireResponse endpoint now supports the _include search parameter. Organisations can use this to include the following in the response when retrieving QuestionnaireResponse resources:

• the Patient resource belonging to the patient that a questionnaire was sent to

• the Patient resource belonging to the patient who completed the questionnaire

• the ServiceRequest that was generated when the questionnaire was sent

Instructions for how to structure these searches can be found in our dev wiki.

Bug fixes

1. Reusing a deactivated professional’s email address

We have resolved an issue which prevented a deactivated professional’s email address from being reused when adding a new coordinator to a new team. After deactivation, the email can now be used.

2. Viewing measurements or plans containing measurements with multiple values

We have resolved an issue that prevented users from viewing measurements or plans containing measurements where a measurement has been sent with two values, but the measurement type only supports one value. These measurements will now be displayed with both values.

Bug fixes

1. ID conflicts in our FHIRstore

We are adding additional checks for ID conflicts in our FHIRstore.

Technical improvements

General performance and reliability improvements.

Feature updates

1. Advanced questionnaires FHIR API - Support for search parameters

The advanced questionnaires QuestionnaireResponse endpoint now supports search parameters. Organisations can search for QuestionnaireResponses for a specific patient, date, questionnaire, or whether the QuestionnaireResponse is completed or in progress. Instructions for how to structure these searches can be found in our dev wiki.

2. Configuration for email notifications when patients are discharged from a team

Organisations can now configure whether patients should be sent email notifications when discharged from teams via the HL7 remove from teams workflow. This is to support customer workflows where patients are added to and removed from teams for administrative purposes and it is therefore not appropriate for them to be informed that they have been discharged.

3. Plan export adhering to privacy label consent

Previously, team-professionals could export all data-points from a plan when the plan template belonged to their team. We have updated the plan exports so that the export will adhere to privacy label access and will only contain data that the professional has access to view in the User Interface.

4. Improved user flows when using password reset links

If a user is logged in to PKB and clicks on a reset password link from their email inbox, they are now taken to the PKB home page. Previously, the user could try to reset their password while logged in but would get an error. Users can still reset their password from the Profile section of their record while logged in.

Patients will now be taken to the login page if they use an expired reset password link. If the patient still needs to reset their password, they can click on 'Forgot Password' to trigger a new reset password link.

5. REST API Swagger documentation update

The Swagger documentation for updatedSince query parameters in the REST API that were documented as unsupported have now been removed from /v1/medications/active, /v1/medications/forPatient/id, /v1/medications/forPatient/id/active & /v2-beta/allergies/forPatient/id. The comment against /v2-beta/encounters/ for the updatedSince parameter has been updated to provide more detailed information.

Feature updates

1. FHIR registration endpoint - expanded national identifier support

The FHIR registration endpoint now supports any national identifier type from our list of supported national identifiers. Previously, this endpoint only accepted NHS numbers.

2. FHIR searching - UK national identifier support

FHIR API searching now supports any national identifier type from our list of supported national identifiers. Previously only NHS numbers were supported.
We additionally also support using non-national identifiers in FHIR searches.

3. Skype ID field removed

The Skype ID has been removed from the following locations:

• Profile page for all users

• Colleagues page for Professionals

• Registration page in all registration pathways

4. Advanced questionnaires - support for ‘additionalidentifier’ parameter

The $send-questionnaire-request operation now supports the ‘additionalIdentifier’ parameter, which organisations will use to send local identifiers when sending questionnaires. The value provided in the additionalIdentifier parameter is added as an identifier to the ServiceRequest that is generated when the questionnaire is sent. When the QuestionnaireResponse endpoint supports search parameters, this additionalIdentifier can be used to search for a QuestionnaireResponse.

For full history please see pkbstatus.com history