...
Excerpt | ||
---|---|---|
| ||
Feature updates
We have modified the text in the NHS services section of our Privacy notice in line with NHS England updates. See https://wiki.patientsknowbest.com/space/MAN/4062118010/Privacy+Notice+UK#NHS-services.
We have updated our input fields (such as radio buttons and checkboxes) and their corresponding labels to be closely aligned with proper padding and spacing. These updates ensure users can easily identify which label is associated with which input, improving the overall experience by making forms easier to read and interact with.
Patients using the appointment messaging feature can only request to cancel or modify an appointment 72 hours before the appointment.
We now display the full name of the user who created or edited a plan to eliminate any ambiguity.
We have modified the ‘Email notification preferences’ section on the Profile page to improve usability. These changes include updating the header for consistent styling and navigation with a screen reader. We have also added the word ‘events’ to the list of time-sensitive emails.
We removed the following lines from all email notifications sent to patients “For timely and important messages such as appointment changes we notify you immediately. You get at most one email per day about other new data added to your record.” We removed these lines as we now have an option to unsubscribe from email notifications that are not time-sensitive. New text was added to the footer as part of that change.
Advanced questionnaires can now be sent to patients with no email address in their record. These patients will see the questionnaire in their record and can complete it after they register.
Organisations can now delete medications via the Custom REST API using the DELETE endpoint. See our Swagger documentation for the specification of this endpoint. Bug fixes
We have resolved an issue which caused medicines that had been updated via the REST API with a patientOnMedication value of ‘false’ to be visible in the PKB UI. Medicines with a patientOnMedication value of ‘false’ will no longer be visible in the patient’s record.
We have resolved an issue which caused appointments to display out of order on the Appointments page. Upcoming appointments are now listed in ascending date order and past appointments are listed in descending date order. Appointments on the notifications panel are listed in order of last updated. |
...
New features
Image files of any type, e.g. png and jpeg can now be sent via a HL7 MDM T02 care plan message by setting the Data type (OBX-5.2) to ‘IMAGE’ and the Sub-data type (OBX-5.3) to an image file type e.g. ‘PNG’. The images are contained within the Action Plan section on the Plans page and can be both viewed and downloaded.
Audio files of any type, e.g. mp3 and m4a can now be sent via a HL7 MDM T02 care plan message by setting the Data type (OBX-5.2) to ‘AUDIO’ and the Sub-data type (OBX-5.3) to an audio file type e.g. ‘MP3’. The audio files are contained within the Action Plan section on the Plans page and can then be downloaded.
This new feature allows sections of care plan templates to be designated as exclusively editable by team professionals. When such templates are utilised, sections marked as non-editable can only be modified by team professionals, including those outside the specific team to which the plan belongs. Patients, carers, and individual professionals are restricted from editing these designated sections but can continue to update the rest of the plan. Feature updates
We have added placeholder text in the phone number fields on both the ‘Profile' page and the ‘Invite patient’ page. We have also updated labels on the phone number fields on the 'Invite patient’ page.
Unregistered patients will now get an email notification when a plan is added to their record or updated via the HL7 API. This behaviour already applies for plans added or updated via the PKB User Interface. Bug fixes
We have resolved an issue which prevented an individual professional sending a message on behalf of a patient to a professional who are part of a team.
We have fixed an issue which prevented phone numbers being extracted via the REST API if they were not marked as primary.
Previously, patients with no date of birth in their record would hit a page crash when attempting to open an advanced questionnaire request from an email notification. This is because patients have to provide their date of birth before answering the questions. Now, the patient will be shown an error message stating that they need to register before completing the questionnaire because their record has no date of birth. |
Thursday 8th August 2024 |
---|
Technical Improvements
...