Required Activity Type Selection for Staff Activities
We've updated the Add Activity and Start Activity flows to require an activity type selection before saving—so your staff activity records are always complete and ready for downstream processing. 💙
✨ What's new:
  • 📋 Activity type is now required
    — When you add or start a new staff activity from My Activities, you'll be prompted to select an activity type before saving. No more defaulting to a pre-selected value.
  • ⚠️ Inline validation
    — If you try to save without selecting an activity type, you'll see a clear error message letting you know what's needed.
  • ✅ Appointment-mapped activities unchanged
    — If you start an activity from an appointment that already has a configured activity type mapping, the type will continue to pre-populate as expected.
💡 Why it matters:
Accurate activity type data is essential for clean records and smooth integration with your practice management system. Previously, activities could be saved with a default type that didn't reflect the actual work performed, leading to errors or manual corrections downstream. This update ensures the right data is captured at the point of entry—helping your team stay focused on care, not cleanup.
👉 Learn more about:
────────
Removed "Rate" as Measurement Option for Frequency Programs
We've removed "Rate" from the measurement options available on Frequency program types—resolving a source of confusion when setting up programs and reviewing graphs. 💙
✨ What's changed:
  • 🔧"Rate" option removed from Frequency programs
    — The Rate measurement option is no longer available when configuring a Frequency program type, since rate is not a meaningful calculation for frequency-based data.
  • 📊 Cleaner graph settings
    — Your graph Y-axis options for Frequency programs now only show measurement types that apply, making it easier to configure accurate visuals.
💡 Why it matters:
Having "Rate" as an option on Frequency programs created confusion for clinicians setting up programs and interpreting graphs. Removing it means fewer setup mistakes and clearer data—so your team can trust what they see on the graph without second-guessing the configuration.
👉 Learn more about: