Healthtech · United States
Elasticsearch-backed reporting, timezone-aware goal automation across hundreds of tenants, two-way sync with 75+ practice-management systems, role-specific dashboards and mobile APIs, inside a SOC 2 and HIPAA-compliant Rails product.
A SOC 2 and HIPAA-compliant SaaS that sits on top of a dental practice's management system and turns the numbers into daily behaviour: live dashboards, monthly goals, leaderboards, team incentives paid out through Stripe, automated patient workflows and a morning huddle screen. It syncs two-way with more than 75 practice-management systems and is used by single practices, dental service organisations and consultants who manage many practices at once.
The platform was growing fast and the reporting layer hadn't kept up. Goal reports refreshed slowly because they aggregated straight from the transactional database. Monthly goals were set up by hand per practice, in each practice's own timezone. Consultants comparing dozens of practices had to click through dashboards to answer simple questions. The data ingestion from practice-management systems also needed to support instant onboarding for free trials. We joined the engineering team as a senior engineer owning reporting and ingestion.
How the system is layered, from the people using it down to the data and the services it depends on.
The choices that made the difference, and why we made them.
Every practice gets its monthly goals created at 1 AM in its own timezone, by a cron job that walks tenants and schedules per-tenant execution rather than running once in UTC. The same pattern drives automated report refreshes, so a practice in Hawaii and one in Maine both start the month with fresh numbers at the right local time.
We indexed goals, patients, treatments and ledger transactions into Elasticsearch to take the reporting load off PostgreSQL, which cut goal update latency by more than 75 percent. Later, once the biggest tables were costing more to keep in sync than they saved, we led a scoped removal from those tables. Good architecture includes knowing when to take something out.
Cron-based pipelines pull practice data from multiple practice-management systems: a full initial load, hourly incremental updates, and a six-month historical pull during trials so a prospect sees real trends instead of an empty dashboard.
A practice owner, a doctor and a hygienist need different numbers from the same ledger. We built role-specific dashboards with their own goal types and leaderboards, an Excel export for consultants who compare dozens of practices, and the mobile APIs behind production, collections, treatment-plan and analysis screens, all reading from the same indexed data so no two views disagree.
Tell us what you're building. You'll get a straight answer on scope, timeline and cost, usually within one business day.