Most hospice startups are organised around the application. The application is the visible milestone, so it becomes the plan, and the systems get built afterward in whatever order problems arrive. That sequence is backwards, and survey activity tends to expose it. These are the systems worth having in place before certification rather than after.
Build governance before the first survey
Define who holds operational authority, how the governing body receives information, how policies get approved, how conflicts are escalated, and how leadership will actually oversee quality and compliance. A paper organisation chart is not governance. If nobody in the building can explain how a decision moves through the company, the structure exists on the wall rather than in practice, and that difference becomes visible quickly under questioning.
Design the patient workflow end to end
Map the full path before the first referral arrives: referral, eligibility review, admission, election documentation, comprehensive assessment, plan of care, interdisciplinary work, medications, durable medical equipment, visits, after-hours response, recertification, transfers, discharge and bereavement. Every handoff in that chain needs a named owner. Handoffs without owners are where items stall invisibly, and a startup has no institutional memory to catch them.
Make billing part of operations from day one
Eligibility, physician certification, notices, levels of care, visit documentation and claims are one connected system, not a clinical process with a financial process bolted on afterward. When billing is designed after the clinical workflow is already running, organisations routinely discover that required information is not being captured reliably, and by then it is being retrofitted into habits that have already set.
Create QAPI before there is enough data to look impressive
Early QAPI will have small numbers and that is fine. Small numbers are not the problem; absent governance is. Decide how incidents, complaints, chart audits, quality measures and operational risks will be reviewed, by whom, and on what cadence. The follow-through structure should exist before there is volume to run through it, because building it under load rarely happens.
Prepare staff to explain the system
During certification and survey activity, staff are asked what they do, not what the policy says. Those answers should match. Test the workflow with mock cases and internal audits rather than relying on policy memorisation. Someone who can describe their own role in the process is far more convincing, and far more useful, than someone who can quote a manual.
Use the current CMS institutional enrolment roadmap
CMS publishes enrolment and certification guidance specifically for institutional providers, including hospices. Build the startup timeline from current CMS, state and accreditor sources rather than from a checklist another agency shared two years ago. Requirements change, and inherited checklists are one of the more common reasons a startup discovers a gap late. Compliance note: Hospice startup requirements depend on federal, state, payer and accreditation pathways. This article is not legal advice and should not be used as a certification checklist on its own.
Sources used for fact-checking
- https://www.cms.gov/medicare/health-safety-standards/certification-compliance/hospices
- https://www.cms.gov/Medicare/Provider-Enrollment-and-Certification/Enroll-as-an-Institutional-Provider
- https://www.cms.gov/hospice-information-center
- https://pfundamental.com/hospice-consulting-service/