Release 158 is scheduled for 2018-01-30 @ 6:00pm Eastern
Available on 2018-01-23 @ 6:00pm Eastern on your Preview environment.
We will use our release notes to publish the next 4 release dates to keep everyone 1/3 of a year informed.
- Feb 27th
- March 27th
- April 24th
- May 22nd
Register to our Webinar regarding monthly releases. Each monthly release, we'll run through all the new exciting features and improvement included in the release.
When: January 25th, 2018 1:00 PM Eastern Time (US and Canada)
After registering, you will receive a confirmation email containing information about joining the webinar.
For February, many new highly anticipated features have been added. Accounting folks will be happy to see the introduction of Medicaid Eligibility and Funder Integration!
Read below to see the complete list of improvements made to AlayaCare. For more information, don't hesitate to contact your Client Success Manager.
See Accounting>Accounting Settings>Funders.
The funder list has been refactored.
So has the Funder Add/Edit dialogue:
When creating a new funder, the user can select a funder type. Depending on the selection, additional fields will appear which are necessary for that funder.
The available types include CCAC (for tenants with the CCAC feature flag on), and Medicaid (for tenants with the Medicaid feature flag on).
Automated Medicaid Eligibility checks are now available, dependent on the Medicaid feature flag.
To check client medicaid eligibility, the client must have at least one service funded by a Medicaid-type funder.
A summary of the client's eligibility information will appear in their Overview:
For more information, click on More Details:
Writeoff/Void invoice item
It is no longer possible to write off or void a single invoice item from the invoice preview. This is to eliminate subledger conflicts and double-counting between transactions performed at the invoice level and at the invoice item level.
These actions can still be performed at the invoice level.
See Accounting>Accounting Settings>Accounts.
In order to prevent data errors concerning subledgers, it is no longer possible to delete accounts.
Instead, accounts may be disabled or enabled.
Disabled accounts can no longer be selected in dropdowns (for example: when creating a bill code), but disabling them will not impact functionality of past transactions created with them.
Improvements have been made to visit locking to make it more flexible and robust, as well as simpler to use.
The previous multitude of ACLs which governed permissions to edit locked visits have been replaced with a single Edit Locked Visits ACL. This single ACL is used in conjunction with ACLs controlling editing of individual fields within the visit in order to grant permissions to edit locked visits.
For users with permission to edit a locked visit, a warning has been put in place which they must override in order to save a change to a locked visit. A user who chooses to override the warning can then take appropriate action around the related invoice(s) or payroll run(s) to correspond to any changes to the visit.
Finally, for reasons of data integrity, it is now impossible to delete a visit which has been included in an invoice or payroll run. The visit can still be cancelled for a non-billable or non-payable reason.
Form context attributes from the Client sections are now visible in the Service dialog, as well as the Service Overview page.
Blocking terminated employees from logging in
A new security feature has been added. When an employee or user is terminated in the system, they will no longer be able to log into AlayaCare and will be notified via the following error message: