Compliance
ClinConnect keeps placement requirements on the record instead of in a spreadsheet. This page describes what the platform tracks, and — just as importantly — what it does not decide for you.
Requirements live on the placement
Schools configure the requirements a program expects, and clinical sites add anything specific to their setting. A student's checklist is assembled from both, so nobody has to reconcile two lists by hand.
- Immunisation records, background checks, certifications, and signed agreements.
- Each item carries its own status: pending review, approved, rejected, or expired.
- A requirement is only satisfied by an approved document that has not passed its expiry date.
Expiry is tracked, not assumed
Documents with an expiry date move to "Expiring Soon" 30 days before they lapse, and the student and their school both see it while there is still time to act. After the date passes the requirement stops counting as met.
Two approvals, both recorded
A placement needs the clinical site to accept the student and the school to approve the placement. Each decision is stored with the account that made it and the time it was made, and the sequence is visible on the application itself.
Hours are submitted by the student and verified by a preceptor. Evaluations are completed against the placement they belong to and stay attached to it.
What this platform does not do
ClinConnect is placement management software. It records what your programs and sites require and shows you where each student stands against it. It does not certify a school, a site, or a student as compliant with any regulation, accreditation standard, or state requirement — those determinations remain with your institution.