Release 26.3.2.0 - 26.4.1.0

Liberally-scheduled order MAR stamping update

New help text for medication scheduling

As of our March 11 release, the Medication Changes Report has been expanded to include activity from Manage Orders pages and the Pharmacy Inbox.

The new Source column in the report now shows where the change originated. Audit messages have also been enhanced to include helpful identifiers, such as Order ID, Rx number, and medication name when available. 

Updates apply to a variety of order changes, including new orders, updated orders, discontinuations, and auto-mapped or auto-processed messages.  

Disable payment methods for disabled/removed payers

As of our March 25 release, all payment methods associated with a payer will now be automatically disabled when that payer is disabled or removed.

A warning message will appear to let users know that the payer’s associated payment methods will also be disabled.

This update helps keep payment configurations aligned with payer status and prevents charges from being attempted for payers who should no longer be billed. 

Gateway ACH/CC now reflects "Balance Due as of" 

As of our March 11 release, the Collect ACH/CC panel in the Payment Center now displays “Balance Due as of” instead of “Balance as of" to better align with billing teams think about outstanding balances. 

This update clarifies that the amount shown reflects the balance due for the selected date, helping users better understand the payment amount being collected.

Track Prospects that are 'Lost to Competitor' 

As of our March 18 release, the ALIS CRM now includes a workflow to track when a prospect is lost to a competitor.

After the feature entitlement is enabled for your community, users with access must add competitors names in the new CRM Settings → Competitors table. Editing any applicable Prospect Stages as 'Lost to Competitor' will then trigger the workflow. 

When a prospect is moved to one of these stages in the ALIS CRM, users are prompted to select the competitor and optionally add notes.

This information is recorded in the Prospect Story, Audit History, and Stage Change History for clear visibility and can be updated when editing the profile. 

Competitor details for these stage changes are also available in Prospect Activity and Prospect Addresses reports, making it easier to review and analyze lost leads.

Auto-create tasks for new Prospects

As of our March 11 release, sales teams can now automatically generate CRM tasks when a new prospect is created. This supports faster follow-up with new inquiries and helps standardize outreach workflows.

In CRM Settings, enable the new "Automatically create for new prospects?" setting when adding or editing a task in the CRM Task Types grid. This allows specific task types to generate automatically when a new prospect is added

Once enabled, the task is automatically created, assigned to the prospect’s sales agent, and given a due date set for the following day.

Contact your Account Manager for assistance with feature enablement or settings configuration.

Meal Plan data available via API

As of our April 1 release, resident Meal Plan assignments and community Meal Plan configurations are now available through the API to support accurate pricing and automation for dining integrations.

Integration partners, such as POS dining systems, can retrieve both the meal plan assigned to each resident and the list of configured meal plans for a community.

Expanded Care integration endpoints

As of our April 1 release, care integration APIs now include Assistance Level data for individual care tasks and care items.

The new /v1/integration/care/{communityId}/assistanceLevels endpoint also allows partners to retrieve the list of configured assistance levels for a community.

These updates help care integrations better organize and display resident care tasks based on the level of assistance required.

New v3 HQ Occupancy export API endpoint

As of our April 1 release, a new v3 export API endpooint supports filtering HQ Occupancy data by a custom date range, instead of requiring a full month selection.

The /v3/export/communities/floorPlan/hqOccupancies endpoint allows integration partners to pull only the occupancy data they need while improving performance and reducing unnecessary data processing.

Invoice Charges integration endpoint

As of our April 1 release, a new API endpoint allows integration partners to retrieve invoice charge data for a community within a selected date range.

The /v1/integration/billing/{communityId}/invoiceCharges endpoint includes detailed charge information such as item name, quantity, unit price, discounts, and payer type, making it easier to integrate billing data with external financial and reporting systems.

Updated Incidents integration endpoint

As of our March 25 release, the Incidents integration endpoint improves how incident data can be shared with ALIS.

The new /v2/integration/incidents/{incidentId} endpoint allows partners to create incidents directly in ALIS, supporting automated feeds from fall detection systems, eCall solutions, and other clinical tools.

The previous v1 endpoint is deprecated, eliminating the need to handle multiple response formats and reducing duplicate parsing logic for integration partners.

New Health Profile integration endpoint

As of our March 25 release, a new endpoint exposes resident functional statuses and adaptive needs to help enable tools like evacuation reports that use accurate, up-to-date resident data.

The new /v1/integration/residents/{residentId}/healthProfile/functionalStatus endpoint  gives access to multiple fields such as vision, ambulation, evacuation status, hearing, speech, assistive devices, and cognitive details. 

Updated Diagnoses and Allergies integration endpoint

As of our March 18 release, the existing endpoint for Diagnoses and Allergies now includes unique identifiers and timestamps for each diagnosis record.

With this /v1/export/clinical/diagnosesAndAllergies endpoint, integration partners can reliably match and track diagnoses, improving data reconciliation and reporting.

Updated Resident Basic Info integration endpoint

As of our March 18 release, integration partners can now access all basic resident information in a single call, reducing the need for multiple API requests.

The existing /v1/integration/residents/{residentId}/basicInfo endpoint returns a full set of resident details, including Middle Name, Nickname, Pronouns, Veteran Status, and Languages.

Updated Resident Contacts integration endpoint

As of our March 18 release, integration partners can now accurately associate shared contacts with every relevant resident in a community.

The existing /v1/integration/residents/contacts/{contactId} endpoint now returns a residentIds array, showing all residents linked to a contact. 

Expanded integration endpoints for CRM

As of our March 18 release, several updates improve how prospect and resident data is exposed via API to streamline CRM data integration and improve reconciliation across prospect and resident workflows:

• Multiple resident endpoints now include a convertedProspectId field, allowing partners to link residents back to their originating prospect.
• The /v1/integration/prospects/referralSources endpoint adds a referralType field, giving more context for categorizing and reporting on referral sources.
• The /v1/integration/communities/{communityId}/prospectTasks endpoint now includes taskOutcome, completedAt, and createdAt, providing better visibility into task history and outcomes for more complete reporting and data synchronization.

Updated Medications integration endpoints

As of our March 11 release, integration partners can accurately link medications to residents and track medication timelines, improving workflows and reporting.

The /v1/integration/residents/{residentId}/medications and medications/{medicationId} endpoints now include residentId and endDate fields.

Contact your Account Manager for assistance with API access and locating specific endpoints.

Want to enable an integration with us?

Reach out to info@go-alis.com to get started.

Unsaved changes warning in key workflows

As of our April 1 release, users will now see a browser "Leave site?" warning when attempting to exit while in the midst of certain workflows.

This warning appears when a user tries to navigate away from the Pass Meds, Care Tracking, and Bulk Payments pages after data is already entered.

Simply click the Cancel button to remain on the page and prevent losing your work.

Security role permission for iStream refunds

As of our March 18 release, a new 'Perform Payment Gateway Refund' security role permission has been added for communities using ALIS Pay with iStream.

This permission controls access to the Process Gateway Refund function.  The new permission separates refund access from bulk payment permissions, giving more control over which users can process gateway refunds.

Existing security roles that already have bulk payment permissions also have this refund permission post-release.

Contact your Account Manager for assistance with updating security role permissions.

Improved Gold Occupancy Logic

This month, we enhanced the logic behind the Gold Occupancy data model to better account for resident status changes within shared units.

The system now automatically generates a corresponding Move-In event when a Secondary resident's status changes to Primary to ensure move-in and move-out activity remains properly reconciled when the previous primary resident departs.

Both promotion (Secondary → Primary) and demotion (Primary → Secondary)  scenarios are handled consistently, improving accuracy of occupancy and financial reporting through the /hqoccupancies endpoint.

Click HERE to view our list of bug fixes in the last month's releases.