AWS Connected KPI Dashboard & DrChrono Analytics
Budget: $15 – $25 USD
DrChrono Analytics Pipeline and KPI Dashboard — Continuation of Existing AWS Project
I own a mental health practice in New York with 9 providers and 1,200+ weekly patient visits operating on a fully telehealth model. I'm building a KPI dashboard that pulls data from DrChrono into AWS and displays in Tableau Desktop. The goal is a clean, well-documented analytics infrastructure built for long term operational visibility and future business growth.
This is a continuation project. The initial AWS foundation has been set up and I need an experienced developer to complete the remaining work.
What's already in place
The AWS account is configured with the HIPAA BAA accepted. A PostgreSQL database is live on RDS in us-east-2. The DrChrono API connection is established and working with four endpoints pulling data including appointments, patients, providers, and payments. Credentials are stored in AWS Secrets Manager and an ECS cluster is deployed.
What needs to be completed
Milestone 1 — Remaining API endpoints connected and pulling data. This includes claims, billing profiles, line items and charges, insurance plans, offices and locations, appointment profiles and visit types, and eligibility. ERAs are autoposted through DrChrono's clearinghouse so denial reason codes are available.
Milestone 2 — Full pipeline build and data modeling. Automated syncing on a regular schedule, star schema built out with fact tables for appointments, charges, payments and claims and dimension tables for patients, providers, dates, payers and offices. Three years of historical data loaded. Data transformation and cleaning. Basic reconciliation confirming database numbers match DrChrono natively.
Milestone 3 — Tableau Desktop dashboard. Clean and polished design with global filters for provider, date range, visit type, and location. KPIs required include AR aging buckets, net collection rate, denial rate, days in AR, payer mix breakdown, revenue per provider, visits per provider, no-show rate, new patient volume, and patient retention.
Milestone 4 — Documentation and handoff. Architecture diagram, data dictionary, KPI definitions document, pipeline runbook, reconciliation report, and recorded training walkthrough. Documentation must be thorough enough that someone unfamiliar with the system can understand and maintain it without the developer present.
Requirements
Must be willing to sign a Business Associate Agreement before accessing any patient data as this project involves protected health information under HIPAA and New York Mental Hygiene Law. All credentials must be stored in AWS Secrets Manager and never on local devices. All code delivered in a Git repository under my ownership. Milestone based payments tied to deliverables, not time. Clear proactive communication throughout — I am not technical and need things explained in plain terms.
I own a mental health practice in New York with 9 providers and 1,200+ weekly patient visits operating on a fully telehealth model. I'm building a KPI dashboard that pulls data from DrChrono into AWS and displays in Tableau Desktop. The goal is a clean, well-documented analytics infrastructure built for long term operational visibility and future business growth.
This is a continuation project. The initial AWS foundation has been set up and I need an experienced developer to complete the remaining work.
What's already in place
The AWS account is configured with the HIPAA BAA accepted. A PostgreSQL database is live on RDS in us-east-2. The DrChrono API connection is established and working with four endpoints pulling data including appointments, patients, providers, and payments. Credentials are stored in AWS Secrets Manager and an ECS cluster is deployed.
What needs to be completed
Milestone 1 — Remaining API endpoints connected and pulling data. This includes claims, billing profiles, line items and charges, insurance plans, offices and locations, appointment profiles and visit types, and eligibility. ERAs are autoposted through DrChrono's clearinghouse so denial reason codes are available.
Milestone 2 — Full pipeline build and data modeling. Automated syncing on a regular schedule, star schema built out with fact tables for appointments, charges, payments and claims and dimension tables for patients, providers, dates, payers and offices. Three years of historical data loaded. Data transformation and cleaning. Basic reconciliation confirming database numbers match DrChrono natively.
Milestone 3 — Tableau Desktop dashboard. Clean and polished design with global filters for provider, date range, visit type, and location. KPIs required include AR aging buckets, net collection rate, denial rate, days in AR, payer mix breakdown, revenue per provider, visits per provider, no-show rate, new patient volume, and patient retention.
Milestone 4 — Documentation and handoff. Architecture diagram, data dictionary, KPI definitions document, pipeline runbook, reconciliation report, and recorded training walkthrough. Documentation must be thorough enough that someone unfamiliar with the system can understand and maintain it without the developer present.
Requirements
Must be willing to sign a Business Associate Agreement before accessing any patient data as this project involves protected health information under HIPAA and New York Mental Hygiene Law. All credentials must be stored in AWS Secrets Manager and never on local devices. All code delivered in a Git repository under my ownership. Milestone based payments tied to deliverables, not time. Clear proactive communication throughout — I am not technical and need things explained in plain terms.