by Becky - 21st September 2022
The NHS EPR Usability Survey was first circulated in 2021, and was designed to collect the experiences of NHS staff across England. There has since been multiple versions focusing on different areas of healthcare. Our iaptus electronic patient record (EPR) was included in the first wave of the survey which was looking for feedback from NHS staff in mental health, community and ambulance settings.
Not so fast! Before we share our results with you, let us introduce ourselves and what it is we do to support NHS mental health services.
Mayden is a health tech company that creates insightful software, supporting healthcare services to deliver patient centred, outcome focused and data driven care. Over the last decade we have focussed on creating a flexible and customisable EPR, developing tools that help services run with efficiency and improve the patient experience.
I’m glad you asked! iaptus is our flexible and customisable EPR system that manages the care of patients across 100 NHS organisations, securely holding the records of over 6.5 million people.
iaptus supports physical and mental health services delivered by public, private and the voluntary sector, both here in the UK and internationally. In the UK, iaptus is the leading clinical software for psychological therapies, supporting over 65% of referrals to NHS talking therapy (IAPT) services.
So how did we do? Well firstly, the full results from the survey includes comparisons with global clinical systems, but for now we are just going to focus on the NHS.
We were pleased with our results for both reliability and speed but since the survey was conducted, we have continued to invest further in our infrastructure. iaptus has always been cloud hosted so we have always looked to take best advantage of modern technologies. We’ve recently moved iaptus to Amazon Web Services (AWS) and have noticed significant improvements in speed and performance as a result. We have also invested in new monitoring tools to help our technical teams optimise our system to continue improving performance.
We are always looking to improve the features and functionality of iaptus. We recently introduced online appointment booking and video consultation features within iaptus which are bringing significant benefits to services. For us to focus our energy in the right place, we will need more detail from customers about what new features would be helpful and which areas of the existing system could be improved. This will be an agenda item at our next user group.
We believe that safe, effective, high quality care is dependent on interoperability.
For that reason we prioritise projects that enable data flow between ourselves and other systems. We currently integrate with over 30 other clinical systems including Rio, SilverCloud, Wysa and Healthcare Gateway. Our team also continues to work with groups seeking to improve interoperability on a national level. Based on this feedback, and to improve in this area, we have already set ambitious targets to serve iaptus data into Local Care Records across England. We will also need to gather more feedback from customers about the system integrations that they’d like us to prioritise. This will be a workshop session at our next user group.
This is the area that, based on this survey feedback, we are most keen to improve. Following feedback from user meetings, we have already improved flagging for digital referrals. Incorporating coloured alert flags into iaptus to indicate risk and clinical safety information provided by external referral applications. We will continue to work with our customers to find additional ways to support care with alerts.
This was feedback that made our team really proud. We have invested heavily in user experience, with dedicated UX specialists embedded in our development team. We have designed iaptus and developed tools and processes which means training typically takes just one day. That said, we are still keen to improve and will continue to adopt UX best practice whenever possible. We are also currently scoping improvements to our customer help site to support both initial training and ongoing system use for customers.
We believe that great things happen when we collaborate with others, and are open about our strengths and where we need to improve. Our customers took the time to give us valuable feedback, and sharing that keeps us all accountable and working together to achieve a common goal –
improving patient care.
The Old Dairy,
Melcome Road, Bath BA2 3LR
Telephone 01249 701100
iaptus® and Mayden® are registered trademarks of Mayden.
Cookie | Duration | Description |
---|---|---|
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 1 year | The GDPR Cookie Consent plugin sets the cookie to store whether or not the user has consented to use cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
hid | session | No description available. |
tableau_locale | session | No description available. |
VISITOR_PRIVACY_METADATA | 5 months 27 days | Description is currently not available. |
_hjIncludedInSessionSample_3201 | 2 minutes | Description is currently not available. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies store information about how the user uses the website to present them with relevant ads according to the user profile. |
test_cookie | 15 minutes | doubleclick.net sets this cookie to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gat_UA-* | 1 minute | Google Analytics sets this cookie for user behaviour tracking. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gcl_au | 3 months | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores the true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjRecordingEnabled | never | Hotjar sets this cookie when a Recording starts and is read when the recording module is initialized, to see if the user is already in a recording in a particular session. |
_hjRecordingLastActivity | never | Hotjar sets this cookie when a user recording starts and when data is sent through the WebSocket. |
_hjSessionUser_* | 1 year | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
_hjSession_* | 30 minutes | Hotjar sets this cookie to ensure data from subsequent visits to the same site is attributed to the same user ID, which persists in the Hotjar User ID, which is unique to that site. |
Cookie | Duration | Description |
---|---|---|
tableau_public_negotiated_locale | session | Tableau sets this cookie in context with the language settings on the website. Facilitates the translation into the preferred language of the visitor. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect a user's first pageview session, which is a True/False flag set by the cookie. |
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |