Skip to content

The platform

One platform for the note, the codes, and the claim.

Pinotage Health unifies ambient documentation, intelligent coding, and billing automation into one continuous workflow: from the first word of the visit to the final payment, the encounter is documented, coded, and billed from one record.

Schedule a demo See how it works
Document Code Bill
HIPAA compliant · attested via Scytale

Pillar 1 · Ambient scribe

Automated Clinical Documentation

An evolving record of the consultation: your note builds itself as the visit unfolds.

Pinotage's ambient scribe doesn't wait for the visit to end. It transcribes the conversation as you speak and rebuilds the chart moments behind it, so a structured clinical note, a patient-facing after-visit summary, and any orders (imaging, labs, referrals, home programs) assemble live in front of you. Your note appears the moment it's ready, while deeper coding and compliance checks finish in the background.

  • Ambient capture, transcribed and diarised as you speak
  • Structured note, after-visit summary, and orders built live during the visit
  • Shaped by your own templates, preferences, and spoken voice macros
  • Edit mode preserves the changes you make as the note keeps updating

What one visit produces

One capture · many outputs

Structured clinical note

Shaped by your template and preferences, in your section format.

After-visit summary

A patient-facing recap of the visit, ready to share.

Orders

Imaging, labs, referrals, and home programs, drawn from the plan.

Documentation checklist

A live list of what's still missing for a compliant note.

ICD-10-CM diagnoses

Validated against real CMS / ICD-10 coding rules.

CPT / HCPCS procedures

Finalized with NCCI compliance edits and modifiers.

While the patient is still in the room

A live checklist of what the note still needs.

The scribe tracks an open-loop checklist as you talk, surfacing what's missing or contradictory for a complete, compliant note, so you can fix it before the patient leaves.

The checklist asks structured questions spanning the major clinical groups, and only the ones relevant to the visit in front of you. It also raises conflict items on the fly, like a documented penicillin allergy against a "no allergies" note, or a left/right laterality mismatch. The questions are anchored to the actual CMS/AMA Medical-Decision-Making data-element definitions.

  • Questions scoped to the visit at hand, across the major clinical groups
  • Flags missing, assumed, conflicting, and verified items
  • On-the-fly conflict detection (allergies, laterality, and more)
  • One-tap correction with the right control for each item

Pillar 2

Intelligent Coding & Compliance

Coding you can defend, with the reasoning to back it up.

The platform derives ICD-10-CM diagnosis codes during the visit and procedural CPT and HCPCS codes at finalization, then checks every code against real CMS and ICD-10 rules. Any diagnosis code that breaks a rule is dropped, and a code can never be invented; the National Correct Coding Initiative (NCCI) procedure-to-procedure, per-day, and add-on edits payers use are applied as well. Compliance issues are flagged while the encounter is still open, so they can be resolved before the claim is submitted, because accurate coding is what keeps the revenue cycle moving.

  • ICD-10-CM diagnoses and CPT / HCPCS procedures from the same encounter
  • Built-in safeguards enforce real ICD-10 rules, and only ever remove codes
  • Built-in NCCI edits (PTP bundling, per-day caps, add-on parent checks)
  • Highest-value supportable coding, fee-schedule aware: every modifier must cite its evidence
  • Guardrails for known over-coding traps, like the G2211 visit-complexity add-on

Pillar 3

Billing & Invoice Settlement Automation

Carry a clean, coded encounter straight into the revenue cycle.

Because the note and its codes originate from the same captured encounter, what reaches billing is already structured and compliance-checked. Pinotage Health automates the steps that usually consume administrative hours (claim submission, settlement tracking, patient billing, and follow-ups) with status visible to billing staff and the clinician throughout.

  • Electronic claim submission
  • Settlement tracking
  • Patient billing
  • Automated follow-ups
  • Less manual paperwork across the team

Who it's for

Outcomes for clinicians and the organizations behind them.

The same workflow that gives doctors their time back gives health organizations a faster, cleaner revenue cycle.

For clinicians

Get the documentation hours back.

  • The note drafts live during the visit, not after hours
  • Review and sign every note, nothing posts without you
  • ICD-10 and NCCI checks run in the background, off your desk

For healthcare organizations

A cleaner, faster revenue cycle.

  • Coded, compliance-checked encounters reach billing claim-ready
  • Real-time revenue-cycle insight and audit-ready coding trails
  • Coded results written back to the EHR over HL7 FHIR

Coding you can trust

Hard guardrails around every suggested code.

Real CMS and ICD-10 rules are enforced before anything reaches a claim: the AI suggests codes, deterministic rules decide what's allowed, and a clinician signs off.

Safeguards that can only remove codes

Every diagnosis code is checked against the current ICD-10 master and the official coding guidelines before it reaches a claim, and codes that conflict, hedge an uncertain diagnosis, sit in the wrong order, or mismatch anatomy or laterality are flagged or removed. The safeguards can never invent a code.

NCCI compliance edits, applied before submission

On the finalized procedure set, Pinotage runs the CMS National Correct Coding Initiative checks payers run: procedure-to-procedure (PTP) bundling, Medically Unlikely Edit (MUE) per-day unit caps, and add-on code (AOC) parent validation.

Evidence-cited modifiers, highest-value ordering

Modifier choices (-25, -59, -50, -RT and others) must cite the specific clinical or fee-schedule evidence that justifies them, and suggested codes are ordered so the highest-value supportable coding leads, aware of the current fee schedule.

Guardrails against known over-coding errors

Known over-coding traps, like the G2211 visit-complexity add-on, are suppressed whenever CMS conditions disqualify them, defending against the most common misuses before a payer ever sees the claim.

Built for the way you practice

The note is shaped by you, not a fixed format.

Templates, preferences, and spoken macros mean the scribe charts the way you do. And as the note updates live, your manual edits are preserved.

Your note templates

The scribe works to the clinical-note template you choose (your sections, your structure) so output reads like your charting, not a generic format.

Your preferences

Set detail level, bullet-only formatting, and how the note should refer to you. Your preferences shape every version of the note as it builds.

Spoken voice macros

Define trigger phrases that expand into pre-written text: say 'RC standard repair' and a full procedure paragraph drops into the note.

Edits that survive updates

The note updates live as the visit unfolds, and keeps building without overwriting the edits you've made by hand.

Interoperability

Standards-based EHR integration over HL7 FHIR.

Pinotage Health connects to the EHR through the Redox interoperability platform using HL7 FHIR R4, reading the patient's context before the visit and writing the finished encounter back after it.

Connections are authenticated with the SMART backend-services OAuth flow, with no shared passwords. Patient data is parsed into validated FHIR resource types, and write-back tracks each resource individually with PHI-safe error handling and idempotent re-submit. Production EHR write-back is being rolled out and validated per-EHR; document and encounter write-back work in the integration sandbox today.

Comparing vendors? We wrote up the six questions to ask any scribe vendor about EHR integration, including the ones we'd want asked of us.

Coded-resource write-back: rolling out per-EHR

Reads before the visit

Patient context, pulled from the chart.

Patient Encounter Condition CareTeam Appointment Practitioner

Writes back after the visit

  • The encounter: Posted back as a FHIR Encounter.
  • Diagnoses: Written as coded Conditions.
  • Orders: Written as ServiceRequests.
  • The note: Written as a DocumentReference.

Works with

Connected through our Redox partnership over HL7 FHIR R4.

Standards-based read and write-back is the design for every connection. Coded write-back is rolling out per-EHR.

  • Epic
  • Oracle Health (Cerner)
  • athenahealth
  • MEDITECH
  • Veradigm
  • eClinicalWorks
  • NextGen
  • + more via Redox

All product names and marks belong to their respective owners. Listing reflects connectivity via Redox, not vendor endorsement.

Under the hood

One source of truth, end to end.

The visit is captured once, and everything downstream (note, checklist, codes, claim) is built from that single record.

Your note appears the moment it's ready, while deeper coding checks finish in the background. And because the note, the codes, and the claim all originate from the same encounter, errors are caught early and the revenue cycle moves faster.

  • Runs the full workflow, from the visit through claim payment
  • Reads and writes back to your EHR over standards-based HL7 FHIR
  • Real-time insight into compliance and the revenue cycle
  • Automates the back-office steps that drive operational cost

One captured encounter

  1. Clinical note

    Ambiently captured, structured, reviewed.

  2. Codes applied

    Drawn from the same note, checked against real CMS rules.

  3. Claim submitted

    Clean claim, tracked to settlement.

  4. Synced to your EHR

    Encounter, codes, orders, and note written back over FHIR.

See how a single visit becomes a note, its codes, and a clean claim.

Schedule a demo

On our roadmap

Where the platform is heading.

A look at what we're building next. These are forward-looking: in development or validation today, not generally available.

In development

Pinotage AI: a code & guideline assistant

A doctor-facing chat that answers CPT, HCPCS, and ICD-10 questions and explains CMS/AMA billing guidance (grounded in the official code sets and guidance, with mandatory citations), and when it can't ground an answer, it says so instead of guessing. It is designed to explain why the platform generated each code for a given encounter, behind a strict authorization gate.

In development

Code suggestions grounded in the real code set

A coding path designed so the platform can only choose from verified, real codes: every suggestion grounded in the complete, current code set, never an invented one. It is being validated against live encounters for comparison today, not as the default.

In development

Deeper EHR write-back, and launch from the chart

Building toward end-to-end transmit of coded diagnoses, procedures, and orders into production EHRs, a scheduling feed that pre-populates the day's patient list, and SMART/SSO launch of Pinotage from inside the EHR.

You stay in charge

What the clinician keeps control of.

The scribe drafts and the rule checks run in the background. These three things always wait for you.

The note

Nothing reaches the patient record until you've reviewed and approved it, and your manual edits survive the live updates.

The codes

Every suggestion is checked against real CMS and ICD-10 rules, and the safeguards can only remove a code, never invent one.

The modifiers

Each modifier carries the clinical or fee-schedule evidence that justifies it, so you can see why it's on the claim.

HIPAA compliant, attested via Scytale
See it in action

Walk through the full workflow with our team.

We'll show you how a single visit becomes a note you'd sign and a claim that clears.

Schedule a demo Talk to our team

HIPAA compliant · No commitment · 30-minute call