PKB Release Notes 25/02/2021
- Tim Whitlock (Deactivated)
Feature Updates
HL7 Messages - Email address handling
Previously, we only sent patient invitations to register when a first email address was added during record creation. We have updated this behaviour so that an email address provided in an HL7 message (A28 or A31) for an existing record will also add the email to the record and the patient will be sent an invitation to register.
Sharing
If a patient is in a team but not sharing any privacy labels with them, we have added some text on the sharing page to explain that the team can only see data they added.
Bug fixes
Alignment issue
We have fixed an alignment issue of sub menu tiles in patient view when the name of the tile had to split onto several lines.
Test results
We have resolved an issue where an HL7 ORU R01 lab result (http://dev.patientsknowbest.com/home/hl7-api/messages/oru-r01/laboratory) with a result that is declared to be textual was incorrectly displayed as as a numeric result.
Measurements
Self-registered patients now have the ability to add an individual professional via the ‘Sharing’ section.
HL7 messaging
We have resolved an issue where an HL7 message could be sent without a value in MSH-10 or MSH-11 field of the Message Header (http://dev.patientsknowbest.com/home/hl7-api/segments/msh), these are now mandatory fields.
HL7 Measurements, laboratory results and radiology reports
The OBX-11 field within HL7 ORU R01 messages is now mandatory, and additional validation has been added to ensure the correct code is sent through, for more information on this please visit http://dev.patientsknowbest.com/home/hl7-api/messages/oru-r01
HL7 radiology reports
The FON (Filler Order Number) is now mandatory when a radiology report is provided in an HL7 ORU R01 message.
HL7 laboratory results and radiology reports
Laboratory results and radiology reports which are sent via an HL7 ORU R01 message and contain more than one FON (Filler Order Number) will now be rejected.
HL7 laboratory reports
We have resolved an issue to ensure content in the NTE segment is displayed after the content of the OBX segment in HL7 ORU R01 messages which contain a multiline textual report in a single OBX.