DASH 21.1 Service Pack #5 Release Notes

DASH 21.1 Service Pack #5 contains bug fixes and minor enhancements for the DASHcentral and DASHself. Please contact your Client Success Manager with any questions.

DASHcentral 

Coordinated care

  • Fixed an issue affecting provider combinations in coordinated care. If multiple providers were selected, combination slots were offered for providers that are not paired together. For example, in a configuration where Provider A is paired with Provider B and Provider X is paired with Provider Y, if the user selects Providers A and X from the displayed list of providers, the search results would show coordinated care slots for a combination of Providers A and X (despite being an invalid option). This issue was predominantly seen when slots for either of the providers in the set up were unavailable, causing the program to create an invalid pairing. This has now been rectified and provider combinations (and time slots) shown in coordinated care output will now follow the configuration set up. 

Guarantor 

  • Corrected an issue related to the pre-population of the “Middle Name,” “SSN,” and “Address Line 2” fields in the Guarantor Information section of the Demographics page. These fields did not pre-populate when searching for a guarantor that is not the same as the patient, even if the information was available on the guarantor’s Demographics page. The issue has now been rectified. 

  • Corrected an issue related to the population of the “Relation to Patient” and “SSN” fields in the Subscriber Information section of the Insurance page. Previously, when the user indicated that the subscriber is the same as the guarantor, these fields did not pre-populate from the responses provided in the Guarantor Information section of the Demographics page. This issue has now been rectified.   

Audit reporting 

  • On the Appointment Details screen, the “Audit History” tab captures all activity pertaining to an appointment, such as updates to appointment comments and statuses. This is true whether the actions taken in DASH or the EHR. It has been observed that Audit History currently displays some duplicate information, making it difficult for the user to understand the exact updates. This duplication was occurring whenever a user opened the Appointment Details screen, and the duplicated version displayed the username of the user who opened the details. 

This issue has now been repaired for any New Appointment Scheduling and Cancellation workflows. Duplicate and redundant entries related to updates in the New Appointment and Cancellation workflows have now been eliminated, making the “Audit History” tab cleaner and more legible.

(Note that this fix is the first step towards making sure that only necessary updates are displayed in the “Audit History” tab. Additional workflows will be addressed in future releases.) 

  • Fixed a UI distortion issue on the Audit Reporting page that occurred when the search results contained long text strings (for example, during Guarantor and Subscriber updates). Updates to these fields caused the Audit Reporting page to skew left and required the user to reduce the browser zoom ratio to view the full page. Long text strings will no longer require this adjustment.  

Manual inventory sync 

  • Repaired a bug affecting the “Manual Inventory Sync” function. On selecting the provider and the date range for which the inventory needs to be obtained/synced, the page refreshed but did not respond with updated results. The issue has now been rectified.   

Patient instructions 

  • Repaired the display sequence of the instructions entered in the “Instructions to Patient” textbox on the Resource Services page. The instructions entered on this page are displayed to the user in the “Confirm Appointment” modal under the “Patient Instructions” heading. In some cases, if the “Enter” key was used to insert line breaks between instructions, the displayed sequence did not match the sequence as entered by the user. (There was no observable pattern to the displayed sequence.) Extensive testing has been performed to ensure the issue is fixed.  

DASHself 

User interface 

  • Resolved a bug that caused providers’ titles to run onto a second line when hovered over by the user, causing distortion to the surrounding text. 

  • Updated the wording of the final button in the self-scheduling process from “Next” to “Confirm.” This will indicate to clients that they have reached the last step in the process and will have a scheduled appointment when the button is clicked.  

Multiple appointment scheduling 

  •  A bug was identified in which the automated URL redirection following a successful appointment booking was interfering with patients’ attempts to schedule another appointment. This was occurring when a patient booked one appointment and then used the “back” button in their browser to return to the initial search screen to book their subsequent appointment. In these cases, the system was not resetting the automated URL redirection time. As a result, the patient’s subsequent booking attempt would be interrupted with a redirection to the designated website once the redirection time limit had been met. (Note that this did not occur in cases when the patient booked the subsequent appointment in a new browser window or used the “refresh” button in their browser.) This bug has been resolved.  

Data fidelity 

  • Resolved a bug that was displaying inactive providers and PAs in the "Need More” options. 

  • Repaired a bug that allowed the application to reference expired age rules. Moving forward, only active patient age-related rules will be considered on the provider search screen.  

Geographic search 

  • The patient’s home ZIP code, which is entered on the initial DASHself screen, will no longer be auto-populated at the patient demographic stage. Many patients prefer to search for providers in or near a ZIP code other than their home ZIP code, and therefore this field will no longer auto-populate.  

Integrations   

Modernizing Medicine 

  • DASH will now utilize the patient MRN instead of individual patient IDs. 

 

 

Self-configuration 

  • The “Execute Attribute at Slot” checkbox on the “Preference Attributes” screen is used to indicate whether an attribute should be applied at the slot level. Previously, this box was checked by default when creating a new attribute. This has been changed so that the box will be unchecked by default, and the user will need to manually check it to apply the preference at the slot level.  

Additionally, the tooltip for the “Execute Attribute at Slot” checkbox has been modified to improve its usefulness to users during configuration. The tooltip now reads:  

“Slot-level attributes are utilized to calculate data for each slot that will be offered, such as appointment counts, consecutiveness, or time-based rules. Attributes that can be evaluated at the patient or provider-level, such as Age, Visit Reason, or Insurance, should not be executed at the slot level. Attributes that utilize the @date@, @time@, or @appt_type_id@ variables must be executed at the slot level.” 

  • The character limit for the Facility Name, Facility Name (Other), and Facility Abbreviation fields has been increased to 200 to accommodate longer facility names. Tooltips for these fields have been updated to indicate the 200-character limit.