...
Wednesday 6th Dec 2023
Bugs
1. Team selector
We have resolved an issue with the display of roles in the team selector affecting users who were both a professional and coordinator in the same team. It now correctly highlights the chosen role. For more info please see PKB Manual - Register as a professional.
Wednesday 29th Nov 2023
Feature updates
...
A new privacy label of ‘not set’ will be applied to incoming FHIR data upon aggregation where a privacy label is not provided and a privacy mapping doesn’t already exist. Data with a ‘not set’ privacy label will only be visible to the patient and users who have access to all other privacy labels (general, mental, sexual, social). Datapoints with a ‘not set’ privacy label will have no privacy label beside it in the UI for the moment.
...
Bugs
1. HL7 medications
We have resolved an issue where HL7 updates containing medications were being silently ignored if the provided frequency (in the ZRX1 field of an ADT A28 message) was unsupported. If an unsupported frequency is provided, the message will no longer be ignored and the provided string (e.g. “every 96 hours”) will be displayed in the UI.
...
Only a preview of a textual test result will be displayed in the notifications panel, where the full length value would spread over multiple lines. Previously, the full text was displayed.
...
Bugs
1. HL7 ADT A28 message processing
...
On the Plans page, if a coordinator or professional clicks to export 'All' plan responses, the resulting CSV now includes columns for primary email, Plan ID, and national ID type e.g. NHS number.
Bugs
1. Plans
We have resolved an issue that meant non-ASCII characters ( e.g. á) would show as '?' in the plan export. Non ASCII characters will now show in exported plans.
...
When calling the API
Medication.orderDate has been removed, along with ApiMedication.notedTimestamp
Calls to POST /v1/medications will continue to work if notedTimstamp has been provided; the value will be silently ignored
What is returned
notedTimestamp will no longer be returned from any API call
Bugs
1. Measurements
We have resolved an issue which meant that ‘Weight (kg)’ measurements over 100kg could not be recorded to the precision of 1 decimal point. Previously, these weights were being rounded to the nearest kg, but are now rounded to the nearest 0.1kg.