NoteLane — Field Documentation & Wisconsin DHS 36 Pre-Flight for Community Providers

Presence-First Community Documentation

Be fully there for the human work. Let NoteLane carry the paperwork home.

Community mentoring, skill-building, and recovery work happen on front porches, in kitchens, on trails, and in cars — not behind a hospital desk. Built by a Wisconsin CCS practitioner, NoteLane turns a 60-second voice debrief in your car after session into a grounded, person-first progress note that passes every county QA and State of Wisconsin DHS 36 check on the first try.

100% Isolated Per-Provider Workspaces: Every subscribing provider operates in a private, encrypted workspace with their own client roster, Recovery Plan goals, billing credentials, and handwritten signature.

In-App Encrypted Recovery Plan PDF Intake (Zero PHI in Email): Drop a county Recovery Plan PDF directly into your authenticated HTTPS workspace — NoteLane extracts verbatim ISP goals & objectives in RAM, builds your client's .docx templates, and immediately shreds the PDF.

Hot-Adaptable Wisconsin DHS 36 & County Rule Engine: Validates service time math, verbatim ISP goals, in-car transport vs. billable mileage separation, and future Next Plan dates — and adapts instantly when county QA or state auditors update a requirement.

Designed for One Thumb in the Car After Session

Documentation shouldn't steal your evenings or pull your eyes away from the person sitting across from you.

Step 1 · Presence

Stay Unhurried in the Session

Keep your phone in your pocket and your attention on the person in front of you. No typing during session, no clinical clipboards in the room.

Step 2 · 60-Second Debrief

Speak Naturally Before You Drive Off

Capture what you worked on, how the member responded, and where you drove while the session is still vivid. Your voice brief stays strictly private.

Step 3 · One-Tap Closeout

Proof, Approve & Export Your .docx

Tap once to verify times and mileage, see your 16/16 Pre-Flight green light, and download your signed Word (.docx) file or copy for RWC Avatar.

How NoteLane Protects Client Confidentiality (HIPAA Security Architecture)

Engineered from the ground up so providers, contracted agencies, and county programs can trust every step of documentation.

Pillar 1 · Infrastructure

AWS HIPAA BAA & Encrypted Storage

Hosted on dedicated AWS (us-east-2 Midwest) infrastructure covered by an active AWS HIPAA Business Associate Addendum (BAA), with AES-256 encrypted gp3 volumes and automated 35-day encrypted snapshots.

Pillar 2 · Multi-Tenancy

Strict Per-Provider Workspace Isolation

Every subscribing provider operates inside a cryptographically isolated workspace (tenants/<provider_id>/). No provider — and no outside agency — can ever view, query, or access another provider's client roster, voice briefs, or progress notes.

Pillar 3 · Zero Email PHI

In-App Encrypted Recovery Plan Intake

Account setup and subscription billing never touch client information. Providers onboard clients strictly inside their authenticated HTTPS (TLS 1.3) workspace by dropping in a county Recovery Plan PDF — the parser extracts verbatim goals in RAM, builds the .docx templates, and immediately shreds the PDF.

Pillar 4 · Voice Privacy

Ephemeral Voice-to-Note Processing

Post-session voice briefs are processed strictly to generate the structured progress note in the provider's house style and are never used to train external AI models or shared across accounts.

Pillar 5 · Pre-Flight Validator

16-Point County & DHS 36 Pre-Flight

Built-in validator enforces county and state compliance (verbatim Recovery Plan goals, 12-hour standard time, in-car drive intervention rules, exact mileage/documentation minutes, and [Initials]- MM.DD.YYYY.docx naming) before a note ever leaves the app.

Pillar 6 · Audit & Access Control

Per-Provider Audit Trail & Session Security

Every view, edit, approval, and .docx export is recorded in an immutable, per-provider HIPAA audit log (0600 permissions) protected by HttpOnly; Secure; SameSite=Strict cookies and brute-force rate limiting.

Built for State of Wisconsin DHS 36 & County QA Audits — With Instant Rule Adaptability

Every progress note is checked against all 12 Wis. Admin. Code § DHS 36.16–36.18 (Comprehensive Community Services) and county QA inspection points before export — and our declarative audit engine lets new county or state audit feedback be applied across templates and notes immediately:

1. Client & County Header (DHS 36.18): Recipient Name, DOB, County Agency & Service Facilitator match.

2. Exact Time & Duration Math: 12-hour AM/PM start/stop times (zero midday AM typos) & exact elapsed Service Minutes.

3. Authorized Service Array (DHS 36.17): Exact match to Recovery Plan authorization (ISDE, Service Planning, WMR, etc.).

4. Specific WI Place of Service: Explicit municipality + absent-client virtual dual-location rule when applicable.

5. Verbatim Recovery Plan Goal (DHS 36.16): Word-for-word Goal, numbered Objectives & Provider Action Plan bolded in P[8].

6. Active Skill-Building Interventions: Concrete provider interventions tied directly to the member's Recovery Plan.

7. Member Response & Progress: Observable client response and progress toward objectives in person-first language.

8. In-Car Community Transport Separation: Goal work during in-session drives documented in body; never mixed into billable travel.

9. Billable Travel Origin & Destination: Explicit from origin and to destination (never ambiguous toward) with paired miles/minutes.

10. Continuity of Care (Next Plan): Explicit future Next Plan date strictly after Date of Service (Next Plan > DOS).

11. Provider Attestation & Signature: Provider Name, Billing Credentials, embedded handwritten signature & Signature Date >= DOS.

12. Telehealth Consent & Language Bar: Synchronous audio+visual verbal permission & zero forbidden clinical clichés.