Organization-Specific ConfigurationQuality assurance checks are configured per organization. You define your own best practices, documentation standards, and validation rules. The system enforces both traditional scrubber rules and semantic expectations specific to your agency’s protocols.
Real-Time Validation
The system checks documentation as it’s created. Traditional scrubber rules catch missing signatures, incomplete time entries, and required field omissions. Beyond that, semantic rules check for clinical inconsistencies—if blood pressure is 80/40 but the patient is marked stable, it flags the contradiction. Missing OASIS items on Start of Care visits are highlighted. Wound measurements that don’t align with previous visits trigger alerts.Compliance Monitoring
Each visit type has specific requirements based on payer and regulations. The system knows what Medicare requires, what OASIS items are mandatory, and which assessments must be completed. Missing or incorrect elements are caught before submission.Cross-Visit Consistency
Documentation is validated against the patient’s history throughout the episode. Examples of semantic rules that track changes over time:- Medication Changes: If Metformin was added last visit but isn’t mentioned today, the system asks for confirmation—was it discontinued or just not discussed?
- Functional Decline: Patient could transfer independently at admission but now needs assistance—the system ensures you document what caused the change
- Wound Progression: A 2x3cm wound last week is now documented as 4x5cm—the system prompts for documentation of deterioration causes and treatment plan changes
- Pain Management: Pain was 8/10 on Monday’s visit but not mentioned Wednesday—the system flags this for follow-up
- Fall Risk Evolution: Patient had no fall history at SOC but reports a fall today—the system ensures fall risk reassessment and safety interventions are documented