🔔 The Next New Features Webinar is scheduled for the 12th June, from 12.30 pm
📅 We also offer a Weekly Refresher Training Webinar on Thursdays from 12.30 pm
To view and register for any session, please visit ➤ Patchs Upcoming Webinars & Training Sessions
Below are details of this month's new developments:
New Features
1. Cancel appointments from appointment reminders (EMIS)
EMIS practices will be pleased to hear that patients can now cancel their appointments directly from their email/SMS appointment reminder, making it quicker and easier and helping reduce DNAs. This brings the functionality into line with that already available for Patchs TPP practices.
| Email reminder |
SMS Reminder |
| Email Cancellation |
SMS Cancellation |
Cancellation links will be included for new appointment reminders by default and you can add cancellation links to your existing appointment reminders from the Appointment reminders and messages page.
SCREEN SHOT TO BE ADDED HERE
2. 🧭 Increased character limit for login and request limit messages
We know that some practices would like to add more information when patients login or are told that all the appointment slots are full. We have now extend these limits to make that easier.
Login Page message - now 500 characters
Request Limit messages - 300 characters
Bug Fixes
Edit patient details with shared NHS Number
This bug fix will allow staff users to edit patient details when NHS numbers are shared globally.
This addresses an issue that occurred when a non-digital record exists for a patient with an NHS Number and the patient registers for Patchs with a first name/last name/DOB that is different to the the non-digital record. The details provided by the patient are not recognized by the clinical system so:
- the the patient's newly registered account is not assigned an NHS Number
and - the non-digital record is not merged into the registered account.
Attempting to update the NHS Number on the registered account previously caused an error because the non-digital record is still unmerged and active.
This bug fix has resolved this issue.