Who this is for
Get started
1
Add PostgreSQL
Connect your scheduling, EHR, or revenue warehouse. See Add connectors.
2
Index and mark key tables
Flag appointments, admissions, claims, and providers.
3
Ask your first question
Try: What is no-show rate by site for the last 90 days?
4
Build the dashboards below
Share operational and revenue-cycle views with site leaders.
See it in Vizkraft
Your data
Tables to mark during indexing
- Appointments — volume, no-shows, wait times
- Admissions — encounter volume and capacity
- Claims — revenue cycle and A/R
- Providers — utilization and scheduling load
Dashboards to build
Patient volume and capacity
Answers: How busy are our sites and where are no-shows highest? Include appointment and admission KPIs, no-show rate, daily volume trend, and volume by site.Claims and revenue cycle
Answers: How efficiently are we collecting revenue? Include days in A/R and denial rate KPIs; claims by status; and an aging claims table.Provider utilization
Answers: Are clinicians scheduled efficiently? Include utilization and FTE KPIs; utilization by specialty; and provider schedule load table.Wait times and SLA
Answers: Are patients waiting too long? Include average and p95 wait KPIs; wait trend over time; and wait by department.Questions to ask by role
Example conversations
No-show rate
Ask: What is no-show rate by site for the last 90 days? Use the result to compare sites fairly — pair rate with appointment volume.Metrics worth defining
Add to Connector memory as needed:- No-show rate — no-show appointments ÷ scheduled appointments
- Days in A/R — average days from claim submission to payment
- Utilization — booked clinical time ÷ available capacity
- Denial rate — denied claim amount ÷ submitted amount