Authorization Validation and Billing - Complete Guide
What Are Authorizations?
Authorizations are approvals from insurance companies that allow a patient to receive specific healthcare services. Think of them as "permission slips" that define:
- What services are approved (e.g., skilled nursing, physical therapy, home health aide)
- How much service is approved (hours per week, visits per month, etc.)
- When the service can be provided (start date, end date, specific days of the week)
- Any special limitations (maximum total hours, specific days only, etc.)
When you schedule a visit in the system, the authorization validation ensures that the visit complies with these insurance-approved limits.
Quick Start: Authorization Basics
When Do You Need an Authorization?
Whether an authorization is required depends on two factors:
1. Insurance Configuration
- If the insurance has "Authorization Required" = true, all visits need authorizations
- If "Authorization Required" = false, authorizations are optional but can still be used
2. Service Code Configuration
- Individual service codes can be marked as "Authorization Optional"
- This overrides the insurance requirement for that specific service
- Common for services like assessments or evaluations
CRITICAL: Authorization and Billing
The system ONLY bills visits that have authorizations linked.
- If a service code is marked "Authorization Optional" = true, you can schedule visits BUT they will NOT be billed
- Visits without authorizations are excluded from billing/invoicing
- "Authorization Optional" means optional for scheduling validation only, not optional for billing
- If you want a visit to be billed, it MUST have an authorization linked, regardless of the "Authorization Optional" setting
Bottom line: Authorization Optional = Can schedule without errors, but won't bill. To bill a visit, always link an authorization.
Example Scenarios
Scenario 1: Authorization Required - Will Bill
- Insurance: Medicare, Authorization Required = true
- Service: Skilled Nursing, Authorization Optional = false
- Validation: Must have authorization to schedule visit (warning if missing)
- Billing: Will bill if authorization is linked; won't bill without authorization
Scenario 2: Service Override - WON'T Bill Without Auth
- Insurance: Medicare, Authorization Required = true
- Service: Initial Assessment, Authorization Optional = true
- Validation: Can schedule without authorization (generates warning but allows save)
- Billing: ✗ Will NOT bill unless you manually add an authorization
- Use case: Initial assessments that you track but don't bill to insurance
Scenario 3: Optional Authorization - Still Need Auth to Bill
- Insurance: Private Pay, Authorization Required = false
- Service: Home Health Aide
- Validation: Authorization not required for scheduling (no warnings)
- Billing: ✗ Will NOT bill unless authorization is added
- Best practice: Always add authorization if you intend to bill the visit
Scenario 4: Non-Billable Service - Tracking Only
- Insurance: Any
- Service: Care Coordination Call, Authorization Optional = true
- Purpose: Track the activity in the system but never bill for it
- Action: Schedule without authorization
- Result: Tracked in system, ✗ excluded from billing
Understanding Authorization Types at a Glance
Regular Authorizations
What they are: Standard approvals from insurance companies
How they work: Define units (hours/visits) that renew on a schedule (daily, weekly, monthly)
When to use: This is your primary, go-to authorization for all standard scheduling
System behavior: Automatically selected and applied when you create a visit
Accumulation Authorizations
What they are: Automatically calculated "rollover" units from unused regular authorization hours/visits
How they work: System tracks unused units from past periods and makes them available
When to use: When you've exhausted current week/month authorization but patient has accumulated unused units
System behavior: Must be manually selected; requires special permission ("CanUseAccumulatedAuthUnits")
Learn more: See the separate "Accumulation Authorization User Guide" for detailed explanation
Common Authorization Scenarios
Scenario 1: Simple Weekly Authorization
Setup: Authorization for 20 hours per week, Monday-Friday
What happens:
- Every Sunday, patient gets a fresh 20 hours for the new week
- Can schedule up to 20 hours total for that week
- System automatically selects this authorization when scheduling visits
- If you try to schedule more than 20 hours, you'll get a warning
Scenario 2: Day-Specific Authorization
Setup: Authorization for 4 hours on Mon, Wed, Fri only
What happens:
- Can only schedule on Monday, Wednesday, Friday
- Each allowed day can have up to 4 hours
- Try to schedule Tuesday? System shows error
- Try to schedule 5 hours on Monday? System shows error
Scenario 3: Overnight Visit Spanning Two Days
Setup: Visit from Saturday 10 PM to Sunday 6 AM (8 hours)
Problem: Saturday's weekly authorization only has 2 hours remaining
Solution: Split Billing
- Bill 2 hours to Saturday (uses last hours of this week)
- Bill 6 hours to Sunday (uses hours from next week)
- Contract must have "Allow Splitting Auths" enabled
Scenario 4: Running Out of Hours Mid-Week
Setup: Authorization for 40 hours/week, already used 40 hours by Thursday
What happens:
- Try to schedule Friday? System warns no hours available
- Option 1: Wait until Sunday when new week starts (40 fresh hours)
- Option 2: Use accumulation authorization if patient has accumulated units
- Option 3: Contact insurance for authorization increase
Scenario 5: Authorization Expires During Coverage Period
Setup: Auth #100 ends 1/31/2025, Auth #200 starts 2/1/2025
What happens:
- Visits in January automatically use Auth #100
- Visits in February automatically use Auth #200
- Overnight visit 1/31 11 PM - 2/1 7 AM? Use split billing with both authorizations
Important: Validation vs. Hard Stops
The authorization validation system is designed to warn you about potential issues, but in most cases, it will still allow you to save the visit. This is intentional because:
- Clinical needs may override authorization limits - patient safety comes first
- Insurance may approve overages retroactively - you can't always wait for paperwork
- Authorization data may be temporarily incomplete - pending approvals, data entry delays
However: Just because you can save doesn't mean you should. Validation warnings often indicate:
- Potential billing denials from insurance
- Need for additional authorization from insurance
- Data entry errors that should be corrected
Best Practice: Investigate and resolve all validation warnings before finalizing visits
What This Guide Covers
This comprehensive guide is organized to take you from basic concepts to advanced troubleshooting:
- Section 1-2: Authorization types and structure (data model, period types, unit types)
- Section 3: How validation works (9-step validation process explained in detail)
- Section 4: Split billing for overnight visits (complete how-to with examples)
- Section 5: How billing reconciliation works (billing system implementation details)
- Section 6: How the system selects authorizations automatically
- Section 7: Technical validation rules and calculations
- Section 8: Configuration settings at insurance, contract, and user levels
- Section 9: Troubleshooting common errors with solutions
- Section 10: Real-world examples showing complete scenarios
How to use this guide:
- New users: Read sections 1-6 for foundational understanding
- Troubleshooting an error: Jump to section 9 for quick solutions
- Understanding specific scenarios: Check section 10 for examples
- Technical details: Sections 5, 7-8 provide deep dives into calculations and billing system internals
Table of Contents
- 1. Authorization Types
- 2. Understanding Authorization Structure
- 3. How Authorization Validation Works
- 4. Split Billing (Auth Billing)
- 5. Billing Reconciliation and System Implementation
- 6. How the System Selects Authorizations
- 7. Detailed Validation Rules
- 8. Configuration and Settings
- 9. Troubleshooting Common Issues
- 10. Real-World Examples
1. Authorization Types
The system supports two main types of authorizations:
Regular Authorizations
Type Code: Regular (1)
Purpose: Standard authorizations that define the approved units (hours or visits) for a specific service code and time period.
Characteristics:
- Can be verbal or written
- Define specific periods (daily, weekly, monthly, or entire authorization period)
- Can specify different units for different days of the week
- Can have maximum unit caps for the entire authorization period
- Automatically selected for scheduling when available
Accumulation Authorizations
Type Code: Accumulation (2)
Purpose: Automatically calculated authorizations that track unused units from regular authorizations, allowing patients to "roll over" unused hours/visits.
Characteristics:
- Created and maintained automatically by the system
- Share the same authorization number as their regular authorization counterparts
- Require special permission to use ("CanUseAccumulatedAuthUnits")
- Units are recalculated weekly and when schedules change
- Always show minimum of 0 units (never negative)
When to use: When a patient needs extra hours/visits beyond their regular weekly/monthly allocation, and they have accumulated unused units from previous periods.
Additional Authorization Flags
| Flag | Description | Impact on Validation |
|---|---|---|
| Verbal Authorization | Indicates the authorization was given verbally and is awaiting written confirmation | No impact on validation; for tracking purposes only |
| Terminated for Hospitalization | Authorization ended due to patient hospitalization | Authorization will not be available for scheduling after hospitalization date |
| Single Case Agreement | Special authorization negotiated for a specific case | No special validation; treated as regular authorization |
2. Understanding Authorization Structure
Core Components
Every authorization consists of two main parts:
Authorization Header
- Authorization Number: Unique identifier (max 36 characters)
- Authorization Date: Date the authorization was issued
- Start Date: First date the authorization is effective
- End Date: Last date the authorization is effective
- Chart Contract: Links to patient's insurance contract
- Authorization Type: Regular or Accumulation
Authorization Details (Service Codes)
Each authorization can contain multiple service codes, and each service code has its own configuration:
Unit Configuration
- Unit Type: Hours (H) or Visits (V)
- Units: Number of hours/visits allowed per period
- Period Type: Week (W), Month (M), Day (D), or entire Period (P)
Weekday Configuration
Controls which days of the week are allowed and how units are distributed:
- Weekdays UOM (Unit of Measure):
- Day: Specific days selected (e.g., Mon, Wed, Fri)
- Number: Any X days per week (e.g., any 5 days)
- Weekdays Value:
- For "Day" UOM: Bitwise selection (1=Sun, 2=Mon, 4=Tue, 8=Wed, 16=Thu, 32=Fri, 64=Sat)
- For "Number" UOM: Count of days allowed (e.g., 5)
- Weekdays Allowed to Vary: If true, can schedule on any day regardless of selection
Day-Specific Units (Weekly Authorizations)
For weekly authorizations, you can specify different units for each day:
- SunUnits, MonUnits, TueUnits, WedUnits, ThuUnits, FriUnits, SatUnits
- Example: Mon=4 hours, Tue=4 hours, Wed=2 hours, Thu=4 hours, Fri=4 hours
Maximum Units Cap
- MaxUnitsForAuthorization: Maximum total units allowed for the entire authorization period
- Example: Authorization is for 10 hours/week for 12 weeks, but max cap is 100 hours total
- System tracks "UnitsUsed" and validates against this cap
Period Types Explained
Week (W) - Most Common
Meaning: Authorization allowance renews every week
Example: 10 hours per week
How it works:
- Week starts on Sunday (configurable by insurance)
- Patient gets 10 fresh hours every Sunday
- Unused hours from previous weeks may accumulate (if accumulation is enabled)
Month (M)
Meaning: Authorization allowance renews every month
Example: 40 hours per month
How it works:
- Month starts on the 1st of each month
- Patient gets 40 fresh hours on the 1st
- Different months have different numbers of days
Day (D)
Meaning: Authorization allowance is per individual day
Example: 8 hours per day
How it works:
- Each day gets its own unit allowance
- Can be restricted to specific days of the week
- Can specify "any 5 days per week" constraint
Period (P)
Meaning: Authorization allowance is for the entire authorization period
Example: 100 hours total for authorization spanning 3 months
How it works:
- No weekly or monthly renewal
- Once units are used, they're gone
- Commonly used for rehabilitation or time-limited services
3. How Authorization Validation Works
When you schedule or confirm a visit, the system performs comprehensive validation through multiple layers. Understanding this process helps you anticipate and resolve authorization issues.
Validation Layers
1 Authorization Usage Validation
What it checks: Does the visit have at least one authorization linked?
Pass conditions:
- Visit has one or more authorizations linked, OR
- Service code is marked as "Authorization Optional"
Can save if failed: Yes (generates warning)
2 Authorization Date Validation
What it checks: Is the visit date within the authorization's effective dates?
Pass conditions:
- For regular schedules: Start and end dates both within authorization dates
- For overnight schedules: Start date within authorization, end date can be 1 day past
- For split billing: Each billing date checked against its respective authorization dates
Can save if failed: Yes (generates warning)
Example:
Authorization: 1/1/2025 - 1/31/2025
Visit 1: 1/15/2025 10:00 AM - 2:00 PM ✓ PASS
Visit 2: 2/1/2025 9:00 AM - 5:00 PM ✗ FAIL (starts after auth ends)
Overnight Visit: 1/31/2025 11:00 PM - 2/1/2025 7:00 AM ✓ PASS (allowed 1-day overage for overnight)
3 Authorization Units Available Validation (MOST COMPLEX)
What it checks: Comprehensive validation ensuring sufficient units are available
This validation includes multiple sub-checks (see detailed section below)
Can save if failed: Yes (generates warning), but may indicate billing issues
Detailed Units Available Validation Process
This is the most comprehensive validation rule. The system performs these checks in sequence:
Step 1: Prevent Duplicate Authorization Usage
Rule: Each authorization can only be linked once per billing date
Why: Prevents accidentally billing the same authorization multiple times
Example of violation:
- Visit on 1/15/2025 has Auth #12345 linked twice
- System blocks this to prevent double-billing
Step 2: Validate Split Billing is Allowed
Rule: If billing date differs from schedule date, contract must allow split billing
Why: Split billing requires special contract configuration
Example of violation:
- Overnight visit: 1/15/2025 11 PM - 1/16/2025 7 AM
- Trying to bill different authorizations to each date
- Contract has "AllowSplittingAuths = false"
Step 3: Check Maximum Units for Authorization
Rule: Total units used cannot exceed MaxUnitsForAuthorization
Why: Authorization may have a lifetime cap regardless of period type
Example:
- Authorization: 10 hours/week for 12 weeks, Max: 100 hours total
- Already used: 95 hours
- Trying to schedule: 8 hours
- Result: FAIL (would exceed 100-hour cap)
Step 4: Validate Day of Week Allowed
Rule: Schedule date must fall on an allowed day of the week
Why: Authorization may restrict service to specific days
Example:
- Authorization: Mon, Wed, Fri only (Weekdays Value = 42)
- Trying to schedule: Tuesday visit
- Result: FAIL (Tuesday not allowed)
Exception: If "Weekdays Allowed to Vary" is true, any day is allowed
Step 5: Calculate Period Dates and Load Usage
What happens: System determines the relevant period and loads all usage for that period
Period calculation examples:
- Week: If scheduling on Wed 1/15/2025, period is Sun 1/12/2025 - Sat 1/18/2025
- Month: If scheduling on 1/15/2025, period is 1/1/2025 - 1/31/2025
- Day: If scheduling on 1/15/2025, period is just 1/15/2025
- Period: If auth is 1/1/2025 - 3/31/2025, entire period is used
Usage includes:
- Confirmed visits in the period
- Other scheduled visits in the period (if they count)
- Current visit being scheduled/edited
Step 6: Validate Hours Available (for Hourly Authorizations)
Rule: Total hours used + hours being scheduled cannot exceed authorized hours for period
Calculation:
Example:
- Authorization: 40 hours per month
- Period: January 2025
- Already used: 35 hours
- Available: 40 - 35 = 5 hours
- Trying to schedule: 8 hours
- Result: FAIL (need 8 hours, only 5 available)
Step 7: Validate 24-Hour Daily Cap
Rule: No single day can exceed 24 hours per authorization
Why: Physical impossibility - only 24 hours in a day
Additional check: Total hours for billing date across ALL authorizations cannot exceed 24 hours
Example:
- Billing Date: 1/15/2025
- Auth A: 20 hours already scheduled for 1/15
- Trying to add: Auth A for 6 more hours on 1/15
- Result: FAIL (would be 26 hours in one day)
Step 8: Validate Number of Visits (for Visit-Based Authorizations)
Rule: Number of visits used + visits being scheduled cannot exceed authorized visits for period
Example:
- Authorization: 5 visits per week
- Week: 1/12/2025 - 1/18/2025
- Already scheduled: 4 visits
- Available: 5 - 4 = 1 visit
- Trying to schedule: 1 visit
- Result: PASS
Step 9: Validate Number of Days Per Week
Rule: If authorization limits number of days per week, cannot exceed that limit
Applies when: Weekdays UOM = "Number" (e.g., "any 5 days per week")
Example:
- Authorization: 8 hours per day, any 5 days per week
- Week: 1/12/2025 - 1/18/2025
- Already scheduled: Mon, Tue, Wed, Thu, Fri
- Trying to schedule: Saturday
- Result: FAIL (would be 6 days, only 5 allowed)
Special Case: Accumulation with Regular Authorization
Scenario: Using both a regular authorization and its accumulation authorization for a past week
Problem: Risk of double-counting units
Solution: System automatically reduces accumulation units by the regular authorization units applied
Example:
- Regular Auth #12345: 10 hours per week
- Accumulation Auth #12345: 15 hours available
- Scheduling visit for last week: 12 hours total
- System applies: 10 hours from Regular, 2 hours from Accumulation
- This ensures accumulation calculation remains accurate
4. Split Billing (Auth Billing)
What is Split Billing?
Split billing, also called "auth billing," allows you to bill different portions of an overnight visit to different dates or even different authorizations. This is essential for overnight care that spans two billing days.
Real-World Scenario
Situation: Patient needs overnight care from 10 PM to 6 AM
Problem:
- Visit starts on Day 1 (10 PM)
- Visit ends on Day 2 (6 AM)
- Patient has different authorizations or different insurance on each day
- OR weekly authorization limit reached on Day 1, need to use Day 2's allowance
Solution: Split billing allows you to assign hours to each billing date
How Split Billing Works
Prerequisites
- Contract Setting Must Be Enabled
- Chart Contract must have "Allow Splitting Auths" = true
- This is configured at the contract level
- Different contracts for same patient can have different settings
- Visit Must Be Overnight
- Start date and end date must be different calendar days
- Example: Start 1/15 11:00 PM, End 1/16 7:00 AM
- Valid Authorizations for Each Date
- Each billing date must have an active authorization
- Each authorization must have sufficient units for its portion
Billing Date Types
| Type | Description | When Used |
|---|---|---|
| None (0) | No special billing date handling | Single-day visits (default) |
| Start Date (1) | Authorization bills to the visit start date | Regular authorizations in split billing; first day of overnight visit |
| End Date (2) | Authorization bills to the visit end date | Split billing; second day of overnight visit |
Split Billing Configuration Process
Step 1: Schedule the Overnight Visit
- Create visit spanning two days
- Example: 1/15/2025 10:00 PM - 1/16/2025 6:00 AM (8 hours)
Step 2: Add Authorizations with Billing Dates
- Authorization 1: 5 hours, Billing Date = 1/15/2025
- Authorization 2: 3 hours, Billing Date = 1/16/2025
- Total: 5 + 3 = 8 hours (matches visit duration)
Step 3: System Marks Billing Date Type
- System detects different billing dates
- Authorization 1 marked as "Start Date" type
- Authorization 2 marked as "End Date" type
- This is automatic - you don't need to set it manually
Step 4: Validation Occurs
- System validates Authorization 1 against 1/15/2025 period
- System validates Authorization 2 against 1/16/2025 period
- Each authorization checked independently for available units
Split Billing Examples
Example 1: Split Due to Weekly Authorization Limits
Authorization: 40 hours per week (Sun-Sat)
Situation:
- Week 1 (1/12-1/18): Already used 38 hours through Friday
- Need to schedule: Saturday 10 PM - Sunday 6 AM (8 hours)
- Saturday is in Week 1 (only 2 hours remaining)
- Sunday is in Week 2 (full 40 hours available)
Solution:
- Auth #12345: 2 hours billed to Saturday 1/18/2025
- Auth #12345: 6 hours billed to Sunday 1/19/2025
Result: ✓ PASS - Week 1 uses 40/40 hours, Week 2 uses 6/40 hours
Example 2: Split Due to Different Authorizations
Situation:
- Auth #100 expires on 1/31/2025
- Auth #200 starts on 2/1/2025
- Need overnight care: 1/31 11 PM - 2/1 7 AM (8 hours)
Solution:
- Auth #100: 5 hours billed to 1/31/2025
- Auth #200: 3 hours billed to 2/1/2025
Validation:
- Auth #100 active on 1/31: ✓ PASS
- Auth #200 active on 2/1: ✓ PASS
- 5 hours available in Auth #100: ✓ PASS
- 3 hours available in Auth #200: ✓ PASS
Example 3: Failed Split Billing - Contract Not Allowed
Situation:
- Chart Contract has "Allow Splitting Auths" = FALSE
- Overnight visit: 1/15 10 PM - 1/16 6 AM
- Trying to apply different authorizations to each date
Result: ✗ FAIL
Fix: Enable "Allow Splitting Auths" on the chart contract, or use single authorization for entire visit
Example 4: Complex Split with Accumulation
Situation:
- Regular Auth #500: 10 hours/week, Week ending 1/18
- Already used: 9 hours this week
- Accumulation Auth #500: 15 hours available
- Need overnight: Saturday 1/18 11 PM - Sunday 1/19 7 AM (8 hours)
Solution:
- Regular Auth #500: 1 hour billed to 1/18/2025 (uses last available hour of week)
- Regular Auth #500: 7 hours billed to 1/19/2025 (new week, fresh 10 hours)
Alternative Solution:
- Regular Auth #500: 1 hour billed to 1/18/2025
- Accumulation Auth #500: 7 hours billed to 1/19/2025
Note: Second solution preserves more regular auth hours for future, but uses accumulation. Choose based on your preference and accumulation policy.
Common Split Billing Questions
Q: Can I split a single-day visit?
A: No. Split billing only works for overnight visits where the start and end dates are different calendar days. Single-day visits (even if they're 12+ hours) cannot be split.
Q: Can I split across more than 2 days?
A: The system supports billing dates for start and end dates. For multi-day visits (e.g., Friday 8 AM - Monday 8 AM), you would need to break this into separate visits or bill the entire duration to one authorization.
Q: Do the hours need to be split proportionally?
A: No. You can split hours however you need, as long as:
- Total hours match the visit duration
- Each authorization has sufficient units available
- No single billing date exceeds 24 hours
Example: 8-hour overnight visit can be split 7/1, 5/3, 4/4, etc. - whatever works for your authorization limits.
Q: What if I forget to enable "Allow Splitting Auths" on the contract?
A: The system will show a validation error when you try to use different billing dates. You'll need to either:
- Enable the setting on the chart contract, OR
- Use a single authorization for the entire visit billed to one date
5. Billing Reconciliation and System Implementation
This section explains how the billing system works behind the scenes, including how authorization changes are tracked, how billing items are created, and special handling for specific insurance types.
CRITICAL: Authorization Required for Billing
The billing reconciliation process ONLY creates billing items for visits that have authorizations linked. This is a fundamental requirement enforced at the database level.
- No authorization = No billing item created
- Visits without authorizations are completely excluded from billing
- "Authorization Optional" on service codes only affects validation warnings, NOT billing eligibility
How Billing Reconciliation Works
The billing reconciliation process (implemented in the BillingItems_Reconcile stored procedure) is responsible for creating and updating billing items based on visit schedules and authorizations. This process runs regularly to ensure billing data stays synchronized with schedule changes.
Billing Item Creation Rules
1. Billable Units Requirement
Rule: Billing items are ONLY created when BillableUnitsOrHours > 0
Why: Zero-unit visits have nothing to bill
Implementation:
WHERE BillableUnitsOrHours > 0 AND BillingItemId IS NULL
Example Scenarios:
- Visit scheduled for 4 hours with authorization: ✓ Billing item created
- Visit scheduled for 0 hours (placeholder): ✗ No billing item
- Visit cancelled (units reduced to 0): ✗ Billing item removed or not created
2. Authorization Linkage
Rule: Authorization ID is stored on the BillingItemDetail table via ChartAuthorizationId
Why: Maintains linkage between billing and authorization for audit trail and rebilling
Data Flow:
- User schedules visit and selects authorization(s)
- Schedule saved with authorization ID(s) linked
- Billing reconciliation creates BillingItem
- BillingItemDetail created with ChartAuthorizationId from schedule
- Authorization ID now traceable from bill back to original authorization
3. Split Authorization Tracking
Rule: Split authorizations are tracked via IsSplitAuth flag on billing items
Why: Identifies overnight visits billed across multiple dates for reporting and audit purposes
How It Works:
- When a visit has multiple billing dates (overnight split), the system sets
IsSplitAuth = 1 - This flag helps identify which billing items are part of a split authorization scenario
- Reporting and analytics can filter or group by this flag
Example:
Visit: 1/15/2025 10 PM - 1/16/2025 6 AM (8 hours) → BillingItem 1: 5 hours, BillingDate = 1/15/2025, IsSplitAuth = 1 → BillingItem 2: 3 hours, BillingDate = 1/16/2025, IsSplitAuth = 1
Authorization Change Detection and Rebilling
The billing reconciliation process includes sophisticated logic to detect when authorizations have changed and trigger rebilling accordingly.
What Triggers Rebilling?
The system detects changes to authorization linkage and automatically marks items for rebilling. This ensures billing accuracy when schedules are updated.
- Authorization ID Changed: User changed which authorization is linked to the visit
- Authorization Removed: User removed the authorization from the visit
- Authorization Added: User added an authorization to a previously unbilled visit
- Split Authorization Changes: User changed how hours are split between billing dates
Rebilling Process
When authorization changes are detected:
- Existing billing item is marked for review or deletion
- New billing item is created with updated authorization linkage
- Authorization usage counts are recalculated
- Audit trail is maintained showing the change
Important: This is why you should avoid frequently changing authorizations on already-billed visits. Each change can trigger rebilling workflows and insurance resubmission.
Special Insurance Type Handling
LHCSA Insurance Exclusion
Rule: LHCSA insurance contracts are excluded from standard billing reconciliation
Implementation:
WHERE ip.PlanName <> 'LHCSA'
Why: LHCSA (Licensed Home Care Services Agency) has specialized billing requirements and workflows that differ from standard home care billing
What This Means:
- LHCSA visits are handled by a separate billing process
- Standard authorization validation still applies to LHCSA schedules
- LHCSA billing items are created through a different pathway
- Users need special permission (
CanAddEditAuthorizationsForLHCSAContract) to work with LHCSA authorizations
Why LHCSA is Different
LHCSA insurance in New York State has unique requirements:
- Different billing codes: LHCSA uses different procedure codes than traditional home care
- Different rate structure: Rates may be negotiated separately
- Different reporting: State reporting requirements differ
- Different authorization format: LHCSA may use different authorization structures
Therefore, the system handles LHCSA billing through specialized logic separate from the standard BillingItems_Reconcile process.
Billing Reconciliation Performance Considerations
Efficient Processing
The billing reconciliation process is optimized for performance:
- Incremental Updates: Only processes schedules that have changed since last reconciliation
- Bulk Operations: Creates/updates multiple billing items in batches
- Index Optimization: Uses database indexes on BillingItemId, ChartAuthorizationId, and BillingDate
- Filtered Queries: Excludes LHCSA and zero-unit visits early in the query to reduce processing
Billing Reconciliation and Authorization Usage
The billing reconciliation process works closely with authorization usage tracking:
Authorization Usage Flow
- Schedule Created: Visit scheduled with authorization selected
- Validation Runs: System validates authorization has sufficient units available
- Units Reserved: Visit units are tracked against authorization usage
- Billing Item Created: Billing reconciliation creates billing item with authorization link
- Usage Finalized: Authorization usage is now permanently recorded on billing item
- If Schedule Changed: Usage recalculated and billing item updated or recreated
Authorization Usage vs. Billing
Important Distinction:
- Authorization Validation: Checks if units are available at time of scheduling
- Billing Item Creation: Records that units were actually used and should be billed
- Key Point: A visit can pass validation but not be billed if authorization is removed later, or fail validation but still consume units if overridden
Common Billing Reconciliation Scenarios
Scenario 1: Normal Visit Billing
Steps:
- Visit scheduled: 1/15/2025, 4 hours, Authorization #12345
- Authorization validated: 4 hours available, ✓ PASS
- Visit saved successfully
- Billing reconciliation runs (nightly or on-demand)
- BillingItem created: BillableUnitsOrHours = 4, BillingDate = 1/15/2025
- BillingItemDetail created: ChartAuthorizationId = 12345
- Authorization usage incremented by 4 hours
Scenario 2: Authorization Changed After Initial Billing
Steps:
- Visit originally billed with Authorization #100
- User changes authorization to #200 (different insurance)
- Visit saved with new authorization
- Billing reconciliation detects authorization ID change
- Original billing item marked for rebilling/deletion
- New billing item created with Authorization #200
- Authorization #100 usage decreased by 4 hours
- Authorization #200 usage increased by 4 hours
Result: Billing now reflects the correct authorization, but this may trigger insurance claim adjustments
Scenario 3: Visit Without Authorization (No Billing)
Steps:
- Visit scheduled: 1/15/2025, 4 hours
- Service Code has "Authorization Optional" = TRUE
- User does NOT select an authorization (leaves blank)
- Visit saves successfully (no validation error because optional)
- Billing reconciliation runs
- NO BILLING ITEM CREATED - visit has no authorization
- Visit appears in schedules but NOT in billing reports
- No revenue captured for this visit
Result: ✗ Visit NOT billed - Even though validation passed, billing requires authorization
Scenario 4: LHCSA Visit Billing
Steps:
- Visit scheduled for patient with LHCSA insurance
- Authorization validated (same rules apply)
- Visit saved successfully
- Standard billing reconciliation runs
- Visit excluded from standard reconciliation (
WHERE ip.PlanName <> 'LHCSA') - Separate LHCSA billing process handles this visit
- LHCSA-specific billing item created with appropriate codes
Result: Visit is billed, but through specialized LHCSA pathway
Monitoring Billing Reconciliation
Key Metrics to Monitor
- Unbilled Visits: Schedules with hours but no billing items (may indicate missing authorizations)
- Split Authorization Count: Number of visits using
IsSplitAuth = 1 - Rebilling Events: Frequency of authorization changes requiring rebilling
- LHCSA vs. Standard Volume: Percentage of visits processed through each pathway
- Authorization Usage Accuracy: Compare schedule hours to billed hours
6. How the System Selects Authorizations
Automatic Authorization Application
When you create a new visit, the system can automatically select and apply an appropriate authorization. Understanding this logic helps you anticipate which authorization will be used.
Authorization Selection Criteria (Priority Order)
1. Authorization Type Must Be "Regular"
Rule: System only auto-applies regular authorizations
Why: Accumulation authorizations require explicit user selection with proper permission
Exception: Users with "CanUseAccumulatedAuthUnits" permission can manually select accumulation authorizations
2. Authorization Must Be Active on Schedule Date
Rule: Start Date ≤ Schedule Date ≤ End Date
Example:
- Authorization: 1/1/2025 - 1/31/2025
- Schedule Date: 1/15/2025 ✓ Eligible
- Schedule Date: 2/5/2025 ✗ Not Eligible
3. Chart Contract Must Be Active
Rule: Contract Effective Date ≤ Schedule Date, and (Contract End Date is null OR ≥ Schedule Date)
Why: Even if authorization is active, the patient's insurance contract must also be active
4. Service Code Must Match
Rule: Authorization detail must exist for the same service code as the scheduled visit
Example:
- Visit Service Code: Skilled Nursing (RN)
- Authorization must have a detail for Skilled Nursing (RN)
- Authorization with only Physical Therapy will not be selected
5. LHCSA and Charity Insurances Excluded
Rule: LHCSA and Charity insurance contracts are excluded from auto-apply
Why: These require special handling and explicit user selection
Permission: Users need "CanAddEditAuthorizationsForLHCSAContract" or "CanAddEditAuthorizationsForCharityContract" to use these
6. Primary Contract Preferred
Rule: If multiple authorizations meet all criteria, select from primary contract
Why: Patients often have multiple insurances; primary insurance should be billed first
Example:
- Patient has Medicare (Primary) and Medicaid (Secondary)
- Both have active authorizations for same service
- System selects Medicare authorization
7. If Only One Option, Select It
Rule: If only one authorization meets all criteria, use it regardless of primary status
Why: Simplifies scheduling when choice is obvious
Manual Authorization Selection
In the following scenarios, you must manually select authorizations:
- Multiple authorizations available: System cannot determine which to use
- No authorizations match criteria: May need to select from secondary insurance or future-dated authorization
- Accumulation authorization needed: Must explicitly select accumulation auth
- Split billing required: Must specify which authorization for each billing date
- LHCSA or Charity insurance: Must manually select with proper permission
Authorization Loading for Scheduling
When the scheduling screen loads, the system filters available authorizations based on several factors:
Standard Filters Applied
- Date Range: Only shows authorizations active within the specified date range
- Service Code: Only shows authorizations with matching service code
- Authorization Type: Excludes accumulation unless user has permission
- Day of Week: If scheduling specific days, filters to authorizations allowing those days
Example: Filtering by Day of Week
Scenario: Scheduling weekly recurring visits for Monday, Wednesday, Friday
Authorization A: Mon, Wed, Fri, Sat (Weekdays Value = 106)
Authorization B: Mon, Tue, Wed, Thu, Fri (Weekdays Value = 62)
Authorization C: Any 5 days per week (Weekdays UOM = Number)
Result: All three appear in list because they all allow Mon, Wed, Fri
7. Detailed Validation Rules
Available Units Calculation by Period Type
Weekly Authorization Units
Method: Get day-specific units or total weekly units
Day-Specific Units:
- If authorization specifies SunUnits, MonUnits, etc., use those values
- Example: Authorization has MonUnits=4, TueUnits=4, WedUnits=2
- Monday visit: 4 hours available
- Wednesday visit: 2 hours available
- If day has 0 units: Cannot schedule on that day
Number of Days:
- If Weekdays UOM = Number (e.g., "any 5 days")
- Any day returns full weekly units
- Example: 40 hours per week, any 5 days = 40 hours available per day
- System validates number of days separately
Daily Authorization Units
Method: Return per-day units, check if day is allowed
Specific Days:
- If Weekdays UOM = Day with specific days selected
- Check if schedule day is in selected days
- If yes: Return daily units
- If no: Return error (day not allowed)
Number of Days:
- If Weekdays UOM = Number
- Return daily units for any day
- System validates total days per week separately
Allowed to Vary:
- If "Weekdays Allowed to Vary" = true
- Return daily units for any day regardless of selection
Monthly Authorization Units
Method: Return full monthly units
Period: First day of month to last day of month
Example:
- Authorization: 160 hours per month
- Any day in January: 160 hours available (minus already used)
Period Authorization Units
Method: Return full authorization units
Period: Authorization start date to end date
Example:
- Authorization: 100 hours total, 1/1/2025 - 3/31/2025
- Any day within range: 100 hours available (minus already used)
Period Date Calculation Logic
| Period Type | Period Start Date | Period End Date | Example (Schedule Date: 1/15/2025, Wed) |
|---|---|---|---|
| Week | First day of week (Sunday)* | Last day of week (Saturday) | 1/12/2025 (Sun) - 1/18/2025 (Sat) |
| Month | First day of month | Last day of month | 1/1/2025 - 1/31/2025 |
| Day | Schedule date | Schedule date | 1/15/2025 - 1/15/2025 |
| Period | Authorization start date | Authorization end date | 1/1/2025 - 3/31/2025 (if auth spans this range) |
*First day of week is configurable per insurance but defaults to Sunday
Weekday Selection (Bitwise Logic)
The system uses bitwise flags to store selected days efficiently:
| Day | Bit Value | Binary |
|---|---|---|
| Sunday | 1 | 0000001 |
| Monday | 2 | 0000010 |
| Tuesday | 4 | 0000100 |
| Wednesday | 8 | 0001000 |
| Thursday | 16 | 0010000 |
| Friday | 32 | 0100000 |
| Saturday | 64 | 1000000 |
Weekdays Value Examples
- Monday, Wednesday, Friday: 2 + 8 + 32 = 42
- All weekdays (Mon-Fri): 2 + 4 + 8 + 16 + 32 = 62
- Entire week: 1 + 2 + 4 + 8 + 16 + 32 + 64 = 127
- Weekend only: 1 + 64 = 65
How it's checked: System performs bitwise AND operation
Example: Is Wednesday (8) in value 42?
- 42 & 8 = 8 (non-zero, so YES, Wednesday is included)
Example: Is Tuesday (4) in value 42?
- 42 & 4 = 0 (zero, so NO, Tuesday is not included)
Usage Calculation from Database
The system uses a stored procedure to calculate authorization usage:
What Gets Counted as "Used"
Confirmed Visits:
- Visits that have been confirmed (not just scheduled)
- Excludes missed visits (visits with ChartVisitMissedReasonId)
- Uses the billing date if specified, otherwise visit start date
Scheduled Visits (Optional):
- Unconfirmed scheduled visits
- Only included if insurance setting "Include Scheduled Units in Accumulation" is enabled
- Helps prevent over-scheduling
Two Result Sets Returned
Result Set 1: Authorization-Specific Usage
- All visits using this specific authorization
- Filtered to the period being validated
- Shows individual visit details
Result Set 2: Daily Care Type Usage
- Total units for the care type on each date
- Used to validate 24-hour daily cap
- Aggregated across all authorizations
8. Configuration and Settings
Insurance-Level Settings
| Setting | Description | Impact |
|---|---|---|
| Authorization Required | Controls whether authorizations are mandatory for this insurance | If true, all visits must have authorizations unless service code is marked "Authorization Optional" |
| Hospitalization Ends Auth | Automatically terminates authorization when patient is hospitalized | Authorization becomes inactive; cannot schedule new visits after hospitalization date |
| Allow Accumulating Auth | Enables accumulation authorization feature | System automatically creates and maintains accumulation authorizations (see Accumulation Authorization Guide) |
| Include Scheduled Units in Accumulation | Whether scheduled (unconfirmed) visits count toward accumulation calculations | If true, scheduling a visit immediately reduces accumulation units; if false, only confirmed visits count |
| Exclude Missed Days from Accumulation | Whether days with only missed visits don't count against authorization | If true, days where all visits were missed don't reduce authorized units (patient keeps those units) |
| Require Diagnosis Code on Auth | Whether diagnosis codes are mandatory on authorizations | If true, cannot save authorization without at least one diagnosis code |
| Bill PMPM | Per Member Per Month billing | Special billing model; affects invoicing but not authorization validation |
Chart Contract Settings
| Setting | Description | Impact |
|---|---|---|
| Is Primary | Marks this contract as the patient's primary insurance | Primary contract authorizations are preferred during auto-selection |
| Allow Splitting Auths | Enables split billing for this contract | If true, overnight visits can bill different hours to different dates/authorizations; if false, split billing validation fails |
Service Code Settings
| Setting | Description | Impact |
|---|---|---|
| Authorization Optional | Service code can be scheduled without authorization | If true, authorization usage validation passes even without authorization linked. CRITICAL: Visits without authorizations will NOT be billed, regardless of this setting. |
Critical Billing Rule
The HCM system ONLY bills schedules/visits that have authorizations linked.
The "Authorization Optional" setting controls validation warnings only, not billing behavior:
- Authorization Optional = true: Can schedule without authorization (no validation warning), but visit will NOT be billed
- Authorization Optional = false: Generates validation warning if no authorization, and visit will NOT be billed without authorization
Key Takeaway: If you want to bill a visit, you MUST link an authorization, regardless of any "optional" settings.
User Permissions
| Permission | Purpose | Impact |
|---|---|---|
| CanUseAccumulatedAuthUnits | Allows user to select and use accumulation authorizations | Without this, accumulation authorizations are hidden from authorization selection screens |
| CanAddEditAuthorizationsForLHCSAContract | Allows user to work with LHCSA insurance authorizations | LHCSA authorizations are excluded from auto-apply and require this permission for manual selection |
| CanAddEditAuthorizationsForCharityContract | Allows user to work with Charity insurance authorizations | Charity authorizations are excluded from auto-apply and require this permission for manual selection |
System Parameters
| Parameter | Default Value | Purpose |
|---|---|---|
| BillingPayrollRoundingStrategy | Nears15Minutes | Controls how visit hours are rounded when calculating authorization units; affects accuracy of "hours used" calculations |
9. Troubleshooting Common Issues
Issue: Authorization Not Appearing in Selection List
Possible Causes:
- Authorization dates don't include the schedule date
- Service code doesn't match between authorization and visit
- Chart contract is not active
- Authorization is accumulation type and user lacks permission
- Authorization is LHCSA/Charity and user lacks permission
- Day of week not allowed by authorization
How to Fix:
- Verify authorization start/end dates include schedule date
- Check authorization has detail for the correct service code
- Confirm chart contract is active on schedule date
- Request "CanUseAccumulatedAuthUnits" permission if needed
- Check weekday configuration allows the schedule day
Issue: "Authorization cannot be linked more than once to a schedule"
Cause: Same authorization linked multiple times with same billing date
How to Fix:
- Review authorizations on the visit
- Remove duplicate authorization entries
- If splitting hours, ensure each entry has different billing date OR different authorization
Issue: "Authorization [number] cannot be used for a split billing"
Cause: Trying to use different billing dates but contract doesn't allow split billing
How to Fix:
- Go to Chart Contract settings
- Enable "Allow Splitting Auths" setting
- OR use single authorization with single billing date
Issue: "Authorization [number] will exceed the maximum [X] units allowed"
Cause: Authorization has MaxUnitsForAuthorization cap that would be exceeded
How to Fix:
- Review total units used on authorization detail
- Check if MaxUnitsForAuthorization needs to be increased
- Consider using different authorization or splitting visit
- Verify if some visits were incorrectly billed to this authorization
Issue: "Authorization [number] is not authorized for [day of week]"
Cause: Schedule date falls on a day not allowed by authorization's weekday configuration
How to Fix:
- Check authorization's weekday settings
- Verify Weekdays UOM (Day or Number) and Weekdays Value
- If day should be allowed, update authorization weekday configuration
- If day should not be allowed, reschedule visit to allowed day
- Check if "Weekdays Allowed to Vary" should be enabled
Issue: "Authorization [number] does not have enough available hours/visits"
Cause: Insufficient units available for the period
How to Fix:
- Check authorization period type and units
- Review usage report for the period to see what's already scheduled/confirmed
- Consider using accumulation authorization if available
- For overnight visits, consider split billing across two periods
- Verify if some visits need to be rescheduled or removed
- Check if authorization needs to be increased
Issue: "Authorization [number] usage would exceed 24 hours in a single day"
Cause: Single billing date would have more than 24 hours (impossible)
How to Fix:
- Review all visits scheduled for that billing date
- Check if visit durations are correct (not accidentally 20 hours instead of 2 hours)
- Verify billing dates are set correctly
- For overnight visits, ensure proper split billing configuration
Issue: "Authorization [number] allows a maximum of [X] days per week"
Cause: Authorization has "Number of Days" constraint (e.g., "any 5 days per week")
How to Fix:
- Review which days are already scheduled in the week
- Reschedule visit to a week with available days
- Check if authorization needs to be changed to allow more days
- Consider if some existing visits need to be moved
Issue: System Auto-Selected Wrong Authorization
Cause: Multiple authorizations available; system selected based on priority rules
How to Fix:
- Manually change to the correct authorization
- If this happens frequently, review contract "Is Primary" settings
- Consider if authorizations need different date ranges to avoid overlap
Issue: Cannot See Accumulation Authorization
Cause: User lacks "CanUseAccumulatedAuthUnits" permission
How to Fix:
- Request permission from system administrator
- Verify accumulation authorization exists (check authorization list)
- Confirm insurance has "Allow Accumulating Auth" enabled
10. Real-World Examples
Example 1: Weekly Authorization with Day-Specific Hours
Authorization Setup:
- Authorization #12345
- Service Code: Skilled Nursing (RN)
- Period: Week
- Weekdays UOM: Day
- Days: Mon, Tue, Wed, Thu, Fri (Weekdays Value = 62)
- MonUnits: 4, TueUnits: 4, WedUnits: 2, ThuUnits: 4, FriUnits: 4
- Total: 18 hours per week
Scheduling Scenarios:
| Visit | Result | Explanation |
|---|---|---|
| Monday 9 AM - 1 PM (4 hours) | ✓ PASS | Monday allows 4 hours, using 4 hours |
| Wednesday 9 AM - 12 PM (3 hours) | ✗ FAIL | Wednesday only allows 2 hours, trying to use 3 |
| Saturday 9 AM - 1 PM (4 hours) | ✗ FAIL | Saturday not in allowed days |
| Friday 9 AM - 1 PM (4 hours), already have 4 hours on Mon, Tue, Wed, Thu | ✓ PASS | Total for week: 4+4+2+4+4 = 18 hours, all used but within limit |
Example 2: Daily Authorization with "5 Days Per Week" Constraint
Authorization Setup:
- Authorization #67890
- Service Code: Home Health Aide
- Period: Day
- Units: 8 hours per day
- Weekdays UOM: Number
- Weekdays Value: 5 (allows any 5 days per week)
Week Scheduling:
| Action | Result | Days Used This Week |
|---|---|---|
| Schedule Monday 8 AM - 4 PM | ✓ PASS | 1/5 |
| Schedule Tuesday 8 AM - 4 PM | ✓ PASS | 2/5 |
| Schedule Wednesday 8 AM - 4 PM | ✓ PASS | 3/5 |
| Schedule Thursday 8 AM - 4 PM | ✓ PASS | 4/5 |
| Schedule Friday 8 AM - 4 PM | ✓ PASS | 5/5 |
| Schedule Saturday 8 AM - 4 PM | ✗ FAIL | Would be 6/5 - exceeds limit |
| Next Monday (new week) 8 AM - 4 PM | ✓ PASS | 1/5 (new week, counter reset) |
Example 3: Monthly Authorization Approaching Limit
Authorization Setup:
- Authorization #11111
- Service Code: Physical Therapy
- Period: Month
- Units: 12 visits per month
- Month: January 2025
Usage Through January:
- Week 1: 3 visits (Total: 3)
- Week 2: 3 visits (Total: 6)
- Week 3: 4 visits (Total: 10)
- Week 4: Want to schedule 3 visits
Week 4 Scheduling:
| Visit | Result | Total After |
|---|---|---|
| Monday visit | ✓ PASS | 11/12 |
| Wednesday visit | ✓ PASS | 12/12 |
| Friday visit | ✗ FAIL | Would be 13/12 |
Options:
- Wait until February 1st (new month, fresh 12 visits)
- Use accumulation authorization if available
- Contact insurance for authorization increase
Example 4: Split Billing for End-of-Month Overnight Visit
Situation:
- Patient: John Doe
- Authorization #22222: 40 hours per week (Sun-Sat)
- Week of 1/26-2/1: Already used 38 hours through Friday
- Need overnight care: Saturday 1/31 10 PM - Sunday 2/1 6 AM (8 hours)
Analysis:
- Week 1 (ending 2/1): 2 hours remaining
- Week 2 (starting 2/2): Full 40 hours available
- Visit spans two weeks
Solution: Split Billing
| Authorization | Hours | Billing Date | Week |
|---|---|---|---|
| Auth #22222 | 2 hours | 1/31/2025 (Saturday) | Week ending 2/1 |
| Auth #22222 | 6 hours | 2/1/2025 (Sunday) | Week starting 2/2 |
Validation:
- Contract has "Allow Splitting Auths" = true ✓
- Saturday billing: 2 hours available, using 2 ✓
- Sunday billing: 40 hours available, using 6 ✓
- Neither day exceeds 24 hours ✓
- Total hours (8) matches visit duration ✓
Result: ✓ PASS - Visit successfully scheduled with split billing
Example 5: Period Authorization with Maximum Cap
Authorization Setup:
- Authorization #33333
- Service Code: Occupational Therapy
- Start Date: 1/1/2025
- End Date: 3/31/2025 (3 months)
- Period: Week
- Units: 10 hours per week
- MaxUnitsForAuthorization: 100 hours (entire period cap)
Usage Through March:
| Time Period | Weekly Average | Total Used | Remaining (Max Cap) |
|---|---|---|---|
| January (4 weeks) | 10 hours/week | 40 hours | 60 hours |
| February (4 weeks) | 10 hours/week | 40 hours | 20 hours |
| March Week 1 | 10 hours | 10 hours | 10 hours |
| March Week 2 | 10 hours | 10 hours | 0 hours |
Total Used: 100 hours (reached maximum cap)
Attempting to Schedule March Week 3:
- Weekly authorization still shows 10 hours available per week
- But MaxUnitsForAuthorization = 100 hours is exhausted
- Result: ✗ FAIL
Options:
- Request authorization extension or new authorization from insurance
- Use accumulation authorization if available
- Wait for new authorization period
Example 6: Combining Regular and Accumulation Authorization
Authorization Setup:
- Regular Auth #44444: 10 hours per week
- Accumulation Auth #44444: 20 hours available (accumulated over past weeks)
Current Week Usage:
- Monday: 4 hours (Regular)
- Tuesday: 4 hours (Regular)
- Wednesday: 2 hours (Regular)
- Total Regular Used: 10 hours (limit reached)
Need Additional Visit:
- Thursday: Need 4 hours
- Regular authorization exhausted for the week
Solution: Use Accumulation
| Day | Authorization | Hours | Regular Used | Accumulation Used |
|---|---|---|---|---|
| Mon | Regular #44444 | 4 | 4/10 | 0/20 |
| Tue | Regular #44444 | 4 | 8/10 | 0/20 |
| Wed | Regular #44444 | 2 | 10/10 | 0/20 |
| Thu | Accumulation #44444 | 4 | 10/10 | 4/20 |
Result: ✓ PASS - Used regular authorization first, then accumulation when needed
Best Practice: Always use regular authorization before accumulation to preserve accumulated units for future emergencies
Quick Reference Cheat Sheet
Authorization Type Quick Reference
| Type | Auto-Apply? | Permission Needed? | Use When |
|---|---|---|---|
| Regular | Yes | No | Standard scheduling |
| Accumulation | No | Yes | When regular auth exhausted |
| LHCSA | No | Yes | LHCSA insurances only |
| Charity | No | Yes | Charity care insurances only |
Period Type Quick Reference
| Period | Units Renew | Best For |
|---|---|---|
| Week | Every Sunday | Regular home care, ongoing services |
| Month | 1st of month | Monthly care plans, managed care |
| Day | Every day | Daily care limits, shift-based care |
| Period | Never (one-time) | Rehab, time-limited therapies |
Key Takeaways
Need Additional Help?
For questions about:
- Accumulation Authorization: See the separate "Accumulation Authorization User Guide"
- System Configuration: Contact your system administrator
- Insurance-Specific Rules: Consult with your billing/authorization coordinator
- Technical Issues: Submit a support ticket with specific error messages and screenshots
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article