Scribe-X MMF V5

This is the architecture of what Scribe-X says and why. It defines the audience, the problem, the position, the solutions, the vocabulary, and the proof. It doesn't define voice, tone, or format ... those are applied downstream, in the brain (the AI Brand Twin), and may vary by audience and by market segment without any change here.

Two kinds of text in this document

• Verbatim artifacts are text lifted into an asset word for word: position statements, locked forms, the pitch, glossary entries, sanctioned phrases, FAQ answers. These meet publication standard. Nothing downstream rewrites them.
• Explanatory scaffolding is the reasoning around those artifacts. Internal register. It records why a decision holds so it doesn't have to be relitigated. Don't edit scaffolding as though it were copy.

Locked-form hierarchy

Every claim has one canonical form, the precise version we would defend, which defines what the short form means. Short forms derive from the canonical. A precise or regulatory form exists where finance or legal specificity is required. Nothing enters circulation that isn't derived from a canonical. Variants at equal authority are prohibited: sales reaches for the strongest phrasing available, and the organization gets held to a commitment it never chose.

How this framework is used

Marketing, sales, product, and partner communication all draw from this document. Where an asset needs language this document doesn't contain, the language is added here first, then used.

Purpose

One source of truth for what Scribe-X sells, to whom, against what alternatives, and on what evidence.

---

Primary ICP

Enterprise-level FQHCs and their lookalikes ... larger, multi-site community health organizations, not small private practices.

• Why this vertical: roughly 1,600 FQHCs plus ~150 lookalikes (orgs without the designation, paid the same way). The barrier to entry is high, which is exactly why it becomes a moat once we're in. "If we had 150 of them, we'd be a $100M company."
• Why now: budgets are tighter every year, and these orgs are forced to think differently or they won't survive ... so they're finally open to change instead of riding the old playbook.
• Who we deprioritize (on purpose): health systems (longer cycles, heavier politics, real risk of stalled execution) and small practices (can't carry the model). Large private outpatient groups have the provider volume and the operational pain to carry the model ... a real secondary pathway, but enterprise-level FQHCs and their lookalikes are where we lead.

The buying committee (six roles, two jobs)

We sell into a buying committee, not a single buyer. Six roles matter, and they split into two jobs. The clinical leaders (CMO and CMIO) are the doors in ... they feel the pain first and carry us into the room. The economic buyers (CEO, CFO, and the COO / Chief Quality Officer) control whether dollars get spent and on what, with the CIO clearing risk and governance. We don't rank them ... a real FQHC deal needs the clinical champion AND the economic owners aligned. The three clinical doors below; all six in full in §6.

The cast around the buyer

---

---

Our Identity ... why Scribe-X exists

We exist so patients get the provider's full attention, and the care that follows the visit doesn't fall through the cracks. That's the point ... caring for patients is the action, and better health is the result. Everything else, the notes, the codes, the orders, the inbox, is the work around the visit that too often takes the provider away from the patient.

We come at that as healthcare people building healthcare tools: thirteen years of clinical documentation experience sits behind the platform, in a market most entrants reached from general technology. That's why the automation understands the work, and why our people can stand behind what it produces.

This is our mission layer, not our sales trigger. A buyer rarely arrives searching for our mission ... they arrive with a pain (a provider about to quit, revenue leaking, a stalled rollout). The hook is always the pain. The tie-back is always the patient: more patients seen, better care delivered, a healthier care team, because the providers are freed to do the work only they can do.

Foundational Belief ... "Providers should spend their attention on patients."

"Providers" is shorthand for the clinicians a practice hinges on ... MDs, DOs, NPs, PAs.

Providers should spend their attention on patients. Everything else about the visit is work that can be carried for them.

We believe what these clinicians want is, in good faith, what's best for the patient ... because caring for patients is why they went into medicine. Giving a provider their attention back isn't a perk for the provider. It's the patient getting cared for. Same thing.

---

Position 1 · Composition

Documentation takes two things. Automation that drafts fast and adapts to how each provider works, and trained people who finish the job. Scribe-X is built by people who have done this work for thirteen years, which is why our automation understands the work and why our people can stand behind what it produces.

Scaffolding. This replaces V4's deficiency argument ("AI alone isn't enough"). The critique lands on the operating model, never on the technology: an AI-only tool returns the last mile to the highest-paid person in the building. That's an organizational cost argument, and it holds regardless of how good automation gets. Supporting research stays internal.

Position 2 · Completion

A draft is not the job. The note has to reach the chart, the orders have to be queued, the codes have to be right, the patient has to leave with instructions. Scribe-X completes the work and hands it over ready to sign.

Position 3 · Independent accountability

Somebody should check the work before it reaches the chart, and it should not be the person who is about to sign it.

Canonical: Every note passes a trained Remote Healthcare Assistant before it reaches your chart.
Short form: A second set of eyes on every note.

Scaffolding. Applies to Assist and Live. Depth of checking is scoped, never claimed universally. All edits are intended to occur in the tool prior to EHR import, so the check sits upstream of the write by design rather than by circumstance.

Position 4 · The whole visit

Chart prep, the note, coding, orders, and what happens after. Automating one of those and returning the rest is not relief. Scribe-X works across the visit, and we're specific about what's available now and what's coming.

Position 5 · Value realization

We can show which mechanism produces which result, on what timeline, and what has to be true for it to hold. Most of this market cannot, because most of this market reports one bundled number.

---

Three states, not two. The OLD way was fully manual ... human-only, before AI touched the visit at all. Nobody defends it anymore. The CURRENT way is AI-only: a clinic puts an ambient tool on the encounter and gets a drafted note, fast. That first generation proved drafting works. What it didn't solve is everything around the draft ... chart prep before, the orders and codes during, the referrals, the inbox, and the follow-ups after ... and buyers now have enough experience to notice. The market has learned what a drafted note is worth, and what it leaves behind.

The NEW way completes the whole process around the visit, before, during, and after, with automation carrying the volume and a trained Remote Healthcare Assistant finishing the work and closing the loops. The clinic sets how much human, per provider, with the toggle bar. That is what actually frees the provider, because the work around them is genuinely handled, not just the note auto-drafted.

The shift in one line: from a drafted note with everything around it left in place, to the whole process around the visit completed ... automation for the volume, human intelligence for the judgment, context, and follow-through.

Current way · AI only	What matters most	New way · AI + Human Intelligence
Note	Scope	Journey
None	Judgment	Human
Leaks	Revenue	Captured
Dropped	Follow-ups	Closed
Generic	Fit	Tailored
Stalls	Adoption	Sticks
Added	Risk	Reduced
The chart	Time	Patients

Why the current way is breaking now

Two forces are ending it. The clinics that adopted ambient AI have learned exactly what a drafted note covers and what still lands on the provider. And the accountability for an AI note is settling on the provider who signed it, the same provider the practice is fighting to keep ... states are already writing independent review into law. The draft was the easy half. The market is now buying the finish.

---

A practice where the provider's day belongs to the patient again.

Picture a day in a practice that got this right.

Before the visit, the chart is already prepped. The recent labs, the relevant imaging, the gaps in care are pulled up and waiting, so the provider walks in knowing the patient instead of scrambling to catch up.

During the visit, the provider is with the patient. Eyes up, not buried in a keyboard. The note, the orders, the coding, the endless EHR clicks are handled around them, not by them.

After the visit, the loop actually closes. The note is finished before the provider leaves the room. The referral goes out with what the insurer needs to approve it. The abnormal lab gets its callback. The patient doesn't bounce back in three months because something got missed.

When the day runs like that, everyone is better off at once:

• the provider practices at the top of their license instead of being a paper jockey, leaves the night charting behind, and stays in medicine;
• the care team isn't constantly covering for what didn't get done, and can actually support the visit;
• the practice sees more patients, keeps its people, and stops leaking revenue to the codes that used to get missed;
• the patient gets a clinician who is present, and care that doesn't get missed.

That is the whole point of the Clinical Intelligence Platform. Faster notes are the smallest part of it. The promised land is the whole patient journey, handled end to end ... so the practice runs the way the provider always wanted, and the patient feels the difference.

---

We sell into a buying committee, not a single buyer. Six roles matter, and they split into two jobs. The clinical leaders (CMO and CMIO) are the doors in ... they feel the pain first and carry us into the room. The economic buyers (CEO, CFO, and the COO / Chief Quality Officer) control whether dollars get spent and on what, with the CIO clearing risk and governance. We don't rank them ... we build the case for every one, because a real FQHC deal needs the clinical champion AND the economic owners aligned.

The providers underneath the buyer (who they're buying for → the solutions, §10-§11)

The buyer doesn't set one level for everyone ... each provider is set to the solution they need on the toggle bar: how much human intelligence their work needs, and how much risk the clinic wants handled. Three kinds:

• Solo (left of the bar · self-directed): the cost-conscious or tech-comfortable provider who's fine owning more of the workflow. Automation drafts from the encounter and their team reviews and finalizes; they accept the most risk, because they figure they and their staff can catch whatever slips. (Solo is pre-release ... available now to early-adopter practices at preferential terms while integrations are built.)
• Assist (middle of the bar · the flagship): the provider who wants the work finished, with a trained Remote Healthcare Assistant carrying the note, the codes, and the orders to ready-to-sign ... usually younger, comfortable with technology, the ones who'll be running these clinics in a few years. The biggest untapped group, and the most likely to move. Available now.
• Live (right of the bar · real-time human): two faces ... the high producer you don't dare slow down, and the senior clinician who just wants to see patients and never touch the computer. A trained Remote Medical Scribe documents the encounter in real time. Both want the most human, both have the least tolerance for a critical miss, and both pay for the assurance. Available now.

---

---

Nearly every practice saying these things already has an AI scribe running. This is the pain that's left after the AI did its narrow part.

The injustice

The grievance that turns these problems into a fight worth having.

• You should never have to choose between being present with your patient and finishing your notes.
• You should never have to lose a great provider because the charting beat them.
• You should never have to settle for "good enough" and call it a strategy.
• You should never have to leave revenue you earned on the table because a code got missed in the rush.
• You should never have to wonder whether a dropped follow-up put a patient at risk.
• You should never have to tell your best people to just absorb the pain because the budget said so.
• You should never have to defend a technology investment you can't actually measure.
• You should never have to choose between growing the organization and protecting the people already in it.

---

Standing still feels safe. It isn't. Leaving the work around the visit half-handled doesn't hold steady ... the cost compounds, quarter after quarter, across the provider, the practice, and the patient. And it's countable. Here's what the industry data says each piece costs.

• You lose your best people, and replacing them is expensive. Burnout takes the most conscientious providers first. They already spend close to two hours on the record for every hour with a patient, and the providers doing the most after-hours charting are about twice as likely to burn out. Burnout roughly triples the odds a provider is looking to leave, and the AMA puts the cost of replacing one physician at $500,000 to $1 million once you count recruiting, lost billings, and the ramp. A family-medicine seat now takes about five months to fill, and every month it sits empty is production you don't get back.
• Your providers can leave for a practice that fixed it. The burned-out provider has options. As more organizations pair AI with human intelligence and hand the day back, the practice still running its providers into the ground is the one they leave ... and the patients who counted on that provider lose their access along with them.
• Revenue keeps leaking, mostly through the codes. Every under-coded or missed visit is reimbursement you earned and didn't collect. A federal audit found that miscoded and under-documented Evaluation and Management visits drove $6.7 billion in improper Medicare payments in a single year, with about 42% of those claims coded wrong. And the prevention and coordination work your providers already deliver often never gets billed ... modeling in the Annals of Internal Medicine put that at around $40,000 a provider a year left on the table. It never shows up as a crisis. It comes off the bottom line every month.
• Patients pay for the dropped loops. A lab with no callback, a referral that never went out, a follow-up that slipped ... these become repeat visits, worse outcomes, and real risk to patient safety.
• Patients wait longer for less. As providers fall behind and capacity tightens, appointment slots shrink and wait times grow ... patients get less access to their provider, not more.
• The money you already spent stays wasted. The AI pilot that didn't stick was paid for. Leave it at "good enough" and you keep paying for a tool most providers don't use, while the problem it was meant to fix sits frozen.
• The records become a liability. Notes that AI alone got thin or wrong are a compliance exposure ... inaccurate documentation the clinic is accountable for, in a climate where that accountability is landing harder on the provider who used the AI.
• The margin for error is already gone. Community health centers ran an aggregate operating margin of about 1.6% in 2023, and nearly half operated at a loss. At that thinness, lost visit revenue or added labor cost doesn't dent the budget ... it decides whether the center ends the year in the black. Budgets get tighter every year, and the liability keeps moving onto the provider who used the AI. Doing nothing isn't holding position ... it's falling behind a problem that's getting harder.

Put a number on it, for the finance conversation

The champion can turn this into a figure the CFO can't wave away, using the practice's own numbers:

• The providers you're at real risk of losing, times $500,000 to $1 million to replace each one.
• The visits a day your providers can't get to, times your per-visit rate, times the days you're open. For scale, the Medicare FQHC base rate alone is about $190 a visit, and most FQHC visits are reimbursed below what the care costs, so lost throughput hurts twice.
• The prevention and coordination work already being delivered and never billed, around $40,000 a provider a year, times your providers.

Add those up, and you have what the cheapest tool is quietly costing the practice. That's the number to set the price against.

The question was never whether to change. It's whether to change while it's still cheap to fix, or after the cost has compounded. And this isn't only getting more expensive. The accountability for AI notes is landing now, on the providers you can least afford to lose, in the states that already passed the laws.

The stakes, by role

The cost of doing nothing doesn't land evenly. Each role carries a different piece of it, and it compounds differently for each.

• CMO. Every quarter this stays half-handled, you lose more of the providers you can't replace, and the ones who stay carry a heavier load. The burnout you're tracking today becomes the resignation letter next year.
• CMIO. The tools already in place keep adding review work instead of removing it, and adoption erodes further with every rollout that doesn't stick. The governance question gets harder to answer, not easier.
• CIO. Every month of ungoverned AI use is another month of undocumented risk sitting on your books. When the audit or the breach comes, "we were still figuring it out" is not a defensible answer.
• CEO. Standing still doesn't hold your position, it cedes it. The organizations that move now set the standard the rest of the market gets measured against, and yours falls further behind the longer the decision gets deferred.
• CFO. The revenue that leaks this quarter doesn't come back next quarter, it compounds. Every month without a fix is a month the budget absorbs a cost nobody's put a number on yet.
• COO / Chief Quality Officer. Quality measures don't fail all at once, they slip a little every cycle until the org is chasing a gap it can't explain. Coverage that depends on no one calling in sick isn't a plan, it's a countdown.
• Provider. Every night this stays unfixed is a night that comes home with you. The providers who leave first are usually the ones you could least afford to lose.
• Patient. Every dropped follow-up is a patient whose outcome depends on nobody noticing what fell through. The cost of doing nothing doesn't show up on a balance sheet ... it shows up in someone's chart.

---

A customer chooses one solution for each provider. Layers of capability attach on top. The solutions differ by who performs the work and which layers are included ... and the toggle bar is how a clinic sets it, provider by provider.

Set per provider

Support is set per provider, not per organization. The three settings are three named solutions ... Solo, Assist, and Live ... detailed in §11. They aren't three different products; they're three points on one toggle bar, on one platform, so solutions may be mixed across a team and changed as needs change, in one account. A practice can run its highest-volume providers on Live and the rest on Assist, all under one agreement, and no provider switches tools to move.

The mix ... any number of providers, at any setting

A buyer never has to pick a lane. The organization distributes its whole roster across the bar ... Solo for some, Assist for most, Live for the few who need it ... and changes any provider's setting as needs change. Jason's framing, from the July 16 working session: a clinic could pick Solo for 10, Assist for 20, and Live for 5. That's the model. Meet every provider where they are, and the whole roster lives on one platform ... which is what turns Scribe-X from a one-off solution vendor into the platform that penetrates the whole account.

One discipline rule rides with the mix, always: results attach to each provider's solution, never averaged across the platform. A clinic evaluating outcomes sees what Assist delivered for the providers on Assist and what Live delivered for the providers on Live ... no blended claims.

The canonical mix visual. On the homepage it appears twice: whispered in the hero (small provider facepiles on each toggle-bar card) and taught in the solutions section (the interactive "Build your mix" board, where a buyer toggles provider counts up and down per solution and watches the roster take shape). Every provider figure carries the medical cross ... these are clinicians, not seats.

What this is worth at organizational scale

One vendor for all solutions. Every provider at the level of support that fits them, moved when that changes, in one account with one relationship. This is the land-and-expand argument, and it's an organizational claim, not a provider claim.

Scaffolding, honest limit. Per-provider choice is not unique; scribe incumbents offer support-level choice too. The durable claims are accountability, completion, and value realization (ranked in §12). Open item, asset-level not MMF-level: visual treatment of layer differences ... the claims above hold under either treatment.

---

That's the mechanism. Next, the three solutions it produces, in detail.

---

Three solutions on one platform. Each provider is set to a solution; layers of capability attach on top; the solutions differ by who performs the work and which layers are included. And the counts are the clinic's to set: any number of providers at each solution, mixed freely under one agreement ... 2 on Solo, 6 on Assist, 2 on Live, or Jason's working example, 10-20-5 ... and moved between solutions as needs change, with no migration (see The Mix, §10).

The intelligence layers

• Pre-Visit Intelligence is a SKU. Built into Live, optional add-on to Assist and Solo. Chart prep is a feature inside this SKU, not the name of it. The provider walks in prepared: chart prep, prior visit summary, problem-list and medication review, and open orders and labs surfaced before the visit.
• Encounter Intelligence is in every solution. The note, the after-visit summary, mobile capture, provider style and specialty customization, EHR workflow fit, and multilingual support.
• Revenue Intelligence and Quality Intelligence attach by solution and by agreement. Revenue: coding completeness support, documentation specificity prompts, HCC visibility, level-of-service support, charge capture visibility. Quality: care gap visibility, preventive reminders, problem and medication list accuracy, UDS/HEDIS measure visibility. Each marked honestly as today vs coming in the sales conversation.
• Layers attach all-or-nothing. Solutions differ by who performs the work and which layers are included ... a clinic buys a configuration, not a menu of features.
• Not operational: Inbox Management, Care Coordination, Operations. Side layers, agreement-scoped future scope only, never presented as current capability.

The universal floor

Every account gets a dashboard, a named contact, standard reporting, and a defined support standard. That's not a tier, and it's not an upsell.

Enterprise

Enterprise is a commitment, not a package. Service-level commitments, outcome commitments, the layers you need switched on, and terms written into your agreement.

---

The buyer isn't choosing between Scribe-X and nothing. They're weighing a short list of real options. Name them honestly, and the gap shows itself.

What a clinic is choosing among

• An AI-only ambient tool. The point solutions draft the note well ... and return everything around the draft to the practice. One more vendor to integrate.
• Their EHR's bundled ambient feature. Convenient, already in the workflow, and often looks free. Addressed head-on below.
• A traditional scribe service. Human hands on the documentation. With turnover, no automation carrying the volume ... and offshore, the patient's record leaves the country, a compliance exposure some states already restrict.
• Doing nothing. It costs nothing today, and the cost compounds quarter after quarter (see §9).

Four claims, in order of durability

• 1. Independent accountability. Somebody other than the signer checks the work before it reaches the chart. Competing AI-only vendors' own technical disclosures name the treating clinician's self-review as their safeguard. This doesn't erode as automation improves.
• 2. Completion across the visit. The work arrives finished, not returned for handling ... the note in the chart, the orders queued, the codes reviewed, ready to sign.
• 3. One vendor for all solutions. Every provider at the level that fits, changed when that changes, in one account with one relationship.
• 4. Value realization. Mechanism, timeline, and condition for every claim, while most of the market reports one bundled number (§13).

On the EHR head-on

A bundled draft is a reasonable place to start. It doesn't put the note in the chart with the orders queued and the codes reviewed, and it doesn't put anyone between the draft and the signature.

---

Features versus outcomes

A feature is something the product performs. An outcome is something the customer realizes downstream, gated by their own decisions. An outcome is never presented as a product guarantee.

Realization tiers

Value arrives on different clocks and is never summed as though identical.

• Tier 0. Hard cost avoided immediately.
• Tier 1. Cash on the normal billing cycle.
• Tier 2. Cash contingent on a quality or performance measure.
• Tier 3. Cash contingent on annual reconciliation or risk settlement.
• Tier X. Time value and burden relief. Real, and it doesn't become cash on its own.

Utilization gates everything. An unused tool drafts no note and frees no time. Every figure assumes use.

Two mandatory rules

• Outcome claims attach to a solution, never to the platform.
• Revenue claims segment by payer type. A coding-level improvement is real revenue in a fee-for-service group and is not in a PPS-reimbursed encounter.

The hook and the close

Time and proficiency lead the hook. Operational proof leads the close. Any asset carrying a time or burnout claim also carries an operational credibility signal, because procurement in this market turns on coding accuracy and denial exposure rather than satisfaction.

Proficiency. Proficiency is a clinic and its providers working at full scope. For a provider, that means documenting at the level the work merits, keeping pace without carrying work home, practicing at the top of their license, and having the capacity to see more patients. For the organization, it means teams running efficiently against operating expense, documentation complete enough to be paid properly for work already being done, and the capacity to meet care demand, expand patient volume, and stay profitable while doing it. Capacity is the claim on both sides. Realized volume and realized margin are gated outcomes and are never promised.

Operational anchors

Two distinct metrics, never merged and never used interchangeably:

• Time to close. Elapsed time from encounter to closed chart. Expressed as a percentage reduction.
• Same-day chart closure. Share of charts closed on the day of the visit. Expressed as a rate.

The claim class leads for all three solutions. The feature-level claim carrying the hook: Every note is ready to sign the same day. True of Live in real time, Assist within the hour, Solo in minutes. It describes what we do rather than what the customer realizes, so it needs no gate language. Figures scope per solution and are cited with their basis; figures live in the outputs, not in this document. Solo limit: Solo may claim readiness. It may not claim closure, because review and finalization happen on the customer's cadence.

Patient experience

Qualitative only until quantitative data exists. The sanctioned line: Providers spend the visit with the patient rather than the keyboard. No figure, no comparative claim. This is the one claim class where we're behind the category on evidence.

---

A buyer who understands the offer still has real questions. Here are the ones that come up, and how we answer them straight.

• "Isn't this just another AI scribe?" No. Automation carries the volume; the product is the trained people who finish the work on top of it, across the whole journey. The note is the smallest part of it. If a draft is all a clinic needs, the market already sells that ... and so do we, as Solo, the self-directed entry solution.
• "We already have an ambient tool." Then your providers have a draft. Ask them what happens between the draft and the signed chart, and who does it.
• "Our EHR includes this for free." A bundled draft is a reasonable place to start. It doesn't put the note in the chart with the orders queued and the codes reviewed, and it doesn't put anyone between the draft and your signature.
• "Why pay for a human when automation is improving?" Because the person checking the work should not be the person signing it, and because the work still has to be finished and filed. Neither changes when the drafting gets better.
• "We tried a tool before and it didn't stick. Why is this different?" Because what stalled was a tool that returned the work to your providers to figure out. Here a trained Remote Healthcare Assistant carries the work, so there's no rollout for a busy provider to get right.
• "Is this going to replace our staff?" No. It returns time to the people you already employ.
• "It costs more than the tool we're comparing it to." On the sticker, it does. Set against what standing still costs ... the providers who burn out and leave, the revenue that leaks, the follow-ups that get dropped ... it's the cheaper choice (see §9). And the toggle bar lets a clinic take only the level it needs, per provider, so it never pays for more human than it wants.
• "Will our providers actually use it?" Adoption is our job, not theirs. Because a trained Remote Healthcare Assistant carries the work, there's nothing for a busy provider to use wrong or quietly abandon. That's the difference between a tool a clinic has to adopt and a service that simply runs.
• "Is our patient data safe?" Our trained Remote Healthcare Assistants are US-based and the record stays onshore. That's deliberate. In a climate where offshore handling is getting restricted and the accountability for an AI note is settling on the provider who signed it, it reduces the risk a clinic carries instead of adding to it.

---

A buyer who's been burned by a stalled rollout needs the path to feel safe, not heavy. It's three steps, and we carry the load on every one.

Why the plan removes the risk

The failure a clinic fears ... another tool that's switched on and quietly dies ... can't play out the same way here. A trained Remote Healthcare Assistant carries adoption, so there's nothing for a busy provider to get right. The pilot proves it in a real clinic before anyone scales. And the clinic grows only as fast as it works, one provider and one toggle setting at a time. The decision is reversible at every step, which is exactly why it's safe to start.

---

That closes Phase 3 (Solution & Edge), with §13 Proof parked for data. Now Phase 4: the rebellion and the words to carry it. (The full Language Library now lives in the Appendix at the back.)

---

A rebellion line does one of two jobs. It either names the promised land (the new world, the way the game is now played) or it's a battle cry (verb-first, the call to arms). A brand can run both ... the promised land where it lives, the battle cry where it rallies.

The candidate bank ... pruned by the V5 rules, winner to be picked with Warren/Oliver

• Clinical Intelligence  #ClinicalIntelligence
  The world and the product share a name (the Clinical Intelligence Platform). The most ownable, and it passes the construction rule.
• Co-intelligent Healthcare  #CoIntelligentHealthcare
  The category and thought-leadership banner for the movement ... blogs, keynotes, the POV ... not the homepage tagline.
• Free Up Your Providers.  #FreeUpYourProviders
  Verb-first battle cry; the relief, made personal to the practice and its leaders. Passes the construction rule.
• Retired candidates: "End Pajama Time" (retired vocabulary), "Practice Medicine, Not Paperwork" and "AI + Expertise" (fail the V5 construction and vocabulary rules). Kept here so nobody re-proposes them cold.

---

That's the rebellion. Now the story made sayable.

---

The elevator pitch

Thirty seconds: Most AI scribes stop at the note, which leaves everything else around the visit sitting on your providers ... the chart prep, the coding, the orders, the referrals, the inbox, the follow-ups. That's why they're still charting at 10pm, why your best people burn out, why earned revenue leaks through missed codes, and why dropped follow-ups start putting patients at risk.

Here's what we do, with you: we complete the whole patient journey, before and after the visit ... the whole process, and the note is the smallest part of it. Automation carries the volume, a trained, US-based Remote Healthcare Assistant finishes the work, and you decide how much human each provider needs. Your providers get their day back, and the risk you carry goes down instead of up.

How are you using AI in your practice?

Ten seconds (lead with the question): How are you using AI in your practice? Most stop at the note, which leaves your providers doing the chart prep, the coding, and the follow-ups ... and it's burning them out. We finish the whole patient journey with you: automation for the volume, a trained Remote Healthcare Assistant for the judgment, customized around each provider.

Five seconds (lead with the question): How are you using AI in your practice today? Most AI scribes stop at the note ... we finish the whole patient journey, automation plus a trained Remote Healthcare Assistant.

Opening hooks for outreach

Most of these are built to draw a "No," not a "Yes." Pushing someone toward "Yes" puts them on guard; a "No" feels safe and in their control, and the honest "No" makes them name the situation they can't keep tolerating. That admission is the starting point for action. Then an open "what / how" question widens it, getting them to say the stakes out loud, in their own words.

• Night charting: "Have your providers stopped finishing notes at night?" No ... the 10pm charting is still here.
• The whole journey: "Did your AI scribe take the chart prep, the coding, the orders, and the follow-ups off their plate too?" No ... it only handled the note.
• Retention: "Are you confident you won't lose another good provider to burnout this year?" No ... and that's the one loss they can't afford.
• Revenue: "Are you certain you're capturing every code you've earned?" No ... reimbursement is leaking every month.
• Productivity: "Are your providers able to see as many patients as you'd like?" No ... they're struggling to keep up with what they have.
• Liability (for the CIO): "Have you settled who's accountable when the AI gets a note wrong?" No ... and the liability is shifting onto the provider who used it.
• The cost of standing still (the open follow-up): "What are the ripple effects, for you and for the practice, if this stays the way it is?" An open question that makes them name the stakes themselves ... burnout, turnover, leaked revenue, dropped follow-ups (ties to §9).

Calls to action

Low-friction and value-first. Lead with the scorecard or the free trial, not a demo. CTA rule: every asset works backward from one specific next step, and no asset ends without one.

• See your gaps: "Run the Practice Health Scorecard ... your gaps and what they cost, in minutes." (the front door)
• Feel the win: "Start a free trial ... a few providers, in your real workflow. You tell us what changed."
• See it in action: "Let's get you into a pilot so you can see the whole journey in action ... a few providers, clear KPIs."
• Map the journey: "Book a call and we'll map your patient journey together." (for larger, multi-site organizations)

---

That's the language made sayable. Now the category we plant a flag in, and how we get found.

---

The category we lead

"AI scribe" is a crowded category, and a losing one to fight in. It's a race to the cheapest, the EHRs are bundling it for free, and it stops at the note. Competing there means being compared on price for a commodity. That's why we don't fight there. We define and lead a bigger category.

That category is the Clinical Intelligence Platform (CIP). It's bigger than scribing: the whole patient journey, automation for the volume, a trained Remote Healthcare Assistant for the judgment, set on a toggle bar. The old category, the AI scribe, becomes the entry point we offer (Solo, early adopter) ... the Clinical Intelligence Platform is the category we want to be known for and measured by.

SEO & AEO terms

Scribe-X already has real search equity in the medical-scribe family ... the site ranks for terms like "medical scribe services" and "remote medical scribe" (currently around page two on the core term). That equity is an asset, not a legacy to abandon. Medical scribing is one capability under the Clinical Intelligence Platform, so the play is to build on what's ranking and bridge it up to the category, not start over.

Four buckets, from proven to aspirational:

• What's already ranking (protect and grow): "medical scribe services" · "remote medical scribe" · "real-time remote scribe" · "hybrid AI scribe" · "medical scribe company / partner." Scribe-X.com's proven equity ... keep these strong, and frame the scribe as one capability of the platform.
• Broader existing demand (capture): "AI medical scribe" · "ambient AI scribe" · "AI scribe for FQHC / community health" · "AI medical coding" · "chart prep automation" · "physician documentation burden." Where the wider volume is, even though it's the old category.
• The category we're seeding (own the new term): "Clinical Intelligence Platform" · "human-led AI scribe" · "AI plus human intelligence (healthcare)" · "human-at-the-center medical AI" · "whole patient journey documentation."
• High-intent pain searches (long-tail, ready to act): "providers charting at night" · "AI scribe didn't work / didn't stick" · "missed medical codes lost revenue" · "FQHC provider retention / burnout" · "who is liable for AI medical notes."

---

That closes Phase 4 (Language). Now Phase 5: the go-to-market idea banks, starting with the sales playbook.

---

The meeting sequence

• First conversation: capability, the problems across the visit, and value by category. No menu.
• Second conversation: the solution menu, after discovery. Leading with the menu asks a buyer to choose before they understand what they're choosing between.
• Enterprise motion: service-level and outcome commitments, the layers switched on, terms written into the agreement (see §11).
• Solo early-adopter motion: preferential terms, the integration roadmap, and a feedback expectation ... scope described honestly, never as a lighter Assist.

The motion

• Open with value, not a demo. The Practice Health Scorecard and the free trial are the front doors.
• Run the plan: Discover → Pilot → Expand (see §15). The pilot is where they feel it.
• Multithread the buying group: the CMO champions it, the CMIO usually supports, the CIO clears the risk, the CFO is the cost-first wall you get past through the champion armed with numbers, and the CEO is won separately on strategic and community grounds (see §6).
• Quote from the proposal template. Since named tiers are gone, the proposal template is the artifact carrying commercial structure ... without it, retired complexity becomes improvised quoting.

Plays by persona

Discovery questions that move a deal

Open with a no-oriented question (§17), then size the pain and the stakes.

• "How are you using AI in your practice today?" (the signature opener)
• "What happens to the orders, the coding, and the follow-ups your AI scribe doesn't touch?"
• "What did your last AI rollout actually change?"
• "Who owns the accuracy when the AI gets a note wrong?"
• "If you could set how much human each provider gets, who'd need the most?"
• "What are the ripple effects, for you and the practice, if this stays the way it is?"

---

Next: §20, Lead Magnets & Scorecards.

---

Lead magnet ideas

Gated, value-first, each tied to a pain we already named. Every one captures an email and feeds the pipeline.

• The Practice Health Scorecard (flagship): a few questions in, a score out ... where the workflow breaks, what it's costing, and the next steps. Email-gated, results to the CRM. The hero's secondary CTA.
• "Cost of doing nothing" calculator: estimate the annual cost of burnout, turnover, and leaked revenue (ties to §9).
• Whole-journey gap assessment: where work goes undone before, during, and after the visit.
• FQHC benchmark report: how community health centers are pairing AI with human intelligence (industry data, feeds the AEO play and the webinar).
• Compliance check (for the CIO): "Is your AI documentation a liability?" (ties to the liability research).
• Pajama-time self-check: a quick, provider-facing read on after-hours charting.
• The "5 ways" guide: the webinar's content as a download (ties to §21).

The flagship: the Practice Health Scorecard

• What it does: a short interactive assessment, then a score plus the gaps, what they cost, and recommendations with next steps.
• Where it lives: the secondary CTA on the homepage hero (the primary CTA is the pilot / book a call).
• What it is: the Discover step productized (§15), and Deliverable 5 of this engagement.
• Status: parked. The scoring logic, the questions, and the wire-up (capture email, deliver recommendations, push to the CRM) get built when we render the homepage.

Naming the scorecard

All of these stay live possibilities ... we keep the menu and start with one for the homepage. Grouped by angle:

• Ties to the category: Clinical Intelligence Scorecard · AI + Human Readiness Scorecard.
• Ties to the practice: Practice Health Scorecard · Practice Efficiency Scorecard.
• Ties to the journey: Patient Journey Scorecard · Care Journey Scorecard.
• Ties to readiness: FQHC Readiness Scorecard · Documentation Readiness Scorecard.
• Button copy (can differ from the name): "Score Your Practice" · "Get Your Score" · "See Your Gaps."

---

Next: §21, Webinar & Event Topic Ideas.

---

The anchor: Episode 1 (live)

The pattern (so the team can keep generating)

A provocative truth about the risk or the problem, then a twist line. Underneath, "5 ways [this audience] pair AI with human intelligence," ending in the payoff that audience cares about. Same spine every time; swap the audience and the payoff.

More episodes, by audience

---

Next: §22, the Blog Engine.

---

What the engine is for

• One post a day, in Scribe-X's voice ... it inherits the Language Library and the whole MMF.
• Two goals: seed thought leadership in the FQHC and AI-documentation space, and the bigger one, be the source answer engines (Claude, ChatGPT, Gemini, Perplexity) pull from when an ideal buyer asks about AI scribes, documentation, FQHC operations, or liability.

Why structure matters (the citability thesis)

Answer engines preferentially quote content that's well-structured, answers the question directly, and carries original facts and figures. Every post is engineered to be quoted, not just read. Data isn't decoration here ... it's the thing that gets cited.

Anatomy of a citable post (the agent's output skeleton)

• TLDR up top: one or two lines that answer the post's question outright ... the quotable line.
• Key takeaways: three to five bullets right under the TLDR, each self-contained and grab-able.
• The direct answer first: the core question answered in the opening, before any wind-up.
• Original facts and figures: freshly researched for that post, each with a citation. Every claim that can carry a number, does.
• Clean structure: question-shaped H2s and H3s, one idea per section, scannable.
• Concrete and grounded: examples from the FQHC and ICP world, never generic.
• A short FAQ block at the end: question-shaped, matching how people actually ask an engine.
• A soft close: a relevant lead magnet (the Practice Health Scorecard) or next step.

Operating rules

• Research fresh every post. Pull current data and cite it; don't recycle stale stats.
• Map every post to an ICP pain, a belief, or an objection. No adjacent fluff.
• Inherit voice and positioning from the MMF: trained people behind the automation, the whole journey, no AI-Parmesan, the Language Library and Glossary rules.
• Never fabricate data, never overclaim on liability (follow the Regulatory & Liability Context appendix), and never overclaim scope ... pair "whole journey" with the live-vs-coming split (see the scope-honesty guardrail).

---

AEO, not just SEO

SEO is about ranking in the links. AEO is about being the answer the engine gives, and cites, when a buyer asks "the best AI scribe for community health" or "an AI scribe with independent check." Buyers increasingly ask the engine, not the search box. We engineer to be the answer it returns.

The pages to publish (about 10 to 20)

• A deep FAQ page: the canonical, question-shaped answers to every buyer question. The single most answer-engine-friendly asset.
• Comparison posts: "Best AI Scribes of 2026" and a "Top 5 AI Medical Scribes" piece. Comparison data is exactly what an engine grabs when asked to compare ... so we seed it with accurate, structured, fair tables.
• Definitional pages: what is an AI medical scribe, what is a Clinical Intelligence Platform, what is hybrid AI scribing.
• Use-case pages: the AI scribe for FQHCs, for specific specialties, for multi-site groups.
• The category page: the Clinical Intelligence Platform, defined and owned.

Citability principles (same DNA as the blog)

• Direct answers, question-shaped headings, structured data (tables and lists), facts and figures with sources, schema markup, and freshness.
• Own the category term (Clinical Intelligence Platform) and capture the existing-demand terms (the medical-scribe family, see §18).
• Be the most accurate, most complete, most structured answer on each question. That is what gets cited.

---

Next: §24, the FAQ.

---

What is the Clinical Intelligence Platform?
One platform that pairs automation for the volume with a trained, US-based Remote Healthcare Assistant for the judgment, across the whole patient journey ... not just the note. How much human each provider needs is set on a toggle bar, per provider.

How is this different from an AI scribe?
An AI scribe stops at the note. The Clinical Intelligence Platform completes the whole patient journey, with a trained Remote Healthcare Assistant owning the judgment and the work around the visit.

How is the CIP different from native AI documentation tools?
Native AI generates a note. The Clinical Intelligence Platform supports the full visit ... chart prep before, an independent check on the note, and follow-up after ... tailored to how each provider works. That's where documentation problems actually live.

We already use our EHR's built-in AI. Why add Scribe-X?
Built-in tools handle the encounter for providers who use them. They don't prep the chart, adapt to individual workflows, or support providers who won't drive the technology themselves. Scribe-X covers what happens around the note.

What role does AI play in the CIP?
Automation accelerates documentation across the encounter. Scribe-X leads with human expertise, so every provider gets support tailored to how they work, not just a tool set to a default. The result is documentation that's accurate, complete, and built around the outcomes that matter to your organization.

What's the difference between Live, Assist, and Solo?
They're the three solutions a provider can be set to on the toggle bar, based on how much human support their work needs. Live puts a trained Remote Medical Scribe on the encounter in real time; Assist pairs automation with a trained Remote Healthcare Assistant who finishes the work so it arrives ready to sign; Solo is self-directed ... automation drafts and your team reviews and finalizes, available now to early-adopter practices at preferential terms while integrations are built.

Do all our providers have to use the same solution?
No. Providers are set to Live, Assist, or Solo individually, based on what each one needs, all under one agreement. Your providers don't all have to work the same way.

Are your trained Remote Healthcare Assistants US-based?
Yes. They're US-based and the patient record stays onshore, which reduces the risk a clinic carries rather than adding to it.

We tried an AI scribe and it didn't stick. Why is this different?
What stalled was a tool handed to the provider to run without support. Here a trained Remote Healthcare Assistant carries the work, so there's nothing left for a busy provider to adopt wrong.

What EHR systems does Scribe-X support?
Scribe-X works with all major EHR platforms, including Epic, Athena, NextGen, and eClinicalWorks ... over 20 EHRs. Scribe-X learns your specific platform and workflows rather than forcing a generic setup, and any edge cases are confirmed during discovery before anything is signed.

How long does implementation take?
Most organizations are live within a few weeks of contract signing. Your onboarding contact walks through the process before anything is signed, so timeline and go-live specifics are set upfront and there are no surprises on go-live day.

How much IT involvement is required?
Most implementations require standard EHR access provisioning and a BAA (Business Associate Agreement) review. Scribe-X handles the setup process end to end ... IT gets looped in where needed, not asked to carry the project.

Is the CIP HIPAA-compliant?
Yes. Scribe-X executes a BAA before any provider encounter, and the platform runs on HIPAA-compliant controls: encrypted in transit and at rest, with role-based access and audit logging. Detailed security documentation is available on request.

How does pricing work?
Pricing depends on configuration ... which providers are on which solution, the scale of the program, and any added intelligence layers. Contact Scribe-X to scope the right fit; the price conversation happens on the call.

Who is liable if the AI gets a note wrong?
Clinical decisions, the medical record, and the signature are always the provider's. Scribe-X is accountable for the work our automation and our trained staff produce, and on Assist and Live an independent check happens before the note reaches your chart ... the better question isn't the model's accuracy percentage, it's who checks the work before it's signed.

Who checks the work before it reaches our chart?
Somebody other than the person signing it. On Assist and Live, every note passes a trained Remote Healthcare Assistant before it reaches your chart ... a second set of eyes on every note. On Solo, your team reviews and finalizes.

Can we start with just the automation?
Yes ... that's Solo, available now to early-adopter practices at preferential terms while integrations are built. Solo today is the note, the after-visit summary, capture, provider customization, bilingual and telehealth support, and documentation completeness. It doesn't include order entry, an independent check, or the quality layer.

What specialties do you support?
27 medical specialties, across FQHCs and for-profit healthcare centers.

How do we start?
Get your Practice Health Score, start a free trial on a few providers, or book a structured pilot with defined KPIs ... your contact scopes the right entry point during discovery.

What happens during a trial?
A small number of providers run on Scribe-X in their real workflow for a defined period, with success measured against KPIs you set going in. You see the actual output before committing to anything broader, and the account team walks the results with you at the end.

How fast can we get a program live?
Faster than hiring in-house. Scribe-X handles the recruiting, training, and EHR onboarding, so a program goes live in weeks, not the months an internal build takes.

What does ongoing support look like after we go live?
Your account team stays active after go-live, monitoring performance, supporting slower-to-adapt providers, and flagging issues early. We start from your definition of success and work backwards, and if something isn't working you have a defined contact path, not a ticket queue.

Can a trained Remote Healthcare Assistant handle orders, meds, and instructions?
Yes, and that's the point. The platform goes past the note: the trained Remote Healthcare Assistant enters the orders, medications, referrals, and after-visit instructions the provider directs, so the provider isn't stuck on data entry. The provider always reviews and signs.

What if a trained Remote Healthcare Assistant is out or unavailable?
Coverage is part of the service model, since you're working with a service, not a single hire ... a trained backup steps in, and scaled Live programs carry a 100% coverage guarantee. Your providers don't lose a day to it.

Can you help with value-based care?
Yes. The whole-journey work the platform carries ... closed loops, captured codes, caught care gaps ... is exactly what value-based and quality programs reward. A trained Remote Healthcare Assistant makes sure the documentation and follow-through actually support the measures you're accountable for.

Is this just transcription, or an AI-only tool?
Neither. Transcription turns speech into text and stops. An AI-only tool drafts the note and stops. The Clinical Intelligence Platform completes the whole patient journey, with a trained Remote Healthcare Assistant owning the judgment and the work around the visit.

We're already fairly happy with our current setup. Why look at this now?
Most organizations that look into this have an AI tool handling the note but not much else ... the chart prep, the coding review, the follow-ups still sit with the provider. If that isn't costing you anything visible yet, it likely will as volume grows or turnover hits ... worth a conversation before it does.

How do we build the internal business case?
Scribe-X can build a tailored ROI analysis around your provider mix and payer profile, so the program is revenue-generating from the start, not a cost center you have to defend later. Your champion also gets the cost-of-doing-nothing math (§9) to set the price against.

---

Next: §25, Use Cases.

---

• The FQHC losing providers to burnout. Night charting and the unfinished work around the visit are pushing good clinicians out. The platform gives the day back, and the providers stay. (PPS setting: the value language here is retention and capacity, not coding revenue.)
• The fee-for-service practice leaking revenue through missed codes. Reimbursement earned and not captured, month after month. A trained Remote Healthcare Assistant supports the coding so the revenue actually lands. (Fee-for-service setting: this is where coding-level value is real cash.)
• The clinic whose ambient tool stalled. The tool was turned on and nobody kept using it. A trained Remote Healthcare Assistant carries the work here, so it sticks where the last one stalled.
• The providers struggling to see more patients. Admin work and the endless checkboxes are still a burden despite AI alone. Provider support expands patient access and captures the revenue that comes with it.
• The multi-site group that needs flexibility. Different providers need different levels of help. The toggle bar sets each provider's solution under one agreement.
• The practice drowning in chart prep. Providers walking into visits cold, prepping their own charts at night. Chart prep done 48 hours ahead changes the whole day.
• The private outpatient or specialty group protecting throughput. Procedure-heavy days, revenue tied directly to volume, and providers who can't afford documentation slip. Live covers the encounters where documentation can't wait, Assist carries the rest of the roster, and the group buys it as one account. (Fee-for-service setting: capacity and coding value are both real cash here.)
• The organization building next year's board case. Leadership needs to show the board a technology investment tied to measurable outcomes, not another line item. A tailored ROI analysis ties the program to retention, revenue cycle, and capacity in numbers a board can act on.
• The multi-site group standardizing quality reporting. Different sites document differently, and leadership-level reporting doesn't roll up cleanly. Consistent, leadership-level reporting gives one view across sites instead of a spreadsheet stitched together by hand.
• The organization deciding whether to build in-house or partner. Hiring, training, and managing an internal documentation team takes months and carries its own turnover risk. Scribe-X gets a program live in weeks, with recruiting, training, and coverage already built in.
• The FQHC preparing for a compliance or security review. The CIO needs a clear answer on where data lives and who's accountable before a reviewer asks. trained, US-based Remote Healthcare Assistants and onshore data handling give a documented answer instead of a vendor promise.

---

Next: §26, Social Proof.

---

Provider quotes

• Capacity: "We are now able to see 4 more patients per day. We couldn't have done it without the scribes." ... Dr. Anna Lundeen
• Staying in medicine: "Adding a medical scribe to my team made the difference between closing my doors and practicing for five more years." ... Dr. Murlan G.

More on the site: Dr. MacDonald ("I walk out of here and my charts are done") and Greg Parker (multi-year client, praised COVID-era responsiveness). Pick by message: capacity, retention, or night charting.

October 2025 client survey (V5 additions)

• Jason Sargent · Dunes Family Health ... carries throughput and burnout in a provider's own voice.
• Danielle Tao · Good Shepherd Health Care System
• David Flaherty · Katahdin Valley Health Center

Named training staff appear repeatedly across the survey responses, which substantiates "trained" as more than a modifier. Open: confirm the survey's testimonial opt-in covers sales use before wide circulation.

Named customers (verifiable, public case studies)

• Hometown Health Center ... rural FQHC, Newport, ME (case study).
• Foresight Health ... featured partner.
• Reach: FQHCs and for-profit centers across 27 specialties and 23 states, on over 20 EHR systems.

---

That completes the planned framework (§13 Proof parked for data). The Appendix below always stays last.

---

Every claim has one canonical form; short forms derive from it. These blocks lift into assets word for word.

Assist

Assist completes the work.
Automation drafts the documentation. A trained Remote Healthcare Assistant finishes it: the note in your chart, the orders, the codes, the after-visit summary. It arrives ready to sign.

Live

A trained Remote Medical Scribe documents the encounter in real time. The work is done before the patient leaves.

Solo

Automation drafts the documentation from the visit. Your team reviews and finalizes it. Available now to early-adopter practices while integrations are built.

Accountability

Canonical: Every note passes a trained Remote Healthcare Assistant before it reaches your chart.
Short form: A second set of eyes on every note.
Scoped to Assist and Live, never claimed for Solo or the platform.

Organization level

One vendor for all solutions. Every provider set to the level of support that fits them, and moved when that changes.

Readiness and closure

• Lead, feature level, all three solutions: "Every note is ready to sign the same day." Short form: "Ready to sign, same day."
• Support, outcome level (figure supplied in the asset): "Chart closure time reduced by X percent." · "X percent same-day chart closure." Two distinct metrics ... never merged (§13).

Patient experience

Providers spend the visit with the patient rather than the keyboard. Qualitative only ... no figure, no comparative claim.

The pitch

Scribe-X is the Clinical Intelligence Platform for outpatient organizations. Automation drafts the documentation and trained people finish it, so work arrives ready to sign instead of waiting on a provider. Every provider is set to the level of support that fits them, from a real-time scribe to self-directed automation, in one account with one vendor.

---

Register note. This is the one section where "human in the loop" is permitted as a term of art, and where the self-review distinction may be stated plainly, sourced to competitors' own disclosures rather than characterized. HIPAA, encryption, data handling, and access-control language holds. SOC 2 is not claimed ... compliance infrastructure is partial; HIPAA statements are unaffected.

The legal trend: a licensed human must review the AI

• Texas SB 1188 (effective Sept 1, 2025): a practitioner may use AI for diagnosis or treatment only if they personally review all AI-generated content before the clinical decision, plus patient disclosure. Penalties run $5,000 to $250,000 per violation.
• California AB 3030 (effective Jan 1, 2025): generative-AI patient clinical communications need a disclaimer ... but communications a licensed provider reads and reviews are exempt. A direct legal reward for a human at the center.
• California SB 1120, the Physicians Make Decisions Act (effective Jan 1, 2025): when a health plan uses AI in utilization review, a licensed physician must make the medical-necessity decision, based on the patient's own clinical record.
• The scale: law firms tracking the space report roughly 40-plus bills across about 25 states in 2026, mostly requiring clinical oversight of AI and patient disclosure.

Offshore PHI: the US-based advantage

• Florida SB 264 (effective July 1, 2023): patient EHR data must be physically maintained in the continental US, its territories, or Canada ... including third-party and cloud vendors ... with a compliance affidavit signed under penalty of perjury. Stricter than HIPAA, which sets no geographic limit.
• HHS OCR warning: storing or processing ePHI overseas can raise HIPAA risk that the US provider cannot offload, because OCR has limited reach over foreign vendors.

Colorado (correct the common misread)

Colorado is not anti-AI-in-healthcare. Its AI Act (SB 24-205) was an anti-discrimination law that carved out provider-action healthcare AI, was repeatedly delayed, and was repealed and replaced in May 2026 with a narrower, more HIPAA-friendly version (effective Jan 1, 2027). Colorado's 2026 healthcare bills (HB 26-1139, HB 26-1195) mandate independent check, which favors our model.

The litigation reality

• Patient-side AI malpractice is still forming: no landmark case yet holds a clinic liable for an AI-documentation error. The emerging theory is over-reliance and automation bias.
• Billing enforcement is already live and expensive: UCHealth paid $23M (False Claims Act, 2024) over an automated coding rule that upcoded ER visits; Aetna paid $117.7M over inaccurate Medicare Advantage diagnoses.

How it maps to our messaging

The law is mandating the model we sell: a US-based independent checks and owns the AI output. Pure-autonomous or offshore AI leaves the provider as the unprotected "liability sink." The sharpest reframe: turn "accuracy" into "accountability." The question isn't the model's accuracy percentage ... it's who's accountable when it's wrong. A trained, US-based Remote Healthcare Assistant is the documented answer.

---

The platform

Clinical Intelligence Platform (CIP) is the full name; Clinical Intelligence is the category shorthand. Spell it out on first use, then "the CIP" or "the platform." ScribeBridge is retired.

Solutions

• A solution is what a customer selects for one provider. Three exist and may run together across one organization.
• Live ... high-touch and specialty. Assist ... the flagship. Solo ... self-directed entry solution, pre-release with early-adopter availability.
• Retired: Pulse (replaced by Solo); Essentials and Professional as names. Enterprise is permitted as an ordinary adjective and as the commitment construct (§11), never as a tier, SKU, package, or column header. Live Enhanced is internal only, with no external name or date until a release gate exists.
• Presentation order: detail presentation leads Live, Assist, Solo. A left-to-right visual may run Solo, Assist, Live to show ascending human involvement. Never mix both inside one asset.

People

• trained Remote Healthcare Assistant (RHA) and trained Remote Medical Scribe. "Trained" is a permanent modifier, not an intensifier. First use spells out the title with the acronym; later uses take "trained RHA."
• "Scribe" survives only inside "trained Remote Medical Scribe" and in the company name. Never "AI scribe" (for us), "scribing services," or "our scribes." Revisit at the 2027 shift.
• Never for RHAs: certified, licensed, specialist, or "humans."

Technology

• AI is the competition's word and the category's word. Automation is ours. Use "automation" and "adaptive automation" for Scribe-X. Use "AI," "AI-only tools," "ambient AI," "AI scribes" for competitors, the category, and the market.
• Never for Scribe-X: our AI, AI-powered, AI-driven, AI-enabled, autonomous.
• AEO carve-out: "AI" is permitted in page titles, metadata, schema, and category-definition copy where it matches search behavior, and in regulatory copy where it's a term of art. Body copy describing our product says automation.

Layers, SKUs, features, outcomes

• A layer is a band of capability across the visit: Pre-Visit, Encounter, Revenue, Quality Intelligence. A SKU is what a customer can buy. A feature is something the product performs. An outcome is something the customer realizes downstream, gated by their own decisions.
• Chart prep is a feature inside Pre-Visit Intelligence, not the name of the SKU.
• Retired: configure/configured (use customized, tailored, adjusted) · spectrum.

The human layer

• The layer does two jobs, named separately. Completion is primary and external: the work arrives finished. Accountability is secondary externally and primary in regulatory copy: an independent check before anything reaches the chart.
• "Completes" is the anchor verb, with the trained RHA as subject. "Finishes" and "carries" are body synonyms. "Ready to sign" is a sanctioned standard phrase.
• Accountability is scoped to our output. We're accountable for the work our automation and our trained staff produce. Clinical decisions, the medical record, and the signature remain the provider's.
• The three jobs of the human layer: catching errors, supporting coding accuracy, and adapting to how each provider documents.
• Retired: "human review" (near-total ... say "independent check") · "verified" as an absolute · "judgment" as an RHA descriptor (use intelligence) · own/ownership externally · delivers/delivery externally. "Human QA" sparingly, operational and liability contexts only. "Human in the loop" / HITL in regulatory and technical copy only. "A human at the center" survives only inside Assist- and Live-scoped copy, never as the platform umbrella.

Metrics

Time to close and same-day chart closure are distinct metrics, never used interchangeably and never merged into one "chart closure" figure (§13).

Prohibited constructions

• No X-not-Y in any verbatim artifact. Narrow exemption: the legacy tag #PatientsNotPaperwork is a fixed proper noun. The exemption doesn't license "paperwork" in sentences or new X-not-Y constructions.
• No word-family echo inside a locked form. Anchor terms repeat across assets, vary within a passage, and don't occupy a fixed slot.
• No absolutist QA claims. Never imply every note receives deep review.
• "Paperwork" is retired in body copy. Name the concrete work instead: the chart, the codes, the orders, the inbox.
• House rules hold: no em dashes ("..." or single hyphens) · no anaphora · no manufactured rule-of-three · contractions always · concrete over metaphor.

Internal only, never external

"Assist = Solo + Delivery + Review." Delivery and copy-paste mechanics. Coordination and human-customization mechanics. Realization-effort shares, capture rates, cost and margin language, confidence tiers.

Register discipline

Internal and external vocabularies stay separate. Four audiences take different register but identical vocabulary: prospects, current customers, RHA and scribe recruiting, partners. Register examples live in the brain; the vocabulary above doesn't vary by audience.