Bug Fixes
- Fixed an issue where saving a daily schedule would shift the entire week to the previous day for users in certain timezones.
- Corrected an issue where untoggling an element in a Clinical Note would leave it appearing toggled even after saving, causing confusion when charting.
- Fixed an error preventing credit cards with a Canadian billing address from being saved to a patient's payment information.
- Resolved an issue where migrating patients with payment methods that have no billing address on file would fail; the system will now use the patient's demographics address as a fallback when a billing address is not present in the payment processor.
Labs
- When PrimeLabs results are successfully received, a task is now automatically created in the Lobbie tasks dashboard to notify staff — consistent with behavior for other lab providers.
Patient Census / CRM
- The Patient Census (CRM) feature is now enabled by default for all enterprise accounts and no longer requires a feature flag to access.
Enhanced Branding
Note: Enhanced Branding is still in active development and is not yet broadly available.
- Multi-location accounts can now configure identity settings (logo, colors, fonts) on a per-location basis, with the ability to add, edit, or remove location-specific overrides independently of the account-level defaults.
Partner API
Note: The Partner API is still in active development.
- New endpoints for Form Templates and Form Template Groups are now available, enabling partners to read and manage form configuration programmatically.
- New Lab and Lab Test Component endpoints are now available, allowing partners to retrieve lab orders, results, and individual test components with filtering by patient, appointment, status, vendor type, and date range.
- Corrected an inconsistency in the Partner API where some validation errors returned HTTP 400 instead of the standard 422 response code, making error handling more predictable for API consumers.
Infrastructure
- All API environments have been migrated to AWS API Gateway, improving reliability, scalability, and the foundation for future partner API capabilities.
Payments V2
Note: Payments V2 is a new feature currently in active development.
- Staff can now create a payment request for a patient for a specific amount, with the payment attempt appearing immediately in the UI with a pending status.
- When creating a payment request, staff can now select from a patient's stored payment methods, displaying the card type, brand, last four digits, and expiration date for easy identification.
- Payment requests are now submitted to the payment processor asynchronously, with safe retry logic to ensure no duplicate charges are created.