Blue Sage Data Systems
A use case we run for Lincoln healthcare providers

AI for medical records — Lincoln healthcare

Ambient documentation, prior-auth letter drafting, denials response, coding support — drafted by AI, signed by the clinician or coder. Built on a Business Associate Agreement, with the audit trail HIPAA expects.

Omaha companies asking the same? See the Omaha view →

Text Rosey · Schedule a call →

The workflow, end to end

What goes in, what the AI does, what comes out, what your team gets back.

Input
Patient encounter (audio or transcript) + EHR context + prior auths and denials queue
Work
Draft clinical note, prior-auth letter, denials response, coding suggestion; flag PHI handling exceptions
Output
Clinician-reviewable note draft, prior-auth packet, denials response in queue, coding suggestions
Saved
5–15 minutes per encounter on documentation; 10–20 minutes per prior-auth packet

What this looks like in production

Medical records work has the highest documentation burden in healthcare and the strictest data-handling requirements. AI fits well because the work is high-volume, structured, and reviewable.

At a Lincoln health system, the workflow that scales is AI-drafts-and-clinician-signs. Ambient documentation captures the encounter, AI drafts the clinical note in your EHR's format, the clinician reviews and signs. Prior auths and denials follow the same pattern.

The governance discipline: HIPAA-covered entities cannot put PHI into a tool without a Business Associate Agreement. Enterprise tiers offer BAAs; consumer tiers do not. HHS OCR's January 2025 NPRM would treat AI software touching ePHI as inventoriable. Section 1557's affirmative duty to identify and mitigate bias risk in patient-care decision-support tools became effective May 1, 2025.

How we run it

  1. Identify the AI vendor with a BAA, no-training data handling, SOC 2 reports.
  2. Map the AI's role per workflow — drafter, packet-assembler, suggester. Never decider for clinical care.
  3. Build the ambient documentation flow — capture, draft, clinician review and sign.
  4. Build the prior-auth flow — pull from chart and policy, draft the packet, specialist reviews and submits.
  5. Build the denials-response flow — analyze denial reason, pull supporting evidence, draft appeal.
  6. Bias-mitigation discipline for any AI that influences clinical decisions.

Common questions

Do we need a BAA with the AI vendor?
Yes — full stop, before any PHI touches the tool. Consumer-tier use with PHI is a HIPAA violation.
What about HHS OCR's HIPAA Security Rule NPRM?
Not yet finalized as of mid-2026. Proposed rule would treat AI software touching ePHI as inventoriable. Treat as expected forward direction.
Does Section 1557 apply to all AI use?
Section 1557 applies to AI used in patient-care decision-support tools, with the affirmative duty effective May 1, 2025.
Can AI handle the prior-auth submission directly?
AI assembles and drafts; specialists submit. Direct submission introduces accountability complications.
Nebraska-specific rules?
No NE DHHS AI-specific guidance as of 2026-05-01. Lincoln providers default to federal HHS OCR / HIPAA / Section 1557 frameworks.

Sources

Related

Use Case
AI for healthcare records
Industry
Healthcare
Service
running AI from strategy to cutover
Service
approved AI tool list and policy
Concern
AI and data privacy concerns
Answer
AI oversight and governance
→ Start here

Text Rosey to begin.

Rosey is our executive-assistant bot. Text the number below — she'll ask two questions, offer three calendar slots, and put a 30-minute call on Jim's calendar.

Text Rosey · Schedule a call →

or call 415 481 2629