v1.7.76

Released on May 5, 2026

This release fixes several issues that practice staff would have noticed firsthand — including forms incorrectly showing missing required fields, patients being able to skip required questions on lead forms, and photo pagination getting stuck. Deposit collection now correctly uses the payment processor configured for each location.

Highlights

• Required Fields Now Enforced on Lead Forms Patients can no longer submit a lead form without answering questions that your team marked as required. This closes a gap where required fields could be bypassed, helping ensure you collect complete intake information every time.
  • Required questions on lead forms are now enforced on submission — patients will see an error if they try to skip them
  • This applies to all lead forms with required fields configured in your form builder
  • Helps maintain complete patient intake data and supports compliance requirements

Improvements

• Completed Forms Now Display in Read-Only Mode When staff or patients view a previously completed form, it now displays the submitted answers cleanly without showing red “required field” markers — so it’s clear the form was properly filled out at the time of submission.
  • Completed forms in the admin view and patient portal no longer appear editable or show missing-field warnings
  • The answers shown always reflect what the patient actually submitted, not their current profile information
  • Find this when reviewing a patient’s completed Forms & Consents in their chart
• Photo Pagination Always Reachable Scrolling through a patient’s photo gallery no longer traps you in the grid — the page navigation controls now stay visible and accessible at the bottom of the photo panel no matter how many photos are loaded.
  • The Previous / Next page controls stay pinned at the bottom of the photo panel while you scroll through images
  • You can now browse large photo libraries without losing access to pagination
  • Find this in the Photos tab of a patient’s chart

Bug Fixes

• Deposit Collection Uses Correct Payment Processor When collecting a deposit, the payment form now correctly uses the payment processor configured for the specific location — instead of defaulting to a different processor set at the account level.
  • Practices with location-specific payment processor settings will now see the correct payment fields when collecting deposits
  • Previously, deposits at those locations could silently use the wrong processor, potentially causing payment issues
  • No action needed — this is corrected automatically going forward