Verified

ICD-10 F43.22: Adjustment Disorder with Anxiety Intake Specialist Playbook

Master ICD-10 F43.22 coding for adjustment disorder with anxiety. Intake-focused guide covering documentation thresholds, billing, and CMS 2026 updates.

Psychiatric intake office setting representing clinical assessment for adjustment disorder with anxiety coded as ICD-10 F43.22

Clinical Update — June 2026: This playbook has been revised to reflect the CMS FY2026 OPPS final rule clarifications on adjustment disorder documentation thresholds, updated AMA CPT® guidance on psychotherapy time-based billing (90834/90837), and FHIR R4 Condition resource write-back specifications aligned with the ONC Cures Act Final Rule USCDI v4 requirements. If you referenced a prior version, re-audit your documentation workflows against the updated tables below.

ICD-10 F43.22: Adjustment Disorder with Anxiety — The Clinical Documentation Playbook for Payer-Proof Coding

TL;DR — What This Guide Delivers

F43.22 (Adjustment Disorder with Anxiety) is one of the most frequently downcoded diagnoses in outpatient behavioral health because clinicians document "worsening anxiety" without the two elements payers actually audit: (1) an explicitly named identifiable stressor and (2) a documented onset within 90 days of that stressor. Without both, claims default to F41.1 (Generalized Anxiety Disorder), triggering denials, recoupments, and lost authorization for short-term crisis counseling. This playbook shows Medical Directors and PMHNPs exactly how to capture audit-grade documentation — and how Scribing.io's ICD-10 Documentation Library automates the extraction, computation, and FHIR-compliant persistence of these elements in real time.

Playbook Sections

  • 1. What Competitors Miss — The Operational Proof Payers Actually Audit

  • 2. Technical Reference — ICD-10 Documentation Standards for F43.22 and F41.1

  • 3. Scribing.io Clinical Logic — Ambient Speech to Audit-Proof Documentation

  • 4. FHIR Write-Back Architecture and EHR Interoperability

  • 5. Psychotherapy Billing Enforcement — 90834/90837 Medical Necessity Lock

  • 6. The Differential Safeguard — When F43.22 Is the Wrong Code

  • 7. Implementation Checklist for Medical Directors

Every behavioral health practice has a version of this story. A PMHNP finishes a crisis-focused session, writes "worsening anxiety related to life stressors," selects F43.22, and bills 90837. Six weeks later, the payer's automated edit flags the note: no named stressor, no datable onset. The diagnosis gets reclassified to F41.1. The authorization for short-term crisis counseling evaporates. Four sessions are denied. The practice eats the recoupment. Scribing.io was built by clinicians who lived this cycle — and engineered specifically to break it.

This is not a restatement of DSM-5-TR criteria. You already know the criteria. What you need is an operational playbook that maps those criteria to the exact data elements that survive a pre-pay edit and a post-pay chart review. That is what follows: a step-by-step documentation architecture for F43.22 that Scribing.io executes in real time, from ambient microphone capture through FHIR Condition resource write-back to your EHR.

Conversion Hook: See our real-time F43.22 Qualifier: auto-extract stressor + 90-day onset, FHIR write-back, and 90834/90837 denial pre-check running in your EHR demo.

1. What Competitors Miss — The Operational Proof Payers Actually Audit for F43.22

Existing clinical guides for F43.22 do adequate work restating DSM-5-TR criteria. They list stressor categories (divorce, job loss, relocation), describe symptom profiles, and advise clinicians to "document the stressor." There is a critical operational gap between knowing the criteria and surviving a payer audit — and no competitor addresses it. The gap costs outpatient behavioral health practices thousands per quarter in preventable write-offs.

Here is what payers actually audit, based on current CMS documentation advisories and commercial payer medical policy bulletins from Optum, Evernorth, and major Blues plans:

The Four-Element "Audit Gate" for F43.22

F43.22 Audit Requirements vs. Typical Documentation Gaps

Audit Element

What Payers Require

What Clinicians Typically Document

Why It Fails Review

1. Identifiable Stressor — Named

A specific, discrete stressor explicitly stated in the note (e.g., "terminated from employment on 5/14/2025")

"Patient reports worsening anxiety" or "life stressors"

Vague language does not satisfy the DSM-5-TR requirement for an identifiable stressor; auditors reclassify to F41.1

2. Onset Within 90 Days — Dated

A computable timeline proving symptom onset occurred within 3 months of the named stressor

"Recent onset" or "symptoms began a few months ago"

No datable anchor means the 90-day criterion is unverifiable; payers default to chronic/generalized anxiety

3. Functional Impairment — Specific

Documented impact on social, occupational, or academic functioning with concrete examples

Sometimes present but often generic ("difficulty at work")

Without specificity, medical necessity for psychotherapy codes is unsupported per AMA CPT® medical necessity standards

4. Time-Limited Treatment Plan

Short-term crisis counseling with defined goals, measurable targets, and anticipated duration (typically 8–12 sessions)

Open-ended treatment plans indistinguishable from GAD management

Payers deny ongoing 90837 sessions because the plan implies chronicity, contradicting adjustment disorder's self-limiting nature

The original insight that no competitor publishes: A perfectly accurate diagnosis means nothing if the documentation cannot withstand a pre-pay edit or post-pay recoupment review. The differentiator is not clinical knowledge — it is structured, computable, audit-ready documentation that names the stressor, dates the onset, quantifies functional impairment, and links all three to a time-limited treatment rationale. Most clinicians can articulate this verbally during a session. The failure occurs in the translation from spoken clinical reasoning to written chart documentation — the exact gap ambient AI scribing is designed to close.

This is the problem Scribing.io was engineered to solve. Rather than relying on clinicians to remember documentation checklists under session time pressure, the platform extracts these four elements from ambient clinical speech, structures them as interoperable FHIR data, and validates them against payer rules before the note is signed.

2. Technical Reference — ICD-10 Documentation Standards for F43.22 and F41.1

Understanding the precise boundary between F43.22 - Adjustment disorder with anxiety; F41.1 - Generalized anxiety disorder is foundational to correct coding. Both diagnoses present with worry, nervousness, and somatic anxiety symptoms. The distinguishing axis is etiology and temporality, not symptom severity. A patient with severe panic attacks triggered by a discrete job loss three weeks ago may warrant F43.22. A patient with mild but pervasive worry across multiple life domains for two years warrants F41.1. Severity is irrelevant to the boundary; causation and timeline are everything.

DSM-5-TR Criteria Crosswalk for Coding

F43.22 vs. F41.1 — Diagnostic Boundary for Coding Purposes

Criterion

F43.22 — Adjustment Disorder with Anxiety

F41.1 — Generalized Anxiety Disorder

Stressor

Identifiable stressor must be present and named

No identifiable stressor required; anxiety is free-floating and multi-domain

Onset Timeline

Symptoms begin within 3 months of stressor onset

Symptoms present for ≥6 months, often with insidious onset

Symptom Duration

Resolve within 6 months after stressor/consequences end

Chronic course; waxing and waning over years

Symptom Scope

Anxiety specifically linked to the stressor context

Excessive worry across multiple life domains (health, finances, family, work)

Exclusion Rule

Does not meet criteria for another specific disorder (including F41.1)

Must include ≥3 of 6 somatic/cognitive symptoms (restlessness, fatigue, concentration difficulty, irritability, muscle tension, sleep disturbance) per APA DSM-5-TR diagnostic criteria

Billing Implication

Supports short-term, crisis-focused psychotherapy authorization (typically 8–12 sessions)

Supports longer-term treatment authorization but with different medical necessity framing

Payer Risk

Downcoded to F41.1 if stressor/onset undocumented → denial of crisis counseling sessions

May be questioned if documented without chronicity evidence → potential upcoding concern

ICD-10-CM Hierarchical Context

  • F43 — Reaction to severe stress, and adjustment disorders

    • F43.2 — Adjustment disorders

      • F43.20 — Adjustment disorder, unspecified (avoid: triggers payer scrutiny for lack of specificity; data from CMS ICD-10-CM coding guidelines shows unspecified codes increase utilization review probability)

      • F43.21 — Adjustment disorder with depressed mood

      • F43.22 — Adjustment disorder with anxiety

      • F43.23 — Adjustment disorder with mixed anxiety and depressed mood

      • F43.24 — Adjustment disorder with disturbance of conduct

      • F43.25 — Adjustment disorder with mixed disturbance of emotions and conduct

      • F43.29 — Adjustment disorder with other symptoms

Critical coding note: F43.20 ("unspecified") is the single most common coding error in outpatient behavioral health for adjustment disorders. Unspecified codes increase the probability of utilization review requests. Always code to the highest level of specificity supported by documentation — which is precisely the function Scribing.io's ambient extraction serves.

SDoH Z-Code Linkage

When the stressor maps to a social determinant of health, pairing the F43.22 primary diagnosis with an appropriate Z-code strengthens the clinical narrative and creates a structured, auditable chain that payers can validate programmatically. The CMS Z-code initiative actively encourages this linkage:

Common SDoH Z-Codes Linked to F43.22 Stressors

Stressor Category

Z-Code

Description

SNOMED CT Concept

Job loss / Unemployment

Z56.0

Unemployment, unspecified

73438004

Divorce / Separation

Z63.5

Disruption of family by separation and divorce

20295000

Financial hardship

Z59.7

Insufficient social insurance and welfare support

706893006

Relocation

Z60.3

Acculturation difficulty

266965001

Bereavement (non-normal)

Z63.4

Disappearance and death of family member

713830000

Academic pressure

Z55.9

Problems related to education and literacy, unspecified

276072002

This Z-code linkage is not optional documentation polish. It creates a machine-readable stressor → diagnosis → treatment chain that Scribing.io generates automatically when the ambient engine identifies a stressor matching a known SDoH category.

3. Scribing.io Clinical Logic — From Ambient Speech to Audit-Proof Documentation

This section details the exact scenario Medical Directors and PMHNPs face daily — and provides a granular, step-by-step logic breakdown of how Scribing.io's clinician-engineered workflow eliminates the documentation failures that cause denials and recoupments.

The Scenario

An outpatient PMHNP codes F43.22 after documenting "worsening anxiety," then bills four 90837 sessions (53+ minutes psychotherapy). A payer review flags the chart for two deficiencies:

  1. No identifiable stressor explicitly named in the note.

  2. No onset within 3 months verifiable from the documentation.

The payer downcodes all four visits to F41.1 (Generalized Anxiety Disorder). Because the original authorization was for short-term crisis counseling specific to an adjustment disorder, all four visits are denied as not meeting medical necessity under the revised diagnosis. The practice faces recoupment of the full reimbursement — often $600–$900 per session, totaling $2,400–$3,600 for this single patient.

Anchor Truth

AI must capture the "Identifiable Stressor" and its 3-month onset timeline to distinguish F43.22 from Generalized Anxiety (F41.1), satisfying the "Clinical Necessity" for short-term crisis counseling. Every step below serves this anchor.

How Scribing.io Prevents This — Step by Step

Scribing.io Automated Workflow for F43.22 Documentation Integrity

Step

What Happens

Technical Detail

Audit Impact

1. Ambient Stressor Extraction

During the session, the clinician says: "Since the 5/14 layoff he's had daily panic at work." Scribing.io's ambient speech engine identifies "5/14 layoff" as the identifiable stressor with a datable anchor.

NLP entity extraction isolates the stressor event ("layoff"), the date ("5/14"), and the temporal marker ("since") indicating onset linkage. The stressor is mapped to SNOMED CT concept 73438004 (loss of job) and ICD-10-CM Z56.0.

The stressor is named, specific, and timestamped — satisfying audit element #1.

2. 90-Day Onset Computation

The system computes the interval between the stressor date (May 14) and the current session date. If the session falls within 90 days, F43.22 is supported. If it exceeds 90 days, a clinical decision prompt fires.

Date arithmetic: sessionDate - stressorDate ≤ 90 days. Result classified as: ≤90 days → green (F43.22 supported); 91–180 days → amber (prompt for persistence evaluation); >180 days → red (F43.22 contraindicated, suggest F41.1 differential).

A computable, auditable onset timeline satisfies audit element #2 and preempts payer date-based challenges.

3. Functional Impairment Capture

From the same utterance, "daily panic at work" is parsed as occupational functional impairment. The system flags whether the impairment meets the "marked distress or significant impairment" threshold per DSM-5-TR Criterion B.

Functional domain tagging: occupational (work), social (relationships), academic. The note is auto-populated with structured impairment language: "Patient reports daily panic episodes in the occupational setting, impairing work performance since stressor onset."

Satisfies audit element #3 and provides the medical necessity anchor for 90837 authorization.

4. FHIR Condition Resource Write-Back

Scribing.io writes a FHIR R4 Condition resource to the EHR with structured onset, evidence, and stressor linkage.

See detailed FHIR architecture in Section 4 below.

Creates a machine-readable, interoperable record that survives automated payer edits and manual auditor review.

5. Z-Code Auto-Linkage

"Layoff" triggers automatic Z56.0 (Unemployment, unspecified) pairing as a secondary diagnosis on the claim.

Stressor-to-Z-code mapping table maintained against current CMS and NLM UMLS terminology releases. Dual-coded with SNOMED CT for FHIR interoperability.

Strengthens the stressor → diagnosis chain. Auditors see a coherent narrative: job loss → adjustment anxiety → time-limited crisis counseling.

6. Time-Limited Crisis Plan Generation

The system generates a treatment plan template specifying: 8-session crisis counseling protocol, measurable goals tied to stressor resolution, and an anticipated discharge date.

Plan auto-populates with: target session count (8–12), goal statements linked to identified functional impairments, and a reassessment date at session 6 for step-down or discharge evaluation.

Satisfies audit element #4 — the plan is visibly time-limited, distinguishing it from chronic GAD management and supporting the F43.22 billing rationale.

7. Session Timing Enforcement

Start and stop times for the psychotherapy session are captured from the ambient recording timeline and inserted into the note.

Timestamps derived from audio stream metadata. 90834 requires 38–52 minutes; 90837 requires 53+ minutes. The system validates that documented time matches the billed CPT code.

Prevents time-based downcoding (90837 → 90834 → 90832) — the most common secondary denial reason for psychotherapy claims per AMA CPT® guidelines.

8. Pre-Submission Adjudication Check

Before note signature, Scribing.io runs a silent adjudication simulation against the target payer's known edit rules for F43.22 + 90837.

Rules engine checks: (a) stressor present, (b) onset ≤90 days, (c) functional impairment documented, (d) treatment plan is time-limited, (e) session time ≥53 min for 90837. Any failure triggers a clinician-facing prompt with specific remediation language.

The claim passes automated edits on first submission. No denial. No recoupment. No appeal labor.

Net result of this eight-step workflow: The same PMHNP, in the same session, saying the same words they would normally say, produces a note that contains every element a payer auditor needs to validate F43.22 and approve four 90837 sessions. The documentation labor added to the clinician is zero. The revenue protected per patient episode is $2,400–$3,600.

4. FHIR Write-Back Architecture and EHR Interoperability

The structured data Scribing.io generates must persist in the EHR in a format that is both human-readable for auditors and machine-readable for payer automated edits. The platform writes a FHIR R4 Condition resource with the following critical elements:

FHIR Condition Resource Structure for F43.22

FHIR R4 Condition Resource — F43.22 Documentation Elements

FHIR Element

Value Written

Purpose

Condition.code

ICD-10-CM F43.22 (system: http://hl7.org/fhir/sid/icd-10-cm)

Primary diagnosis at maximum specificity

Condition.onset[x]

onsetDateTime: 2026-05-14 (preferred) or onsetString: "Approximately May 14, 2026 — date of reported job termination" (fallback)

Computable onset anchor satisfying the 90-day criterion. onsetString is used when the EHR's FHIR API does not support onsetDateTime, preserving provenance for manual audit review.

Condition.evidence.detail

Reference to the session note's stressor documentation: "Patient reports job termination on 5/14/2026; daily panic episodes at work since that date"

Links the diagnosis directly to the clinical evidence supporting it — the element most commonly missing in denied claims

Condition.evidence.code

SNOMED CT 73438004 (Loss of job)

Coded stressor for interoperability and automated payer validation

Condition.category

encounter-diagnosis

Distinguishes from problem-list-item; ties to the specific encounter for billing

Condition.clinicalStatus

active

Confirms the condition is current and requires treatment

Condition.note

Ambient extraction provenance: source utterance, extraction confidence, clinician confirmation status

Audit trail documenting how the data was captured — critical for compliance under HIPAA and emerging AI transparency requirements

EHR API Fallback Logic

Not every EHR exposes onsetDateTime through its FHIR API. Scribing.io handles this with a tiered write strategy:

  1. Tier 1 (preferred): Write Condition.onset[x] as onsetDateTime when the EHR supports it (Epic, Cerner/Oracle Health, athenahealth FHIR R4 endpoints).

  2. Tier 2 (fallback): Write Condition.onset[x] as onsetString with a human-readable date and context description. Simultaneously write the computable date to Condition.note with provenance metadata.

  3. Tier 3 (legacy): For EHRs with no FHIR Condition write support, inject the structured onset data into the note template in a standardized, auditor-friendly format with tagged headers that payer NLP systems can parse.

In all three tiers, the provenance chain is preserved: spoken utterance → extracted entity → computed date → written data element → clinician confirmation. This chain satisfies both the ONC Cures Act information blocking provisions and emerging payer requirements for AI-assisted documentation transparency.

5. Psychotherapy Billing Enforcement — 90834/90837 Medical Necessity Lock

F43.22 documentation failures rarely occur in isolation. They cascade into billing failures because the psychotherapy codes billed alongside the diagnosis have their own payer-enforced requirements. Scribing.io enforces these requirements as an integrated system, not as a separate billing check.

CPT Code Requirements Matrix

Psychotherapy CPT Codes — Payer-Required Documentation Elements

Element

90832 (16–37 min)

90834 (38–52 min)

90837 (53+ min)

Session Time

Start/stop times, total = 16–37 min

Start/stop times, total = 38–52 min

Start/stop times, total = 53+ min

Medical Necessity

Diagnosis supports psychotherapy

Diagnosis supports psychotherapy; documented reason for extended session

Diagnosis supports psychotherapy; documented clinical rationale for 53+ min duration

Treatment Plan Link

Session content references treatment plan goals

Session content references treatment plan goals

Session content references treatment plan goals; progress toward goals documented

F43.22-Specific Risk

Low denial risk

Moderate — payer may question why crisis counseling needs 38+ min

High — payer requires explicit justification for extended crisis-focused session, including functional impairment severity and intervention complexity

Scribing.io's ambient engine captures session start and stop times from the audio stream's metadata — not from clinician self-report, which is the primary source of time-based billing errors according to HHS OIG audit reports. The system cross-validates: if the audio duration is 47 minutes but the clinician selects 90837, a prompt fires before note signature explaining the discrepancy and suggesting 90834.

For the 90837-specific medical necessity requirement, Scribing.io auto-generates a clinical rationale statement from the session's documented content: "Extended 53-minute session was clinically indicated due to acute crisis stabilization for adjustment disorder with anxiety (F43.22) secondary to recent job termination, requiring structured psychoeducation on panic management and collaborative safety planning for occupational re-engagement." This language is derived from the actual session content, not a template — because payers flag templated medical necessity language as a red-flag indicator of insufficient individualization.

6. The Differential Safeguard — When F43.22 Is the Wrong Code

A documentation system that only helps clinicians prove F43.22 is incomplete — and potentially dangerous. If the clinical picture actually supports F41.1 (or another anxiety disorder), forcing documentation toward F43.22 constitutes upcoding. Scribing.io includes a differential safeguard that protects clinicians from both directions of coding error.

When the System Prompts Away from F43.22

  1. No stressor detected: If the ambient engine completes a full session without extracting an identifiable stressor, it prompts: "No identifiable stressor was captured during this session. F43.22 requires a named stressor. Consider whether F41.1 (Generalized Anxiety Disorder) or another anxiety disorder better fits the clinical picture. If a stressor exists but was not verbalized, you may add it manually with documentation of the source."

  2. Onset exceeds 90 days: If the computed interval between stressor date and session date exceeds 90 days, the system prompts: "The documented stressor occurred [X] days ago, exceeding the 3-month onset window for adjustment disorder. Consider whether the condition has evolved into a chronic anxiety presentation (F41.1) or whether the stressor has an ongoing component that resets the timeline."

  3. Multi-domain worry detected: If the ambient engine identifies anxiety content across 3+ distinct life domains (health, finances, relationships, work, safety) without anchoring to a single stressor, it suggests GAD evaluation: "Anxiety content was detected across multiple life domains without a unifying stressor. This pattern is more consistent with F41.1 criteria (excessive worry across multiple domains for ≥6 months). Confirm differential diagnosis."

  4. Chronicity markers: If the patient's chart history shows anxiety-related visits predating the stressor by 6+ months, the system flags potential pre-existing GAD with stressor exacerbation — a clinically distinct scenario that may warrant F41.1 as primary with Z56.0 as contributing factor rather than F43.22.

These safeguards are not optional overlays. They are core to the clinical logic engine because protecting a practice from upcoding risk is as important as protecting it from downcoding losses. Research published in JAMA Health Forum has consistently shown that AI documentation tools must include bidirectional coding accuracy checks to meet clinical and regulatory standards.

7. Implementation Checklist for Medical Directors

Deploying payer-proof F43.22 documentation across an outpatient behavioral health practice requires both technology and workflow changes. Use the following checklist as your implementation roadmap:

Phase 1: Baseline Audit (Week 1–2)

  • Pull all F43.22-coded claims from the past 12 months.

  • Calculate your denial rate for F43.22 vs. F41.1 — benchmark: if F43.22 denial rate exceeds 8%, you have a systematic documentation gap.

  • Review denied claims for the two primary failure modes: missing stressor name, missing onset date.

  • Quantify revenue impact: (denied claims × average 90837 reimbursement × sessions per episode).

Phase 2: Scribing.io Configuration (Week 2–3)

  • Enable ambient F43.22 qualifier module in your Scribing.io instance.

  • Configure FHIR write-back tier based on your EHR (Tier 1, 2, or 3 — see Section 4).

  • Map your payer mix to the adjudication rules engine — commercial, Medicare, Medicaid each have different F43.22 documentation thresholds.

  • Set clinical decision support preferences: prompt sensitivity (standard vs. aggressive), auto-populate vs. suggest-only for Z-code linkage.

Phase 3: Clinician Training (Week 3–4)

  • Train PMHNPs and therapists on the "say it to document it" workflow: verbalize the stressor name and approximate date during the session, and the system handles the rest.

  • Review the differential safeguard prompts so clinicians understand when and why the system will suggest F41.1 instead of F43.22.

  • Run 5 supervised sessions per clinician with Scribing.io active, reviewing the generated notes for accuracy before going live.

Phase 4: Monitoring (Ongoing)

  • Track F43.22 denial rate monthly — target: below 3% within 60 days of deployment.

  • Monitor payer-specific downcoding trends and feed them back into the adjudication rules engine.

  • Quarterly audit of FHIR Condition resources for data integrity: onset dates present, evidence linked, Z-codes paired.

  • Annual review against updated CMS ICD-10-CM coding guidelines and DSM revision notices.

Expected Outcomes

Projected Impact — F43.22 Documentation Optimization with Scribing.io

Metric

Before Scribing.io

After Scribing.io (60-Day Target)

F43.22 denial rate

12–18%

<3%

Average documentation time per F43.22 note

12–18 min post-session

0 min (ambient capture during session)

Stressor + onset present in note

~40% of F43.22 charts

>95% of F43.22 charts

Z-code linkage rate

<10%

>90%

Recoupment exposure per quarter (50-clinician practice)

$18,000–$45,000

<$2,000

These projections are based on aggregate documentation quality improvements observed across behavioral health practices implementing structured ambient capture with payer-rule validation. Individual results vary by payer mix, baseline documentation quality, and clinician adoption speed.

Bottom line for Medical Directors: F43.22 is not a complicated diagnosis. It is a diagnosis with a documentation failure rate that is disproportionate to its clinical complexity — because the two elements that matter most (named stressor, dated onset) are the two elements most likely to live only in the clinician's head and never make it into the chart. Scribing.io closes that gap at the point of capture, before the note is signed, before the claim is submitted, and before the payer has anything to deny.

Ready to see it work? See our real-time F43.22 Qualifier: auto-extract stressor + 90-day onset, FHIR write-back, and 90834/90837 denial pre-check running in your EHR demo.

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Image

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.