...
...
Thursday 26th September 2024 |
|---|
Feature updates
1. QuestionnaireResponse endpoint supports national ID as a search parameter
Organisations can now search for QuestionnaireResponse resources using a patient’s national identifier in API calls to the QuestionnaireResponse endpoint. For an example API call, see our Advanced Questionnaires API spec.
2. FHIR MedicationStatement status display
MedicationStatements with an "unknown" status will now be displayed under current medicines in the user interface (UI). Previously MedicationStatements with a status of “unknown” would display under past medicines. For further information on FHIR MedicationStatements, see our developer wiki.
Coordinators can now reset MFA codes for patients in their team
When a coordinator resets the password for a patient with MFA enabled, their MFA credentials will also be reset. Previously, PKB Support had to assist with resetting MFA codes.
Bug fixes
1. Button display on 'Activated patients' screen
We have resolved an issue affecting the display of the action buttons on the coordinator’s ‘Activated patients’ page. These actions now correctly appear as disabled until a patient is selected using the radio button beside the patient. Once a patient is selected, available actions will show as enabled.
2. Error reminding patients to register if they had started to register via token registration
It is now possible to remind a patient to register if they are in the middle of the token registration process. Previously, if a patient had registered via token registration but not completed the last step to confirm their email address, a professional or coordinator could not remind them to register. Now, a professional or coordinator can send a reminder and then the patient can complete registration. The link they received to confirm their email for token registration will no longer be valid.
3. Credential synchronisation after password resets
We have resolved an issue that prevented users from accessing their data via NHS login or EMIS/SystmOne single sign-on (SSO) after a password reset by a team coordinator.
Wednesday 11th September 2024 |
|---|
Feature updates
1. Accessibility improvements to radio button and checkboxes
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.
2. Team professionals can lock plans
Team professionals can now lock plans, leaving them non-editable for patients and carers. When a professional has locked a plan, the patient and carer see a message telling them which professional and which team locked the plan and the ‘Edit’ button is greyed out. Plans can be unlocked by any team professional that has access to the plan.
...
Bug fixes
1. Error adding a patient to team via single sign-on
We have fixed an issue that prevented a professional accessing a patient record via single sign-on from adding that record to their team or breaking the glass to view the record.
2. Attaching files with no file extension to plans will not cause an error
Users can now attach files with no file extension to plans without that resulting in an error when saving the plan.
Tuesday 3rd September 2024 |
|---|
Feature updates
1. Privacy notice updates
...
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
1. Updates to placeholder & label text for phone numbers
...
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
1. Individual professionals can now send a message on behalf of patient to a team professional
...
Patients can now choose whether they want to receive email notifications about all new data added to their records or limit their notifications to time-sensitive changes only. These preferences can be managed from the ‘Profile’ page. All email notifications will include a link to manage email notification preferences. More information is available in the PKB manual.
Feature updates
1. Coordinator patient search controls
...
QRISK3 10 year cardiovascular disease risk score
QRISK3 healthy heart age
Bug fixes
1. Library upload limit set to 5GB
...
These measurements can be added via our HL7 API and tracked in a plan. In the next release, it will be possible to add and view these measurements in the Measurements section.
Feature updates
1. Questionnaire links now included in the response when sending a questionnaire via FHIR API
We now include a personalised questionnaire link in the ServiceRequest returned when an organisation sends a questionnaire to a patient via the $send-questionnaire-request endpoint. This is the same link that is added to the patient’s email notification. Organisations can send this link to patients using other communication methods, such as via SMS. To read more about this, see the advanced questionnaire API specification.
Bug fixes
1. Users can now edit privacy labels for data sent by partner organisations
...
The ‘Consultations’ page for professionals and coordinators is being renamed to ‘Questionnaires'. The ‘Start consultation’ button will now say ‘Send questionnaire’ and all references to ‘consultations’ in the professional and coordinator UI will now refer to ‘questionnaires’. Patients will still see a ‘Start consultation’ button in their record, as by initiating a questionnaire they are consulting their team online. You can read more about these changes and other upcoming changes in our blog post.
...
Bug fixes
1. Issue with phone number constraint preventing some users from registering
...