i800services | Shola Emmanuel
The i800services 1-in-3 AIMI 7 Pillar System
Discover if you qualify for Predictive Revenue
5-minute assessment • Instant results
Your answers are private. No spam. No sales scripts.
Unify EVV, Portal, Payroll, GAMMIS, and Invoices into One Secure System
Cut manual re-entry, prevent duplicates, speed claims/payroll, and get audit-ready visibility
-60%
Data entry errors eliminated
-40%
EVV→Payroll processing time
95%+
First-pass claim acceptance
From Manual Chaos to Automated Control
Today's Pain
- Re-keying data across three systems (EVV, Portal, Payroll)
- Duplicate vendor payments from lack of visibility
- Paper invoices causing slow lookups and errors
- EVV and Portal data mismatches requiring manual reconciliation
- Portal security incidents from weak access controls
- Excel tracking for checks creating audit gaps
Integrated Future
- One source of truth with zero re-entry
- Auto-dedupe invoices by hash, number, amount, and vendor
- EVV→Timesheet→Payroll automation with validation
- GAMMIS EDI 837/835 submission with RPA fallback
- Digital document vault with full-text search
- MFA/SSO + role-based access + complete audit logs
Not another forced app: Staff-led pilot with 5-10 users. IT retains Active Directory, SSO, and security oversight. We handle the integrations and automation. Your team defines "done."
How the Integration Hub Works
Click each component to learn more
EVV
→
Pulls clock-in/out times and GPS coordinates. Creates pre-timesheets. Flags mismatches against authorized schedules and locations.
Integration Hub
↔
Central orchestration layer. Validates, routes, and tracks all data flows. Provides exception queues and audit trails.
CFS Portal
↔
Bidirectional sync for participant data, approvals, and status updates. Can be phased out as Hub functions expand.
iSolved
Receives approved timesheets and pay rates. Returns payroll status and reconciliation data.
Email/AP
→
Email ingestion from dedicated mailbox. OCR extraction of invoice fields. Automatic routing to approval queue.
OCR/Dedupe
→
Extracts vendor, amount, invoice number, date. Checks duplicates by hash + invoice# + amount + vendor before approval.
GAMMIS
→
Submits EDI 837 claims via clearinghouse. Auto-posts 835 remittances. RPA fallback with full audit trail if EDI unavailable.
Payments
→
Generates ACH/check batches. Captures payment references. Auto-updates reconciliation status.
Reconciliation
Matches payments to claims and invoices. Tracks aging receivables/payables. Provides audit-ready reports.
Live Demo (Simulated)
Interactive simulation with sample data. No external calls.
EVV Events Pending Approval
| Date | Caregiver | Participant | Service | GPS Match | Hours | Status |
|---|---|---|---|---|---|---|
| 2026-03-07 | Sarah Johnson | John Doe | Personal Care | ✓ | 4.0 | Pending |
| 2026-03-07 | Mike Williams | Jane Smith | Respite Care | ✓ | 6.5 | Pending |
| 2026-03-06 | Emily Davis | Robert Brown | Companion | ✓ | 8.0 | Pending |
Invoice Inbox
| Vendor | Invoice # | Amount | Date | Status | Action |
|---|---|---|---|---|---|
| ABC Medical Supply | INV-2026-001 | $1,245.00 | 2026-03-05 | Pending Review | |
| XYZ Pharmacy | INV-2026-002 | $850.00 | 2026-03-06 | Pending Review |
Exceptions Queue
| Type | Item | Issue | Age (hrs) | Action |
|---|---|---|---|---|
| EVV Mismatch | Visit #12345 | GPS outside service area | 2 | |
| Missing Doc | Claim #CLM-001 | Authorization not uploaded | 18 | |
| Duplicate Invoice | INV-2026-003 | Matches existing payment | 4 | |
| Claim Rejection | CLM-2026-002 | Invalid procedure code | 24 |
Resolved Today: 0
Security & Compliance
HIPAA-aligned practices with enterprise-grade controls
MFA
Multi-factor authentication required for all users
SSO
Single sign-on with Active Directory integration
RBAC
Role-based access control with least privilege
Encryption
TLS 1.2+ in transit, AES-256 at rest
WAF
Web application firewall with rate limiting
Backups
Daily encrypted backups with tested restores
Audit Logs
Immutable logs for every action and change
HIPAA
BAA with vendors, PHI minimization, compliance ready
Scalecard: Weekly Operational Metrics
Sample targets - fully configurable for your operations
EVV Capture Rate
98%
Exception Rate
3.2%
Approval Cycle Time
4.2 hrs
Payroll Accuracy
99.2%
Duplicate Invoice Rate
0.5%
First-Pass Claim Acceptance
96%
Days to Payment
12
Reconciliation Lag
2.1 days
Phased Delivery Timeline
Staff-led, measurable, low-risk implementation
Phase 0
3 weeks
Discovery
- Map current workflows and pain points
- Document data schemas and field mappings
- Confirm security requirements and EDI path
- Define pilot team and success metrics
Done when: Signed requirements doc, test credentials obtained, pilot team selected
Phase 1
5 weeks
EVV→Timesheet→iSolved MVP
- Build Integration Hub core and EVV connector
- Create timesheet approval UI and validation rules
- Implement iSolved export/import automation
- Deploy to pilot team with daily standup support
Done when: Pilot team processes one full pay cycle with zero manual re-entry
Phase 2
4 weeks
AP/Invoices + Document Hub
- Email ingestion and OCR extraction
- Deduplication by hash + invoice# + amount + vendor
- Digital document vault with search and version control
- Approval workflow with dual-control options
Done when: Zero paper invoices, 100% digital storage, duplicate rate below 1%
Phase 3
4-6 weeks
GAMMIS Claims/835 Remits
- EDI 837 generation and clearinghouse submission
- 835 remittance auto-posting (+2 weeks if RPA fallback needed)
- Claim tracking and rejection workflow
- Payment reconciliation automation
Done when: 95%+ first-pass acceptance, auto-posted remits, audit-ready claim history
Phase 4
3-4 weeks
Security Hardening & Rollout
- Penetration testing and vulnerability remediation
- RBAC fine-tuning and MFA enforcement
- Training documentation and video walkthroughs
- Expand to all teams with tiered rollout
Done when: All staff trained, zero critical security findings, full production deployment
Frequently Asked Questions
Is this replacing our portal or IT team?
+
No. Your IT team keeps Active Directory, SSO, and security oversight. The portal team collaborates on requirements. The Integration Hub handles connections, automation, and reporting—not replacement.
What if GAMMIS has no API available?
+
We prefer EDI 837/835 via a clearinghouse (faster, more reliable). If that's not available, we use secure RPA (robotic process automation) with full audit trail, screenshots, and error handling. Final approach determined in discovery.
How do we avoid another "forced app" situation?
+
We start with 20-minute listening huddles with staff. The 90-day pilot runs with 5-10 users who define what "done" looks like. UAT (user acceptance testing) gates each phase. If the pilot doesn't deliver measurable wins, we adjust or stop.
How are duplicates prevented?
+
Every document and invoice gets a unique hash. We check: document hash + invoice number + amount + vendor. If all four match, the system stops the approval and alerts the user. No duplicate can pass without explicit override (which is logged).
What happens to our existing data?
+
Historical data can be migrated via one-time import with cleansing and validation. Active records sync bidirectionally. Legacy systems remain accessible during transition. We never delete source data without explicit approval.
How long until we see results?
+
Phase 1 (EVV→Payroll) delivers measurable time savings within 5 weeks. Document deduplication shows impact immediately in Phase 2. Full end-to-end automation (invoice→claim→payment) completes in 12-16 weeks depending on GAMMIS integration path.
Ready to Eliminate Manual Re-Entry?
Approve a 30-minute briefing to review the pilot plan and success metrics
Appendix: Technical Reference
Canonical Data Model
| Entity | Key Fields | Purpose |
|---|---|---|
| Participants | medicaid_id, name, dob, address, authorized_services | Care recipients |
| Employees | employee_id, name, certifications, pay_rate | Caregivers and staff |
| Visits/EVV Events | visit_id, participant, employee, clock_in, clock_out, gps, service_code | Service delivery tracking |
| Timesheets | timesheet_id, employee, period, hours, status | Payroll preparation |
| Claims | claim_id, participant, service_date, procedure_code, amount, status | Medicaid billing |
| Vendors | vendor_id, name, tax_id, payment_terms | Supplier management |
| Invoices | invoice_id, vendor, invoice_number, amount, date, hash | Payables tracking |
| Payments | payment_id, invoice, method (ACH/Check), reference_number, date | Payment execution |
| Documents | document_id, type, entity_reference, file_path, upload_date | Document vault |
Sample Field Mappings
EVV → Timesheet Mapping
{
"evv_clock_in": "timesheet.start_time",
"evv_clock_out": "timesheet.end_time",
"evv_employee_id": "timesheet.employee_id",
"evv_service_code": "timesheet.service_type",
"calculated_hours": "timesheet.hours",
"gps_verified": "timesheet.location_verified"
}
Invoice OCR → Claim Mapping
{
"ocr_vendor_name": "claim.provider_name",
"ocr_invoice_number": "claim.external_reference",
"ocr_amount": "claim.billed_amount",
"ocr_service_date": "claim.service_from_date",
"participant_medicaid_id": "claim.subscriber_id"
}
Sample EDI 835 Remittance
{
"transaction_set": "835",
"payer": "Georgia Medicaid",
"payment_date": "2026-03-10",
"payment_method": "ACH",
"payment_amount": 12450.00,
"claims": [
{
"claim_id": "CLM-2026-03-001",
"patient_control_number": "12345",
"billed_amount": 1245.00,
"paid_amount": 1245.00,
"status": "Approved",
"adjustment_codes": []
},
{
"claim_id": "CLM-2026-03-002",
"patient_control_number": "12346",
"billed_amount": 850.00,
"paid_amount": 0.00,
"status": "Denied",
"adjustment_codes": ["CO-16: Invalid procedure code"]
}
]
}
Validation Rules
- EVV GPS must be within 0.5 miles of authorized service address
- Clock-out time must be after clock-in time
- Service code must match participant's authorized services
- Invoice duplicate check: hash + invoice# + amount + vendor must be unique
- Claim procedure codes must be valid Medicaid codes
- Payment amount cannot exceed invoice amount
- MFA required for approval actions over $1,000
Invoice #:
Amount:
Date: 2026-03-05
Status: Pending Review
OCR Extracted Fields
Vendor Name:
Invoice Number:
Amount:
Service Date: 2026-03-05
Duplicate Risk: