Posted on
Feb 9, 2025
Posted on
May 14, 2026
How Qualifacts Credible AI Scribe handles high-acuity workflows. Solve broken objective links, versioned treatment plans & goal-directed documentation gaps.
Qualifacts (Credible) AI Scribe: High-Acuity Workflows — The Clinical Library Playbook for Goal-Directed Documentation
TL;DR
Qualifacts Credible versions Treatment Plans so that Goals and Objectives receive new internal IDs at every revision. Standard exports and the Credible API do not provide a stable historical resolver for retired Objective IDs—meaning Progress Notes silently lose their link to the active Master Plan. In high-acuity behavioral health (e.g., crisis psychotherapy for suicidal ideation coded under 90839/90840), this gap triggers DHHS post-payment recoupment for missing goal-directed documentation. Scribing.io solves this by embedding a durable PlanVersionID–GoalID–ObjectiveID triple in every note, auto-resolving ID rollovers at plan revision, enforcing 90-day plan review guardrails, and maintaining a 6-year audit trail mapped to the correct plan version. This playbook details the clinical logic, ICD-10 documentation standards for F33.2 Major depressive disorder and R45.851 Suicidal ideation, and the exact workflow architecture that prevents revenue loss in state-audited Credible environments.
Why Generic AI Scribes Fail Qualifacts (Credible) Behavioral Health Workflows
The Credible Plan Versioning Problem: Retired Objective IDs and Broken Goal Linkage
Scribing.io Clinical Logic: Crisis Psychotherapy, Plan Revision, and NC DHHS Audit Recovery
Technical Reference: ICD-10 Documentation Standards for F33.2 and R45.851
Goal-Directed Documentation Architecture: The PlanVersionID–GoalID–ObjectiveID Triple
90-Day Plan Review Guardrails and 6-Year Audit Trail Compliance
Workflow Comparison: Generic AI Scribes vs. Scribing.io in Credible High-Acuity Environments
Implementation Pathway: From Credible Configuration to First Compliant Note
Why Generic AI Scribes Fail Qualifacts (Credible) Behavioral Health Workflows
Every major AI scribe comparison published in 2025 and 2026—Freed vs. Nuance DAX vs. Abridge vs. Suki vs. DeepScribe—evaluates tools along axes built for primary care and hospital medicine: SOAP note fidelity, ambient dictation accuracy, EHR push latency, per-encounter pricing. Those are valid criteria if you run a family medicine panel. They are structurally irrelevant for behavioral health organizations operating inside Qualifacts Credible, where the documentation unit is not a SOAP note but a goal-linked Progress Note anchored to a versioned Individualized Treatment Plan (ITP).
Scribing.io exists because that distinction is not cosmetic—it is the difference between revenue retained and revenue recouped. Organizations already evaluating EHR-native scribe architectures through our athenahealth API integration or our Epic Integration pathway understand that each EHR demands a purpose-built logic layer. Credible's demands are uniquely punishing because of four compounding factors:
1. Treatment Plan–Progress Note linkage is a billing predicate, not a best practice. State DHHS agencies—North Carolina, New York (OMIG), Ohio, and others—mandate that every billable Progress Note reference a specific Goal and Objective from the active ITP. Per CMS compliance guidance, documentation must substantiate medical necessity at the claim level. In Medicaid behavioral health, that substantiation flows through the Treatment Plan. A note without explicit goal linkage to the current plan version is an unbillable note.
2. Credible's data model reassigns internal IDs at every plan revision. When a clinician revises an ITP—adding an Objective, updating a measurement target, conducting a mandated periodic review—Credible generates new GoalIDs and ObjectiveIDs. The prior IDs are retired. No stable cross-version resolver exists in standard Credible exports or the Qualifacts API. This is an architectural fact, not a configuration error.
3. Ambient listening cannot solve a data-model problem. An AI scribe that captures session audio, transcribes it, and generates a narrative has zero awareness of which ObjectiveIDs are active in Credible's current PlanVersion. It cannot detect a retired ID reference. It cannot stamp the correct triple. It cannot enforce a review window. The problem is structural, not acoustic.
4. High-acuity encounters draw disproportionate audit scrutiny. Crisis psychotherapy (CPT 90839/90840), sessions documenting active suicidal ideation, and encounters carrying severe recurrent diagnoses like F33.2 Major depressive disorder are the encounters state auditors pull first. Per the APA Practice Guidelines for Major Depressive Disorder, documentation of crisis encounters requires explicit risk stratification, intervention rationale, and treatment plan alignment. A documentation gap here produces the largest per-encounter recoupment.
No tool in any published competitor comparison addresses Qualifacts Credible by name, discusses Treatment Plan versioning, references Goal-Directed Documentation mandates, or acknowledges state DHHS post-payment audit logic. That gap is the operating environment this playbook addresses.
The Credible Plan Versioning Problem: Retired Objective IDs and Broken Goal Linkage
The failure mode described in this section has produced six- and seven-figure recoupments at mid-size behavioral health organizations. Understanding it requires tracing how Credible manages Treatment Plan data at the database level.
How Credible Versions Treatment Plans
When a clinician creates an Individualized Treatment Plan in Credible, the system generates a hierarchical data structure:
A Plan record with an internal PlanID and a PlanVersionID
One or more Goals, each assigned a GoalID scoped to that PlanVersion
One or more Objectives nested under each Goal, each assigned an ObjectiveID scoped to that PlanVersion
Interventions linked to Objectives, specifying modality, frequency, and responsible provider
This structure constitutes the Master Plan. It governs all billable documentation for the episode of care. The SAMHSA treatment planning framework and state-level Medicaid manuals require that this plan be individualized, measurable, and current.
When the plan is revised—whether for a 90-day periodic review mandated by NC DHHS Medicaid policy, a change in clinical acuity, or the addition of a new treatment target—Credible creates a new PlanVersion. In this new version:
Goals that carry forward receive new GoalIDs
Objectives receive new ObjectiveIDs—even when the clinical content is identical
The prior version's IDs are retired—they persist in the database but are no longer the active identifiers
The Export and API Gap
Credible's standard data exports and API endpoints surface the current active plan. They do not provide:
A historical map from retired ObjectiveIDs to successor IDs in the new version
A cross-version resolver that allows an external system to query "which active ObjectiveID corresponds to the concept previously tracked under retired ObjectiveID X?"
A retroactive flag on signed Progress Notes indicating whether their referenced ObjectiveID belongs to the currently active PlanVersion or a retired version
This means a Progress Note written two days before a plan revision—referencing ObjectiveID 4872—will still carry that reference after ObjectiveID 4872 is replaced by ObjectiveID 5301 in the new version. To an auditor pulling the active plan and matching it against Progress Notes, the note appears unlinked to any active Objective. The clinical content may be identical. The structural linkage is broken.
The Audit Consequence
State DHHS auditors conducting post-payment reviews follow a protocol documented in each state's Medicaid provider manual (see NC Medicaid Provider Playbook):
Pull the active Treatment Plan (or the plan version active on the date of service)
Read the Progress Note for the encounter under review
Confirm that the note references a specific Goal and Objective from that plan version
Confirm that the note documents measurable progress toward the stated Objective
Confirm that the plan was reviewed within the required interval (typically 90 days for NC; 180 days for some NY OMIG populations)
If step 3 fails because the note references a retired ObjectiveID, the encounter is denied. If step 5 fails because the 90-day review lapsed and no new PlanVersion was created, every encounter billed after the lapse is denied. These are independent denial vectors. In the scenario grounding this playbook, both fired simultaneously across 28 encounters.
Scribing.io Clinical Logic: Crisis Psychotherapy, Plan Revision, and NC DHHS Audit Recovery
This section provides the granular, step-by-step logic breakdown of how Scribing.io prevents the exact failure mode described above. The scenario is real-world, the denial amounts are representative of NC DHHS enforcement patterns, and the resolution architecture is production-tested.
The Scenario
A mobile crisis clinician in North Carolina documents psychotherapy for crisis (CPT 90839 + 90840, defined in the AMA CPT Manual) in Credible for a patient diagnosed with F33.2 Major depressive disorder, recurrent severe without psychotic features, and active R45.851 Suicidal ideation.
Two weeks earlier, the patient's ITP was revised during a scheduled 90-day review. During that revision, Objective O1.2—"Reduce suicidal ideation from daily frequency to fewer than 1 episode per week as measured by patient self-report and PHQ-9 Item 9"—was carried forward with updated measurement targets. Credible assigned O1.2 a new ObjectiveID (5301, replacing retired 4872).
The clinician, working in a mobile crisis setting with limited connectivity and high cognitive load, writes Progress Notes referencing the retired ObjectiveID 4872 for O1.2. Neither the clinician's memory nor Credible's native interface surfaces the mismatch.
The Failure Cascade Without Scribing.io
NC DHHS conducts a post-payment audit. The state reviews 28 encounters spanning the two-week window after the plan revision. Auditors match Progress Note Objective references to the active PlanVersion. Twenty-eight notes reference ObjectiveID 4872, which does not exist in the active plan. Additionally, a secondary flag notes that the 90-day review, while completed, was not properly timestamped in the note metadata—creating a second denial vector. Total recoupment: $12,320. The clinician's documentation was clinically sound. The system failed structurally.
The Resolution With Scribing.io: Six-Step Logic Chain
Step | Scribing.io Action | Clinical Effect |
|---|---|---|
1. Active Plan Read | At session initiation, Scribing.io queries the Credible PlanVersion endpoint, pulling all active GoalIDs and ObjectiveIDs with their full clinical descriptions, measurement criteria, and review dates | The scribe operates from the ground truth of the current plan—not cached references, not clinician memory, not prior note templates |
2. ID Rollover Detection | Scribing.io maintains an internal version map. When a plan revision is detected (new PlanVersionID since last encounter), the system identifies all retired ObjectiveIDs and maps them to successor IDs using clinical content matching and Credible's hierarchical position data | The clinician receives a real-time prompt: "Objective O1.2 ('Reduce SI frequency') was updated in the plan revision of [date]. The new ObjectiveID is 5301. Please confirm current progress against the active Objective." |
3. Goal-Directed Prompting | The scribe prompts the clinician to verbally state measurable progress against O1.2, including baseline measurement and target. The prompt is structured to elicit audit-defensible language per CMS medical necessity documentation standards | The note captures: "Patient reports SI frequency reduced from daily (baseline at ITP initiation 01/15/2026) to approximately 3 episodes/week. Target per Objective O1.2: <1 episode/week. PHQ-9 Item 9 score: 2, decreased from 3 at last review (02/28/2026). Patient engaged in safety planning and cognitive restructuring per ITP Intervention I1.2a." |
4. Triple Stamp | Scribing.io embeds the durable PlanVersionID–GoalID–ObjectiveID triple (e.g., PV-2026-0312 / G1 / O1.2-5301) into both the structured note metadata fields and the narrative body of the Progress Note | The note is permanently and unambiguously linked to the correct plan version. Any future revision creates a new triple; this note's linkage survives intact for the full 6-year audit lookback window |
5. CPT Element Validation | For 90839, Scribing.io validates presence of: crisis precipitant, risk assessment (SI frequency, plan, intent, means, protective factors), psychotherapy modality delivered, and time documentation ≥60 minutes. For 90840, it validates each additional 30-minute increment with continued crisis justification. Validation logic aligns with AMA CPT coding guidance for psychotherapy for crisis | The note meets payer-specific requirements for crisis psychotherapy billing. Missing elements trigger pre-sign-off alerts, not post-submission denials |
6. Plan Review Window Check | Scribing.io calculates days elapsed since the last PlanVersion creation date. If the 90-day window mandated by NC DHHS (or the applicable state interval) has lapsed—or will lapse before the next scheduled encounter—the system blocks sign-off and generates an alert to both the clinician and the clinical supervisor | No note is finalized against an expired plan. This prevents the second denial vector (lapsed periodic review) independently of the goal-linkage vector |
Result: All 28 encounters documented during the post-revision window carry the correct PlanVersionID–GoalID–ObjectiveID triple, contain validated 90839/90840 elements, and reference the active plan version. The $12,320 in revenue is preserved. The clinician's documentation withstands NC DHHS post-payment review without remediation, appeal, or resubmission.
See our Credible-native Goal Linker in action: real-time PlanVersionID mapping, 90-day review guardrails, and one-click OMIG/NCDHHS audit packet export—book a 20-minute demo today.
Technical Reference: ICD-10 Documentation Standards for F33.2 and R45.851
High-acuity behavioral health encounters in Credible frequently involve the diagnostic pairing of Major Depressive Disorder with active suicidal ideation. Precise ICD-10-CM coding—carried to maximum specificity—is both a clinical documentation standard and an audit-defense requirement. Per CMS ICD-10-CM Official Guidelines for Coding and Reporting, codes must be documented to the highest level of specificity supported by the clinical record.
F33.2 — Major Depressive Disorder, Recurrent Severe Without Psychotic Features
F33.2 Major depressive disorder, recurrent severe without psychotic features, is the correct code when clinical documentation establishes:
Recurrence: At least two distinct major depressive episodes separated by a period of at least two consecutive months without meeting full criteria, per DSM-5-TR diagnostic criteria
Severity — Severe: Most symptoms present, symptom intensity is distressing and unmanageable, and marked interference with social/occupational functioning. PHQ-9 score ≥20 supports but does not replace clinical judgment of severity
Without psychotic features: No hallucinations, delusions, or disorganized thinking documented in the current episode
Documentation trap Scribing.io prevents: Clinicians frequently document "Major Depression, recurrent" without specifying severity or psychotic status. This defaults to F33.9 (unspecified), which lacks the specificity required for crisis-level service authorization and triggers payer requests for additional documentation. Scribing.io's diagnostic prompt requires the clinician to confirm severity level and psychotic feature status before the code is stamped, enforcing F33.2 specificity at the point of care.
R45.851 — Suicidal Ideation
R45.851 Suicidal ideation is reported as a secondary diagnosis when the clinical encounter documents active suicidal ideation. Per the CDC guidelines on suicide documentation and the Joint Commission National Patient Safety Goals, documentation must include:
Presence of ideation: Active vs. passive, with frequency and duration
Plan specificity: Whether the patient has identified a method, timeline, or location
Intent: Stated desire to act on ideation
Means access: Availability of identified method (firearms, medications, etc.)
Protective factors: Reasons for living, social support, treatment engagement
Coding interaction: R45.851 is reported in addition to F33.2—not instead of it. The R code captures the symptom (suicidal ideation) as a focus of clinical attention during the encounter. Omitting R45.851 when SI is documented in the note creates a mismatch between narrative content and coded claims, which is a red flag in both automated claims edits and manual audit review.
Scribing.io's role: During encounter documentation, if the clinician describes suicidal ideation in any form, Scribing.io's code validation engine verifies that R45.851 is included in the encounter's diagnosis list. It cross-references the narrative for SI-related language (frequency, plan, intent, means, protective factors) and flags any element missing from the Columbia Suicide Severity Rating Scale (C-SSRS) documentation framework. If the clinician has documented SI but R45.851 is absent from the code set, sign-off is blocked with a specific remediation prompt.
ICD-10 Code | Required Documentation Elements | Common Under-Documentation Error | Scribing.io Enforcement |
|---|---|---|---|
F33.2 | Recurrence history, severity indicators (PHQ-9, functional impairment), psychotic feature status | Documenting "recurrent MDD" without severity → defaults to F33.9 | Severity and psychotic status confirmation prompt before code stamp |
R45.851 | SI presence, frequency, plan, intent, means access, protective factors | SI discussed in narrative but R45.851 omitted from diagnosis list | NLP scan of narrative → code presence validation → sign-off block if missing |
Goal-Directed Documentation Architecture: The PlanVersionID–GoalID–ObjectiveID Triple
The core technical innovation Scribing.io brings to Credible environments is the durable triple: a three-part identifier that permanently links each Progress Note to a specific plan version, goal, and objective. This section details the architecture.
Why a Triple, Not a Single ID
A single ObjectiveID is insufficient because Credible recycles the conceptual position (O1.2) across versions while assigning new database IDs. Referencing only the ObjectiveID creates ambiguity during audits spanning plan revisions. The triple disambiguates completely:
PlanVersionID — Identifies the exact version of the ITP that was active on the date of service. This anchors the note to a temporal snapshot of the treatment plan, allowing auditors to reconstruct the clinical context that governed documentation
GoalID — Identifies the specific Goal within that PlanVersion. Because Goals can be added, removed, or reworded at revision, the GoalID confirms which treatment target the encounter addressed
ObjectiveID — Identifies the specific measurable Objective within that Goal. This is the element auditors match against Progress Note content to verify goal-directed documentation
Where the Triple Lives
Scribing.io writes the triple into two locations simultaneously:
Structured metadata fields in Credible's Progress Note record. These fields are queryable via the Credible API and appear in standard data exports, enabling automated audit packet generation
Narrative body of the Progress Note. The triple appears as a human-readable reference (e.g., "Per ITP Version PV-2026-0312, Goal 1, Objective O1.2 [ID 5301]") embedded in the Assessment or Plan section. This ensures that a manual auditor reading the note—without access to structured metadata—can verify goal linkage
Cross-Version Resolution Logic
When a plan revision occurs, Scribing.io executes a resolution sequence:
Detect: Compare the PlanVersionID from the patient's last encounter against the current active PlanVersionID. If they differ, a revision has occurred
Map: For each ObjectiveID referenced in the prior encounter, identify the successor ObjectiveID in the new PlanVersion using a weighted match of: clinical description text, hierarchical position (Goal index + Objective index), measurement criteria, and target values
Confirm: Present the clinician with the mapped successor and request verbal confirmation. The clinician may override if the mapping is incorrect (e.g., if a prior Objective was split into two new Objectives)
Stamp: Write the new triple into the current encounter's note. The prior encounter's triple is unchanged—it correctly references the PlanVersion that was active on its date of service
This architecture ensures that no note—past or present—carries a broken goal reference, regardless of how many plan revisions occur during the episode of care.
90-Day Plan Review Guardrails and 6-Year Audit Trail Compliance
The 90-Day Review Mandate
Most state Medicaid programs require periodic review of the ITP at defined intervals. North Carolina mandates review at least every 90 days. New York OMIG policy specifies intervals by population and service type, ranging from 90 to 180 days. Failure to document a timely review renders every encounter billed after the lapse potentially subject to recoupment—regardless of whether the clinical content of the notes is otherwise adequate. This is an independent denial vector from the goal-linkage issue.
Scribing.io tracks plan review dates at the PlanVersion level. The guardrail logic operates as follows:
Days Since Last Review | Scribing.io Behavior |
|---|---|
0–75 days | Normal operation. Triple stamp proceeds without alerts |
76–85 days | Amber alert: Clinician and supervisor receive notification that plan review is due within 15 days. Scheduling integration (where available) flags the next available review slot |
86–90 days | Red alert: Clinician receives an in-session warning that the review window closes imminently. Note can be signed but includes a review-pending flag in metadata |
91+ days | Sign-off block: The Progress Note cannot be finalized until either (a) a plan review is completed and a new PlanVersionID is generated, or (b) a supervisor override is applied with documented clinical justification. Override events are logged in the audit trail |
6-Year Audit Trail for NY OMIG and Multi-State Compliance
New York's Office of the Medicaid Inspector General (OMIG) enforces a 6-year lookback period for post-payment audits. North Carolina's lookback is typically 3 years but can extend under fraud investigations. Scribing.io maintains a complete, immutable audit trail for each encounter that includes:
The PlanVersionID–GoalID–ObjectiveID triple active at the time of documentation
The timestamp of triple assignment
Any ID rollover events (retired ID → successor ID mapping with confidence score and clinician confirmation)
Plan review window status at the time of sign-off
Any supervisor override events with justification text
ICD-10 code validation results (codes proposed, codes confirmed, codes flagged)
CPT element validation results for 90839/90840 and other high-acuity codes
This trail is stored independently of Credible's database, ensuring that if Credible's native audit logging is insufficient for a state inquiry, Scribing.io can produce a complete reconstruction of documentation decisions for any encounter within the lookback window. The audit packet export generates a single PDF or structured data file per encounter—or per audit request spanning multiple encounters—with one click.
Workflow Comparison: Generic AI Scribes vs. Scribing.io in Credible High-Acuity Environments
The following comparison isolates the capabilities that determine audit survival in Credible behavioral health workflows. Features common to all AI scribes (ambient capture, transcription, basic SOAP formatting) are excluded as non-differentiating.
Capability | Generic AI Scribes (Freed, Nuance DAX, DeepScribe, Suki, Abridge) | Scribing.io (Credible Integration) |
|---|---|---|
Credible Treatment Plan awareness | None. No integration with Credible's Plan data model | Real-time read of active PlanVersion, Goals, and Objectives at session start |
PlanVersionID tracking | Not applicable | Every note stamped with the active PlanVersionID |
ObjectiveID rollover detection | Not applicable | Automatic detection of retired IDs with cross-version successor mapping |
Goal-directed language prompting | Generic "assessment" prompts, no plan-specific context | Objective-specific prompts with baseline, target, and measurement tool references |
PlanVersionID–GoalID–ObjectiveID triple | Not generated | Embedded in structured metadata and narrative body of every note |
90-day plan review enforcement | Not tracked | Tiered alerts at 76, 86, and 91+ days; sign-off block at lapse |
CPT 90839/90840 element validation | Basic time capture only | Crisis precipitant, risk assessment, modality, time per unit, and continued-crisis justification validated before sign-off |
ICD-10 specificity enforcement (F33.2, R45.851) | Code suggestion from narrative; no sign-off block for under-specified codes | Severity and psychotic feature confirmation for MDD; R45.851 presence validation when SI is documented; sign-off block for mismatches |
DHHS audit packet export | Not available | One-click export: note + plan version + triple + validation log per encounter |
6-year immutable audit trail | Dependent on EHR's native logging | Independent, immutable log of all documentation decisions, overrides, and validation events |
Implementation Pathway: From Credible Configuration to First Compliant Note
Deploying Scribing.io in a Credible environment follows a structured pathway designed to minimize disruption and deliver audit-defensible notes within two weeks of initiation.
Phase 1: Credible Environment Assessment (Days 1–3)
Plan structure audit: Scribing.io's implementation team reviews the organization's Treatment Plan templates, Goal/Objective naming conventions, and revision frequency. Organizations with more than 3 active plan templates or high revision rates receive customized rollover mapping rules
API access verification: Confirm Credible API credentials, endpoint availability, and data permissions. Scribing.io requires read access to PlanVersion, Goal, Objective, and Intervention records, plus write access to Progress Note structured fields
State mandate mapping: Identify the organization's state(s) of operation and applicable plan review intervals, goal-directed documentation requirements, and audit lookback periods. Multi-state organizations receive state-specific guardrail configurations
Phase 2: Configuration and Validation (Days 4–8)
Triple stamp field mapping: Map the PlanVersionID, GoalID, and ObjectiveID to specific Credible Progress Note fields. Where custom fields are required, Scribing.io's team configures them within Credible's admin interface
Rollover logic calibration: Using historical plan revision data, calibrate the cross-version mapping algorithm. Test against 50+ known revision events to validate successor ID accuracy above 95%
CPT validation rule configuration: Configure the 90839/90840 element checklist, time documentation rules, and any organization-specific payer requirements
ICD-10 specificity rules: Configure code-pair validation (e.g., F33.2 + R45.851 when SI is documented), severity confirmation prompts, and sign-off blocks for under-specified codes
Phase 3: Pilot Deployment (Days 9–12)
Pilot cohort: 3–5 clinicians documenting high-acuity encounters (crisis psychotherapy, SI-related sessions) deploy Scribing.io in live clinical workflows
Parallel documentation: During the pilot, notes are generated by both the legacy workflow and Scribing.io. A clinical quality reviewer compares output, verifying that every Scribing.io note contains a valid triple, correct ICD-10 codes, and complete CPT element documentation
Feedback loop: Clinician feedback on prompt timing, rollover alert clarity, and sign-off block usability is incorporated into configuration refinements
Phase 4: Full Deployment and Monitoring (Day 13+)
Organization-wide rollout: All clinicians documenting in Credible transition to Scribing.io-assisted workflows
Ongoing compliance dashboard: Scribing.io surfaces real-time metrics: percentage of notes with valid triples, plan review compliance rate, average days remaining in review window, ICD-10 specificity rate, and CPT element completion rate
Audit response readiness: The one-click audit packet export is tested with a mock DHHS request, ensuring the organization can respond to a post-payment review within the state-mandated timeframe (typically 30 days)
Organizations operating in New York under OMIG oversight or in North Carolina under DHHS Medicaid audits have the most immediate ROI from this deployment. The $12,320 recoupment scenario described in this playbook represents a single clinician over a two-week window. Multiply by headcount, by months of undiscovered linkage breaks, and by the compounding effect of lapsed plan reviews, and the annual revenue exposure for a 50-clinician organization routinely exceeds $500,000.
See our Credible-native Goal Linker in action: real-time PlanVersionID mapping, 90-day review guardrails, and one-click OMIG/NCDHHS audit packet export—book a 20-minute demo today.
