ACIS · Portfolio · Live System ↗

← Portfolio

Roadmap & Vision: ACIS at BRMS


Current State (Live Now)

Module Status What It Does
Regulatory Pulse Live 5-source federal feed, daily Claude scoring, 64 events
Attestation Vault Live RxDC + Gag Clause tracking for 8 client plans
Vendor Risk Live Real TLS/header scanning + Claude HIPAA risk assessment
Incident Response Live NIST 800-61 playbooks auto-generated on every incident
Executive Hub Live Single dashboard at acis.rossonlineservices.com
Operations Tab Live Manual triggers, heartbeat view, AI Gateway log streaming
Heartbeat Agent Live Daily self-audit → Green/Yellow/Red → CCC Admin report
Agent Logs Live Full AI inference trace visible in Operations tab

Near-Term Roadmap (Next 30 Days)

✅ Playbook Agent Upgrade — Complete (2026-04-25)

The NIST playbook generator has been upgraded from claude-sonnet-4-6 to claude-opus-4-7. CFR citation precision and phase-level specificity for complex incident types (supply chain compromise, insider threat) are measurably improved. Every new incident now receives an Opus-quality playbook.

1. Attestation Email Reminders

Automated outbound reminders to client plans with approaching or overdue RxDC and Gag Clause deadlines. Triggered by the daily cron when rxdc_status or gag_clause_status reaches a threshold. Sent via Resend API with HIPAA-appropriate templating. This closes the loop between tracking and action — the system doesn't just surface overdue records, it contacts the responsible parties.

2. Incident Escalation Notifications

When the Heartbeat Agent detects an incident open longer than 7 days, send a targeted alert to the compliance administrator and log an escalation event to the admin layer. Ensures incidents don't silently age past the HIPAA Breach Notification Rule's 60-day OCR reporting window.

3. GitHub PR Automation

When the Regulatory Pulse detects a new High-risk event (e.g., a CMS bulletin changing an RxDC submission deadline), the system opens a GitHub pull request automatically — updating the organization's policy documentation with the new requirement, citing the source regulatory document, and tagging the change for review. This is the feature that demonstrates ACIS is not just monitoring but acting: the compliance administrator reviews a PR rather than manually researching a bulletin.


BRMS-Specific Adaptation (If Deployed)

ACIS was built as a general healthcare compliance platform. Adapting it for BRMS would require approximately two weeks of configuration:

Data layer:

Compliance layer:

Reporting layer:


The Vision: Compliance as Infrastructure

The traditional compliance administrator model requires constant manual effort: reading bulletins, updating spreadsheets, chasing attestations, writing incident reports, reviewing vendor SOC 2 reports. The ceiling on what one person can manage is defined by hours in a day.

ACIS redefines that ceiling. With ACIS deployed:

One compliance administrator with ACIS operates at the throughput of a three-person compliance team — with an audit trail, an AI reasoning log, and a self-monitoring system that reports its own health daily.

That is not a role description. It is a competitive advantage for the organization that deploys it.