Knowledge base » Release Notes - epi-me » 2022/11/16 Release Notes epi-me (eAdmissions)
2022/11/16 Release Notes epi-me (eAdmissions)
Pease contact help@episoft.com.au if you would like any of these features activated in your epi-me portal.
NEW FEATURES
PATIENT PORTAL
Ability for patients to access a Frequently Asked Questions (FAQ) guide configured by their healthcare provider (EM-3013, Helpdesk #22669)
Healthcare providers can now configure a FAQ which patients can access from anywhere in the Patient Portal in the 'Footer' section.
Showing the location of the FAQ on the Patient Portal.
Each FAQ is designed as an 'expandible' so that the Patient User can reveal the answer to their question. The content of the answer is rich-text including support for HTML content eg. embedded videos, images and other media.
Sample FAQ (above)
If your team want this FAQs feature configured, please contact episoft on help@episoft.com.au. This has to be configured by Episoft's development team but can be done without a full software release.
Admin Portal Users with the 'Portal FAQs - Add/Edit' Role Right can maintain the questions and answers / content that appear on the FAQ page, once activated by Episoft.
Improve instructions for overseas patients entering a valid mobile phone number on Patient Portal registration (EM-1628, Helpdesk #11487 and #20596)
Patients registering on Episoft with international phone numbers now have helpful and dyanamic instruction text for the most common countries used in epi-me and clearer instructions on registration.
New Form Configuration to hide CPE question on Infection Screening page (EM-3055, Helpdesk #14352)
A new Form Configuration called HISTORY_INFECTION_SHOW_CPE has been added which allows healthcare providers to show / hide the following question 'Have you previously been infected or colonised with Carbapenem-resistant Enterobacteriaceae (CRE/CPE)? *' on the Infection Screening page.
ADMIN PORTAL
Ability for staff to generate eAdmission from Admin Portal (EM-1646)
EpiSoft have introduced a feature within the Admin Portal for healthcare provider staff to create admissions on behalf of patients. This was requested by one of our customers to ensure that patient data could be created securely on the patient's behalf if they had difficulty using eAdmissions, specifically for patients who required assistance or who did not have an email address.
Currently, the functionality is limited to Acute eAdmissions but we plan to expand this functionality to other patient cohorts in the future.
This functionality is restricted by a Role Right called 'Create New Admission (acute)'. See interactive tutorial on Role Rights.
Admin Portal Users with this Role Right can create new Acute eAdmissions directly from the Admission Worklist.
Selecting one of the available Admission Forms in this dropdown menu opens a new eAdmission form, very similar to what Patient Users see on the Patient Portal - but with a twist!
Patient Search is as per the same function for Internal eReferrals. Simply search for an existing patient (noting the Source and the Last updated) or create a New Patient.
Important! The available Patient Records are demarcated / partitioned by admitting facility - so if the Admin Portal User only has access to a particular facility/ies, they will also be restricted to viewing Patient Records which have admitted at those facilities.
Important! The new eAdmission will only be prepopulate / copied from a previously selected patient eAdmission if the previous was submitted by healthcare provider staff ("I" for Internal / Admin Portal).
Explaining the terminology 'Source' and some tips for finding the correct Patient Record.
The landing page after an admitting facility and patient has been selected.
One the admitting facility and patient has been selected, the eAdmission form process is unchanged other than:
1. Admin Portal Users cannot acknowledge any consents on the patient's behalf
2. Admin Portal Users are not required to validate their form submissions via SMS validation code.
Both these differences also apply to an Admin Portal User finishing off an eAdmission that a patient started from the Patient Portal.
Ability for staff to delete eAdmissions from the Patient Portal (EM-1724)
EpiSoft consistently receives a large number of requests from customers, particularly Maternity facilities, to remove eAdmissions from the Patient Portal. There are a variety of use-cases, including
1. Patient has submitted an eAdmission twice, and healthcare providers want to delete the duplicate.
2. Patient requests for admission to be deleted, citing privacy or cybersecurity concerns. With this use-case, the healthcare provider needs to ensure they have a backup of the patient's information (such as in the Patient Administration System) in accordance with the relevant privacy legislation (eg. retention of records for 7 years).
3. Patient Starts registration forms, but admission is cancelled before patient can complete forms. These users will receive reminder notifications to complete these forms unless the admission is completed or deleted.
4. Maternity Patients submits Admission + Health History forms, but has a miscarriage, and requests for the admission to be deleted so that they are not reminded and distressed when they access their Patient Portal account in future.
EpiSoft has now provided a means for healthcare provider staff to delete these eAdmissions themselves (without involving EpiSoft) from the Admission Worklist.
See interactive tutorial on How to delete an eAdmission from the Admin Portal.
There is also a related 'Deleted Admissions Report' which has been created to effectively audit which eAdmissions have been deleted, for what reason, and by whom.
An explanation of the data and function of the Deleted Admissions Report.
See interactive tutorial on running Reports which explains how to access and use reports in general.
Admin Portal Users can view what triggered a Clinical Alert on the Staff Clinical Alert Email PDF (EM-1729, Helpdesk #22552)
Previously, the Clinical Alert PDF report did not include the detail on what actually triggered a Clinical Alert - meaning healthcare provider staff needed to check the Alert Worklist on the Admin Portal to interrogate this detail.
To save staff time, we have now replicated the same clinical detail shown on the Alerts Worklist onto the PDF report.
Sample Staff Clinical Alert Email PDF.
Part of delivering this function also required significant enhancement to the Alert Worklist to display what triggered the various Clinical Alerts:
BUG FIXES
Clinical Alerts duplicating on Resubmit of eAdmissions (EM-1177)
When an eAdmission had clinical alerts and it is unsubmitted then re-submitted, it duplicated the clinical alerts rather than merging any identical alerts on the re-submit with previous submissions of that form.
This meant that Admin Portal Users had to close both copies of the alert in order to get them off the Alerts work list.
This has now been fixed.
Form Audit didn't display date in Australian format (EM-3927, Helpdesk #16398 and #18622)
The 'Form Audit' function previously displayed all dates in American format, i.e MM/DD/YYYY format.
A change has been made to display dates on the forms in Australian format - DD/MM/YYYY to avoid confusion.
Generic name of 2nd drug not displayed in Patient Portal for combination drugs (Allergies & Medications page) (EM-4853, Helpdesk #22219)
Previous to this fix, on the Medications lookup on the Allergies and Medications page if there were two names within a single drug line item for a composite drug on the MIMS search both drug names did not display. This was most common for composite drugs with a brand and generic name. The fix was applied to the database across all customers to ensure all relevant medication names displayed.
Message Templates - %%FirstName%% and %%LastName%% were populating with the Patient's name instead of the Accountholder's name (EM-4854, Helpdesk #21694)
This issue has now been fixed on all templates includinng 'Estimate of Fees Incomplete). The %%FirstName%% and %%LastName%% fields should always populate with the accountholders/user's name. The %%PatientFirstName%% and %%PatientLastName%% events should always populate with the patient’s name
Falls Risk Question and Response not appearing on the Health History PDF Printout (EM-5113, Helpdesk #22459)
Previously, the response to the question 'Have you had a fall in the last 12 months or do you fear falling or feel unsteady on your feet? *' was not displaying on the PDF printout.
This is now fixed.
Payment Gateway Change - Additional Fields
A minor change was made to track additional fields in the payment transaction log to cater for other customers using alternate payment gateways. This should have no impact on the use of current payment gateways.
NEW FEATURES
PATIENT PORTAL
Ability for patients to access a Frequently Asked Questions (FAQ) guide configured by their healthcare provider (EM-3013, Helpdesk #22669)
Healthcare providers can now configure a FAQ which patients can access from anywhere in the Patient Portal in the 'Footer' section.
Showing the location of the FAQ on the Patient Portal.
Each FAQ is designed as an 'expandible' so that the Patient User can reveal the answer to their question. The content of the answer is rich-text including support for HTML content eg. embedded videos, images and other media.
Sample FAQ (above)
If your team want this FAQs feature configured, please contact episoft on help@episoft.com.au. This has to be configured by Episoft's development team but can be done without a full software release.
Admin Portal Users with the 'Portal FAQs - Add/Edit' Role Right can maintain the questions and answers / content that appear on the FAQ page, once activated by Episoft.
Improve instructions for overseas patients entering a valid mobile phone number on Patient Portal registration (EM-1628, Helpdesk #11487 and #20596)
Patients registering on Episoft with international phone numbers now have helpful and dyanamic instruction text for the most common countries used in epi-me and clearer instructions on registration.
New Form Configuration to hide CPE question on Infection Screening page (EM-3055, Helpdesk #14352)
A new Form Configuration called HISTORY_INFECTION_SHOW_CPE has been added which allows healthcare providers to show / hide the following question 'Have you previously been infected or colonised with Carbapenem-resistant Enterobacteriaceae (CRE/CPE)? *' on the Infection Screening page.
ADMIN PORTAL
Ability for staff to generate eAdmission from Admin Portal (EM-1646)
EpiSoft have introduced a feature within the Admin Portal for healthcare provider staff to create admissions on behalf of patients. This was requested by one of our customers to ensure that patient data could be created securely on the patient's behalf if they had difficulty using eAdmissions, specifically for patients who required assistance or who did not have an email address.
Currently, the functionality is limited to Acute eAdmissions but we plan to expand this functionality to other patient cohorts in the future.
This functionality is restricted by a Role Right called 'Create New Admission (acute)'. See interactive tutorial on Role Rights.
Admin Portal Users with this Role Right can create new Acute eAdmissions directly from the Admission Worklist.
Selecting one of the available Admission Forms in this dropdown menu opens a new eAdmission form, very similar to what Patient Users see on the Patient Portal - but with a twist!
Patient Search is as per the same function for Internal eReferrals. Simply search for an existing patient (noting the Source and the Last updated) or create a New Patient.
Important! The available Patient Records are demarcated / partitioned by admitting facility - so if the Admin Portal User only has access to a particular facility/ies, they will also be restricted to viewing Patient Records which have admitted at those facilities.
Important! The new eAdmission will only be prepopulate / copied from a previously selected patient eAdmission if the previous was submitted by healthcare provider staff ("I" for Internal / Admin Portal).
Explaining the terminology 'Source' and some tips for finding the correct Patient Record.
The landing page after an admitting facility and patient has been selected.
One the admitting facility and patient has been selected, the eAdmission form process is unchanged other than:
1. Admin Portal Users cannot acknowledge any consents on the patient's behalf
2. Admin Portal Users are not required to validate their form submissions via SMS validation code.
Both these differences also apply to an Admin Portal User finishing off an eAdmission that a patient started from the Patient Portal.
Ability for staff to delete eAdmissions from the Patient Portal (EM-1724)
EpiSoft consistently receives a large number of requests from customers, particularly Maternity facilities, to remove eAdmissions from the Patient Portal. There are a variety of use-cases, including
1. Patient has submitted an eAdmission twice, and healthcare providers want to delete the duplicate.
2. Patient requests for admission to be deleted, citing privacy or cybersecurity concerns. With this use-case, the healthcare provider needs to ensure they have a backup of the patient's information (such as in the Patient Administration System) in accordance with the relevant privacy legislation (eg. retention of records for 7 years).
3. Patient Starts registration forms, but admission is cancelled before patient can complete forms. These users will receive reminder notifications to complete these forms unless the admission is completed or deleted.
4. Maternity Patients submits Admission + Health History forms, but has a miscarriage, and requests for the admission to be deleted so that they are not reminded and distressed when they access their Patient Portal account in future.
EpiSoft has now provided a means for healthcare provider staff to delete these eAdmissions themselves (without involving EpiSoft) from the Admission Worklist.
See interactive tutorial on How to delete an eAdmission from the Admin Portal.
There is also a related 'Deleted Admissions Report' which has been created to effectively audit which eAdmissions have been deleted, for what reason, and by whom.
An explanation of the data and function of the Deleted Admissions Report.
See interactive tutorial on running Reports which explains how to access and use reports in general.
Admin Portal Users can view what triggered a Clinical Alert on the Staff Clinical Alert Email PDF (EM-1729, Helpdesk #22552)
Previously, the Clinical Alert PDF report did not include the detail on what actually triggered a Clinical Alert - meaning healthcare provider staff needed to check the Alert Worklist on the Admin Portal to interrogate this detail.
To save staff time, we have now replicated the same clinical detail shown on the Alerts Worklist onto the PDF report.
Sample Staff Clinical Alert Email PDF.
Part of delivering this function also required significant enhancement to the Alert Worklist to display what triggered the various Clinical Alerts:
| Alert | Alert Text |
| 80 + years | Displays exact age in years |
| Any Allergies | Displays the entered allergies |
| Been Overseas/Interstate in past 12 months | Displays detail of overseas or interstate admission including location, reason and what type of facility |
| Blood and Bleeding Disorders | Displays the blood and bleeding disorders, and any provided detail |
| Blood clots | Displays location of blood clot, and any provided details |
| BMI < 18 | Displays the exact BMI |
| BMI > 35 | Displays the exact BMI |
| BMI > 40 | Displays the exact BMI |
| Cancer | Displays cancer diagnosis date, location of cancer and whether treatment is current or complete. |
| Cardiac | Displays what question triggered the alert |
| Chronic pain | Displays patient specified detail about chronic pain |
| Cognitive risk (>65 years or memory loss) | Displays questions which triggered the alert. |
| COVID | Includes COVID-like symptoms, diagnosis date, close contact in past 7 days |
| Diabetic | Displays diabetes type and how it is managed. |
| Discuss needs before admission | Displays preferred contact number |
| Falls risk | Displays whether fallen in last 12 months, and how many times. |
| Infection risk | Displays questions which triggered the alert eg. CJD, MRO, travel to infectious areas. |
| Latex allergy | Displays reaction to latex (if applicable). |
| Nutritional risk | |
| Nutritional risk (weight loss > 5kg) | Displays what triggered the alert. |
| Polypharmacy (>= 5 medications) | |
| Previous anaesthetic problem/s | Displays detail of self or blood-relative malignant hyperthermia (where and when), as well as self or blood-relative anaesthetic reactions or problems (who and short description) |
| Skin Integrity | Displays skin problems and description of skin ulcer, bladder or kidney issues, as well as describes any impairment of general mobility or impairment of mobility caused by respiratory issues. |
| Weight > 100 kg | Displays exact weight (kg) |
| Weight > 120 kg | Displays exact weight (kg) |
| Weight > 130 kg | Displays exact weight (kg) |
BUG FIXES
Clinical Alerts duplicating on Resubmit of eAdmissions (EM-1177)
When an eAdmission had clinical alerts and it is unsubmitted then re-submitted, it duplicated the clinical alerts rather than merging any identical alerts on the re-submit with previous submissions of that form.
This meant that Admin Portal Users had to close both copies of the alert in order to get them off the Alerts work list.
This has now been fixed.
Form Audit didn't display date in Australian format (EM-3927, Helpdesk #16398 and #18622)
The 'Form Audit' function previously displayed all dates in American format, i.e MM/DD/YYYY format.
A change has been made to display dates on the forms in Australian format - DD/MM/YYYY to avoid confusion.
Generic name of 2nd drug not displayed in Patient Portal for combination drugs (Allergies & Medications page) (EM-4853, Helpdesk #22219)
Previous to this fix, on the Medications lookup on the Allergies and Medications page if there were two names within a single drug line item for a composite drug on the MIMS search both drug names did not display. This was most common for composite drugs with a brand and generic name. The fix was applied to the database across all customers to ensure all relevant medication names displayed.
Message Templates - %%FirstName%% and %%LastName%% were populating with the Patient's name instead of the Accountholder's name (EM-4854, Helpdesk #21694)
This issue has now been fixed on all templates includinng 'Estimate of Fees Incomplete). The %%FirstName%% and %%LastName%% fields should always populate with the accountholders/user's name. The %%PatientFirstName%% and %%PatientLastName%% events should always populate with the patient’s name
Falls Risk Question and Response not appearing on the Health History PDF Printout (EM-5113, Helpdesk #22459)
Previously, the response to the question 'Have you had a fall in the last 12 months or do you fear falling or feel unsteady on your feet? *' was not displaying on the PDF printout.
This is now fixed.
Payment Gateway Change - Additional Fields
A minor change was made to track additional fields in the payment transaction log to cater for other customers using alternate payment gateways. This should have no impact on the use of current payment gateways.
| Tags |
|---|
