The website and the office both need clarity.
For a family or referral partner, the first challenge is understanding services and the next step. Inside a home health agency, the challenge is different: records, schedules, visit evidence, staff coordination, and follow-up have to stay connected across systems.
My PTHHS work addresses both sides. The public website work improves the path into the agency. The management platform is designed to give the agency ownership of its workflows while treating HHAeXchange as an external system to integrate with—not the place where every local operating rule must live.
A public front door and an operational foundation.
The website work includes migration from the previous WordPress/Proweaver setup to Firebase, asset and page repairs, and clearer service, attendant-care, insurance, and referral information. Location content is connected to service and eligibility context. Search visibility remains a measured objective; I do not claim rankings without a Search Console baseline.
The management layer includes a TypeScript backend, a contract-aware HHAeXchange SOAP adapter, and a vendor-neutral data model. Its capability audit maps 222 vendor operations. Protected workspace reads, owner preferences, investigations, change-review flows, documents, and audit history establish a foundation for operational use. Mapped capability is not the same as a live-enabled integration.
An uncertain result must stay uncertain.
A proposed vendor change moves through preparation, a fresh recheck, independent review, a single submission, and a read-back reconciliation. If the outcome is unknown, the system retains that state rather than automatically retrying an action that may already have happened. Source versions and durable locks support that behavior.
Visit corrections preserve original clock evidence, with reasons and supervisor review kept separate from billing and payroll effects. Staffing plans prioritize patient choice and continuity; current review surfaces expose preferences and availability without pretending to decide clinical eligibility or make assignments autonomously.
An implemented foundation, with activation still to earn.
The public website work is delivered. The management implementation has fixture-based validation and a documented release review, but production data activation, vendor verification, and agency acceptance remain staged. That distinction is essential when describing a platform that touches real operational records.
The roadmap includes validated live imports, visit-exception queues, supervisor summaries, staff coordination, authorization and billing visibility, and payroll reconciliation. AI-assisted note review and validation are planned extensions, not a claim of autonomous clinical decisions or completed state-system automation.
About this case study +
Current PTHHS repository and management-layer release review, HHA remaining-implementation notes, and October 1, 2026 website content review, supplemented by the recorded agency roadmap.
Researched and updated October 3, 2026.