From 807dda4d54ac6f06531e9675a5d5b08cc3646541 Mon Sep 17 00:00:00 2001 From: Kisa Date: Tue, 12 May 2026 05:10:13 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20update=20CLAUDE.md=20=E2=80=94=20curren?= =?UTF-8?q?t=20active=20files=20after=20repo=20reorganization?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Sonnet 4.6 --- CLAUDE.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index bf2fd07..c504e75 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,11 +1,13 @@ -# STTIL Solutions — Signal CGM | Level 1 Active Context +# STTIL Solutions — Signal | Level 1 Active Context ## What This Tool Does -Signal CGM is a B2B CGM coverage worklist tool for DMEPOS suppliers. -It ingests shipment data (CSV from Brightree/WellSky), calculates -coverage expiration per patient using device wear-day rules, and -produces a prioritized worklist so small DME teams can do proactive -outreach BEFORE claims deny. +Signal is a B2B CGM documentation readiness tracker for DMEPOS suppliers. +It ingests order data from any DME order management CSV export (e.g., Brightree), +evaluates each patient against documentation requirements (6-month qualifying +visit, PECOS enrollment, SWO, resupply eligibility), and produces a Signal Report +so supplier staff can prioritize outreach and capture revenue before it leaks. +NOTE: Signal identifies gaps. It does not conduct outreach. Never write copy +implying Signal contacts prescribers or patients directly. ## Core Value Proposition Shifts supplier staff time from reactive (appeals after denial) @@ -34,11 +36,10 @@ and stays predictable. ## Active Files - python-backend/core/coverage_calculator.py - python-backend/core/audit_logger.py -- python-backend/core/db_models.py - python-backend/config/payer_rules.json -- Projects/DMEPOS/dmepos-research-v3.md (market context) -- Projects/DMEPOS/compliance-roadmap-v1.md -- Projects/Newsletter/newsletter-strategy-v1.md +- research/dmepos-research-v3.md (market context) +- docs/hipaa-deployment-analysis-v1.md (compliance) +- docs/sttil-brand-system-v1.md (brand) ## Current BAA Obligations (Level 1 Only) - Hostinger VPS: Request BAA (PHI host) @@ -48,7 +49,7 @@ and stays predictable. ## Workload Impact Model (Build This) Two-curve graph showing supplier staff time over months: - Curve A: Appeals/denials workload (reactive) — starts HIGH, trends DOWN -- Curve B: Proactive outreach via Signal CGM — starts MANAGEABLE, stays FLAT +- Curve B: Proactive outreach via Signal — starts MANAGEABLE, stays FLAT - X-axis: Months 1–12 post-onboarding - Crossover point = ROI moment to show on discovery calls @@ -69,3 +70,4 @@ Two-curve graph showing supplier staff time over months: - When building calculations, reference payer_rules.json for wear days - When building audit logs, always hash patient_id before storing - If asked about Phase 2/3, acknowledge and defer — do not spec or build +- Use "resupply" not "refill". CGM supply allowances are exempt from Medicare refill rules