Every essential duty and knowledge requirement from the Security Compliance Administrator II position description is addressed below with the specific ACIS capability that demonstrates it โ and a live endpoint or UI location where it can be verified.
Demonstrated by: The entire ACIS system. This is not a plan for a compliance program โ it is a running compliance program. Four modules cover the four primary compliance domains in healthcare administration (regulatory monitoring, attestation, vendor risk, incident response), unified under a single Executive Hub dashboard.
RxDC โ Demonstrated by: Attestation Vault tracks rxdc_status per client plan: Pending โ Submitted โ Confirmed โ Overdue. Completion percentage is surfaced on the dashboard. The regulatory scraper flags every CMS bulletin that affects RxDC reporting deadlines.
Gag Clause โ Demonstrated by: Attestation Vault tracks gag_clause_status per client: Not Started โ In Progress โ Attested โ Overdue. Independent lifecycle from RxDC because attestation timelines differ.
CMS โ Demonstrated by: CMS is one of three Federal Register feed sources and one of two Firecrawl newsroom sources. Every CMS bulletin is ingested, scored, and surfaced within 24 hours of publication. CMS-specific risk events are tagged and searchable in the Live Pulse panel.
Demonstrated by: Regulatory Pulse module. Five live data sources:
Each document is scored by Claude: risk_level (High/Medium/Low), impacted_field (RxDC/GagClause/HIPAA/GeneralSecurity), summary, remediation_step, and deadline. The Live Pulse panel surfaces the 50 most recent of 65 scored documents from a continuously growing database.
Demonstrated by: Heartbeat Agent. Every morning, after the scraper runs, a 13-query D1 audit checks:
Claude produces a Green/Yellow/Red assessment per module and a list of specific action items. Available via GET /api/heartbeat/last or the Operations tab.
Demonstrated by: Incident Response module. Every incident automatically receives a NIST SP 800-61 Rev 2 playbook before the creation response returns. The playbook includes:
45 CFR ยง 164.404, 45 CFR ยง 164.312(a)(1))Demonstrated by:
rxdc_status and gag_clause_status lifecycle tracks remediation per clientOpen โ Contained โ Remediated โ Closed) with closed_at timestampoverall_status lifecycle tracks remediation per vendor (Pending Review โ Approved or High Risk โ Requires Review)Demonstrated by: Vendor Risk module. The scanner assesses security controls at each vendor's web presence:
Demonstrated by:
acis.rossonlineservices.com โ visual summary of all four compliance domains| Requirement | ACIS Demonstration |
|---|---|
| NIST framework | Incident playbooks are grounded in NIST SP 800-61 Rev 2 by system prompt instruction; all five phases implemented |
| ISO 27001 | Planned โ see Roadmap |
| SOC 2 Audit management | Planned โ see Roadmap |
| Annual RxDC reporting | Attestation Vault rxdc_status lifecycle with completion percentage tracking |
| Annual Gag Clause Attestation | Attestation Vault gag_clause_status lifecycle, independent of RxDC |
| Vendor Management | Vendor Risk module with real security scanning, risk classification, and status tracking |
| Analytical and risk assessment skills | Four Claude agents, five inference calls โ risk scoring, playbook generation, vendor assessment, system health audit |
| Written and verbal communication | Every AI output (playbooks, risk summaries, heartbeat reports) demonstrates precise regulatory language |
| Executive reporting | Executive Hub + Heartbeat Agent provide the reporting layer |
| Project management | CCC Admin tracks this project: 10 modules, 5 agents, 8 planned features, version history |