[{"data":1,"prerenderedAt":1800},["ShallowReactive",2],{"toolkit-assets":3,"resources-news":997},[4,218,440,633,846],{"id":5,"title":6,"accentColor":7,"assetType":8,"body":9,"description":203,"extension":204,"icon":205,"meta":206,"navigation":207,"order":208,"path":209,"readTime":210,"seo":211,"states":212,"stem":214,"type":215,"updated":216,"__hash__":217},"toolkit\u002Fresources\u002Fhcbs-audit-readiness-checklist.md","HCBS Medicaid Audit-Readiness Checklist","bg-primary-500","checklist",{"type":10,"value":11,"toc":191},"minimark",[12,21,24,29,49,53,74,78,92,96,107,111,122,126,137,141,156,160,182,185],[13,14,15,16,20],"p",{},"Audits rarely fail because the care was bad. They fail because the ",[17,18,19],"strong",{},"record can't prove the care happened",". The goal of audit readiness is simple: every billed unit should be traceable to a complete, signed, time-stamped record that matches the authorized plan of care.",[13,22,23],{},"Use this checklist as a self-audit. Work through it for a random sample of recent claims, the same way a reviewer would, and fix what you find before someone else finds it.",[25,26,28],"h2",{"id":27},"_1-eligibility-authorization","1. Eligibility & authorization",[30,31,32,36,39,46],"ul",{},[33,34,35],"li",{},"Each individual has a current Medicaid eligibility determination on file for every date of service billed.",[33,37,38],{},"A current, signed plan of care (or service plan \u002F ISP) authorizes the specific service, frequency, and number of units billed.",[33,40,41,42,45],{},"Services billed fall ",[17,43,44],{},"within"," the authorized dates, units, and service definitions, no billing before the plan's start date or after it expires.",[33,47,48],{},"Any service limits, prior authorizations, or level-of-care determinations are documented and unexpired.",[25,50,52],{"id":51},"_2-documentation-completeness","2. Documentation completeness",[30,54,55,62,65,68,71],{},[33,56,57,58,61],{},"A service note exists for ",[17,59,60],{},"every"," billed unit, no billed service without a matching note.",[33,63,64],{},"Each note identifies the individual, the date, the start and end time, the specific service delivered, and the staff member who delivered it.",[33,66,67],{},"Notes describe what actually happened in enough detail to justify the service and tie back to the individual's goals, not just \"client doing well.\"",[33,69,70],{},"Notes are signed and dated by the staff member who provided the service, with credentials where required.",[33,72,73],{},"Late entries and corrections are clearly marked as such, with the date of the correction and the author, never overwritten or backdated.",[25,75,77],{"id":76},"_3-time-units","3. Time & units",[30,79,80,83,86,89],{},[33,81,82],{},"Documented start\u002Fend times support the number of units billed (units are not rounded up beyond what the time supports).",[33,84,85],{},"No overlapping services: the same staff member is not billed as serving two people at the same time (unless a group ratio is authorized and documented).",[33,87,88],{},"Group services document the staff-to-individual ratio and each participant's individual record.",[33,90,91],{},"Travel, no-shows, and missed visits are handled per your state's billing rules and are not billed as delivered services.",[25,93,95],{"id":94},"_4-staff-qualifications-training","4. Staff qualifications & training",[30,97,98,101,104],{},[33,99,100],{},"Every staff member who delivered a billed service met the qualification requirements for that service on the date it was delivered.",[33,102,103],{},"Required background checks, certifications, and competency training were current on each date of service.",[33,105,106],{},"Training records (initial and annual) are on file and retrievable.",[25,108,110],{"id":109},"_5-electronic-visit-verification-evv","5. Electronic Visit Verification (EVV)",[30,112,113,116,119],{},[33,114,115],{},"For services subject to EVV, every visit captures the six federally required data elements (see the EVV Readiness Guide).",[33,117,118],{},"EVV records reconcile with billed claims, no claims without a matching verified visit.",[33,120,121],{},"Manual edits to EVV records are documented with a reason and an audit trail.",[25,123,125],{"id":124},"_6-health-safety-incidents","6. Health, safety & incidents",[30,127,128,131,134],{},[33,129,130],{},"Required incident reports were filed within your state's timeframe and are on file.",[33,132,133],{},"Follow-up actions from incidents are documented and closed out.",[33,135,136],{},"Required health and safety items (e.g., medication administration records where applicable) are complete and signed.",[25,138,140],{"id":139},"_7-records-retention-retrieval","7. Records retention & retrieval",[30,142,143,146,153],{},[33,144,145],{},"Records are retained for at least your state's required retention period (commonly 5–10 years, confirm yours).",[33,147,148,149,152],{},"You can produce a complete record for any requested claim ",[17,150,151],{},"within the time an auditor allows"," (often days, not weeks).",[33,154,155],{},"Records are backed up and protected, and access is limited to authorized staff (HIPAA).",[25,157,159],{"id":158},"how-to-run-a-mock-audit","How to run a mock audit",[161,162,163,166,169,176,179],"ol",{},[33,164,165],{},"Pull a random sample of 10–20 claims from the last 90 days across different services and staff.",[33,167,168],{},"For each claim, try to assemble the complete proof: authorization, note, time record, EVV record, staff qualification.",[33,170,171,172,175],{},"Score each claim pass\u002Ffail and log ",[17,173,174],{},"why"," any failed.",[33,177,178],{},"Group the failures by root cause (missing signatures, time mismatches, late notes), that's your corrective-action plan.",[33,180,181],{},"Re-run the sample after fixes to confirm the gap is closed.",[183,184],"hr",{},[13,186,187],{},[188,189,190],"em",{},"This checklist provides general, federal\u002FCMS-level guidance for HCBS providers and is not legal advice. Medicaid documentation, retention, and billing rules vary by state and by waiver program, always verify the specific requirements of your state Medicaid agency and managed care organizations before relying on it.",{"title":192,"searchDepth":193,"depth":193,"links":194},"",2,[195,196,197,198,199,200,201,202],{"id":27,"depth":193,"text":28},{"id":51,"depth":193,"text":52},{"id":76,"depth":193,"text":77},{"id":94,"depth":193,"text":95},{"id":109,"depth":193,"text":110},{"id":124,"depth":193,"text":125},{"id":139,"depth":193,"text":140},{"id":158,"depth":193,"text":159},"A practical, walk-through checklist for HCBS and IDD agencies preparing for a Medicaid record review, PERM audit, or state program-integrity audit. Use it to find gaps before an auditor does.","md","i-heroicons-clipboard-document-check",{},true,1,"\u002Fresources\u002Fhcbs-audit-readiness-checklist",9,{"title":6,"description":203},[213],"All states","resources\u002Fhcbs-audit-readiness-checklist","Checklist","2026-06-05","PArkcgsi9eKhVkAAa2OEZdPbN557qjWO1xEftZwlvTs",{"id":219,"title":220,"accentColor":221,"assetType":222,"body":223,"description":430,"extension":204,"icon":431,"meta":432,"navigation":207,"order":193,"path":433,"readTime":434,"seo":435,"states":436,"stem":437,"type":438,"updated":216,"__hash__":439},"toolkit\u002Fresources\u002Fevv-readiness-guide.md","Electronic Visit Verification (EVV) Readiness Guide","bg-accent-500","guide",{"type":10,"value":224,"toc":414},[225,240,243,247,250,287,290,294,300,309,314,340,344,348,351,355,358,362,365,369,372,376,379,383,386,390,407,409],[13,226,227,228,231,232,235,236,239],{},"Electronic Visit Verification (EVV) is a federal requirement, not a vendor product. Under the ",[17,229,230],{},"21st Century Cures Act",", state Medicaid programs must require EVV for Medicaid-funded ",[17,233,234],{},"personal care services"," and ",[17,237,238],{},"home health care services",". States that don't enforce it face reduced federal funding, which is why every state now has an EVV program, even though the details differ.",[13,241,242],{},"This guide covers what's federally fixed, what varies by state, and how to get ready.",[25,244,246],{"id":245},"what-evv-must-capture-the-six-data-elements","What EVV must capture: the six data elements",[13,248,249],{},"Federal law requires every EVV-verified visit to electronically capture six things:",[161,251,252,258,264,270,276,281],{},[33,253,254,257],{},[17,255,256],{},"Type of service"," performed",[33,259,260,263],{},[17,261,262],{},"Individual receiving"," the service",[33,265,266,269],{},[17,267,268],{},"Date"," of the service",[33,271,272,275],{},[17,273,274],{},"Location"," of service delivery",[33,277,278,263],{},[17,279,280],{},"Individual providing",[33,282,283,286],{},[17,284,285],{},"Time"," the service begins and ends",[13,288,289],{},"If any of the six is missing or can't be verified, the visit isn't compliant, and the claim built on it is at risk.",[25,291,293],{"id":292},"whats-federal-vs-whats-up-to-your-state","What's federal vs. what's up to your state",[13,295,296,299],{},[17,297,298],{},"Federal (the same everywhere):"," the mandate itself, the six data elements, and the services covered (personal care and home health).",[13,301,302,305,306],{},[17,303,304],{},"State-specific (confirm yours):"," the EVV model your state uses, whether you must use the state's chosen system or may bring your own compliant system, accepted verification methods (mobile GPS, telephony, fixed device), how manual edits and exceptions are handled, and the reason codes you must use. ",[17,307,308],{},"Always confirm these with your state Medicaid agency.",[310,311,313],"h3",{"id":312},"evv-models-states-choose-from","EVV models states choose from",[30,315,316,322,328,334],{},[33,317,318,321],{},[17,319,320],{},"State Mandated In-House",", you must use the system the state provides.",[33,323,324,327],{},[17,325,326],{},"State Mandated External Vendor",", the state contracts a single vendor everyone uses.",[33,329,330,333],{},[17,331,332],{},"Provider Choice \u002F Open Model",", you may use any system that meets the state's requirements and submits data to the state aggregator.",[33,335,336,339],{},[17,337,338],{},"MCO Choice",", managed care organizations select the system for their networks.",[25,341,343],{"id":342},"a-step-by-step-readiness-path","A step-by-step readiness path",[310,345,347],{"id":346},"step-1-confirm-scope","Step 1, Confirm scope",[13,349,350],{},"Identify exactly which of your services are subject to EVV in your state. Personal care and home health are federally required; some states extend EVV to additional waiver services.",[310,352,354],{"id":353},"step-2-confirm-your-states-model","Step 2, Confirm your state's model",[13,356,357],{},"Find out whether you must use a state system, an MCO system, or may use your own compliant system. This determines everything downstream.",[310,359,361],{"id":360},"step-3-choose-verification-methods-that-fit-real-life","Step 3, Choose verification methods that fit real life",[13,363,364],{},"Mobile GPS is the most common, but plan for the field: spotty rural connectivity, members without smartphones, and shared living settings. Make sure your method has an offline mode and a clean exception process.",[310,366,368],{"id":367},"step-4-train-dsps-on-clock-inclock-out-discipline","Step 4, Train DSPs on clock-in\u002Fclock-out discipline",[13,370,371],{},"The most common EVV failures are human: forgetting to clock in, clocking in from the wrong location, or fixing it later without a reason. Train staff to verify at the point of care, every time.",[310,373,375],{"id":374},"step-5-build-a-manual-edit-policy","Step 5, Build a manual-edit policy",[13,377,378],{},"Edits will happen. Define who may edit, what reason codes are valid, and how every edit is logged. Unexplained edits are an audit magnet.",[310,380,382],{"id":381},"step-6-reconcile-evv-to-claims-before-you-bill","Step 6, Reconcile EVV to claims before you bill",[13,384,385],{},"No claim should go out without a matching verified visit. Reconcile daily or weekly so you catch missing or unmatched visits while they're still fixable.",[25,387,389],{"id":388},"common-pitfalls","Common pitfalls",[30,391,392,395,398,401,404],{},[33,393,394],{},"Treating EVV as a payroll tool instead of a billing-integrity tool.",[33,396,397],{},"Letting clock-in\u002Fout drift from the actual service time.",[33,399,400],{},"High volumes of manual edits with vague or missing reasons.",[33,402,403],{},"No reconciliation step, so EVV gaps surface only at audit.",[33,405,406],{},"Choosing a system that can't operate offline in the field.",[183,408],{},[13,410,411],{},[188,412,413],{},"This guide provides general, federal\u002FCMS-level information about EVV and is not legal advice. EVV models, accepted verification methods, covered services, and edit rules vary by state and may differ across managed care organizations, verify the specific requirements of your state Medicaid agency before acting.",{"title":192,"searchDepth":193,"depth":193,"links":415},[416,417,421,429],{"id":245,"depth":193,"text":246},{"id":292,"depth":193,"text":293,"children":418},[419],{"id":312,"depth":420,"text":313},3,{"id":342,"depth":193,"text":343,"children":422},[423,424,425,426,427,428],{"id":346,"depth":420,"text":347},{"id":353,"depth":420,"text":354},{"id":360,"depth":420,"text":361},{"id":367,"depth":420,"text":368},{"id":374,"depth":420,"text":375},{"id":381,"depth":420,"text":382},{"id":388,"depth":193,"text":389},"What EVV is, the six data elements federal law requires you to capture, and a step-by-step path to getting your agency compliant and your claims clean.","i-heroicons-map-pin",{},"\u002Fresources\u002Fevv-readiness-guide",11,{"title":220,"description":430},[213],"resources\u002Fevv-readiness-guide","Guide","0TscXbBAexb60sMhN1FyLaY9EnhuFPgRrST99LoHf58",{"id":441,"title":442,"accentColor":443,"assetType":444,"body":445,"description":623,"extension":204,"icon":624,"meta":625,"navigation":207,"order":420,"path":626,"readTime":627,"seo":628,"states":629,"stem":630,"type":631,"updated":216,"__hash__":632},"toolkit\u002Fresources\u002Fservice-documentation-standards.md","Service Documentation Standards: What Every Billable Note Must Contain","bg-secondary-500","template",{"type":10,"value":446,"toc":616},[447,450,453,457,460,516,520,527,547,551,557,560,574,577,581,591,595,609,611],[13,448,449],{},"A billable service note has one job: to prove, after the fact, that an authorized service was actually delivered to a specific person, by a qualified person, for a documented amount of time, in pursuit of that person's goals. Most documentation problems come from notes that describe a feeling (\"good day\") instead of a service.",[13,451,452],{},"Use this as a team standard. Adapt the labels to your EHR, but keep the required elements.",[25,454,456],{"id":455},"the-required-elements","The required elements",[13,458,459],{},"Every billable note should answer all of these:",[30,461,462,468,474,480,486,492,498,504,510],{},[33,463,464,467],{},[17,465,466],{},"Who received the service",", the individual, clearly identified.",[33,469,470,473],{},[17,471,472],{},"Who delivered it",", staff name and credentials, with a signature.",[33,475,476,479],{},[17,477,478],{},"When",", date, and start\u002Fend time precise enough to support the units billed.",[33,481,482,485],{},[17,483,484],{},"Where",", service location (especially where EVV applies).",[33,487,488,491],{},[17,489,490],{},"What service",", the specific authorized service, named the way the plan of care names it.",[33,493,494,497],{},[17,495,496],{},"What happened",", a specific description of the support provided.",[33,499,500,503],{},[17,501,502],{},"Why it mattered",", how the activity connected to the individual's authorized goals.",[33,505,506,509],{},[17,507,508],{},"Outcome \u002F response",", how the individual responded or progressed.",[33,511,512,515],{},[17,513,514],{},"Signature & date",", signed by the person who delivered the service, at or near the time of service.",[25,517,519],{"id":518},"the-writing-rubric","The writing rubric",[13,521,522,523,526],{},"Train staff to write notes that are ",[17,524,525],{},"Specific, Service-linked, and Signed",":",[30,528,529,535,541],{},[33,530,531,534],{},[17,532,533],{},"Specific",", concrete actions and observations, not adjectives. \"Prompted to brush teeth, completed with two verbal cues\" beats \"good hygiene.\"",[33,536,537,540],{},[17,538,539],{},"Service-linked",", the note describes the authorized service and ties to a plan goal, not just an activity.",[33,542,543,546],{},[17,544,545],{},"Signed",", authored, dated, and attributed to the person who was there. Corrections are added as new dated entries, never written over the original.",[25,548,550],{"id":549},"good-vs-weak-examples","Good vs. weak examples",[13,552,553,556],{},[17,554,555],{},"Weak:"," \"Client had a good day. Went into the community.\"",[13,558,559],{},"Why it fails: no service named, no goal link, no specifics, no time, nothing an auditor can verify.",[13,561,562,565,566,570,571,573],{},[17,563,564],{},"Strong:"," \"Community integration, 10:05–11:35. Supported ",[567,568,569],"span",{},"individual"," on a planned grocery trip toward goal of independent shopping. Provided verbal prompts to locate items from a written list; ",[567,572,569],{}," completed 6 of 8 items independently and used self-checkout with one prompt. Calm and engaged throughout. Next session: practice handling payment independently.\"",[13,575,576],{},"Why it works: names the service, ties to a goal, documents specific support and the individual's response, supports the time billed, and sets up continuity.",[25,578,580],{"id":579},"a-reusable-note-skeleton","A reusable note skeleton",[582,583,588],"pre",{"className":584,"code":586,"language":587},[585],"language-text","Service: [authorized service name]\nIndividual: [name \u002F ID]\nDate: [date]   Time: [start]–[end]\nLocation: [location]\nGoal addressed: [goal from the plan of care]\nSupport provided: [specific actions, prompts, assistance]\nIndividual's response\u002Fprogress: [what happened, how they responded]\nFollow-up \u002F next steps: [continuity]\nStaff: [name, credentials]   Signature: ____   Date signed: [date]\n","text",[589,590,586],"code",{"__ignoreMap":192},[25,592,594],{"id":593},"quality-check-before-it-counts","Quality-check before it counts",[30,596,597,600,603,606],{},[33,598,599],{},"Could a reviewer who wasn't there understand exactly what service was delivered and why?",[33,601,602],{},"Does the documented time support the units being billed?",[33,604,605],{},"Is it tied to an authorized goal in a current plan of care?",[33,607,608],{},"Is it signed and dated by the person who delivered the service?",[183,610],{},[13,612,613],{},[188,614,615],{},"This standard offers general, federal\u002FCMS-level documentation guidance and is not legal advice. Required note elements, signature rules, and billing standards vary by state, waiver program, and payer, confirm the specifics for your programs before adopting.",{"title":192,"searchDepth":193,"depth":193,"links":617},[618,619,620,621,622],{"id":455,"depth":193,"text":456},{"id":518,"depth":193,"text":519},{"id":549,"depth":193,"text":550},{"id":579,"depth":193,"text":580},{"id":593,"depth":193,"text":594},"A reusable standard your whole team can follow so every progress note holds up to billing review. Includes the required elements, a writing rubric, and good vs. weak examples.","i-heroicons-document-text",{},"\u002Fresources\u002Fservice-documentation-standards",8,{"title":442,"description":623},[213],"resources\u002Fservice-documentation-standards","Template","7vuW7_ns5pxYEPAk0JJ7FGxvKs9FLpDndRIQwZ7Xfrs",{"id":634,"title":635,"accentColor":636,"assetType":222,"body":637,"description":837,"extension":204,"icon":838,"meta":839,"navigation":207,"order":840,"path":841,"readTime":210,"seo":842,"states":843,"stem":844,"type":438,"updated":216,"__hash__":845},"toolkit\u002Fresources\u002Fcritical-incident-reporting-guide.md","Critical Incident Reporting & Response Guide","bg-red-500",{"type":10,"value":638,"toc":825},[639,642,649,653,656,704,707,711,714,740,744,748,763,767,770,774,781,785,788,790,807,811,818,820],[13,640,641],{},"Incident management is one of the core assurances CMS expects of every HCBS program: states must demonstrate that providers identify, report, respond to, and learn from incidents that affect the health and welfare of the people they serve. A weak incident process is both a safety risk and an audit finding.",[13,643,644,645,648],{},"This guide gives you a state-agnostic framework. The categories and timeframes below are typical, ",[17,646,647],{},"your state defines the exact reportable categories and deadlines",", so map this to your own requirements.",[25,650,652],{"id":651},"what-is-typically-reportable","What is typically reportable",[13,654,655],{},"Most state systems require reporting of incidents such as:",[30,657,658,664,670,676,682,687,692,698],{},[33,659,660,663],{},[17,661,662],{},"Death"," of an individual receiving services.",[33,665,666,669],{},[17,667,668],{},"Serious injury"," or a medical emergency requiring treatment beyond first aid.",[33,671,672,675],{},[17,673,674],{},"Abuse, neglect, or exploitation",", alleged, suspected, or confirmed.",[33,677,678,681],{},[17,679,680],{},"Medication errors"," with potential or actual harm.",[33,683,684],{},[17,685,686],{},"Missing person \u002F elopement.",[33,688,689],{},[17,690,691],{},"Use of restraint or restrictive intervention.",[33,693,694,697],{},[17,695,696],{},"Law enforcement involvement"," related to an individual.",[33,699,700,703],{},[17,701,702],{},"Significant property or environmental events"," affecting safety.",[13,705,706],{},"When in doubt, report. Under-reporting is treated far more harshly than over-reporting.",[25,708,710],{"id":709},"respond-first-document-second","Respond first, document second",[13,712,713],{},"The order matters. In the moment:",[161,715,716,722,728,734],{},[33,717,718,721],{},[17,719,720],{},"Ensure immediate safety",", provide or summon medical help; remove the danger.",[33,723,724,727],{},[17,725,726],{},"Notify"," as required, emergency services, supervisor, guardian\u002Ffamily, and any mandated authorities.",[33,729,730,733],{},[17,731,732],{},"Preserve information",", note times, who was present, what was observed (facts, not conclusions).",[33,735,736,739],{},[17,737,738],{},"File the formal report"," within your state's required timeframe.",[25,741,743],{"id":742},"a-reporting-workflow-that-holds-up","A reporting workflow that holds up",[310,745,747],{"id":746},"tier-the-timeline","Tier the timeline",[13,749,750,751,754,755,758,759,762],{},"Separate ",[17,752,753],{},"immediate notifications"," (often within hours for the most serious incidents) from the ",[17,756,757],{},"full written report"," (often within 24–72 hours) and any ",[17,760,761],{},"follow-up\u002Fcloseout report",". Build these deadlines into your system so nothing is reported late.",[310,764,766],{"id":765},"capture-facts-not-opinions","Capture facts, not opinions",[13,768,769],{},"A report should record what was observed and done, times, actions, people involved, not speculation about cause or blame. Conclusions come from the review, not the first report.",[310,771,773],{"id":772},"assign-every-incident-an-owner-and-a-closeout","Assign every incident an owner and a closeout",[13,775,776,777,780],{},"An open incident isn't finished until follow-up actions are completed and documented: medical follow-up, plan-of-care changes, retraining, or referrals. Auditors look for the ",[17,778,779],{},"loop being closed",", not just the initial report.",[310,782,784],{"id":783},"review-for-patterns","Review for patterns",[13,786,787],{},"Aggregate incidents periodically. Three minor medication errors on the same shift is a systems signal, not three isolated events. Pattern review is what turns reporting into prevention, and it's exactly what CMS wants to see.",[25,789,389],{"id":388},[30,791,792,795,798,801,804],{},[33,793,794],{},"Treating the form as the goal instead of the response.",[33,796,797],{},"Late reports because deadlines live in someone's head, not the system.",[33,799,800],{},"Reports full of conclusions (\"staff was negligent\") instead of observations.",[33,802,803],{},"Incidents that are reported but never closed out with follow-up.",[33,805,806],{},"No trend review, so the same root cause recurs.",[25,808,810],{"id":809},"build-your-reportable-incident-reference","Build your reportable-incident reference",[13,812,813,814,817],{},"Create a one-page table for your team that lists, for ",[17,815,816],{},"your"," state and programs: each reportable category, who must be notified, the notification deadline, the written-report deadline, and where it gets filed. Post it where staff actually work.",[183,819],{},[13,821,822],{},[188,823,824],{},"This guide provides general, federal\u002FCMS-level information on HCBS incident management and is not legal advice. Reportable categories, notification requirements, and deadlines are defined by your state Medicaid agency and other authorities (including adult\u002Fchild protective services and licensing bodies) and vary significantly, confirm your exact obligations.",{"title":192,"searchDepth":193,"depth":193,"links":826},[827,828,829,835,836],{"id":651,"depth":193,"text":652},{"id":709,"depth":193,"text":710},{"id":742,"depth":193,"text":743,"children":830},[831,832,833,834],{"id":746,"depth":420,"text":747},{"id":765,"depth":420,"text":766},{"id":772,"depth":420,"text":773},{"id":783,"depth":420,"text":784},{"id":388,"depth":193,"text":389},{"id":809,"depth":193,"text":810},"What counts as a reportable incident, how to respond in the moment, and how to build a reporting workflow that meets CMS health-and-welfare expectations without burying your team in paperwork.","i-heroicons-exclamation-triangle",{},4,"\u002Fresources\u002Fcritical-incident-reporting-guide",{"title":635,"description":837},[213],"resources\u002Fcritical-incident-reporting-guide","Xp9t8WkjVICfxMVM5A0brNfn6-vmg_-WaGmqcWswbLg",{"id":847,"title":848,"accentColor":849,"assetType":8,"body":850,"description":987,"extension":204,"icon":988,"meta":989,"navigation":207,"order":990,"path":991,"readTime":992,"seo":993,"states":994,"stem":995,"type":215,"updated":216,"__hash__":996},"toolkit\u002Fresources\u002Fnew-dsp-compliance-onboarding-checklist.md","New DSP Compliance Onboarding Checklist","bg-slateSuccess-500",{"type":10,"value":851,"toc":979},[852,858,861,865,890,894,920,924,935,939,947,951,959,963,969,972,974],[13,853,854,855],{},"Here's a costly, common mistake: a new DSP starts delivering services before their file is complete, the agency bills for it, and an audit later disallows every one of those claims because a background check or required training wasn't on file on the date of service. ",[17,856,857],{},"A staff member is only billable once their qualifications are documented and current.",[13,859,860],{},"Use this checklist to gate that first billable shift. Nothing below should be \"in progress\" when the DSP starts delivering services.",[25,862,864],{"id":863},"pre-employment-eligibility","Pre-employment & eligibility",[30,866,867,870,873,880,887],{},[33,868,869],{},"Application, resume, and verified references on file.",[33,871,872],{},"Identity and work-authorization verification completed.",[33,874,875,876,879],{},"All required ",[17,877,878],{},"background checks"," completed and cleared (criminal, and where applicable abuse\u002Fneglect registry, sex-offender registry, and exclusion-list checks).",[33,881,882,883,886],{},"Confirmation the individual is ",[17,884,885],{},"not on any federal or state exclusion list"," (excluded individuals cannot be paid with Medicaid funds).",[33,888,889],{},"Required licenses or certifications verified as current and authentic.",[25,891,893],{"id":892},"required-training-before-first-service","Required training (before first service)",[30,895,896,899,902,905,908,911,914,917],{},[33,897,898],{},"Agency policies, code of conduct, and mandatory-reporter responsibilities.",[33,900,901],{},"HIPAA \u002F privacy and security.",[33,903,904],{},"Person-centered practices and rights of the individuals served.",[33,906,907],{},"Abuse, neglect, and exploitation prevention and reporting.",[33,909,910],{},"Incident reporting procedures and emergency response.",[33,912,913],{},"Documentation standards and how to write a compliant service note.",[33,915,916],{},"EVV clock-in\u002Fclock-out procedure (where applicable).",[33,918,919],{},"Any service-specific or individual-specific training required by the plan of care (e.g., medication administration, transfers, behavior support plan).",[25,921,923],{"id":922},"competency-sign-off","Competency & sign-off",[30,925,926,929,932],{},[33,927,928],{},"Documented competency check for the specific services and supports the DSP will provide.",[33,930,931],{},"Supervisor sign-off that the DSP is cleared to work independently.",[33,933,934],{},"Date the DSP became eligible to deliver billable services is recorded.",[25,936,938],{"id":937},"systems-access","Systems & access",[30,940,941,944],{},[33,942,943],{},"DSP set up in scheduling, documentation, and EVV systems with appropriate (least-privilege) access.",[33,945,946],{},"Login tested and the DSP can complete a real note and an EVV check-in.",[25,948,950],{"id":949},"record-keeping","Record-keeping",[30,952,953,956],{},[33,954,955],{},"All of the above stored in the personnel file and retrievable on request.",[33,957,958],{},"A renewal tracker is in place for anything that expires (background checks, certifications, annual training) so no one drifts out of compliance mid-employment.",[25,960,962],{"id":961},"the-one-rule-to-enforce","The one rule to enforce",[964,965,966],"blockquote",{},[13,967,968],{},"Do not schedule a new DSP for a billable service until the eligibility date is recorded and every \"before first service\" item is complete and on file.",[13,970,971],{},"Build that gate into your scheduling system if you can, it's far cheaper than disallowed claims and a corrective action plan.",[183,973],{},[13,975,976],{},[188,977,978],{},"This checklist provides general, federal\u002FCMS-level guidance and is not legal advice. Specific background-check requirements, required training, competency standards, and timelines vary by state, waiver program, and service type, confirm your exact requirements with your state Medicaid agency and licensing authorities.",{"title":192,"searchDepth":193,"depth":193,"links":980},[981,982,983,984,985,986],{"id":863,"depth":193,"text":864},{"id":892,"depth":193,"text":893},{"id":922,"depth":193,"text":923},{"id":937,"depth":193,"text":938},{"id":949,"depth":193,"text":950},{"id":961,"depth":193,"text":962},"Everything that should be complete and on file before a new Direct Support Professional delivers a billable service, so you never have to disallow a claim because a hire wasn't cleared yet.","i-heroicons-user-plus",{},5,"\u002Fresources\u002Fnew-dsp-compliance-onboarding-checklist",7,{"title":848,"description":987},[213],"resources\u002Fnew-dsp-compliance-onboarding-checklist","kYruHVqBaiXXwsCHV3lW80cj2AOp0rRwlyKUF6in-Hg",[998,1323,1563],{"id":999,"title":1000,"body":1001,"category":1308,"date":1309,"description":1310,"extension":204,"image":1311,"meta":1312,"navigation":207,"path":1319,"seo":1320,"stem":1321,"__hash__":1322},"news\u002Fnews\u002Fcommunity-integration-documentation-hcbs.md","Community Integration Services: What HCBS Agencies Need to Document for Compliance",{"type":10,"value":1002,"toc":1293},[1003,1006,1009,1012,1015,1017,1021,1024,1030,1036,1047,1050,1052,1056,1060,1063,1066,1069,1073,1076,1079,1082,1085,1089,1092,1115,1118,1122,1125,1129,1132,1135,1137,1141,1144,1147,1164,1167,1169,1173,1176,1182,1188,1194,1200,1206,1208,1212,1215,1221,1227,1233,1239,1245,1251,1257,1259,1263,1266,1269,1272,1274,1278,1281,1284],[13,1004,1005],{},"There is a quiet shift happening across the HCBS sector. State Medicaid agencies, pushed by the 2014 CMS HCBS Settings Rule, have been steadily moving provider agencies away from purely facility-based day services and toward something with a longer name and higher expectations: community integration.",[13,1007,1008],{},"In Louisiana it is called Community Life Engagement. Ohio and Texas call it Community Integration. Florida uses Community Inclusion. The billing codes differ by state. The documentation requirements, however, follow a consistent federal logic, and most agencies are not fully meeting them.",[13,1010,1011],{},"This is not a criticism. Community integration is genuinely harder to document than a 1:1 home visit or even a facility-based Day Program session. The service happens at a library, a park, an employer's office, or a grocery store. The location changes session to session. Multiple clients may participate, each with different goals. And unlike a home visit, there is no physical address pre-registered in your system that anchors the record.",[13,1013,1014],{},"This guide is for agency directors and quality assurance staff who want to understand what compliant community integration documentation actually requires, and where most agencies fall short.",[183,1016],{},[25,1018,1020],{"id":1019},"what-the-cms-settings-rule-actually-says","What the CMS Settings Rule Actually Says",[13,1022,1023],{},"The 2014 CMS HCBS Final Rule drew a sharp line between two categories of service settings:",[13,1025,1026,1029],{},[17,1027,1028],{},"Provider-operated facilities",", a company-owned or leased day center. The client comes to you. This covers traditional Day Program.",[13,1031,1032,1035],{},[17,1033,1034],{},"Community settings",", the broader community: public spaces, employers, retail environments, recreational facilities. The client goes out into the world with DSP support. This is community integration.",[13,1037,1038,1039,1042,1043,1046],{},"The rule requires that community integration services actually take place in community settings, not in agency facilities dressed up with community-sounding names. More importantly, it requires that documentation demonstrates this. An auditor reviewing a CLE claim should be able to look at the record and see ",[188,1040,1041],{},"where"," the session happened, ",[188,1044,1045],{},"what"," was done there, and how it connected to the individual's goals.",[13,1048,1049],{},"A sign-in sheet and a general note that says \"community outing\" does not meet that standard.",[183,1051],{},[25,1053,1055],{"id":1054},"the-five-documentation-requirements-that-matter","The Five Documentation Requirements That Matter",[310,1057,1059],{"id":1058},"_1-community-location-specifically-where-not-just-community-outing","1. Community Location, Specifically Where, Not Just \"Community Outing\"",[13,1061,1062],{},"Every community integration session must document the specific location or locations visited. This means a name and address, \"East Baton Rouge Public Library, 7711 Goodwood Blvd\", not a category like \"library\" and not a vague description like \"out in the community.\"",[13,1064,1065],{},"This matters for two reasons. First, auditors verify that services are happening in genuine community settings and not in your facility. Second, for states that bill community integration at different rates based on the type of setting (an employer site vs. a recreational setting, for example), the location type directly affects billing legitimacy.",[13,1067,1068],{},"One additional complication: a single community integration session often involves more than one stop. A DSP might take a client to a grocery store and then to a bank in the same session block. Both locations need to be documented, not just the first one.",[310,1070,1072],{"id":1071},"_2-individual-goal-progress-required-not-optional","2. Individual Goal Progress, Required, Not Optional",[13,1074,1075],{},"This is where most agencies are most exposed.",[13,1077,1078],{},"CMS policy classifies individual progress toward goals as a required daily documentation field for community integration sessions, not an optional add-on. A session note that documents location and activities but omits goal progress is technically incomplete, and in a Medicaid audit, an incomplete note is a non-billable note.",[13,1080,1081],{},"The practical implication: your DSPs need to know, at session time, what each client's active goals are. They need to record progress for each goal, achieved, partially met, not attempted, or refused. And if a client refused or was unable to work toward a goal, the reason should be captured.",[13,1083,1084],{},"This requires more than just telling DSPs to \"track goals.\" It requires that goals are entered into the system before sessions begin, linked to the individual's schedule, and surfaced automatically when the DSP opens the session. If your DSPs are manually looking up goals from a paper support plan while managing four clients in a community setting, this step gets skipped.",[310,1086,1088],{"id":1087},"_3-activities-and-skills-practiced","3. Activities and Skills Practiced",[13,1090,1091],{},"Beyond goals, documentation should capture what specifically happened during the session. The CMS activity categories that tend to appear in state policy include:",[30,1093,1094,1097,1100,1103,1106,1109,1112],{},[33,1095,1096],{},"Volunteering and civic participation",[33,1098,1099],{},"Adult education and vocational exploration",[33,1101,1102],{},"Recreation and fitness",[33,1104,1105],{},"Social clubs and community groups",[33,1107,1108],{},"Travel training and transportation independence",[33,1110,1111],{},"Daily living skills practiced in natural settings (grocery shopping, banking, meal preparation)",[33,1113,1114],{},"Career exploration and supported employment activities",[13,1116,1117],{},"This is not a checklist to complete for its own sake. This data becomes the monthly aggregated record that demonstrates the breadth and quality of your community integration programming, which is increasingly what states use to evaluate provider quality.",[310,1119,1121],{"id":1120},"_4-time-in-and-time-out","4. Time In and Time Out",[13,1123,1124],{},"Standard across all Medicaid waiver services, but worth stating explicitly: community integration sessions require documented time in and time out for each client. For EVV-required services, this also means electronic verification tied to the actual community location, not your facility address.",[310,1126,1128],{"id":1127},"_5-staff-signature-and-supervisor-review","5. Staff Signature and Supervisor Review",[13,1130,1131],{},"Daily documentation requires a DSP signature. Most agencies have this. What many are missing is the supervisor review layer.",[13,1133,1134],{},"CMS policy and most state CLE regulations include a requirement that supervisors review session notes, not every note the same day, but on a regular basis, and flag sessions with missing or incomplete documentation before billing is submitted. Agencies that skip this layer are submitting claims without a quality check, which is an audit risk regardless of how carefully their DSPs document.",[183,1136],{},[25,1138,1140],{"id":1139},"the-monthly-aggregation-requirement","The Monthly Aggregation Requirement",[13,1142,1143],{},"Individual session notes are the foundation. The structure built on top of them is the monthly summary, and it is not optional.",[13,1145,1146],{},"Most state CLE regulations require that agencies (or their software) aggregate session data over a billing period into a monthly summary that shows, per individual:",[30,1148,1149,1152,1155,1158,1161],{},[33,1150,1151],{},"Total sessions and attendance",[33,1153,1154],{},"Community locations visited (unique locations and total visits)",[33,1156,1157],{},"Activities completed, broken down by category",[33,1159,1160],{},"Skills practiced and engagement levels",[33,1162,1163],{},"Goal progress over the period, which goals advanced, which were not attempted, and how often",[13,1165,1166],{},"This monthly record is what a Medicaid auditor or state QA reviewer is likely to ask for when auditing community integration billing. Generating it manually from individual session notes is a significant administrative burden. Agencies that can produce it quickly are in a much stronger position during reviews.",[183,1168],{},[25,1170,1172],{"id":1171},"where-most-agencies-fall-short","Where Most Agencies Fall Short",[13,1174,1175],{},"Based on the documentation requirements above, the most common gaps are:",[13,1177,1178,1181],{},[17,1179,1180],{},"Vague location documentation."," \"Community outing\" or \"community trip\" in place of a specific address. This is the most frequent finding in CLE audits.",[13,1183,1184,1187],{},[17,1185,1186],{},"Missing or inconsistent goal tracking."," Goals are maintained on paper or in a separate system and are not consistently surfaced to DSPs at session time. Goal progress is therefore inconsistently documented or omitted.",[13,1189,1190,1193],{},[17,1191,1192],{},"No multi-stop documentation."," Sessions that visit more than one location are documented with only one, leaving a gap in the record.",[13,1195,1196,1199],{},[17,1197,1198],{},"No supervisor review before billing."," Session notes go directly from DSP submission to billing without a QA layer. This is fine until one incomplete note triggers a recoupment.",[13,1201,1202,1205],{},[17,1203,1204],{},"Monthly summaries produced manually."," Administrators compile monthly summaries from individual notes by hand, which is time-consuming, error-prone, and not scalable as census grows.",[183,1207],{},[25,1209,1211],{"id":1210},"what-a-good-documentation-workflow-looks-like","What a Good Documentation Workflow Looks Like",[13,1213,1214],{},"A compliant community integration documentation workflow follows roughly this sequence:",[13,1216,1217,1220],{},[17,1218,1219],{},"Before sessions begin:"," The supervisor enters the client's active community integration goals into the system and links them to the client's CLE schedule. This is a one-time setup that holds until goals change, not something that happens every session.",[13,1222,1223,1226],{},[17,1224,1225],{},"At session start:"," The DSP opens the session on their mobile device. The client's goals appear automatically, pre-populated from the schedule. The DSP does not need to look them up.",[13,1228,1229,1232],{},[17,1230,1231],{},"During the session:"," As the group visits community locations, the DSP captures each location, name, address, and type. This can be as simple as using the phone's GPS to confirm the location rather than typing an address from scratch.",[13,1234,1235,1238],{},[17,1236,1237],{},"At session end:"," The DSP records activities completed, selects skill categories practiced, notes engagement level, and records goal progress for each client using a simple status selector (achieved, partially met, not attempted, refused). A brief narrative note is added. Total session time is confirmed. The note is submitted.",[13,1240,1241,1244],{},[17,1242,1243],{},"This should take under five minutes."," If it takes longer, the workflow has too much friction and DSPs will shortcut it.",[13,1246,1247,1250],{},[17,1248,1249],{},"After submission:"," The supervisor reviews the session note before it enters the billing queue. Any missing fields, goal progress, location, time out, are flagged back to the DSP for correction before the claim is submitted.",[13,1252,1253,1256],{},[17,1254,1255],{},"Monthly close:"," The system aggregates the session data into the monthly summary automatically. The supervisor adds a narrative review and approves for billing.",[183,1258],{},[25,1260,1262],{"id":1261},"a-note-on-state-variation","A Note on State Variation",[13,1264,1265],{},"Everything above describes the federal CMS framework. Your state will add requirements on top of it.",[13,1267,1268],{},"Louisiana's Community Life Engagement has specific billing codes (H0043 HH for group, H0043 for individual) and documentation requirements that reflect the state's CLE policy framework. Ohio, Texas, and Florida have their own procedure codes and their own checklists for what session notes must contain. If you operate across multiple states, your documentation system needs to accommodate these differences without requiring a different workflow for each state.",[13,1270,1271],{},"The underlying documentation logic, location, goals, activities, supervisor review, monthly aggregation, is consistent across states. The labels and billing codes change.",[183,1273],{},[25,1275,1277],{"id":1276},"conclusion","Conclusion",[13,1279,1280],{},"Community integration services are among the most person-centered services an HCBS agency can offer, and they carry documentation requirements that reflect that complexity. The bar is higher than a home visit because the service is happening in dynamic, uncontrolled settings where the stakes, community access, skill building, employment readiness, are also higher.",[13,1282,1283],{},"Meeting that bar consistently requires a documentation system designed for group, community-based services. Not a home visit platform with an extra field for \"location.\"",[13,1285,1286,1287,1292],{},"At Cura OS, we are building exactly this kind of infrastructure for community integration and Day Program services. If you want to talk through how your agency is currently handling CLE documentation, ",[1288,1289,1291],"a",{"href":1290},"\u002Fcontact","we'd be glad to connect",".",{"title":192,"searchDepth":193,"depth":193,"links":1294},[1295,1296,1303,1304,1305,1306,1307],{"id":1019,"depth":193,"text":1020},{"id":1054,"depth":193,"text":1055,"children":1297},[1298,1299,1300,1301,1302],{"id":1058,"depth":420,"text":1059},{"id":1071,"depth":420,"text":1072},{"id":1087,"depth":420,"text":1088},{"id":1120,"depth":420,"text":1121},{"id":1127,"depth":420,"text":1128},{"id":1139,"depth":193,"text":1140},{"id":1171,"depth":193,"text":1172},{"id":1210,"depth":193,"text":1211},{"id":1261,"depth":193,"text":1262},{"id":1276,"depth":193,"text":1277},"compliance","2026-04-17","CMS requires more than a sign-in sheet for community integration services. Here's what compliant documentation actually looks like, locations, goals, activities, and the supervisor layer most agencies skip.",null,{"tags":1313,"readTime":1318},[1308,1314,1315,1316,1317],"community integration","CLE","documentation","HCBS",10,"\u002Fnews\u002Fcommunity-integration-documentation-hcbs",{"title":1000,"description":1310},"news\u002Fcommunity-integration-documentation-hcbs","p1uaa8c-Svvqyy7092pc9J4uSqwEbRenzhb4i7yRS7k",{"id":1324,"title":1325,"body":1326,"category":1552,"date":1309,"description":1553,"extension":204,"image":1311,"meta":1554,"navigation":207,"path":1559,"seo":1560,"stem":1561,"__hash__":1562},"news\u002Fnews\u002Fday-habilitation-documentation-software.md","Day Program Documentation: Built for Group Services",{"type":10,"value":1327,"toc":1543},[1328,1331,1334,1337,1340,1342,1346,1349,1352,1355,1361,1367,1373,1375,1379,1382,1388,1394,1400,1406,1412,1414,1418,1421,1424,1430,1436,1442,1445,1447,1451,1454,1457,1460,1463,1466,1468,1472,1475,1478,1481,1484,1486,1490,1493,1499,1505,1511,1517,1523,1529,1531,1533,1536],[13,1329,1330],{},"Picture a typical Monday morning at a Day Program center. Fifteen clients arrive by van. Three staff members get them settled. By 9:15 AM, the group is doing morning circle. By 10:00, they have moved to arts and crafts.",[13,1332,1333],{},"Now picture the DSP responsible for documenting this. If their agency is running Day Program through a platform designed for 1:1 home visits, their phone looks like this: fifteen individual visit cards, one per client, each waiting to be documented separately. Morning circle gets entered fifteen times. Arts and crafts gets entered fifteen times. If three clients arrived late and one did not show, those exceptions get handled across fifteen records.",[13,1335,1336],{},"By the time the session ends at 3:00 PM, the DSP has spent the better part of an hour doing administrative work that could have taken ten minutes, entering the same information over and over for clients who were all in the same room doing the same things.",[13,1338,1339],{},"This is not a niche complaint. It is one of the most consistent frustrations voiced by Day Program staff and the administrators who supervise them. And it exists entirely because most HCBS software was not designed for group services.",[183,1341],{},[25,1343,1345],{"id":1344},"why-most-platforms-handle-day-program-poorly","Why Most Platforms Handle Day Program Poorly",[13,1347,1348],{},"Home and Community-Based Services software has historically been built around the home visit: one DSP, one client, one location, one set of tasks. That model works well for personal care, supported living, and in-home respite. It is a poor fit for Day Program, where the fundamental unit of service is a group, not an individual visit.",[13,1350,1351],{},"The problem is not that these platforms cannot store Day Program data, most can. The problem is that they require staff to interact with the service as if it were fifteen simultaneous home visits, because that is the data model underneath. Each client has a visit record. Each visit record needs to be opened, documented, and submitted. The fact that all fifteen clients were doing the same activity at the same time is invisible to the system.",[13,1353,1354],{},"The downstream effects go beyond inconvenience:",[13,1356,1357,1360],{},[17,1358,1359],{},"Documentation quality suffers."," When entering data fourteen more times after the first entry feels like busywork, staff start abbreviating. Notes get thinner. Exceptions get skipped. The documentation becomes less accurate, not more.",[13,1362,1363,1366],{},[17,1364,1365],{},"Compliance risk increases."," Incomplete or inconsistent notes across a group session create discrepancies. If twelve clients have a note that says \"Arts and Crafts, 10:00–11:00 AM\" and three have nothing, the billing for those three clients is exposed in an audit regardless of whether they actually participated.",[13,1368,1369,1372],{},[17,1370,1371],{},"DSP burnout accelerates."," Staff who spend an hour at the end of a six-hour shift entering repetitive data are spending an hour on something they correctly perceive as unnecessary. In a sector with persistent staffing challenges, administrative friction matters.",[183,1374],{},[25,1376,1378],{"id":1377},"what-day-program-documentation-actually-requires","What Day Program Documentation Actually Requires",[13,1380,1381],{},"To understand what the right approach looks like, it helps to walk through what Day Program documentation actually needs to capture.",[13,1383,1384,1387],{},[17,1385,1386],{},"Attendance."," Who was present, who was absent, who arrived late or left early, and why. For a group of fifteen, this means a quick pass to confirm everyone who showed up, then individual notes for exceptions. It does not mean opening fifteen separate check-in records.",[13,1389,1390,1393],{},[17,1391,1392],{},"Group activities."," What the group did during the session, morning circle, arts and crafts, music therapy, community outing, lunch preparation. These activities happen at the group level. They need to be logged once, with participation noted per client. A client who opted out of an activity due to sensory sensitivity should have that noted on their individual record; everyone else simply participates.",[13,1395,1396,1399],{},[17,1397,1398],{},"Individual notes."," Within a group session, individual clients still have individual needs. A behavioral incident, a progress note on a specific goal, a health observation, these belong to the individual, not the group. Good documentation software keeps the group view and the individual view connected, so a DSP can log a group activity and then tap into a specific client's record for a personal note, without losing context.",[13,1401,1402,1405],{},[17,1403,1404],{},"Staff clock-in and clock-out."," Multiple staff are often working the same session. Each needs their own time record, tied to the session rather than managed separately.",[13,1407,1408,1411],{},[17,1409,1410],{},"EVV where required."," Electronic Visit Verification requirements for Day Program vary by state. Where EVV applies, the check-in and check-out need to be captured at the session level, not duplicated across every client record.",[183,1413],{},[25,1415,1417],{"id":1416},"the-session-model-a-different-way-of-thinking-about-group-services","The Session Model: A Different Way of Thinking About Group Services",[13,1419,1420],{},"The design shift that makes Day Program documentation manageable is treating the session itself as the primary object, not the individual visit.",[13,1422,1423],{},"In a session-first model, DSPs see a single session card on their device rather than a list of individual visit cards. The session card shows the location, the time window, the number of clients, and the staff assigned. Tapping it opens a session view with three things: attendance, activities, and individual client access.",[13,1425,1426,1429],{},[17,1427,1428],{},"Attendance"," works from the assumption that everyone is present, then handles exceptions. A single tap marks all clients as arrived. The DSP then addresses the two who came late and the one who called in sick, individually, quickly, with a reason. This takes two minutes instead of fifteen.",[13,1431,1432,1435],{},[17,1433,1434],{},"Activities"," are logged once at the group level. The DSP selects the activity, sets the time window, and checks off participants. The default is everyone present; the exception is a client who did not participate, which gets a note. One entry creates documentation records for every participating client automatically.",[13,1437,1438,1441],{},[17,1439,1440],{},"Individual access"," is always available. Any client in the session can be tapped to add a personal note, record goal progress, or log an incident. This happens within the session context, so it is connected to the group record rather than floating as a separate visit entry.",[13,1443,1444],{},"The result is documentation that reflects how Day Program actually operates, as a coordinated group service, rather than forcing a group reality into a solo-visit mold.",[183,1446],{},[25,1448,1450],{"id":1449},"what-stays-the-same","What Stays the Same",[13,1452,1453],{},"One concern agencies frequently raise when evaluating group session tools is whether adopting them requires changing everything else: scheduling workflows, billing processes, compliance documentation.",[13,1455,1456],{},"The answer should be: nothing else changes.",[13,1458,1459],{},"Day Program clients are scheduled like any other service, service type, location, days, and times. The system should identify which clients are scheduled at the same location on the same day and group them automatically. Schedulers should not need to do anything differently.",[13,1461,1462],{},"Billing pulls from the same underlying data it always has: the client's authorization, the procedure code, the documented time. The group session model changes how that data is entered, not what data exists. Per-client documentation records are still generated, they are just created more efficiently through the group workflow rather than entered manually fifteen times.",[13,1464,1465],{},"Progress notes, incident reports, and EVV records are all still tied to individual clients. Nothing about the per-client compliance record changes. The group session model is about how staff interact with documentation during the session, it is not about what ends up in each client's file.",[183,1467],{},[25,1469,1471],{"id":1470},"state-naming-and-billing-codes","State Naming and Billing Codes",[13,1473,1474],{},"One structural challenge for agencies expanding across state lines, or for software built to serve them, is that the service is called something different in nearly every state.",[13,1476,1477],{},"Louisiana uses Day Habilitation (H2015). Ohio calls the equivalent service Adult Day Support (T2021). Texas uses Day Habilitation with a different procedure code (H2014). Florida calls it Adult Day Training. New York uses Day Habilitation with its own billing modifiers. California has Adult Day Programs.",[13,1479,1480],{},"The documentation requirements and the general workflow are similar across these states. What changes are the program names, the billing codes, and some state-specific compliance fields. A documentation platform that hard-codes Louisiana's naming into its interface creates a migration problem for any agency that operates in multiple states or switches Medicaid programs.",[13,1482,1483],{},"The better design: the platform stores program service names and billing codes as configurable data tied to the state, and the interface derives its labels and dropdowns from that configuration. When an Ohio agency uses the system, they see \"Adult Day Support\" where a Louisiana agency sees \"Day Habilitation.\" Same workflow, correct terminology.",[183,1485],{},[25,1487,1489],{"id":1488},"what-to-look-for-in-day-program-documentation-software","What to Look for in Day Program Documentation Software",[13,1491,1492],{},"If you are evaluating tools for Day Program documentation, the questions worth asking are specific:",[13,1494,1495,1498],{},[17,1496,1497],{},"Does the system have a session model or a visit model?"," Ask to see the DSP's view. If it shows individual visit cards for each client in a group, the system was not designed for group services.",[13,1500,1501,1504],{},[17,1502,1503],{},"How does attendance work?"," It should be bulk-first, mark everyone present, handle exceptions, not a per-client check-in process.",[13,1506,1507,1510],{},[17,1508,1509],{},"Can a group activity be logged once for all participants?"," If the answer is no, or if the workaround involves copying notes across records, the system will create documentation burden rather than reduce it.",[13,1512,1513,1516],{},[17,1514,1515],{},"Does billing change?"," It should not. The group session model should be an input layer that feeds the same billing data structure the agency already uses.",[13,1518,1519,1522],{},[17,1520,1521],{},"Does it handle state variation?"," If you operate in more than one state or anticipate doing so, confirm that program names and billing codes are configurable rather than hard-coded.",[13,1524,1525,1528],{},[17,1526,1527],{},"Does it work on mobile for DSPs in the field?"," Day Program staff are not at desks. The documentation flow needs to work on a phone, quickly, in a busy environment.",[183,1530],{},[25,1532,1277],{"id":1276},[13,1534,1535],{},"Day Program documentation does not have to mean fifteen entries for one session. The problem is not inherent to the service, it is a product of using tools built for a different service model. A session-first approach reduces documentation time, improves note quality, and removes one of the most persistent frustrations for Day Program staff.",[13,1537,1538,1539],{},"At Cura OS, we built our group sessions feature specifically for Day Program and community-based services, designed around how these services actually work, not adapted from a home visit model. ",[1288,1540,1542],{"href":1541},"\u002Ffeatures\u002Fday-habilitation","Learn more about how it works for your agency.",{"title":192,"searchDepth":193,"depth":193,"links":1544},[1545,1546,1547,1548,1549,1550,1551],{"id":1344,"depth":193,"text":1345},{"id":1377,"depth":193,"text":1378},{"id":1416,"depth":193,"text":1417},{"id":1449,"depth":193,"text":1450},{"id":1470,"depth":193,"text":1471},{"id":1488,"depth":193,"text":1489},{"id":1276,"depth":193,"text":1277},"operations","Most HCBS platforms were built for 1:1 home visits. When agencies use them for Day Program, DSPs end up documenting the same session 15 times. Here's what group-first documentation actually looks like.",{"tags":1555,"readTime":210},[1556,1316,1308,1557,1558],"day program","DSP","group services","\u002Fnews\u002Fday-habilitation-documentation-software",{"title":1325,"description":1553},"news\u002Fday-habilitation-documentation-software","3flVzV6DVLRF-XtEEqARO19q5Z3nA16xzedMDG9zDLs",{"id":1564,"title":1565,"body":1566,"category":1308,"date":1309,"description":1791,"extension":204,"image":1311,"meta":1792,"navigation":207,"path":1796,"seo":1797,"stem":1798,"__hash__":1799},"news\u002Fnews\u002Fhcbs-transportation-documentation-billing.md","Transportation in HCBS: Why It's a Documentation Problem, Not Just a Logistics Problem",{"type":10,"value":1567,"toc":1775},[1568,1571,1574,1577,1579,1583,1586,1590,1593,1596,1599,1602,1606,1609,1612,1615,1617,1621,1624,1628,1631,1634,1638,1641,1644,1648,1651,1654,1656,1660,1663,1666,1669,1672,1674,1678,1681,1684,1687,1689,1693,1696,1701,1712,1717,1731,1736,1744,1746,1750,1753,1756,1759,1761,1763,1766,1769],[13,1569,1570],{},"Most HCBS agency administrators think about transportation as a logistics problem. You have vans, you have routes, you have clients who need to get from home to your Day Program center and back. You coordinate drivers, manage schedules, and handle the inevitable late arrivals. That part is operational.",[13,1572,1573],{},"What agencies less often think about is the documentation side of transportation, and for Day Program and Community Integration services specifically, the documentation side is where the compliance risk lives.",[13,1575,1576],{},"This post is about that second problem: how transportation connects to your service records, what needs to be captured and why, and where agencies tend to have gaps that create billing exposure.",[183,1578],{},[25,1580,1582],{"id":1581},"two-services-two-different-transportation-realities","Two Services, Two Different Transportation Realities",[13,1584,1585],{},"Day Program and Community Integration both involve transporting clients. But the transportation dynamic is fundamentally different between the two, and so is the documentation requirement.",[310,1587,1589],{"id":1588},"day-program-transport-to-a-fixed-facility","Day Program: Transport to a Fixed Facility",[13,1591,1592],{},"In Day Program, transport is the handoff. Clients travel from their homes to your center, spend the day, and return home. Your facility is the known, registered destination, it is already in your scheduling system. The transportation itself is generally not billed as a separate service; it is either included in the Day Program rate, handled by a separate Medicaid transportation broker, or coordinated by the client's family.",[13,1594,1595],{},"The documentation challenge here is not about billing the trip. It is about what happens when transport goes wrong and how that connects to your session record.",[13,1597,1598],{},"A client who arrives forty-five minutes late because the van was delayed has a different attendance record than a client who arrived on time. That late arrival affects their documented time in, which affects billable units for that day. If your transportation records and your session attendance records live in separate systems, or if your DSP handles the late arrival by just checking the client in without noting the time, you have a discrepancy between what happened and what was documented.",[13,1600,1601],{},"Multiply this by a group of fifteen clients across multiple vans, some arriving on time and some not, and the reconciliation problem becomes significant.",[310,1603,1605],{"id":1604},"community-integration-transport-is-part-of-the-service","Community Integration: Transport Is Part of the Service",[13,1607,1608],{},"Community Integration is different in a more fundamental way. For CLE and similar services, transportation is not just a handoff to the service, it is often woven into the service itself.",[13,1610,1611],{},"When a DSP takes a group to a library, a grocery store, and a bank in one session, the travel between those locations is part of the community integration experience, particularly when travel training is one of the individual's documented goals. The vehicle used, the route taken, and the mileage covered are not just operational notes, they are potentially required documentation fields depending on your state's billing rules.",[13,1613,1614],{},"This is where the state variation becomes important.",[183,1616],{},[25,1618,1620],{"id":1619},"how-states-handle-transportation-billing-differently","How States Handle Transportation Billing Differently",[13,1622,1623],{},"There is no single Medicaid rule for how transportation relates to Day Program and Community Integration billing. It varies by state, and in some cases by the specific procedure code being billed. Understanding your state's model is the starting point for knowing what you need to document.",[310,1625,1627],{"id":1626},"when-transport-is-bundled-into-the-service-rate","When Transport Is Bundled Into the Service Rate",[13,1629,1630],{},"In Louisiana, transportation is included in the Day Habilitation rate (H2015) and in the Community Life Engagement rate (H0043). The agency is not submitting a separate claim for the trip. However, \"included in the rate\" does not mean \"not documented.\" It means the mileage and transport detail need to be recorded at the session level, not for a separate billing submission, but because state auditors can and do review transportation records as part of CLE compliance reviews.",[13,1632,1633],{},"Specifically, for CLE sessions: the community locations visited, the mileage covered between them, and the vehicle used should be captured in the session record. If a client's plan includes travel training as a goal, the documentation of how they traveled that day is part of the goal progress record.",[310,1635,1637],{"id":1636},"when-transport-is-billed-separately","When Transport Is Billed Separately",[13,1639,1640],{},"In states where non-emergency medical transportation (NEMT) is billed as a separate service alongside Day Program or Community Integration, the coordination requirement goes further. The trip record, origin, destination, vehicle, driver, times, needs to be linkable to the service session it was associated with. An auditor reviewing a Day Program claim alongside a transportation claim for the same client on the same day will expect those records to tell a consistent story.",[13,1642,1643],{},"If the Day Program session shows the client arriving at 9:45 AM and the transportation record shows a dropoff time of 9:10 AM, the discrepancy is a finding. Both records need to be accurate, and ideally they are connected in the same system rather than maintained separately and reconciled manually.",[310,1645,1647],{"id":1646},"the-multi-stop-problem-in-community-integration","The Multi-Stop Problem in Community Integration",[13,1649,1650],{},"For Community Integration sessions with multiple stops, the transportation documentation challenge compounds. A session that visits an employer site, then a grocery store, then a community recreation center has three distinct location records. If transportation is being tracked for compliance purposes, the sequence of stops, the mode of travel between them, and the total mileage all need to be captured.",[13,1652,1653],{},"This is not something most generic scheduling or documentation platforms handle well. The session record typically has one location field. A CLE session with three stops needs three location records, each with its own address, type, and timing, and the transportation record needs to connect the dots between them.",[183,1655],{},[25,1657,1659],{"id":1658},"the-attendance-transportation-connection-in-day-program","The Attendance-Transportation Connection in Day Program",[13,1661,1662],{},"Back to the Day Program context, there is a specific documentation gap that is worth naming directly: the disconnect between transport delays and attendance records.",[13,1664,1665],{},"Here is how it typically plays out. The van arrives twenty minutes late. The DSP at the center starts the session with the clients who are there. When the late clients come in, the DSP checks them in without recording the actual arrival time, because doing so requires opening each client's individual record, noting the time, and adding a reason, three extra steps per late client. Under documentation pressure, that step gets skipped.",[13,1667,1668],{},"The result: the session record shows all fifteen clients as present from session start, but three of them actually arrived forty-five minutes in. If billing is calculated on documented session time, those three clients are being billed for time they were not at the center. That is a billing compliance issue, and it is a direct consequence of the documentation system making it easier to skip the exception than to record it.",[13,1670,1671],{},"Good group session documentation makes handling transport-related exceptions fast enough that DSPs actually do it. The attendance flow should assume everyone is present and let staff handle exceptions quickly, tap a client, mark them late, note \"transport delay,\" done. The friction needs to be low enough that accuracy is the path of least resistance.",[183,1673],{},[25,1675,1677],{"id":1676},"vehicles-as-a-coordination-layer","Vehicles as a Coordination Layer",[13,1679,1680],{},"For agencies operating their own transport, vans or other vehicles assigned to Day Program locations or CLE routes, vehicle assignment is another documentation touchpoint that often gets handled informally.",[13,1682,1683],{},"Which van goes to which location, which driver is assigned, how many clients it is carrying, these are operational decisions made every morning and often never formally recorded. When a vehicle is involved in an incident, when a client claims they were in a different van than recorded, or when a state reviewer asks for documentation of your transport procedures, the informal coordination model creates exposure.",[13,1685,1686],{},"Linking vehicle assignment to the session record, which vehicle served which session, which clients it transported, closes that gap without creating a separate administrative workflow. It becomes part of the session setup rather than a separate logistics system.",[183,1688],{},[25,1690,1692],{"id":1691},"what-connected-transportation-documentation-looks-like","What Connected Transportation Documentation Looks Like",[13,1694,1695],{},"Bringing this together, connected transportation documentation for Day Program and Community Integration means a few specific things in practice:",[13,1697,1698],{},[17,1699,1700],{},"For Day Program:",[30,1702,1703,1706,1709],{},[33,1704,1705],{},"Client arrival times are recorded accurately at attendance, with transport delays noted as the reason for late check-ins",[33,1707,1708],{},"Vehicles assigned to the location are recorded at the session level",[33,1710,1711],{},"Transport-related attendance exceptions (late, early departure due to early transport pickup) are captured per client and reflected in billed time",[13,1713,1714],{},[17,1715,1716],{},"For Community Integration:",[30,1718,1719,1722,1725,1728],{},[33,1720,1721],{},"Each community location visited is documented with address, type, and timing, not just the first stop",[33,1723,1724],{},"Mileage covered between stops is recorded for states where it is a required documentation field",[33,1726,1727],{},"Where transport is bundled into the service rate, the session record contains enough detail to demonstrate compliance if reviewed",[33,1729,1730],{},"Where transport is billed separately, trip records are linked to the session they correspond to, so both claims tell a consistent story",[13,1732,1733],{},[17,1734,1735],{},"For both:",[30,1737,1738,1741],{},[33,1739,1740],{},"Transportation-related exceptions at attendance connect automatically to the billing record rather than requiring manual reconciliation",[33,1742,1743],{},"Vehicle and driver assignment is part of session setup, not informal coordination that lives only in someone's head",[183,1745],{},[25,1747,1749],{"id":1748},"the-practical-starting-point","The Practical Starting Point",[13,1751,1752],{},"If you are an agency director reading this and wondering where to start, the most useful first step is a documentation audit on one specific question: when a client arrives late due to transportation, how consistently is that arrival time recorded accurately in your session records today?",[13,1754,1755],{},"Pull a sample of Day Program sessions from the past month and compare documented check-in times against your transport logs or driver communications. The gap between those two records, if there is one, is your current compliance exposure.",[13,1757,1758],{},"The same exercise applies to CLE sessions: pick five sessions from the past month and verify that every community location visited appears in the session documentation. If some sessions show one location and your DSPs' notes or communications mention two or three stops, you have a documentation gap that needs to be addressed before billing those sessions becomes a liability.",[183,1760],{},[25,1762,1277],{"id":1276},[13,1764,1765],{},"Transportation in HCBS is easy to treat as a logistics function separate from your documentation and billing infrastructure. For Day Program and Community Integration specifically, that separation creates compliance gaps that are common, addressable, and worth understanding before an audit surfaces them.",[13,1767,1768],{},"The goal is not to add documentation burden. It is to connect the records that are already being kept, transport logs, vehicle assignments, attendance, so they tell a consistent story in the same place rather than living in separate systems that have to be reconciled by hand.",[13,1770,1771,1772],{},"At Cura OS, transportation coordination is built into the same platform as group session documentation and billing, so arrival times, vehicle assignments, and community stop records connect to the session automatically, not as a separate workflow. ",[1288,1773,1774],{"href":1290},"Talk to us about how it works for your agency.",{"title":192,"searchDepth":193,"depth":193,"links":1776},[1777,1781,1786,1787,1788,1789,1790],{"id":1581,"depth":193,"text":1582,"children":1778},[1779,1780],{"id":1588,"depth":420,"text":1589},{"id":1604,"depth":420,"text":1605},{"id":1619,"depth":193,"text":1620,"children":1782},[1783,1784,1785],{"id":1626,"depth":420,"text":1627},{"id":1636,"depth":420,"text":1637},{"id":1646,"depth":420,"text":1647},{"id":1658,"depth":193,"text":1659},{"id":1676,"depth":193,"text":1677},{"id":1691,"depth":193,"text":1692},{"id":1748,"depth":193,"text":1749},{"id":1276,"depth":193,"text":1277},"For Day Program and Community Integration agencies, transportation isn't just about getting clients there. How you document it, and whether it connects to your session records, directly affects compliance and billing.",{"tags":1793,"readTime":627},[1794,1556,1314,1795,1308,1317],"transportation","billing","\u002Fnews\u002Fhcbs-transportation-documentation-billing",{"title":1565,"description":1791},"news\u002Fhcbs-transportation-documentation-billing","jOrx8gWunDayT4MCQ378snzi3AoReYS813x8Y0mAcNw",1790093085258]