Project and task management decision
One Care Portal
Build a narrow replacement (ERA parsing + basic charting and claim validation) is realistic for a capable engineer, but the vendor's audited HIPAA compliance (BAA), onboarding/migration, state-specific waiver templates, and payer-tested ERA/denial mappings are durable operational advantages worth paying for.
Visit website↗$5.99/mo
$72/yr
Read off the official pricing page.
$100one-off92 h to build
$250/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 44 seats.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Record participants and visits, generate visit/claim events, validate claims and authorizations, parse payer 835 ERA remits, and surface denials/work queues for review.
What it still won’t have
- Business Associate Agreement signed by vendor (BAA)
- Specialized onboarding, data migration and one-week go-live service
- Prebuilt waiver-specific templates and state-audit-focused workflows
- Established payer/clearinghouse handling and tested ERA mappings
- Vendor support and audit-ready reporting tuned for Medicaid waiver programs
What remains hard
- Compliance and regulation
BAA With Every Customer
- Brand trust
Featured in Louisville Business First
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 44 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a HIPAA-ready care management and billing prototype using Node.js (Express), PostgreSQL, React, and hosted on a single DigitalOcean droplet plus managed Postgres and S3-compatible encrypted storage. Core features in scope: user auth with RBAC and audit logs; participant record CRUD and encrypted file attachments; calendar-based visit scheduling and attendance capture; templated visit/contact notes with e-signature and an AI-draft endpoint (pluggable to OpenAI); claim generation with basic pre-submission validation (authorizations, units, rates); X12 835/ERA parser to ingest .835/.era/.txt files and surface paid/denied/underpaid claims and CARC/RARC codes in a review queue; admin exports for audit. Out of scope: full payer submission integrations, multi-state regulatory tailoring, enterprise onboarding services, and SLA/backups beyond standard managed provider. Include input validation, error handling, automated tests for each major feature, and deployment scripts (Docker + Terraform).
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-3
- Evidence score59
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productOne Care Portal — official product
- official pricingOne Care Portal Pricing
- official docsWaiver Documentation Requirements
Integrity checks
What held up, and what did not.
