Our district was just briefed that starting July 1 we can bill Medicaid for eligible school-based mental health supports, not just IEP-related services. For those already doing this, how are you handling parent consent and documentation so it protects student privacy and time with kids while keeping us audit-ready?
We built consent into online registration as a one-page ‘minimum necessary’ release that explicitly names Medicaid billing for school-based MH, and in our EHR a smart phrase auto-fills date, code, and location so the narrative stays minimal and kid time isn’t eaten up. Only caveat: our auditor required a separate FERPA disclosure log tied to each claim (no clinical details), so we auto-generate that — do you have a way to log disclosures outside the chart?
But in our district, we added a consent status field to the note template that pulls the e-sign date and, if valid, spits out a separate billing summary (date, units, CPT, NPI) while locking the narrative to FERPA only — tiny setup lift, big privacy win. > claim (no clinical details), so we auto-generate that — do you have a way to log disclosures outside the — we use the EHR’s disclosure log for any phone/fax and run a quick monthly audit; @sophia_rhodes91 does that track with what you’re doing?
One tweak that’s helped us: a stop-bill rule in the EHR so if Medicaid consent isn’t current the claim save button is greyed out (“no consent, no claim”), and we log only date, minutes, POS 03, and program code in a billing-only encounter so the clinical note stays private. @l_torres99 are you doing monthly eligibility sweeps or real-time checks at intake?
Since your go-live is July 1, we made that our annual renewal day and use a super-short ‘billing abstract’ note separate from the clinical note — just date, time, HCPCS/CPT, and NPI — so privacy stays tight but auditors have what they need. , the EOB issue bites, so our consent spells out that Medicaid may send mail and we offer a confidential contact option for adolescents where allowed; CMS’ school-based memo helped us wordsmith: https://www.medicaid.gov/federal-policy-guidance/downloads/sho23006.pdf. Do you have a clean way to flag crisis drop-ins so they don’t clog claims queues but still count for utilization?
Quick win: use a FERPA‑compliant consent solely for reimbursement that says ‘not a condition of services,’ names Medicaid, and expires July 1 — then have SIS feed that status to the EHR so clinicians just tick billable and move on (seatbelt for audits). @randall_hopkins19 did you tie your renewal to that date or keep it rolling?
ParentSquare e-consent at registration; explain ‘not just IEP-related’; auto-void from revocation date. Using texting?
We cut admin time by adding a “billable” checkbox in the EHR that auto-generates a locked billing stub (date, start/stop, HCPCS/CPT, POS, rendering NPI) while the narrative stays FERPA-only; consent lives in SIS and syncs nightly to block claims on revocation, anchored by this brief: https://www2.ed.gov/policy/gen/guid/fpco/doc/ferpa-hipaa-guidance.pdf. Does your vendor support role-based access so billing only sees the stub?