New SHIN-NY participants consistently underestimate the documentation intensity of the onboarding process. The agencies I have seen complete onboarding smoothly — in 60 days or less — are the ones that had a complete HIPAA compliance programme in place before applying for SHIN-NY participation and who approached the CSPP development process with an understanding of what the RHIO reviewers are looking for. The agencies that take 90–150 days are typically those approaching SHIN-NY as the first formal security compliance project their organisation has undertaken, or those who submitted a CSPP that did not reflect current implemented controls and needed multiple revision cycles.
This guide maps the realistic SHIN-NY onboarding timeline for a New York home health agency starting from a position of reasonable HIPAA compliance maturity — an existing security programme that may not be documented to CSPP standards but that reflects genuine implementation of core security controls.
Pre-Onboarding Preparation: The Foundation That Determines Onboarding Speed
The most important determinant of SHIN-NY onboarding speed is the state of the organisation's underlying security programme before the CSPP development process begins. A CSPP is a documentation of a security programme — it cannot create a compliant security programme where one does not exist. An agency that attempts to write a CSPP without first implementing the controls the CSPP will describe creates a document that RHIO reviewers will question during compliance review.
Pre-onboarding preparation should confirm that the following are in place before CSPP development begins: a current HIPAA risk analysis (within the past 12 months); MFA enforced on all accounts with access to clinical systems; device encryption verified on all devices accessing patient data; a designated HIPAA Security Officer with an active compliance programme role; and a documented incident response plan. These are the controls that CSPP reviewers will ask about most specifically. Having them in place before the CSPP is written means the CSPP accurately describes the current state of the programme.
Days 1–30: CSPP Development and Internal Review
CSPP development begins with understanding the template requirements of your specific RHIO. Request the current CSPP template from your RHIO participant services contact and review it thoroughly before writing a single line of the CSPP. Map each required content area to the corresponding element of your current security programme. Identify any gaps — sections the template requires that your current programme does not address — and address those gaps before the CSPP is finalised. A CSPP submitted with acknowledged gaps generates clarification requests that are more damaging to the review timeline than taking the time to close the gaps before submission.

