# Patient Square: Practice Copilot and Hospital Copilot

> Patient Square makes two AI copilots for clinicians. Practice Copilot can use Patient Square EHR as the practice system of record or work alongside an existing EHR. Hospital Copilot can deploy the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Live consultation audio is processed in memory and discarded when the note is drafted. In India, uploaded recordings use a separate retention mode with explicit consent.

## Why Patient Square exists

- Documentation should not compete with patient care. Patient Square's ambient AI scribe turns the visit into a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review and signature.

## What each product does

### Practice Copilot (for independent clinics)

- Ambient AI scribe: listens during the visit; the clinician does nothing but see the patient. A SOAP note, ICD-10 code suggestions, and a prescription draft are ready when the visit ends.
- ICD-10 suggestions and Rx draft are each traceable to the moment in the conversation they came from.
- Review-and-sign: nothing is filed or prescribed without the clinician. Every output is a draft.
- AI Receptionist: every call answered, appointments booked, 24/7.
- eRx: drug, dose, route, and frequency pre-filled from the conversation; nothing sends without a signature.
- AI Follow-ups, WhatsApp, scheduling, and Patient Square EHR round out the seven modules.
- Record system: use Patient Square EHR or keep an existing EHR. Signed notes can be copied into a web-based EHR or downloaded in the supported export formats.

### Hospital Copilot (for multi-department hospitals)

- Everything in Practice Copilot, plus three hospital-only modules.
- AI Discharge Summary: drafted from the stay's own record during the stay, reviewed and signed before the family waits.
- Claims Management: in the US, documentation-complete claims from day one; in India, TPA and cashless files assembled from the chart, pre-auth to final bill.
- Bed / IPD Management: live census, admissions, transfers, and estimated discharges on one board.
- One chart from OPD to discharge, readable by every department.
- Record system: deploy the complete Patient Square HIS/EHR or keep an existing HIS/EHR and define the workflow during discovery.

## Privacy and compliance

- Live consultation audio is processed in memory and discarded when the note is drafted. In India, uploaded recordings use a separate retention mode with explicit consent.
- Website analytics: Plausible page counts use canonical page addresses without query parameters, fragments, referrer data, or custom properties. Page counts and PostHog events are not sent when Do Not Track or Global Privacy Control is enabled. PostHog uses a same-origin proxy that removes forwarding IP headers and sets its client-IP field to 0.0.0.0; it sends explicit site interaction events only, with automatic capture, page views, page-leave events, and session recording disabled. Its state remains in memory.
- PHI is encrypted in transit (TLS 1.2+) and at rest (AES-256).
- US: handled to HIPAA standards, with a BAA available. A SOC 2 Type II audit is underway; the report is available on request.
- India: handled to DPDP Act 2023 standards, consent-first and purpose-limited.

## Regions

- United States: https://patientsquare.com/, HIPAA compliant; existing-record-system deployment is presented first, with Patient Square EHR/HIS available for greenfield buyers.
- India: https://patientsquare.com/in/, captures English, Hindi, and 20+ Indian languages (Tamil, Telugu, Bengali, Marathi, Gujarati, Kannada and more) on India-tuned speech models; Patient Square EHR/HIS deployment is presented first, while existing record systems remain supported. ABDM/ABHA integration is on the roadmap.

## Key pages

- US landing: https://patientsquare.com/
- US Practice Copilot: https://patientsquare.com/us/products/practice-copilot/
- US Hospital Copilot: https://patientsquare.com/us/products/hospital-copilot/
- US pricing: https://patientsquare.com/us/pricing/
- US security: https://patientsquare.com/us/security/
- US about: https://patientsquare.com/us/about/
- India landing: https://patientsquare.com/in/
- India Practice Copilot: https://patientsquare.com/in/products/practice-copilot/
- India Hospital Copilot: https://patientsquare.com/in/products/hospital-copilot/
- India pricing: https://patientsquare.com/in/pricing/
- India Practice Copilot trial: https://copilot.patientsquare.com/in/trial
- India security: https://patientsquare.com/in/security/
- India about: https://patientsquare.com/in/about/

## Pricing model

- Practice Copilot: flat rate per clinician per month, unlimited visits and notes, no per-note metering, no setup fees. Three tiers: Assist from $79 / Rs 1,599, Copilot $119 / Rs 2,399, Autopilot $199 / Rs 3,999. US clinics book setup for a 7-day trial; India clinics can start a 7-day free trial through the India trial page.
- Hospital Copilot: priced per bed or per doctor, whichever fits how the hospital runs. All ten modules, unlimited visits, notes, and summaries. Contact for pricing.

---

# Full text of every post

Auto-generated from 427 published posts, newest first. Each post's canonical URL(s) are listed above its text.

## Medical Record Signature Requirements for AI Notes
https://patientsquare.com/us/blog/medical-record-signature-requirements-ai-notes/
Published 2026-10-16 · Tags: medical-records, signatures, ai-scribe, documentation, medicare

Use CMS signature rules to build a review, concurrence, attestation, and exception workflow for clinician notes drafted by people or AI.

For Medicare medical review, the clinician responsible for the care must authenticate an AI-drafted entry. CMS says the clinician should sign the entry; the human or AI scribe does not need to sign or date it. A practice still needs its own policy for review, electronic-signature safeguards, exceptions, and any stricter state, payer, facility, or service-specific rule.

CMS added artificial intelligence to its scribe-signature guidance in July 2025. The practical rule is short: the treating practitioner signs an AI-transcribed entry when Medicare signature requirements apply, and the scribe does not need to sign or date it (CMS MLN905364, July 2025).

That sentence settles who acts. It does not tell a practice which version was reviewed, what to do with a missing signature, or how to keep an electronic signature from becoming a shared button. Those are the policy and system questions that decide whether concurrence can be proved later.

> Key takeaways
> - Treat every AI note as a draft until the responsible clinician reviews and authenticates it.
> - Keep authorship, transcription provenance, and clinical concurrence as separate facts.
> - Route missing, illegible, late, and post-signature corrections through different exception paths.
> - Test six synthetic failure cases before measuring how fast clinicians can clear the queue.

This article is an operational reading of current federal sources, not legal or billing advice. Medicare policy, a hospital condition of participation, state law, payer rules, service-specific requirements, medical-staff bylaws, and local policy can set different or stricter conditions. Name the source behind each rule in your own policy.

## CMS added AI to the scribe rule

CMS does not describe a signature as decoration at the bottom of a note. Its July 2025 fact sheet says reviewers look for signed and dated documentation from the people responsible for providing care. It also says reviewers use signatures for two purposes: meeting an explicit rule and resolving concern about whether documentation is authentic (CMS MLN905364, July 2025).

That distinction matters. A missing signature does not have one universal consequence across every record. The relevant statute, regulation, national coverage determination, local coverage determination, order requirement, and authenticity evidence determine the path. A clinic policy that says "all unsigned notes fail" is too blunt. A policy that says "sign whenever convenient" is worse.

Hospital records have a separate federal baseline. [42 CFR 482.24](https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-G/part-482/subpart-C/section-482.24) requires hospital medical-record entries to be legible, complete, dated, timed, and authenticated by the person responsible for providing or evaluating the service, consistent with hospital policy. The same section requires final completion of hospital records within 30 days after discharge. That 30-day condition is hospital-specific. Do not paste it into an office policy and call it a universal Medicare deadline.

## One signature carries three facts

The current Medicare Program Integrity Manual names AI directly. When a scribe documents a medical-record entry, CMS does not require the scribe to sign or date it. The treating practitioner signs to affirm that the note adequately documents the care. CMS says the same practitioner concurrence is required when artificial intelligence captures the transcription ([Medicare Program Integrity Manual, section 3.3.2.4](https://www.cms.gov/sites/default/files/2024-10/r12897pi.pdf)).

So the useful record has three separate facts:

| Fact | The question it answers | Evidence to preserve |
|---|---|---|
| Clinical author | Who provided or evaluated the service? | Practitioner identity and role |
| Draft provenance | How did the words enter the draft? | Approved workflow metadata under local policy |
| Concurrence | Who reviewed and accepted this entry? | Signature, date or time evidence, and record version |

Do not make the AI tool the clinical author. Do not make a generic "AI generated" badge substitute for the clinician's action. And do not hide the draft source if local policy requires provenance. These are different controls.

## Give each signature exception its own lane

A queue labeled "unsigned" usually mixes problems that should not share a fix. Use the matrix below before anyone starts clearing old charts.

| Exception | First question | Safe operational path |
|---|---|---|
| Ordinary unsigned draft | Has the clinician reviewed the actual final draft? | Review, correct, then sign under the normal policy |
| Wrong clinician assigned | Who provided or evaluated the service? | Reassign through an approved path; never sign for a colleague |
| Material error before signature | Does the draft match the encounter evidence? | Correct the draft, preserve necessary provenance, then review again |
| Missing required signature found later | Does the controlling rule permit attestation? | Use the author-created attestation path only when allowed |
| Illegible handwritten signature | Can the author be identified? | Attach the approved signature log or other allowed evidence |
| Correction after signature | Does the record need an addendum or correction? | Preserve the signed entry and use the approved amendment path |
| Order missing a signature | Is the order subject to a distinct timing rule? | Stop and apply the order-specific rule; do not reuse the note-attestation lane |

CMS accepts an attestation for some missing signatures in medical records other than orders. The record's author must create it, it must identify the beneficiary and entry, and it cannot repair a rule that required the signature before a specific event or date. CMS gives the plan of care as an example: an attestation cannot backdate it (CMS MLN905364, July 2025).

For an illegible signature, CMS permits a signature log or an attestation that identifies the signer. A signature log may be created later. That does not turn it into a universal repair for missing authorship, a wrong signer, or a missing order. It answers an identity problem.

## Break the version chain on purpose

Use synthetic records. No real patient information belongs in an acceptance test.

1. Send a correct draft to the responsible clinician and confirm that the signed version is the version reviewed.
2. Put the wrong patient in a draft and confirm that it cannot be signed into the intended chart.
3. Change a medication or assessment sentence before signature and confirm that the clinician sees the changed version.
4. Leave a required signature missing and confirm that the exception remains visible to its owner.
5. Submit an illegible handwritten signature and confirm that the approved signature-log path identifies the author.
6. Request a correction after signing and confirm that the original stays intact while the approved addendum carries its own author and time.

Time the ordinary case only after all six pass. Fast review of the wrong version is still wrong.

## Only then build the worklist

The worklist should show more than a red badge. At minimum, capture the encounter identifier, responsible clinician, draft-created time, current version, review state, exception type, signature time, and final disposition. Limit the worklist to the information needed for the job, and keep access consistent with the practice's [security controls](../../security/).

One clean state model is enough:

```text
DRAFT CREATED
  -> CLINICIAN REVIEW
      -> CORRECTION NEEDED -> CLINICIAN REVIEW
      -> READY TO SIGN
          -> SIGNED AND LOCKED
              -> APPROVED CORRECTION OR ADDENDUM, IF NEEDED

EXCEPTION PATHS
  wrong clinician | missing signature | illegible signature | order rule
```

Measure the queue by age and reason, not only by total count. "18 unsigned" tells you there is work. "Seven awaiting first review, three returned for material correction, six ready to sign, two assigned to the wrong clinician" tells you what to fix.

The [medical-chart audit checklist](../medical-chart-audit-checklist/) helps test a sample after rollout. If signed content needs a later change, use the separate [correction and addendum workflow](../medical-record-amendment-correction-addendum/) instead of overwriting the original entry.

## The button is not the evidence

CMS tells providers using electronic signatures to protect the system against modification and to apply administrative safeguards that fit recognized standards and laws. The signer and provider remain responsible for authenticity. CMS also directs physicians to check with counsel and malpractice insurers about alternative signature methods (CMS MLN905364, July 2025).

A vendor demo should therefore answer concrete questions:

- Can one user apply another user's signature?
- Does the record show which version the clinician reviewed?
- What happens when the note changes after review but before signature?
- Can an administrator see the signature time without changing the record?
- Does an addendum preserve the original signed content?
- What evidence leaves with the practice during an export or vendor exit?

We think the version question is the most revealing. A polished signature screen is not useful if a late edit can slip into the note without a fresh review.

## The software should stop before authorship

AI Scribe by Patient Square is an ambient AI medical scribe. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

The clinician owns the review and signature. The scribe does not decide whether a Medicare signature requirement is satisfied, invent a concurrence statement, apply a colleague's identity, or choose an attestation route. Those decisions stay with the practice's clinicians, compliance owners, billing owners, and counsel.

Use the [clinical documentation audit](../ai-scribe-clinical-documentation-audit/) to compare source evidence with a finished note, then run the six signature cases above. The product question comes after the record-control question: can your team show who reviewed which version and what happened when the normal path broke?

---

## Patient Grievance Form for a Medical Practice
https://patientsquare.com/us/blog/patient-grievance-form-medical-practice/
Published 2026-10-15 · Tags: patient-grievance, complaint-form, practice-operations, patient-rights

Use a patient grievance form that captures the concern, preferred contact, urgent routing, investigation owner, response, and closure without forcing legal conclusions.

A patient grievance form should capture who is raising the concern, safe contact preferences, the event in the person's own words, dates and locations, people involved, supporting material, requested response, accessibility needs, and permission to contact a representative. Staff need a separate routing and closure log.

"Please call my daughter, not the number on the chart." That sentence can matter more than a page of complaint detail. A useful grievance form captures the concern and gives staff a safe way to respond.

> **Key takeaways**
> - Let the patient describe the event in their own words and choose a safe contact route.
> - Keep investigation notes and legal conclusions off the patient-facing form.
> - Route urgent safety, privacy, billing, and service concerns to different owners.
> - Track acknowledgement, response, and closure in a protected staff log.

This template is an operating aid, not legal advice. Hospital, ambulatory, payer, accreditation, state, federal, and contract rules can define complaints and grievances differently. Have counsel and the practice's compliance, privacy, clinical, and patient-relations owners approve the local process.

## Copyable patient-facing form

```text
PATIENT CONCERN OR GRIEVANCE

Today's date: ____________________________________________
Patient name: ____________________________________________
Person submitting, if different: _________________________
Relationship or authority to speak for patient: __________

SAFE RESPONSE
Preferred method: phone / mail / portal / email / other
Safe phone or address: ___________________________________
May we leave a message? yes / no
Language or accessibility support requested: _____________

WHAT HAPPENED
Date and approximate time: _______________________________
Location, department, or visit: __________________________
People involved, if known: _______________________________

Please describe the concern in your own words:
__________________________________________________________
__________________________________________________________

Supporting material you want reviewed: ___________________
What response or resolution would you like? ______________

Signature, if required by local policy: __________________
Best time to contact you: _________________________________

FOR INTAKE ONLY
Received date, channel, and staff member: _________________
Reference number: ________________________________________
```

Don't ask the patient to choose a legal category. "HIPAA violation," "malpractice," and "billing fraud" are conclusions staff may need to review. The form's job is to preserve what happened, where, when, who was involved, and what response the person wants.

## The four-lane intake card

One concern can need more than one route. A scheduling complaint may also reveal an unreviewed clinical message. A billing dispute may include a privacy allegation. Mark every applicable lane and appoint one coordinator so the patient isn't sent around the building.

| Lane | Intake signal | Immediate owner | Intake action |
|---|---|---|---|
| Safety or clinical follow-up | New symptom, missed result, medication concern, abuse allegation, or immediate danger | Licensed clinical lead or emergency route | Separate urgent care from later grievance review |
| Privacy or records | Wrong recipient, access concern, disclosure, amendment, or records delay | Privacy officer or records lead | Preserve the allegation and relevant access evidence |
| Billing or coverage | Charge, estimate, claim, payment, or insurer dispute | Billing lead | Keep the service concern visible if one also exists |
| Service or conduct | Communication, delay, access, accommodation, staff conduct, or environment | Practice manager or patient-relations owner | Acknowledge and assign an investigator |

The intake person doesn't decide whether an allegation is true. They protect the route, preserve evidence, and get urgent care needs to the right person now.

## Hospitals have a specific federal rule

The Medicare Conditions of Participation require a hospital to establish a grievance process, tell patients whom to contact, review and resolve grievances, and provide a written notice with named elements. The regulation also addresses verbal and written grievances and governing-body oversight ([42 CFR 482.13](https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-G/part-482/subpart-B/section-482.13)).

That hospital rule is not a universal script for every independent office. A medical practice may face different requirements from state law, health-plan contracts, professional rules, accreditation, or its own policy. Use the federal hospital rule only when it applies. For everyone else, it is a useful warning against copying a hospital deadline or definition without checking authority.

## The staff log is a different document

The patient-facing form should be easy to complete. The staff log needs enough structure to prove that someone owned the concern.

```text
GRIEVANCE WORK RECORD

Reference number: ________________________________________
Received date and channel: _______________________________
Safe-contact restriction copied from form: ______________
Routes opened: safety / privacy / billing / service / other
Urgent action and owner: __________________________________
Acknowledgement date and method: __________________________
Investigator: _____________________________________________
Questions to resolve: _____________________________________
Evidence locations: _______________________________________
Decision owner: ___________________________________________
Response requirement and source: __________________________
Response date and method: _________________________________
Corrective action owner and due date: _____________________
Closure evidence: _________________________________________
```

Don't put a diagnosis, a full visit narrative, or copied chart pages into this log unless the approved process requires them. Link to protected evidence. Access to a service-recovery complaint doesn't automatically justify access to the patient's whole chart.

## Write the acknowledgement before the conclusion

An acknowledgement says the concern was received, who owns the next contact, and how to share urgent new information. It doesn't promise a result. If clinical follow-up is needed, keep it separate from the investigation so a patient isn't waiting for committee review before getting care instructions.

The final response should follow the rule and policy that apply to the organization. Hospital requirements name specific written-notice elements in [42 CFR 482.13](https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-G/part-482/subpart-B/section-482.13). An independent office shouldn't claim those are its federal obligations without confirming scope.

Where a person wants to complain to a federal civil-rights or health-information-privacy regulator, the HHS Office for Civil Rights publishes its own [complaint routes](https://www.hhs.gov/ocr/complaints/index.html). Don't obstruct that choice or imply the internal form replaces an external right.

## Test the process with six awkward cases

Use fictional data and ask the intake team to route these without improvising:

1. A patient requests a call but says voicemail isn't safe.
2. A family member submits the form and authority is unclear.
3. A complaint about rudeness also reports a new medication reaction.
4. A billing concern says records were sent to the wrong insurer.
5. A person needs an interpreter and cannot use the web form.
6. An anonymous note names a staff member but gives no date.

Score the process on safe contact, urgent escalation, authority check, route, evidence preservation, acknowledgement, and ownership. Don't score whether staff made the complaint disappear quickly.

## Communication after harm needs its own protocol

A grievance form is not an adverse-event investigation or disclosure plan. The Agency for Healthcare Research and Quality's CANDOR toolkit treats event reporting, investigation, communication, resolution, and learning as a connected organizational process ([AHRQ CANDOR](https://www.ahrq.gov/patient-safety/settings/hospital/candor/index.html)). Organizations using that approach need trained leaders and approved procedures beyond a generic form.

When a grievance alleges harm, preserve the person's words and activate the relevant safety process. Don't let the service-recovery queue become the only record of a clinical event.

## Software can route; people still decide

A practice system can assign a reference number, restrict access, preserve dates, send an acknowledgement, and remind an owner that a response is due. It cannot decide whether the practice violated a rule, whether a clinical explanation is sufficient, or what corrective action is fair.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square doesn't claim a grievance-management module. If you're evaluating the platform, test only the documented [Practice Copilot scope](../../products/practice-copilot/) and compare the [security posture](../../security/) with your access and evidence requirements. The [medical records release workflow](../medical-records-release-form-workflow/) and [medical chart audit checklist](../medical-chart-audit-checklist/) cover two routes that may branch from a grievance.

The form opens the door. The log proves somebody walked through it.

---

## Wound Care Documentation Template for Consistent Notes
https://patientsquare.com/us/blog/wound-care-documentation-template/
Published 2026-10-15 · Tags: wound-care, documentation, clinical-notes, template

Use a wound-note template that keeps measurements, tissue description, procedure details, response, ownership, and the next comparison in one record.

A wound care note should make the current wound, today's work, and the next comparison traceable. Capture location, measurement method, dimensions, tissue and surrounding-skin observations, drainage, pain, procedure details when performed, patient response, plan, follow-up owner, and the clinician's signature.

The first note says 2.0 × 1.5 × 0.3 cm. The follow-up says "smaller." A third note calls the wound stable but gives no method, location marker, or prior value. Three encounters later, nobody can reproduce the trend.

> **Key takeaways**
> - Use one approved measurement method and carry the wound identifier forward.
> - Separate observation, procedure, response, and plan. They answer different questions.
> - A template should prompt the clinician, never stage a wound or choose treatment.
> - Test continuity across two visits, not just completeness inside one note.
> - Record an owner and next comparison so follow-up doesn't depend on memory.

This is a documentation template, not a wound-assessment, treatment, coding, or coverage protocol. Licensed clinicians and the organization's wound, compliance, and billing leads should adapt it to the care setting, scope of practice, payer, and local policy.

## Copyable wound note

```text
WOUND CARE ENCOUNTER

Encounter date and time: _________________________________
Clinician and role: ______________________________________
Reason for visit: ________________________________________

WOUND IDENTIFIER
Stable wound ID: _________________________________________
Anatomical location and side: ____________________________
New / follow-up / postoperative / other: _________________

CURRENT OBSERVATIONS
Measurement method and patient position: _________________
Length: ______  Width: ______  Depth: ______  Unit: ______
Tunneling or undermining, if assessed: ___________________
Wound-bed observation: __________________________________
Edges and surrounding skin: ______________________________
Drainage amount and character: ___________________________
Odor, if assessed and after cleansing status: ___________
Pain or other reported symptoms: _________________________
Photo obtained under approved policy: yes / no / not used

TODAY'S WORK
Care or procedure performed: _____________________________
Procedure location, instrument, tissue, depth, and area: __
Materials or dressing documented under local protocol: ___
Patient response: ________________________________________

ASSESSMENT AND NEXT STEP
Clinical assessment: _____________________________________
Change from comparable prior measure: ____________________
Plan and responsible clinician: __________________________
Escalation or referral, if ordered: ______________________
Next review date or trigger: ______________________________
Signature and timestamp: _________________________________
```

The blank areas are intentional. A prompt should make missing information visible without manufacturing it. If a field isn't assessed or doesn't apply, use the organization's approved notation instead of copying yesterday's value.

## Give each wound a durable identity

"Left foot wound" breaks as soon as a second lesion appears. Use a stable identifier tied to an exact anatomical location and side. Keep it the same across visits, photographs, procedures, orders, and messages.

For two wounds, produce two observation blocks. Don't combine dimensions or tissue descriptions into one paragraph. If a procedure covers multiple wounds, the procedure note should still let a reviewer understand what area and depth were treated under the applicable coding and coverage rules.

The original artifact here is a continuity grid. It catches the common situation where each note looks complete by itself but the sequence can't be followed.

| Continuity question | Visit 1 evidence | Visit 2 evidence | Pass condition |
|---|---|---|---|
| Same wound? | Stable ID and location | Same ID and location | No ambiguous merge or split |
| Comparable measure? | Method, position, units | Same method or explained change | Trend can be reproduced |
| What changed? | Baseline observations | Current observations and comparison | Change isn't reduced to "better" |
| What happened? | Care or procedure record | Current work and response | Actions remain encounter-specific |
| What comes next? | Owner and target | Closure or revised plan | No unowned follow-up |

## Measurements need a method

CMS's negative-pressure wound therapy compliance page calls for quantitative measurements of length, width, depth, and drainage in the records used to support that benefit ([CMS NPWT compliance tips](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/negative-pressure-wound-therapy)). That requirement is service-specific, but the documentation lesson travels: numbers without a repeatable method make a weak comparison.

Record patient position, units, and the organization's chosen measurement convention. If edema, debridement, device removal, or another condition makes today's number non-comparable, say why. Don't smooth the series by changing an old value.

Words matter too. "Moderate drainage" needs the approved local scale. "Worse" needs the actual finding. "No change" needs a comparable prior observation. The template should point staff to the approved definitions, not invent a second terminology inside the note.

## Observation isn't a procedure note

A wound assessment records what the clinician observed. A procedure note records what the clinician did. Mixing them makes it difficult to establish which tissue was present, which tissue was removed, and what the wound looked like afterward.

Current CMS contractor coding guidance for wound care says the reported debridement depth follows the tissue actually removed, not the full depth or grade of the wound. It also addresses how treated surface area is measured when the entire wound or only part of it is debrided ([CMS article A55818, version 26](https://www.cms.gov/medicare-coverage-database/view/article.aspx?articleid=55818&ver=26)). The article applies to named jurisdictions and services, so check the rule that controls the actual encounter before relying on any template.

## A safe AI boundary

An AI scribe can draft a wound note from facts the clinician says during the encounter. It cannot see the wound, validate a measurement, infer an unspoken tissue type, decide that a wound is infected, stage it, choose treatment, or select a final code. The clinician reviews the draft against the encounter and signs only what is accurate.

Use a red-line test before adopting any drafting tool:

| Test phrase | Acceptable draft behavior | Reject behavior |
|---|---|---|
| "Left heel, two by one centimeters" | Records the stated site and dimensions | Adds a depth that wasn't spoken |
| "Drainage is unchanged" | Preserves the clinician's statement | Labels an infection |
| "Sharp debridement to subcutaneous tissue" | Drafts the narrated procedure for review | Chooses a code or expands the treated area |
| "Photo not taken" | Records that fact if relevant to the template | Claims an image was reviewed |

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

## Run a two-visit acceptance test

Use fictional data. Start with two nearby wounds, record different measurements, and dictate one procedure on only one wound. At the follow-up, change one dimension, leave the other stable, and add a new symptom. Ask a reviewer who didn't see the scenario to reconstruct the sequence.

Fail the template if the reviewer can't answer all five questions:

1. Which wound is which?
2. Were the measurements comparable?
3. What changed?
4. What did the clinician do today?
5. Who owns the next action?

Then test the same facts through your current documentation method and any proposed tool. The better workflow is the one that preserves the clinician's observations with less cleanup, not the one that produces the longest note.

For adjacent checks, use the [medical chart audit worksheet](../medical-chart-audit-checklist/) and the [AI scribe quality rubric](../ai-scribe-soap-note-quality/). Review [Practice Copilot](../../products/practice-copilot/) and the [security page](../../security/) before putting any real patient information into a trial environment.

A wound note is a chain. Make every link inspectable.

---

## AI Scribe for Allergy and Immunology: A Pilot Test
https://patientsquare.com/us/blog/ai-scribe-for-allergy-immunology/
Published 2026-10-14 · Tags: allergy-immunology, ai-medical-scribe, clinical-documentation, specialty-practice

Test an allergy and immunology AI scribe on source attribution, test-result boundaries, immunotherapy records, corrections, and clinician review.

An allergy and immunology AI scribe should draft the history and clinician-spoken assessment without turning a patient report, skin-test form, spirometry output, outside laboratory result, or immunotherapy administration record into a finding it generated. Test source labels, dates, reaction history, allergen names, dose references, corrections, and blank-field behavior. The clinician still interprets results, selects treatment, reviews the note, and signs it.

An allergy note can contain four versions of the same word: the patient's reported trigger, a product label, a test panel entry, and the allergist's interpretation. Smooth prose can erase those boundaries in one sentence.

Test an AI scribe on provenance before testing speed. Every result, reaction, dose reference, and outside record needs a source the reviewer can see.

## Give every fact a source label

Use a small trace table during the pilot.

| Draft element | Allowed source | Review question |
|---|---|---|
| Suspected trigger | Patient or caregiver report | Is uncertainty preserved? |
| Prior reaction | Patient report or named record | Are date, setting, and source clear? |
| Skin-test result | Authorised test form plus clinician statement | Did the scribe copy rather than interpret? |
| Spirometry or laboratory value | Named device report or outside result | Are source and date present? |
| Assessment | Clinician-spoken judgment | Did a source result become a diagnosis on its own? |
| Plan | Clinician decision | Are orders and future actions still drafts for review? |

The [AAAAI skin-testing resource](https://www.aaaai.org/practice-management/practice-tools/immunotherapy-forms/allergy-skin-testing-forms) includes documentation guidance, report forms, a completed example, and patient instruction and consent forms. That is a useful reminder: structured test documentation already has a job. An ambient note should not pretend to replace it.

## Separate three documentation surfaces

An allergy practice may use a narrative visit note, a structured test form, and an administration record. Their contents overlap, but their controls differ.

The visit note can explain why the patient came, what history was discussed, what the clinician observed, and what the clinician decided. The test form records the approved test procedure and result fields. The administration record belongs to the clinic's approved immunotherapy workflow.

Ask the vendor to demonstrate how the note points to a source without cloning every field. If the test result changes after quality review, the narrative should not silently keep an obsolete value. If the scribe never received the source, it should leave the field blank or mark it for review.

## Run the homonym and negation test

Allergy visits are full of names that sound alike, brand names, compound ingredients, abbreviations, and family recollections. Build a synthetic transcript with controlled traps:

- two allergens with similar names;
- "no wheeze today" next to a history of wheeze;
- a caregiver report that the patient does not confirm;
- a suspected drug reaction with an unknown date;
- an outside lab result discussed without the report in hand;
- one corrected dose or concentration reference.

The draft should keep negation, timing, and attribution. It should not turn "mother recalls" into an observed finding, "possible" into confirmed, or "outside result discussed" into a result the system reviewed.

Shorter is often better. A blank source field is easier to catch than a fluent invention.

## Keep skin testing outside the scribe's judgment

AAAAI publishes [practice parameters and statements](https://www.aaaai.org/allergist-resources/statements-practice-parameters) for clinicians and notes that these resources support clinical assessment and treatment. An AI scribe does not perform a test, judge quality, measure a wheal, choose a panel, or interpret a result.

During a pilot, hand the clinician an authorised synthetic test form and have them state selected findings aloud. Check whether the scribe:

1. names the source form and date;
2. records only the spoken or provided facts;
3. preserves units and qualifiers;
4. avoids filling unmentioned controls or results;
5. keeps the clinician's interpretation separate.

Repeat the test with a corrected form. The reviewer must be able to find which value changed and why.

## Do not rebuild an immunotherapy log from conversation

An administration workflow can carry vial or extract references, dose, route, site, time, observation, reaction, staff identity, and follow-up under the clinic's policy. The exact fields belong to the practice and applicable guidance.

The ambient note may say that immunotherapy was discussed or administered when an authorised user states that fact. It should not invent a dose, infer an observation period, or copy the last visit forward. If the structured administration record is missing, the scribe cannot repair the event with prose.

Run a mismatch drill. Put one dose reference in the synthetic conversation and a different one in the test administration fixture. A safe system surfaces the contradiction. It does not pick the value that sounds more plausible.

## Test the handoff around urgent statements

Include a synthetic statement about breathing difficulty or another potentially urgent concern. The scribe's role is still documentation. The practice's clinical protocol, qualified staff, and emergency workflow govern response.

Ask where a flagged phrase goes, who sees it, what happens when routing fails, and whether staff might mistake an alert for completed clinical action. A note generated after the encounter cannot prove that somebody responded during it.

## Choose the surrounding record separately

An allergy practice may need test scheduling, extract or vial management, inventory, device data, consent, administration records, recalls, billing, and registries. A good scribe demo proves note behavior. It does not prove those other capabilities.

Create a requirements sheet with three columns: Patient Square, existing allergy system, and human workflow. For every handoff, name the source of truth, permitted direction, failure owner, and exit format.

HHS distinguishes covered entities and business associates in its [HIPAA guidance](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html). Map each vendor's role, data path, access, retention, and contract before real patient use.

## Product boundary

Patient Square's AI Medical Scribe drafts clinical documentation for clinician review. It does not perform allergy testing, interpret laboratory or device results, select allergens, prescribe treatment, manage extracts, or replace clinician sign-off. ICD-10 output remains suggestions. Prescription content remains a draft.

Use the [current US plan page](../../pricing/) to verify what is offered. In a demo, bring one synthetic allergy case with conflicting sources and one correction. The best result is not the prettiest note. It is the note whose provenance survives review.

---

## Medical Records Release Form: A Routing Template
https://patientsquare.com/us/blog/medical-records-release-form-workflow/
Published 2026-10-14 · Tags: medical-records, release-of-information, hipaa, workflow

Separate patient access from third-party authorization, then route, verify, fulfill, and close each medical-record request with an evidence log.

A useful medical records release form identifies the patient, recipient, information, purpose, expiration, signature, and any required authorization statements. Before using it, determine whether the patient is exercising the HIPAA right of access or authorizing a separate disclosure. Those are different routes.

A fax arrives at 4:42 p.m. It asks for "the complete chart," names a law office, carries the patient's signature, and gives no expiration date. Calling it a records request doesn't tell the release clerk which legal path applies. The first job is routing.

> **Key takeaways**
> - Separate a patient's access request from an authorization for another disclosure before checking fields.
> - A usable authorization names the information, sender, recipient, purpose, expiration, and signer.
> - Preserve the received date when something is missing. Don't make the request disappear into a new queue.
> - Close the job with delivery evidence and an exception log, not a green checkbox alone.

This template is an operating aid, not legal advice. Federal and state law, substance-use records, minors' records, psychotherapy notes, subpoenas, and other special cases can change the route. Have privacy counsel or the practice's privacy officer approve the local version.

## Route before you validate the form

The U.S. Department of Health and Human Services treats a patient's HIPAA right-of-access request differently from an authorization. HHS warns that requiring a person to execute a HIPAA authorization for an access request can create an impermissible obstacle. A covered entity may use an access form and take reasonable identity-verification steps, but neither may become an unreasonable barrier or delay ([HHS right-of-access guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html)).

An authorization has another job. It permits a use or disclosure that HIPAA does not otherwise permit. HHS describes it as a detailed document with specific core elements and required statements ([HHS consent and authorization FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/what-is-the-difference-between-consent-and-authorization/index.html)).

Use a three-lane intake decision:

| Lane | First question | Working record |
|---|---|---|
| Patient access | Is the patient requesting their own information or directing a copy? | Access request and fulfillment log |
| Authorization | Is the patient permitting another use or disclosure? | Valid authorization plus disclosure log |
| Other authority | Is the request based on a court order, legal mandate, public-health route, or another permission? | Escalation record tied to the controlling authority |

Don't ask the front desk to make the hard legal call. Ask staff to capture facts, choose the apparent lane, and escalate exceptions to the privacy owner.

## Copyable authorization intake sheet

The core elements below track the authorization requirements summarized by HHS and codified in [45 CFR 164.508](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.508). It is a validation sheet for an approved form, not a universal form for every jurisdiction.

```text
MEDICAL RECORDS DISCLOSURE INTAKE

Received date and channel: ______________________________
Patient name and second identifier: _____________________
Description of information: _____________________________
Date range or encounter range: __________________________
Person or class permitted to disclose: __________________
Recipient or recipient class: ___________________________
Purpose of disclosure: __________________________________
Expiration date or event: _______________________________
Signature: _______________________  Date: _______________
Authority if signed by a representative: _______________

REQUIRED-STATEMENT CHECK
Right to revoke and how to revoke:        present / absent
Treatment, payment, or benefit condition: present / absent
Redisclosure warning:                     present / absent

ROUTING
Access request / authorization / other / privacy review
Owner: ____________________  Target date: _________________
Missing item or exception: ______________________________
```

The HHS authorization summary lists the information, discloser, recipient, purpose, expiration, signature, and date as core elements. It also identifies statements about revocation, conditioning, and possible redisclosure ([HHS authorization guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/emergency-preparedness/authorization/index.html)). The local form should present those statements clearly enough for a person to understand what they are signing.

## Scope needs nouns and dates

"Send the chart" sounds plain until the chart contains ten years of visits, outside reports, imaging, billing records, and material governed by a separate rule. Ask what information, which dates, which recipient, and which purpose the requester intends.

HHS says an authorization that specifies the "entire medical record" can be specific enough, but "all protected health information" may not describe the information with enough specificity ([HHS entire-record FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/may-a-covered-entity-use-or-disclose-a-patients-entire-medical-record-based-on-the-patients-authorized-signature/index.html)). That distinction is useful for form design. Offer understandable record categories without steering the patient away from a scope they are entitled to request.

When the scope is unclear, send one concrete question. For example: "Should this include billing records and outside records, or clinical records created by this practice only?" Record the answer next to the original request.

## The exception log keeps work honest

A release queue fails quietly. One request waits for representative paperwork, one contains a mismatched date of birth, and another needs privacy review. A single status labeled "pending" conceals all three.

Use a log with explicit states:

| State | Evidence to retain | Next owner |
|---|---|---|
| Received | Original request, channel, timestamp | Intake staff |
| Identity or authority check | Method and result, without unnecessary document copies | Records team |
| Scope clarification | Question, response, and revised scope | Requester liaison |
| Privacy review | Exact exception and decision | Privacy officer or counsel |
| Production | Record set, exclusions, and quality check | Release specialist |
| Delivery | Recipient, method, timestamp, and confirmation | Release specialist |
| Closed | Completion or denial notice and reason | Queue owner |

Keep dates visible. Preserve the first received date even if the request needs clarification. If a deadline pauses or changes under an applicable rule, have the privacy owner record the basis rather than letting software infer it.

## Test the route with four awkward requests

A blank form doesn't prove the process works. Run these fictional requests through a training queue:

1. A patient asks for a PDF copy of the last two visits and uses a nickname that differs from registration.
2. A parent requests a teenager's complete record, but the chart contains a service that may follow a different authority rule.
3. A signed authorization names a lawyer and the whole record but has no expiration date or event.
4. A patient directs the practice to send a copy to another clinician and staff mistakenly demand the practice's authorization form.

For each one, record the lane, missing fact, person allowed to decide, response to the requester, and closure evidence. The test passes only if two trained staff members reach the same route from the written policy.

## Where software helps, and where it doesn't

A records system can keep one request, one owner, dates, tasks, and delivery evidence together. It can't decide a contested authority question or invent a valid authorization field. Those decisions belong to the practice's approved policy and privacy reviewer.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

If your release queue exposes a broader records problem, compare the [medical chart audit checklist](../medical-chart-audit-checklist/) with the [record-amendment routing guide](../medical-record-amendment-request/). Then review [Practice Copilot](../../products/practice-copilot/) and the current [security posture](../../security/) against your own acceptance test.

The best release form won't rescue a hidden queue. Route the request, name the exception, prove the delivery, and close the loop.

---

## Medical Records Retention Policy for Indian Hospitals
https://patientsquare.com/in/blog/medical-records-retention-policy-india/
Published 2026-10-14 · Tags: medical-records, retention-policy, hospital-governance, india

Build an India medical-records retention schedule by record class, source authority, trigger, legal hold, storage format, disposal, and proof.

An Indian hospital should not use one retention period for every record. Build a schedule by record class, applicable central and state source, facility or programme rule, start event, minimum period, longer hold condition, storage format, access owner, and approved disposal. Include medico-legal holds, minors, research, transplant, employment, billing, imaging, and system logs where they apply. Qualified legal, medical-records, privacy, and clinical owners must approve the schedule.

"Keep everything forever" is not a retention policy. Neither is "delete after three years." A hospital holds case sheets, medico-legal files, images, registers, billing records, consent artefacts, staff records, device logs, quality workpapers, and backups. Their clocks do not all start or stop together.

Build a source-backed schedule by record class. Then prove that systems can hold, retrieve, export, freeze, and dispose of each class under control.

## Start with an authority register

For every schedule row, record the source that controls it.

```text
MEDICAL RECORDS RETENTION AUTHORITY REGISTER

Record class: ____________________________________________
Facility, department, and location: ______________________

Central source: __________________________________________
State or local source: ___________________________________
Professional or programme source: ________________________
Court order, contract, research, or payer source: ________

Start event for the clock: _______________________________
Minimum retention: _______________________________________
Longer-period trigger: ___________________________________
Legal-hold or complaint trigger: _________________________

Physical, digital, or hybrid format: _____________________
System of record and backup: _____________________________
Access owner: ____________________________________________
Disposal approver and method: ____________________________

Source checked on: ______________ Next review: ___________
Approved by legal: ______________ MRD: ___________________
Privacy: ________________________ Clinical owner: _________
```

Do not populate the period from memory. Attach the official source, edition or date, scope, and hospital interpretation.

## Use government schedules as sources, not universal shortcuts

The 2025 DGHS [Hospital Manual](https://dghs.mohfw.gov.in/uploads/assets/b9gSYbHAzy9pIrF74o1Aw7bvw91KW9Axd5wrlqPd.pdf) lists physical in-patient case records and OPD records or registers at three years, and medico-legal case records and registers at ten years or until disposal of the related court case. It describes digital records as capable of indefinite storage under policy and updated guidance.

The lesson is not "three years." It is that record type and governing source matter. A facility may face a longer period from state law, a court matter, a programme, professional duty, research requirement, patient age, transplant rule, insurance or contract, or its approved risk decision.

## Build the schedule around classes and triggers

| Record class | Start event to define | Longer-hold questions |
|---|---|---|
| OPD register or visit record | Last entry, visit, or closure under source | Complaint, minor, continuing care, state rule |
| In-patient case record | Discharge, closure, or last entry | Litigation, programme, transplant, research |
| Medico-legal record | Source-defined event | Court disposal and legal hold |
| Imaging and reports | Study, report, or episode closure | Linked case, specialty rule, storage source |
| Consent and notice evidence | Event or withdrawal | Linked procedure, claim, complaint, proof need |
| Billing and claim record | Financial close or claim event | Tax, payer, dispute, audit |
| System audit and access logs | Event or system period | Security investigation, contract, incident |
| Quality and incident record | Case closure | Accreditation, legal privilege, investigation |
| Research record | Study milestone | Protocol, sponsor, ethics, regulator |
| Backup copy | Backup generation or rotation | Legal hold and source-record recovery need |

The start event is as important as the number. "Five years" cannot run if nobody knows whether the clock begins at admission, discharge, last visit, closure, adulthood, final claim, or final court action.

## Add legal holds before adding deletion

A legal hold pauses normal disposal for defined records. Build the hold route before turning on any automated retention job.

Record the hold authority, scope, identifiers, record classes, systems, custodians, start time, preservation actions, acknowledgements, changes, and release approval. Include paper stores, local drives, email, scanned documents, exports, and backups where they are in scope.

The VMMC and Safdarjung Hospital [official retention schedule](https://vmmc-sjh.mohfw.gov.in/retention-schedule-respect-records-pertaining-safdarjang-hospital) says a record needed to dispose of another record should not be weeded out until the related issues are finally decided, even if its marked period has expired. That is a practical dependency rule: one file's clock cannot ignore the case it supports.

## Digitisation needs an acceptance test

Scanning paper does not by itself prove completeness, integrity, legibility, or lawful disposal of the original.

Test a batch with:

- page count before and after capture;
- patient and encounter matching;
- front and back where information exists;
- colour or resolution requirements;
- signatures, stamps, annotations, and attachments;
- missing-page and duplicate-page handling;
- search and retrieval by authorised staff;
- immutable or attributable correction history;
- checksum or other integrity control where used;
- approved treatment of the original.

Sample difficult files: foldouts, thermal paper, faint ink, multilingual notes, loose reports, and two patients with similar identifiers. A "scan complete" flag is worthless if nobody can read page four.

## Reconcile privacy duties with record duties

The [DPDP Act, 2023](https://www.indiacode.nic.in/indiacode/handle/123456789/22037?view_type=browse) governs digital personal-data processing within its scope and commencement framework. The hospital must map privacy duties alongside laws and obligations that require medical records to remain.

Do not promise a patient that every clinical record will be erased on request. Do not use retention law as a reason to keep optional marketing lists forever. Classify the data, purpose, lawful route, record duty, and system copy. Privacy and legal owners must resolve the overlap.

This is also why a deactivated user account, a deleted appointment, and a destroyed medical record cannot share one button.

## Dispose with proof

When the approved period has ended and no hold or longer duty applies, create a disposal batch. It should list record class, date range, authority, review result, approvers, method, vendor or witness where used, completion date, exceptions, and certificate or log.

For digital systems, define deletion from the active store, search index, replicas, exports, and backups under the approved architecture. A backup may age out through rotation rather than immediate selective deletion. State that honestly.

Run a pre-destruction sample. Confirm that no record in the batch belongs to the wrong class, a minor or ongoing episode, an open complaint, a linked medico-legal matter, a research hold, or another exception.

## Make vendor exit part of retention

Before signing a system contract, test whether the hospital can export a complete, readable record with metadata and history. Record the format, attachments, audit trail, terminology, identifiers, access controls, cost, time, and assistance needed.

Ask what happens to active records, archived records, logs, and backups when the contract ends. Ask how holds survive termination. Ask for deletion evidence only after the hospital has accepted the export and approved the exit.

A platform that stores a record but cannot return it in usable form has changed the retention problem into a captivity problem.

## Product boundary

Patient Square is an AI clinical platform, not a legal archive opinion. It does not choose a hospital's retention period, issue a legal hold, approve destruction, or certify that a scanned record can replace an original.

Verify the [current India security posture](../../security/), product scope, export, access, backup, correction, deletion, and exit behavior. Patient Square does not claim ABDM certification. The hospital's qualified legal, medical-records, privacy, and clinical owners must approve the schedule and test it against real systems.

---

## Switching HMS in India: A Practical Migration Plan
https://patientsquare.com/in/blog/switching-hms-what-to-expect-india/
Published 2026-10-14 · Updated 2026-09-24 · Tags: hospital-management-system, hms-migration, hospital-software, india, buyer-guide

A hospital management system migration guide for Indian hospitals: data scope, rehearsals, cutover, ownership, and exit checks.

There is no dependable universal duration. It depends on data volume, source quality, integrations, departmental scope, and the number of rehearsal cycles. Ask vendors for a milestone plan with entry and exit criteria instead of accepting a date without assumptions.

An HMS migration does not begin when a vendor imports a database. It begins when the hospital decides what must still work at 9:00 on the first morning after cutover.

Registration must find the right patient. The ward must see current admissions. Billing must carry the correct balances. Pharmacy and stores need trustworthy stock. Clinicians need the records required for safe continuity of care. Those are separate acceptance tests, not one technical milestone called "data migrated."

This guide turns an HMS switch into a controlled hospital programme. It does not prescribe a fixed timeline because source systems, data quality, integrations, and facility scope differ.

## Start with a migration charter, not a feature list

Write one page before anyone maps a field. It should name the executive owner, clinical safety owner, privacy owner, finance owner, technical lead, and vendor lead. It should also state:

- which facilities and departments are in scope;
- which system is authoritative before, during, and after cutover;
- which workflows cannot tolerate an outage;
- what success looks like for patient identity, clinical access, billing, and inventory;
- who can approve cutover, pause it, or order a rollback.

The National Informatics Centre's eHospital service illustrates why module boundaries matter. Its official service describes functions including patient registration, admissions, billing, pharmacy, laboratory, and blood bank. A hospital may use a different product and module set, but the migration still has to follow the real departmental handoffs rather than a vendor's umbrella label.

## Build a data decision register

"Move everything" sounds safe. It usually hides hard choices. A better register assigns every data group one of three outcomes: migrate into the live system, retain in an accessible archive, or dispose of it only under an approved retention and legal process.

| Data group | Questions to settle before extraction | Practical acceptance evidence |
|---|---|---|
| Patient identity | How are duplicates, aliases, old identifiers, and deceased patients handled? | Sample matches reviewed; duplicate rules signed off |
| Encounters and clinical records | Which notes, diagnoses, allergies, orders, results, and documents remain clinically necessary? | Clinician can trace a selected patient journey |
| Admissions and beds | Which current admissions and transfers must be live at cutover? | Ward census reconciles to the source |
| Billing and receivables | Which open balances, deposits, refunds, and payer references move? | Finance totals and patient-level samples reconcile |
| Pharmacy and inventory | Which item masters, batches, expiries, and opening stock are authoritative? | Store totals and selected batches match physical checks |
| Users and permissions | Who needs access, at which facility, and with which role? | Joiner, mover, leaver, and privileged-access tests pass |
| Audit and consent records | What must remain searchable, attributable, and exportable? | Retrieval test succeeds with timestamps and actor context |

Keep the register versioned. If the decision for an old document changes from "archive" to "migrate," the change should name an owner and a reason.

## Clean identity before moving history

Patient matching is not a cosmetic cleanup. A duplicate can split a clinical history; a false merge can place one person's information in another person's record.

Profile the source first. Count empty identifiers, duplicate mobile numbers, reused local IDs, malformed dates, and records that disagree across systems. Then define deterministic matching rules and a queue for human review. Do not let a vendor silently resolve uncertain matches through a broad fuzzy rule.

Use synthetic or properly controlled test data during early rehearsals. When personal data is used, apply the hospital's approved access, purpose, retention, and security controls. The Digital Personal Data Protection Act, 2023 establishes duties around processing digital personal data; it does not turn a software purchase into automatic compliance. Hospitals should obtain legal and privacy guidance for their circumstances.

## Rehearse the migration at least as a full workflow

A technically successful import can still fail at the counter. Rehearsal must include users following work from start to finish.

One useful sequence is:

1. Freeze a source snapshot and record its timestamp.
2. Extract and transform it with logged rules.
3. Load it into a production-like target environment.
4. Reconcile totals, exceptions, and selected patient records.
5. Ask departmental users to complete scripted workflows.
6. Log every defect, assign an owner, and rerun the affected test.
7. Measure the final-delta load that cutover will require.

Test awkward cases on purpose: an inpatient with an outstanding bill, a patient with two old identifiers, a returned pharmacy item, a corrected lab result, and a staff member whose role changed. These cases expose handoff errors that happy-path demonstrations miss.

## Set cutover gates that anyone can read

A go-live meeting needs facts, not confidence. Use a short gate sheet with a named approver for each line.

- Critical data reconciliations are within the hospital's approved tolerance, with every exception documented.
- Current admissions, urgent patient lists, and essential clinical history are available.
- Registration, admission, discharge, billing, pharmacy, and other in-scope workflows pass.
- Interfaces and devices have passed end-to-end tests, or a documented manual fallback exists.
- Role-based access and privileged accounts have been reviewed.
- Backups, restore evidence, downtime forms, escalation contacts, and rollback criteria are ready.
- Staff know which system is authoritative and where to report a problem.

"The database loaded" is evidence for one line of a much larger decision.

## Keep parallel running narrow

Some hospitals compare critical outputs in both systems for a limited period. That can catch mapping problems. It can also produce contradictory balances, duplicate orders, and exhausted staff.

If parallel checks are required, name the authoritative system per workflow and restrict the comparison to defined outputs. For example, finance may reconcile a daily total while clinicians document only in the new record. Set an end date. Once the old HMS becomes read-only, verify that authorised staff can still retrieve retained history.

## Plan rollback around transactions, not servers

A server snapshot is useful, but it does not explain what happens to registrations, payments, orders, or notes created after go-live. The rollback plan should answer four questions:

1. What condition triggers the decision?
2. Who makes it, and by what deadline?
3. How are post-cutover transactions exported and reconciled?
4. How will staff and patients be told which system is authoritative?

Run a tabletop exercise. If the team cannot explain how a payment entered at 10:15 would survive a rollback at 11:00, the plan is incomplete.

## Treat interoperability claims as test cases

ABDM is not a checkbox to inherit from a sales deck. The ABDM Health Data Management Policy describes a consent-oriented framework for health data exchange. A buyer should ask what specific capability exists today, which environment it works in, what evidence can be demonstrated, and which party operates each workflow.

Patient Square's ABDM integration is on the roadmap. We do not present the product as ABDM-certified or as having completed an ABDM milestone. Verify current product status during procurement.

Use the same discipline for every integration. Ask the vendor to demonstrate a real registration, result, billing, or record-retrieval path in the quoted configuration. A logo on a slide is not an acceptance test.

## Demand an exit package before signing

The best time to negotiate the next migration is before this one begins. Put export scope, format, attachments, code sets, audit data, fees, assistance, deletion, and turnaround terms into the contract.

Ask for a sample export and have someone other than the vendor open it. A large file is not necessarily a usable record. The hospital should be able to identify a patient, reconstruct important history, and reconcile balances without a proprietary viewer that disappears with the contract.

## A practical first conversation

Bring three artefacts to the vendor: the migration charter, the data decision register, and ten workflow tests. Ask the vendor to mark what is standard, configurable, custom, or unsupported. Then price the gaps and attach responsibilities to the statement of work.

Patient Square Hospital Copilot can be evaluated in either of two configurations: alongside an incumbent hospital system, or, where the quoted scope fits, with the complete Patient Square HIS/EHR. The discovery session should confirm the actual modules, interfaces, data work, and support required. Do not infer unlisted hospital capabilities from the Copilot name.

## Sources

- [National Informatics Centre: eHospital NextGen](https://nextgen.ehospital.gov.in/)
- [India Code: Digital Personal Data Protection Act, 2023](https://www.indiacode.nic.in/bitstream/123456789/22037/2/a2023-22.pdf)
- [Ayushman Bharat Digital Mission: Health Data Management Policy](https://abdm.gov.in/static/media/health_management_policy_bac9429a79.80f74bc3e039c00acd4f.pdf)
- [Patient Square: Hospital Copilot for India](https://patientsquare.com/in/products/hospital-copilot/)

---

## Patient Consent Form for Indian Clinics: Split the Decisions
https://patientsquare.com/in/blog/patient-consent-form-india-clinics/
Published 2026-10-13 · Tags: patient-consent, dpdp, clinic-workflow, india

Design an Indian clinic consent workflow that separates clinical consent, data notice, optional communications, ABDM choices, withdrawal, and proof.

An Indian clinic should not put every decision into one blanket consent line. Separate consent to examination or treatment from the privacy notice, any consent relied on for digital-personal-data processing, optional messaging or marketing, and ABDM or other network-specific choices. Record the text version, purpose, language, patient or representative, affirmative action, date, withdrawal route, and downstream action. Qualified clinical, privacy, and legal owners must approve the form for the clinic's setting and state.

One signature cannot explain five decisions. Yet clinic forms often place examination, treatment, data use, WhatsApp reminders, marketing, and ABHA linking under a single "I agree" line.

Split the decisions before choosing paper, tablet, or portal. The evidence becomes easier to read, honour, withdraw, and audit.

## Draw the consent map first

| Decision | Example purpose | Approval owner |
|---|---|---|
| Clinical consent | Examination, procedure, treatment, teleconsultation | Clinical and legal leadership |
| Data notice and lawful processing | Registration, care record, billing, required operations | Privacy and legal leadership |
| Optional patient communication | Appointment or follow-up messages through a chosen channel | Privacy and operations |
| Marketing | Promotions unrelated to the immediate care workflow | Privacy and marketing, separately |
| ABDM or other network action | A specific linking, sharing, or network request | Authorised ABDM and privacy owner |

The map prevents a clinic from promising that refusal of an optional message channel means refusal of care. It also stops staff from treating a treatment signature as permanent permission for every future data use.

## Put the notice before the choice

The [Digital Personal Data Protection Act, 2023](https://www.indiacode.nic.in/indiacode/handle/123456789/22037?view_type=browse) creates India's statutory framework for digital personal data. The [DPDP Rules, 2025](https://www.meity.gov.in/documents/act-and-policies/digital-personal-data-protection-rules-2025-gDOxUjMtQWa?pageTitle=Digital-Personal-Data-Protection-Rules-2025) set out the implementation framework, including requirements for notices in clear and plain language with itemised descriptions of personal data and specified purposes.

Do not hide the notice behind a link nobody can open at the desk. Give the patient a readable version in the language and format the clinic has approved. Record which version was shown.

```text
PATIENT DATA NOTICE RECORD

Clinic legal name and contact: ___________________________
Notice version and effective date: _______________________
Language and format presented: ___________________________

Personal data described: ________________________________
Purpose or purposes described: ___________________________
Service or use connected to each purpose: _______________

Rights, grievance, and complaint routes provided: _______
Withdrawal route where consent is relied on: ____________
Retention or source-policy reference: ____________________

Presented by or through: _________________________________
Date and time: ___________________________________________
Evidence location: _______________________________________
```

This record proves what the patient saw. It is not a substitute for the clinical consent or the patient's affirmative choice.

## Use one purpose per optional choice

```text
OPTIONAL PATIENT COMMUNICATION CHOICES

Appointment reminders by approved channel:  Yes / No
Care follow-up messages by approved channel: Yes / No
Patient-selected channel: ________________________________
Marketing or promotional messages:             Yes / No

Each choice can be changed through: ______________________
Changing an optional choice does not alter completed care records.

Patient or representative: _______________________________
Representative authority, if applicable: _________________
Signature or approved affirmative action: _________________
Date and time: ___________________________________________
Form version: ____________________________________________
```

Do not pre-tick boxes. Do not treat a phone number as consent for every message. If the clinic relies on another lawful ground for a required communication, label that route correctly instead of manufacturing consent.

## Keep clinical consent clinical

The Ministry of Health and Family Welfare's [Clinical Establishments standards](https://clinicalestablishments.mohfw.gov.in/sites/default/files/2022-06/776.pdf) include requirements for consent in hospital care settings. The actual consent needed depends on the examination, procedure, treatment, patient, capacity, emergency, facility, profession, and applicable state or central rules.

The treating team must explain the clinical decision under the approved process. Software can display a form and preserve an event. It cannot decide capacity, substitute for the clinician's explanation, or turn a generic signature into informed consent for a specific procedure.

When a representative signs, record the identity, relationship, authority, and reason under the clinic's policy. A parent, guardian, attendant, nominee, and informal caregiver are not interchangeable roles.

## Keep ABDM choices separate

ABHA and ABDM workflows have their own actors, purpose, consent, and technical evidence. Do not claim that a general clinic registration form authorises every future health-information exchange.

Patient Square does not claim ABDM certification or live connectivity. If the clinic uses another certified system for an ABDM action, keep the network evidence with that system and link only the minimum local reference the approved workflow needs.

The clinic should be able to answer: which network action occurred, which record set was involved, who requested it, what consent artefact or lawful route applied, when it occurred, and how the patient can inspect or change future choices where supported.

## Make withdrawal a workflow, not an inbox

When the clinic relies on consent for a purpose, a withdrawal must reach the systems and people using that consent. Record the request, identity check, purpose, time, downstream tasks, completed actions, and patient response.

Withdrawal does not erase clinical facts or records that another law requires the clinic to retain. Nor does it undo processing already completed under the applicable framework. Legal and privacy owners must decide the effect on each purpose and record class.

Test four cases:

1. Patient stops marketing but keeps appointment reminders.
2. Patient changes the phone number used for reminders.
3. Representative authority expires or changes.
4. Patient withdraws an optional data-sharing choice while a mandatory medical record remains under retention.

The system should not answer all four by deleting the patient account.

## Preserve the version and the action

A consent table needs more than `true` or `false`.

| Field | Why it matters |
|---|---|
| Purpose | Shows what the choice covered |
| Text and version | Shows what was presented |
| Language and format | Shows how it was communicated |
| Patient or representative | Shows who acted |
| Authority evidence | Supports representative action |
| Affirmative action and time | Shows how and when the choice was made |
| Source channel | Paper, tablet, portal, or other approved route |
| Withdrawal or change history | Preserves the lifecycle |
| Downstream completion | Shows that systems honoured the change |

Never rewrite an old consent event when the wording changes. Create a new version and keep the old evidence tied to the period when it applied.

## Product boundary

Patient Square can support documentation and configured practice workflows within the confirmed product scope. It does not provide legal advice, decide the lawful basis for data processing, obtain informed clinical consent on the clinician's behalf, judge representative authority, or certify ABDM participation.

Review the [current India security posture](../../security/) and product pages before deployment. Have qualified clinical, privacy, and legal owners approve the consent map, form text, languages, accessibility, system evidence, retention, and withdrawal path.

---

## Insurance Eligibility Verification Checklist for Clinics
https://patientsquare.com/us/blog/insurance-eligibility-verification-checklist/
Published 2026-10-11 · Tags: insurance-eligibility, front-desk, revenue-cycle, checklist

Run insurance eligibility verification as an exception workflow: identity, coverage dates, benefits, referrals, authorization, evidence, and handoff.

Verify the patient's identity and member details, payer and plan, coverage status for the date of service, benefit details relevant to the scheduled service, network information, referral or prior-authorization requirements, coordination-of-benefits questions, and the source and time of the response. Treat the response as time-bound evidence, not a guarantee of payment. Route exceptions to a named owner before the visit.

January creates the obvious pile. Plans reset, cards change, and tomorrow's schedule still looks exactly like December's. The quieter version happens every week: one transposed member ID, one expired referral, one payer response saved with no date.

Eligibility verification works better as an exception queue than as a green check beside every appointment. Capture the evidence once. Put uncertain cases in view. Give each one an owner before the patient reaches the desk.

## Start with a verification workboard

```text
INSURANCE ELIGIBILITY WORKBOARD

Patient and appointment ID: ______________________________
Date and planned service category: _______________________

Member name and ID checked against source: ______________
Date of birth and relationship to subscriber: ___________
Payer and plan: __________________________________________

Inquiry source and reference: ____________________________
Inquiry date and time: ___________________________________
Coverage dates returned: _________________________________
Coverage status for planned date: ________________________

Relevant benefit details returned: _______________________
Network information returned: ____________________________
Referral requirement: ____________________________________
Prior-authorization signal: ______________________________
Coordination-of-benefits question: _______________________

Status: Clear / Needs patient input / Needs payer review /
        Referral or authorization work / Escalated
Owner: __________________________ Due: ____________________
Evidence location: ________________________________________
Patient communication: ___________________________________
```

The workboard records what came back. It does not promise what the payer will do with a future claim.

## Know what the transaction answers

[CMS describes HETS](https://www.cms.gov/data-research/cms-information-technology/hipaa-eligibility-transaction-system/about-hets-270-271) as a system that accepts HIPAA-compliant 270 eligibility requests and returns 271 responses for Medicare. CMS's [270/271 companion guidance](https://www.cms.gov/files/document/mmsea-111-270271-health-care-eligibility-benefit-inquiry-and-response-companion-guide-mandatory.pdf-1) identifies the 270 as the inquiry and the 271 as the response.

Commercial payer portals and clearinghouses may expose the same transaction family through different screens. Save the response or reference permitted by policy, along with the date, planned date of service, and user. A copied sentence in an appointment note is weak evidence because it loses the source and timing.

## Verify identity before interpreting benefits

Many failures begin before coverage. Compare the patient-entered details, card, registration record, and payer response under the practice's identity procedure.

Check:

- spelling and approved identifiers;
- member and group numbers;
- subscriber name and relationship;
- payer and product name;
- old card versus current card;
- effective and termination dates;
- whether another plan may be primary.

Do not merge two patients because their names resemble each other. Do not replace an old insurance record without preserving which claims or appointments used it.

## Read the response for the scheduled work

"Active" is not a complete answer. The response must be read against the date and planned service category.

Look for returned information on network, copay, deductible, coinsurance, limits, referral requirements, or authorization signals that matter to the appointment. The exact response varies. When the data is absent or unclear, say that. Do not manufacture a zero balance or a covered-service promise.

The patient-facing sentence should be careful: the practice verified the information shown by the named source at a named time. Eligibility and benefits are not a guarantee of payment. Final responsibility depends on the claim and applicable plan rules.

## Work exceptions by type

One red queue is noisy. Split it.

| Exception | Next owner | Evidence needed |
|---|---|---|
| Member not found | Registration or patient contact | Card, identifiers, payer confirmation |
| Inactive for planned date | Patient contact and billing review | Coverage dates and alternate plan |
| Network unclear | Contract or payer-review owner | Plan, provider, location, payer response |
| Referral required | Referral desk | Referring provider, order or referral, validity |
| Authorization signal | Authorization team | Planned service, payer rule, submission status |
| Other coverage indicated | Coordination-of-benefits owner | Primary and secondary plan facts |
| Response unavailable | Supervisor or downtime lane | Attempt log and approved fallback |

Do not use a generic "insurance issue" task. It hides the work and makes aging useless.

## Test five cases before trusting automation

Use synthetic accounts and payer training environments where available.

1. Active coverage, no returned exception. Confirm that the evidence is stored and the result expires under policy.
2. Coverage terminates the day before the appointment. Confirm that the workflow compares the date instead of trusting the word "active."
3. Member ID is wrong by one digit. Confirm that the system does not silently attach a different person.
4. Response indicates a referral or authorization issue. Confirm a task reaches the correct owner with the source attached.
5. Payer endpoint is unavailable. Confirm the appointment does not become "verified" because the check failed open.

Then change the appointment date. The prior response should remain in history, while the new date receives a fresh decision under policy.

## Keep eligibility, estimates, and collections apart

Eligibility checks coverage and returned benefits. It does not replace the practice's good-faith-estimate duties for applicable uninsured or self-pay patients, its price-estimate workflow, or payer-specific authorization work. CMS keeps [provider No Surprises Act resources](https://www.cms.gov/initiatives/no-surprise-billing/overview/policies-resources/provider-requirements-resources) in a separate body of guidance for a reason.

Likewise, a coverage problem should not become a collection note before the balance exists. Preserve the sequence: verify, communicate uncertainty, perform approved referral or authorization work, submit the claim if appropriate, receive adjudication, correct errors, and only then manage a patient balance.

## Measure the queue, not a vanity percentage

Track clear results, exceptions, age, resolved-before-visit counts, rescheduled cases, payer downtime, and rework caused by bad identifiers. Sample results back to the source response.

A 99 percent "verified" rate is meaningless if staff mark unavailable responses as clear. The useful measure is how many exceptions reached the correct owner soon enough to act, without an invented benefit quote.

## Product boundary

Patient Square can support practice workflows within the current product scope. This article does not claim automated payer eligibility, benefit interpretation, prior-authorization submission, guaranteed estimates, claim adjudication, or payment collection.

Check the [current US plan scope](../../pricing/) before buying around any workflow. Ask the vendor to demonstrate the exact transaction source, evidence record, exception queue, permissions, failure behavior, and handoff to staff.

---

## AI for Surgeons in India: What Is Ready Now
https://patientsquare.com/in/blog/ai-for-surgeons-india/
Published 2026-10-10 · Tags: ai-for-surgeons, surgical-documentation, india, clinical-ai

A practical green-amber-red map for AI around surgical documentation in India, from clinic and rounds to the hard boundary around operative decisions.

Start with narrow, reviewable work around care: drafting a clinic note from the consultation, structuring a ward-round note, summarising an authorised record, or preparing a postoperative or discharge draft for clinician review. Keep diagnosis, consent, operative decisions, orders, and final signing with qualified people.

At 6:45 p.m., the operating list is finished but the documentation is not. One note needs the exact procedure and findings. Two families need a plain follow-up plan. Tomorrow's clinic already has 14 patients. This is where AI can help a surgeon now: drafting and organising words, under review, outside the operative decision.

> **The working boundary**
>
> - Use AI first where the output is a visible draft tied to an authorised source.
> - Keep consent, diagnosis, operative choices, orders, and final signatures human-owned.
> - Never replace the surgical team's safety pause with a software completion mark.
> - Test Indian language input, English note output, privacy, corrections, and downtime together.

## A green, amber, red map for a surgical unit

| Zone | Example | Minimum control | Verdict |
|---|---|---|---|
| Green | Draft a clinic, ward-round, or follow-up note from a conversation | Surgeon checks every fact before signing | Pilotable |
| Green | Turn the surgeon's dictated facts into a structured draft | Preserve source, author, time, and corrections | Pilotable |
| Amber | Summarise an authorised longitudinal record for review | Link every conclusion back to the source record | Test narrowly |
| Amber | Prepare a postoperative instruction draft | Treating team approves every patient-specific instruction | Test narrowly |
| Red | Infer an operative finding that was not stated | No safe documentation shortcut | Do not deploy |
| Red | Recommend an incision, device, diagnosis, or treatment from the live case | Requires a different validated clinical product and governance case | Outside scribe scope |
| Red | Mark a safety checklist complete because a field is populated | Team confirmation has not occurred | Do not deploy |

The colour belongs to the task, not the brand. A product can be green for clinic-note drafting and red for intraoperative decisions on the same day.

## Before theatre: draft the record, not the consent decision

A preoperative consultation contains history, the surgeon's assessment, discussion of options, and a plan. An ambient scribe can draft the words spoken during that consultation. It cannot decide whether consent is valid, whether the proposed procedure fits the patient, or whether an unstated risk was discussed.

Use a short review card:

- correct patient and encounter;
- history and examination facts actually stated;
- procedure and laterality stated by the surgeon;
- discussion captured without invented assurances;
- medicines and allergies checked against the authorised record;
- questions or uncertainty left visible;
- clinician edits and signature recorded.

The [MoHFW EHR Standards for India, 2016](https://www.mohfw.gov.in/sites/default/files/EMR-EHR_Standards_for_India_as_notified_by_MOHFW_2016_0.pdf) describe an EHR as a collection of records generated through clinical encounters and explain why longitudinal, clinically relevant records matter. They are a standards reference, not proof that any AI draft is complete.

For the narrower specialty-scribe decision, compare the [India cardiology clinic workflow](../ai-scribe-for-cardiology-clinics-india/) and the [medico-legal documentation guide](../ai-scribe-medico-legal-documentation-india/). The surgical boundary is stricter when the missing fact concerns an operation.

## Inside theatre: the team pause stays a team pause

The [WHO Surgical Safety Checklist resources](https://www.who.int/teams/integrated-health-services/patient-safety/research/safe-surgery/tool-and-resources) organise checks around three critical points: before anaesthesia, before incision, and before the patient leaves the operating room. WHO's implementation material centres verbal participation and local adaptation.

Software can show a checklist, record a time, or route an unresolved item under a hospital's approved process. It should not infer that a pause happened because boxes became checked. Nor should an AI scribe decide that the site, procedure, count, specimen label, antibiotic plan, or recovery concern is correct.

If the team finds a discrepancy, the useful system keeps it open and names an owner. A green dashboard that hides an unresolved mismatch is worse than paper.

## After theatre: dictate exact facts, then inspect the draft

An operation-note draft should begin with facts supplied by the surgeon and theatre record. Build the review around what could cause harm if copied incorrectly:

1. procedure and laterality;
2. operative findings;
3. specimens and labels;
4. implants, devices, drains, or counts when applicable;
5. blood loss and complications as documented by the responsible team;
6. postoperative plan and destination;
7. author, reviewer, time, and later correction.

Do not let the model fill silence from a template. "No complication stated" is not the same as "no complication occurred." The reviewer must resolve the difference.

The same rule applies to discharge material. A draft can organise the treating team's approved instructions. It cannot invent a medicine, follow-up interval, warning sign, or fitness decision.

## Privacy starts before the first real recording

The [DPDP Act, 2023](https://www.indiacode.nic.in/bitstream/123456789/22037/1/a2023-22.pdf) supplies the statutory framework for processing digital personal data in India. Its application to a hospital workflow, notices, consent, lawful uses, processors, retention, and patient rights needs organisation-specific legal review.

For a pilot, name the data path on one page:

- which encounter is captured;
- which device and account receive it;
- whether audio is stored;
- which note and transcript artifacts remain;
- who can view, edit, export, and delete them;
- how a patient request or incident is routed;
- what happens when connectivity fails.

Start with synthetic cases. Move to real patient information only after the hospital's privacy, security, clinical, and contracting owners approve the exact workflow.

## The India pilot: five cases, one correction drill

Use five synthetic cases rather than a polished vendor script:

- a Hindi-English clinic discussion that must yield an English clinical draft;
- a laterality correction caught before signature;
- a ward round with two speakers and an interrupted plan;
- a postoperative draft with one deliberately unstated field;
- a connectivity loss followed by recovery and audit review.

Score factual omissions, unsupported additions, correction trace, reviewer effort, access, and export. Do not publish an accuracy percentage from five cases. The pilot is a failure search, not a marketing study.

[WHO's AI-for-health guidance](https://www.who.int/publications/i/item/9789240029200) puts human autonomy, safety, transparency, accountability, inclusion, and sustainability at the centre of deployment. For a surgical unit, that means the surgeon and hospital remain responsible for deciding when a draft can enter the record.

We think the best early result is boring: fewer unfinished notes, no broader clinical claim, and a correction trail the quality team can follow.

## Patient Square's stated scope

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For India, Patient Square's stated scribe scope includes multilingual and code-mixed speech with the note produced in clinical English. Live consultation audio is processed in memory and discarded when the note is drafted; uploaded recordings use a separate retention mode with explicit consent. ICD-10 output remains suggestions, prescriptions remain drafts, and ABDM integration remains on the roadmap. Patient Square does not claim image interpretation, surgical planning, robotic control, intraoperative recommendations, or autonomous signing.

If the green-zone documentation work is your bottleneck, [review the current Hospital Copilot scope](../../products/hospital-copilot/). Confirm the current [India plan and product scope](../../pricing/) and [security posture](../../security/) before expanding the pilot.

---

## Medical Records Release Form: A HIPAA Field Map
https://patientsquare.com/us/blog/hipaa-medical-records-release-form/
Published 2026-10-10 · Tags: medical-records, hipaa, release-of-information, template

Build a medical records release form around HIPAA authorization fields, record scope, recipients, expiration, revocation, and a tested clinic workflow.

A valid HIPAA authorization identifies the information, who may disclose it, who may receive it, the purpose, an expiration event or date, and the individual's signature and date. It also carries required statements about revocation, conditioning, and redisclosure. A practice should have privacy counsel approve its form and any state-specific or specially protected record language.

A records clerk receives a signed page that says, "Send all PHI to my lawyer." The signature is present. The authority is not yet clear.

A medical records release form is useful only when staff can answer five questions without guessing: whose records, which records, released by whom, sent to whom, and for how long. Treat the form as a routing instruction backed by an authorization, not as a decorative signature page.

## Route the request before choosing a form

Start by naming the route. They are not interchangeable.

| Request | Working route | First owner |
|---|---|---|
| Patient asks the practice for a copy | HIPAA right of access workflow | Release-of-information staff |
| Patient asks the practice to send records to a named third party | Authorization review | Privacy or records staff |
| Another provider asks for records for treatment | Approved disclosure workflow | Records staff under practice policy |
| Lawyer, insurer, employer, school, or family member asks | Authority-specific review | Privacy or legal lane |
| Court order, subpoena, law-enforcement request, or oversight request arrives | Legal process | Privacy counsel or approved legal owner |

[HHS OCR's access guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html) describes an individual's right to inspect or obtain a copy of protected health information in a designated record set, subject to the rule's scope and exceptions. Do not make that patient-access route depend on a broad third-party authorization form when a different process applies.

## Build the authorization field by field

[45 CFR 164.508](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.508) supplies the federal authorization framework. Translate it into a controlled field map, then have privacy counsel review the final wording and any state overlays.

```text
MEDICAL RECORDS RELEASE AUTHORIZATION: FIELD MAP

Patient name: __________________________________________
Date of birth or approved identifier: ___________________

Person or organisation authorised to disclose:
Name: __________________________ Contact: _______________

Person or organisation authorised to receive:
Name: __________________________ Contact: _______________

Information described in a specific and meaningful way:
Record types: ___________________________________________
Date range or encounter: _________________________________
Excluded items, if any: __________________________________

Purpose of the disclosure: _______________________________
Expiration date or expiration event: _____________________

Delivery route requested: ________________________________
Identity and destination verified by: _____________________

Required authorization statements reviewed: _____________
Individual or authorised representative signature: _______
Date: ____________________________________________________

If signed by a representative:
Name: __________________ Relationship and authority: _____
Authority evidence checked by: ___________________________
```

The field map is not finished legal language. It is a completeness control for the approved form.

## Describe the records without making staff infer intent

HHS says an authorization can describe an "entire medical record" or "complete patient file" when that wording is specific and meaningful and the authorization is otherwise valid. The same [HHS answer](https://www.hhs.gov/hipaa/for-professionals/faq/may-a-covered-entity-use-or-disclose-a-patients-entire-medical-record-based-on-the-patients-authorized-signature/index.html) warns that "all protected health information" may be too broad without more definition.

Give the signer practical choices. A date range, encounter, clinician, facility, and record category make fulfillment easier to test. Include an "entire medical record" option only in counsel-approved wording. Do not hide specially protected categories inside a generic checkbox.

Psychotherapy notes have their own authorization rule under 45 CFR 164.508. Substance-use-disorder records, reproductive-health information, minors' records, genetic information, and other categories may trigger separate federal or state requirements. A universal internet template cannot settle those questions. The approved workflow needs a stop-and-review lane.

## Treat destination verification as part of the release

A perfectly drafted authorization can still fail at the last mile. One transposed fax digit sends the right records to the wrong place.

Record the destination from a trusted source. Confirm the recipient name and route using the practice's approved method. Keep the verified destination separate from free-text notes. If the patient changes the destination, capture a new instruction rather than editing history without a trace.

For electronic delivery, define how staff verify an address, protect the file, send any password or access code, and record successful delivery. For paper, define pickup identity checks, mailing steps, and returned-mail handling. The form starts the work; the disclosure log closes it.

## Keep expiration and revocation operational

An expiration field cannot live only on paper. Store the date or event in a form that staff can act on. A request received after expiration goes back to review.

The authorization must contain the required statement about the individual's right to revoke and the exceptions described by the rule. The practice also needs a route to receive a revocation, timestamp it, stop work that has not already occurred, and preserve what was disclosed before the revocation took effect.

Use three statuses:

1. Received. The instruction exists, but authority and scope are not yet cleared.
2. Approved for fulfillment. Required fields, identity, authority, scope, and destination passed review.
3. Released or closed. The disclosure log records what left, when, by which route, and who completed the work.

A signature should never jump a request from received to released.

## Test the workflow with five synthetic requests

Run the approved form and process without real patient data.

| Test | Expected control |
|---|---|
| Patient requests one encounter for personal use | Correct access route, no unnecessary third-party authorization |
| Patient directs a complete file to a new physician | Meaningful scope, verified recipient, fulfillment log |
| Parent signs for a minor | Representative authority review and state-specific check |
| Request includes psychotherapy notes | Separate stop-and-review path |
| Patient revokes before staff send the file | Timestamped stop, preserved audit history |

Add a sixth test for the actual software: paste an incorrect fax number and then correct it. The history should show both values and the approval event. Silent replacement defeats the point of a controlled release.

## Product boundary

Patient Square is an AI clinical platform. Its documentation and record features operate within the configured practice workflow. It does not decide whether an authorization is valid, resolve representative authority, interpret a subpoena, or approve a state-specific form.

Review [Patient Square's current security posture](../../security/) before mapping any record workflow. Keep legal authority with the practice's privacy owner and counsel. Keep clinical content with the clinician. Keep a release log that can reconstruct what actually happened.

---

## Patient Payment Plan Policy: A Practice Template
https://patientsquare.com/us/blog/patient-payment-plan-policy-medical-practice/
Published 2026-10-10 · Tags: patient-payments, financial-policy, medical-practice, template

Design a patient payment plan policy with eligibility, written terms, good-faith-estimate handoffs, exceptions, missed-payment review, and reconciliation.

A patient payment plan policy should name who qualifies, who can approve an exception, the balance and services covered, payment dates and amounts, accepted methods, statements, failed-payment handling, dispute routes, and when a plan closes. Keep the policy, the patient-specific agreement, the good faith estimate, and the final bill as separate records. Have counsel and billing leadership review fees, interest, collections, credit reporting, and state or payer rules.

"Can I split this into four payments?" sounds like a yes-or-no question. At the front desk it is six questions: which balance, which services, whose approval, what dates, what happens to pending insurance, and where the agreement will be recorded.

A payment plan policy should make those decisions repeatable. It should not turn a receptionist into a lender, contract drafter, or collections manager between check-ins.

## Keep four financial records separate

The fastest way to create a billing dispute is to let one document impersonate another.

| Record | Job | It does not prove |
|---|---|---|
| Good faith estimate | Expected charges before covered self-pay care | Final amount owed |
| Claim or payer response | Insurer's processing of submitted services | Patient agreement to a payment schedule |
| Patient bill or statement | Balance presented after adjudication or other billing steps | Approved installment terms |
| Payment plan agreement | Dates, amounts, methods, and approved handling for a named balance | That the underlying bill is correct |

[CMS explains](https://www.cms.gov/initiatives/no-surprise-billing/overview/policies-resources/providers-payment-resolution-patients) that providers and facilities generally must give uninsured or self-pay consumers a good faith estimate when covered conditions are met, including when care is scheduled or an estimate is requested. Keep that estimate linked to the account. Do not overwrite it with the later bill or payment agreement.

## Draft the policy before drafting an agreement

The policy governs how staff decide. The agreement records one approved decision.

```text
PATIENT PAYMENT PLAN POLICY: DECISION SHEET

Policy owner: ____________________________________________
Effective date and review date: __________________________

Eligible balances or services: ___________________________
Balances excluded or held for review: ____________________
Minimum or maximum terms after legal approval: __________
Pending-insurance rule: __________________________________

Standard approval role: __________________________________
Exception approval role: _________________________________
Hardship or accessibility review route: __________________
Interpreter or communication support route: _____________

Required agreement fields: _______________________________
Approved payment methods: ________________________________
Statement and receipt schedule: __________________________

Missed-payment review owner: _____________________________
Dispute and correction route: ____________________________
Collections handoff, if legally approved: ________________

Reconciliation owner and frequency: ______________________
Closure evidence: ________________________________________
```

Leave interest, fees, acceleration, credit reporting, and collection language out until counsel and billing leadership approve exact terms. A copied clause can create obligations the practice never meant to assume.

## Resolve the balance before offering dates

A patient should be able to see which balance the plan covers. Record the account, services, dates, original charge, payer adjustment, payments already received, credits, and current patient responsibility. If a claim is still pending or under appeal, follow the policy for holding or separating that amount.

Do not roll unrelated family balances or future services into one line because the practice system makes it convenient. If the policy allows aggregation, the agreement should list each component and explain how new charges are treated.

The [AMA's private-practice sample forms](https://www.ama-assn.org/system/files/steps-forward-private-practice-playbook-sample-forms.pdf) keep a practice financial policy and a patient payment plan as distinct documents. That separation is useful even when a practice writes its own counsel-approved forms.

## Make each installment reconstructable

For one patient-specific agreement, capture:

- agreement ID and account ID;
- covered balance and service dates;
- installment amount, due date, and count;
- accepted payment route;
- receipt and statement method;
- who approved standard or exception terms;
- how the patient can dispute an amount or report hardship;
- what triggers review rather than automatic escalation;
- signatures, date, version, and delivery record.

Keep authorization for recurring payment separate from the financial agreement when the approved payment processor or applicable rules require it. Do not store full payment credentials in a general task, note, spreadsheet, or AI prompt.

## Use an exception lane, not whispered exceptions

Staff will meet cases the standard table cannot answer: insurance reprocessing, a returned refund, two family accounts, a corrected coding error, a patient who needs an accessible communication method, or a balance already in dispute.

Create one visible exception status. It needs a reason category, owner, due date, patient communication, and outcome. The approver should see the same information for every request. Free-text sympathy is not a control, and neither is a rigid denial button.

If the patient contests the bill, pause the payment-plan decision long enough to route the underlying balance. A schedule for the wrong amount only gives the error more dates.

## Missed payments need review before consequence

Separate a failed transaction from a broken promise. Cards expire. Bank details change. A portal link may never arrive. A statement can go to the wrong address.

Use a short sequence:

1. Record the attempted installment and processor response without copying sensitive payment data into the account note.
2. Check whether a billing correction, insurance change, dispute, or access problem is open.
3. Send the approved neutral notice through the patient's chosen route.
4. Offer the policy's review or cure path.
5. Escalate only under counsel-approved terms, with a named owner and preserved history.

Clinical messages and urgent care questions stay out of the collections lane. A financial flag should not hide a test result or close a care task.

## Reconcile the ledger every month

The payment plan ledger should add up without reading narrative notes.

| Measure | What to compare |
|---|---|
| Opening balances on active plans | Prior close plus approved changes |
| Installments due | Agreement schedules |
| Payments posted | Processor settlement and patient accounts |
| Failed or reversed payments | Processor event and review outcome |
| Adjustments | Approved correction or payer event |
| Plans completed | Zero covered balance and closure record |
| Plans in dispute | Named owner and next review date |

Sample a few plans from agreement to receipt and back. Test a correction after the second installment. The ledger must preserve the old amount, new authority, changed future schedule, and patient notice.

## Product boundary

Patient Square's current practice plans combine clinical documentation and selected practice workflows. This article does not claim that Patient Square underwrites credit, provides legal forms, collects debt, interprets payer contracts, or decides who qualifies for a payment plan.

Use the [current US pricing page](../../pricing/) to verify the product modules actually offered. Keep money movement in the approved payment system, policy approval with the practice, and legal terms with qualified counsel.

---

## ABDM Milestone 1 (M1) Explained for Clinics
https://patientsquare.com/in/blog/abdm-milestone-1-explained-clinics/
Published 2026-10-09 · Tags: abdm, milestone-1, abha, india, vendor-certification

ABDM Milestone 1 is the ABHA create-and-verify stage. It certifies your software vendor, not your clinic. What M1 covers, and what it leaves out.

M1 is the ABHA identity milestone. NHA's Milestone 1 API document describes it as the creation and verification of the ABHA number, and covers registering an ABHA, linking an ABHA address, logging in, retrieving a lost account, and editing or deactivating it. No clinical records move at M1.

ABDM Milestone 1 is the identity milestone. NHA's own M1 API document describes it as the creation and verification of the ABHA number: a product proves it can register an ABHA, verify one, and manage that account afterwards. It certifies the software vendor, not your clinic. And no clinical record moves at M1.

That last sentence is where the confusion at Indian clinics usually starts. A vendor says ABDM, the clinic hears records, and what actually shipped is an ABHA field on the registration screen.

> **Key takeaways**
> - NHA's Milestone 1 document scopes M1 to one job: creation and verification of the ABHA number. Identity, not records.
> - Milestones are certified against the software. Your clinic's equivalent homework is HFR and HPR registration.
> - M1 is the shallowest true version of "ABDM ready", which is why so many vendor claims quietly stop there.
> - Passing a milestone in the sandbox and running it live in production are 2 different achievements. Ask about both.
> - Patient Square is not ABDM-certified at any milestone today, M1 included. ABDM support is on the roadmap.

_Source: NHA, Working with ABHA (Health ID) API, Milestone 1, March 2022._

## M1, in NHA's own words

You don't have to guess at this one. NHA published an API document for the milestone, titled "Working with ABHA (Health ID) API, Milestone 1", version 1.0 revision 1, dated March 2022. Its purpose line is unusually blunt for a government spec: the document holds the APIs and sequence diagrams for "Milestone One/M-1 (Creation and Verification of ABHA Number)."

The contents page is the scope. Reading down it, a vendor working M1 has to handle all of this:

- Register an ABHA using an Aadhaar number, or using other ID documents.
- Link and de-link an ABHA address against that ABHA number.
- Log a patient in with an Aadhaar OTP or a mobile OTP.
- Retrieve an account for a patient who's lost track of theirs.
- Pull a profile, pull its QR code, and edit an email or mobile number on it.
- Delete, deactivate, or reactivate the account.

Look at that last line. Account lifecycle. Most people picture M1 as a create button and stop there, but a vendor also has to handle the unglamorous half: the patient who keyed the wrong email, the patient who wants their account deactivated. That's real engineering, and it's the part demos skip.

One caveat, and it matters. That document is from 2022, and NHA has since moved to newer API versions published on the v3 sandbox. So read the list above as the shape of the milestone rather than today's tick-box checklist. The live checklist is whatever NHA's current sandbox documentation says, and that's the only version anyone gets assessed against.

## The identity layer stops short of the consent layer

The most useful line in that NHA document isn't an API at all. ABDM, it says, has now segregated the identity layer from the consent layer: the ABHA number provides a strong identity to an individual, while the ABHA address is what lets that individual share their health records with providers and payers.

M1 lives entirely on the identity side of that split. It answers "who is this person, verifiably, across every facility in India?" It does not answer "where is this person's history, and may we see it?"

Practically, that means a product certified at M1 and nothing else can identify your patient cleanly and tie your file to a national ID. It cannot push last Tuesday's OPD note anywhere, and it cannot pull the discharge summary from the hospital across town. Those are separate capabilities on separate milestones, covered in the [Milestone 2 explainer](../abdm-milestone-2-explained-clinics/) and the [Milestone 3 explainer](../abdm-milestone-3-explained-clinics/). If the number-versus-address distinction is still fuzzy, the [ABHA number vs ABHA address post](../abha-number-vs-abha-address-explained/) untangles the two identifiers your desk will actually see.

## Your clinic doesn't pass M1. Your software does.

Clinic owners get this one wrong constantly, and it costs them weeks.

Milestones are earned by a software product, integrating against NHA's APIs in the sandbox and demonstrating the required flows. A hospital doesn't sit an M1 exam. A three-doctor clinic in Nashik doesn't either. If someone tells you your clinic needs to "get M1 certified", they've either misread the scheme or they're selling you something.

Your side of the work exists, it's just a different shape. It's registry work. The facility gets registered on the Health Facility Registry at facility.abdm.gov.in, and the treating doctor gets registered on the Healthcare Professionals Registry. That's what makes your clinic a recognised node the patient's app can share to, and it's the prerequisite behind incentive eligibility too. The [ABHA linking front-desk workflow](../abha-linking-clinic-workflow/) walks the desk-level version of all of this, including the duplicate-ABHA mistake that causes more grief than any technical failure.

So there are two tracks running in parallel. Your vendor climbs milestones. You get on the registries. Neither substitutes for the other.

## Where "ABDM ready" usually comes from

We'll say what we think: most "ABDM ready" claims in Indian clinic software are M1 claims wearing a bigger jacket.

The reason is structural, not dishonest. Creating and verifying an ABHA is the shallowest useful integration in the whole stack. There's no consent manager to wire, and no callbacks to serve when another facility comes asking for records. A competent team can ship an ABHA create-and-verify flow in a fraction of the time the later milestones take. So that's where a lot of products stop, and "we support ABDM" stays technically true of them.

Which means the claim can be accurate while the purchase is wrong. Buy expecting a patient's old records to surface mid-consult, get identity plumbing instead, and nobody lied to you. You're still stuck. One question before you sign closes most of that gap: which milestone, exactly?

## Sandbox pass, production live: two different sentences

Every ABDM capability exists twice before it's real. Once in the sandbox, once in production.

The sandbox is NHA's test environment, and its own documentation frames it as ready to be integrated with hospital and lab software: EMR, HIMS, LIMS, telemedicine, and similar. A vendor registers there, gets test credentials, builds the flows, and demonstrates them. All of that can be genuinely complete while your Tuesday OPD sees nothing, because the same capability still has to be enabled in the live environment your patients touch.

Which is where the second question comes from, and it's the one vendors dodge: is your M1 capability live in production, for real patients, today? A vendor with a clean answer gives it in one sentence. A vendor without one starts describing a roadmap, and that's your answer.

## A 90-second vendor check

Run this on your next sales call. It's a translation exercise more than an interrogation.

| What you hear | What it usually means | Ask this next |
|---|---|---|
| "We're ABDM ready" | Anything from a sandbox login to full certification | "Which milestone, and is it live in production?" |
| "We create ABHA numbers" | M1-class capability, identity only | "Can you also link and share a visit record?" |
| "We're integrated with ABDM" | Often M1, possibly still in the sandbox | "Show me your current milestone status." |
| "Records sync with ABDM" | Needs M2 or M3, not M1 | "Which one, and can a doctor fetch under consent today?" |
| "It's on our roadmap" | Honest, and not shipped | "What happens to my records until then?" |

Cross-check whatever you're told against the official ABDM and NHA portals rather than a slide. And keep the answers in writing, because "ABDM ready" in an email is a lot harder to walk back than "ABDM ready" in a meeting.

## When a different vendor is the better fit

If ABHA creation and linking from inside your clinic software is a hard requirement this quarter, we're not your answer, and we'll say so plainly. eka.care publicly ships live ABDM integration across the M1 to M3 milestones, and for a clinic building its workflow around ABDM right now, that's the honest pick. Put the same two questions to them anyway, because milestone status moves.

The case for going beyond M1 is usually financial as much as clinical. The Digital Health Incentive Scheme can pay facilities for eligible KYC-verified ABHA-linked transactions, but identity creation by itself is not the qualifying event. The effective corrigendum can change the eligible record types, rates, patient limits, API version, security evidence, and filing period. If you are building a business case, use the [source-dated DHIS breakdown](../abdm-incentives-for-doctors/) and verify the vendor's production status instead of relying on an old flat per-record figure.

The reverse is also true. A vendor certified at M1 in production still has to survive your OPD queue and your billing on a 40-patient Saturday. Milestone status answers one narrow question well. It says nothing about whether the software is any good at the rest of the job.

## The honest verdict on where we sit

Patient Square is not ABDM-certified at any milestone today, M1 included, and we won't imply otherwise. ABDM support is on our roadmap, not shipped. We don't create or verify ABHA numbers inside the product, and we claim no HIP, HIU, HFR, HPR, NHCX, or Consent Manager integration. If you need an ABDM milestone in production, that conversation belongs with your HMS or EMR vendor.

What we do ship is a packaged copilot. Practice Copilot can use Patient Square EHR or an existing EHR for independent clinics. Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR for multi-department hospitals, with the ambient AI scribe as one module inside either product. The scribe listens during the consult and drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft in clinical English, ready about two minutes after the visit ends. You review and sign. The ICD-10 entries are suggestions to confirm, never codes applied on your behalf. The prescription is a draft, not something transmitted anywhere. Visit audio is processed and discarded rather than stored, and the note stays yours. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The connection to M1 is indirect but real: you can't link a record you never wrote down properly. Whatever milestone your clinic software eventually reaches, the raw material is a complete, structured note from every visit. How we handle that data is set out on the [security page](../../security/).

## If you remember one thing

M1 is identity. It's the milestone that gets a patient verifiably identified under ABDM, nothing more, and NHA's own documentation says so in the title. Your vendor holds the certification; you hold the registry registrations. And a milestone completed in the sandbox is not a milestone running in production, which is why both questions get asked every time.

If the documentation half is the part that's actually broken in your clinic, <a href="/in/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and bring one consult from last week. Then judge the note on one thing: could you sign it without rewriting it?

---

## AI Scribe for Neurology: Preserve the Timeline
https://patientsquare.com/us/blog/ai-scribe-for-neurology/
Published 2026-10-09 · Tags: neurology, ai-medical-scribe, clinical-documentation, longitudinal-care, specialty-practice

A neurology AI scribe evaluation built around chronology, spoken exam findings, source attribution, and clinician review.

It should draft the history and the clinician's spoken findings without merging old, patient-reported, and current observations. The exact note structure belongs to the neurologist. Test chronology, attribution, laterality, relevant negatives, medication changes, and whether an unspoken exam element stays absent.

Neurology notes break when timepoints blur. A symptom from last year, a patient-reported change last week, and today's examination cannot become one timeless paragraph. Test an AI scribe on chronology first. Then test source attribution, laterality, and whether the system leaves an unspoken finding blank.

## Build the note around three timepoints

Start a pilot with one synthetic case, not twenty real patients. Give it three facts:

- Old: an event documented before today's visit.
- Interval: a change the patient or caregiver reports since the last review.
- Today: a finding the clinician observes and states now.

Mention those facts out of order. The draft should produce a readable timeline without silently upgrading an old or reported fact into today's examination.

Use a small provenance ledger:

| Draft element | Timepoint | Source label | Reviewer decision |
|---|---|---|---|
| Prior event | Exact source date | Prior record or patient report | Keep, qualify, or remove |
| Interval change | Stated period | Patient, caregiver, or source record | Confirm attribution |
| Current finding | Today | Clinician-spoken examination | Confirm wording and laterality |
| Test result | Source date | Named report | Confirm source and interpretation |
| Plan | Today | Clinician decision | Confirm it is a plan, not a completed action |

The ledger is not a clinical template. It is a way to catch time travel in generated prose.

## Spoken findings are not a performed examination

NINDS explains that a neurological examination may assess movement, sensation, hearing and speech, vision, coordination, balance, and aspects of mental status. It also states that the examination and history help the clinician decide what further testing may be needed ([NINDS diagnostic tests and procedures](https://www.ninds.nih.gov/health-information/disorders/neurological-diagnostic-tests-and-procedures)).

An ambient scribe does not perform that work. It can draft the findings a clinician says aloud. If the clinician never states a reflex, gait finding, score, or relevant negative, the system should not supply one from a familiar template. Blank is safer than invented completeness.

The same boundary applies to MRI, EEG, EMG, and outside records. A spoken summary can be documented with the right attribution. The scribe should not claim to have read or interpreted a source it never received.

## Try the contradiction round

After the basic timeline test, add one controlled contradiction. The patient says the symptom began in March; a prior record says April. The clinician notes that discrepancy but does not resolve it.

A useful draft preserves both sources and the unresolved state. A bad draft picks one date, averages them into "spring," or drops the disagreement. That edit may read smoothly, which is exactly why it is dangerous.

Repeat the exercise with laterality and a medication list. Ask the vendor where uncertainty appears, whether reviewers can find changed text, and what the system does when two speakers disagree. HHS explains that covered entities and their business associates have defined HIPAA responsibilities when protected health information is handled ([HHS covered entities and business associates](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html)). Contract, access, and retention questions belong in the same pilot packet as note quality.

## Choose the surrounding record separately

Patient Square is an AI clinical platform. Its AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Practice Copilot can work alongside an existing EHR or use the bundled Patient Square EHR, named AI Copilot EHR on the pricing page, from the Copilot tier. Annual US pricing is $79 per physician per month for Assist and $119 for Copilot ([Patient Square pricing](https://patientsquare.com/us/pricing/)).

Patient Square does not claim MRI, EEG, or EMG interpretation; neurology registries; diagnostic support; procedure coding; or specialty-device integration. A neurology practice that depends on those capabilities should keep the system that owns them. The scribe evaluation can still answer a narrower question: does it reduce drafting work without corrupting chronology?

Our view is blunt. If a vendor demo never includes an old fact, an interval change, and today's finding in the same visit, the demo is too easy. Pair this timeline test with the [data-ownership and export guide](../ai-scribe-data-ownership-export/) and the [accuracy evaluation checklist](../ai-scribe-accuracy-what-to-expect/). Book a demo with the contradiction case ready.

---

## AI Scribe for ENT: Draw the Device Boundary
https://patientsquare.com/us/blog/ai-scribe-for-otolaryngology/
Published 2026-10-09 · Tags: otolaryngology, ent, ai-medical-scribe, clinical-documentation, specialty-practice

An ENT AI scribe evaluation for spoken findings, audiograms, scope media, procedure records, registry data, and clinician review.

Do not assume it can. Patient Square does not claim audiogram ingestion, scope-image interpretation, or device integration. Its scribe can draft what the clinician says about a verified source. The reviewer must preserve the source, date, laterality, and distinction between a measured result and an interpretation.

An ENT scribe should know where the conversation ends. Audiograms, scope media, device output, and registry submissions have their own source systems and reviewers. A safe pilot checks whether the draft preserves that boundary. If a result was not spoken or supplied through an approved path, it should not appear as fact.

## Three lanes, one signed record

At the end of a busy clinic session, the signed note may refer to information that began in different places. Split the pilot into three lanes before judging the prose:

| Lane | Examples | Scribe acceptance rule |
|---|---|---|
| Conversation | Symptoms, history, goals, instructions discussed | Draft with speaker and time context intact |
| Observed and stated | Clinician-spoken examination or procedure finding | Include only what the clinician actually states |
| Device or source record | Audiogram, scope media, imaging report, prior procedure record | Cite the source in the note only when the clinician supplies or verifies it |

The lane label does not need to appear in the final note. It belongs in the test worksheet, where it exposes unsupported jumps.

## The silent-result case catches overreach

Give the reviewer a synthetic encounter with an audiogram in the source system. Do not mention one of its values during the recorded conversation. If the draft supplies that value anyway, stop and trace how it arrived.

Then reverse the case. Have the clinician state a verified result, its date, and the source. The draft should preserve all three without implying the scribe independently read the study. Run the same drill with a scope finding and a prior procedure record.

This is a better trial than counting how many ENT terms the product spells correctly. Vocabulary is visible. Provenance failures hide inside fluent sentences.

## Connectivity is a separate capability

Device, media, and registry connectivity are contract-and-demonstration questions, not benefits to infer from the words "AI" or "EHR." Ask the vendor to name the supported product, data path, implementation owner, and current status. The federal Health IT Playbook recommends common demo scenarios and testing tied to the practice's needs ([ASTP/ONC Health IT Playbook](https://playbook.healthit.gov/playbook/full/)). If the vendor cannot show the required path with representative data, treat the answer as no.

Patient Square does not claim Reg-ent connectivity, registry submission, audiogram ingestion, scope-media handling, or device integration. Those gaps are disqualifying when the practice needs the scribe to own them. They are not disqualifying when the real job is drafting the spoken visit beside an existing specialty system.

## A six-row pilot log beats a polished demo

Use two rows for each lane: one ordinary case and one exception. Record the source expected, what the draft produced, the correction made, who reviewed it, and whether the failure would have been obvious during signing.

Add contract controls to the same packet. HHS describes covered entities and business associates as carrying defined responsibilities for protected health information ([HHS covered entities and business associates](https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html)). Ask where visit data goes, which vendors receive it, how access is logged, how long each artifact remains, and what the practice can export or delete.

Repeat the same six cases after configuration changes. A stable log exposes unsupported changes faster than another polished demo.

## Keep the product claim narrow

Patient Square is an AI clinical platform. Its AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Practice Copilot can work alongside an existing EHR or use the bundled Patient Square EHR, named AI Copilot EHR on the pricing page, from the Copilot tier. Annual US pricing is $79 per physician per month for Assist and $119 for Copilot ([Patient Square pricing](https://patientsquare.com/us/pricing/)).

It does not claim the ENT-specific capabilities named above. We think that honesty makes the evaluation easier: keep the specialty system for device, media, and registry work, then test whether the scribe reduces the spoken-documentation burden without blurring sources.

Use the [EHR integration checklist](../ai-scribe-ehr-integration-checklist/) to document the handoff and the [HIPAA, BAA, and consent guide](../ai-scribe-hipaa-baa-consent/) for the privacy review. Book a demo when the six-row log is ready.

---

## AI Scribe for Pain Management: Separate the Note From the Check
https://patientsquare.com/us/blog/ai-scribe-for-pain-management/
Published 2026-10-09 · Tags: pain-management, ai-medical-scribe, clinical-documentation, pdmp, specialty-practice

A pain-management AI scribe guide for keeping visit narrative, PDMP review, procedure evidence, and clinician decisions in the right lane.

Only if the vendor specifically proves that capability and the practice approves the access path. Patient Square does not claim PDMP access or checking. Its scribe can draft what the clinician says about a review, but the authorized clinician still performs and verifies the source-system check.

A pain-management scribe can draft the visit narrative. It cannot turn an unperformed PDMP review, an unseen image, or a planned procedure into completed evidence. The pilot should test that boundary on purpose. Keep source-system checks, prescribing authority, and the final signed decision with the people and tools that own them.

## Thursday's refill visit has two clocks

One clock follows the conversation: pain since the last visit, function, response, adverse effects, and what the patient reports taking. The other follows actions outside the conversation: source records reviewed, examinations performed, decisions made, and orders actually authorized.

An ambient draft can help with the first clock. It must not fake the second.

| Statement in the draft | Evidence owner | Acceptance test |
|---|---|---|
| Patient reports a change in function | Patient conversation | Attribution remains explicit |
| Clinician reviewed PDMP data | Authorized clinician and PDMP | Review occurred and is recorded according to local policy |
| Procedure was performed | Procedure record and clinician | Date, site, laterality, and completion agree |
| Medication was prescribed | Prescriber and prescribing system | Draft discussion is not presented as transmission |
| ICD-10 candidate | Clinician or authorized coding reviewer | Suggestion is accepted, changed, or rejected before use |

This is the core buying test. The note can be concise or long. Source confusion is the failure.

## PDMP review is not a sentence-generation task

CDC describes a prescription drug monitoring program as an electronic database that tracks controlled-substance prescriptions. Its clinical guidance points clinicians to Recommendation 9 of the 2022 opioid guideline and says PDMP information should be reviewed at defined prescribing moments to assess risk ([CDC PDMP guidance](https://www.cdc.gov/overdose-prevention/hcp/clinical-guidance/prescription-drug-monitoring-programs.html)). The full guideline also addresses PDMP review and the benefits and risks of toxicology testing ([CDC 2022 guideline](https://www.cdc.gov/mmwr/volumes/71/rr/rr7103a1.htm)).

This article is not prescribing advice. The operational point is narrower: a draft that says "PDMP reviewed" needs evidence from the authorized workflow. Hearing those words in a room is not the same thing as accessing the source database. A clinic's medical, compliance, and legal owners should define when the check occurs and how it is documented.

Patient Square does not access a PDMP, perform toxicology review, transmit prescriptions, or provide EPCS. It can draft what was discussed. The clinician verifies the record and completes required work in the approved systems.

## Use a missing-fact drill

Build three synthetic encounters for the pilot. In one, the patient reports a medication but the dose is not stated. In another, a prior procedure is discussed but today's laterality is never spoken. In the third, the clinician says a source check will happen after the visit.

Now read the drafts cold. Any filled-in dose, inferred laterality, or completed check is a stop signal. Mark it, correct it, and record how the vendor responds. A useful system should make uncertainty visible to the reviewer instead of smoothing it into confident prose.

Run the same cases twice: once with the clinician narrating relevant findings clearly, and once with normal conversational shorthand. The difference tells you how much workflow change the product demands. The federal Health IT Playbook recommends common demonstration scenarios and structured testing against practice needs ([ASTP/ONC Health IT Playbook](https://playbook.healthit.gov/playbook/full/)).

## Define the product boundary before price

Patient Square is an AI clinical platform. Its AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Practice Copilot can sit alongside the clinic's current EHR or use the bundled Patient Square EHR, named AI Copilot EHR on the pricing page, from the Copilot tier. US annual pricing is $79 per physician per month for Assist and $119 for Copilot ([Patient Square pricing](https://patientsquare.com/us/pricing/)).

The boundaries matter more here than the price. Patient Square does not claim PDMP access, EPCS, pharmacy transmission, procedure-device integration, imaging review, or a coding engine. A pain clinic that needs those functions should keep or buy systems that provide them.

We think the right trial question is not "Did the AI write a complete note?" Ask, "Can a reviewer tell which facts came from the room and which controls happened somewhere else?" The [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/) covers the coding boundary, while the [prescription-draft safety guide](../ai-scribe-prescription-draft-safety/) covers the difference between a draft and transmission. Book a demo after your missing-fact cases are written.

---

## AI Scribe for Plastic Surgery: Keep Photos and Notes Apart
https://patientsquare.com/us/blog/ai-scribe-for-plastic-surgery/
Published 2026-10-09 · Tags: plastic-surgery, ai-medical-scribe, clinical-documentation, hipaa, specialty-practice

A plastic-surgery AI scribe test for consultation notes, procedure findings, patient images, review ownership, and EHR handoff.

Do not assume it can. A visit scribe may draft the spoken consultation, but image capture, comparison, annotation, consent, and storage are separate product claims. Patient Square does not claim image interpretation. Keep the photo system and its clinical review step explicit in the workflow.

A plastic-surgery scribe should draft what the clinician and patient say. It should not quietly turn a photograph, implant record, or procedure observation into text it never received. Test those boundaries separately. The useful product is the one that keeps each fact tied to its source and gives the surgeon a clean review queue.

## One visit can leave four different records

Picture a 3:40 p.m. consult. The patient explains a prior procedure. The surgeon describes today's findings aloud. Staff capture photographs in an approved system. A plan is discussed, but nothing has been performed yet.

Those facts should not collapse into one undifferentiated paragraph. Use this source card during a trial:

| Record lane | Source | Safe scribe job | Human checkpoint |
|---|---|---|---|
| Patient narrative | Conversation | Draft the reported history and goals | Confirm attribution and context |
| Clinician finding | Spoken observation | Draft only what the clinician states | Confirm laterality, site, and wording |
| Photograph or image | Approved image system | No inference from the image | Review image, label, consent, and access separately |
| Procedure record | Clinician and source record | Draft the dictated account | Confirm what actually occurred before signing |

The table is intentionally strict. A polished sentence with no traceable source is still a bad sentence.

## The photograph needs its own privacy path

HHS explains that health information becomes protected health information when it identifies a person, or when there is a reasonable basis to believe it can identify the person. Its HIPAA de-identification guidance lists full-face photographs and comparable images among the Safe Harbor identifiers that must be removed ([HHS de-identification guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html)).

That does not mean every clinical photograph follows one universal rule. It means a practice cannot treat its photo library as decorative media. Privacy and legal owners should define why an image is captured, where it is stored, who can view it, how consent or authorization is handled, and how the practice handles patient access and amendment requests ([HHS medical records guidance](https://www.hhs.gov/hipaa/for-individuals/medical-records/index.html)). Record retention and disclosure still follow applicable law and practice policy.

An AI-scribe pilot should not improvise this policy. Keep image capture outside the scribe test unless the vendor contract and the practice's approved workflow expressly include it.

## Run a three-encounter falsification test

Do not start with the easiest visit. Try to prove the product wrong.

First, run a consultation where the patient describes old surgery but the clinician has not verified the details. The draft should preserve that attribution. Next, use a follow-up with an image in the chart that is never described aloud. The draft should not invent an image finding. Last, dictate a procedure account with exact site and laterality, then change one detail during review and check whether the edit history remains visible in the destination system.

Score each encounter on five items:

1. Every statement has a clear speaker or source.
2. Unspoken image findings stay out.
3. Planned care does not become completed care.
4. Laterality and dates survive review.
5. The clinician can correct the draft before it becomes part of the record.

The federal Health IT Playbook recommends selecting technology against the practice's own needs, using common demonstration scenarios and a testing plan ([ASTP/ONC Health IT Playbook](https://playbook.healthit.gov/playbook/full/)). A three-encounter falsification test turns that advice into something a specialty practice can run in one afternoon.

## Put the scribe beside the specialty system

Patient Square is an AI clinical platform. Its AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Practice Copilot can work alongside an existing EHR or use the bundled Patient Square EHR, named AI Copilot EHR on the pricing page, from the Copilot tier. The annual US rates are $79 per physician per month for Assist and $119 for Copilot ([Patient Square pricing](https://patientsquare.com/us/pricing/)).

Patient Square does not claim photo management, image interpretation, implant tracking, procedure imaging, or plastic-surgery-specific clinical modules. If one of those capabilities decides the purchase, keep the specialty system. Evaluate the scribe on spoken documentation and review burden instead.

Our opinion: the strongest plastic-surgery pilot is deliberately boring. It proves that the draft knows less than the surgeon, not more. Use the [AI scribe security checklist](../ai-scribe-security-checklist/) for the vendor review and the [small-practice implementation guide](../ai-scribe-implementation-small-clinic/) for a limited rollout. Book a demo when you have the three test encounters ready.

---

## Multispecialty Clinic Software in India: Buyer Guide
https://patientsquare.com/in/blog/multispecialty-clinic-software-india/
Published 2026-10-09 · Tags: multispecialty-clinic, clinic-software, india, procurement

Test multispecialty clinic software against shared registration, specialty notes, cross-referrals, billing, access, corrections, and downtime before buying.

It is a clinic system configured for several specialties that share patients, registration, schedules, records, billing, and administration while preserving specialty-specific documentation and access. The buyer should test the handoffs between departments, not count module names.

A multispecialty clinic does not become complicated because it has several note templates. It becomes complicated when one patient moves from front desk to one doctor, another department, a test, billing, and follow-up without anyone losing the thread.

Buy software around those handoffs. A long module list can still leave staff retyping names, doctors hunting for prior notes, and billing guessing which department owns a charge.

## Draw five patient journeys before the demo

Use journeys that actually cross specialties. Keep them synthetic during procurement.

1. A new patient sees general medicine and receives an internal referral to cardiology.
2. A returning patient books dermatology with changed contact details already known to another department.
3. A child sees paediatrics while a guardian handles registration and payment.
4. Two consultants contribute to one episode but need separate authorship and sign-off.
5. A patient moves between branches and later requests a correction or copy.

For each journey, mark the owner at registration, scheduling, consultation, orders, results, billing, follow-up, and correction. Then make the vendor run the entire path. Slides do not count.

## Keep one identity and governed specialty views

Duplicate patient identities create bad handoffs. The [ASTP/ONC patient-identification SAFER Guide](https://healthit.gov/resources/2025-safer-guide-patient-identification/) is written for US health IT, but its operational questions travel well: search before creation, handle similar names, review duplicates, and make identity errors visible.

Test Indian naming and contact realities. Include initials, transliteration differences, shared family phones, changed surnames, incomplete addresses, and a guardian. Ask what the system does when it is unsure. The correct answer is often a staff review queue, not an automatic merge.

One identity does not mean every user sees every detail. Ask for a role and access matrix by specialty, job, location, and task. Verify a permitted view and a denied view. Confirm that emergency or break-glass access, if offered, creates a reason and audit event.

## Let specialties differ without fragmenting the chart

Cardiology, dermatology, orthopaedics, gynaecology, psychiatry, and physiotherapy do not document the same encounter. The software should support specialty templates and forms without turning the patient's history into disconnected islands.

During the demo, change a template. Check who approves it, which version applies to new visits, and what happens to old notes. Have two specialties document the same synthetic patient. Confirm that authorship, date, source, corrections, and visibility remain clear.

Avoid a template contest. More fields can mean more clicks and more copied text. Ask each specialty to identify the smallest record that supports its work, then test the difficult exceptions.

## Test internal referral as a closed loop

An internal referral is not complete when one doctor types "cardiology opinion." The receiving department needs an actionable request, relevant information, urgency, owner, status, and result back to the referrer.

Run four variations:

- The patient accepts and books before leaving.
- The patient wants to book later.
- The receiving specialty asks for more information.
- The patient never attends.

Ask who sees each state and what closes the loop. A shared calendar with no owner can lose work just as easily as a paper slip.

## Separate orders, results, and interpretation

If the clinic offers diagnostics or connects to an outside provider, map the order and result path. Confirm patient matching, ordering clinician, destination, review queue, communication, amendment, and downtime.

Do not accept "lab integration available" as a complete answer. Name the laboratory, interface or transfer method, supported fields, error queue, implementation owner, and commercial dependency in writing. Patient Square itself does not claim named lab, imaging, EHR, HL7, or FHIR integrations.

The same boundary applies to AI. A draft note, ICD-10 suggestion, or prescription draft is not a final clinical decision. The treating clinician reviews and signs what belongs in the record.

## Make billing follow the clinical journey

Define who owns registration fees, consultation charges, packages, procedures, discounts, refunds, and taxes. Test a patient who sees two specialties on one day, cancels the second visit, and returns for a procedure at another branch.

Watch for hidden duplicates. A system may create one bill per department even when the front desk expects one patient statement. Another may combine charges but obscure who approved a discount. Ask for a clear audit trail and a reconciliation report.

Pricing needs the same discipline. Compare subscription, setup, migration, template work, messaging, payment fees, training, custom reports, support, storage, integrations, and exit assistance. A low per-doctor rate can be expensive after every cross-department workflow becomes a custom project.

## Treat privacy as a workflow decision

Map which personal data each role collects, why, where it goes, and how patients can use the practice's approved request and correction process. Use the official [DPDP framework page](https://www.meity.gov.in/data-protection-framework) as the starting point with Indian counsel and the clinic's privacy lead.

Ask the vendor to show role access, authentication, activity logs, support access, backups, incident handling, retention, export, deletion, and subcontractors. Review contract language against the demonstrated system. A privacy slide is not operating evidence.

If a vendor says ABDM ready, stop and ask for the exact milestone certificate, product name, environment, and production scope. Patient Square makes no ABDM milestone claim today. ABDM is on the roadmap.

## Use NABH's software programme as a question source

NABH now publishes a [Digital Health Standards programme for Clinic Management Systems](https://nabh.co/programmes/digital-health-standards-for-clinic-management-system/). Its official page describes assessment of safe, secure, interoperable clinic software and sets specific eligibility and certification conditions for vendors.

That does not make every clinic buyer an assessor. It does give procurement teams a useful warning: "NABH aligned" and "NABH certified" are not interchangeable. Verify certificates on the NABH site and read the scope. Patient Square does not claim this certification.

For a non-certified product, ask the same practical questions about identity, access, documentation, continuity, security, and evidence. Judge the answers you can observe.

## Run downtime and exit before signing

Switch off a dependency in the test environment. Can staff see the interruption? Can doctors continue under the clinic's approved fallback? What queues for later, who reconciles it, and how does replay avoid duplicates?

Then test exit. Export synthetic patients with notes, attachments, author, dates, corrections, appointments, bills, and audit information included in the agreed scope. Open the export without the vendor's application. Record the format and gaps in the contract.

The final scorecard should keep hard failures separate from preferences. A missing identity review queue is not equivalent to an inconvenient colour scheme.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The scope and plan boundaries are shown on the [India pricing page](https://patientsquare.com/in/pricing/). Patient Square does not establish every multispecialty registration, billing, diagnostic, or accreditation workflow described here. Bring one synthetic cross-specialty journey to a demo and keep any unproved step outside the purchase claim.

---

## NABH Audit Checklist for Hospitals: 6th Edition Prep
https://patientsquare.com/in/blog/nabh-audit-checklist-hospitals-india/
Published 2026-10-09 · Tags: nabh, hospital-audit, quality, india

Prepare an internal NABH audit without copying a paid standards manual: map the 10 chapters, sample evidence, log gaps, assign CAPA, and recheck.

The official 6th Edition uses AAC, COP, MOM, PRE, IPC, PSQ, ROM, FMS, HRM, and IMS: access and continuity, care, medication, patient rights, infection control, safety and quality, management responsibility, facilities, human resources, and information management. Use the official standard for the exact requirements.

An NABH internal audit should make weak evidence visible before an assessor does. It should not be a borrowed spreadsheet where every department ticks "compliant" on Friday afternoon. Start with the exact 6th Edition standard your hospital is using, assign trained reviewers, sample real evidence, and preserve the gap trail.

This article is not an official NABH checklist and does not reproduce the standard. Use it to organise the audit. Map every row to the applicable objective element in the official document.

## Copyable audit control sheet

```text
NABH INTERNAL AUDIT CONTROL SHEET

Hospital and location: __________________
Programme and edition: __________________
Audit scope and dates: __________________
Lead auditor: ____________________________
Approved standard copy/version: __________

CHAPTER | PROCESS OWNER | SAMPLE | EVIDENCE | FINDING | OWNER | DUE | RECHECK
AAC     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
COP     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
MOM     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
PRE     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
IPC     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
PSQ     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
ROM     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
FMS     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
HRM     | _____________ | ______ | ________ | _______ | _____ | ___ | _______
IMS     | _____________ | ______ | ________ | _______ | _____ | ___ | _______

Finding classification: Conformity / Gap / Observation / Not sampled
Immediate safety action, if required: _____
Corrective action and root cause: _________
Evidence accepted by: ____________________
Closure date: ____________________________
```

The control sheet is an index. The real checklist lives in the hospital's licensed standard mapping, approved policies, legal register, committee terms, forms, and department-level audit tools.

## Lock the edition and programme first

The official [NABH Hospital Accreditation Standards, 6th Edition](https://portal.nabh.co/images/Standards/NABH%20Hospital%20Accreditation%20Standard%206th%20Edition%20January%202025.pdf) is dated January 2025. Hospitals also encounter Entry-Level, SHCO, digital health, and other programmes. Their scopes are not interchangeable.

Write the programme, edition, effective date, hospital location, and audit period on every working pack. Keep clarification notes and official notifications with the controlled copy. If a consultant sends a checklist with no edition, do not use it until the quality team maps it.

NABH offers implementation programmes for healthcare teams. Its official [6th Edition implementation programme](https://portal.nabh.co/EventDetails.aspx?id=277) describes training intended to help hospitals build internal counsellors. Use trained reviewers who understand the process they audit and can remain independent enough to challenge it.

## Plan samples across the ten chapters

The 6th Edition chapter codes provide the audit spine. The short descriptions below are navigation aids, not substitutes for the standard.

| Code | Audit lane | Evidence trail to plan |
|---|---|---|
| AAC | Access, assessment, and continuity | Registration, assessment, transfer, referral, and discharge samples |
| COP | Care of patients | Approved care processes, high-risk paths, procedure records, and monitoring |
| MOM | Management of medication | Procurement, storage, orders, administration, reconciliation, and event review |
| PRE | Patient rights and education | Information, consent, privacy, communication, feedback, and grievance handling |
| IPC | Infection prevention and control | Policies, surveillance, practice observation, training, and corrective work |
| PSQ | Patient safety and quality improvement | Indicators, incidents, analysis, committee review, and improvement evidence |
| ROM | Responsibilities of management | Governance, legal compliance, resources, oversight, and meeting actions |
| FMS | Facility management and safety | Utilities, equipment, fire, emergency, maintenance, and drills |
| HRM | Human resource management | Credentials, privileges, induction, competency, training, and records |
| IMS | Information management systems | Medical records, access, completeness, security, retention, and information use |

Choose samples that cross departments. A medication event may touch MOM, COP, nursing competency, quality review, and the medical record. Keep one primary finding, then link the related evidence instead of counting the same gap five times.

## Ask for record, observation, and interview evidence

A policy alone proves that a document exists. It does not prove the process runs. Build each audit step around several evidence types where the standard and risk call for them:

- Controlled policy, procedure, form, or committee record.
- Patient, medication, equipment, training, or incident sample.
- Direct observation of the approved process.
- Interview with the person who performs or oversees it.
- System event, log, report, or reconciliation record.

Use the exact objective element and approved local process to decide what is enough. Do not invent a universal sample size. Record how the sample was selected and why it can answer the audit question.

## Follow one patient across departments

Pick a synthetic drill or an authorized real-record sample under the hospital's privacy policy. Trace admission or registration, assessment, orders, medication, procedure where applicable, results, transfer, discharge, billing handoff, and record closure.

The cross-department trace exposes gaps that isolated checklists miss: a consent in one file, a medication change absent from discharge instructions, a result with no reviewer, or a referral that never closes.

Protect patient information in audit workpapers. Use the minimum identifier needed to trace evidence, restrict access, set retention, and record disposal under the hospital's approved policy.

## Treat medical-record review as evidence, not paperwork

The IMS lane should test whether the hospital can retrieve a complete, legible, dated, attributable, corrected, protected, and retained record under its mapped requirements. The clinical departments still own the content of care; the records team owns parts of the information lifecycle.

Sample difficult records, not only neat discharges. Include an amended note, a transfer, a patient with more than one department, a result after discharge, a scanned external document, and a downtime record. Check the approved process for each.

Software can help locate missing signatures or incomplete fields, but the auditor must inspect meaning. A completed checkbox can sit beside contradictory prose. Automation narrows the search; it does not decide conformity.

## Separate correction from closure

A department can upload a missing form and still leave the root cause untouched. Record the immediate correction, root-cause analysis, corrective action, owner, due date, and recheck as separate fields.

The recheck needs new evidence. If the finding involved three incomplete transfer records, examine the next approved sample after the process change. Meeting minutes saying "staff informed" do not prove the transfer workflow now works.

Escalate an immediate patient or worker safety issue through the hospital's approved response path. The audit calendar does not delay urgent action.

## Verify certificates and vendor language

NABH runs distinct programmes for healthcare organisations and digital health products. "NABH ready," "aligned," and "supports NABH" are marketing phrases unless tied to a verifiable certificate and scope.

Use the [official NABH portal](https://nabh.co/) to verify the organisation or product, programme, certificate number, validity, location, edition, and scope. Keep the verification date in procurement records.

Patient Square does not claim NABH certification. Its AI Medical Scribe produces a draft clinical note for clinician review; it does not make a hospital accredited, write its quality programme, or close audit findings. Patient Square also does not claim ABDM certification today. ABDM remains roadmap work.

## Run a closing meeting that names owners

Send factual findings to process owners before the closing meeting. Let them provide missing evidence, but do not erase the original observation. Record the final classification and adjudicator.

The closing record should contain:

1. Scope, edition, team, and sample method.
2. Findings linked to objective elements and evidence.
3. Immediate actions and safety escalations.
4. Corrective actions, owners, due dates, and rechecks.
5. Open interpretation questions sent to the authorized NABH or legal source.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

If clinicians are completing notes late and the hospital wants to test a drafting workflow, [review the current Hospital Copilot scope](../../products/hospital-copilot/). Keep the NABH audit independent, evidence-led, and owned by the hospital quality system.

---

## HIPAA De-Identification: Safe Harbor vs Expert Determination
https://patientsquare.com/us/blog/hipaa-deidentification-safe-harbor-expert-determination/
Published 2026-10-08 · Tags: hipaa, de-identification, safe-harbor, expert-determination, health-data

Compare HIPAA Safe Harbor and Expert Determination with a practical decision record for dates, free text, data utility, recipients, and release evidence.

The HIPAA Privacy Rule recognizes Safe Harbor and Expert Determination. Safe Harbor removes specified identifiers and requires no actual knowledge that the remaining data can identify a person. Expert Determination uses a qualified expert who concludes and documents that re-identification risk is very small for the data and anticipated recipient.

HIPAA offers two ways to de-identify protected health information: Safe Harbor and Expert Determination. Safe Harbor removes specified identifiers. Expert Determination documents that identification risk is very small for a defined dataset and anticipated recipient. The useful choice depends on the data you need to preserve and the release you can govern.

> Takeaways:
> - Removing names is not enough; Safe Harbor addresses 18 identifier categories.
> - Expert Determination is a documented risk analysis by a qualified expert, not an internal opinion.
> - Dates, free text, rare events, geography, and outside datasets often decide which path fits.
> - Keep a release record that ties the method, data version, recipient, controls, and approver together.

## A date field forces the real decision

A quality team wants to study 30-day readmissions. The analyst needs admission and discharge dates. A privacy reviewer points out that Safe Harbor generally removes date elements more specific than year when they are directly related to an individual. Dropping the dates may break the analysis. Keeping them without a valid method may keep the dataset inside HIPAA.

That is the trade. The [HHS de-identification guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html) explains the two methods under 45 CFR 164.514(b). Safe Harbor follows the specified identifier-removal route and requires no actual knowledge that remaining information could identify the person. Expert Determination requires a person with suitable statistical and scientific knowledge to document that identification risk is very small.

Neither method begins with a tool. Begin with the intended data, recipient, purpose, linkable outside information, and the fields the work cannot lose.

## The method decision record

Use this record before anyone transforms the dataset. A later reviewer should be able to tell what was approved without reconstructing a meeting.

| Decision field | Safe Harbor route | Expert Determination route |
|---|---|---|
| Data need | Analysis can work after specified identifiers are removed | Useful fields would be lost under the fixed removal rule |
| Main test | Remove required identifier categories and retain no actual knowledge of identifiability | Qualified expert documents that risk is very small |
| Context | Rule is applied to the dataset; actual knowledge still matters | Dataset, anticipated recipient, environment, controls, and outside data shape the analysis |
| Dates and geography | Detail is sharply limited by the rule | Detail may be retained if the expert's documented result supports it |
| Evidence | Field inventory, transformation rule, validation result, release approval | Expert report, methods, results, conditions, data version, release approval |
| Change trigger | New columns, free text, data source, or known identification route | Any change that can alter the expert's assumptions or risk result |

The record should name a versioned dataset. "Claims extract" is not enough if next month's extract contains two new quasi-identifiers and an unreviewed notes column.

## Safe Harbor is mechanical until it isn't

The [regulation at 45 CFR 164.514](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.514) lists the Safe Harbor identifiers and adds the actual-knowledge condition. That second part matters. A dataset can pass a field checklist while a covered entity knows that a rare occupation, event, or combination points to one person.

Free text deserves its own test. A clinical note can contain a name, phone number, exact date, workplace, location, record number, or a unique story. Removing structured columns does not clean the narrative. Run realistic samples through the transformation, then inspect misses and false confidence.

Codes need care too. The rule permits a code or other means of record identification in limited circumstances, but the code cannot be derived from information about the person, and the mechanism for re-identification cannot be disclosed. Tokenizing a medical record number with a reversible house key is not automatically a public de-identification method.

## Expert Determination keeps utility under conditions

HHS says there is no single numerical threshold that universally defines "very small" identification risk. The expert considers the data and the environment in which it is expected to be used. HHS also requires the methods and results that justify the determination to be documented.

That flexibility can preserve dates, finer geography, or other fields needed for valid analysis. It also creates conditions. The conclusion may assume a named recipient, contract limits, access controls, no onward disclosure, a specific outside-data environment, or a fixed dataset. Change those facts and the old determination may no longer answer the new release.

Ask the expert report to state its dataset fingerprint, anticipated recipients, data-use conditions, transformations, risk measures, unresolved limits, and re-evaluation triggers. Store it with the release record, not in an inbox.

## An AI dataset pressure test

Suppose a team wants 20,000 old notes to evaluate a summarization model. The easiest mistake is to remove patient names and call the rest anonymous. Notes can contain dates, clinicians, relatives, addresses, workplaces, facilities, rare diagnoses, and singular events. Model prompts, evaluation exports, and error logs can create new copies after the original transformation.

Write four boundaries before release:

1. the source fields and note sections included;
2. the de-identification method and evidence;
3. every recipient and processing environment; and
4. the outputs, logs, retention, deletion, and onward-use limits.

Then test sampled records. Record residual identifiers and alter the method. A pass rate invented for the project would be worse than no number, so use documented acceptance rules and human review proportionate to the risk.

## De-identified is not the same as a limited data set

The HIPAA Privacy Rule also defines a limited data set under 45 CFR 164.514(e). It can retain some information that Safe Harbor would remove, but it remains protected health information and requires a data use agreement for permitted purposes. Do not use "limited" and "de-identified" as synonyms in architecture diagrams or contracts.

We think every release needs a one-page cover sheet: data version, method, evidence location, recipient, permitted purpose, controls, expiry, onward-disclosure rule, and owner. Boring paperwork is useful when someone asks six months later why exact dates left the source system.

## Product scope stays separate

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

This article does not claim that Patient Square turns clinical notes into de-identified datasets or provides Expert Determination. For product privacy and security questions, use the [Patient Square security page](../../security/) and the [AI scribe data-ownership guide](../ai-scribe-data-ownership-export/). If you are mapping an AI feature that may receive PHI, the [HIPAA-compliant AI feature card](../hipaa-compliant-ai/) covers the live-service review rather than secondary data release.

---

## Letter of Medical Necessity Template: Build an Evidence Spine
https://patientsquare.com/us/blog/letter-of-medical-necessity-template/
Published 2026-10-08 · Tags: medical-necessity, prior-authorization, payer-documentation, clinical-documentation, physician-workflow

A letter of medical necessity template that maps payer criteria to dated chart evidence, prior treatment, requested service, and clinician review.

A letter of medical necessity should connect the requested service to dated chart evidence, applicable payer criteria, prior care, and a clinician-reviewed request. Use a reusable evidence structure, then adapt it to the current benefit, policy, and patient record.

The blank letter is the easy part. The hard part is proving that every sentence points back to the current payer rule and the patient's dated record.

A generic letter of medical necessity template can organize that proof. It cannot decide which benefit applies, invent missing documentation, or turn a clinician's conclusion into sufficient evidence by itself. The useful template is an evidence spine: criterion, patient fact, source record, and requested service in one traceable line.

## Start with the request instructions

Before drafting, save the payer's current request instructions and the coverage material that applies to the patient's plan, item, or service. Record where the rule came from and when staff retrieved it.

Coverage requirements can vary by payer and can change. For Medicare, national and local coverage materials can be searched through the [Medicare Coverage Database](https://www.cms.gov/medicare-coverage-database/). A commercial or Medicaid plan may use a different source and submission path. Staff should not reuse a prior patient's checklist without checking the current request.

Create a short control block:

| Control | Value to record |
|---|---|
| Payer and plan | Exact entity and product named in the record |
| Requested item or service | Plain-language name plus required code, if applicable |
| Policy | Title, identifier, version or effective date, and URL or saved copy |
| Submission rule | Required form, channel, attachments, signature, and deadline |
| Owner | Person responsible for submission and response tracking |

If staff cannot identify the governing material, that is a workflow exception. Do not hide it by drafting more forceful prose.

## Map each criterion to a chart location

Read the coverage criteria before opening the letter. Build a private worksheet that the clinician can verify.

| Payer criterion | Patient-specific fact | Record location | Status |
|---|---|---|---|
| Criterion text or faithful summary | Documented patient fact | Note or report, author, and date | Met, not met, or unclear |
| Criterion text or faithful summary | Documented patient fact | Note or report, author, and date | Met, not met, or unclear |

This table is not a place to stretch the record. "Unclear" means the reviewer needs clarification or the request packet is not ready. A missing fact should not become a confident statement because the template has an empty field.

CMS documentation guidance illustrates the larger principle. For evaluation and management services, CMS tells clinicians to document the reason for the encounter, relevant history and findings, assessment, rationale for ancillary services, plan, date, and clinician identity ([CMS E/M guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)). The exact requirements for a medical-necessity request depend on its own policy, but the signed record remains the source of patient facts.

## Use the template as a controlled draft

Replace every bracketed instruction. Delete sections that do not apply instead of filling them with boilerplate.

```text
PRACTICE LETTERHEAD
DATE: ____________________

To: ____________________
Patient full name: ____________________
DOB: ____________________
Member ID: ____________________
Request or reference number: ____________________

REQUESTED ITEM OR SERVICE
Item or service: ____________________
Dose, quantity, frequency, duration, or setting when required:
________________________________________________________________

CLINICAL CONDITION AND CURRENT EFFECT
Verified diagnosis or clinical problem: ____________________
Onset and dated course: ____________________
Functional effect and pertinent findings: ____________________
Source notes and test dates: ____________________

APPLICABLE COVERAGE CRITERIA
Policy title and identifier: ____________________
Version or effective date: ____________________
Relevant criterion: ____________________
Patient fact supporting the criterion: ____________________
Source, author, and date: ____________________

PRIOR CARE AND RESPONSE
Treatment or conservative measures, dates, and duration: ____________________
Documented response, intolerance, contraindication, or reason a step did not apply:
________________________________________________________________

RATIONALE FOR THIS REQUEST
Patient-specific clinical reasoning connecting the current condition and
evidence to the requested item or service:
________________________________________________________________

SUPPORTING RECORDS
Named notes, orders, reports, imaging, results, treatment logs, and payer forms:
________________________________________________________________

REQUESTED REVIEW
Policy or benefit for review: ____________________
Approved clinical contact and channel: ____________________

Sincerely,
Clinician name, credentials, and required identifiers: ____________________
Signature and date: ____________________
```

This is a drafting aid, not legal, billing, or coverage advice. The clinician and revenue-cycle team should adapt it to the actual payer process.

## Write chronology instead of adjectives

"Severe," "failed," and "necessary" are conclusions. A reviewer needs the observations underneath them.

Prefer a dated sequence:

- symptom or functional change and when it began;
- examination, test, or assessment findings with dates;
- prior treatment, dose or duration when relevant, and observed response;
- contraindication or intolerance supported by the record; and
- the present effect on function, care, or risk as documented by the clinician.

Do not turn "patient did not return" into "treatment failed." Do not turn "medication discussed" into "medication trial completed." Those substitutions make the letter cleaner and the evidence worse.

## Attach the record the letter cites

For some Medicare DMEPOS claims, CMS states that a physician order, certificate, supplier-prepared statement, or physician attestation by itself does not provide sufficient documentation of medical necessity, even when signed ([CMS Article A55426](https://www.cms.gov/medicare-coverage-database/view/article.aspx?articleid=55426)). That example should not be generalized into one rule for every payer or service. It does show why a letter cannot be treated as a replacement for the underlying record.

Name each attachment in the letter and in the submission checklist. Use dates and document types. If the payer asks for a physical-therapy note, send the required note through the approved channel rather than copying one sentence from it and assuming the summary will suffice.

Before submission, reconcile the letter against the attachments. A stale medication list, changed diagnosis, mismatched laterality, unsupported duration, or wrong policy date can break the chain.

## Keep codes subordinate to evidence

Codes can route a request and express the service or diagnosis in a standard field. They do not prove that a coverage criterion is met.

Verify that every submitted code matches the current code set, the requested service, the payer instruction, and the signed record. If software suggests an ICD-10 code, keep it in suggestion status until a qualified reviewer confirms it. Do not add a more specific diagnosis merely to fit a form.

For a deeper prior-authorization workflow, see [Prior Authorization Documentation: Build a Submission Packet That Survives Review](../prior-authorization-documentation/). The letter is one artifact inside that packet, not the whole process.

## Control version, signature, and submission

Treat the draft as a controlled clinical document.

The clinician should see the exact version being signed. After approval, prevent silent edits or require a new review. Preserve the author, reviewer, signature time, attachments, destination, transmission evidence, and payer response under the organization's retention policy.

Do not place a signature image into a regenerated letter and call that clinician review. The approval event needs to bind the clinician to the actual content submitted.

CMS's documentation fact sheet points practices to service-specific guidance because requirements differ across items and services ([CMS MLN909160](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/certmedrecdoc-factsheet-icn909160.pdf)). The workflow should therefore record the requirement source for each request, rather than maintaining one undated master checklist.

## Test the process with one returned request

Choose a de-identified or synthetic case modeled on a recent request for more information. Ask a staff member who did not prepare it to reconstruct:

1. which policy version governed the request;
2. where each criterion appeared in the record;
3. which attachments were sent;
4. what the clinician approved; and
5. what the payer returned and who handled it.

If reconstruction requires searching email, a fax console, the EHR, and a shared drive with no common identifier, the letter template is not the bottleneck. Fix the packet index and status ownership.

CMS's prior-authorization API guidance describes coverage-requirement discovery as a way for an impacted workflow to identify whether authorization is required and what documentation is needed; the discovery response alone is not the authorization request ([CMS Prior Authorization API FAQ](https://www.cms.gov/initiatives/burden-reduction/overview/interoperability/frequently-asked-questions/prior-authorization-api)). The same separation helps manual workflows: discovering requirements, assembling evidence, submitting, and receiving a decision are distinct events.

## The Patient Square boundary

Patient Square's public US pricing describes review-ready SOAP notes, ICD-10 suggestions, eRx drafts, and EHR-ready exports ([Patient Square pricing](https://patientsquare.com/us/pricing/)). It does not claim payer-policy interpretation, automatic coverage determination, autonomous coding, claim submission, or insurer approval.

A reviewed note draft may help staff locate current clinical facts. The letter still needs the payer-specific rule, required attachments, clinician judgment, signature, and controlled submission path.

[Review the published product scope](/us/products/practice-copilot/).

The strongest letter of medical necessity is not the one with the most emphatic language. It is the one in which a reviewer can move from criterion to patient fact to dated record without guessing.

---

## Medical Necessity Documentation: A Claim-to-Note Check
https://patientsquare.com/us/blog/medical-necessity-documentation-checklist/
Published 2026-10-08 · Tags: medical-necessity, clinical-documentation, claims, practice-operations

Use a claim-to-note check to connect the ordered service, patient-specific findings, clinical rationale, and follow-up without inventing documentation.

A medical necessity record should connect the patient-specific problem and findings to the service ordered or performed and the clinician’s rationale. Check that the note, order, and claim agree, then compare them with the applicable payer rule; a diagnosis code alone does not establish necessity.

A denial letter says the record did not support medical necessity. The note contains a diagnosis, a normal-looking template, and a plan to perform the service. What it does not contain is the clinician's patient-specific reason for choosing that service now.

Medical necessity documentation should connect five things: the patient's current problem, relevant findings, prior response or risk, the ordered service, and the clinician's rationale. An ICD-10 code cannot make that connection by itself. Use the record to explain the clinical decision, then make sure the order, note, and claim describe the same event.

> **Takeaways for the documentation team**
> - Start with the coverage requirement, not a generic note template.
> - Record the patient's facts and the clinician's reasoning in their own lanes.
> - Compare the signed note with the order, claim, and attachments before submission.
> - Never add a symptom, finding, or failed treatment merely to satisfy a checklist.

## Build the chain before checking the prose

Medical necessity is not one sentence hidden under Assessment. It is a chain that a reviewer can follow without guessing.

| Link | Record the patient-specific answer | Common weak substitute |
| --- | --- | --- |
| Current problem | What symptom, impairment, risk, or change is being addressed today? | A diagnosis copied from the problem list |
| Relevant evidence | Which history, examination, test, or prior record informs the decision? | Every field in a broad template |
| Prior response | What was tried, what happened, and why does that matter now? | "Failed conservative care" with no detail |
| Service | What is being ordered, performed, or continued? | A vague plan such as "proceed" |
| Rationale | Why is this service appropriate for this patient at this time? | A policy phrase pasted into the note |
| Follow-up | What result, response, or next decision will the team track? | No accountable next step |

The chain changes with the service. A diagnostic test, therapy course, medication, procedure, and durable medical equipment item do not share one universal checklist. Read the applicable coverage policy and payer instruction before deciding which facts belong in the record.

CMS tells providers that medical-record entries should be complete, dated, timed, and authenticated, and that documentation needs to support the services billed ([CMS medical-record requirements](https://www.cms.gov/files/document/mln4840534-medical-record-maintenance-and-access-requirements.pdf)). That is a record standard, not permission to write a coverage conclusion that the clinician did not make.

## Separate clinical facts from coverage language

Coverage policies often name indications, exclusions, or documentation elements. Use them as a pre-service prompt for the clinician, not as text to paste after the visit.

Suppose a policy asks about symptom duration, a prior treatment, and a relevant examination finding. The useful workflow places those prompts where the clinician can answer them during care. The unsafe workflow inserts affirmative statements into the note because the claim needs them.

The distinction is simple:

- the policy can ask the question;
- the clinician supplies the answer;
- the record keeps the actual answer, including "not present" or "unknown"; and
- the billing team checks alignment without changing the clinical facts.

CMS's E/M compliance guidance makes a related point: medical necessity is the main payment criterion for a service in addition to the individual requirements of a CPT code ([CMS](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)). More documented work does not automatically justify a higher service.

## A code is an index, not the argument

An ICD-10 suggestion can help a clinician find a candidate code. It does not prove the condition, establish severity, or explain why an ordered service is reasonable and necessary.

Check the claim-to-note chain in both directions. From the claim, locate the exact service, date, clinician, diagnosis, and any modifier in the source record. From the note, confirm that its plan and clinical rationale agree with the order and billed event. If the claim says one side, frequency, or unit count and the note says another, stop the submission and resolve the source discrepancy.

For related controls, use the [claim-denial documentation guide](../ai-scribe-claim-denials-documentation/) and the [prior-authorization documentation guide](../prior-authorization-documentation/). The first looks backward from a denial; the second helps teams gather requirements before a payer decision.

## Review a source packet, not an isolated note

A reviewer may need more than the encounter note. Assemble only the documents relevant to the request and confirm that they agree.

| Source | Alignment question |
| --- | --- |
| Order | Does it identify the intended service, ordering clinician, patient, and date? |
| Encounter note | Does it contain the patient-specific facts and rationale? |
| Test or prior-treatment record | Does it support the history stated in the note? |
| Authorization record | Does the requested service match the performed or planned service? |
| Claim | Do service, date, units, diagnoses, and clinician agree with the source record? |
| Attachment index | Can a reviewer tell what was sent without searching unrelated records? |

CMS warns that insufficient documentation includes records that are absent or do not support that services were reasonable and necessary ([CMS MLN documentation booklet](https://www.cms.gov/files/mln909160-complying-with-medical-record-documentation-requirements.pdf)). Sending a larger packet does not repair a missing clinical explanation. It can instead bury the useful evidence and disclose unnecessary information.

## Repair errors without rewriting history

If the signed note contains an error, use the organization's correction or addendum process. Preserve the original, identify the author and actual entry time, and state the reason. The [record amendment comparison](../medical-record-amendment-correction-addendum/) explains why a clinician correction differs from a patient amendment request.

Do not backdate an entry or compose a confident narrative from billing-team assumptions. If the clinician cannot truthfully supply the missing fact, the gap remains a gap. A clean denial is preferable to a manufactured record.

Track the denial reason separately. Was the evidence absent from the clinical record, omitted from the packet, inconsistent with the claim, or judged insufficient under the policy? Those failure modes need different fixes.

## Put AI on the drafting side of the line

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan.

The scribe output is a draft. A clinician reviews it before signing. Public scope does not promise a medical-necessity determination, autonomous coding, claim submission, or automatic write-back into another EHR. Any prompt tied to a payer policy should preserve the clinician's real answer rather than manufacture a qualifying statement.

Review current data-handling statements on the [security page](../../security/). In a demo, use a synthetic case with one missing policy element, one conflicting order, and one unsupported ICD-10 suggestion. Ask the team to show exactly where the clinician reviews each item.

## Run ten records through the check

Choose ten recently completed services with synthetic or properly authorized review data. For each, trace the current problem, evidence, prior response, service, rationale, and follow-up. Compare the note with the order and claim. Record the first broken link and its owner.

Do not score success by note length. Score whether a trained reviewer can understand the decision from truthful, patient-specific documentation and whether every submitted item agrees with that record.

Compare the [Practice Copilot scope](../../products/practice-copilot/) with that claim-to-note chain using a synthetic case.

---

## Prior Authorization Appeal Documentation: Build the Packet
https://patientsquare.com/us/blog/prior-authorization-appeal-documentation/
Published 2026-10-08 · Tags: prior-authorization, appeals, medical-necessity, claims

Classify the denial, follow the notice, and build a prior authorization appeal packet that connects payer criteria to patient-specific evidence.

Start with the denial notice to identify the reason, review route, deadline, and required format. Build an indexed packet that connects the plan’s criteria to patient-specific records and the clinician’s rationale, without inventing missing evidence or treating a correctable submission error as a formal appeal.

The denial fax lands at 4:42 p.m. One person sends the same records again. Another starts a peer-to-peer request. A third drafts an appeal letter. None has read the reason code or deadline.

Begin a prior authorization appeal by classifying the denial. An administrative omission, coverage exclusion, medical-necessity decision, and untimely request do not share one repair path. Read the notice, identify the controlling plan instruction, then map each disputed criterion to patient-specific evidence. The packet should make that map visible.

> **Before anyone writes a letter**
> - Save the denial notice and record when it arrived.
> - Capture the exact reason, requested service, identifier, deadline, and review route.
> - Decide whether the response is a correction, reconsideration, peer review, or appeal.
> - Name one owner and use one packet index.

## Route the denial before assembling records

Use the notice, benefit documents, and payer instructions as the controlling sources. This table is a sorting aid, not a substitute for those materials.

| Denial pattern | First question | Likely evidence task |
| --- | --- | --- |
| Missing field, identifier, or attachment | Does the plan allow a corrected request? | Supply the exact missing item and preserve submission history |
| Service does not meet stated criteria | Which criterion is disputed? | Link each criterion to a dated patient fact or explain the disagreement |
| Benefit exclusion or noncovered service | Is this a benefit issue or a clinical-necessity issue? | Use plan language and the correct coverage-review route |
| Timeliness or no prior request | What deadline and exception rule applies? | Build the event timeline with transmission evidence |
| Level, site, frequency, or unit mismatch | What exactly did the request and denial identify? | Reconcile order, note, code, units, and authorization identifier |
| Urgent clinical risk | Does the plan provide an expedited route? | Document the clinician's patient-specific urgency and follow that route |

CMS's consumer appeal guidance illustrates why the notice matters: it describes internal appeals and external review for certain non-grandfathered health plans, with distinct procedures and time frames ([CMS](https://www.cms.gov/cciio/resources/fact-sheets-and-faqs/appeals06152012a)). Those federal examples do not create one deadline for every request. State law, plan type, service, and contract can change the path.

## Turn the denial into an evidence map

Do not begin with a broad template letter. Copy the denial reason into a working document, split it into testable criteria, and place the source beside each one.

| Denial criterion | Patient-specific source | Packet locator | Owner |
| --- | --- | --- | --- |
| Current clinical problem | Signed encounter note dated MM/DD | Tab 2, page 3 | Clinician |
| Relevant finding or test | Report dated MM/DD | Tab 3, page 1 | Records team |
| Prior treatment and response | Medication or therapy history | Tab 4 | Clinician |
| Requested service | Signed order and request | Tab 1 | Authorization staff |
| Timing or urgency | Dated clinician statement | Tab 2, page 4 | Clinician |

The map exposes three different problems. The fact may exist but be absent from the packet. The record may contradict the request. Or the fact may never have been documented. Only the first is solved by attaching another page.

Use the [medical-necessity claim-to-note check](../medical-necessity-documentation-checklist/) before asking a clinician for more prose. The [prior-authorization documentation guide](../prior-authorization-documentation/) helps teams collect the initial requirement set.

## Make the packet navigable

A useful submission starts with a short index. Identify the patient and request using the payer's permitted identifiers. State the denial date, reference number, requested review, and attached documents. Put the clinician's response next to the disputed criterion instead of hiding it in a chronology.

Keep unrelated chart material out. More pages can create privacy exposure and make the relevant evidence harder to find. Check that every attachment belongs to the right patient, date, service, and clinician before transmission.

CMS publishes electronic reason statements and document codes for its esMD workflows so a submitter can understand why a transaction was rejected or what document type was received ([CMS esMD](https://www.cms.gov/data-research/computer-data-systems/esmd/reason-statements-and-document-emdr-codes)). That example supports a broader operations lesson: retain the exact response code and transmission evidence. Do not translate a specific rejection into "payer denied" and discard the details.

## Keep the record and argument separate

The clinical record should state what the clinician knew and decided during care. The appeal explains how that truthful record answers the denial. Do not edit the chart to make it read like a payer policy.

If a correction or addendum is warranted, follow the authorized workflow and preserve the original. The [record amendment guide](../medical-record-amendment-correction-addendum/) covers that boundary. A late entry must show its actual author and date; it cannot pretend that later reasoning was contemporaneous.

The appeal letter should also distinguish fact from argument:

- **Fact:** the patient completed six weeks of documented therapy on stated dates.
- **Source:** the signed therapy record at a named packet tab.
- **Argument:** that history satisfies or should be considered under the cited criterion.
- **Request:** the specific decision or review the practice seeks.

If the clinician disagrees with the policy, say so directly and support the position. Do not manufacture a fact that would fit it.

## Know which new CMS rules apply

The CMS Interoperability and Prior Authorization Final Rule requires certain impacted payers to provide a specific reason for denied prior authorization decisions, with compliance dates that vary by provision. Its prior-authorization API and process provisions focus on medical items and services and exclude drugs of any type from that rule's scope ([CMS fact sheet](https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-prior-authorization-final-rule-cms-0057-f)).

Do not turn that into "all payers must decide every request the same way." Confirm whether the payer and request fall within the rule, which compliance date applies, and whether another federal or state requirement governs. For Medicare hospital outpatient department services, CMS maintains a separate FAQ and operational pathway ([CMS OPD FAQ](https://www.cms.gov/files/document/opd-frequently-asked-questions.pdf)).

## Put software in the evidence lane

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan.

The scribe prepares a draft for clinician review. Public scope does not promise payer-policy interpretation, autonomous appeal writing, appeal submission, or a coverage outcome. Hospital Copilot names a Claims Management module, but public materials do not establish a specific prior-authorization appeal workflow. Treat that as a demonstration question.

Review current statements on the [security page](../../security/). In a demo, use a synthetic denial and ask the team to show source attribution, clinician review, attachment handling, and any handoff that remains outside Patient Square.

## Close the loop on the decision

Record the submitted route, packet version, transmission time, confirmation, deadline, and owner. When the response arrives, preserve the notice and connect it to the original request. If the result is another denial, classify it again rather than reflexively resending the same packet.

The best operational metric is not letters produced. It is denials correctly routed, evidence gaps found before submission, deadlines met, and decisions returned to the clinical and scheduling teams without losing the patient in an inbox.

Compare the [Practice Copilot scope](../../products/practice-copilot/) with your denial workflow using a synthetic case.

---

## EHR Downtime Plan for Medical Practices: First 30 Minutes
https://patientsquare.com/us/blog/ehr-downtime-plan-medical-practice/
Published 2026-10-07 · Tags: ehr-downtime, contingency-planning, hipaa, practice-operations, patient-safety

Use a 30-minute EHR downtime plan to protect the patient schedule, keep approved paper records, control access, and reconcile every item after recovery.

A medical practice should declare the outage, assign an incident lead, and switch to its approved downtime procedures. Staff need a safe way to identify patients, document care, handle orders, and track unfinished work; after service returns, they must reconcile each paper or offline item into the record.

At 8:07 on a fully booked Tuesday, the schedule screen stops loading. One receptionist starts a spreadsheet. A medical assistant takes a phone photo of yesterday's list. A clinician writes on the back of a referral. The outage is now three record systems, and recovery will be worse than the downtime.

An EHR downtime plan stops that split. In the first 30 minutes, confirm the outage, put one person in charge, switch every role to approved forms, protect patient identity and urgent information, and create a reconciliation queue. The plan covers care continuity and ePHI protection alongside IT recovery.

> **The working rules**
> - One incident lead declares the operating state and owns the clock.
> - Keep a printed or otherwise approved downtime packet outside the unavailable EHR.
> - Separate clinical continuity from vendor recovery. Both need owners.
> - Recovery ends only after every paper note, order, result, charge, and message is reconciled.

## An outage is an operating state, not a blank screen

The HIPAA Security Rule's contingency-plan standard requires covered entities to prepare for emergencies or occurrences that damage systems containing electronic protected health information. HHS breaks that standard into data backup, disaster recovery, emergency-mode operations, testing and revision procedures, and application and data criticality analysis ([HHS audit protocol](https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/audit/protocol/index.html)).

That legal frame matters, but it does not tell the receptionist which schedule to trust at 8:09. The [2025 ASTP/ONC SAFER contingency guide](https://healthit.gov/resources/2025-safer-guide-contingency-planning/) fills the operational gap. It treats planned and unplanned EHR unavailability as a patient-safety problem and calls for clinician participation in substitute workflows.

A small practice therefore needs two linked plans:

- the technical response that diagnoses, contains, restores, and verifies the system; and
- the clinical operating response that manages patients while the system is unavailable.

The same person may coordinate both in a tiny clinic. The responsibilities are still different.

Use the [HIPAA app-architecture checklist](../hipaa-compliant-app-architecture-checklist/) to connect this operating plan to access, logging, backup, and vendor controls. The [EHR data-migration guide](../ehr-data-migration-guide/) covers a different continuity event: moving records deliberately rather than working through an outage.

## The first 30-minute card

Print this card, tailor it to the practice, and keep it with approved downtime forms. A plan trapped inside the unavailable EHR is decorative.

| Clock | Incident lead | Front desk | Clinical team | IT or vendor contact |
| --- | --- | --- | --- | --- |
| 0-5 minutes | Confirm scope, record start time, declare the downtime state | Stop unsanctioned workarounds and use the approved schedule source | Finish any immediately time-sensitive action under the clinical escalation policy | Open the approved support path and preserve incident details |
| 5-15 minutes | Assign one communication channel and set the next update | Verify each patient's identity against the downtime source | Use approved forms; record author, date, time, encounter, decisions, and orders | Determine whether the event is local, vendor-wide, security-related, or power/network related |
| 15-30 minutes | Decide whether the patient day continues, narrows, or pauses | Mark arrivals, cancellations, calls, and reschedules in one queue | Flag orders, results, medications, referrals, and follow-ups that need later reconciliation | Give an evidence-based status, not an invented restoration time |
| Recovery | Open the reconciliation log and retain the incident record | Re-enter or route schedule changes once | Reconcile every signed note and outstanding clinical item through the approved process | Verify availability, integrity, access, and any security response before closure |

The AAFP's 2026 outpatient downtime guidance makes the same practical point: procedures should cover paper scheduling, visit documentation, billing, communications, prescriptions, orders, results, and referrals ([AAFP Family Practice Management](https://www.aafp.org/fpm/2026/0300/preparing-for-downtime.html)). A single blank SOAP form is not a downtime plan.

## Build one approved packet before the outage

The packet should be boring. That is a compliment.

Start with a role sheet. It names who may declare downtime, who leads, who contacts each vendor, who makes clinical continuation decisions, and who owns reconciliation. Include alternates. The person who wrote the policy may be on a flight when the router dies.

Then add approved forms for the work the clinic has chosen to continue. At minimum, the practice should decide how it will handle:

- patient identification and the current schedule;
- encounter documentation with author, date, and time;
- allergies, medications, urgent history, and other information the clinical policy requires;
- orders, results, referrals, prescriptions, and follow-up tasks;
- charges and coverage information if those processes continue; and
- custody of every paper or offline artifact until reconciliation.

Do not print a full patient database merely because printing is possible. The risk analysis should decide what minimum information must remain available, where it is kept, who can reach it, and how stale copies are replaced. HHS requires protection of ePHI during emergency-mode operations, not unlimited copies in an unsecured drawer.

## Patient identity is the hard part

Most downtime errors start before anyone writes a note. The wrong chart label, yesterday's schedule, two patients with similar names, or a handwritten callback number can poison the recovery queue.

Make identity verification explicit on every downtime form. Pick the identifiers and exception path in advance. Assign one temporary encounter or packet number if the practice needs it. Never let individual staff invent numbering systems at different desks.

The packet also needs a visible version date. When the practice changes locations, vendors, phone trees, or EHRs, old copies should be removed. A flawless 2024 plan with a disconnected support number is not a plan in 2026.

## Downtime may also be a security incident

An outage does not prove a cyberattack. It also does not rule one out.

Staff need a separate escalation cue for suspicious events: ransom messages, unexpected account lockouts, altered data, unusual login prompts, or vendor notices. The incident lead should preserve evidence and follow the approved security response instead of repeatedly rebooting devices or moving PHI into personal email. HHS notes that contingency planning supports availability during ransomware and other emergencies, while incident response addresses containment and recovery ([HHS ransomware guidance](https://www.hhs.gov/hipaa/for-professionals/security/guidance/cybersecurity/ransomware-fact-sheet/index.html)).

Write the rule plainly: normal outage troubleshooting stops when the security escalation path begins.

## Recovery is a queue, not an announcement

"The EHR is back" is the midpoint.

Open one reconciliation log. Each downtime artifact gets an owner and a terminal state. The practice decides how the source document is retained, how the electronic record identifies a delayed entry, and which person confirms completion. Do not hide the gap by copying text into a chart with a false encounter time.

| Recovery item | Minimum check before closure |
| --- | --- |
| Encounter note | Correct patient, author, service date, actual entry time, signature, original artifact retained per policy |
| Order or referral | Correct destination, transmission confirmed, duplicate risk checked |
| Result | Routed to the responsible clinician, acknowledgment and follow-up handled |
| Medication or prescription | Authorized clinician review complete; duplicate or conflicting action checked |
| Appointment or message | Final schedule and callback queue agree |
| Charge | Service, date, clinician, and supporting record match |

Close the incident only when the log reaches zero or an accountable owner accepts each remaining exception. Keep the after-action note short: what failed, what nearly failed, the owner, and the deadline.

## What to make a vendor demonstrate

Cloud hosting does not erase the practice's continuity responsibility. Ask the EHR or practice-software vendor to run a synthetic outage in front of you.

Request the actual support route, status communication, backup and recovery commitments, export options, access logs, and restoration testing described in the contract. Then test the practice side: schedule access, identity checks, documentation, pending results, order status, and reconciliation. A slide that says "99.9%" cannot show what Tuesday morning looks like.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Public scope does not promise automatic failover, an offline chart mirror, or write-back to another EHR. Those are discovery questions.

Use the [security page](../../security/) to inspect current data-handling claims, then read the [Practice Copilot scope](../../products/practice-copilot/). During a product evaluation, bring a downtime scenario and ask the presenter to show the boundary, the failure, and the recovery evidence. A polished happy path can wait.

## Run a 20-minute drill next Friday

Pick five synthetic patients: one routine follow-up, one same-name identity risk, one prescription question, one pending result, and one referral. Disable normal access for the drill. Watch where staff reach for personal devices, stale lists, or memory.

The result is not a pass or fail grade. It is a repair list. Update the packet, name the owners, and schedule the next test. The HHS audit protocol explicitly examines testing and revision, and the SAFER guide treats maintenance as continuing work. A downtime plan improves when it has embarrassed the practice safely, before a real outage gets the chance.

---

## Healthcare Task Management Software: Keep PHI Out of the Wrong Board
https://patientsquare.com/us/blog/healthcare-task-management-software/
Published 2026-10-07 · Tags: task-management, hipaa, healthcare-software, security, workflow

Evaluate healthcare task software with a PHI boundary, business-associate review, minimum-data task card, access-removal drill, and export test.

Healthcare task software should be evaluated against the data it handles, the people who can access it, and where completed work enters the clinical record. Test vendor obligations, minimum necessary data, access removal, and export before choosing a board.

Before creating a patient-linked card, open the product's notification preview, guest controls, mobile sessions, audit history, and user-removal screen. Those five places reveal more about the proposed healthcare use than a gallery of board layouts.

Healthcare task management software should make ownership and next action visible while keeping the authoritative clinical record where the practice intends. That requires a data boundary, a review of vendor access, and an offboarding test before clinical work enters the tool.

Evaluate that path before comparing views, colors, or automation.

## Draw a red, yellow, and green data boundary

Begin with three categories approved by the practice's privacy and security owners.

| Boundary | Example operating rule |
|---|---|
| Green | Non-patient operational work may use the approved workspace |
| Yellow | A permitted patient reference and minimum task detail require the approved healthcare configuration and workflow |
| Red | Full notes, credentials, exports, or sensitive attachments stay out unless explicitly approved for that use |

These are design labels, not legal conclusions. The practice must define them from its use case, risk analysis, contracts, policies, and applicable law.

HHS explains that a cloud service provider that creates, receives, maintains, or transmits electronic protected health information for a covered entity or business associate is itself a business associate, even when it cannot view encrypted data. The [HIPAA cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html) also says the parties need an applicable business associate agreement and that the customer retains its own Security Rule duties.

Do not infer approval from a “HIPAA-ready” badge. Review the exact service, plan, configuration, subcontractors, data locations, support path, and written agreement for the proposed use.

## Keep the task card smaller than the chart

A task needs enough context for the assigned person to act. It does not need to become a second medical record.

Use a compact card:

```text
Approved reference: __________________
Action: ______________________________
Owner: _______________________________
Due state: ___________________________
Authoritative record link or location: __________
Escalation role: _____________________
Final disposition recorded at: __________________
```

Avoid diagnoses, copied notes, images, results, and long message threads when a permitted reference and secure route to the authoritative record will do. Decide what notifications display on lock screens, email previews, and browser tabs. The most careful card can still leak through an overly descriptive alert.

## Determine the vendor's role from actual access

Software companies are not automatically business associates. HHS says a vendor that merely sells software and does not need access to a covered entity's PHI is not a business associate for that reason alone. When a vendor needs PHI access to provide its service on the covered entity's behalf, the analysis changes. The HHS FAQ on [software vendors and business-associate status](https://www.hhs.gov/hipaa/for-professionals/faq/is-software-vendor-business-associate/index.html) gives that distinction.

Ask concrete questions:

- Can vendor staff access workspace content for support?
- Which subprocessors maintain or transmit the data?
- Is a business associate agreement available for the exact plan?
- Can administrators restrict guests, public links, exports, and integrations?
- What audit events can the practice retrieve?
- How are backups, deletion, incidents, and account closure handled?

Record the answers and the person who approved the intended use. A sales statement should not be the only evidence.

## Run the former-worker drill

Create synthetic tasks and a test user. Give that user only the access expected for the role. Assign a task, change its owner, and remove the user as though their employment or contract had ended.

Check every route the user may still possess:

1. web session;
2. mobile session;
3. email notifications;
4. shared links;
5. downloaded exports;
6. connected calendar or automation;
7. API token or integration, if applicable.

Time how long removal takes and save evidence from the administrative log. If access depends on a person remembering seven separate screens, the practice has found an operational risk before live use.

NIST Special Publication 800-66 Revision 2 maps HIPAA Security Rule standards to practical security considerations and other NIST resources. Its [resource guide](https://csrc.nist.gov/pubs/sp/800/66/r2/final) can support the practice's assessment, but it does not certify a vendor or replace a use-specific risk analysis.

## Test the final disposition

The board may coordinate work, but the clinical outcome often belongs in the EHR or another designated record. Pick a fictional task such as reviewing an incoming document. Complete it in the board, then verify where the actual review and patient communication are recorded.

Ask two people to find the final state without coaching. If one relies on the board and the other relies on the chart, define which one is authoritative and how the two reconcile. “Done” must mean more than moving a card to the rightmost column.

Also test correction. Change the task after completion, inspect the history, and confirm the authoritative record is not silently contradicted.

## Score the product on evidence

Use a short scorecard after the drills.

| Test | Pass evidence |
|---|---|
| Minimum-data card | Routine work completed without copying the chart |
| Access | Test roles saw only the approved workspace and fields |
| Removal | All tested access routes stopped within the approved interval |
| Notification privacy | Previews exposed no disallowed patient detail |
| Accountability | Assignment, changes, and completion had retrievable history |
| Record handoff | Final disposition appeared in the designated record |
| Export and closure | Approved administrators retrieved needed records and closed the test workspace |

Price and user experience matter after the product passes the intended workflow. A cheap board that requires a second clinical record or leaves access behind is not cheap to govern.

Patient Square does not position Practice Copilot as a generic clinical task or care-plan platform. Its public scope covers named practice workflows, and buyers should verify each intended handoff instead of assuming a feature that is not published. Define what belongs inside Patient Square and what should remain elsewhere by checking the workflow, data boundary, and final record.

---

## Medical Record Amendment vs Correction vs Addendum
https://patientsquare.com/us/blog/medical-record-amendment-correction-addendum/
Published 2026-10-07 · Tags: medical-records, chart-correction, hipaa-amendment, documentation-integrity, ehr-workflow

Use the right workflow for a chart correction, clinician addendum, delayed entry, or patient amendment request without erasing the original record.

A correction fixes an error in an existing entry; an addendum adds information later; a patient amendment request follows the formal HIPAA Privacy Rule process. In each case, preserve the original record, identify the author and date, and use the workflow that matches who is requesting the change.

The note says "left knee." The clinician treated the right knee. The patient spots it that evening, and the office manager asks a dangerous question: can we just change the word?

No. Use the record workflow that matches the event. A correction fixes an erroneous entry, an addendum adds missing information, a delayed entry documents something later, and a HIPAA amendment request is a separate patient-rights process. In every case, preserve the original, identify the change, and record who made it and when.

> **The record rules**
> - Never make a signed record silently look as if the error never existed.
> - Clinician corrections and patient amendment requests follow different paths.
> - The audit trail needs the original content, changed content, author, time, and reason.
> - Fix downstream orders, claims, referrals, and patient communications when the error traveled.

## Four labels that offices keep mixing up

CMS's Medicare recordkeeping principles group amendments, corrections, and delayed entries together for review purposes, but the operational reason for each change still matters. The [Indian Health Service comparison](https://www.ihs.gov/IHM/pc/part-3/p3c3-ex/) provides a useful vocabulary: an update replaces information designed to change over time, an administrative correction fixes administrative information, an addendum supplies extra information, and an amendment changes permanent-record information through an authorized process.

Use this decision card before anyone touches the chart:

| Situation | Correct path | What must remain visible |
| --- | --- | --- |
| Author typed the wrong side, date, dose, or factual statement | Clinician correction under policy | Original entry, corrected content, author, current date/time, reason |
| Clinician needs to add relevant information omitted from the signed note | Addendum | Original note plus separately identified added material |
| Documentation was not entered at the time of service | Delayed or late entry | Original record, actual entry date/time, author, connection to the service |
| Patient disputes information in the designated record set | HIPAA amendment-request workflow | Request, decision, accepted amendment or denial materials, related statements where applicable |
| Address, phone number, or other maintained demographic information changed | Update or approved administrative correction | Prior value when policy or system integrity requires it, plus accountable change history |

The label is not cosmetic. It determines who may act, what review is needed, and which notices or downstream repairs follow.

For controls around generated drafts, pair this workflow with the [AI scribe security checklist](../ai-scribe-security-checklist/). The [EHR data-migration guide](../ehr-data-migration-guide/) explains why correction history and audit evidence also matter when records move between systems.

## CMS gives a three-part integrity test

For records submitted to Medicare contractors and auditors, CMS says an amendment, correction, or delayed entry must:

1. be clearly and permanently identified as a change;
2. show the date and author of that change; and
3. preserve the original content without deletion.

The current principle appears in CMS transmittal R615PI, section 3.3.2.5 ([CMS](https://www.cms.gov/regulations-and-guidance/guidance/transmittals/downloads/r615pi.pdf)). On paper, CMS describes a single-line strike-through that keeps the text readable, with the author's signature and date. In an EHR, the system needs a reliable way to identify original content, modified content, and the person who made the change.

That is the audit-trail floor. The practice policy may require more, and a payer or service-specific rule may change the submission question. But "edit and save" without a visible history fails the basic integrity test.

## A patient amendment request is its own lane

The HIPAA Privacy Rule gives an individual a right to request amendment of protected health information in a designated record set, subject to the rule's grounds and process. Under [45 CFR 164.526](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.526), the covered entity acts on the request, communicates its decision in writing, and follows the rule's acceptance or denial steps.

That does not mean a patient can rewrite a clinician's professional judgment on demand. It does mean the office should stop treating the message as an ordinary portal complaint. Route it to the named privacy or records owner, log receipt, preserve the request, and follow the formal timeline and response process that apply to the organization.

Do not ask the original clinician to quietly revise the note while the request is being reviewed. That collapses the patient-rights record into the clinical-documentation record and makes both harder to explain.

## The correction may need to travel

Changing one chart field is not enough when the wrong information left the chart.

Suppose the wrong laterality appears in a referral, imaging order, prior-authorization request, and patient instruction. The clinical note correction is only the first item in the repair queue. Each affected destination needs an owner, a verified correction path, and a closure record.

Use a downstream-impact log:

| Destination | Question | Closure evidence |
| --- | --- | --- |
| Order | Was the incorrect order canceled or corrected through the authorized workflow? | Order status and accountable signer |
| Referral | Did the receiving office get the corrected information? | Confirmed transmission and contact |
| Claim or authorization | Did the error affect a submitted code, attachment, or medical-necessity statement? | Corrected submission or documented no-impact decision |
| Patient message | Did the patient receive incorrect instructions? | Clinician-approved correction and contact record |
| External record | Was information exported or shared before correction? | Authorized notification or updated document |

Do not send a fresh document and assume the recipient will infer which one wins. Name the correction and verify receipt when the risk warrants it.

## A clean addendum says why it exists

An addendum should be understandable without detective work. State the original encounter or document, the information being added, why it is being added now, the author, and the current date and time. Keep the original note intact.

Avoid boilerplate such as "clarification" when the addendum materially changes the record. If the change affects care, coding, an order, or a patient communication, say what downstream action was taken. If the author cannot truthfully reconstruct the missing information, the answer is not to write a confident late narrative.

The same honesty applies to delayed entries. Never backdate. The service date and the entry date answer different questions; the record should show both.

## Configure the EHR around authority, not convenience

Ask the vendor to demonstrate a signed-note correction with synthetic data. Watch who can initiate it, whether a second signer is needed, how the original appears, how timestamps display, what exports show, and which audit events an administrator can retrieve.

Then test a patient amendment request. That workflow often lives outside the note editor, and it should. The privacy owner may need a request queue, correspondence, decision, and attachment process that a clinician's addendum screen cannot supply.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan.

The scribe output is a draft. The clinician reviews and signs it. Public scope does not claim automatic changes to a signed note, a HIPAA amendment-request module, or write-back into an incumbent EHR. Read the [Practice Copilot scope](../../products/practice-copilot/), then ask the team to show the precise boundary for a signed-note correction. The [security page](../../security/) is the companion read for access and data handling.

## One correction drill beats ten policy pages

Use a synthetic wrong-side note. Ask the clinician to correct it, route a mock patient amendment request, identify two downstream documents, export the corrected record, and retrieve the audit history. Time the work.

The drill will find the soft spots quickly: broad permissions, missing ownership, an export that hides the change, or a help-desk ticket where a clinical correction process should be. Fix those. A record-integrity policy earns its keep only when the practice can execute it under pressure.

---

## Medical Referral Tracking System: Sent Is Not Closed
https://patientsquare.com/us/blog/medical-referral-tracking-system/
Published 2026-10-07 · Tags: referral-tracking, medical-practice, care-coordination, workflow

Use five referral statuses, named owners, specialist-result reconciliation, and a weekly exception queue to close the referral loop.

A medical referral tracking system follows an order through sending, scheduling, specialist response, clinician review, patient communication, and closure. Each open referral needs an owner, next action, and due date so a sent message is never mistaken for completed care.

“Referral sent” is a transport event. It does not tell the ordering clinician whether the patient was scheduled, attended, received an alternate recommendation, or had a result reviewed.

A medical referral tracking system should make those states visible without pretending that every patient follows the same route. The smallest workable design has five statuses, two kinds of ownership, and a weekly queue for items that stopped moving.

## Use five operating statuses

Avoid a long menu that staff interpret differently. Begin with five states and define the evidence needed to enter each one.

| Status | Required evidence | Next owner |
|---|---|---|
| Ordered | Clinician-approved referral order and reason | Referral coordinator or designated staff |
| Sent | Destination and transmission evidence recorded | Tracking owner |
| Scheduled or alternate outcome | Appointment detail, patient decline, unreachable result, or another documented disposition | Tracking owner or clinician |
| Result received | Specialist report or approved alternate information linked to the record | Ordering clinician |
| Closed | Clinician review, required patient communication, and final disposition recorded | None, unless follow-up is created |

The middle state is deliberately broad. A patient may decline, choose another specialist, face an access delay, or become unreachable after approved attempts. Those are outcomes to route, not reasons to make an item disappear.

## Separate tracking ownership from clinical ownership

An operations role can confirm transmission, contact a destination, and keep the queue current. It should not decide that a clinical result is acceptable or that no further action is required.

Assign both roles on the referral record:

```text
Tracking owner: ______________________
Ordering clinician: __________________
Current status: ______________________
Next action: _________________________
Due date: ____________________________
Escalation role: _____________________
Final disposition: ___________________
```

Shared ownership without names usually means no ownership. A due date without an escalation role only creates an older queue.

## Build from the return path

Begin at the end. Decide what the ordering clinician must receive, where it lands, how they acknowledge review, and who communicates the approved next step to the patient. Then work backward to the referral order.

The AHRQ Health Literacy Universal Precautions Toolkit advises practices to prepare patients for referrals, provide clear instructions, follow up with both the specialist and patient, obtain the specialist's report, and document the result in the medical record. [Tool 21, Make Referrals Easy](https://www.ahrq.gov/health-literacy/improve/precautions/tool21.html), treats referral work as a loop rather than a single handoff.

This backward design catches a common gap: a report arrives by fax or another channel but never enters the ordering clinician's review queue. The tracker looks complete because a document exists. The clinical loop remains open.

## Make the exception queue specific

Review open items at a fixed interval. Each row should say why it is open and what happens next.

Useful exception reasons include:

- destination did not confirm receipt;
- patient has not selected or reached a specialist;
- appointment is later than the clinician's requested interval;
- patient declined or requested another destination;
- specialist report has not returned;
- report arrived but awaits clinician review;
- clinician reviewed the result but patient communication remains open.

Do not use “pending” as the only reason. It describes age, not the work needed.

The ASTP/ONC SAFER materials include a Clinician Communication guide with recommended practices for referral tracking and notifications when appointments are not scheduled or completed. The current [SAFER Guides collection](https://healthit.gov/clinical-quality-and-safety/safer-guides/) should be used as a source for local assessment, not as a substitute for the practice's clinical policy.

## Reconcile the tracker with the clinical record

A tracker can coordinate work while the EHR remains the authoritative clinical record. Write down which facts live in each place and what must be copied or linked back.

At weekly review, sample referrals from both directions:

1. Pick five open tracker items and confirm their status in the clinical record.
2. Pick five referral orders from the clinical record and confirm they appear in the tracker.
3. Pick received reports and confirm the ordering clinician's review state.
4. Pick closed items and verify the documented disposition.

This catches omissions that a one-way dashboard cannot show.

If an outside vendor stores or processes protected health information on behalf of a covered entity, determine its HIPAA role and contractual obligations. HHS explains the business-associate framework and written-assurance requirements in its [Business Associates guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html). Do not put live patient data into an unapproved spreadsheet or trial account.

## Test three referrals with synthetic data

Create three fictional cases before launch.

The first follows the routine path from order to reviewed report. The second uses a destination that never confirms receipt. The third ends with a patient choosing not to proceed after the clinician's approved discussion.

For each case, verify:

- only permitted roles can view or change the item;
- status changes preserve an accountable history;
- overdue work reaches the named escalation role;
- an incoming report reaches the clinician's review queue;
- the final disposition is visible in the clinical record;
- reports and exports can be retrieved when needed.

A colorful dashboard is not evidence that these routes work. The synthetic cases are.

## Measure closure, not transmission

Count referrals ordered, sent, scheduled, completed, returned, clinically reviewed, communicated, and closed. Show median age in each open status and the number beyond the locally approved interval. Separate patient declines and access barriers from staff processing delays so the practice does not blame one group for every open item.

The purpose of the measure is to find stopped work. It is not to promise a universal clinical deadline or to grade individual patients.

A referral tracking system earns its place when a clinician can see what returned, staff can see what needs action, and the practice can explain every final disposition. Compare one routine referral with one that stalled to map the ownership and record handoffs around them.

---

## Clinic Workflow Map Template: Test One Visit Before You Buy
https://patientsquare.com/us/blog/clinic-workflow-map-template/
Published 2026-10-06 · Tags: clinic-workflow, workflow-mapping, medical-practice, software-buying

Map one clinic visit across people, systems, handoffs, and exceptions, then turn the current-state workflow into a software acceptance test.

A clinic workflow map follows one patient journey across owners, systems, waits, and exceptions. Start with the current process, then use each handoff as an acceptance test when evaluating software.

A useful clinic workflow map passes a handoff test. Give it to someone who did not draw it. They should be able to identify who acts next, which system holds the work, what evidence moves it forward, and where an exception goes.

Most first drafts cannot answer all four. They show departments and arrows while the queues, copies, and informal workarounds remain invisible.

Start with one ordinary visit. Follow it from trigger to final record and write down what really happens. The result becomes a practical test before a software demo, during implementation, and after a process failure.

## Use one row per change of ownership

Copy this header into a spreadsheet or a document:

| Step | Trigger | Owner | System | Input | Output | Wait or queue | Exception owner |
|---:|---|---|---|---|---|---|---|
| 1 | Patient requests visit | Front desk | Scheduler | Identity and request | Proposed slot | Callback queue | Front-desk lead |
| 2 | Slot accepted | Front desk | Scheduler | Confirmed details | Booked appointment | Reminder queue | Front-desk lead |
| 3 | Patient arrives | Check-in staff | Registration record | Identity check | Ready status | Rooming queue | Office manager |
| 4 | Encounter starts | Clinician | Clinical record | Patient history | Draft documentation | Review queue | Treating clinician |
| 5 | Draft reviewed | Clinician | Clinical record | Corrected draft | Signed record | Follow-up queue | Treating clinician |

Add a row whenever work changes owner, system, or queue. A line such as “room patient” is too broad if one person checks identity, another records vitals, and a third resolves a medication discrepancy.

The Agency for Healthcare Research and Quality describes workflow mapping as a method for understanding processes, identifying who performs each task, and finding redesign opportunities. Its [workflow mapping resource](https://www.ahrq.gov/evidencenow/tools/workflow-mapping.html) also uses swim lanes to show responsibilities across roles.

## Observe the current visit

Do not build the first version in a conference room. Follow a real process without recording patient details in the map. Ask the person doing each step what arrives, what they produce, where work waits, and whom they call when it fails.

Listen for sentences that reveal a hidden branch:

- “Usually the front desk fixes that.”
- “I keep a separate list so I remember.”
- “If it is urgent, I send a message too.”
- “The status does not update until tomorrow.”
- “Only one person knows how to export it.”

Put the branch on the map. An informal workaround is still part of the current workflow.

AHRQ's broader [Workflow Assessment for Health IT Toolkit](https://digital.ahrq.gov/health-it-tools-and-resources/workflow-assessment-health-it-toolkit) collects approaches for assessing clinical and administrative work around health IT. The aim is not a beautiful diagram. It is a shared account of what the clinic must preserve, remove, or test.

## Mark the authoritative record

Circle the point where each important fact becomes final. The booked time, verified identity, reviewed medication list, signed note, and approved follow-up may live in different systems today.

For each item, label one location authoritative. Then mark copies. A copy can be useful, but it creates a reconciliation question when the source changes.

This is especially important during platform selection. Patient Square, for example, publishes a path that uses its EHR and another that works alongside an existing EHR on the [Practice Copilot page](../../products/practice-copilot/). A buyer should decide which record is authoritative and test the route. The category label alone does not answer that question.

## Add the waits, not just the clicks

Clinics often measure the time someone touches a screen and omit the hours an item spends in a queue. Add a timestamp or expected interval to each handoff:

```text
Step completed: __________________
Next owner notified: _____________
Expected response by: ____________
Escalation after: _________________
Final disposition: _______________
```

That small block distinguishes completed work from abandoned work. It also reveals whether software shortened a workflow or merely moved it into a less visible queue.

## Inject one exception

Once the main path is accurate, choose a failure the clinic has actually seen. Use synthetic data and no real patient information.

For a scheduling workflow, change the appointment after a reminder has been queued. For documentation, correct the patient identity before the note is signed. For a follow-up, make the designated owner unavailable. Watch whether the item stops, duplicates, or reaches a fallback owner.

Record five facts:

1. Which system first showed the problem?
2. Who had permission to correct it?
3. Which copies also needed correction?
4. How did the next owner learn the work was ready?
5. What evidence showed the route was complete?

The ASTP/ONC [SAFER Guides](https://healthit.gov/clinical-quality-and-safety/safer-guides/) cover areas such as patient identification, clinician communication, system configuration, and contingency planning. They are useful prompts for choosing exceptions even when the immediate project is a clinic software purchase rather than a formal safety assessment.

## Turn the map into a demo script

Send vendors the same synthetic journey. Do not let each vendor choose its easiest route.

Ask the presenter to begin with the patient request, complete the booking, handle the changed time, produce a reviewable note, correct a known error, show the final record, and route an approved follow-up. Name every manual step. Capture where data is copied, where staff leave the product, and which role owns a failed handoff.

Grade the result with four outcomes:

| Outcome | Meaning |
|---|---|
| Pass | The routine and exception routes finish with the expected evidence |
| Conditional | The route works after a named configuration or training change |
| Manual | A person must bridge systems or reconcile copies |
| Stop | The workflow loses ownership, identity, or final-state evidence |

Now the map is an acceptance test rather than wall art.

## Revise after the first week

Implementation changes work. Observe the same journey after launch and compare it with the proposed future map. Keep useful deviations, correct unsafe or wasteful ones, and assign owners to the remaining manual steps.

One accurate patient journey is more valuable than an enterprise diagram nobody trusts. It gives clinicians, staff, and vendors the same concrete test. Use it to walk through routine and exception paths before discussing a larger rollout.

---

## Medical Office No-Show Policy: A Fair Template
https://patientsquare.com/us/blog/medical-office-no-show-policy/
Published 2026-10-06 · Tags: no-show-policy, scheduling, medical-office, template

Copy a medical-office no-show policy with notice, exceptions, escalation, privacy-safe reminders, consistent application, and a monthly measurement sheet.

Define a no-show and late cancellation, explain how patients receive the policy, name reminder channels, state any fee or scheduling consequence only after legal and payer review, list exceptions and appeal routes, and describe progressive escalation. Use the same documented process for similarly situated patients.

At 10:12 a.m., the second patient of the morning still has not arrived. The front desk can log the missed visit, offer the slot to the waitlist, and send a neutral rebooking message. It should not decide from memory whether this patient gets a fee, a warning, or an exception.

> **Policy controls at a glance**
>
> - Define the event before assigning a consequence.
> - Keep reminders useful and privacy-limited.
> - Put hardship, access, and clinical exceptions in the normal workflow.
> - Measure the policy by appointments offered, missed, recovered, waived, and appealed.

## Copyable no-show policy

```text
MEDICAL OFFICE APPOINTMENT AND NO-SHOW POLICY

Purpose
We use appointment time carefully and want patients to have a clear route to
cancel, reschedule, explain an exception, and return to care.

Definitions
No-show and grace period: _________________________
Late-cancellation window: _________________________
Late-arrival review: ______________________________

How to cancel or reschedule
Phone and hours: __________________________________
Portal or other approved route: ___________________
After-hours instructions: _________________________

Reminders
We may send appointment reminders through __________. Reminders are a
courtesy; patients should keep their own appointment information current.

First event
Neutral outreach and rebooking steps: _____________

Repeated events
Progressive review, owner, and approved consequences: __________

Fees, if approved
Amount or formula after required review: __________
Charging, waiver, disclosure, and appeal rules: ___

Exceptions and review
Tell us if an emergency, hospitalization, transport failure, disability-related
need, communication barrier, or other circumstance affected the appointment.
The designated reviewer is __________ and uses the same documented criteria.

Clinical continuity
A missed visit does not authorize staff to ignore an urgent message, pending
result, active treatment issue, or other clinical concern. Route those items to
the named clinical role and response path: ______________________.

Questions or appeal
Contact __________ by __________. We document the review and response.

Effective date: __________  Owner: __________  Review date: __________
```

This template deliberately leaves fees and time windows blank. The practice has to earn those lines through local review.

## Define the event in plain language

Decide how late is late, when a cancellation becomes late, and what happens when the clinic itself is running behind. Include telehealth connection failures, transport problems, and appointments the patient reasonably believed were cancelled.

A useful event log needs facts:

- appointment start time;
- arrival, call, cancellation, or connection time;
- reminder channel and delivery status;
- outreach attempt;
- rebooked, waitlist-filled, or unresolved outcome;
- exception requested and reviewer;
- consequence, waiver, or appeal result.

Avoid labels such as "habitual" or "noncompliant" in the scheduling log. Count events and record the reviewed outcome.

## Reminders should disclose less, not more

[HHS OCR says](https://www.hhs.gov/hipaa/for-professionals/faq/may-health-care-providers-leave-messages/index.html) the HIPAA Privacy Rule permits appointment reminders and other communications about care. The same guidance advises limiting what is left on an answering machine to information reasonably needed for the communication, such as the provider's name and callback number.

Let patients state communication preferences and keep contact details current. Test voicemail, text, email, and portal wording with synthetic accounts. A reminder should not reveal a specialty, diagnosis, procedure, or sensitive clinic name when a simpler confirmation will do.

For the wider scheduling-system decision, see the [medical office scheduling software guide](../medical-office-scheduling-software/). For automated recovery messages, the [patient follow-up automation guide](../ai-patient-follow-up-automation/) keeps clinical replies with a human.

## Use an exception lane every time

Do not bolt on an exception after somebody complains. Put it in the standard event screen.

The staff member logs the request. A named reviewer checks the policy criteria. A clinical concern goes to the clinical lane. A disability or discrimination concern goes to the approved compliance lane. The patient receives the outcome and an appeal route.

The same workflow can still produce different outcomes when facts differ. Consistency means using the same criteria and review, not pretending an emergency and a forgotten appointment are identical.

## Escalation is not automatic dismissal

Progressive steps can include a reminder, a copy of the policy, a scheduling conversation, or a manager review. If the practice considers ending the relationship, stop the scheduling automation and open a separate case.

The [AMA ethics opinion on terminating a patient-physician relationship](https://code-medical-ethics.ama-assn.org/ethics-opinions/terminating-patient-physician-relationship) requires notice long enough to permit the patient to secure another physician and appropriate help transferring care. The exact legal and operational path varies. Use the [state-aware patient dismissal template](../patient-dismissal-letter-template/) only after that review.

Pending results, active medication questions, postoperative care, or other urgent issues need owners regardless of appointment status. A no-show flag cannot close a clinical task.

## One monthly table tells you whether the policy works

| Measure | Count | What to inspect |
|---|---:|---|
| Appointments offered | | Denominator and clinic mix |
| Late cancellations | | Timing and reminder delivery |
| No-shows | | Repeated patterns and access barriers |
| Slots filled from waitlist | | Recovery, not punishment |
| Exceptions requested | | Whether patients can find the route |
| Exceptions approved | | Consistency by reviewer and reason |
| Fees or other consequences applied | | Contract and policy compliance |
| Appeals changed | | Policy ambiguity or staff error |

Compare the same definitions month to month. Do not claim the policy reduced no-shows when the office changed the denominator, grace period, or appointment mix.

We think the recovered-slot row is the useful one. A stern policy that leaves the calendar empty has solved the wrong problem.

## Product boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

That scope does not promise automated fee assessment, contract interpretation, patient dismissal, or a legally approved no-show policy. Keep those decisions with the practice.

If scheduling and documentation fail at the same handoff, [review the current Practice Copilot scope](../../products/practice-copilot/). Verify the [current US plan scope](../../pricing/) and [security controls](../../security/) before adopting any workflow.

---

## Medical Record Amendment Request: Form and Workflow
https://patientsquare.com/us/blog/medical-record-amendment-request/
Published 2026-10-06 · Tags: medical-records, hipaa, amendment, template

Use a patient amendment request form with a 60-day HIPAA clock, denial path, disagreement statement, routing log, and separate clinician-correction lane.

Yes. Under 45 CFR 164.526, an individual can ask a covered entity to amend protected health information in a designated record set while that information is maintained. The covered entity may require a written request and a reason if it tells patients about that requirement in advance.

The amendment envelope arrives on Tuesday. A patient says the chart lists the wrong employer and misstates what she reported about an allergy. One item is administrative. The other could change a future clinical read. Both deserve a tracked answer, but neither should trigger a silent edit of yesterday's note.

> **Before you route the request**
>
> - Start the HIPAA action clock when the covered entity receives the request.
> - Separate patient-requested amendments from clinician-initiated corrections.
> - Preserve the original record and attach the accepted amendment or authorized correction.
> - Route a denial, disagreement, and later disclosure according to the rule.

## Copyable amendment request form

```text
REQUEST TO AMEND A MEDICAL RECORD

Patient name: _________________________________
Date of birth: ________________________________
Account or record number: _____________________
Preferred contact method: _____________________

RECORD TO REVIEW
Visit or service date: ________________________
Clinician or department: ______________________
Document or field: ____________________________

CURRENT ENTRY
Exact information: ________________________________

REQUESTED AMENDMENT
Requested wording or addition: ___________________

REASON FOR THE REQUEST
Reason the record should be amended: _____________

OTHER PEOPLE OR ORGANIZATIONS TO CONSIDER
Possible recipients to notify if accepted: _______

Patient or representative signature: __________
Authority of representative, if any: __________
Date submitted: _______________________________

PRACTICE INTAKE
Received date: ________________________________
Received by: __________________________________
Privacy owner: ________________________________
60-day action date: ___________________________
Extension notice date, if used: _______________
Final action date: ____________________________
Outcome: accepted / partly accepted / denied
Linked record or notice reference: ____________
```

The form is an intake aid, not a legal determination. Match it to your notice of privacy practices, state law, designated-record-set policy, and counsel-approved response templates.

## Put the 60-day clock on the intake screen

[45 CFR 164.526](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.526) requires a covered entity to act on an amendment request within 60 days of receipt. The same section permits one extension of up to 30 days when the individual receives a written delay notice that explains the reason and gives a completion date.

That clock belongs beside the request, not in somebody's inbox. Record four dates: receipt, ordinary due date, extension notice if used, and final action. Assign one privacy owner and one backup.

Do not confuse receipt with the day a clinician happens to open the task. The routing queue is part of the compliance workflow.

## Two lanes prevent bad edits

| Lane | Trigger | Decision owner | Record action |
|---|---|---|---|
| Patient amendment | Individual asks to change protected health information in a designated record set | Covered entity's assigned privacy and clinical reviewers | Accept, partly accept, or deny under the amendment process |
| Clinician correction | Author or authorized reviewer finds an error in the clinical record | Organization's clinical and record-integrity policy | Add a linked, dated correction or addendum with an audit trail |

The lanes can meet at the same chart, but their reasons and notices differ. A patient amendment request is a right governed by the HIPAA process. A clinician correction is the practice repairing its own record under an approved integrity workflow.

Never solve either lane by deleting the earlier entry. The reviewer needs the before state, the after state, who authorized the change, when it occurred, and which later uses received the accepted amendment.

For retention and legal-hold decisions, use the [medical record retention policy worksheet](../medical-record-retention-policy/). For a broader record-quality sample, pair it with the [medical chart audit checklist](../medical-chart-audit-checklist/).

## Acceptance needs more than a changed sentence

When a covered entity accepts an amendment, [the federal rule](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.526) calls for identifying the affected records, appending or linking the amendment, obtaining the individual's agreement about relevant people to notify, and making reasonable efforts to provide the amendment to those identified and to known recipients who may have relied on the information.

Build those actions into the completion screen:

- record locations affected;
- amendment or link added;
- patient agreement captured;
- recipient list reviewed;
- notices sent or exception documented;
- patient notified of acceptance.

The useful question is not "did we fix the field?" It is "can every later reader see the accepted context?"

## A denial opens another branch

The rule allows denial only on listed grounds. Those include specified circumstances where the information was not created by the covered entity, material outside the designated record set, information unavailable for inspection, or a record the entity determines is accurate and complete.

The written denial process must explain the basis and the individual's options, including a statement of disagreement and complaint routes. If the individual submits a disagreement, the practice follows the rule's rebuttal and record-linking steps. Use counsel-approved language. Do not turn the intake template into a homemade denial letter.

## Include business associates in the route map

[HHS OCR explains](https://www.hhs.gov/hipaa/for-professionals/faq/do-business-associates-have-obligations/index.html) that the covered entity remains responsible for individual rights and must arrange for a business associate to make protected health information available and amend it when needed to fulfill the covered entity's obligations.

Your route map should therefore answer two questions before a request arrives:

1. Which designated-record-set copies sit with a business associate?
2. Which contract and operational contact can carry an accepted amendment into those copies?

A vendor ticket with no owner is not a closed amendment.

## Test the awkward case

Use a synthetic request with two items. Accept one administrative correction and deny one clinical change because the reviewed entry is accurate and complete. Then add a disagreement, send the proper notices, and produce the record later for an authorized disclosure.

The exercise should preserve the original entry, show every linked document, and expose the dates. If the exported record hides the disagreement or the old value disappears, the workflow is not ready.

We think this mixed outcome is a better test than a simple typo. It forces the practice to exercise both branches without using a real patient's information.

## Product boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

That scope does not state that Patient Square runs the HIPAA amendment workflow described above. Treat amendment intake, legal decisions, recipient notices, and final record action as practice-owned controls unless the current product demonstration proves otherwise.

If record provenance is part of your EHR evaluation, [review the current Practice Copilot scope](../../products/practice-copilot/). Check the current [security posture](../../security/) and [plan scope](../../pricing/) before putting protected health information into any workflow.

---

## Practice Copilot ROI: Build a Retire-or-Retain Business Case
https://patientsquare.com/us/blog/practice-copilot-roi-business-case/
Published 2026-10-06 · Tags: practice-copilot, roi, practice-management, software-buying

Build a Practice Copilot ROI case from software overlap, staff-owned handoffs, implementation cost, and evidence that a tool can actually be retired.

A Practice Copilot ROI case compares confirmed savings from retired tools and changed handoffs with the subscription and transition costs. Credit a retirement only after the replacement passes a real workflow test and the old contract can end.

A clinic pays for five systems. A new platform appears to cover work performed in three of them. The tempting calculation subtracts three subscriptions from one quote and calls the difference ROI.

That arithmetic is premature. A contract is not retired when a feature appears in a demo. It is retired when the replacement completes the real workflow, the practice can retrieve its records, staff know the exception path, and the old vendor can be switched off without losing required work.

Use a Practice Copilot ROI case to decide what the clinic can retire, what it must retain, and what evidence is still missing. Keep the spreadsheet small enough that an owner can challenge every number.

## Start with a three-column software ledger

List every tool touched by one patient journey, from booking through the signed record and approved follow-up. Put each tool in one of three columns.

| Decision | Meaning | Evidence needed |
|---|---|---|
| Retire | The proposed workflow replaces the job and the contract can end | Completed acceptance test, export plan, owner approval, cancellation date |
| Retain | The clinic still needs the system | Named job, current cost, interface or manual handoff |
| Overlap | The answer depends on a test or contract term | Open question, test date, decision owner |

Do not use “included” as a fourth decision. Included describes the quote. Retire describes an operational result.

Patient Square currently publishes three US tiers. The monthly prices shown in September 2026 are $99 for Assist, $149 for Copilot, and $249 for Autopilot. Annual billing is shown as $79, $119, and $199 per month respectively. The [current pricing page](../../pricing/) is the source to check before a purchase decision because prices and plan scope can change.

The same page lists documentation and scheduling in Assist, Patient Square EHR and WhatsApp in Copilot, and named receptionist and follow-up modules in Autopilot. Those labels still need to be translated into the clinic's work.

## Calculate a conservative first-year case

Use four lines, not an elaborate forecast.

```text
Confirmed annual savings from retired tools       $________
Confirmed staff cost removed from named handoffs  $________
New annual subscription                           $________
One-time implementation and transition cost       $________

Conservative first-year value = savings - subscription - transition
```

Only the first two lines require judgment. A software saving belongs in the model when the cancellation date is known and the clinic has handled export, retention, and closeout. Staff savings belong there when a task goes away, not when it merely moves to another screen.

Keep possible upside below the line. If shorter documentation work might create more visit capacity, show it as a scenario. Do not convert every saved minute into revenue unless the schedule, demand, staffing, and completed-visit data support that conversion.

## Follow one visit before pricing the whole platform

AHRQ describes workflow mapping as a way to make a process visible, clarify who performs each step, and find opportunities for redesign. Its [workflow mapping guide](https://www.ahrq.gov/evidencenow/tools/workflow-mapping.html) recommends mapping the current process before designing the future one.

Pick a common visit with a slightly awkward ending. For example:

1. A patient books and later asks to change the time.
2. Staff confirm identity and update the appointment.
3. The clinician conducts the encounter and reviews a drafted note.
4. The clinician signs the final record.
5. Staff send an approved follow-up message.
6. The patient replies after the office closes.

Mark the system, person, input, output, and exception owner at each step. Run the proposed setup with synthetic data. Then disable one expected handoff or send the reply to the wrong queue on purpose. The business case should include the labor and fallback that remain after that test.

## Give each planned retirement a proof card

A one-line assumption is too easy to forget. Use a proof card for every system marked Retire.

```text
Current tool and contract end: ______________________________
Job it performs today: ______________________________________
Replacement workflow tested on: _____________________________
Routine case result: ________________________________________
Failure case result and owner: ______________________________
Data export and retention checked by: _______________________
Retirement approved by: ____________________________________
```

If the card has blanks, keep the cost in the overlap column. This makes the ROI case less exciting and more useful.

## Treat the record decision as its own gate

Patient Square describes two Practice Copilot deployment paths: use the Patient Square EHR or work alongside an existing EHR. That choice changes migration work, duplicate entry, export needs, and the number of systems the clinic can plausibly retire. The [Practice Copilot page](../../products/practice-copilot/) is explicit about the two paths; it does not establish an interface with every named outside EHR.

Draw a box around the system that will hold the completed, signed record. Write down how scheduling, draft notes, messages, and approved follow-ups enter that box. The ASTP/ONC [SAFER Guides](https://healthit.gov/clinical-quality-and-safety/safer-guides/) provide practical safety material for EHR configuration, communication, patient identification, contingency planning, and other areas worth testing during a change.

No retirement credit belongs in the model while the authoritative record or fallback route is undecided.

## Present three outcomes to the owner

The final packet can fit on one page.

- **Proceed:** tested retirements cover the new cost and the owners accept the transition work.
- **Pilot:** the workflow looks viable, but important costs remain in the overlap column.
- **Stop:** the clinic would add a platform while keeping the same systems and staff handoffs.

Attach the software ledger, the conservative calculation, and one proof card per proposed retirement. That is enough for a real decision. A large feature matrix is not.

The strongest ROI case may conclude that the clinic should buy a smaller plan, keep its present EHR, or wait until a contract expires. It may also show that several subscriptions and handoffs can safely disappear. Either result is better than counting a demo as a saving. Bring us one patient journey and the tools it touches; we can map the proposed Practice Copilot path without inventing retirement credit.

---

## Hospital Incident Report Format: An India Template
https://patientsquare.com/in/blog/hospital-incident-report-format-india/
Published 2026-10-05 · Tags: hospital-incident-report, patient-safety, quality, india

Build a hospital incident report around immediate response, neutral facts, source evidence, review ownership, corrective action, and recheck.

A hospital incident report should record when and where the event was noticed, who was affected, immediate care and safety actions, an objective description, witnesses and source records, notifications, equipment or medication identifiers where relevant, and the receiving reviewer. Investigation, root cause, corrective action, owner, due date, and recheck belong in a linked review record. Follow the hospital's approved policy and escalate urgent clinical or safety needs at once.

At 7:42 p.m., a nurse finds a patient beside the bed. The first job is care. The second is making the area safe. The report comes after those actions begin, and it must not rewrite the event to make the form look tidy.

A useful incident format keeps immediate facts separate from later analysis. It preserves uncertainty, names the receiving owner, and leaves a trail from first report to recheck.

## Put the first-hour card above the long form

Staff need a short response card before they need a taxonomy.

```text
HOSPITAL INCIDENT: IMMEDIATE RESPONSE CARD

Attend to urgent clinical or safety needs under the approved protocol.
Call the required clinical, emergency, security, or engineering role.
Protect other patients, visitors, staff, and the scene where appropriate.
Preserve relevant records, equipment, labels, logs, and timestamps.
Notify the shift or department owner under policy.
Start the incident report as soon as the situation permits.

Person initiating report: ________________________________
Incident reference: ______________________________________
Time noticed: ______________ Time escalated: _____________
Receiving owner: _________________________________________
```

The card is not a clinical protocol. The hospital must connect it to the exact local response pathways for falls, medication events, equipment failures, infection concerns, security events, needle-stick injuries, fire, blood products, and other risks.

## Use a fact record, not a verdict

```text
HOSPITAL INCIDENT REPORT: INITIAL FACT RECORD

Incident reference: ______________________________________
Date, time, department, and exact location: ______________
Person affected and approved identifier: _________________
Reporter name, role, and contact: _________________________

How the event was noticed: _______________________________
What was directly observed, in time order: _______________
___________________________________________________________

Immediate clinical assessment and care record location: __
Immediate safety action: _________________________________
People notified, route, and time: ________________________

Witnesses or other direct sources: _______________________
Equipment, device, medicine, batch, or asset reference: __
Photos, system logs, CCTV, or documents preserved: _______

Known impact at time of report: __________________________
Unconfirmed statements requiring review: _________________

Received by: __________________ Time: _____________________
Initial classification under hospital policy: ___________
Next owner and due time: _________________________________
```

The All India Institute of Ayurveda's [Safety Manual](https://www.aiia.gov.in/wp-content/uploads/2023/02/8.1.3Mockdrill-to-manage-complications.pdf) instructs staff to report incidents and near misses, complete the report objectively, route it for review, and investigate where required. Use the hospital's own approved categories and clocks; do not copy another facility's deadline without review.

## Record clinical care in the clinical record

The incident report and the patient record answer different questions. The clinical record must show the patient's condition, assessment, care, orders, monitoring, communication, and follow-up under the hospital's rules. The incident system supports safety and quality work.

Define how the two records link without pasting confidential quality analysis into every chart. Decide who can see each record, what identifiers are necessary, how corrections work, and when legal or regulatory owners must review access or disclosure.

An incident report must never delay care. Nor should a quality form become the only place where a changed clinical condition is documented.

## Preserve the difference between source and inference

Use source labels in the initial account:

- directly observed by the reporter;
- reported by the patient or attendant;
- reported by another staff member;
- device or system timestamp;
- clinical record entry;
- CCTV or access log under authorised review;
- unconfirmed statement.

Avoid loaded phrases such as "careless," "ignored," or "obvious cause." Write what occurred: the alarm sounded at a recorded time, the response was logged later, a label was unreadable, or two records disagree. Investigation can then test why.

The [VMMC and Safdarjung Hospital safety policy](https://vmmc-sjh.mohfw.gov.in/sites/default/files/Policy%20on%20Security%20and%20Safety%281%29.pdf) includes an incident record with fields for root cause, corrective action, preventive action, follow-up, and signature. Those later fields belong to controlled review, not to guesswork in the first minutes.

## Link the report to a review record

```text
INCIDENT REVIEW AND ACTION RECORD

Incident reference: ______________________________________
Review lead and team: ____________________________________
Scope and evidence preserved: ____________________________
Timeline confirmed through: ______________________________

Finding and confidence: __________________________________
Contributing conditions: _________________________________
Root-cause method used: __________________________________

Immediate correction: ____________________________________
Corrective or preventive action: _________________________
Owner: __________________________ Due date: _______________
Measure of completion: ___________________________________
Recheck sample and date: _________________________________

Reportability or external-notification review owner: _____
Closure approved by: ______________ Date: ________________
```

Correction and corrective action are not the same. Replacing a broken call bell fixes one item. Finding why preventive maintenance missed it, changing the process, and testing a new sample addresses the system.

## Build a near-miss lane

If nothing reached the patient, the information may still matter. The AIIA manual includes near-miss reporting in its incident process. Make the route easy enough that staff can report a wrong label caught before administration or a bed alarm fixed before use.

Near-miss data becomes useless when the form demands a known injury or forces the reporter to accuse a colleague. Allow "no known harm at reporting time" and "cause not yet determined." Preserve the opportunity to learn.

## Test correction, downtime, and duplicate reports

Run three drills with synthetic data.

First, the reporter enters the wrong location and corrects it. The system should retain the original, correction, author, reason, and time.

Second, the network is down. Staff use the approved paper route, urgent notifications still occur, and the later digital entry links to the original without changing its timestamp.

Third, two staff report the same event from different viewpoints. The review team should link the reports, not delete one and keep the more convenient story.

## Product boundary

Patient Square is an AI clinical platform. It does not replace a hospital's patient-safety system, clinical response, incident investigation, legal review, NABH programme, regulatory reporting, or quality governance. Patient Square does not claim NABH certification.

If authorised teams test drafting or routing around an incident, use synthetic data first. Verify the [current India security posture](../../security/), permissions, change history, failure behavior, export, and deletion before real use. Keep urgent decisions with trained people.

---

## Nuance DAX Copilot Pricing: Read the $600 Listing
https://patientsquare.com/us/blog/nuance-dax-copilot-pricing/
Published 2026-10-05 · Tags: dragon-copilot, nuance-dax, pricing, ai-scribe

Separate the public $600 DAX listing from current Dragon Copilot licensing, then normalize the quote, services, usage, and workflow cost.

The Marketplace lists a limited-term DAX Copilot offer at $600 per user monthly ($7,200 for a year) and requires a separate professional-services quote. Treat it as a reference because Dragon Copilot pricing may differ.

There is a public Nuance DAX number: Microsoft Marketplace lists a limited-term hosted-service offer at $600 per user per month, or $7,200 for one year. The listing also says the transaction still needs a professional-services quote. Current Dragon Copilot licensing has more than one route, so $600 is a reference point, not your final budget.

> **Pricing facts to carry into the call**
>
> - Public DAX reference: $600 per user each month on a one-year term.
> - The Marketplace listing still requires a professional-services quote.
> - Current Dragon Copilot documentation names per-user, Flex, and usage-based licensing paths.
> - The only useful comparison puts licenses, services, integration, internal labor, and exit in one sheet.

## The public $600 number has a narrow label

The [Microsoft Marketplace DAX Copilot listing](https://marketplace.microsoft.com/en-us/product/web-apps/nuance_gskaff.dax_copilot_per_user?tab=PlansAndPrice) names a hosted-service, limited-term offer. It shows $600 per user per month, a one-year subscription, and $7,200 for the term. It also warns that the transaction will not complete until the buyer connects with Nuance for a professional-services quote.

That is unusually useful evidence because it comes from Microsoft's own marketplace. It is also easy to misuse. The page is a specific offer, not a promise that every physician, hospital, partner deployment, or renewal receives the same structure.

For a 20-user reference calculation, the marketplace license line alone is $12,000 per month and $144,000 for one year. That multiplication adds no implementation, services, usage, taxes, or internal labor. Put it in the model as "public DAX offer," not "our Dragon Copilot quote."

## Current Dragon Copilot licensing is a different map

Microsoft's [Dragon Copilot licensing overview](https://learn.microsoft.com/en-us/industry/healthcare/dragon-admin-center/licensing/) lists Physician Per User, Physician Flex, a physician pay-as-you-go consumption unit, and Nurse Per User. The physician per-user license covers the physician workflow without an Azure consumption meter. Flex provides dictation per user and lets administrators enable ambient and generative AI capabilities that are charged by use through an Azure subscription.

Microsoft says buyers obtain physician licenses through a direct customer agreement or a certified partner. Nursing licenses use the direct Microsoft route. No public dollar figure appears in that licensing table.

This is why one sentence should lead the request for proposal: "State the exact license family and every meter used in this quote." If the seller cannot fill that line, the total is not ready for comparison.

## Normalize the quote before debating value

Copy each vendor's proposal into this grid. Leave no bundled cell blank.

| Quote line | Quantity | Unit price | One-time or recurring | Evidence to request |
|---|---:|---:|---|---|
| Named-user license |  |  | Recurring | License name and eligible role |
| Ambient or AI use |  |  | Recurring or variable | Meter definition and overage rate |
| Professional services |  |  | One-time or recurring | Statement of work and acceptance criteria |
| EHR or partner work |  |  | One-time plus support | Named workflow, owner, and support boundary |
| Training |  |  | One-time or recurring | Sessions, audience, and materials |
| Support |  |  | Recurring | Hours, severity levels, and response targets |
| Exit assistance |  |  | One-time | Export, access removal, and deletion evidence |

Then run three volumes: expected use, a quiet month, and a month with 25 percent more ambient sessions. Flex can be sensible when use varies, but a variable meter needs a budget guard. A fixed per-user offer can be easier to model, yet wasteful when many licensed clinicians rarely use it.

Our opinion: procurement should reject a blended "platform fee" until the seller separates license, usage, and services. The spreadsheet is not busywork. It is the only way to see which number can change at renewal.

## Price the actual EHR workflow

Microsoft documents two broad physician experiences. In standalone Dragon Copilot apps, users finalize content and manually transfer it into their EHR. In an embedded partner experience, ambient capture and generated summaries can operate inside the third-party EHR, depending on the partner's design. Microsoft also says the end user keeps a separate contract with that EHR vendor ([Dragon Copilot physician overview](https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/about/)).

Those paths should not share one implementation assumption. A manual-transfer pilot has a smaller technical boundary and more staff handling. An embedded deployment can remove that transfer step, but adds partner, configuration, testing, and support questions. Ask the seller to demonstrate the exact destination, correction route, and downtime fallback named in your quote.

The [AI scribe EHR checklist](../ai-scribe-ehr-integration-checklist/) supplies the workflow questions. The [vendor pricing contract guide](../ai-scribe-vendor-pricing-contract/) covers renewal, termination, and evidence language.

## Compare a published small-practice path honestly

Patient Square publishes three US practice tiers on its [pricing page](../../pricing/). Assist is $99 month to month or $79 per clinician per month on annual billing. Copilot is $149 or $119 and adds the bundled AI EHR. Autopilot is $249 or $199. These are practice prices. Hospital Copilot is separately demo-priced.

Patient Square is an AI clinical platform. Practice Copilot includes an ambient AI Medical Scribe that prepares a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. Practices can keep an existing record system or use the bundled AI EHR starting at the Copilot tier.

The comparison is not "same product, lower price." Dragon Copilot can be embedded through enterprise EHR and partner architecture. Patient Square gives an independent practice a published ladder and a smaller procurement path. Run both against the same workflow.

| Buying situation | Better first shortlist |
|---|---|
| Health system wants Microsoft administration and embedded partner workflow | Dragon Copilot |
| Organization expects variable ambient use and can manage Azure metering | Dragon Copilot Flex |
| Independent practice wants a public price and a contained scribe pilot | Patient Square Assist |
| Practice also wants a bundled record system | Patient Square Copilot |

Dragon Copilot is the better fit when its enterprise licensing and EHR path are the reason for the purchase. A cheaper standalone workflow cannot replace that architecture. Patient Square is the better fit when the clinic does not need that architecture and wants to know the subscription before a sales call.

## Turn the quote into a one-page approval

The approval page should show the license family, enabled users, expected annual usage, one-time services, recurring support, internal implementation hours, contract term, increase cap, and exit work. Attach the vendor's statement of work. Put every unverified number in a separate assumptions box.

Use the $600 listing as a negotiation anchor only when the quote covers the same DAX offer. Use current Dragon Copilot licensing documents to identify the actual model. Compare the same clinic workflow with Patient Square, then price the work left to your own team. The lowest license number can still produce the larger operating bill.

## FAQs

### The published Nuance DAX price

Microsoft Marketplace lists a limited-term DAX Copilot hosted-service offer at $600 per user per month, or $7,200 for one year, and says a Nuance professional-services quote is still required. Treat that as a public reference point, not a universal Dragon Copilot quote.

### What the Marketplace figure covers

Not necessarily. Microsoft's current licensing documentation describes Physician Per User, Physician Flex, pay-as-you-go consumption, and Nurse Per User paths, purchased through Microsoft or a certified partner. Your quote may use a different license and service structure from the older DAX Marketplace offer.

### Quote lines to include

Ask for the license type, enabled users, ambient or AI usage charges, implementation, professional services, EHR work, training, support, minimum term, price increases, and exit assistance. Put one-time and recurring charges in separate columns before comparing vendors.

### Dragon Copilot and the EHR

Microsoft documents standalone web, desktop, and mobile workflows where finalized content is manually transferred into the EHR. Embedded experiences can deliver summaries inside a third-party EHR, depending on the partner design. Price the workflow you will deploy, not the best possible architecture.

### The enterprise-fit test

It can be the better fit when a health system wants Microsoft licensing, partner delivery, embedded EHR workflow, enterprise administration, or variable usage under the Flex model. An independent practice that only needs a reviewable draft may prefer a smaller buying and implementation boundary.

### The Patient Square price comparison

Patient Square publishes US practice prices per clinician: Assist is $99 monthly or $79 on annual billing, Copilot is $149 or $119 and adds the bundled AI EHR, and Autopilot is $249 or $199. Hospital Copilot is separately demo-priced and should not use practice pricing.

---

## OPD vs IPD: What Hospital Software Must Handle
https://patientsquare.com/in/blog/opd-vs-ipd-hospital-software-india/
Published 2026-10-05 · Updated 2026-09-24 · Tags: opd-software, ipd-software, hospital-management-system, india, buyer-guide

An India-focused guide to OPD and IPD software workflows, ownership, handoffs, billing, and buyer tests for hospitals.

OPD workflows centre on registration, appointments or queues, consultation, orders, prescriptions, billing, and follow-up without an inpatient admission. IPD workflows add admission, bed and ward movement, ongoing orders and administration, deposits and charge capture, discharge, and a longer episode of care. A hospital system should preserve the handoff when an OPD patient becomes an inpatient.

A patient arrives for an OPD consultation. The clinician decides that the patient needs admission. At that moment, a hospital's software either carries the work forward or makes staff start again.

That crossing is a better buying test than a long feature grid. It reveals whether identity, clinical context, orders, results, medicines, charges, and responsibility can move from a short outpatient visit into a managed inpatient episode.

OPD and IPD are not merely two menu items. They have different rhythms, risks, owners, and financial workflows. The software has to respect those differences while keeping one traceable patient journey.

## Follow one patient across the boundary

In an OPD workflow, a patient is commonly registered, placed into an appointment or queue, seen by a clinician, sent for any required service, billed, and given a follow-up plan. The visit may last minutes or hours, but it does not create an inpatient stay.

An IPD workflow begins with an admission decision and continues across shifts. It adds a bed or ward context, repeated observations and orders, administration records, deposits or payer processes, accumulated charges, and discharge work.

The National Informatics Centre's published eHospital module list separates OPD registration, clinic workflows, admission, discharge, transfer, billing, laboratory, pharmacy, and other functions. That list is not a specification for every hospital product. It is useful evidence that hospital operations contain distinct modules and handoffs that buyers should test.

## OPD software is built around flow

The OPD front desk needs to identify or register a patient without creating avoidable duplicates. The queue needs a clear state. Clinicians need relevant history and a place to record the consultation. Orders, results, prescriptions, billing, and follow-up need ownership.

A useful OPD demonstration therefore starts outside the consultation screen. Ask the vendor to show:

1. a returning patient with a changed mobile number;
2. a walk-in placed alongside booked appointments;
3. an order that reaches the correct service point;
4. a result returned to the correct encounter;
5. a bill correction with a visible reason and actor;
6. a follow-up that staff can find without reading free text.

Fast registration alone does not prove the workflow is safe or complete.

## IPD software is built around continuity

Inpatient work survives handovers, location changes, and a longer chain of decisions. The system needs to show the current state and the history that produced it.

Test admission, bed assignment, ward transfer, orders, results, medicines, consumables, professional charges, deposits, and discharge as connected events. Ask what happens when an order changes, a bed move is reversed, a charge is corrected, or discharge is paused.

The National Health Mission publishes Indian Public Health Standards for public health facilities. The standards are broader than a software checklist, and the appropriate document depends on facility type. They are a useful reminder to map technology to actual service delivery, staffing, records, and facility processes instead of copying a generic vendor template.

## The OPD-to-IPD handoff is the decisive test

Put a realistic case into the demonstration environment. Register the patient in OPD, complete a consultation, create an order, post a result, and then initiate admission.

Watch what crosses the boundary:

| Handoff item | What the hospital should verify |
|---|---|
| Patient identity | The same patient continues without an unsafe duplicate or false merge |
| Clinical context | Relevant OPD notes, allergies, current medicines, orders, and results are available with provenance |
| Admission decision | The actor, time, reason, and destination are traceable under hospital policy |
| Financial state | OPD charges, deposits, payer details, and IPD billing rules do not conflict |
| Medicines and inventory | Orders and issues reach the correct pharmacy or store workflow without silent duplication |
| Documents | Consent and other required records are linked to the correct episode and access-controlled |
| Responsibility | Staff can see who owns the next action and which team receives alerts or work queues |

Do not accept a slide showing arrows between OPD and IPD. Complete the handoff and inspect the resulting record.

## Separate the record, operations, and AI layers

Hospital software discussions often mix three different jobs.

The **record layer** stores clinical and administrative history. The **operations layer** coordinates queues, admissions, beds, billing, departments, and discharge. An **AI assistance layer** may support a specific task, such as drafting a clinical note for review.

Those layers can be bought together or combined across systems. Either choice creates an integration obligation. A single suite is not automatically integrated in practice, and separate products are not automatically fragmented. Evidence comes from an end-to-end test in the proposed configuration.

Patient Square's scribe drafts notes for clinician review. It does not diagnose, autonomously approve a record, or replace the OPD or IPD workflow. Prescription output is a draft for clinician review, not direct transmission to a pharmacy. Any ICD-10 output is a suggestion, not autonomous coding.

## Assign ownership before configuring screens

Software cannot resolve a workflow that the hospital has not assigned. Create a simple responsibility map before implementation.

- Registration owns identity capture and defined correction paths.
- Clinical leadership owns documentation and order policies.
- Nursing or ward leadership owns inpatient handoffs relevant to its scope.
- Pharmacy, laboratory, radiology, and stores own their work queues and exception paths.
- Finance owns tariff, deposit, payer, refund, and reconciliation rules.
- Privacy and security owners approve access, audit, and data-use controls.
- IT owns system availability and interfaces, not the clinical meaning of every field.

Names will vary by facility. The point is to prevent a failed handoff from becoming "the software team's problem" after go-live.

## Test exceptions, not just the ideal visit

Ask each shortlisted vendor to run the same scenario pack. Include cases that stress the seam between departments:

- the patient already exists under a slightly different name;
- the planned admission is cancelled after a deposit;
- an OPD result arrives after the patient reaches the ward;
- a patient moves wards before an order is completed;
- a discharge bill is corrected and reissued;
- an authorised correction is required after the episode closes;
- the network is unavailable at a critical desk.

Record the expected behaviour, actual behaviour, evidence, owner, and severity. This produces a procurement record that a generic "supports OPD and IPD" tick cannot provide.

## Apply privacy rules to the whole journey

Moving from OPD to IPD typically widens the set of staff and departments involved. Access should follow purpose and role rather than broad convenience. Test whether the system records access and changes, supports timely removal of access, and prevents users from seeing information outside their duties.

The Digital Personal Data Protection Act, 2023 applies a legal framework to digital personal data. This article is an operational buying guide, not legal advice. A product label does not certify a hospital's compliance; the hospital should obtain advice for its processing, notices, consent where applicable, security, retention, and response duties.

ABDM integration also needs precise language. Patient Square describes it as roadmap work and does not claim ABDM certification or completed milestones. Ask every vendor to name the capability, current environment, evidence, and responsible operating party.

## Choose software by the hardest handoff

A clinic with no beds may need a strong OPD record and practice workflow without an IPD module. A hospital needs continuity across admission, ward work, department services, finance, and discharge. The right scope follows the facility, not the largest bundle a vendor can quote.

Before signing, run one patient through the hardest OPD-to-IPD handoff you expect. Reconcile the record, orders, results, medicines, charges, permissions, and audit trail. Then repeat it with an exception. The second run usually teaches you more than the first.

Patient Square Hospital Copilot can be discussed in either of two configurations: alongside an incumbent HIS, or with the complete Patient Square HIS/EHR for an agreed scope. Discovery should establish which modules and integrations are actually included. It should not assume unlisted departmental capabilities.

[compare the options](/in/compare/)

## Sources

- [National Informatics Centre: eHospital module list](https://ehospital.gov.in/ehospitalsso/ehosModuleList.jsp)
- [National Health Mission: Indian Public Health Standards](https://nhm.gov.in/index1.php?lang=1&level=1&lid=154&sublinkid=284)
- [India Code: Digital Personal Data Protection Act, 2023](https://www.indiacode.nic.in/bitstream/123456789/22037/2/a2023-22.pdf)
- [Patient Square: Hospital Copilot for India](https://patientsquare.com/in/products/hospital-copilot/)

---

## Patient Dismissal Letter: A State-Aware Template
https://patientsquare.com/us/blog/patient-dismissal-letter-template/
Published 2026-10-05 · Tags: patient-dismissal, practice-policy, template, continuity-of-care

Draft a patient dismissal letter without inventing a universal notice period, and pair it with continuity, record-transfer, delivery, and exception checks.

Use counsel-approved language that identifies the patient and practice, states the effective date, explains any interim-care boundary, gives a route for finding another clinician, describes record transfer, and supplies contact details. The exact reason, notice, delivery method, and exceptions depend on the jurisdiction and case.

A dismissal letter is the last step in a controlled decision, not the first response to a difficult afternoon. The letter should create a safe, traceable transition: clear effective date, interim-care boundary, route to another clinician, and record-transfer instructions. Your state and case decide the exact wording.

> **Before you draft the letter**
>
> - Do the case review before drafting the letter.
> - Never paste in a universal notice period.
> - Separate factual history from blame or argument.
> - Pair the letter with continuity, record, delivery, and exception logs.

## Start with a release decision sheet

Before the letter, complete this one-page control:

| Question | Owner | Evidence or decision |
|---|---|---|
| Is the relationship being ended by the clinician, the patient, or the practice? | Clinical lead | |
| Is urgent, active, postoperative, prenatal, controlled-medication, or other time-sensitive care involved? | Treating clinician | |
| What state, licensing-board, payer, contract, or facility rule applies? | Compliance or counsel | |
| What notice period and interim-care scope were approved for this case? | Counsel and clinician | |
| Can the patient realistically locate replacement care? | Practice manager | |
| Does a disability, discrimination, retaliation, or communication issue need review? | Compliance or counsel | |
| How will records move after valid authorization? | Records owner | |
| Which delivery method and proof were approved? | Practice manager | |

Stop if any owner is blank. A template cannot resolve a continuity-of-care problem.

## Copyable patient dismissal letter

Complete every blank. Delete every sentence your reviewer did not approve.

```text
PRACTICE LETTERHEAD: ______________________________

DATE: _____________________________________________

PATIENT NAME: _____________________________________
PATIENT ADDRESS: __________________________________

Re: Change in the patient-physician relationship

Dear _____________________________________________,

This letter confirms that __________________________ will no longer provide
ongoing care to you after __________________________.

OPTIONAL COUNSEL-APPROVED FACTUAL REASON OR NEUTRAL STATEMENT:
___________________________________________________

Until the effective date, our approved care boundary is:
INTERIM OR URGENT CARE, CURRENT TREATMENT, REFILLS, RESULTS, AND CONTACT ROUTE:
___________________________________________________

Please arrange care with another qualified clinician. You may contact
__________________________ at ______________________ for help locating a clinician. We cannot guarantee
that a listed clinician will accept you or your insurance.

To request a copy or transfer of your records, use:
___________________________________________________
We will process a valid request under the practice's records policy and
applicable law.

For questions about this notice, contact __________ at __________.

Sincerely,

AUTHORIZED CLINICIAN OR PRACTICE REPRESENTATIVE:
___________________________________________________
```

Do not use this as a fill-and-send form. It is a structure for the words your state-specific review approves.

## The notice period is a decision, not boilerplate

The [AMA Code of Medical Ethics Opinion 1.1.5](https://code-medical-ethics.ama-assn.org/ethics-opinions/terminating-patient-physician-relationship) says physicians should notify the patient long enough in advance to permit securing another physician and should help transfer care when appropriate. It does not supply one universal number for every US case.

Put the approved period in the decision sheet, then calculate the effective date. Check state-board rules, payer or facility obligations, current treatment, the availability of replacement care, and any emergency duties. A familiar "30 days" line is not a substitute for that review.

This matters most when the practice is already frustrated. A date chosen from habit can create a gap for the patient and a preventable risk for the practice.

## Write facts, not a closing argument

If the reason belongs in the letter, use dated, documented facts and the approved policy language. Avoid diagnoses about behavior, sarcasm, speculation, and a recap of every unpleasant conversation.

Compare these two lines:

- "You have shown that you do not respect our time."
- "Our records show missed appointments on DATE 1 and DATE 2 after notices sent on NOTICE DATE 1 and NOTICE DATE 2."

The second can be checked. Whether it belongs in the final letter is still a reviewer decision.

For a fair upstream policy, use the [medical-office no-show policy template](../medical-office-no-show-policy/). If the problem is the record rather than the relationship, route it through the [medical-record amendment workflow](../medical-record-amendment-request/).

## Make the transition executable

The letter should tell the patient what to do next. Name a real referral route, not "find another doctor." State what the practice will do during the approved interim period. List the record-request route and a contact for questions about the notice.

[HHS OCR's access guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html) explains the HIPAA right of individuals to access protected health information in a designated record set, subject to the rule's scope and exceptions. Keep the access workflow separate from the billing dispute or conduct issue that led to dismissal.

Do not promise that another clinician will accept the patient. Give verified resources and let the patient or authorized representative choose.

## Track the delivery without turning it into theatre

Use the delivery method your state-specific reviewer approves. Keep the sent letter, address used, date, method, delivery evidence, returned-mail handling, phone or portal follow-up if approved, and any patient response.

The practice also needs a result and refill sweep. On the day the letter goes out, ask:

- Is any test pending?
- Is a referral unfinished?
- Is a medication decision due during the interim period?
- Is a postoperative or other scheduled follow-up already booked?
- Who owns each loose end before the effective date?

A perfect letter does not close an unmonitored result queue.

## Rehearse one exception case

Use synthetic facts: a patient with repeated no-shows has a pending pathology result and lives in an area with limited specialty access. Run the dismissal policy, then pause it at every exception review.

The exercise passes only if the team can name the clinical owner, legal or compliance reviewer, effective date, interim-care boundary, result owner, referral resource, record route, and delivery evidence. If the software simply mails the template, the hard part is still manual and invisible.

We think exception handling is the actual product requirement here. Mail merge is easy.

## Keep product scope honest

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

That does not claim an automated patient-dismissal module, a legal notice generator, a referral guarantee, or state-law review. Those controls stay with the practice and qualified reviewers.

If you are evaluating the record around the decision, [review the current Practice Copilot scope](../../products/practice-copilot/). Review the [current plan scope](../../pricing/) and [security posture](../../security/) separately from this policy work.

---

## Superbill Template: A Safer Checkout Worksheet
https://patientsquare.com/us/blog/superbill-template-medical-practice/
Published 2026-10-03 · Tags: superbill, medical-billing, template, private-practice

Copy a superbill worksheet, separate it from a CMS-1500 claim and invoice, and test the handoff before a patient submits it to a health plan.

A superbill is an itemized, patient-facing record of a visit that can carry provider, patient, service, diagnosis, procedure, and charge details. It is not automatically an insurance claim. The patient and practice should confirm what the patient's plan accepts before relying on it for reimbursement.

A superbill is a compact handoff. It is not a magic insurance form. It records who provided the service and what happened. It also lists the reviewed codes and what the patient paid. The useful template is the one your biller can trace back to the signed encounter without guessing.

> **Read this before copying**
>
> - Keep the superbill, invoice, and insurance claim as three named documents.
> - Lock practice identifiers once; review encounter fields every time.
> - Treat diagnosis or procedure suggestions as inputs, never final coding.
> - Test the document against one real payer workflow before giving it to every patient.

## Copy this blank superbill worksheet

This is an educational starting point. Your payer contracts, specialty, state, and billing workflow decide the final fields and codes.

```text
SUPERBILL / ITEMIZED VISIT STATEMENT

PRACTICE
Legal practice name: __________________________
Practice address: _____________________________
Phone: _______________________________________
Tax identifier used for this workflow: ________

PROVIDER
Rendering clinician: __________________________
Credentials: __________________________________
Individual NPI: _______________________________
Group NPI, if applicable: _____________________

PATIENT
Name: ________________________________________
Date of birth: ________________________________
Address: ______________________________________
Health-plan name: _____________________________
Member or subscriber ID: ______________________

ENCOUNTER
Date of service: ______________________________
Place of service: _____________________________

DIAGNOSIS LINES
A. Code: __________  Clinician verified: ______
B. Code: __________  Clinician verified: ______

SERVICE LINES
Service or procedure: _________________________
Code and modifier, if applicable: _____________
Diagnosis pointer: ____________________________
Units: __________  Charge: ____________________

PAYMENT
Amount charged: _______________________________
Amount paid: __________________________________
Balance: ______________________________________

ATTESTATION
Prepared by: __________________________________
Clinical and coding review completed by: ______
Date released to patient: _____________________
Correction or reissue reference: ______________
```

Do not preload a specialty code merely because it appears often. A favorite can save keystrokes, but the signed record has to support the choice made for this visit.

## Three documents that look alike but do different jobs

| Document | Main job | Who acts next | Failure to avoid |
|---|---|---|---|
| Superbill | Give the patient an itemized encounter record for a reimbursement workflow | Patient, plan, or billing team | Promising reimbursement |
| Invoice or receipt | Show charges, payment, and balance | Patient or practice | Calling it a claim |
| CMS-1500 | Submit a professional paper claim in the circumstances CMS permits | Eligible provider or supplier | Printing an unofficial copy and assuming it is submittable |

[CMS identifies the CMS-1500](https://www.cms.gov/medicare/billing/electronicbillingeditrans/1500) as the standard professional paper claim form used by eligible non-institutional providers or suppliers in specified billing circumstances. CMS also warns that a downloaded copy may not meet the scanning and print requirements for submission. That is enough reason to keep your in-house superbill template clearly labelled.

The superbill should also avoid making a promise the practice cannot control. A patient can use it to ask a plan for reimbursement. The plan decides. Benefits, coding acceptance, documentation requests, and payment all sit there.

## Freeze the practice block; review the visit block

Split the document into two layers.

The practice layer changes rarely: legal name, address, tax identifier, provider identifiers, and approved contact details. Assign one owner. Add a review date. [CMS's NPI standard](https://www.cms.gov/medicare/regulations-guidance/administrative-simplification/nationalprovidentstand) explains that covered health care providers use the NPI in HIPAA standard transactions. Your billing owner should decide which individual or organization identifier fits the actual arrangement.

The encounter layer changes every time: patient, service date, place of service, diagnosis lines, procedure or service lines, units, charges, and payment. Populate it only from the signed encounter and reviewed billing workflow.

This split prevents a surprisingly common office mistake: fixing a wrong service date while accidentally overwriting a group identifier that should have stayed locked.

## Make the review trail visible

Use three initials boxes if three people touch the document:

1. The clinician confirms the encounter and clinical facts.
2. The coding or billing owner confirms code and charge fields.
3. The release owner confirms the correct patient and delivery route.

One person may perform more than one role in a solo practice. Keep the roles visible anyway. When a patient calls six weeks later, the practice should be able to locate the source note, the released version, and any correction without reconstructing the afternoon from email.

For a wider review of the record before billing, use the [medical chart audit checklist](../medical-chart-audit-checklist/). If the harder question is whether your current stack owns the billing handoff at all, map it with the [medical practice software stack guide](../medical-practice-software-stack/).

## Run a five-case test before launch

Do not start with your easiest visit. Use five synthetic cases:

- a single service with one supported diagnosis;
- two service lines pointing to different diagnosis lines;
- a group practice with rendering and organization identifiers;
- a corrected encounter that requires a reissued document;
- a patient whose plan rejects the first version and asks for another field.

For each case, trace every populated field back to its approved source. Then make the correction without erasing the earlier released copy. The test passes when a second staff member can explain what changed and why.

We think that version history matters more than a handsome PDF. A clean one-page form is useful. A clean one-page form nobody can reconcile is future rework.

## Patient Square's boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For a US practice, that sentence does not claim automated CPT selection, payer eligibility, claim submission, or a billing engine. The clinician owns the signed note and qualified billing staff own the superbill and claim workflow.

If documentation is the broken handoff upstream of your billing work, [review the current Practice Copilot scope](../../products/practice-copilot/). Check the reviewed note first, then decide what your existing billing process can safely reuse. Current plan scope is on the [US pricing page](../../pricing/), and privacy controls are on the [security page](../../security/).

---

## Medical Chart Audit Checklist for Small Practices
https://patientsquare.com/us/blog/medical-chart-audit-checklist/
Published 2026-10-02 · Tags: medical-chart-audit, documentation, compliance, checklist

Run a medical chart audit with a defined sample, evidence-based checklist, reviewer log, correction path, and follow-up owners instead of a vague spot check.

The scope determines the checklist. A documentation audit may check patient identity, encounter reason, supported assessment and plan, orders, results, signatures, dates, code support, corrections, and follow-up. A privacy, quality, or specialty audit needs a different approved checklist.

Seven charts are open on the compliance lead's screen. Three support the reported service. Two are missing a signed plan. One has a copied sentence from the wrong visit, and the last chart is fine but reached the auditor only because somebody skipped the random list. By lunch, the practice has five findings and no reliable denominator.

That is the difference between looking at charts and running an audit. A defensible audit names its question, population, sample, checklist, evidence, reviewer, and follow-up before the first record opens.

This template is an operating aid, not legal, coding, or clinical advice. Have the practice's compliance, billing, privacy, and clinical leaders approve the scope that applies to the audit.

## Copyable chart audit worksheet

```text
MEDICAL CHART AUDIT

Audit question: _________________________
Population and date range: ______________
Sample method: __________________________
Sample size: ____________________________
Reviewer and role: ______________________
Standard or policy version: ______________

CHART IDENTIFIER: _______________________
Do not place unnecessary patient data in the audit log.

ITEM                                      PASS  FAIL  N/A  EVIDENCE / FINDING
Correct patient and encounter              [ ]   [ ]   [ ]  ______________
Reason for encounter present               [ ]   [ ]   [ ]  ______________
Relevant history or prior results present  [ ]   [ ]   [ ]  ______________
Assessment or clinical impression present  [ ]   [ ]   [ ]  ______________
Plan for care present                      [ ]   [ ]   [ ]  ______________
Orders have documented rationale           [ ]   [ ]   [ ]  ______________
Progress or response documented when due   [ ]   [ ]   [ ]  ______________
Date and author identity present            [ ]   [ ]   [ ]  ______________
Reported codes supported by the record      [ ]   [ ]   [ ]  ______________
Required review or signature completed      [ ]   [ ]   [ ]  ______________
Correction history preserved                [ ]   [ ]   [ ]  ______________
Result or referral follow-up owned           [ ]   [ ]   [ ]  ______________

Finding class: Isolated / Repeated / Systemic / Undetermined
Immediate action, if any: _________________
Owner: ___________________________________
Due date: _________________________________
Recheck method: ___________________________
```

The checklist is deliberately modest. Add an item only when the audit question and controlling source require it. Forty generic boxes produce fast check marks and weak evidence.

## Write one audit question

Start with a sentence that can fail. Examples:

- Do signed office-visit records support the codes reported during August?
- Are test results assigned, reviewed, communicated, and closed under the practice policy?
- Do corrected notes preserve the original entry and the approved amendment history?
- Are AI-drafted notes reviewed and signed by the responsible clinician before use?

Each question requires a different population and reviewer. A billing audit does not become a clinical quality audit because both use charts. If two questions need different expertise, run two audits and connect the findings later.

Name exclusions before sampling. Otherwise reviewers can quietly skip the hard charts and leave a sample that proves only the easy cases were easy.

## Define the population before the sample

Write the date range, clinician group, visit type, payer or program when relevant, status, and any approved exclusions. Count the eligible records. Then select from that list.

CMS's [sample manual EHR review checklist](https://www.cms.gov/files/document/ehrmanrevja062816pdf) describes a random sample of five to ten electronic health records per federal program or provider as an illustrative starting point and suggests that a small practice may spread recurring reviews across the year. That is not a universal sample-size rule. A suspected systemic error, refund question, patient-safety concern, or legal hold can require a different design and specialist advice.

Record the selection method. "Ten charts chosen by office manager" does not show whether the manager chose consecutive visits, random records, denials, high-level codes, or familiar patients.

## Tie every row to a source

The core worksheet reflects CMS's current [Evaluation and Management Services compliance tips](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services). CMS tells E/M billers to keep the record complete and legible, document the encounter reason and relevant history, include an assessment and care plan, identify the date and observer, and support reported codes with the record.

That source does not answer every audit question. A specialty procedure, payer contract, state rule, privacy review, or internal quality policy can add different requirements. Put the source and version next to the item. When a rule changes, the team can update the affected row instead of guessing which old checklist was used.

Use `N/A` only when the reviewer writes why the item does not apply. A blank is not evidence.

## Capture evidence, not reviewer mood

For a pass, note the section or event that supports it. For a failure, quote the relevant short phrase or describe the missing event without copying unnecessary patient details into a second file.

Separate four kinds of finding:

1. The record lacks required information.
2. The record contains information that does not support the reported action or code.
3. The workflow failed outside the note, such as an unsigned draft or an unowned result.
4. The reviewer cannot decide because the standard or evidence is unclear.

The fourth class is useful. It tells the practice to repair the checklist or escalate the interpretation rather than forcing a false pass or fail.

## Review patterns before blaming people

One missing signature may be an isolated miss. The same missing signature across several clinicians can point to a template, permission, training, or queue problem. Preserve that distinction in the summary.

Look at denominator and distribution. "Four failures" means something different in four charts than in four hundred. Break recurring findings down by template, visit type, clinician, location, and time period only when the sample supports that comparison and privacy controls allow it.

Do not turn an audit into a leaderboard. The fastest way to destroy reporting is to punish a person for showing where the system fails.

## Correct through the approved record path

An audit log should not silently rewrite a signed chart. Route each correction through the EHR's amendment or addendum function and the practice's approved policy. Preserve the author, date, reason, and history.

Billing and compliance leaders should decide what requires claim review, refund analysis, disclosure, counsel, or payer contact. Clinical leaders should own patient-care follow-up. The auditor identifies evidence; the right owner decides the response.

Give each action a due date and a recheck. "Education provided" is not closure. A recheck might sample the next five eligible records after a template fix or confirm that every old result in a queue has an assigned owner.

## Audit the tool around the note

CMS's manual review material includes EHR security settings, audit logs, access restrictions, templates, macros, and copy-and-paste behavior among possible program-integrity review areas. A clean-looking note can still come from a broken process.

Inspect the events around the chart when the audit question calls for it:

- Who created, edited, and signed the entry?
- Did a template carry forward stale text?
- Was the note available to the correct user and blocked from an unauthorized role?
- Did an order, result, referral, or message reach its queue?
- Was a correction preserved rather than overwritten?

For AI scribe use, compare the authorized encounter evidence, draft, clinician edits, and signed note under the practice's privacy and retention rules. The [AI scribe documentation audit guide](/us/blog/ai-scribe-clinical-documentation-audit/) provides a separate error taxonomy for that narrow question.

## Close with a one-page audit record

The final record should state the question, population, sample, checklist version, reviewer, counts, material findings, immediate actions, owners, due dates, and recheck. Link to protected workpapers rather than copying patient data into the summary.

Keep disagreement visible. If a coder and clinician interpret an item differently, preserve both first-pass views and record who adjudicated the final result. That disagreement may expose an unclear policy worth fixing.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

If the recurring finding is documentation work left until late at night, [review the current Practice Copilot scope](../../products/practice-copilot/). Audit the signed output and the review trail exactly as you would for any other documentation workflow.

---

## Medical Record Retention Policy Template for Practices
https://patientsquare.com/us/blog/medical-record-retention-policy/
Published 2026-10-02 · Tags: medical-record-retention, hipaa, policy-template, records-management

Build a medical record retention policy without confusing HIPAA's six-year documentation rule with state medical-record retention requirements.

The HHS Office for Civil Rights says the HIPAA Privacy Rule does not set a medical-record retention period. State law generally governs how long medical records must be kept. HIPAA separately requires certain policies, procedures, and required compliance documentation to be retained for six years.

The most dangerous line in a medical record retention policy is often "HIPAA requires seven years." HHS says HIPAA does not set the retention period for patient medical records. State law generally does. HIPAA's well-known six-year period applies to specified compliance documentation, which is a different bucket.

That distinction belongs at the top of the policy, not in a footnote discovered during an audit. Use the template below to build a schedule with counsel and the people who run the systems.

## Copyable retention policy skeleton

```text
MEDICAL RECORD RETENTION AND DISPOSAL POLICY

Policy owner: ___________________________
Approved by: ____________________________
Effective date: _________________________
Next review: ____________________________

1. PURPOSE
Define how the practice classifies, retains, protects, retrieves, preserves,
and disposes of records across paper, primary systems, backups, exports,
vendors, and closed-practice arrangements.

2. SCOPE
People, locations, systems, vendors, and record classes covered: __________

3. AUTHORITY REGISTER
Federal source: _________________________
State professional/licensing source: ____
Facility or payer source: _______________
Contract or insurer source: _____________
Counsel review date: ____________________

4. RETENTION SCHEDULE
Record class | Trigger date | Minimum period | Controlling source | Owner
Adult medical record | ____ | ____ | ____ | ____
Minor medical record | ____ | ____ | ____ | ____
Imaging or diagnostic record | ____ | ____ | ____ | ____
Billing and claim support | ____ | ____ | ____ | ____
HIPAA-required documentation | ____ | ____ | ____ | ____
Patient request and disclosure records | ____ | ____ | ____ | ____
Contracts and business-associate records | ____ | ____ | ____ | ____
Other approved class | ____ | ____ | ____ | ____

5. HOLDS
Who can issue a hold: ___________________
How systems and vendors receive it: _____
How release is authorized: ______________

6. ACCESS AND CONTINUITY
How records remain retrievable: __________
How patients request access: _____________
Closed-practice or custodian plan: _______

7. DISPOSAL
Approval: _______________________________
Method by medium: _______________________
Vendor evidence: ________________________
Disposal log fields: ____________________

8. EXCEPTIONS, TRAINING, AND REVIEW
Exception approver: _____________________
Training cadence: _______________________
Annual test and review: _________________
```

Do not fill the period column from a generic web table. The answer can depend on state, license, facility type, patient age, payer, record class, and whether a hold exists.

## Split medical records from HIPAA documentation

The [HHS Office for Civil Rights FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/does-hipaa-require-covered-entities-to-keep-medical-records-for-any-period/index.html) is direct: the Privacy Rule does not include medical-record retention requirements, and state laws generally govern the period. HIPAA still requires safeguards for protected health information for as long as the covered entity maintains it, including disposal.

The [HHS Security Rule summary](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html) describes a separate six-year requirement for documentation that the Security Rule requires. The clock runs until six years after the later of creation or the date the document was last in effect.

Create at least two rows:

- Patient medical records, with the applicable state and specialty sources.
- HIPAA-required policies, procedures, assessments, and actions, with the federal documentation source.

More rows will follow. Combining the first two is how a confident but wrong "HIPAA period" enters contracts, backup settings, and staff training.

## Use trigger dates, not just durations

"Keep seven years" is incomplete. Seven years from what? The last visit, discharge, record creation, the patient's age, contract end, or the date a policy stopped being effective can produce different disposal dates.

Write the trigger beside the period. Test it against an adult patient, a minor, a deceased patient, a long-running episode of care, a corrected record, and a closed location. If the system cannot calculate the trigger safely, retain the record until the practice has a reviewed method.

Version the authority register. State rules and program requirements can change. Record the exact citation, programme, effective date, counsel review, and next review. A screenshot with no source date will be a poor guide five years later.

## Inventory every copy

The EHR is only the first row. List paper files, scanned-document stores, imaging systems, billing platforms, patient portals, secure messaging, email, file shares, transcription systems, data warehouses, backups, cold archives, vendor support tools, and exports.

For each system, record:

1. Which record classes it stores.
2. Whether it is authoritative, a working copy, or a backup.
3. The retention or expiry control.
4. Who can place and release a hold.
5. How deletion or destruction is proved.

Backups deserve blunt language. A backup is not an alternative permanent archive unless the practice can search, restore, protect, and produce it under the approved policy. At the same time, deleting the production chart while leaving indefinite vendor snapshots does not complete disposal.

## Stop the clock for holds

A legal, audit, investigation, payer, patient-safety, or preservation hold can override the ordinary destruction date. Define who may issue a hold, how it identifies affected records, and how every custodian and vendor receives it.

Make release just as formal. A staff member should not resume deletion because a meeting ended or an email thread went quiet. Record the authorized release, date, scope, and systems notified.

Test holds with fake identifiers. Confirm that the EHR, paper archive, backup owner, billing vendor, and any other custodian block destruction for the same set. A hold that reaches only the main chart is a partial hold.

## Preserve access during the retention period

A retained record must remain readable and retrievable. Plan for software changes, encryption keys, media aging, staff turnover, vendor exit, and practice closure.

The [HHS right-of-access guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/access/index.html) describes individuals' access rights under the Privacy Rule. The retention policy should point to the separate access-request procedure and make clear who produces records after a location closes or a system is retired.

Export samples before a migration. Open them without the old system. Check text, attachments, image references, author, dates, amendments, and audit information that the approved scope requires. A successful file count is not the same as a usable record.

## Dispose by medium and keep evidence

HHS publishes [guidance on disposal of PHI](https://www.hhs.gov/guidance/document/faqs-disposal-phi-full-document-0). The practice should approve methods for paper, local devices, removable media, hosted systems, and vendor-held copies. Staff should never improvise disposal at the end of a storage project.

Keep a disposal log that avoids unnecessary PHI. It can record the record class, date range, quantity or batch identifier, authority, hold check, method, vendor certificate where used, approver, and completion date.

Deletion needs exception handling. If a vendor cannot remove a backup immediately, document the technical limit, access restriction, expiry schedule, contract duty, and evidence that deletion later completed. Do not label the batch destroyed while an accessible copy remains unexplained.

## Run one annual retrieval and disposal test

Choose synthetic records in several classes. Calculate their dates, place one on hold, retrieve one from archive, attempt an access request, and dispose of one eligible test copy through the approved path.

Record every handoff. The exercise should reveal who owns old media, whether vendor tickets close with evidence, and whether staff can distinguish medical records from HIPAA compliance documentation.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square does not decide a practice's retention schedule. If late documentation is making the record harder to close and govern, [review the current Practice Copilot scope](../../products/practice-copilot/). Keep retention, holds, access, and disposal under the practice's approved records programme.

---

## Suki AI Pricing: Build a Quote Without a List Price
https://patientsquare.com/us/blog/suki-ai-pricing/
Published 2026-10-02 · Tags: suki-ai, pricing, ai-scribe, procurement

Suki does not publish a simple per-clinician list price. Use this quote worksheet to expose licenses, services, EHR work, support, and exit cost.

Suki does not publish a per-clinician price on its solutions page; the subscription is set in an order form and services may be quoted separately. Request a written quote with recurring and one-time costs.

Suki does not put a simple per-clinician dollar figure on its public solutions page. Its terms place subscriptions and pricing in an order form and purchased professional services in a statement of work. You can still build a firm budget. The trick is to request the quote in pieces before the sales call turns them back into one number.

> **Quote notes**
>
> - Do not guess a Suki seat price from an old review or forum post.
> - Separate the subscription, EHR work, professional services, support, and exit.
> - Model the same users and workflow for every finalist.
> - Keep vendor fees and your own implementation labor in different rows.

## The public record tells you how to ask

Suki's [solutions page](https://www.suki.ai/solutions/) describes ambient documentation, EHR-connected dictation, coding-related workflows, clinical reasoning features, and products for clinicians and partners. Its cost FAQ does not show a dollar figure and directs the buyer toward sales.

The legal structure is more revealing. Suki's [Terms of Service](https://www.suki.ai/terms-of-service/) define an order form as the document that states purchased subscriptions and pricing. The same terms define a statement of work for purchased integration, custom development, or other professional services. Fees come from the applicable order form or statement of work.

That does not mean every deployment has a separate service bill. It means a buyer should refuse an unlabeled total. Ask which work is part of the subscription, which work has its own statement, and which work the health system must staff.

## Send the worksheet before the demo

Use this table as the required pricing response. A blank cell becomes a written assumption, not a verbal promise.

| Cost line | Vendor response | One-time or recurring | Renewal rule | Acceptance evidence |
|---|---|---|---|---|
| Subscription unit |  |  |  | Named product and eligible user |
| Minimum commitment |  |  |  | Users, sites, term, and start date |
| Ambient documentation |  |  |  | Included use and any meter |
| EHR workflow |  |  |  | Named system, destination, and correction path |
| Implementation |  |  |  | Tasks, owners, dates, and pass conditions |
| Professional services |  |  |  | Attached statement of work |
| Training and support |  |  |  | Audience, hours, and response targets |
| Exit assistance |  |  |  | Export, access removal, and deletion evidence |

Run the math over twelve months. For variable charges, include an expected month and a month with 25 percent more use. For fixed charges, show the cost of unused licenses. Add internal hours for clinical ownership, IT, privacy, training, and support.

The result is not glamorous. Good. Procurement goes wrong when a beautiful demo gets a single price line and a messy implementation gets none.

## Match the quote to the exact workflow

Suki's public page describes more than note drafting. It names structured notes, EHR-connected dictation, and downstream workflows. A buyer should not assume every public capability is included in every offer, available in every EHR, or configured without services. Put the exact deployed workflow in the quote.

Ask the seller to demonstrate four moves with synthetic data:

1. Start and stop capture using the contracted interface.
2. Correct a material detail before the clinician accepts the draft.
3. Deliver the final content to the destination named in the proposal.
4. Recover when that destination or another dependency is unavailable.

If the proposal includes coding or revenue work, give that workflow its own owner and acceptance script. Do not let it borrow a passing score from note generation. The [AI scribe demo script](../ai-scribe-vendor-pricing-live-demo/) provides a neutral evidence scale, and the [quote-normalisation guide](../ai-scribe-vendor-pricing-quote-normalisation/) keeps fees comparable.

## Put privacy terms beside price

Suki's terms describe customer data, third-party products, security obligations, and the roles of order forms and services. Your signed documents control your purchase, so have privacy and legal owners review the actual package rather than a marketing page.

For a HIPAA covered entity using a business associate, HHS says the written agreement must address permitted uses, safeguards, incident reporting, subcontractors, and return or destruction at termination, among other subjects ([HHS business associate contracts](https://www.hhs.gov/hipaa/for-professionals/covered-entities/sample-business-associate-agreement-provisions/index.html)). Those contract terms affect cost. Incident support, data return, and deletion evidence need owners even if they do not appear on the invoice.

Keep the security review independent of the pricing review. A lower quote does not answer a data-use question. A strong security answer does not prove the workflow fits.

## Compare Suki with a published-price path

Patient Square publishes US practice prices on its [pricing page](../../pricing/). Assist is $99 month to month or $79 per clinician per month on annual billing. Copilot is $149 or $119 and adds the bundled AI EHR. Autopilot is $249 or $199. Hospital Copilot is separately demo-priced.

Patient Square is an AI clinical platform. Practice Copilot includes an ambient AI Medical Scribe that prepares a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. A practice can keep its existing record system or use the bundled AI EHR from the Copilot tier.

The public price reduces one uncertainty. It does not erase the clinic's work. You still need to test notes, define transfer or record workflow, train staff, and settle support. Compare Suki's completed quote with Patient Square's subscription plus the internal cost of the actual pilot.

| Buyer condition | Better first fit |
|---|---|
| Health system wants Suki's stated EHR-connected workflow and services | Suki |
| Buyer needs a contract shaped around enterprise deployment | Suki |
| Independent practice wants a published starting point | Patient Square |
| Practice wants a bundled record system at a published tier | Patient Square Copilot |

Suki is the honest pick when its connected workflow is the reason you are buying and your organization can run the sales, contract, and implementation process. Patient Square is the cleaner pick when the clinic wants a public price and a smaller boundary.

## Leave the call with three documents

Ask for the order form, every applicable statement of work, and a twelve-month price schedule. The schedule should identify renewal timing and any variable meter. Add a fourth document when the workflow touches protected health information: the applicable privacy and business-associate package.

Do not ask, "What does Suki cost?" Ask, "What will this named workflow cost for these users over twelve months, including services and exit?" Run the same workflow with Patient Square and put both answers in the worksheet. The quote becomes useful when its boundaries stop moving.

## FAQs

### Suki's published price

Suki's public solutions page does not state a per-clinician dollar price. Its terms say subscriptions and pricing sit in the executed order form, while professional services can sit in a separate statement of work. Ask for a written quote that separates every recurring and one-time charge.

### Quote lines to request

Request the subscription unit, minimum users, included products, implementation, EHR work, training, support, professional services, renewal increase, and exit assistance. If any amount depends on use, ask for the meter, included allowance, reporting method, overage rate, and budget control.

### Professional-services pricing

Suki's terms define an order form for subscriptions and pricing and a statement of work for purchased professional services. That does not prove every buyer pays a separate fee, but it means the quote should say which services are included and which require a statement of work.

### Comparing a custom quote with a list price

Convert both options to a twelve-month total for the same clinicians and workflow. Include implementation, EHR work, training, support, internal labor, and exit. A public subscription can still require local effort, while a custom quote may bundle services that a list price omits.

### Suki's best fit

Suki can be the better fit when a health system wants the EHR-connected clinical and revenue workflows described on Suki's product site and is prepared for a scoped sales and services process. A small practice may prefer a public price and a narrower rollout.

### Patient Square's US practice pricing

Patient Square publishes three per-clinician tiers: Assist at $99 monthly or $79 with annual billing, Copilot at $149 or $119 with a bundled AI EHR, and Autopilot at $249 or $199. These practice prices are not a substitute for a separately scoped hospital quote.

---

## After-Visit Summary Template for Medical Practices
https://patientsquare.com/us/blog/after-visit-summary-template/
Published 2026-10-01 · Tags: after-visit-summary, patient-instructions, template, documentation

Copy a plain-language after-visit summary template that separates today's decisions, medications, pending results, follow-up, and urgent instructions.

Identify the patient, visit, and clinician; state what was addressed in plain language; list medication decisions, orders, referrals, pending results, home instructions, follow-up ownership, and urgent contact instructions that the clinician approved. Remove sections that do not apply.

The useful after-visit summary is the one a patient can act on at 7:30 that evening, after the clinic is closed and the conversation has blurred. It names today's decisions, the next action, and who owns each loose end. It does not dump the progress note into a portal and call the job finished.

The template below is educational. The treating clinician must approve every patient-specific instruction, medication statement, result, referral, and warning.

## Copyable after-visit summary

```text
AFTER-VISIT SUMMARY

Patient: _______________________________
Visit date: ____________________________
Clinician: _____________________________
Practice and phone: ____________________
After-hours or urgent contact route: ____

WHY YOU CAME IN
[One plain-language sentence]

WHAT WE DISCUSSED TODAY
[Only the findings or decisions the clinician reviewed with the patient]

MEDICATION DECISIONS
Started: _______________________________
Changed: _______________________________
Stopped: _______________________________
Continue as discussed: _________________
Questions or problems: contact __________

TESTS, PROCEDURES, AND REFERRALS
Completed today: _______________________
Ordered today: _________________________
Referral: ______________________________
Who schedules or calls: _________________

PENDING RESULTS
Result still pending: ___________________
Who reviews it: _________________________
How and when you should hear: ___________
What to do if you hear nothing: _________

WHAT TO DO AT HOME
1. _____________________________________
2. _____________________________________
3. _____________________________________

FOLLOW-UP
Next visit or time window: ______________
Who books it: ___________________________
Bring or track: _________________________

GET URGENT HELP IF
[Clinician-approved, condition-specific instructions and contact route]

PATIENT CHECK
The patient or representative received and reviewed this summary.
Questions or correction noted: __________
```

Delete empty sections. A two-page form full of "not applicable" teaches the reader to skim past the one line that matters.

## Write for the patient, not the chart

The [ASTP/ONC after-visit summary technical guide](https://www.healthit.gov/sites/default/files/measure-tools/avs-tech-guide.pdf) separates identifying information, provider comments, diagnoses, orders, available results, medications, allergies, and follow-up material. Its plain provider-comment frame is still good editorial discipline: what you have, what it means, and what you do next.

Use the terms spoken during the visit. If a diagnosis needs a technical label, pair it with a short explanation. Spell out the action before the rationale. "Call cardiology at 555-0100 by Friday" is easier to use than a paragraph beginning with a review of the differential.

An after-visit summary is not the place to introduce a new diagnosis or treatment. If the patient did not hear it from the clinician, stop and route the draft back for review.

## Put medication changes in their own box

Medication decisions are easy to bury and costly to misunderstand. Separate started, changed, stopped, and continued medicines. Include the instructions that the clinician approved, then provide the practice's contact route for questions.

Do not infer a dose from an old medication list. Do not convert a prescription draft into patient instructions without clinician confirmation. If the EHR and the clinician's decision disagree, resolve the discrepancy before release.

The summary can say that no medication change was made if that fact helps the patient. Silence is ambiguous. A patient may reasonably wonder whether the old plan still applies.

## Give every pending result an owner

"Labs pending" is not a plan. Name the test, the responsible reviewer, how the patient will receive the result, and the step to take if the promised communication does not arrive.

Keep completed and pending results apart. A result reviewed during the visit can appear in the completed section. A specimen collected today belongs under pending until an authorized clinician has interpreted and released it through the approved workflow.

This is also where operational failures surface. If the practice cannot name who watches a result queue, the summary has found a workflow gap. Fix the queue rather than writing around it.

## Make referrals and follow-up executable

A referral line needs a destination and an owner. State whether the practice sends the referral, the patient calls, or the receiving office will make contact. Add the number or portal path when the practice has approved it.

Follow-up needs a time or condition. "Return as needed" may be the clinician's decision, but it should not be a default inserted because nobody chose a date. For a planned return, state the window and who schedules it.

The [ASTP/ONC ambulatory clinical-summary fact sheet](https://www.healthit.gov/resource/fact-sheet-providing-patients-ambulatory-care-settings-clinical-summary-office-visit) recommends reviewing the summary with the patient and explaining instructions or follow-up. That small handoff catches bad phone numbers, impossible dates, and instructions the patient cannot carry out.

## Keep urgent instructions specific and approved

Copying a universal warning paragraph into every summary creates noise. Use the clinician-approved instructions that fit the encounter and tell the patient which contact route to use. The summary should not diagnose a new emergency or invent a threshold.

If the practice uses a standard urgent-care block, give it a clinical owner and review date. Test how it renders on paper and a phone. Tiny gray text at the bottom is technically present and practically absent.

## Review the summary in under a minute

Before release, the clinician or authorized reviewer should answer these questions:

- Is this the correct patient, visit, and clinician?
- Does every diagnosis or finding appear in the approved encounter record?
- Do medication directions match the clinician's decision?
- Are pending results clearly marked with an owner?
- Are orders, referrals, and follow-up steps complete?
- Are urgent instructions appropriate to this visit?
- Does the patient-facing wording preserve the clinical meaning?

Read it on the device patients actually use. The [ASTP/ONC Patient Engagement Playbook](https://playbook.healthit.gov/playbook/pe/full/) shows why clear action steps and readable presentation matter in after-visit material. A clean layout is not decoration here. It helps the instruction survive the trip home.

## Test with a synthetic visit

Create a fake encounter that contains one medication change, one completed test, one pending result, one referral, and one follow-up window. Generate the summary through the real workflow. Then introduce a correction before release.

Check the portal, printed copy, and audit trail. Confirm that the correction reaches every version and that the old draft cannot be mistaken for the final patient copy. Repeat the test after any template or EHR change.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square produces clinician-reviewed drafts, not autonomous patient instructions. If the note and follow-up draft are where your team loses time, [review the current Practice Copilot scope](../../products/practice-copilot/) and judge the review path, not the first output alone.

---

## Heidi Health Pricing: Free, Clinician, and Teams
https://patientsquare.com/us/blog/heidi-health-pricing/
Published 2026-10-01 · Tags: heidi-health, pricing, ai-scribe, buyer-guide

Map Heidi's current Free, Clinician, and Teams plans to real clinic work, then compare limits, integrations, annual terms, and total cost.

Heidi’s Free plan includes core note drafting plus a shared allowance of 10 monthly advanced actions; Clinician and Teams add different capabilities. Compare current plan limits with the work your clinic needs.

Heidi's current US ladder has three buying doors: Free, Clinician, and Teams. Free is a real drafting test, not a pretend trial. Clinician removes several advanced-action limits. Teams moves governance and enterprise work into a sales conversation. The right plan depends on the work your clinic repeats, not the longest feature column.

> **Plan notes**
>
> - Free can test standard note generation and a small allowance of advanced actions.
> - Clinician is the individual paid path with a 14-day trial on the US page.
> - Teams is the route for shared controls, custom terms, and enterprise workflow.
> - Confirm the live dollar amount at checkout because the official public text can change by currency and billing term.

## Free is enough for a serious note test

Heidi's [plan help page](https://support.heidihealth.com/en/articles/8885030-heidi-s-pricing-plans-cost-and-features) says Free includes unlimited transcription and standard-template notes. It also gives a shared monthly allowance of 10 advanced actions for work such as custom templates, Ask Heidi, forms, and patient or session linking. When the allowance is used, standard note generation remains available.

That is enough to test the first question: does the draft reduce or increase the clinician's editing work? Run ordinary visits, interruptions, uncertain histories, and one correction after the initial draft. Do not spend all 10 advanced actions polishing a demo template before you know whether the core note fits.

Track four numbers for each visit: minutes to review, material corrections, transfer steps, and advanced actions used. No accuracy percentage. Seven cases cannot support one, and a tidy percentage hides the edits that matter.

## Clinician pays for repeated advanced work

Heidi says its Clinician plan adds unlimited advanced templates, documents, Ask Heidi, personalisations, and Evidence in patient visits where that feature is available. It also includes priority support, and the [official US pricing page](https://www.heidihealth.com/en-us/pricing) offers a 14-day trial.

The plan becomes easier to judge when you count repeat actions. A clinician who uses one standard template and seldom asks the tool to reshape a document may not need the upgrade. A clinician who builds custom templates for several visit types, drafts referral documents, or uses Ask Heidi during every clinic block can cross the free allowance quickly.

Use this weekly log:

| Work item | Times per week | Free-plan allowance used | Clinician value to test |
|---|---:|---:|---|
| Standard note |  | 0 advanced actions | Draft and review workflow |
| Custom template note |  | 1 per use under stated limit | Repeated specialty format |
| Ask Heidi edit |  | 1 per use | Revision time saved |
| Generated document |  | 1 per use | Referral or other approved output |
| Form or patient link |  | 1 per use | Local handoff and retrieval |

Heidi's plan definitions changed in 2026. Its [plan-change notice](https://support.heidihealth.com/en/articles/13921980-heidi-plan-changes-names-features-faqs) explains that older Pro and Practice names map to grandfathered Scribe plans, while the newer Clinician and Practice plans bundle paid Scribe and Evidence features. Screenshot the plan shown in your own account. An old review may be describing a tier that new US buyers cannot purchase.

## Teams is a governance quote, not a bigger individual plan

The public comparison places centralized billing, team management, guided onboarding, EHR integration, dedicated customer success, single sign-on, and custom terms or hosting in the team or custom part of the ladder. The help center says team and enterprise pricing goes through sales.

Ask the proposal to answer these lines:

| Team question | Written answer required |
|---|---|
| Who can create and approve shared templates? | Roles and approval path |
| What can an administrator see? | Audit and reporting scope |
| Which EHR workflow is proposed? | Named system, version, destination, and support owner |
| What does onboarding include? | Sessions, configuration, and acceptance criteria |
| What happens at termination? | Export, access removal, and deletion evidence |
| How does price change at renewal? | Term, notice, and increase rule |

A team quote earns its premium through administration and delivery, not by making the note intrinsically more clinical. Keep note quality and organizational fit as separate scores.

## Build the twelve-month cost from the live offer

Heidi says monthly and annual self-serve billing are available, while team and enterprise buyers contact sales. The official US page is the right source for the live amount. Its public page text did not expose a stable dollar figure during our September 17 review, so we will not copy a third-party number and call it official.

Record five fields from the checkout or proposal: currency, monthly amount, annual amount, number of paid users, and renewal date. Add onboarding, EHR work, support, and your own training hours. If the practice uses Free, still price the staff time spent transferring and checking notes.

This is the calculation:

`12-month cost = subscription + one-time services + internal implementation labor + expected support or integration charges`

Keep tax and discounts on separate lines. A discount has an end date. A workflow has a continuing owner.

## Compare Heidi with Patient Square by boundary

Patient Square publishes its US practice ladder on the [pricing page](../../pricing/). Assist is $99 month to month or $79 per clinician per month with annual billing. Copilot is $149 or $119 and adds the bundled AI EHR. Autopilot is $249 or $199. Hospital Copilot is separately demo-priced.

Patient Square is an AI clinical platform. Practice Copilot includes an ambient AI Medical Scribe that prepares a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. A practice may keep its current record system or use the bundled AI EHR from the Copilot tier.

Heidi is the better fit when a clinician wants a focused standalone scribe, likes the Free workflow, and plans to keep the rest of the software stack. Paying for a bundled record system you will not use makes no sense.

Patient Square is the better fit when a practice wants public pricing and intends to evaluate the record system or wider practice bundle too. Run the same visits through Patient Square and compare review work, not polished sample notes. The [Heidi alternatives guide](../heidi-health-alternatives/) covers the product-boundary choice; this page is about choosing and pricing the plan.

## Leave the trial with an answer

At the end of the test, decide three things. Did standard notes fit? Did the team repeatedly use advanced actions? Does the practice need shared governance or a custom EHR workflow? Those answers map to Free, Clinician, and Teams more reliably than feature count.

Keep the final edit log and the checkout screenshot with the buying record. Heidi is a strong fit when the standalone workflow is the whole job. A wider platform is a different purchase, not an automatic upgrade.

## FAQs

### Heidi's Free plan

Yes. Heidi's official help center says the Free plan includes unlimited transcription and note generation with standard templates, plus a shared allowance of 10 monthly actions for advanced templates, Ask Heidi, forms, and patient or session linking. Check the live plan page before subscribing.

### Clinician plan additions

Heidi says Clinician adds unlimited advanced templates, documents, Ask Heidi, personalisations, and in-session Evidence where available, plus priority support. The official US page advertises a 14-day trial. Availability can vary by region and EHR partner, so verify your workflow in the account.

### Finding the current Clinician price

Heidi's official US pricing page is the controlling source, but its public text did not expose a stable dollar amount during this review. It offers monthly and annual self-serve billing and routes team or enterprise buyers to sales. Confirm the live checkout price and renewal basis in writing.

### The Teams buying signal

Ask for Teams when shared templates, team controls, guided onboarding, custom hosting or terms, single sign-on, or an enterprise EHR workflow matter. Heidi's public comparison marks several of those capabilities as custom, so the proposal should identify what is included and what requires services.

### A Free-plan test

Use five ordinary visits and two difficult but synthetic visits. Track note edits, the advanced actions consumed, template changes, transfer steps, and staff support. The free tier can test the drafting workflow, but it does not prove that team governance or a specific EHR arrangement is ready.

### Patient Square's pricing boundary

Patient Square publishes its US per-clinician amounts: Assist is $99 monthly or $79 annually, Copilot is $149 or $119 with a bundled AI EHR, and Autopilot is $249 or $199. Heidi may be the better fit when the free standalone scribe is all the clinician needs.

---

## Patient Intake Form Template for Medical Practices
https://patientsquare.com/us/blog/patient-intake-form-template/
Published 2026-10-01 · Tags: patient-intake, template, front-desk, medical-records

Copy a patient intake form template built for safer record matching, useful history, consent routing, corrections, and a clean front-desk handoff.

A useful form collects enough identity and contact data to match the patient safely, the history needed for the visit, current medications and allergies, communication preferences, responsible-party details where relevant, and the notices or acknowledgements approved by the practice. Every field should have an owner and a reason.

A patient intake form has one job before it has any others: attach the right information to the right person. Pretty formatting cannot rescue a wrong-chart match. The template below starts with identity, then collects only what staff can explain and use.

Use it as a working draft, not a legal form bought off the shelf. Your privacy officer, counsel, billing team, and clinical lead should approve the fields and acknowledgements that fit your practice and state.

## Copyable patient intake form

```text
PATIENT INTAKE FORM

Practice: ______________________________
Visit date: ____________________________

1. PATIENT IDENTITY
Legal name: ____________________________
Name used in conversation: _____________
Date of birth: _________________________
Address: _______________________________
Phone: _________________________________
Email: _________________________________
Preferred contact channel: ______________
May the practice leave a message?  Yes / No

2. RESPONSIBLE PARTY OR REPRESENTATIVE, IF APPLICABLE
Name: __________________________________
Relationship or authority: ______________
Phone: __________________________________
Billing responsibility: Patient / Other

3. VISIT INFORMATION
Reason for today's visit: _______________
Referring clinician, if any: ____________
Preferred pharmacy: _____________________
Accessibility or communication need: ____

4. CURRENT CLINICAL INFORMATION
Current medications and doses: __________
Medication allergies and reactions: _____
Other allergies: ________________________
Current conditions under care: __________
Prior surgeries or hospital stays relevant to this visit: __________
Pregnancy status, only when relevant to the planned care: __________

5. COVERAGE AND PAYMENT, IF USED BY THIS PRACTICE
Plan or payer: __________________________
Member ID: ______________________________
Group number: ___________________________
Subscriber name and relationship: _______
Photo ID checked by: ____________________

6. PRACTICE-APPROVED NOTICES AND CHOICES
Privacy notice acknowledgement: _________
Financial policy acknowledgement: _______
Approved communication choices: _________
Separate treatment or procedure consent, if required: See named form

7. PATIENT REVIEW
I reviewed the information above and corrected any errors.
Patient or representative signature: ____
Date and time: __________________________

8. STAFF USE
Existing record searched before creation: Yes / No
Potential duplicate reviewed: Yes / No / Not found
Information needing clinical review: _____
Missing item and follow-up owner: ________
Record matched or created by: ___________
```

The blank lines are the easy part. The decisions around them determine whether the form helps or creates another inbox.

## Start with a two-identifier match

The [2025 ASTP/ONC SAFER Guide on patient identification](https://healthit.gov/resources/2025-safer-guide-patient-identification/) treats correct patient identification as a safety practice across registration and electronic records. That is why the template separates legal name, date of birth, contact details, and the name a patient uses in conversation.

Train staff to search before creating a new record. Test ordinary sources of ambiguity: a changed surname, twins, a shared household phone, transliteration differences, a child with a guardian, and two patients with the same name. A field can assist the match without becoming the only match key.

Do not print a Social Security number box because an old form had one. If the practice cannot name the workflow that requires a sensitive field, remove it. Less data means less clutter, fewer correction requests, and less information to protect.

## Separate collection from clinical review

The patient reports medications, allergies, conditions, and prior care. A clinician or authorized staff member still reviews what matters for the encounter. The form is a source, not a verified medication reconciliation or a diagnosis.

Route clinical answers deliberately. If a patient writes chest pain, a severe reaction, or another response covered by the practice's urgency policy, the form needs a named queue and owner. A red flag sitting in a general intake inbox is not a workflow.

Keep the history proportional to the visit. A podiatry practice and a psychiatry practice will not ask the same questions. Build one common identity block, then add specialty modules with a version owner. That keeps the front desk from handing every patient a ten-page anthology.

## Do not hide four agreements behind one checkbox

Intake, privacy notice acknowledgement, financial policy, communication choices, and informed consent are different events. Keep them distinct. The [HHS Privacy Rule summary](https://www.hhs.gov/hipaa/for-professionals/privacy/laws-regulations/index.html) explains the notice and privacy duties that apply to covered entities, while the treatment-consent rules for a particular procedure can come from state law and professional standards.

A good electronic form stores the exact notice version, the patient's choice, the date and time, and any later correction. It also records a refusal without blocking unrelated care unless an approved policy says the item is required.

Ask counsel to review the actual wording. This article does not supply a universal consent clause because one does not exist.

## Give corrections a visible path

Patients mistype dates, choose the wrong pharmacy, and forget a dose. Staff also make mistakes. The form should say how a patient can correct an answer before the visit, and the record system should preserve who changed an accepted value and when.

For paper, have the patient strike through an error once, enter the correction, and initial it under the practice's approved policy. For a portal, test the edit history. Silent overwrites make later questions hard to answer.

The staff block matters here. It turns missing information into assigned work instead of a sticky note. Write the owner and due point: "Maya, verify subscriber date before claim" is useful. "Check insurance" is not.

## Protect the completed form, not just the blank

A blank PDF is harmless. A completed intake form can contain protected health information. Map where it travels, who can open it, how long it remains in a form vendor, whether it enters email, and what happens after it reaches the chart.

HHS explains that a vendor handling PHI on behalf of a covered entity may be a business associate and that the arrangement needs the appropriate written safeguards. Review the [business-associate guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html) with privacy counsel. Then test access with a front-desk user, a clinician, a terminated account, and a support user.

Avoid sending completed forms through an unapproved channel because it feels convenient. The right channel is the one your practice has assessed, configured, and trained people to use.

## Run eight synthetic cases before launch

Use fake data. Never test a new intake workflow with a real patient's chart.

1. A new adult patient with complete information.
2. A returning patient with a new address and old phone number.
3. Two people with the same name and similar birth dates.
4. A minor whose guardian completes the form.
5. A patient who declines an optional question.
6. An interrupted mobile submission that resumes later.
7. A duplicate submission from the same patient.
8. A correction made after staff accepted the first response.

For each case, watch the staff queue and the destination record. Confirm that the practice can find the response, resolve uncertainty, preserve the correction, and prevent a duplicate chart. The test ends at the usable record, not at the green "submitted" banner.

## Keep the form beside the workflow

Store the field list, purpose, owner, required status, destination, and review date in one small register. Review it when the practice changes payer processes, adds a specialty, replaces software, or changes a notice.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square does not claim to replace every registration, consent, insurance, or portal workflow. If documentation after rooming is the bottleneck, [review the current Practice Copilot scope](../../products/practice-copilot/). Keep the intake acceptance test intact until the system responsible for intake has passed it.

---

## Best EHR for Allergy and Immunology Practices
https://patientsquare.com/us/blog/best-ehr-for-allergy-immunology/
Published 2026-09-30 · Tags: allergy-ehr, immunology-emr, specialty-practice, ehr-selection, clinical-documentation

A US allergy and immunology EHR guide for testing alerts, longitudinal treatment records, specialty workflows, note review, and contract fit.

An allergy-built EHR is the safer starting shortlist when the practice needs structured skin-test, immunotherapy, biologic, or allergy-alert workflows. General products can still fit small offices, but they should demonstrate the practice's exact specialty scenarios before price or interface decides the purchase.

An allergy practice should not choose an EHR from a generic primary-care demo. Put one allergy-alert correction, one longitudinal treatment case, and one specialty workflow in front of every vendor. The best system is the one that preserves the clinical trail and gives unfinished work an owner.

Google Keyword Planner reports 10 average monthly US searches for "best EHR for allergy" with MEDIUM paid competition. Search results include a handful of niche comparisons and vendor pages, but no incumbent or directory wall. The query is small and the decision is specific, which favors a practical test over a long ranking.

## Begin with the word "allergy"

The AAAAI's 2024 position statement argues that the EHR section commonly called "allergies" should be understood as a broader set of actionable alerts, because documented avoidance reasons are not limited to immune-mediated reactions. The statement proposes clearer terminology and more usable information for patient safety ([AAAAI position statement](https://www.aaaai.org/Aaaai/media/Media-Library-PDFs/Allergist%20Resources/Statements%20and%20Practice%20Parameters/Changing-Electronic-Health-Record-Allergy-to-Alerts-Dec-2024.pdf)).

That creates a sharp demo case. Enter a de-identified reaction history, correct an inaccurate label, record the reason for the change, and show how another clinician sees the updated alert. Ask what is structured, what remains free text, and what reaches other parts of the record.

This is not a product trivia question. If the system cannot preserve why an alert changed, a clean screen is beside the point.

## Five cases make a useful shortlist

Run these cases in the version and configuration the vendor is quoting:

| Case | Evidence to capture | What to reject |
|---|---|---|
| Alert correction | Prior value, new value, author, reason, date | Silent overwrite |
| Longitudinal follow-up | Relevant history beside current plan | Copy-forward without source dates |
| Specialty workflow | The practice's real test or therapy path | Generic template presented as specialty depth |
| Patient instruction | Reviewed content and delivery owner | Untracked print or message step |
| Administrative exception | Queue, assignee, due state, resolution | Shared inbox with no status |

The federal Health IT Playbook recommends selecting software against the practice's own needs, using comparison tools, common demonstration scenarios, and a testing plan ([ASTP/ONC Health IT Playbook](https://playbook.healthit.gov/playbook/full/)). A five-case script makes that advice concrete for allergy and immunology.

## Compare specialty depth with configurable breadth

Practice Fusion's allergy and immunology page describes customizable encounter notes, a specialty template library, flowsheets, online booking and intake, and electronic prescribing tools ([Practice Fusion allergy and immunology](https://www.practicefusion.com/ehr/allergy-immunology/)). These are vendor-stated capabilities. Ask to see the quoted product complete your cases rather than assuming a web-page bullet equals the local workflow.

athenahealth lists Allergy and Immunology among the specialties served by athenaOne and describes the wider platform as combining EHR, billing, practice management, and patient engagement ([athenahealth specialty practices](https://www.athenahealth.com/who-we-serve/specialty-practices)). That breadth may suit a group that wants one operational vendor. It may be unnecessary for a small office that already has working billing and communication systems.

A purpose-built allergy system should also enter the shortlist when skin testing, immunotherapy, or other specialty records are central to the practice. We are not naming an automatic winner because current configuration, support, and contract terms matter. The vendor has to show your case.

## Keep specialty tools separate from the note draft

The visit narrative matters, but it is only one layer. An ambient scribe can draft a SOAP note from the conversation. It does not automatically provide alert governance, specialty testing structures, therapy tracking, or the administrative controls around them.

Patient Square's AI Medical Scribe returns a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. The Copilot plan adds a bundled AI EHR, scheduling, and WhatsApp messaging at $119 per clinician per month on annual billing ([Patient Square pricing](https://patientsquare.com/us/pricing/)). Patient Square does not claim allergy-test grids, immunotherapy management, biologic tracking, allergy-specific alerts, or electronic prescribing.

That makes the buying boundary plain. Choose a specialty system when the specialty record is the requirement. Evaluate Patient Square when documentation time is the requirement and the practice has proved the general record is enough, or when it will work alongside an incumbent EHR.

The [AI scribe security checklist](../ai-scribe-security-checklist/) helps review the documentation tool separately. The [small-practice implementation guide](../ai-scribe-implementation-small-clinic/) covers a limited pilot without turning it into an EHR replacement project.

## Use a red-line sheet after each demo

Before the next vendor call, write three lines:

- What the system completed without leaving the product.
- What required duplicate entry, a partner product, or staff memory.
- What the presenter did not show.

Then attach contract status to every promised capability: included, optional, third-party, custom, or planned. If the sales team cannot label it, score it as unproved.

Our opinion is simple: an allergy EHR should make the alert history and longitudinal specialty record boring to retrieve. A scribe should make the note draft faster to review. Do not buy one while pretending it is the other. Book a demo to test Patient Square on the documentation case, and keep the specialty-system demo beside it.

---

## Best EHR for Ophthalmology: A Workflow Shortlist
https://patientsquare.com/us/blog/best-ehr-for-ophthalmology/
Published 2026-09-30 · Tags: ophthalmology-ehr, eye-care-software, ehr-selection, imaging-interoperability, specialty-practice

Compare ophthalmology EHRs through imaging exchange, registry reporting, subspecialty charting, and the honest boundary of a general AI EHR.

A practice that depends on ophthalmic device data, drawings, subspecialty charts, and IRIS reporting should start with ophthalmology-built systems such as ModMed EMA or Nextech. A general EHR belongs on the shortlist only when those specialty workflows are not hard requirements.

The best ophthalmology EHR is the one that can survive your imaging room. If OCT, fundus, visual-field, and anterior-segment data land in separate viewers, a pleasant note editor will not rescue the workflow. Start with device data and registry reporting, then judge charting speed.

Keyword Planner records 30 average monthly US searches for "best EHR for ophthalmology" with MEDIUM paid competition. The organic results are mostly niche roundups and vendor pages rather than an entrenched enterprise wall. A source-led workflow test can compete.

## The image-path test comes first

The American Academy of Ophthalmology calls ophthalmology one of medicine's most imaging-intensive specialties. It says many imaging systems still use proprietary formats that do not reliably communicate with other devices or EHRs, and it recommends asking manufacturers for DICOM conformance statements ([AAO imaging interoperability](https://www.aao.org/advocacy/issues/health-it/imaging-interoperability)).

Turn that policy into a demo script. Pick one device from your practice and ask the vendor to show:

| Step | What the team should see | Failure signal |
|---|---|---|
| Capture | Correct patient and study identity | Manual re-keying or ambiguous match |
| Ingest | Study appears in the intended chart | Separate inbox with no accountable owner |
| Review | Clinician can open the right image and measurements | Viewer switching loses visit context |
| Trend | Prior and current values can be compared | Screenshot or narrative-only workaround |
| Export | Data and image path are documented | "Supported" without a tested format |
| Downtime | Staff know the temporary and recovery steps | No reconciliation plan |

Do not accept a logo wall as proof. Use your device model, a de-identified test record, and the exact production path.

## ModMed and Nextech belong on the first shortlist

ModMed says its EMA ophthalmology EHR has subspecialty workflows, single-screen SOAP documentation, MIPS data capture, and cloud image access. It also states that its page may include forward-looking features, so purchasing decisions should use currently available functionality ([ModMed ophthalmology EHR](https://www.modmed.com/specialties/ophthalmology/ehr/)). That caveat is useful. Ask the presenter to label every demonstrated function as generally available, configured, extra-cost, or planned.

Nextech says IntelleChartPRO was built with input from ophthalmologists and pairs ophthalmology-specific clinical workflows with its practice-management platform. Its current page also describes single-page charting, quality-measure checks, and an ophthalmology-focused scribe ([Nextech ophthalmology](https://www.nextech.com/specialties/ophthalmology)). Again, make the vendor demonstrate your subspecialty and device path rather than reading the feature names back to you.

The honest verdict: practices that need device exchange, eye-specific drawings, cataract or retina workflows, and established quality-reporting paths should start with ophthalmology-built systems. ModMed and Nextech are reasonable first calls because their own product pages describe those workflows directly.

## Registry work needs its own acceptance case

The Academy's 2026 IRIS preparation kit tells integrated practices to review registry data at least quarterly and compare it with their EHR. It names mapping issues and data-entry errors as distinct causes of discrepancies ([AAO 2026 IRIS Prep Kit](https://assets.aao.org/2026-06/2026%20IRIS%20Registry%20Prep%20Kit-1.pdf)).

That means "IRIS integration" is not a checkbox. During selection, ask who maps the data, how the practice sees rejected or incomplete records, who corrects a mapping problem, and what evidence confirms resubmission. Then put those duties into the implementation plan.

Use a small registry drill:

1. Choose one measure or data element the practice actually reports.
2. Enter the data in the EHR through the normal visit workflow.
3. Show where it appears in the registry or test output.
4. Introduce one bad mapping and trace the correction owner.
5. Save the review and reconciliation procedure.

That drill is more informative than a claim that reporting is "built in."

## Where a general AI EHR stops

Patient Square's Copilot tier bundles an AI EHR with an ambient AI Medical Scribe, scheduling, and WhatsApp messaging. The scribe produces a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. US annual-billing pricing for Copilot is $119 per clinician per month ([Patient Square pricing](https://patientsquare.com/us/pricing/)).

Patient Square does not claim ophthalmic image management, device interfaces, drawing tools, or IRIS connectivity. If any of those are required, keep or buy the specialty EHR. This is not a footnote. It is the selection answer.

Patient Square may fit an eye practice that already has a workable device path and mainly wants a faster documentation workflow, or a small office that has proved it does not need the specialty functions above. The [ophthalmology scribe guide](../ai-scribe-for-ophthalmology/) covers spoken narrative and structured eye data in more detail. The India-specific [ophthalmology EMR guide](../ophthalmology-emr-software-india/) addresses a different regional market and should not be used as a US vendor shortlist.

## Run one clinic morning before deciding

Build a de-identified test set with a routine follow-up, a device-heavy visit, and one registry-relevant case. Let the technician, clinician, biller, and quality-reporting owner each complete their portion. Count only unresolved handoffs, duplicate entry, and steps that leave the intended system.

We think a specialty EHR wins when it makes the image and registry paths boring. Patient Square enters the comparison when note drafting is the expensive part and the specialty infrastructure is already solved. Book a demo if you want to test that narrower claim on an ophthalmology visit.

Choose the system that passes your imaging room, not the system with the smoothest home page.

---

## Best EMR for Rheumatology: A Workflow Test
https://patientsquare.com/us/blog/best-emr-for-rheumatology/
Published 2026-09-30 · Tags: rheumatology-emr, specialty-ehr, rise-registry, clinical-workflow, software-selection

A US rheumatology EMR test built around longitudinal disease data, infusion work, registry reporting, note review, and vendor proof.

A rheumatology-built EMR is usually the stronger fit when the practice needs structured disease scores, joint diagrams, infusion workflows, or direct registry support. NextGen is a clear specialty candidate. General systems belong on the shortlist only after they prove those workflows with practice data.

A rheumatology EMR has to remember what changed across months, not merely finish today's note. The strongest shortlist starts with longitudinal disease data, medication and infusion work, prior-authorization evidence, and registry reporting. A fast note editor is useful. It is not the whole record.

Keyword Planner reports 10 average monthly US searches for "best EMR for rheumatology." The result set is thin: one specialist comparison, vendor pages, and unrelated research. That is enough demand for a narrow buyer page, provided it answers the specialty workflow rather than inventing a generic top-ten list.

## Follow one patient across three visits

Ask each vendor to run the same de-identified sequence:

| Visit | Data the clinician needs | EMR proof |
|---|---|---|
| Baseline | Current symptoms, examination, prior therapy, selected disease measures | Structured entry plus narrative without duplicate work |
| Treatment change | Reason, review state, medication history, related administrative work | Visible decision trail and assigned follow-up |
| Follow-up | Interval change, repeated measures, response, unresolved items | Side-by-side trend and clear source dates |

The test is not whether a field exists. It is whether the clinician can see the story without opening six tabs or copying last month's note.

The federal Health IT Playbook recommends comparing EHRs against the organization's own needs and using consistent demonstration scenarios and vendor questions ([ASTP/ONC Health IT Playbook](https://playbook.healthit.gov/playbook/full/)). For rheumatology, your scenario should include the measurements, documents, and exception work the team actually uses.

## NextGen is the specialty-depth benchmark to test

NextGen's current rheumatology page describes rheumatology-specific enhancements, disease-score trending, homunculus diagrams, infusion and allergy workflows, specialty content, and AI-generated SOAP-note drafts. It also describes billing and patient-engagement functions on the wider platform ([NextGen rheumatology](https://www.nextgen.com/markets/specialties/rheumatology)). Those are vendor claims, not independent performance findings.

Still, the page gives buyers a useful test plan. Bring one tender-and-swollen-joint assessment, one repeated score, and one infusion-related administrative case. Ask the presenter to show the workflow in the version and configuration quoted to you. Then ask which functions are included, extra-cost, partner-provided, or planned.

Practice Fusion takes a more general approach. Its rheumatology page emphasizes customizable notes, flowsheets, referrals, lab and imaging orders, and its own e-prescribing workflow ([Practice Fusion rheumatology](https://www.practicefusion.com/ehr/rheumatology/)). A smaller practice may prefer that generalist footprint. It should still prove the longitudinal and administrative cases above.

When specialty depth matters, NextGen is the more direct first demo. When a compact general system matters more, a configurable general EHR can stay in the comparison. Neither wins before your cases run.

## Treat RISE as a working process

The American College of Rheumatology says RISE provides practice, provider, and patient-level views across more than 25 quality measures, including measures specific to several rheumatic diseases. Its page also describes MIPS and MVP reporting support ([ACR RISE for Performance](https://rheumatology.org/rise-for-practices)).

If the practice uses or plans to use RISE, add a registry acceptance test:

1. Identify one measure the practice intends to report.
2. Enter the required data through the ordinary visit workflow.
3. Show the mapped output and any exception queue.
4. Correct a missing or wrong element.
5. Name the practice and vendor owners for review, submission, and support.

Do not infer current RISE connectivity from an old brochure or generic interoperability claim. Verify it with ACR and the vendor for the quoted product, version, and practice arrangement.

## Separate the note from the disease record

An ambient scribe hears the conversation and drafts a note. A rheumatology EMR may also need to hold structured scores, show their change, organize medication work, support infusion operations, and send registry data. Those are different jobs.

Patient Square's AI Medical Scribe produces a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. The Copilot plan adds a bundled AI EHR at a published annual-billing price of $119 per clinician per month ([Patient Square pricing](https://patientsquare.com/us/pricing/)). Patient Square does not claim rheumatology-specific score tracking, homunculus diagrams, infusion management, RISE integration, or electronic prescribing.

That boundary decides the fit. A practice that needs the specialty functions should choose a rheumatology-built system or keep its incumbent, then evaluate a documentation tool alongside it. A small practice whose main burden is narrative documentation can test Patient Square, but it should not pretend the general EHR replaces unproved specialty workflows.

The [rheumatology scribe guide](../ai-scribe-for-rheumatology/) focuses on encounter narration. The [EHR contract checklist](../ehr-rfp-checklist/) covers commercial and exit terms that belong beside this clinical test.

## Score the demo while the room is still quiet

Give two points when the product completes a required step in the quoted configuration, one when it needs a documented workaround, and zero when the presenter cannot show it. Score these five rows: longitudinal view, disease measures, medication or infusion work, administrative exceptions, and registry reporting.

Ten points is not a scientific rating. It is a memory aid that stops the last demo from winning because it was last. Keep screenshots or written evidence for each score, subject to your privacy and security rules.

We think the honest shortlist starts with NextGen for specialty depth, then adds a general EHR only when the practice can name what it is willing to give up. Book a demo if you want to test Patient Square on the documentation half. Bring the same three-visit case. The boundary should be obvious by the end.

---

## Best Practice Management Software for Small Practices
https://patientsquare.com/us/blog/best-practice-management-software-small-practice/
Published 2026-09-29 · Tags: practice-management, small-practice, ehr-selection, software-buyers-guide, healthcare-operations

A practical US shortlist for small practices comparing workflow fit, contract risk, implementation load, and the boundary between PMS and EHR tools.

The best fit is the least complicated system that covers the practice's real scheduling, billing, communication, reporting, and record needs. A two-provider office should test its own front-desk and visit scenarios instead of buying the product with the longest feature list.

A two-provider practice can buy an impressive system and still make the front desk run three browser tabs. The right practice management software is the smallest workable system: it covers the office's real administrative jobs, has a clear boundary with the clinical record, and does not turn every exception into a support ticket.

Google Keyword Planner records 90 average monthly US searches for "best practice management software." Paid competition is MEDIUM. That number shows a live buyer query, not an organic ranking score. The current results mix directories, broad roundups, and thin product lists, so a workflow-first comparison has room to be more useful.

> Takeaways:
>
> - Start with four office scenarios, not a feature spreadsheet.
> - Separate practice-management work from EHR work before comparing bundles.
> - Price the contract, implementation, support, export, and exit terms together.
> - A small practice needs an owner for the rollout even when the software is cloud hosted.

## Start with the jobs that break at 4:45 pm

Write down what happens when the schedule slips, a patient arrives without completed intake, an insurance response needs staff action, or a clinician finishes the day with unsigned notes. Those moments expose the actual system boundary.

Use this one-page map before opening a vendor site:

| Office job | System that should own it | Proof to request in a demo |
|---|---|---|
| Appointment and queue | PMS or scheduling module | Book, move, cancel, and fill a late opening |
| Clinical note and problem list | EHR | Complete a visit and find the signed record |
| Claim or payment exception | PMS, billing tool, or service | Show the work queue, owner, and resolution history |
| Patient message | Approved communication tool | Route one message to the right staff role |
| Operational report | PMS or analytics layer | Produce a report from the same data staff enter daily |
| Record export | EHR and contract process | Export a sample chart plus the agreed data set |

The federal Health IT Playbook says EHR selection should begin with a practice's needs, resources, readiness, team, and realistic expectations, then use common scenarios to compare vendors ([ASTP/ONC Health IT Playbook](https://playbook.healthit.gov/playbook/full/)). That advice applies just as well to a PMS purchase. The screen that looks tidy in a sales demo still has to survive your Monday morning.

## PMS, EHR, and bundled platform are different buys

Practice management software usually runs the administrative side of the office. The EHR owns the clinical record. A suite can sell both, but a shared logo does not prove the modules share one task model, one patient identity, or one support path.

Ask the vendor to draw its boundary. Who owns registration? Where does a demographic correction begin? Which system holds signed notes? Where does billing staff see missing documentation? What happens if the clinical and administrative modules disagree?

We think small practices overbuy when they compare module counts instead of handoffs. One solid scheduling path and one visible exception queue beat six loosely joined dashboards.

## A shortlist by operating model

There is no honest universal ranking. The useful shortlist starts with the kind of office you run.

| Small-practice situation | Best starting category | Main risk to test |
|---|---|---|
| New solo office with simple operations | Lightweight PMS plus record system | Missing billing or export depth |
| Two to five clinicians replacing several tools | Bundled EHR and PMS platform | Weak module boundaries hidden by one contract |
| Specialty office with unusual charting | Specialty EHR plus compatible PMS | Duplicate data and brittle handoffs |
| Practice that outsources billing | EHR plus focused scheduling and communication | Unclear ownership between vendor and biller |
| Office where documentation is the bottleneck | Record system with an ambient documentation path | Draft review, signing, and record placement |

ASTP/ONC maintains a Certified Health IT Product List and selection resources for organizations comparing health IT. Its guidance also points buyers to contingency planning, organizational responsibility, and high-priority safety practices ([Selecting or Upgrading Health IT](https://healthit.gov/clinical-quality-and-safety/safer-guides/selecting-or-upgrading-health-it/)). Certification or a long feature list still does not answer whether the daily workflow fits.

## Run the same four demo cases everywhere

Give each vendor a short script and do not let the presenter substitute a prepared path.

1. Register a new patient, book the next open appointment, and correct a misspelled surname.
2. Start and complete a visit, including the note's review and signature state.
3. Create an administrative exception, assign it, and show how a manager knows it was resolved.
4. Export the record and explain what the practice receives at contract end.

Score each case from zero to two: zero means the workflow was not shown, one means it required a workaround, and two means staff completed it in the product. Add a written note for every handoff to another module, vendor, or service.

That produces a 16-point worksheet across four cases and two questions per case: did it work, and who owned the exception? It is deliberately small. A small practice should be able to explain its software decision on one page.

## Price the exit before the entry

The monthly subscription is only one contract line. Ask for implementation, training, data conversion, support, renewal, termination, export format, export assistance, data deletion, and transition support in writing.

ASTP/ONC's contract guide treats planning and negotiation as ways to reduce business and patient-safety risk. It provides example issues for acquiring, upgrading, or replacing health IT ([EHR Contracts Untangled](https://www.healthit.gov/sites/default/files/playbook/pdf/ehr-contract-guide.pdf)). Have counsel review the actual agreement. A blog checklist is not contract advice.

Also test downtime. The SAFER resources call for contingency planning when all or part of the EHR is unavailable. Ask who declares downtime, what staff use, how work is reconciled, and how the practice proves the system recovered.

## Where Patient Square fits

Patient Square's US plans combine an ambient AI Medical Scribe with scheduling, and the Copilot tier adds a bundled AI EHR and WhatsApp messaging. The scribe returns a structured SOAP-note draft, ICD-10 suggestions, and a prescription draft for clinician review. It does not transmit prescriptions, make diagnoses, or remove the signing step.

Published annual-billing prices are $79 per clinician per month for Assist, $119 for Copilot, and $199 for Autopilot. The current pricing page says visits and notes are unlimited and there are no setup fees ([Patient Square pricing](https://patientsquare.com/us/pricing/)). The security page states HIPAA compliance, BAAs for customers, TLS 1.2+ in transit, AES-256 at rest, and a SOC 2 Type II audit in progress, not completed certification ([Patient Square security](https://patientsquare.com/us/security/)).

Patient Square is not the automatic winner. Pick a specialty platform when its clinical workflows are non-negotiable. Pick a billing-led suite when the billing operation is the primary requirement. Consider Practice Copilot when note creation, scheduling, and a bundled record system are the jobs you want one subscription to cover.

Use the four-case script on us too. Book a demo, bring one real office day, and make the product follow it from booking through signed note. The [medical practice management guide](../medical-practice-management-software-guide/) covers the wider category, while the [small-practice EHR roundup](../best-emr-for-small-practice/) stays focused on the clinical record.

The best result is not a longer feature list. It is a Tuesday your staff can run without inventing a second system in a spreadsheet.

---

## EHR Downtime Procedures for a Small Practice
https://patientsquare.com/us/blog/ehr-downtime-procedures-small-practice/
Published 2026-09-29 · Tags: ehr, downtime, contingency-planning, small-practice, patient-safety

A small-practice EHR downtime plan for the first hour, paper workflows, patient identity, medication and result handling, recovery, and reconciliation.

Name who declares downtime, how staff receive updates, where current approved forms and contacts live, how identity and clinical work continue, which services pause, how records are secured, who decides recovery, and how every paper or alternate record is reconciled into the EHR afterward.

At 9:07 on a Tuesday, the schedule is full and every EHR screen is blank. A useful downtime procedure tells a small practice what happens in the next ten minutes, which care can continue, where approved forms live, and who reconciles every record after recovery. The vendor's status page is only one line in that plan.

> Takeaways:
> - Name an operational lead and a clinical decision owner before the outage.
> - Keep approved contacts, forms, and the downtime procedure reachable outside the failed system.
> - Patient identity, medication work, orders, results, and documentation need separate fallback decisions.
> - Recovery is not complete until downtime work is reconciled and checked.

## The first ten minutes

Do not begin with a root-cause debate. Confirm the boundary. Can nobody sign in, or only one user? Is the EHR slow, read-only, or absent? Do phones, internet, printers, e-prescribing, lab, imaging, and the patient portal share the failure?

The downtime lead records the start time, affected services, person who confirmed the problem, vendor case number, staff update channel, and next update time. The clinical owner decides whether scheduled services continue normally, continue under an approved reduced workflow, pause, or redirect.

The 2025 [SAFER Contingency Planning Guide](https://healthit.gov/resources/2025-safer-guide-contingency-planning/) addresses planned and unplanned EHR unavailability. ASTP/ONC's [Health IT Playbook](https://playbook.healthit.gov/playbook/quality-and-patient-safety/) points practices toward a paper-based route for documentation, medications, tests, and procedures when the EHR is unavailable. Those sources are a starting point. The clinic still needs local roles and approved procedures.

## The one-page command card

Keep this card with the current downtime packet, not inside the EHR.

| Time | Owner | Action | Evidence to retain |
|---|---|---|---|
| 0 to 10 minutes | Downtime lead | Confirm scope, open vendor case, announce status and next update | Event start, boundary, contacts, case number |
| 0 to 15 minutes | Clinical owner | Set continue, modify, pause, or redirect decisions by service | Decision, reason, affected appointments |
| 10 to 30 minutes | Front desk lead | Move to approved schedule and identity procedure | Patient list source, labels, exceptions |
| 10 to 30 minutes | Clinical lead | Issue current forms and medication, order, result, and note instructions | Form versions, staff acknowledgment |
| Every stated interval | Downtime lead | Update staff even when status is unchanged | Message time and content |
| On recovery signal | Technical and clinical owners | Test before declaring normal operation | Test patient, access, order, result, note, audit evidence |
| After return | Reconciliation owner | Account for every downtime record and open task | Reconciliation ledger and exception list |

The card is not the whole policy. It is the page people can use while phones ring.

## Identity comes before blank paper

A stack of forms is dangerous if staff cannot attach the right person to each page. Define how registration checks identity when normal lookup is unavailable, how temporary identifiers work, which labels are permitted, and who resolves a duplicate after recovery. Put identifiers on every approved page before clinical information is added.

Keep an exception list. Misspelled names, newborns, unknown patients, similar names, and people seen at another location need a deliberate route. Do not let each desk invent one.

## Five workflows need separate rules

### Clinical documentation

Use current, approved forms. Record author, date, time, patient identity, assessment, plan, orders, and handoff information required by the practice. Secure completed pages and name the person who collects them. "Scan later" is not a custody plan.

### Medication work

The clinical owner defines what can continue when medication history, interaction checks, or electronic transmission are unavailable. State the alternate order route, read-back rule where applicable, pharmacy communication path, and recovery reconciliation. This is not a place for a blog to invent clinical instructions.

### Orders and results

Track each order outside the unavailable queue. Record destination, time, priority, requester, expected result route, person responsible for follow-up, and whether the result arrived. After recovery, the owner matches every request to a result or an open exception.

### Patient communication

Decide who tells patients about delays, rescheduling, reduced services, portal unavailability, or changed follow-up. Use an approved channel. Do not place PHI in an ordinary messaging tool because the normal system is down.

### Billing and referrals

Capture enough information to restart work without rebuilding the visit from memory. Keep authorization, referral, charge, and document tasks on the same event ledger. Some items can wait. Mark them rather than letting them vanish.

## Recovery is a controlled cutover

An EHR login screen returning does not end downtime. Test a small route first: patient lookup, role access, documentation, an order or equivalent workflow, a result route, and the audit record the practice expects. Confirm what period or function remains incomplete.

Then reconcile. For every patient seen during downtime, list the paper or alternate records created, orders placed, results received or pending, medication actions, messages, referrals, billing items, and follow-up tasks. Name who enters or scans each item, who checks it, and how duplicate or conflicting entries are resolved.

The [HHS OIG contingency-plan report](https://oig.hhs.gov/reports/all/2016/hospitals-largely-reported-addressing-requirements-for-ehr-contingency-plans/) describes the HIPAA contingency-plan elements it reviewed: data backup, disaster recovery, emergency-mode operations, and testing and revision procedures. The regulation itself appears at [45 CFR 164.308(a)(7)](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C/section-164.308). A practice should map its local plan with qualified privacy, security, clinical, and legal owners rather than copying a hospital policy.

## Run a 25-minute tabletop

Pick a Thursday morning with twelve booked patients. Assume the EHR is unavailable but electricity, phones, and the local network still work. Give staff five minutes to find the current plan, contact list, schedule route, and approved forms.

Walk one ordinary visit and one exception. The exception might be two patients with similar names, an outside result expected today, or a prescription request that cannot follow its normal route. Stop when somebody says, "We would probably." That sentence is the gap to assign.

Finish with recovery. Hand the team three paper records, one pending result, and one duplicate-identity question. Ask them to reconcile the set. Record missing documents, stale contacts, unclear authority, inaccessible files, and work without an owner. Set dates.

We think the recovery exercise is the part most small practices skip. It is also where a safe-looking paper process can create a second mess inside the restored EHR.

## Patient Square does not replace the plan

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

A practice can use the bundled Patient Square record system or keep its current EHR and use Practice Copilot alongside it. Either path needs local downtime ownership. Patient Square does not claim that an AI draft replaces approved downtime documentation, medication, order, result, identity, or recovery procedures.

The [EHR implementation guide](../ehr-implementation-guide/) covers planned rollout, while the [EHR data migration guide](../ehr-data-migration-guide/) covers cutover evidence. [review the current Practice Copilot scope](../../products/practice-copilot/), then put the accepted result in the practice's own procedure.

---

## Cashless Pre-Authorisation: A Hospital Desk Playbook
https://patientsquare.com/in/blog/pre-authorization-cashless-claims-india/
Published 2026-09-29 · Tags: cashless-claims, pre-authorization, health-insurance, hospital-billing, india

Run private health-insurance cashless pre-authorisation from admission to discharge approval with a complete packet, query log, amendment trail, and clear ownership.

Cashless pre-authorisation works best when the hospital desk owns a complete packet, payer-specific checklist, query log, amendments, and discharge handoff. Insurer turnaround rules do not replace the hospital's responsibility to submit accurate information and track every outstanding decision.

At 5:10 pm, the surgeon says the patient can leave. The hospital cannot close the cashless bill yet. A new consumable appeared, the operative note is not in the packet, and the insurer has asked why the final amount exceeds the pre-authorised estimate.

The patient experiences one delay. The desk sees four unfinished handoffs.

This playbook is for private health-insurance cashless work at an Indian network hospital. It does not describe PM-JAY package claims, which run on a separate scheme process.

> Takeaways:
> - The one-hour pre-authorisation and three-hour final-authorisation clocks belong to the insurer after receipt of the relevant request.
> - A complete packet and a visible query log matter more than repeated phone calls.
> - Clinical, estimate, policy, and final-bill changes need one amendment trail.
> - A note-drafting tool can sit upstream; it does not file or decide the claim.

## Run the case as two linked packets

The first packet asks whether the insurer will authorise cashless treatment under the policy. The second asks for final authorisation against what actually happened and what the hospital billed.

Treat them as linked versions of one case.

| Stage | Hospital desk needs | Clinical owner contributes | Insurer or TPA returns |
|---|---|---|---|
| Pre-authorisation | Member and policy details, network status, form, estimate, supporting records | Diagnosis, indication, treatment plan, relevant history and investigations | Approval, partial approval, query, or denial under the policy |
| Amendment | Prior reference, changed facts, revised estimate, reason for change | Updated diagnosis, procedure, plan, or complication record where applicable | Revised decision or further query |
| Final authorisation | Final bill, discharge request, completed records, prior decisions and amendments | Procedure or treatment record and discharge summary | Final authorised amount, deductions, query, or denial |

The exact documents vary by payer, policy, and case. HDFC ERGO's published cashless process, for example, asks for a completed pre-authorisation form, prescription with diagnosis and planned treatment, supporting investigations, expected-cost estimate, and relevant history. It names extra records for certain conditions and accidental cases ([HDFC ERGO cashless process](https://www.hdfcergo.com/claim/register-health-insurance-claim/cashless-claims)). Use the current checklist for the payer handling the case.

## The regulatory clock starts at receipt

IRDAI's health-insurance FAQ says the insurer should decide a cashless authorisation request immediately and no later than one hour after receiving it. The same FAQ says final authorisation should be granted within three hours after the insurer receives the hospital's discharge authorisation request ([IRDAI health department FAQ](https://irdai.gov.in/health-dept)). The underlying Master Circular on Health Insurance Business is dated 29 May 2024.

Those limits are easy to quote badly. They are insurer turnaround requirements from receipt. They do not mean:

- the hospital may wait an hour before sending a complete packet;
- every query is automatically resolved inside the original clock;
- a planned admission needs no advance local preparation;
- every bill item is covered; or
- every patient physically leaves within three hours.

Capture two timestamps: when the desk sent the complete request and when the payer acknowledged receipt. If a query arrives, log the exact question, owner, response, attachments, and new receipt evidence. "Followed up" is not a useful case state.

## Build a pre-authorisation packet that can be read cold

The reviewer was not present when the patient arrived. The packet has to explain the case without a ward-side conversation.

Use a cover sheet with:

1. patient and member identity, checked against the payer record;
2. policy or card details and network confirmation;
3. planned or emergency admission status;
4. treating clinician and hospital contact;
5. diagnosis and clinical indication in the treating record;
6. proposed treatment or procedure;
7. investigations that support the request;
8. expected dates and cost estimate;
9. attached-document list; and
10. one hospital case owner.

Do not add clinical facts at the desk because a field is blank. Return the gap to the treating team. A fast invented answer is worse than a visible query.

The desk should also distinguish three amounts: the hospital estimate, the insurer's approved amount, and the patient's possible non-payable or policy share. They are not interchangeable, and a pre-authorised amount is not the final settlement.

## Make every query a work item

Payer queries tend to arrive as short text against a much larger case. Convert each one into a row.

| Received | Query | Owner | Due | Response evidence | State |
|---|---|---|---|---|---|
| 11:04 | Investigation supporting stated diagnosis not attached | Ward coordinator | 11:20 | Named report, date, page, upload receipt | Sent 11:16 |
| 14:32 | Revised procedure differs from initial request | Treating team | 14:50 | Clinical update, revised estimate, amendment reference | Awaiting receipt |

Use states staff can act on: new, assigned, waiting on clinical team, waiting on patient, sent, receipt confirmed, payer review, decided. Avoid "in process." It conceals ownership.

Keep the original request and every amendment. Do not overwrite the first estimate or diagnosis in a shared spreadsheet. The sequence explains why the case changed.

## Amend before the final bill becomes a surprise

Treatment can change after pre-authorisation. A planned procedure may expand, an implant may change, complications may add care, or the length of stay may move. The desk needs a trigger list for when to seek an amendment under the payer's process.

For every change, record:

- what changed;
- when the hospital knew;
- who made the clinical decision;
- the supporting record;
- the estimate effect;
- when the payer received the amendment; and
- the returned decision or query.

The hospital should not expect the discharge desk to reconcile an unexplained difference between the pre-authorised plan and the final bill in a few minutes. Make the case current while care is happening.

## Prepare discharge before the discharge order

The three-hour insurer clock does not excuse a packet assembled at the end. Start the final checklist when discharge becomes likely.

Reconcile the pre-authorisation, amendments, treatment record, final diagnosis, procedure or intervention, investigation results, discharge summary, and itemised bill. Check that dates, clinician names, and amounts agree. If they do not, route the discrepancy to the owner. Do not quietly edit a clinical document to fit a billing line.

Then send the final authorisation request through the applicable payer or TPA channel and preserve receipt evidence. Keep the patient informed using timestamps the desk actually has. A promise based on "usually" is not a status update.

## Protect the packet as health data

The packet contains identity, policy, financial, and health information. The Digital Personal Data Protection Act, 2023 requires consent to be free, specific, informed, unconditional, and unambiguous for processing based on consent, and it places duties around purpose and handling on data fiduciaries ([DPDP Act, 2023](https://www.indiacode.nic.in/bitstream/123456789/22037/1/a2023-22.pdf)). Other lawful uses and insurance obligations may also apply to a particular case; the hospital should follow its approved legal and privacy process.

Operationally, keep the case inside approved channels. Restrict access by role. Do not send full packets into informal groups because the insurer asked for one missing page. Record what was shared, with whom, for which case, and under which approved process. Apply the hospital's retention and deletion policy to local working copies.

## Keep PM-JAY and private cashless separate

The desk may handle private insurance, TPAs, PM-JAY, employer schemes, and state schemes during one shift. Shared staff does not mean shared rules.

This article covers a private health-insurance cashless request governed by the applicable policy, insurer or TPA process, and IRDAI framework. PM-JAY uses its own package, pre-authorisation, transaction, and audit machinery. Read the separate [PM-JAY claim documentation guide](../pmjay-claim-documentation-hospitals-india/) for that path.

The same separation applies to NHCX. The [NHCX explainer](../nhcx-claims-explained-clinics/) covers the exchange. Do not label an ordinary portal upload as NHCX connectivity, and do not infer that a hospital product sends claims merely because it contains a claims module.

## Patient Square sits upstream of the desk

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For this workflow, the boundary matters more than the module list. Patient Square does not claim insurer or TPA connectivity, cashless pre-authorisation submission, NHCX connectivity, automatic claim filing, or live ABDM integration. ABDM integration is on the roadmap. ICD-10 output is a suggestion for authorized review, not a coding decision. Prescription content is a draft, not transmission to a pharmacy.

A reviewed clinical note may provide cleaner upstream source material for the hospital team that assembles the packet. It does not guarantee approval or replace the payer checklist, policy, treating clinician, coder, billing team, or insurer decision.

Bring one de-identified query trail to a process review. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, then keep submission and decision authority exactly where the hospital and payer rules put them.

---

## Blood Bank Management Software in India: A Buyer's Guide
https://patientsquare.com/in/blog/blood-bank-management-software-india/
Published 2026-09-28 · Tags: blood-bank-software, blood-centre, e-raktkosh, hospital, india

What an Indian blood centre must record by law, what daily e-RaktKosh reporting means for your software choice, and when standalone beats an HMS module.

It has to produce the registers the Drugs and Cosmetics Rules require and feed e-RaktKosh. That means a donor record with deferrals, a master record per bag carrying all five mandatory test results, an issue register with cross-match details, a kit and reagent register, adverse-reaction records, and cold-chain logs. Everything else is convenience.

Blood bank software in India gets judged on one thing: whether it produces the registers a drug inspector asks for and the data e-RaktKosh expects, every day, without anyone remembering to do it. Donor record, master record per bag, issue register, cross-match, cold chain. The dashboards are optional. The registers are the licence.

> **Key takeaways**
>
> - Registers have to survive five years. Rule 122-P makes them a licence condition, and the Form 28-C licence itself runs five years.
> - Five tests are mandatory on every unit before use: HIV I and II antibodies, HBsAg, HCV antibody, VDRL and malarial parasite. Results go on the label.
> - The CDSCO advisory of 3 June 2022 says every licensed blood centre is required to register on e-RaktKosh, update stock daily, and send donor data and monthly reports. It is an advisory routed to State licensing authorities for follow-up, not a rule carrying its own penalty.
> - A hospital storage centre is not a licensed blood centre. Schedule K entry 5B exempts it under 2,000 units a year, from a licensed source.
> - Patient Square does not build blood bank software. Nothing here is a pitch for one.

_Sources: CDSCO regulatory requirements for blood and its components; CDSCO e-RaktKosh advisory, 3 June 2022._

## The rulebook writes your feature list, not the vendor

Most demos open with a donor app and a stock dashboard. Neither is what an inspector wants.

The operating rules sit in the Drugs and Cosmetics Rules, 1945, Rules 122-F through 122-P, with the detail in Schedule F Part XII-B. You apply in Form 27-C under Rule 122-F. If the State Drug Controller is satisfied after inspection, you get a licence in Form 28-C under Rule 122-G to collect, store, process and distribute whole human blood and its components, valid five years under Rule 122-H.

Rule 122-P is the part that should shape a shortlist. It makes the Schedule F registers a condition of holding the licence, requires them kept five years from the date of manufacture, and lets an inspector walk in with or without prior notice to read any of them. One condition belongs in the software as a hard block: no blood from a professional or paid donor. Donor category is a compliance field.

On vocabulary: government documents now say blood centre, the older Rules text still says blood bank, and vendors mostly say blood bank. Same licensed facility.

## What has to exist in the record, and who comes looking

Every row below is a record Schedule F Part XII-B names, with what it must carry, who asks for it, and whether it also surfaces nationally.

| Record | What the rules require it to carry | Who asks to see it | Surfaces on e-RaktKosh? |
|---|---|---|---|
| **Blood donor record** | Serial number, date of bleeding, donor identity and signature, age, weight, haemoglobin, group, blood pressure, medical examination, bag number, voluntary or replacement, **deferral records**, Medical Officer's signature | Drug inspector, with or without notice | Yes, donor data is named in the advisory |
| **Master record for blood and components** | Bag serial number, collection and expiry dates, volume, ABO and Rh group, all five test results, irregular antibodies, donor particulars, issue number, components prepared or discarded | Drug inspector | Yes, as the stock position updated daily |
| **Issue register** | Serial number, date and time of issue, bag serial, group, volume, recipient identity and group, unit, cross-matching report, indication for transfusion | Drug inspector; transfusion committee if accredited | Feeds the monthly report |
| **Cross-match report to the patient** | Must be issued to the patient together with the blood unit | The receiving ward, and the inspector if a unit is queried | No, it travels with the unit |
| **Kit and reagent register** | Name of kit or reagent, batch number, date of expiry, date of use | Drug inspector; NABH assessor | No, kept locally |
| **Transfusion adverse-reaction records** | Reactions recorded as they occur | Drug inspector; NABH assessor | No, kept locally |
| **Cold-chain evidence** | Whole blood at 2 to 6 °C, on a fridge with digital dial thermometer, recording thermograph, alarm and continuous power; component freezers at minus 30 to minus 40 °C and minus 75 to minus 80 °C | Drug inspector, by walking to the machine | No, kept locally |

_All of it retained five years. The 2022 advisory names daily stock, donor data and monthly reports without mapping register by register, so the last column is the practical split, not a quotable clause._

Look at the donor row again. Deferral records are named in the rule, and they are where paper fails. Schedule F sets deferment periods across a long list: twelve months after surgery, six months after a tattoo or a prior transfusion, three months after treated malaria in an endemic area and three years in a non-endemic one. A donor deferred in March who walks back in June is a check the system should raise before the phlebotomist reaches for a bag, with the medical officer still making the call. Free-text remarks are not deferral logic.

## e-RaktKosh changed the question in 2022

e-RaktKosh is the Ministry of Health and Family Welfare's centralised blood centre system. The public side is familiar: search availability, find a centre, register as a donor, raise a thalassemia request.

The part that matters to a buyer sits behind the login. On 3 June 2022 the office of the Drugs Controller General of India issued an advisory, File No. Blood Bank/Misc/e-RaktKosh Advisory/2022-D, stating that all licensed blood centres are required to register on the portal to enter their blood stock availability and "update the same on a daily basis", along with donor data and monthly reports. Copies went to every State and UT licensing authority and every CDSCO zonal office for follow-up.

Daily is the operative word. A district hospital centre that closes at 8pm and keys yesterday's issues into the portal next morning is doing double entry forever, and it drifts from the register on exactly the days that matter. So the question to put to a vendor is narrow: does the system make my e-RaktKosh position a by-product of accessioning, testing and issuing, or does it print a report someone retypes?

We think that one question separates good blood centre software from adequate more reliably than any feature grid. Everything else can be worked around. Double entry can't.

## What an inspector actually asks for

An inspection is a trace, and you can rehearse it. Nobody asks to see your dashboard. Pick a bag serial number. Show the donor record behind it, with the medical examination and the deferral check. Show the master record with all five test results. Show the label carrying them, then the issue register entry with the cross-match and stated indication, then the reagent register for that day's kit lots, then the temperature record for the fridge that held it.

If any link lives in a spreadsheet or a drawer, the trace stalls and someone loses an afternoon reconstructing it. Run it during the trial, not after go-live. The [NABH documentation requirements guide](../nabh-documentation-requirements/) makes the same point about hospital records generally: the system that survives an assessment is the one where evidence is a by-product of work.

## Standalone system, HMS module, or e-RaktKosh alone

Running on e-RaktKosh alone is what plenty of small licensed centres actually do, day to day. Cheapest path, and reporting stays current by definition. Limits appear when you want your own component workflow, quality records, or a link to hospital billing.

The blood bank module in your HMS is the right call when blood is one service among many and volume is modest. One login, and the issue lands on the bill without re-keying. The usual failure is depth: modules handle ordering and issuing, then treat deferral, component preparation, reagent lots and adverse reactions as text fields. Same gap we described between a real LIMS and a thin lab tab in the [lab management software guide](../lab-management-software-india-lims/), and the one in bundled stock modules in [hospital inventory management](../hospital-inventory-management-india/).

A specialist blood centre system is built around the bag: accessioning, test results tied to the unit, component splitting with parent and child lineage, quarantine of untested units, cross-match and issue, cold-chain logging, e-RaktKosh submission. If you bleed donors and prepare components, this is normally the better buy, and lineage is the reason more than features. Once one bag becomes packed cells, plasma and platelets, each child unit inherits the donor and the test results and expires on its own schedule. Systems built to issue stock rarely model that. The [HMS modules explainer](../hospital-management-system-explained/) maps the rest of the stack around it.

## The storage centre case that changes the answer

Plenty of hospitals shopping for blood bank software actually run a blood storage centre. The rules treat those differently. Notification GSR 909(E) of 20 December 2001 inserted entry 5B into Schedule K, exempting storage centres run by a First Referral Unit, CHC, PHC or any hospital from holding an operating licence. The conditions: approval by the State or UT licensing authority after inspection, captive consumption under 2,000 units a year, blood procured only from a licensed government, Indian Red Cross Society or regional transfusion centre, and a two-year approval renewed three months before expiry.

If that's you, half this article doesn't apply. No bleeding, so no donor register and no deferral logic. You need receipt from your source centre, temperature evidence, cross-match, issue and expiry control. An HMS module usually covers it, and a specialist system is overbought. Working out which side of entry 5B you sit on is the cheapest decision on this page.

## NABH, if accreditation is on the table

NABH runs a separate accreditation programme for blood banks and blood centres, distinct from its hospital programme, covering donor screening, collection, component preparation, testing, storage and distribution. It accredits the facility, not your vendor. No software is "NABH certified" for your centre. A vendor implying otherwise is selling you a category error. What good software does is make evidence producible: quality indicators, reagent lot traceability, adverse-reaction records, turnaround data.

Alongside NABH sits the National Blood Transfusion Council under DGHS, whose stated role is to formulate policy, strategy, standards and technical guidelines. It has published National Standards for Blood Centres and Blood Transfusion Services (2nd edition, July 2022) and a Transfusion Medicine Technical Manual (3rd edition, August 2023). Read those before the brochures.

## What it costs, honestly

Blood centre software pricing in India is not publicly listed. Vendors gate it behind a call, and the number moves with annual collection, component preparation, apheresis and site count. We are not going to invent a range. What to insist on in the quote: the figure in rupees, ex-GST, with 18% GST stated separately; implementation and migration as line items; annual support and upgrade costs named in figures; and e-RaktKosh submission confirmed as included, not a chargeable add-on. Get that last one in writing.

## The honest verdict, including where we don't belong

Buy the specialist system if you hold a Form 28-C licence, bleed donors, prepare components and report daily. Component lineage, deferral logic and daily reporting are the three things a bundled module gets shallow on, and each sits on the licence side of the line. Keep the HMS module if you run a Schedule K storage centre, or if volume is small and issue against cross-match is most of the work. Run on e-RaktKosh alone if you're a small licensed centre with no appetite for a second vendor.

Now our own position. Patient Square does not build blood bank software. No donor register, no component preparation, no cross-match, no e-RaktKosh submission. If an AI vendor tells you their documentation product covers transfusion services, ask to see a master record and an issue register inside it. Ours has neither, and a documentation tool rarely does.

What we build sits one step away, in the consult room. AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft — ready to review and sign about two minutes after the visit. Where that touches this workflow is narrow: the transfusion consult itself. A haematologist explaining why a thalassaemia child needs a shorter interval, a physician writing up the consent discussion and the stated reason for transfusion. That's documentation, and documentation is our lane. Our [security page](../../security/) covers how the data is handled to DPDP Act 2023 standards, and pricing starts at ₹1,599 per clinician per month on annual billing, ex-GST, about ₹1,887 once 18% GST is added.

If the notes around transfusion are what your clinicians finish at 9pm, <a href="/in/products/hospital-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and bring a real consult. For the centre itself, take the record table above to two specialist vendors and one HMS vendor, and make each of them trace a bag in front of you.

_Sources: CDSCO regulatory requirements for blood and its components (Drugs and Cosmetics Rules 122-F to 122-P, Schedule F Part XII-B, Schedule K entry 5B); CDSCO e-RaktKosh advisory, 3 June 2022; DGHS Blood Transfusion Services; e-RaktKosh; NABH Blood Centres Accreditation Programme._

---

## HIPAA-Compliant AI: Check the Feature, Not the Logo
https://patientsquare.com/us/blog/hipaa-compliant-ai/
Published 2026-09-28 · Tags: hipaa, healthcare-ai, baa, ai-governance, vendor-review

A practical way to check HIPAA scope for AI tools, including BAAs, enabled features, data paths, retention, people, and proof.

An AI tool can be used in a HIPAA-compliant workflow when the regulated organization defines the permitted use, signs required business associate agreements, configures the covered services correctly, applies safeguards, trains its workforce, and monitors the actual data path. A vendor logo alone cannot establish that result.

Monday's email says the AI vendor has added file search and a web connector. The practice approved the chat feature six months ago, so a manager assumes the green light carries over. It may not. The new release can add a retrieval store, another service, different logs, and a support path that the old review never covered.

That is the useful meaning of "HIPAA-compliant AI": not a permanent label on a company, but a current decision about a named workflow. The decision has to survive changes in the service, contract, configuration, and people using it.

## The release note that reopens approval

One AI platform can contain several data routes. Chat text may go straight to a model. File search may copy a document into an index. A meeting feature can create audio, a transcript, and a summary. A connector may send part of a prompt to another system. A support engineer may gain temporary access while investigating an incident.

The [HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html) says a cloud service provider that creates, receives, maintains, or transmits ePHI on behalf of a covered entity or business associate is itself a business associate. That remains true when the provider holds encrypted ePHI without the decryption key. A new place that maintains the data is therefore not a cosmetic product change.

Reopen the decision when a release adds a connector, retrieval feature, model provider, storage region, support channel, or new data-use term. Disable the feature for PHI until the review catches up. An approval that cannot name its change triggers is already stale.

## Write an approval receipt

The output of review should be short enough for a staff member to use. Call it an approval receipt. Give the receipt an owner, effective date, and recheck date, then record:

1. the exact product, account tier, feature, and region;
2. the permitted user, task, data, and decision;
3. the BAA parties, covered service, exclusions, and controlling document;
4. the path through the model, retrieval store, logs, backups, export, and deletion;
5. user roles and any vendor support access;
6. written terms for training, evaluation, abuse monitoring, and subprocessors;
7. the person who handles a wrong output, outage, misrouted record, or incident; and
8. the changes that cancel the receipt and require a new decision.

Do not put a scribe, general chatbot, document assistant, and coding helper on the same receipt. They solve different tasks and can move data through different systems. "Enterprise AI" is not a sufficiently precise service name, just as "clinical use" is not a sufficiently precise purpose.

The receipt also prevents quiet account drift. A contract for an enterprise workspace may not cover a personal login, beta feature, or consumer plan. Product names and bundles change. Record the document version and setting you actually checked.

## Send the change through seven questions

The review meeting does not need a long presentation. Put the proposed workflow on screen and answer seven questions in order.

### 1. Contract and BAA scope

Read the BAA beside the order form and current feature documentation. The [HHS business-associate guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html) describes business associates as people or organizations performing certain functions involving PHI on behalf of a covered entity. It also requires appropriate assurances from subcontractors. If the exact service, party, or account is missing, keep PHI out while the contract owner resolves it.

### 2. The complete copy map

Follow one realistic request through the prompt, uploaded files, retrieval index, model route, response, logs, support tooling, storage, export, backup, and deletion. Every copy needs an owner and a retention answer. A diagram that stops at the vendor's front door is incomplete.

### 3. Settings that widen the route

Look for public links, broad workspace roles, long retention, optional history, copied prompts in debug logs, and connectors enabled by default. Test a denied user and a deletion. The successful demo shows what the tool can do; the denied path shows whether the configuration holds.

### 4. Vendor data use

Ask for contract language on model training, product evaluation, safety monitoring, abuse review, and human support access. "Your data is private" is not a usable answer if it never defines the service, purpose, or retention period.

### 5. Staff obligations

The [HHS Security Rule summary](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html) covers administrative, physical, and technical safeguards. It includes risk analysis, workforce controls, access control, audit controls, authentication, integrity, and transmission security. Staff therefore need an approved account, a permitted-use rule, a reviewer for the output, and a clear route for errors. Encryption cannot substitute for those decisions.

### 6. Error and outage ownership

Name the human decision owner and the fallback workflow. A clinical output remains a draft for qualified review. A service outage needs a route that does not depend on the failed tool. A misrouted record needs an incident owner, preserved evidence, and a contact path.

### 7. Closure evidence

Keep the contract references, settings, screenshots, synthetic test results, unanswered questions, owners, and next review date together. NIST's [AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) is voluntary, but its Govern, Map, Measure, and Manage functions are a useful reminder that a risk decision needs ownership, context, testing, and follow-through.

## Use three verdicts, not a vague green check

An approval meeting should end in one of three states.

**Approved for the named workflow** means the receipt is complete, the exact configuration was tested with synthetic data, and the people who own privacy, security, clinical use, and operations accepted their parts.

**Approved with conditions** means the use can start only after named settings, training, or contract evidence are complete. Put an owner and due date on every condition. Until then, the feature stays off for PHI.

**No PHI** means a required BAA, service boundary, access control, retention answer, or accountable owner is missing. Staff can still use synthetic or properly de-identified data if policy allows, but the verdict is not permission to improvise with a real chart.

This language is deliberately narrow. It tells a user what is allowed today and tells the next reviewer what would invalidate the answer.

## Run the re-approval drill

Take the newly announced feature and compare it with the existing receipt. Use synthetic data to send one representative request, try access from a denied role, delete the item, and open a support case. Observe where the request and support evidence appear. Do not rely on the sales demo or the behavior of the older feature.

Then make one of the three verdicts. If the change passes, issue a new receipt. If it does not, leave the old approval in place only for its old scope. That separation is the difference between feature governance and a vendor-wide badge.

## Put Patient Square through the same gate

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square states that it is HIPAA compliant, makes BAAs available, encrypts data with TLS 1.2 or higher in transit and AES-256 at rest, uses role-scoped logged access, and has a SOC 2 Type II audit in progress. Those statements are published on the [Patient Square security page](../../security/). They answer vendor questions; they do not replace a practice's risk analysis, account controls, workflow policy, or feature-specific approval.

For an ambient documentation workflow, use the [AI scribe BAA and consent guide](../ai-scribe-hipaa-baa-consent/) and the [AI scribe security checklist](../ai-scribe-security-checklist/) as inputs. [review the current Practice Copilot scope](../../products/practice-copilot/), test the named workflow, and leave with a verdict your staff can follow.

---

## IEC 62304 Explained for Software Engineers
https://patientsquare.com/us/blog/iec-62304-explained/
Published 2026-09-28 · Tags: iec-62304, medical-device-software, software-lifecycle, healthtech-engineering

IEC 62304 is a medical-device software lifecycle standard. See its scope, process map, safety classes, SOUP work, maintenance, and evidence trail.

IEC 62304 is an international standard for medical-device software lifecycle processes. It lays out a common framework of processes, activities, and tasks for developing and maintaining software that is itself a medical device or is embedded in one. It does not decide whether a product is a medical device.

IEC 62304 tells a medical-device software team how to run and document its software lifecycle. It does not decide whether your app is a medical device, prove that the finished device is safe, or hand engineers a coding framework. Start with intended use. If device rules apply, build a traceable evidence system around the standard's processes.

> Takeaways:
> - Scope comes before lifecycle: a health app is not automatically device software.
> - FDA recognizes IEC 62304 Edition 1.1 for medical-device software lifecycle processes.
> - Safety class changes the required work, but it does not replace the product risk process.
> - Maintenance, problem resolution, configuration management, and SOUP belong in the lifecycle from day one.

## The first ticket is an intended-use decision

An engineer receives a request: "Add an alert when a lab value looks dangerous." The code may be small. The intended use is not. Does the function merely store or display information? Does it analyze a signal? Does a clinician independently review the basis of a recommendation? What harm could follow if the software is wrong or unavailable?

Those questions belong before the sprint estimate. The FDA's [device software functions guidance](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications) explains the agency's oversight policy for software functions that may meet the device definition and identifies categories where FDA intends to exercise enforcement discretion. The exact regulatory conclusion depends on the function and its claims.

Once the organization determines that software is itself a medical device or part of one, IEC 62304 supplies a lifecycle framework. The [FDA consensus-standard record](https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfstandards/detail.cfm?standard__identification_no=38829) says IEC 62304:2006+A1:2015 defines lifecycle requirements for medical-device software and applies to development and maintenance. The same record notes that the standard does not cover validation and final release of the medical device.

## The evidence map engineers can use

The standard is purchased text, so a blog should not impersonate it clause by clause. This map is a planning aid. Use the licensed standard and your quality system for the actual requirements.

| Workstream | Engineering question | Evidence that should stay connected |
|---|---|---|
| Development planning | Who does what, with which methods and tools? | Plan, responsibilities, lifecycle model, referenced procedures |
| Requirements analysis | What must the software do, and what must it never do? | Identified requirements, interfaces, risk controls, review record |
| Architecture and design | Where are responsibilities and risk controls allocated? | Architecture, units, interfaces, segregation rationale |
| Implementation and verification | What was built, reviewed, and tested? | Versioned code, review evidence, tests, results, unresolved anomalies |
| Integration and system testing | Do combined components meet the specified behavior? | Build identity, test environment, trace links, observed results |
| Release | Which known problems remain, and what exactly ships? | Release decision, configuration, anomaly record, archive |
| Maintenance | How are field changes assessed and controlled? | Change request, impact analysis, regression evidence, release history |
| Problem resolution | How does a defect move from report to closure? | Report, investigation, decision, correction, verification, notice |
| Configuration management | Can the team reproduce the evaluated software? | Item list, versions, baselines, change control, build record |

The hard part is not creating nine folders. It is keeping the links alive. A risk control points to a requirement. The requirement points to design and code. Verification shows the control was implemented. A later change shows which evidence was reconsidered.

## Safety class is a work-scaling decision

IEC 62304 uses software safety classes A, B, and C. The class affects how much lifecycle work applies. Treat the classification as an engineering and risk-management decision with a written rationale, not a label chosen to reduce paperwork.

The useful conversation starts with failure. What hazardous situation can a software failure contribute to? Which controls outside the software reduce the possible harm? Are those controls independent and supported by evidence? The team then carries the result into planning, architecture, verification, and maintenance.

FDA's [premarket software guidance](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/content-premarket-submissions-device-software-functions) uses its own Basic and Enhanced documentation levels for premarket submissions. Do not silently equate those levels with IEC 62304 classes. They answer different documentation questions in different frameworks.

## SOUP needs an owner, not a ban

Medical-device software contains operating systems, libraries, databases, and other components the device manufacturer did not develop under its own lifecycle. IEC 62304 calls out software of unknown provenance or pedigree, usually shortened to SOUP.

The practical job is inventory and control. Record what the component is, the exact version, why it is needed, known anomalies relevant to the device, cybersecurity and safety concerns, and the route for updates or replacement. Pin the evaluated version. Monitor problems that could change the risk analysis. Re-run the affected verification when it changes.

A dependency scanner can help find packages. It cannot decide whether an upstream defect affects a hazardous situation in your product. That link still needs a person.

## Maintenance starts before release

The [IEC publication record](https://webstore.iec.ch/en/publication/22790) identifies the standard as "Medical device software - Software life cycle processes" and includes Amendment 1:2015 in the consolidated edition. Lifecycle means the job continues after the first release.

Suppose a library update closes a security flaw but changes timing around an alarm. The team needs the released baseline, affected requirements and risks, regression evidence, remaining anomalies, and a controlled decision. If those links live only in the memory of the engineer who left last spring, maintenance becomes archaeology.

We think the best implementation starts with one vertical trace. Pick a risk control. Follow it through the requirement, architecture, code, test, release, and first plausible maintenance change. The exercise will expose broken ownership faster than a document-count audit.

## The Patient Square boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square does not represent Practice Copilot, Hospital Copilot, or its AI Medical Scribe as a medical device. This article is an educational explanation of a device-software lifecycle standard, not a claim that the standard applies to Patient Square or to every clinical software product.

If your team is defining a medical-device function, settle intended use and jurisdiction with qualified regulatory owners, obtain the licensed standard, and build the trace around your real process. For non-device clinical software, the [HIPAA app architecture checklist](../hipaa-compliant-app-architecture-checklist/) covers a different question: how ePHI moves through the system. The [healthcare interoperability guide](../healthcare-interoperability-guide/) covers exchange contracts rather than device lifecycle evidence.

---

## Medical Coding Audit Software: Reopen an Old Finding
https://patientsquare.com/us/blog/medical-coding-audit-software/
Published 2026-09-28 · Tags: medical-coding-audit, coding-compliance, icd-10, healthcare-software, revenue-cycle

A buyer's test for medical coding audit software using old-finding reconstruction, source precedence, reviewer actions, exports, and correction evidence.

Medical coding audit software should help reviewers reconstruct old findings from source evidence, record a human decision, and retain exportable correction proof. Test those controls with representative claims before treating a system output as a coding conclusion.

A coding finding ages badly when its rationale lives only in the original reviewer's memory.

Set the product demo six months after a fictional audit. The reviewer has changed jobs. A replacement auditor receives only the case identifier and must explain why the claim was flagged, which rule version applied, who resolved the disagreement, and whether the correction reached its destination.

That future-date exercise is a demanding medical coding audit software evaluation. The product has to preserve a decision, not merely display one.

## The durable unit is the finding record

For each audited claim, the system should connect five kinds of evidence.

| Evidence | What the buyer should inspect | Failure signal |
|---|---|---|
| Source | Note version, order, report, claim data, payer response | A reviewer cannot tell which record was examined |
| Rule | Named rule source, version or effective date, and relevant section | The finding says only "policy mismatch" |
| Finding | Specific code, modifier, unit, diagnosis link, or documentation issue | A generic risk score replaces an explainable issue |
| Decision | Reviewer, timestamp, disposition, rationale, and escalation | An override erases the original finding |
| Closure | Correction, resubmission or education action, owner, and proof | A closed status has no downstream evidence |

The FY 2026 ICD-10-CM guidelines say that the classification's conventions and instructions take precedence and stress the need for consistent, complete record documentation ([CMS and NCHS](https://www.cms.gov/files/document/fy-2026-icd-10-cm-coding-guidelines.pdf)). For Medicare procedure coding, CMS publishes the NCCI manual and edit resources, while warning that the edits do not cover every possible incorrect combination ([CMS NCCI manual](https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits/medicare-ncci-policy-manual), [CMS NCCI FAQ](https://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits/medicare-ncci-faq-library)). A useful audit record therefore names the authority it used instead of presenting every flag as universal truth.

## Run a five-artifact acceptance test

Bring synthetic records modeled on the services you actually bill. Include a clean claim, an ambiguous case, a documented correction, a case affected by a rule update, and a record with missing support. No real patient data is needed for the first product test.

Ask the vendor to produce these artifacts from the exercise:

1. The immutable input packet and its ingestion time.
2. The finding with the exact rule reference and effective date.
3. The review record, including a permitted disagreement and escalation.
4. The corrected output without deletion of the prior state.
5. A portable export that another auditor can understand without the vendor's interface.

Reject a demo that substitutes screenshots for exportable evidence. Screenshots may help a reviewer orient themselves, but they are poor material for filtering, reconciliation, or a later independent review.

## Force rule precedence into the open

Coding reviews often involve more than one authority. A claim may touch the current diagnosis-code instructions, procedure-code guidance, a payer's coverage rule, an NCCI edit, a contract term, and an internal workflow policy. Those sources do not all have the same scope.

Give the vendor a collision scenario. For example, let an internal rule lag behind a newly effective official instruction. Ask which rule fires, who can change the precedence, how the change is approved, and whether old findings retain the rule version that produced them.

The answer should be visible in the product, not buried in an implementation consultant's memory. Versioning also needs an effective-time model. A rule published today may govern service dates next month, while a retrospective audit may examine claims from a prior code year.

## Keep suggestions separate from decisions

Software may identify a possible diagnosis code, modifier issue, or documentation gap. That output is a review prompt. It is not proof that the suggested code is supported or that the claim should be changed.

Use three explicit states:

| State | Meaning | Required actor |
|---|---|---|
| Suggested | The system found a candidate issue or code | None yet |
| Reviewed | A qualified reviewer compared the suggestion with the record and rules | Named reviewer |
| Approved | The organization authorized a defined downstream action | Named approver under local policy |

Do not allow a suggestion to become an approved correction merely because nobody answered it within a timer. Silence is not clinical or coding evidence.

## Test the sample, not only the model

An audit result is shaped by the claims selected for review. A product can find many issues in a narrow high-risk pool and still tell you little about the wider population.

Ask for a sampling record that preserves:

- the eligible population and time period;
- every inclusion and exclusion rule;
- the random seed or repeatable selection method when sampling is random;
- targeted strata such as modifiers, denials, new services, outliers, or high-volume codes; and
- the denominator used for every reported rate.

Keep baseline and targeted findings separate. If the product combines them into one percentage, a buyer may mistake a risk-enriched sample for an organization-wide estimate.

OIG's General Compliance Program Guidance describes compliance guidance as voluntary and nonbinding, while presenting infrastructure for health care compliance programs ([HHS OIG](https://oig.hhs.gov/compliance/general-compliance-program-guidance/)). That distinction is useful in product design: a tool can support a compliance process, but its presence does not prove that the process is effective or that every finding is correct.

## Watch the reviewer workflow under pressure

A polished queue can hide weak controls. Run the test with two reviewers who disagree.

The first reviewer should document a rationale and request a correction. The second should reject it based on a different rule interpretation. The software should preserve both positions, route the dispute to the right owner, prevent unauthorized closure, and show the final reason without overwriting history.

Then remove one reviewer's access. Confirm that prior actions remain attributed to that person and that the account can no longer open protected records. Export the audit packet after the access change. If the export loses actor identity or translates it to a generic "system user," the evidence chain is incomplete.

## Demand a usable correction loop

Finding issues is only the first half of an audit program. The other half is learning what changed.

Track correction types separately: claim amendment, documentation education, rule configuration, workflow change, payer inquiry, and no-change decision. Give each an owner and due date. Re-sample the affected category later using documented criteria.

Do not let the software claim that education worked because someone opened a module. The defensible evidence is a defined follow-up sample and its reviewed outcomes.

## Score the product on later reconstruction

Use a scorecard built around work your team must perform after the sale.

| Test | Pass condition |
|---|---|
| Claim reconstruction | An independent reviewer can trace source, rule, finding, decision, and closure |
| Rule currency | Versions and effective dates remain visible on old and new findings |
| Human approval | Suggestions cannot silently become final corrections |
| Sampling integrity | Population, selection logic, strata, and denominators are preserved |
| Access change | Deactivated users lose access without erasing attribution |
| Export | Structured data and readable evidence leave the platform together |
| Re-review | The system supports a documented follow-up sample and comparison |

Set pass conditions before the demo. Otherwise, a feature tour will define success after the fact.

## The Patient Square boundary

Patient Square's public US pricing describes ICD-10 suggestions as part of its clinical documentation workflow and lists EHR-ready export formats ([Patient Square pricing](https://patientsquare.com/us/pricing/)). Those statements do not establish an autonomous coding engine, a final coding decision, automatic claim submission, payer approval, or a complete audit program.

If the documentation step is part of your evaluation, treat every suggested code as review material. Keep the signed note, current coding sources, payer rules, and qualified reviewer in the decision path.

[Review the published product scope](/us/products/practice-copilot/).

A medical coding audit software purchase should end with a later-reconstruction test, not a feature count. If a replacement auditor can reopen one finding, see the governing evidence, understand the disagreement, and verify the correction, the product has supported the work. If they cannot, the record did not survive its first reviewer.

---

## Medical Referral Letter Template for a Clean Clinical Handoff
https://patientsquare.com/us/blog/medical-referral-letter-template/
Published 2026-09-28 · Tags: referral-letter, care-coordination, clinical-documentation, hipaa, physician-workflow

A practical US medical referral letter template built around the receiving clinician's decision, current evidence, routing, and closed-loop follow-up.

A medical referral letter should state the receiving clinician's decision, the relevant current evidence, secure routing details, and the owner for closed-loop follow-up. A clinician must review the record and local policy before sending any patient-specific referral.

The receiving specialist has about one page to answer a practical question: why is this patient here, and what does the referring clinician need from me?

A long chart export does not answer that question. Neither does a referral letter filled with copied history and no request. The useful letter is a routing document with a clinical point of view. It shows the receiving team what changed, what has already been tried, what evidence matters, and who owns the next step.

## A one-page referral structure

Use the template below as a drafting frame, then adapt it to the patient, specialty, payer process, state law, and your organization's policy.

```text
REFERRAL DATE: ____________________

PATIENT
Name: ____________________
DOB: ____________________
Identifier used by your approved workflow: ____________________
Contact and access needs: ____________________

FROM
Referring clinician and credentials: ____________________
NPI when required: ____________________
Practice: ____________________
Direct clinical contact or approved queue: ____________________

TO
Receiving clinician or service: ____________________
Approved destination: ____________________

REFERRAL REASON
State the problem and why specialty input is needed now:
________________________________________________________________

REQUESTED ACTION
Name the requested consultation, opinion, evaluation, co-management,
transfer, or other action:
________________________________________________________________

CLINICAL SNAPSHOT
Current problem and dated course: ____________________
Pertinent findings and source dates: ____________________
Treatments tried and response: ____________________
Conditions relevant to this request: ____________________
Current medications and allergies: ____________________

ATTACHMENTS
List named reports, images, note dates, medication list, and any required
insurance or authorization material:
________________________________________________________________

URGENCY AND SAFETY
Requested timeframe: ____________________
Specific concern and approved escalation path: ____________________

FOLLOW-UP OWNER
Person or team tracking receipt, scheduling, result, and patient communication:
________________________________________________________________

CLINICIAN REVIEW
Reviewed by and credentials: ____________________
Signed date and time: ____________________
```

Do not use the template as a reason to repeat the whole record. Its value comes from selection and ordering.

## Put the request above the history

The referral reason should identify the clinical problem and the reason for specialty input. The requested action should tell the recipient what response would complete the handoff.

Compare these two lines:

> Knee pain. Please evaluate.

> Six weeks of right knee pain after a twisting injury, persistent despite activity modification; please assess the suspected meniscal injury and advise on imaging and treatment.

The second line is fictional, not medical advice. It works as a template example because it supplies a course, response to an initial step, working concern, and requested decision. A clinician would replace every detail with verified patient-specific facts.

Do not manufacture certainty to make the letter sound decisive. If the diagnosis is uncertain, say so. The specialist needs the actual question, not a polished answer that the record cannot support.

## Build the snapshot around the decision

Every item in the clinical snapshot should help the recipient triage, evaluate, or act on the request.

For a medication-related referral, current medications, prior trials, reactions, renal or hepatic information, and the relevant test results may matter. For a surgical opinion, the functional effect, prior treatment, imaging location, and perioperative risks may matter. The referring clinician decides what is pertinent.

Use dates. "Recent MRI" forces the receiving office to search. "MRI right knee, September 12, 2026; report attached" points to a specific artifact. If the image itself is available through a separate exchange path, name that path instead of implying the letter contains it.

## Separate attached facts from summarized facts

A referral letter can summarize a report, but a summary is not the report. Mark the difference.

| Content in the letter | Supporting artifact |
|---|---|
| "CBC on September 10 showed..." | Named lab result and date |
| "Prior therapy did not improve function" | Therapy notes or verified patient history |
| "Imaging raised concern for..." | Radiology report and image-access instructions |
| "Medication stopped because of..." | Medication record and documented reaction |

When the source conflicts with the summary, stop and reconcile it before sending. Copying both versions into the referral merely transfers the ambiguity.

## Handle HIPAA accurately

HHS explains that treatment includes coordination, consultation, and referral between health care providers. The HIPAA Privacy Rule generally permits a covered entity to use or disclose protected health information for treatment without a separate authorization under that federal rule ([HHS treatment guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/disclosures-treatment-payment-health-care-operations/index.html), [45 CFR 164.506](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.506)).

HHS also states that provider-to-provider disclosures and requests for treatment are exempt from the Privacy Rule's minimum necessary standard ([HHS minimum necessary guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/minimum-necessary-requirement/index.html)). Do not turn that exception into a rule to send everything. The treatment team still needs accurate information, reasonable safeguards, correct routing, and compliance with any stricter law, agreed patient restriction, or organization policy that applies.

Use the approved exchange channel. Verify the destination. Avoid placing sensitive details in an unapproved cover message. If the referral includes records subject to a separate federal or state confidentiality rule, follow the rule and your privacy team's procedure.

## Make urgency operational

"Urgent" without a reason, timeframe, or contact path leaves the receiving office to guess.

Write the observable concern and the requested action. For example: "New progressive weakness documented at today's visit; referring clinician requests same-day triage through the approved direct number." This is a fictional wording example. The actual patient assessment and disposition belong to the treating clinician.

Emergency care should not depend on a routine referral queue. Your workflow should state when staff use emergency services, a direct clinician handoff, or another local escalation path.

## Give the loop an owner

Sending is an event. Referral completion is a workflow.

Record the destination, channel, timestamp, sender, and attachments. Track whether the receiving office accepted the referral, whether the patient was scheduled, and whether a report or other response returned. Route exceptions to a named role rather than a shared queue with no service rule.

A practical status set might include drafted, clinician-approved, sent, receipt-confirmed, scheduled, completed, report-received, and exception. Define what evidence changes each status. An automated "sent" flag should not be relabeled "received" unless the channel actually supplies that confirmation.

## Review an AI-generated draft line by line

An AI draft can reduce retyping. It can also carry forward an old medication, turn a tentative assessment into a diagnosis, omit a failed treatment, attach the wrong time frame, or address the wrong recipient.

The signing clinician should verify patient identity, referral reason, requested action, chronology, medications, allergies, test dates, attachments, urgency, recipient, and follow-up owner. This is a content review and a routing review. Both matter.

Patient Square's public US pricing describes an AI medical scribe, review-ready SOAP notes, ICD-10 suggestions, eRx drafts, scheduling, messaging, and EHR-ready exports ([Patient Square pricing](https://patientsquare.com/us/pricing/)). It does not establish unsupervised referral sending or replace the clinician's responsibility for the letter.

[Review the published product scope](/us/products/practice-copilot/).

The best medical referral letter is not the longest record. It is the shortest accurate path from the referring clinician's question to the receiving clinician's next decision, with the supporting evidence and follow-up ownership still attached.

---

## AI Follow-Up for Patient Engagement in India
https://patientsquare.com/in/blog/ai-follow-up-patient-engagement-india/
Published 2026-09-27 · Tags: patient-engagement, patient-follow-up, clinic-operations, consent, india-healthtech

A consent-aware AI follow-up workflow for Indian clinics, with message boundaries, human escalation, outcome tests, and procurement evidence.

An AI follow-up workflow should route only approved administrative messages, capture replies and withdrawals, and hand clinical or uncertain messages to a named person. Evaluate the controls with real clinic exceptions before relying on automation for patient engagement.

A message marked delivered can still be a failed follow-up. It may reach the wrong shared phone, arrive after the patient withdrew permission, ask a clinical question nobody monitors, or create a reply that sits unread overnight.

Patient engagement is therefore a routing problem before it is a writing problem. An Indian clinic needs to know which messages are allowed, where replies go, who handles uncertainty, and what evidence shows the loop actually closed.

> **Key takeaways**
>
> - Separate administrative reminders from patient-specific clinical communication.
> - Record the approved purpose, channel, audience, withdrawal route, and retention rule before automation.
> - Give every reply and failed delivery a named destination and escalation clock.
> - Measure closed work and exceptions, not message volume or unsupported health outcomes.

## Put each message in a lane

Start with the clinic's current messages. Do not begin with a generic campaign library. Place each message in one of four operating lanes:

| Lane | Example | Automation boundary | Human owner |
|---|---|---|---|
| Administrative | Appointment reminder or clinic-hours notice | Use only approved facts and the intended channel | Front desk or operations |
| Workflow prompt | Request to complete an approved form | Explain the task without interpreting the patient's health | Assigned clinic team |
| Clinical reply | Patient describes symptoms or asks about treatment | Route to an authorized clinician; do not improvise advice | Clinical team |
| Urgent or uncertain | Reply suggests immediate risk or cannot be classified safely | Use the clinic's approved escalation and emergency language | Named escalation role |

The lane determines the template, access, monitoring, and fallback. It also prevents an administrative tool from quietly becoming a clinical decision system.

## Write a message contract before a template

For each approved use, record the sender identity, purpose, triggering event, recipient source, permitted content, prohibited content, channel, sending hours, reply destination, escalation time, withdrawal method, and retention rule. Legal, privacy, clinical, and operations owners should sign the parts they control.

India's Digital Personal Data Protection Act, 2023 concerns the processing of digital personal data ([MeitY](https://www.meity.gov.in/static/uploads/2024/02/Digital-Personal-Data-Protection-Act-2023.pdf)). The clinic's advisers should determine how the Act and any other applicable rule apply to the exact message program. A software setting is not a legal conclusion.

Test shared household numbers and changed phone numbers. A message can reveal sensitive context without naming a diagnosis. Use the minimum content approved for the purpose and give staff a documented correction path.

## Route replies before sending the first message

Open the reply queue during a tabletop exercise. Send a confirmation, a cancellation, a clinical question, an unrelated message, an opt-out or withdrawal, and a reply after hours. Watch where each one lands. Confirm who sees it, what timer starts, and how closure is recorded.

If a clinical reply enters an administrative inbox, the test fails. If staff assume a machine will interpret urgency but the product scope does not establish that behavior, the test fails. If nobody can prove that a withdrawal changed the next send, the test fails.

Keep the automated response modest. It can acknowledge receipt and state the clinic's approved next step. It should not diagnose, recommend treatment, alter a prescription, or claim that a clinician has reviewed the message when none has.

## Use a seven-case acceptance board

Put these cases on the wall or in a test sheet:

1. Correct patient confirms an appointment.
2. Patient asks to reschedule.
3. Patient withdraws from the message use.
4. Delivery fails.
5. Shared-device recipient says the patient is unavailable.
6. Patient sends a clinical question.
7. Patient sends an urgent or ambiguous reply after hours.

For each case, record expected route, actual route, person notified, time to acknowledgement, final action, and evidence retained. The board passes only when each case meets the clinic's prewritten threshold or has an approved manual control.

Do not turn a send count into a patient outcome. Useful operating measures include failed delivery, duplicate send, withdrawal handling, unassigned reply, reopened task, and elapsed time to the right human. Better adherence, fewer complications, or clinical improvement would require a suitable study, not a messaging dashboard.

## Keep product claims narrower than the workflow design

Patient Square's India pricing page lists AI Follow-ups within the Autopilot plan ([pricing](../../pricing/)). This page does not claim how that named module triggers, writes, sends, classifies, or escalates a message. Buyers should require a demonstration and current written scope for every row in their message contract.

Patient Square's broader Practice Copilot includes an AI Medical Scribe, AI EHR, scheduling, and messaging as the plan expands. The scribe returns a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after a visit. Those clinical-documentation outputs are drafts and suggestions for review. They do not authorize a follow-up message or treatment change.

Patient Square says its data is encrypted in transit and at rest, that visit audio is processed in memory and discarded after the note is drafted, and that its SOC 2 Type II audit is in progress ([security](../../security/)). Confirm the controls and contracts that apply to the chosen messaging deployment. An audit in progress is not a completed report. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## Keep ABDM outside the claim unless it is proven

The NHA describes ABDM as federated and consent based ([NHA FAQ](https://abdm.gov.in/FAQ)). Patient Square lists ABDM integration as roadmap work. Do not present a clinic follow-up flow as an ABDM consent transaction, certified integration, or production exchange unless current evidence establishes that exact scope.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

To test the routing board against current product scope, [review Practice Copilot's messaging scope](/in/products/practice-copilot/). Bring one administrative message, one clinical reply, and the owner who handles each exception today.

---

## AI Scribe for Orthopaedics in India: Test the Note
https://patientsquare.com/in/blog/ai-scribe-for-orthopaedics-india/
Published 2026-09-27 · Tags: ai-medical-scribe, orthopaedics, clinical-documentation, specialty-clinic, india

Test an AI medical scribe for Indian orthopaedic OPD notes across laterality, examination, imaging review, procedures, follow-up, and clinician sign-off.

An orthopaedic AI scribe should produce a clinician-reviewed draft that preserves laterality, findings, imaging interpretation, procedures, and follow-up. Test representative visits, Hindi or Hinglish input, correction work, and the final signed note before adopting it.

An orthopaedic note can fail on one short word: left.

The rest of the draft may be polished. If the side, joint, movement, measurement, implant, or procedure is wrong, the doctor has to catch it. That makes orthopaedics a useful stress test for an AI medical scribe. The product must preserve exact spoken facts and leave interpretation with the clinician.

Google Ads Keyword Planner reported 320 average monthly India searches for `ai medical scribe`, 50 for `orthopedic software`, and 10 for `orthopedic EMR software` in the 15 September 2026 pull stored with this article's research. The specialty query is small. The documentation problem is specific enough to test without guessing.

> **Key takeaways**
>
> - Test side and site in every pilot case.
> - The scribe drafts the clinician's imaging interpretation; it does not read the image.
> - ICD-10 output stays a suggestion and prescription output stays a draft.
> - Keep a specialist EMR when it owns workflows the scribe does not.

## Build the note around anchors

Before trying the tool, choose the anchors the clinic refuses to lose.

| Note anchor | What the clinician should verify |
|---|---|
| Identity and visit | Patient, date, new or follow-up, reason for encounter |
| Side and site | Left or right, joint, bone, region, level |
| History | Mechanism, onset, course, prior treatment, functional change |
| Examination | Spoken findings, negatives, range or measurement with units |
| Investigations | Study and date, followed by the clinician's stated interpretation |
| Assessment | The clinician's conclusion, uncertainty, and differential if stated |
| Procedure | Site, consent, preparation, action, material, response, instructions |
| Plan | Tests, treatment draft, restrictions, referral, review interval |

These are pilot anchors, not a universal orthopaedic template. A fracture clinic, sports practice, spine service, and arthroplasty follow-up use different detail. The point is to make required facts visible before anyone sees the generated note.

## Use five very different visits

### New injury

Test mechanism, date, side, swelling, neurovascular findings the clinician actually states, imaging reviewed, assessment, and immediate plan. Correct one fact aloud during the visit. The draft should preserve the correction rather than both versions.

### Chronic joint follow-up

Test change since the last visit, pain pattern, function, examination, prior response, and the clinician's next step. Mention the opposite side once in family history or an old injury. See whether it leaks into the active assessment.

### Post-operative review

Test procedure and date, wound or recovery findings stated by the clinician, restrictions, rehabilitation, and follow-up. The scribe should not infer an uncomplicated recovery from silence.

### Office procedure

Use the clinic's approved procedure-note requirements. The draft must not invent consent, technique, medicine, dose, site, or response. If the clinician did not say it, the tool should leave it out or make the gap obvious.

### Rehabilitation review

Test goals, function, range or strength values the clinician provides, adherence, and the next review point. Units and side matter as much as the number.

## The image stays outside the scribe

An X-ray can sit on the screen while the scribe listens. That does not mean the scribe has read it.

The clinician should state the interpretation intended for the note. The draft can organize those words. Patient Square does not claim image interpretation, measurement, or a device connection in this workflow. If the clinic needs PACS, templating, implant inventory, theatre management, or structured measurements, evaluate specialist software for those jobs and keep the system boundary clear.

This is also why the scribe should not silently turn a discussion into a final diagnosis. It prepares a note from the encounter. The doctor interprets the image, examines the patient, decides the assessment, and signs.

## Laterality needs more than spell-check

Run the same short case twice, once for each side. Include "left" and "right" in unrelated context. Add a bilateral symptom with a unilateral procedure plan. Then ask another clinician to review the draft without hearing the original.

The WHO Surgical Safety Checklist asks teams to confirm the patient, site, and procedure before incision and includes site marking where applicable ([WHO Safe Surgery resources](https://www.who.int/teams/integrated-health-services/patient-safety/research/safe-surgery/tool-and-resources)). A clinic note is not the surgical checklist, and an AI scribe does not replace it. The source shows why side and site deserve explicit confirmation rather than trust in fluent text.

Add a laterality line to the sign-off screen or local review habit. If the product does not provide one, make it part of the pilot checklist.

## Hindi in the room, English in the record

Patient Square lists English, Hindi, and 20-plus Indian languages, including code-mixed speech, for Practice Copilot. The note comes back in English ([Practice Copilot](../../products/practice-copilot/)).

Test the actual clinic mix. Combine Hindi history with English examination terms. Use local medicine brands, abbreviations, implant names, and spoken measurements. Add corridor noise and two speakers. A language list is not evidence for one clinician's accent or one crowded room.

Score the finished draft for meaning. A perfectly spelled wrong number is still wrong.

## Keep every clinical output reviewable

Patient Square's scribe can return a structured SOAP note, ICD-10 suggestions, and a prescription draft. The doctor reviews and signs. Codes remain suggestions. The prescription remains a draft; it is not sent to a pharmacy.

Use the same rule for missing content. The product should not manufacture a negative examination, consent, imaging result, or treatment response to make the note look complete. A blank that prompts the doctor is safer than an elegant sentence nobody said.

The Indian Medical Council's Code of Medical Ethics Regulations, 2002, hosted by the National Medical Commission, sets duties around medical records, including retention for indoor-patient records and a response period for qualifying requests ([NMC](https://www.nmc.org.in/rules-regulations/code-of-medical-ethics-regulations-2002/)). The clinic should make approved notes retrievable with their author and date, whether it adopts a new EHR or keeps the current one.

## Check privacy before recording

Map notice and consent, capture purpose, processors, access, retention, security, and deletion. The DPDP Act 2023 ties consent to a specified purpose and the personal data necessary for that purpose ([MeitY Gazette copy](https://www.meity.gov.in/static/uploads/2024/02/Digital-Personal-Data-Protection-Act-2023.pdf)). Counsel should confirm the provisions in force and the exact clinic workflow.

Patient Square states that visit audio is processed in memory and discarded after the note drafts, while notes are encrypted in transit and at rest ([India security](../../security/)). It also states that SOC 2 Type II is in progress and ABDM integration is on the roadmap. Do not convert either status into a certification claim. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## The orthopaedic pilot card

Use one row per visit:

- side and site correct;
- numbers and units correct;
- negatives preserved;
- speakers assigned correctly;
- imaging wording matches the clinician's dictation;
- no unsupported finding or decision;
- correction minutes;
- signed note completed in the intended record;
- fallback used successfully during one simulated failure.

Stop the pilot on a wrong-patient event, repeated laterality error, invented clinical content, unclear draft status, or a route the clinic cannot recover. Fix, retest, and restart with the same case.

An orthopaedic-ready scribe is not one that writes confidently about orthopaedics. It is one that preserves the clinician's side, site, facts, and uncertainty, then waits for review. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and grade every anchor before using the tool in a live OPD.

---

## AI Medical Coding in India: ICD-10 Suggestions
https://patientsquare.com/in/blog/ai-medical-coding-icd-10-india/
Published 2026-09-26 · Tags: medical-coding, icd-10, hospital-operations, india-healthtech

See where AI-assisted ICD-10 suggestions fit in an Indian hospital coding workflow, what a human checks and how to test the process without auto-coding claims.

AI can surface ICD-10 coding suggestions for an Indian hospital, but a qualified reviewer must validate the source documentation, required code set, specificity, exclusions, and payer policy. Evaluate the workflow as assisted code search and review, not autonomous coding or claim submission.

An AI ICD-10 suggestion is a search result, not a signed code. In an Indian hospital, it can place candidates beside the clinician's documentation. A trained reviewer still confirms the applicable code set, checks the record, chooses or rejects the suggestion and owns the final coding decision. No review means no defensible shortcut.

> **Key takeaways**
>
> - Keep AI output labelled as a suggestion through the entire workflow.
> - Confirm the required ICD edition and payer rule before testing.
> - Record every accepted, changed and rejected suggestion with a reason.
> - Do not turn a convenience sample into an accuracy claim.

## One suggestion, five human checks

At 8 p.m. in a Pune hospital, a coder opens a signed discharge record and sees an AI-suggested code. The useful question isn't "Did the system find a code?" It is "Can the reviewer trace this candidate to documented evidence and the right coding rule?"

Use five checks:

1. Source: Is the diagnosis or condition supported by the signed clinical record?
2. Code set: Is this the edition and adaptation required by the hospital, payer or reporting program?
3. Specificity: Does the documentation support the detail in the candidate?
4. Rule: Have applicable inclusion, exclusion and sequencing instructions been checked?
5. Ownership: Who selected the final code and recorded any change?

The [World Health Organization](https://www.who.int/standards/classifications/classification-of-diseases/international-classification-of-diseases) maintains the International Classification of Diseases. Its [ICD-10 instruction manual](https://icd.who.int/browse10/Content/statichtml/ICD10Volume2_en_2019.pdf) describes coding as assigning an alphanumeric code to diagnostic statements and supplies conventions for using the classification. Software can help with the search. It does not become the accountable reader of the record.

## ICD-10 is not one interchangeable database

The letters "ICD-10" can hide an expensive assumption. WHO publishes the international classification. The US Centers for Disease Control and Prevention identifies [ICD-10-CM as the United States clinical modification](https://www.cdc.gov/nchs/icd/icd-10-cm/index.html). An Indian hospital should not inherit a US code set because a vendor demonstration used it.

The Ministry of Health and Family Welfare's [EHR Standards for India](https://www.mohfw.gov.in/sites/default/files/EMR-EHR_Standards_for_India_as_notified_by_MOHFW_2016_0.pdf) identifies ICD-10 among the standards for diagnosis classification in the Indian EHR context. The operational requirement still belongs in the hospital's own coding, payer and reporting policy.

Write this field at the top of the pilot sheet:

| Coding control | Hospital entry |
|---|---|
| Classification and edition | Exact name and version |
| Payer or reporting context | Named scheme or contract |
| Authorized source record | Signed document type |
| Final decision role | Named qualification or role |
| Escalation owner | Named role and response route |

If the first row is blank, the pilot is not ready.

## Where an AI suggestion fits

The safe sequence is short:

`signed clinical documentation → candidate suggestion → human rule check → final code → audit record`

Keep the candidate visibly separate from the final choice. If a reviewer changes or rejects it, capture a reason such as unsupported detail, wrong edition, insufficient documentation, rule conflict or not in scope. The reason list turns correction into usable quality evidence.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot &mdash; an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The [India plan page](../../pricing/) lists ICD-10 suggestions and prescription drafts. It does not claim an autonomous coding engine, a final claim decision or pharmacy transmission. The <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> says ABDM integration is on the roadmap; it is not shipped, and Patient Square does not claim ABDM certification.

That boundary is useful. A suggestion can be reviewed, rejected and measured. An "auto-coded" claim can conceal who made the final decision.

## Build the pilot around corrections

A polished demo tends to show cases that already fit the system. A hospital pilot should include the services and documentation patterns that will actually enter scope, with approval from the relevant clinical, coding, privacy and security owners.

Use this adjudication log:

| Case ID | Suggested code | Final code | Result | Reason | Reviewer | Second review needed? |
|---|---|---|---|---|---|---|
| Approved test ID | Candidate | Final entry | Accepted, changed or rejected | Controlled reason | Named role | Yes or no |

Do not place a real patient's name in a spreadsheet made for a demonstration. Start with synthetic or properly approved de-identified cases. If production personal data enters the evaluation, document purpose, access, processor relationships, retention, deletion and incident handling against the organization's obligations under the [Digital Personal Data Protection Act, 2023](https://www.indiacode.nic.in/bitstream/123456789/22037/1/a2023-22.pdf) and other applicable rules. Get legal review for the actual deployment.

## Measure the workflow without inventing accuracy

Report counts first:

- eligible records;
- records with a suggestion;
- suggestions accepted unchanged;
- suggestions changed;
- suggestions rejected;
- records escalated for missing documentation;
- unresolved cases;
- downstream corrections found after finalization.

Each percentage needs its numerator and denominator. A 40-case convenience sample cannot support a national accuracy claim. Even a large local sample applies only to its defined services, documentation, code set and review process.

We think "coder correction rate" is more useful than a vendor's bare accuracy number because the correction log tells the hospital what must change. It may reveal a terminology mapping issue, missing documentation, a training gap or a use case that should stay outside scope.

## Name the stop rule before day one

The hospital's clinical and coding leaders should set severity and thresholds. Candidate stop events may include a serious unsupported suggestion, repeated wrong attribution, use of the wrong classification, loss of the human review step or a downstream claim effect outside the approved process.

Record who pauses the pilot, what manual workflow resumes, who receives the notice and what evidence is needed to restart. A monthly review meeting is too slow if nobody has authority during the shift.

For broader hospital operations, the [hospital management system explainer](../hospital-management-system-explained/) maps system boundaries. The [cashless-claim documentation guide](../ai-scribe-cashless-claim-documentation/) keeps documentation support separate from payer adjudication.

## The coder remains the decision point

An AI suggestion can reduce search work when it surfaces a candidate grounded in the signed record and the required classification. It fails when staff treat a plausible candidate as a completed decision.

A rule-based encoder or established coding workflow may be the better fit when the hospital needs deterministic edits, payer-specific controls or integrations that an AI suggestion tool cannot prove. An AI-assisted path earns its place only through reviewed local evidence.

If your coding team has the code-set row and correction reasons ready, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Keep the reviewer in the loop from the first suggestion.

## Frequently asked questions

### Can AI infer a diagnosis that the clinician did not document?

It should not become the source of a diagnosis. Coding follows the authorized clinical record and the applicable rules. If the documentation lacks support, the workflow should route the case through the hospital's approved clarification process. Do not let a plausible suggestion silently add clinical meaning to the signed record.

### Should the pilot include cashless insurance claims?

Only if the hospital has approved that scope and named the payer rules, decision owner and downstream controls. Start with candidate suggestions and human review. Do not imply that an ICD suggestion predicts payer acceptance. Claim submission and adjudication are separate workflows with their own evidence and accountability.

### Can a coding team report an acceptance rate?

Yes, with the numerator, denominator, sample method, services, code set and time period. Acceptance is a workflow measure, not proof that every accepted code was correct. Add independent review or adjudication to evaluate quality, and keep changed and rejected reasons visible beside the rate.

### What data should a vendor receive for a pilot?

Start with the minimum needed for the approved purpose and prefer synthetic or approved de-identified cases during evaluation. Map any production personal data, access roles, processors, retention and deletion before use. The hospital's privacy and legal teams should approve the real data path and contract terms.

### Does a suggestion reduce the hospital's accountability?

No. The hospital still owns its clinical record, coding policy, staff authorization, payer submissions and audit response. A vendor can provide a candidate and evidence trail. The qualified human and organization decide how that candidate enters the final record or claim under the applicable rules.

---

## Voice to Notes for Doctors: Pick the Right Output
https://patientsquare.com/in/blog/voice-to-notes-for-doctors-india/
Published 2026-09-26 · Tags: voice-to-notes, medical-dictation, ai-medical-scribe, clinical-documentation, india

Compare generic voice typing, medical dictation, transcription, and an AI scribe for Indian clinics by output, review, language, privacy, and record handoff.

Voice typing, dictation, transcription, and AI scribes create different outputs and require different review steps. Choose the workflow that produces the record your clinic needs, then test language handling, privacy, correction work, and the final record handoff.

"Voice to notes" sounds like one feature. It is at least four products wearing the same label.

One types exactly what a doctor says. One sends a recording to a person. One returns a transcript. One tries to sort the consultation into history, findings, assessment, and plan. If a buyer does not name the required output, every demo can claim success.

Google Ads Keyword Planner reported 8,100 average monthly India searches for `voice to notes`, 4,400 for `medical transcription`, and 480 for `voice dictation` in the 15 September 2026 English pull stored with this article's research. The demand is broad. The clinical choice needs to be narrow.

> **Key takeaways**
>
> - Decide whether you need raw text, a transcript, or a structured draft note.
> - Test the final output, not the animated waveform.
> - Hindi or Hinglish input does not guarantee a usable English clinical record.
> - Keep prescription output as a draft and coding output as suggestions.

## Four products behind one phrase

### Generic voice typing

The microphone types words where the cursor sits. This can work for short letters, instructions, and dictated paragraphs. The doctor controls the order and punctuation. The tool does not need to understand the clinical encounter as a whole.

Its weakness is also simple: a wall of accurate text is still a wall of text. Someone must place history, examination, assessment, and plan in the right sections. Generic consumer tools also require a privacy review before any patient information enters them.

### Medical dictation software

Medical dictation adds specialty vocabulary, correction commands, templates, or direct text entry into a clinical application. It still follows the doctor's monologue. The doctor decides what to dictate after or during the visit.

This suits clinicians who already think aloud in a reliable note order. It can be frustrating for someone who wants to stay in conversation with the patient and summarize later.

### Recorded transcription

A recording goes to speech recognition, a transcriptionist, or both. The output is usually a transcript or dictated report. Turnaround, quality control, audio retention, and access vary by service, so the clinic must inspect the actual contract and workflow.

### Ambient AI scribe

The product listens to the consultation and prepares a structured draft. It must distinguish speakers, filter small talk, preserve negation, place details in the right section, and avoid inventing missing findings. That is a larger job than speech to text. The clinician still reads and approves the note.

Patient Square's AI Medical Scribe is one module inside Practice Copilot. Its public India page describes code-mixed input across English, Hindi, and 20-plus Indian languages, with a structured English note, ICD-10 suggestions, and a prescription draft for review ([Practice Copilot](../../products/practice-copilot/)). The prescription is not sent to a pharmacy. The codes are not final coding.

## Pick the output before the product

| Need at the end | Likely starting category | Proof to demand |
|---|---|---|
| A paragraph at the cursor | Voice typing | Words, punctuation, correction, and privacy fit |
| A dictated letter or report | Medical dictation | Vocabulary, commands, template, destination |
| Verbatim or edited speech record | Transcription service | Speaker labels, turnaround, quality review, retention |
| Reviewable visit note | AI medical scribe | Structure, omissions, unsupported content, clinician sign-off |

A clinic may need more than one. A radiologist might dictate a report and use a different tool for an outpatient consultation. A hospital may keep a transcription service for operative reports while piloting ambient notes in one OPD. Do not force every document through the newest workflow.

## The Hindi-English test

Use a five-minute sample that sounds like the clinic. The patient can answer in Hindi. The doctor can name medicines and investigations in English. Switch languages mid-sentence. Add a family member who talks over one answer. Correct a dose aloud. Mention a negative finding.

Then compare the draft with the encounter. Did the product keep "no fever" negative? Did it assign the family member's history to the patient? Did it preserve the corrected number? Did it turn a discussion into a diagnosis the doctor never made?

The score should separate capture from clinical structure:

1. spoken content preserved;
2. speaker assigned correctly;
3. negation and numbers preserved;
4. content placed in the right section;
5. nothing unsupported added;
6. corrections easy to make;
7. final note readable in English.

No published accuracy percentage can answer those questions for your room. Run the sample.

## Voice data still needs a data map

The DPDP Act 2023 states that consent for personal-data processing must relate to a specified purpose and be limited to data necessary for that purpose ([MeitY Gazette copy](https://www.meity.gov.in/static/uploads/2024/02/Digital-Personal-Data-Protection-Act-2023.pdf)). Its provisions have a commencement process, so the clinic should obtain legal advice on what is in force and how the Act applies to the chosen workflow.

The operational map is useful regardless:

- what the microphone captures;
- whether audio leaves the device;
- who processes it;
- whether audio or transcripts remain after the note;
- who can open the draft;
- where the signed record lives;
- how data is returned or deleted.

Patient Square states that visit audio is processed in memory and discarded once the note is drafted, that records are encrypted in transit and at rest, and that SOC 2 Type II is in progress ([India security](../../security/)). Its security page describes DPDP-aligned handling and says ABDM integration is on the roadmap. Roadmap does not mean live or certified. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## A note must survive beyond the demo

The Indian Medical Council's 2002 ethics regulations, hosted by the National Medical Commission, set medical-record duties including a three-year period for indoor-patient records and a 72-hour response when qualifying records are requested ([NMC](https://www.nmc.org.in/rules-regulations/code-of-medical-ethics-regulations-2002/)). Those provisions do not tell a clinic which voice product to buy. They do make record access and retrieval a real acceptance question.

Ask where an approved note lands. Can another authorized clinician find it? Does the author and sign-off remain visible? Can the clinic export it? What happens when the voice service is unavailable?

MoHFW's EHR Standards for India 2016 cover record structure, terminology, exchange, privacy, and security recommendations ([MoHFW](https://esanjeevani.mohfw.gov.in/assets/guidelines/ehr_guidlines.pdf)). Use the standards to ask how a structured output preserves meaning. Do not treat a familiar code or file format as proof of conformance.

## A seven-day buying test

Pick ten recurring visit types and two awkward ones. Rotate clinicians rather than relying on the champion. Record correction time, missing facts, unsupported additions, wrong speakers, failed sessions, and completion in the clinic's record.

Try one outage. Use the fallback. Restore service and check for duplicates.

At the end, choose the smallest workflow that produces the required output. A good dictation tool may beat an ambient scribe for dictated letters. A scribe may beat voice typing when the doctor wants the conversation turned into a draft note. The category follows the work.

<a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">Compare the options</a>. Ask the demo team to show the draft, correction, sign-off boundary, and final record route without skipping a screen.

---

## EMR Implementation in India: A Practical Rollout Plan
https://patientsquare.com/in/blog/emr-implementation-guide-india/
Published 2026-09-25 · Tags: emr, implementation, india, hospital

What EMR implementation really takes in an Indian clinic or 50-bed hospital: honest timelines, data migration, master data, go-live day, and month 1 to 3.

For a two-doctor clinic, about two weeks from master data to a retired paper register. For a 50-bed hospital, six to ten weeks. Installation is a day of that. The rest is building your service and tariff masters, cleaning the patient list, training the front desk, and running both systems side by side until the numbers tally.

EMR implementation is a sequencing problem, not a software problem. A two-doctor clinic can be off paper in about two weeks. A 50-bed hospital needs six to ten. The order that works is the same at both sizes: master data first, then a pilot department, then a capped parallel-running period, then everything else.

> **Key takeaways**
>
> - Two doctors: roughly two weeks. Fifty beds: six to ten. Installation is one day of that; the rest is masters, migration and training.
> - Build master data before you migrate anything. Services, tariffs, doctors, roles, and the ABDM facility and practitioner IDs if you're joining.
> - Migrate the active panel and about twelve months of history. Not the archive. Keep the paper registers.
> - Parallel running needs an end date before it starts. Two weeks is usually enough.
> - Month 1 to 3 breaks at the front desk and the billing tally, almost never at the doctor's screen.

## What implementation actually is, once the sales language comes off

Installing the software takes an afternoon. For a cloud system it takes a login. What takes weeks is everything the software cannot do for you: deciding what your service list is called, agreeing on the tariff for a dressing, cleaning a patient list with four spellings of the same surname, and getting a receptionist to trust a screen over a register she has run for eleven years.

That's the whole job. Cloud or an on-premise box decides who patches the server and where the data sits. It changes almost nothing about the list above. Our [cloud versus on-premise breakdown](../cloud-emr-vs-on-premise-india/) covers that decision separately; this piece assumes you've made it.

## A realistic timeline: two doctors versus fifty beds

Here's how we'd sequence it at both ends of the range. The phases don't change with size. The duration and the number of people in each one do.

| Phase | What it covers | 2-doctor clinic | 50-bed hospital |
|---|---|---|---|
| Master data | Services, tariffs, doctors, users, roles, departments, beds | Days 1 to 3 | Weeks 1 to 2 |
| Data migration | Active panel, last 12 months, outstanding balances | Days 3 to 5 | Weeks 2 to 3 |
| Core training | Front desk first, then billing, then doctors | Day 5 | Week 3, repeated per shift |
| Pilot department | One OPD or one specialty, real patients | Days 6 to 8 | Week 4 |
| Parallel running | Both systems, capped, daily tally | Days 8 to 12 | Weeks 5 to 6 |
| Full go-live | Registers retired, one fallback day only | Day 12 | Week 7 |
| Stabilisation | Daily fix list, weekly review, master data cleanup | Weeks 3 to 6 | Weeks 8 to 12 |

_Add two weeks to the hospital column if you're also doing IPD, pharmacy and insurance claims in the same rollout. We'd argue you shouldn't, at least not in the same month._

The hospital timeline stretches for one reason: shift work. A clinic trains two doctors and one receptionist once. A 50-bed hospital trains three shifts of front desk, a billing team, nursing on two floors, and visiting consultants who come twice a week and were not there on training day.

## Master data first, because everything downstream inherits its mistakes

This is the least interesting part of the project and the one that decides whether it works. Get it wrong and you'll be correcting bills in month three.

What has to exist before a single patient is entered: the service list with the exact names your staff already say out loud, the tariff for each service including any package and insurance rate, every doctor with their registration number, user accounts with roles that actually restrict what a receptionist can see, departments, and bed numbers if you run IPD.

Name one owner for this. One person, named, whose job it is to approve a new service or tariff, before and after go-live. The commonest failure we see is that master data has an owner during the project and nobody after it.

If you plan to join ABDM, register here rather than after go-live. Ayushman Bharat Digital Mission is run by the National Health Authority and participation is voluntary; nothing forces a private clinic to integrate. Facility and healthcare-professional registration now both run through ABDM's National Healthcare Providers Registry, and the older facility and professional registry addresses redirect there. Those IDs sit in the same doctor and facility records that appointments, prescriptions and reports all reference, so doing it later means touching every one of them again. Our [ABHA linking walkthrough](../abha-linking-clinic-workflow/) covers the day-to-day flow.

One more decision worth making now: coding. The MoHFW's Electronic Health Record Standards for India, 2016 name SNOMED CT as the primary clinical terminology, LOINC for tests, measurements and observations, and the WHO ICD family for disease classification. You don't need to code everything on day one. You do need masters that can hold those codes, because retrofitting them into three years of free text is not a project anyone finishes.

## Data migration: the decision is what to leave behind

Almost every clinic starts by asking how to get ten years of records into the new system. Wrong question. The right one is how little you can carry and still run Monday's OPD.

| What you're leaving | Carry it in | Leave it where it is |
|---|---|---|
| Paper OPD register | Active panel demographics, phone, allergies, current medicines | Old consult notes; keep the register itself |
| Excel patient list | The full file, after de-duplicating on phone number | Free-text notes columns that no one will search |
| Old on-prem system, clean export | Demographics, appointments, last 12 months of visits, outstanding balances | Deep clinical history unless it exports structured |
| Old on-prem, no usable export | Rekey the active panel only, over two weeks | Everything else; keep the old machine read-only |
| Lab and imaging reports | Scan and attach for active patients only | The archive shelf |
| Outstanding dues | All of it, reconciled to the cash book on one date | Settled ledgers older than the current financial year |

_De-duplicate on phone number before the import runs. Cleaning it up afterwards costs far more. Two records for one patient is the single most expensive mistake in this table, because it splits the clinical history and nobody notices for months._

Two rules sit behind that table. First, the paper doesn't get destroyed. Under regulation 1.3.1 of the Indian Medical Council (Professional Conduct) Regulations 2002 a physician maintains indoor-patient records for three years from the start of treatment, and under 1.3.2 those records must be produced within 72 hours of a request. A migration that quietly leaves a gap is a problem you discover at the worst possible moment.

Second, more is not safer. The Digital Personal Data Protection Act 2023 ties consent to a specified purpose and to the personal data necessary for that purpose, and requires erasure once the purpose is no longer served, except where another law in force requires you to keep it. Record-retention rules like the one above are that exception, so erasure is a decision you make record by record, not a switch you throw. Bulk-loading everything you happen to hold because it might be useful someday is the opposite of that posture. Our [DPDP guide for clinics](../dpdp-act-clinics-guide/) has the longer version, and our [security page](../../security/) sets out how we handle it on our side.

## Parallel running, and how to stop it

Run both systems for two weeks. Front desk enters in the EMR and writes the register. Billing raises the bill in the EMR and tallies it against the cash book at close. It's genuinely annoying, which is the point: parallel running that isn't annoying doesn't end.

Set the end date before you start. Then pick a measurable signal for hitting it. Ours is simple: three consecutive days where the day's collection total comes out of the EMR and matches the cash book without anyone reconstructing anything. Hit that, stop the paper the next morning.

Clinics that skip the end date are still double-entering in month four. At that point the staff have concluded the EMR is extra work rather than the work, and you have lost the rollout without anyone announcing it.

## Training, and the front-desk problem

Picture a 40-bed hospital in Nashik. Two receptionists, three shifts between them and a relief, a billing clerk, six resident doctors, and visiting consultants across ortho, gynae and general medicine. The doctors will be fine. They spend two minutes a visit in the system and their alternative was already dictation or a hurried scrawl.

The front desk is where this succeeds or fails. Their resistance is arithmetic. The senior receptionist registers a walk-in in about fifteen seconds with a pen. The new screen takes her ninety on day one and there are nine people waiting. Telling her the system is better is useless. Getting her to sixty seconds by day four is not.

So: train the front desk first, longest, and on real patients rather than dummy data. Name one super-user per shift. Train billing separately, because their failure mode involves money. Give doctors twenty focused minutes, not a workshop. And book fewer patients for week one, because week one is slower for everyone.

## Go-live day

Pick a Monday. We think that beats a quiet Saturday. Call it a preference, but the reasoning is practical: a Monday gives you a full week of vendor support, your own staff at full strength, and four working days to fix whatever surfaces before the weekend. Going live on a Saturday means finding the problem on Saturday evening and living with it until Monday.

What we'd want in place before the first patient: a printed one-page cheat sheet at each counter, the vendor's support person on a number that actually answers, a lighter appointment list than usual, the paper register on the counter as a fallback for exactly one day, and one person walking the floor whose only job is to answer questions.

Then keep a written fix list. Not a WhatsApp group, a list. Every issue, who raised it, what happened. We'd budget for a few dozen items in the first fortnight at hospital scale, mostly tariff corrections and missing masters. The ones nobody writes down are the ones still broken in month three.

## What actually goes wrong in month 1 to 3

The failures are boring and they repeat.

Tariffs turn out wrong at billing, usually a verbal discount the system doesn't know about. Duplicate patients pile up because the front desk searches by name instead of phone. Doctors quietly go back to paper for "quick" cases, so the share of visits with a note in the system stalls well short of all of them. The month-end report doesn't tally with the cash book and nobody can say why. And the champion who drove the project gets busy, master data ownership evaporates, and new services start getting added by whoever is at the counter.

None of that is a software defect. All of it is cheap to fix in the first ninety days and expensive after.

## How to tell whether it worked

Four numbers, checked at day 30, 60 and 90. What share of visits have a note in the system, which should be near 100% by day 60 and tells you whether the clinical side actually adopted it. Whether the EMR's day total matches the cash book three days running. How many duplicates the patient master has picked up, checked by counting repeated phone numbers. And how long a registration takes now against week one.

Add one more if documentation time was the reason you started: how much of the charting is still happening after the last patient leaves. That's the number clinicians care about, and it's the one a record system alone rarely moves.

## When you should not implement now

Being straight about this matters more than a feature list.

Don't start if you're weeks away from a NABH assessment or any audit. NABH, run under the Quality Council of India, publishes hospital standards and separate entry-level standards for small healthcare organisations, and preparing for an assessment on a system your staff learned last week is a bad trade. Finish one, then start the other.

Don't start in your busiest season, don't start without a named master data owner, and don't start if the person championing it is leaving in two months. A rollout eats slack you may not have. Those are the three cheapest ways to find out.

And don't replace a working system purely on price. Migration has a real cost in staff hours that no quote shows you; our [EHR cost guide](../ehr-software-cost-india-buyers-guide/) breaks down where the money actually goes. If your current EMR stores records fine and the pain is the hour of typing after the last patient, you have a documentation problem, not a records problem, and swapping the record system won't touch it.

## Where we fit, and where we don't

If the documentation hour is the real bottleneck, the cheaper move is to add a layer rather than replace the system. That's a two-week change instead of a two-month one, and our [small-clinic scribe rollout guide](/us/blog/ai-scribe-implementation-small-clinic/) walks through it.

AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft — ready to review and sign about two minutes after the visit.

That module runs alongside whatever you implement. There's no HL7 or FHIR interface between us and your EMR; every plan includes "EHR-ready export (PDF · HL7 · FHIR)", which is an export, not a certified interface. If you'd rather have the record system bundled, our Copilot tier includes the AI Copilot EHR. India pricing per clinician per month on annual billing, ex-GST: ₹1,599 for Assist, ₹2,399 for Copilot, ₹3,999 for Autopilot. Add 18% GST and the Assist invoice is about ₹1,887. The [pricing page](../../pricing/) has what sits in each tier.

Where we're the wrong answer: if live ABHA linking has to work on go-live day, we can't do that today. ABDM integration is on our roadmap and not shipped, and we're not ABDM-certified. eka.care already offers live ABHA linkage, and if that's a hard requirement for your facility, they're the better fit. We'd rather say so than let you find out in week six.

The honest verdict on the whole exercise: EMR implementation succeeds or fails on master data, a hard stop to parallel running, and the front desk. Not on the feature list you compared. If you want to sanity-check your own shortlist first, our [EMR buyer's guide for India](../emr-software-india-guide/) covers what to ask vendors before any of this starts.

If documentation is the piece you want to test on a real OPD day before committing to anything larger, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical Monday list.

---

## Healthcare Interoperability: Trace One Fact End to End
https://patientsquare.com/us/blog/healthcare-interoperability-guide/
Published 2026-09-25 · Tags: healthcare-interoperability, fhir, smart-on-fhir, uscdi, healthtech-engineering

A field guide to healthcare interoperability across meaning, identity, exchange, authorization, operations, and evidence, with a practical delivery sequence.

Healthcare interoperability is the ability to exchange and use the needed information across people and systems in a defined workflow. Start with a specific handoff, clarify the source of truth and failure path, and validate the exchange with representative cases rather than relying on a vendor label.

The result was in both systems. It was still missing.

One interface delivered the lab value. The receiving chart stored it under the wrong encounter, displayed a local code nobody recognized, and gave the on-call team no alert. Transport succeeded. Care did not.

Healthcare interoperability lives in that gap between "payload received" and "the right person can safely use this fact." A useful project traces one fact across meaning, identity, exchange, authorization, operations, and evidence.

## The six-layer test

Pick one fact, such as a potassium result, medication order, allergy, or appointment status. Walk it through six layers.

| Layer | Question | Typical evidence |
|---|---|---|
| Meaning | Do both sides interpret the fact the same way? | Profile, terminology, units, required fields |
| Identity | Is it attached to the right patient, encounter, order, and organization? | Identifier rules, match cases, merge handling |
| Exchange | How does it move and change state? | Message, API, document, event, acknowledgment |
| Authorization | Who may request, receive, or act on it? | Scopes, roles, consent, purpose, launch context |
| Operations | What happens when the path is slow, duplicated, unavailable, or changed? | Queues, alerts, retries, reconciliation, runbook |
| Evidence | How do both parties prove the intended result occurred? | Test fixtures, logs, destination record, owner sign-off |

Most troubled projects over-invest in the third row. They choose a standard, open a connection, and discover later that nobody agreed on the first two or staffed the last two.

## Meaning comes before mapping

A field called `status` can describe collection, clinical finality, interface processing, billing state, or display state. Moving it from one schema to another is not interoperability until the parties agree which meaning survives.

Create a data contract for the use case. For every field that drives care or operations, record its definition, source authority, allowed values, units, null behavior, update rule, and downstream use. Bind coded values to named terminology and version where the program requires it. Document local codes rather than hiding them inside a transformer.

USCDI is a standardized set of health data classes and elements used in federal health IT policy. It gives programs a common data baseline, but it does not define every workflow, API behavior, or local operating rule ([ASTP/ONC USCDI](https://www.healthit.gov/isp/uscdi)). Treat it as one contract input.

## Identity is an exchange of its own

The wrong-patient test belongs at the start, not the final safety review. List the identifiers for patient, encounter, practitioner, organization, location, order, specimen, result, and device that matter to the chosen fact.

Then test collisions and change:

- two people share a name and birth date;
- a local medical-record number is reused outside its assigning organization;
- demographic data changes;
- duplicate records merge;
- an encounter moves between locations;
- an order is replaced or cancelled; and
- the receiver knows the identifier value but not its issuer.

FHIR resources can carry business identifiers and references, yet the implementation still needs rules for scope, issuer, matching, and provenance ([HL7 FHIR Resource](https://hl7.org/fhir/R4/resource.html)). A syntactically valid identifier can still be operationally useless.

## Pick the exchange pattern after the event

There is no single interoperability pipe.

An HL7 v2 message may report an admission or result event. A FHIR client may read or search resources through a defined API. A document may carry a signed summary. A network may support query and exchange across participating organizations. These patterns solve different jobs and can coexist.

Use this short selection sequence:

1. Name the real-world event or user action.
2. Name the authoritative source before and after it.
3. Name the consumer and the decision or task it performs.
4. Set the timing, authorization, and completeness requirement.
5. Choose the exchange pattern already supported by the participants when it satisfies the first four lines.

For the narrower standards comparison, read [FHIR vs HL7 v2](../fhir-vs-hl7-explained/). The sequence matters: a standard implements the use case; it does not invent one.

## FHIR, SMART, and USCDI do different jobs

These names often appear in one procurement sentence even though they answer different questions.

FHIR defines resources and exchange patterns. The SMART App Launch guide defines authorization and launch patterns for applications using FHIR, including scopes and context. USCDI defines a US data set used by federal programs. A certified API criterion can reference all three in a particular regulatory contract ([HL7 SMART App Launch](https://hl7.org/fhir/smart-app-launch/), [ASTP/ONC standardized API](https://www.healthit.gov/wp-content/uploads/2025/05/Standardized-API-for-patient-and-population-services.pdf)).

Do not collapse them into "we have a FHIR API." Ask instead:

- Which FHIR version and implementation guide apply?
- Which resources, profiles, search parameters, and operations are supported?
- Which USCDI version and elements are in scope for this program?
- Which SMART launch mode, scopes, token behavior, and context are supported?
- Which roles and organizations may access which patients for which purpose?
- What happens when an optional element is absent?

A server's CapabilityStatement and the applicable implementation guides belong in the acceptance packet.

## Networks add policy to the wire

Cross-organization exchange needs more than an endpoint. Participants need common terms, permitted purposes, directory and identity rules, security expectations, dispute processes, and operating agreements.

The Trusted Exchange Framework and Common Agreement is a US framework for nationwide network-to-network health information exchange. The Recognized Coordinating Entity publishes the Common Agreement, qualified health information network materials, standard operating procedures, and related resources ([TEFCA resources](https://rce.sequoiaproject.org/tefca-and-rce-resources/)).

TEFCA is not a synonym for every interface between two systems. If it is relevant, state which participant, exchange purpose, network path, and operating procedure apply to the use case.

## Failure behavior is part of the clinical contract

A result that arrives twice, late, or without an order link can create work even when its values are correct. Write a failure matrix before go-live.

| Failure | Receiver behavior | Owner | Recovery proof |
|---|---|---|---|
| Duplicate event | Detect by stable business identity; do not create a second clinical fact | Interface owner | One final record, duplicate logged |
| Unknown patient | Hold outside the chart; route to reconciliation | Registration or HIM | Authorized match and release trail |
| Invalid code or unit | Reject or quarantine under the contract | Data steward | Corrected value and replay evidence |
| Destination unavailable | Queue or stop according to agreed durability boundary | Operations | Backlog drains without loss or duplication |
| Authorization denied | Return a clear denial; never weaken scope silently | Security owner | Denied test and audit event |
| Late correction | Preserve provenance and update the intended record | Clinical data owner | Old and new states traceable |

Rehearse the matrix. A runbook that nobody has used is a hypothesis.

## Acceptance follows the fact

The best acceptance test begins in the source workflow and ends where a user acts.

For a lab result, prove the order identity, specimen, code, value, unit, reference range, status, time, patient, encounter, provenance, and correction behavior. Verify the receiving display and any alert or queue. Then reconcile the source and destination.

Keep the request or message, response or acknowledgment, validation output, logs, destination evidence, and owner decision in one test record. That packet tells a future engineer what "worked" meant.

## The Patient Square boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The public scope includes "EHR-ready export (PDF · HL7 · FHIR)." It does not include a claim of certified interoperability, FHIR conformance, SMART App Launch, TEFCA participation, a named EHR connection, automatic filing, or write-back. Export may be the right handoff for a workflow. If a live exchange is required, it needs its own contract and evidence.

Start the next architecture meeting with one fact, not a diagram of every system. Trace it through all six layers. The missing agreement usually appears before the first connector is built.

---

## FHIR vs HL7 v2: Pick by Workflow, Not Age
https://patientsquare.com/us/blog/fhir-vs-hl7-explained/
Published 2026-09-24 · Tags: fhir, hl7-v2, interoperability, healthcare-developers, healthtech

Compare FHIR resources and APIs with HL7 v2 event messages, then choose by workflow, source authority, exchange contract, identity, failure handling, and evidence.

HL7 and FHIR are healthcare interoperability standards, but neither alone proves that two systems can exchange the required data safely in a real workflow. Define the use case, data elements, ownership, transport, error handling, and validation evidence before treating a standards claim as an integration.

An admission message arrives. Should the next system receive an `ADT^A01`, or should an app fetch an Encounter resource? That sounds like a standards question. It is really a workflow question wearing angle brackets.

FHIR and HL7 v2 are not two rungs on one upgrade ladder. They package work differently. Start with the business event, authority, and consumer. The wire format comes later.

> Takeaways:
> - HL7 v2 sends event messages; FHIR organizes exchange around resources and defined interactions.
> - Hospitals often need both because events, documents, queries, and app access are different jobs.
> - A standard name does not settle profiles, local codes, identity, authorization, retries, or ownership.
> - Export in an HL7 or FHIR format is not proof of a live interface.

## HL7 is the family name

"HL7 versus FHIR" is common shorthand, but it hides the family tree. Health Level Seven International publishes HL7 Version 2 and FHIR, along with other standards. The useful comparison is HL7 v2 versus FHIR.

HL7 v2 is message-oriented. A sending system reports an event, such as an admission, order, or result, using a message whose segments carry fields. Implementations commonly exchange those messages over interfaces that define triggers, fields, local codes, acknowledgments, retries, and operations. HL7 describes Version 2 as a standard for exchanging clinical data among systems ([HL7 v2 product brief](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185)).

FHIR is resource-oriented. HL7 defines resources for clinical and administrative concepts and several ways to exchange them. A resource has identity, metadata, structured elements, and possible human-readable text. Resources can reference one another, and REST is one specified exchange style ([FHIR resource architecture](https://hl7.org/fhir/R4/overview-arch.html), [FHIR RESTful API](https://hl7.org/fhir/R4/http.html)).

| Dimension | HL7 v2 | FHIR |
|---|---|---|
| Usual unit | Event message | Resource or bundle of resources |
| Common shape | Delimited segments and fields | JSON, XML, or other defined representations |
| Typical motion | Sender pushes a business event | Client reads, searches, creates, or updates within allowed interactions |
| Contract evidence | Interface specification plus message samples | Capability statement, profiles, implementation guide, scopes, and examples |
| Frequent trap | Assuming the standard eliminates local variation | Assuming a REST endpoint behaves like a generic database API |

Neither column is inherently more correct. The receiving workflow decides.

## Follow one admission through both models

Suppose registration completes an inpatient admission.

In an HL7 v2 flow, the registration system may emit an admission event. The receiver processes the message, matches the patient and visit, applies field mappings, updates local state, and returns an acknowledgment under the interface contract. If a field is missing or a destination is unavailable, the parties need an agreed retry and reconciliation path.

In a FHIR flow, an authorized client may read or search Patient and Encounter resources, or receive a notification under an implementation pattern defined for that environment. The server's capabilities, profiles, search support, authorization, and local policy determine what the client can do. FHIR does not imply that every client may create or update every resource.

The two approaches can coexist. A hospital can continue event-driven HL7 v2 feeds while exposing selected FHIR APIs for app access. An integration service may even translate between representations, but translation does not automatically preserve business meaning. The owner still has to decide which event becomes which resource state and how conflicts resolve.

## Choose with a five-line use case

Before a standards workshop, write this card:

1. When this real-world event occurs...
2. this source is authoritative for...
3. this consumer needs these data to perform...
4. within this time and authorization boundary...
5. with this recovery path when exchange fails.

Now compare options.

A lab result delivered to an existing hospital result interface may fit the established HL7 v2 route. A patient-authorized application reading a standardized data set from a certified API may fit FHIR plus SMART App Launch. A longitudinal summary sent as a document may call for a different standard again. The card prevents "modern" from becoming the sole requirement.

## FHIR brings web patterns, not magic

FHIR's RESTful API specification defines interactions such as read, search, create, update, and history, with HTTP behavior and FHIR representations ([FHIR RESTful API](https://hl7.org/fhir/R4/http.html)). That familiarity helps web developers, but a healthcare API still carries domain rules.

Ask for these artifacts:

- the FHIR version and server base URL;
- the server's CapabilityStatement;
- required profiles and implementation guides;
- supported resources, interactions, search parameters, and operations;
- terminology and value-set bindings;
- authorization scopes and launch context;
- identifier and patient-matching rules;
- provenance, update, deletion, and history behavior; and
- rate limits, errors, downtime, and support ownership.

The US certification criterion for standardized patient and population services references FHIR R4, US Core, USCDI, and SMART App Launch requirements. It also includes API and token-related obligations for certified developers ([ASTP/ONC standardized API fact sheet](https://www.healthit.gov/wp-content/uploads/2025/05/Standardized-API-for-patient-and-population-services.pdf)). That is a defined regulatory context, not proof that every FHIR server supports every imagined workflow.

## HL7 v2 is not one universal message

Two systems can both say "HL7 v2" and disagree about version, trigger, required segments, repeated fields, local codes, identifiers, and acknowledgment meaning. The interface specification is where those differences become testable.

Record at least:

- business event and trigger;
- sending and receiving applications;
- version and message structure;
- required, optional, and prohibited fields;
- local code sets and owners;
- patient, visit, order, and result identifiers;
- acknowledgment boundary;
- duplicate and out-of-order behavior;
- transport and security; and
- queue, alert, replay, and reconciliation ownership.

An `AA` acknowledgment means only what the parties define it to mean. Did the receiver parse the message, queue it durably, or update the final clinical system? Put that state in the contract.

## Identity breaks both standards

A well-formed message or resource can still point to the wrong person, encounter, order, or organization. Treat identity as its own design surface.

Test exact matches, changed demographics, twins, reused local numbers, merged records, unknown identifiers, and cross-organization identifiers. Preserve source identifiers and provenance. Do not use a display name as a join key because it looked unique in a fixture.

FHIR resources distinguish logical identity from business identifiers, and HL7's specification explains that resources can carry identifiers representing the underlying real-world entity ([FHIR Resource](https://hl7.org/fhir/R4/resource.html)). The application still needs rules for issuer, system, scope, and reconciliation.

## Acceptance evidence beats a standards logo

For HL7 v2, keep approved messages for ordinary, missing-field, duplicate, delayed, and out-of-order cases. Prove acknowledgment and replay behavior. Reconcile the source event to the destination record.

For FHIR, keep requests, responses, authorization cases, profile validation, terminology failures, pagination, rate-limit behavior, and version evidence. Test a denied scope. Test a server that omits an optional field your user interface quietly assumed would exist.

For both, name who owns changes. A local field or profile can change without a compiler warning in the other organization.

## Patient Square's export boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square states "EHR-ready export (PDF · HL7 · FHIR)." That phrase describes export formats. It does not claim FHIR R4 conformance, an HL7 interface, SMART authorization, a named EHR connection, automatic filing, bidirectional exchange, or write-back. A practice can use Patient Square EHR from the Copilot tier or keep its existing EHR, but a live exchange remains a separate design and acceptance problem.

If an evaluation begins with "Do you support HL7 or FHIR?", hand the team the five-line card first. The answer may be both, neither, or a simple export. Only the workflow can tell you which answer is useful.

---

## Hospital Copilot Implementation: A Department Rollout
https://patientsquare.com/us/blog/hospital-copilot-implementation-guide/
Published 2026-09-24 · Tags: hospital-copilot, clinical-ai-implementation, hospital-operations, ai-governance, change-management

Plan a hospital copilot rollout by department, with governance, simulation, pilot order, stop rules, downtime tests, and evidence for expansion.

Start a hospital copilot rollout with one bounded workflow, a named clinical owner, visible review, and a safe fallback. Expand by department only after simulation, pilot measures, downtime tests, and stop rules show the current cell is ready.

Put a hospital floor plan on the wall. Mark one department, one shift, and one piece of work. That is the first implementation cell. Everything outside the line stays unchanged until the cell produces evidence.

Hospital copilot implementation fails on vague scope long before it fails on model choice. "Launch the platform" gives nobody a safe unit to test. A department rollout gives the hospital a clinical owner, source system, reviewer, fallback, and decision date for each cell.

> **Key takeaways**
>
> - Roll out one department-workflow cell at a time.
> - Give each cell a clinical owner, operations owner, system owner, and pause authority.
> - Simulate identity, routing, correction, outage, and rollback before live use.
> - Expand on measured evidence, not the size of the vendor's module catalog.

## Build the rollout board

The rows are departments. The columns are workflows. A cell might be "hospitalist discharge-summary draft" or "cardiology clinic visit-note draft." It is not "hospital AI."

| Department | First workflow | Source | Human review | Final system | Fallback |
|---|---|---|---|---|---|
| Ambulatory clinic | Visit-note draft | Encounter and approved chart context | Treating clinician | Designated EHR | Established documentation route |
| Hospital medicine | Discharge-summary draft | Approved inpatient record | Responsible clinician | Designated EHR | Existing discharge process |
| Access center | Scheduling task | Approved schedules and booking rules | Authorized staff or configured rule | Scheduling system | Staff booking queue |
| Revenue cycle | Reviewable claims work item, if in scope | Signed record and approved billing inputs | Coding or billing staff | Claims system | Existing work queue |

The last column determines whether the cell can be piloted. If staff cannot explain the fallback, the rollout is not ready.

Patient Square's Hospital Copilot page lists documentation and operational modules and describes both a complete Patient Square HIS/EHR path and an incumbent-system path ([Hospital Copilot](../../products/hospital-copilot/)). Those choices change the board. A bundled record system adds migration and cutover. An incumbent path adds interface and reconciliation work. Neither route should be inferred from the product name.

## Give six people explicit authority

The executive sponsor funds the change and resolves priorities. The clinical owner defines acceptable use and can stop a clinical workflow. The operations owner manages staffing, training, and exceptions. The privacy and security owner reviews data handling and incidents. The record-system owner controls configuration, interfaces, and downtime. The vendor counterpart owns product escalation.

One person can hold more than one role in a smaller hospital. No role can be blank.

NIST's AI Risk Management Framework uses Govern, Map, Measure, and Manage as its core functions ([NIST AI RMF](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10)). The [AI RMF Playbook](https://airc.nist.gov/airmf-resources/playbook/) supplies optional actions. A rollout board turns those ideas into operating assignments: governance names authority, mapping defines the cell, measurement sets pass conditions, and management decides what happens next.

## Phase 0: contract and architecture

Complete this before patient data enters the pilot.

Document the data used by each cell, the vendor's role, retention, permitted uses, access, incident route, return or deletion, subcontractors, and service dependencies. HHS says a covered entity using a cloud service to maintain electronic protected health information needs an applicable business associate agreement and must perform its own risk analysis ([HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)).

Name the authoritative system for every output. If an AI prepares a note, label it as a draft and identify the authentication event. CMS's July 2025 guidance says the treating physician or non-physician practitioner must sign entries made by a scribe, including AI technology, to authenticate the documentation and care ([CMS signature guidance](https://www.cms.gov/files/document/mln905364-complying-medicare-signature-requirements.pdf)).

Draw dependencies. Identity, patient matching, schedules, clinical context, results, messaging, billing, and the record system each need an owner. A line on the diagram is also a possible failure route.

## Phase 1: simulation room

Use fictional patients and approved test accounts. Run the cell through ordinary work, then make it uncomfortable.

Create two similar patient names. Remove a source field. Send a correction after the draft appears. Deny one user access. Break the destination. Delay a dependency. Restore service and watch what duplicates. Ask a staff member who missed training to take over.

The ASTP/ONC SAFER Guides cover patient identification, organizational responsibilities, system configuration, test-result follow-up, clinician communication, and contingency planning among their EHR safety areas ([SAFER Guides](https://healthit.gov/clinical-quality-and-safety/safer-guides/)). Select the guides that touch the cell and turn their recommended practices into simulation cases.

Record findings in four columns: trigger, observed behavior, risk, owner. Fix the workflow and rerun the same case. A new slide deck is not a retest.

## Phase 2: one shift, shadow mode

Choose willing users and representative work. Keep the established process authoritative while the team compares the copilot output. Do not select only the cleanest cases.

For documentation, measure missing content, misplaced content, corrections, completion time, and the point of sign-off. For operations, measure wrong queues, staff takeover, unresolved exceptions, and final completion in the authoritative system. Track counts and examples. A single average can hide a rare event the clinical owner would never accept.

Hold a ten-minute review at shift end. The owner categorizes failures while the context is fresh. Product bugs, configuration errors, workflow gaps, source-data problems, and training misses need different responses.

## Phase 3: limited live pilot

Move the cell into normal work only after simulation and shadow-mode pass conditions are met. Keep the user set and case scope bounded. Publish the fallback at the workstation, not in a project folder nobody opens during an outage.

The person with pause authority should be reachable during every pilot shift. Staff need a plain instruction: stop the cell, use the fallback, preserve the evidence, and route the incident. They should not debug a clinical workflow while a queue grows.

Review performance daily at first. Weekly review is enough only after exception patterns stabilize and owners are closing them within the agreed time.

## Phase 4: expand across one axis

Expand to more users in the same department or the same workflow in another department. Do not widen both at once. One-axis expansion keeps the comparison legible.

Before expansion, require:

1. pass conditions met for the agreed review period;
2. no unresolved stop-rule event;
3. exception volume within staffed capacity;
4. downtime and rollback rehearsed;
5. contracts and interfaces valid for the wider scope;
6. the receiving department's clinical and operational owners named.

If the next department changes the clinical vocabulary, source systems, staffing, or record path, treat it as a new cell. Success in dermatology does not validate a surgery workflow. Success in an ambulatory note does not validate claims routing.

## The stop card

Print one card for each cell. It should name conditions that pause work immediately, conditions that trigger same-day review, and conditions that can wait for the weekly meeting.

Wrong-patient content, an unclear final status, an unauthorized disclosure, loss of the approved fallback, or an output sent beyond its review boundary belong in the first category. Repeated template mismatch may belong in the second. Cosmetic preferences can wait.

The clinical owner sets those categories. The vendor can help investigate; it does not decide the hospital's tolerance.

## The board after go-live

Keep the rollout board. It becomes the operating inventory: departments, workflows, data sources, reviewers, final systems, fallbacks, measures, and owners. Review it when a module changes, an interface moves, a vendor updates terms, or a department changes its process.

The floor plan should fill slowly. Bring Patient Square one proposed cell, including its fallback and worst exception. A useful implementation discussion starts inside that boundary.

---

## Hospital Copilot vs Standalone AI Scribe: Draw the Boundary
https://patientsquare.com/us/blog/hospital-copilot-vs-standalone-scribe/
Published 2026-09-24 · Tags: hospital-copilot, ai-medical-scribe, hospital-operations, procurement, clinical-documentation

Compare a standalone AI scribe with a hospital copilot by workflow ownership, record-system scope, review, exceptions, rollout, and operating evidence.

A hospital copilot may support several defined hospital workflows, while a standalone scribe is focused on encounter documentation. Choose between them by mapping the jobs in scope, record ownership, approvals, integrations, failure handling, and the operational evidence required for each workflow.

A microphone on a rounding cart does not tell you what the hospital bought. It could feed a standalone AI scribe that drafts one note. It could sit inside a wider hospital product with discharge, claims, bed, scheduling, and record-system scope. The hardware looks identical. The operating boundary does not.

That boundary is the buying decision.

> Takeaways:
> - Buy the scribe when the bounded problem is note drafting and the surrounding systems already work.
> - Evaluate a hospital copilot by named workflows, owners, review points, final systems, and fallbacks.
> - Decide whether the incumbent HIS/EHR stays authoritative before comparing features.
> - A demo passes only when the team can recover from a failure, not when one clean note appears.

## Two products can share the same first screen

A standalone scribe listens during an encounter and prepares a note draft. The clinician checks the history, examination, assessment, and plan, corrects the text, and authenticates the record. CMS says medical records should be complete, legible, and recorded during or soon after the encounter. Its signature guidance also addresses authentication of entries made by scribes, including AI technology ([CMS E/M guide](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/eval-mgmt-serv-guide-icn006764.pdf), [CMS signature guidance](https://www.cms.gov/files/document/mln905364-complying-medicare-signature-requirements.pdf)).

A hospital copilot may include that same drafting job, then place it beside other named hospital workflows. Patient Square lists Claims Management, AI Discharge Summary, Bed/IPD Management, and an AI Copilot EHR within Hospital Copilot. Those names define categories to investigate. They do not prove automatic filing, adjudication, diagnosis, coding, or an interface to an incumbent system.

The practical comparison starts one level below the product label.

| Buying question | Standalone AI scribe | Hospital copilot |
|---|---|---|
| Primary scope | Encounter documentation | Documentation plus named hospital workflows |
| Final decision | Clinician reviews and signs | Authorized owner still reviews each bounded output |
| Record-system choice | Usually keep the incumbent record system | Keep the incumbent or select a complete HIS/EHR path |
| Rollout unit | Clinician, specialty, or documentation team | Department plus workflow plus system boundary |
| Main failure mode | Bad or incomplete draft | Bad draft, broken handoff, wrong queue, or unclear system ownership |
| Evidence to request | Note quality, edit burden, consent, data handling | The same evidence plus interfaces, exceptions, reconciliation, downtime, and cutover |

## Start with the work, not the bundle

Write one sentence for every workflow under consideration. Keep the verb and the final owner visible.

"The hospitalist reviews and signs a discharge-summary draft in the designated record" is testable. "AI automates discharge" is not. The first sentence names the person, artifact, review, and destination. The second hides all four.

Use a boundary sheet like this during procurement:

| Workflow | Source | Draft or task | Reviewer | Final system | Failure route |
|---|---|---|---|---|---|
| Ambulatory visit | Encounter plus approved context | Note draft | Treating clinician | Designated EHR | Existing documentation process |
| Inpatient discharge | Approved inpatient record | Summary draft | Responsible clinician | Designated EHR | Existing discharge process |
| Claims work | Signed record plus approved billing input | Reviewable work item, if contracted | Coding or billing staff | Claims system | Existing work queue |
| Bed workflow | Authorized census and operational input | Bed/IPD task, if contracted | Bed or operations staff | Named operational system | Manual bed board or current queue |

If a vendor cannot fill a cell without vague nouns, the scope is not ready for a contract. If the hospital cannot name the fallback, the scope is not ready for a live pilot.

## The standalone scribe is often the right answer

A hospital does not need a platform project to fix every documentation problem. A standalone scribe can be the cleaner choice when five conditions hold:

1. the hospital wants note drafting, not a record-system change;
2. the current scheduling, discharge, claims, and bed workflows are staying in place;
3. clinicians can review drafts inside a defined operating process;
4. export and filing responsibilities are understood; and
5. privacy, retention, access, and incident terms are acceptable.

That is a narrow purchase. Narrow is useful. It shortens the pilot, reduces dependencies, and lets the clinical owner measure edit burden without pretending the rest of the hospital changed.

The limit should remain visible. A draft does not select a diagnosis, choose an ICD-10 code for billing, send a prescription, or complete a claim. Patient Square describes ICD-10 output as suggestions and prescription content as a draft. Authorized people decide what becomes part of care and the legal record.

## The copilot case begins at the handoff

A broader product earns its place when the hospital is buying several connected workflows or a new record-system path. Even then, connection is a hypothesis until the team sees evidence.

Follow one item across the floor. A discharge note begins with approved inpatient context. A clinician reviews it. The signed record may later support coding, billing, patient communication, and follow-up. Every handoff needs a source, an owner, a state, and a recovery rule. A bundle can reduce vendor boundaries, but it does not erase departmental boundaries.

NIST's AI Risk Management Framework organizes work around Govern, Map, Measure, and Manage ([NIST AI RMF](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10)). The labels fit a hospital evaluation well:

- Govern: name the clinical, operational, privacy, security, and technical owners.
- Map: document the workflow, affected people, data, dependencies, and failure consequences.
- Measure: define what the pilot will count and inspect.
- Manage: set stop rules, incident routes, change control, and expansion criteria.

This is not paperwork for its own sake. It keeps a polished demo from becoming an unnamed production dependency.

## Settle the record-system path early

Patient Square describes two Hospital Copilot deployments. A hospital may keep its incumbent HIS/EHR and use selected Patient Square workflows alongside it, or choose the complete Patient Square HIS/EHR as the system of record. The first path needs explicit handoffs and reconciliation. The second adds migration, cutover, downtime, archival, and staff-transition work.

Neither path is automatically smaller. An incumbent path can accumulate interface and duplicate-entry work. A replacement path can turn one product decision into a hospital-wide data and operations program.

Ask for a one-page answer to these questions before pricing the rollout:

- Which system is authoritative before, during, and after the pilot?
- Which data must move, and which historical data stays where it is?
- Is the proposed movement an export, a live interface, or manual entry?
- Who reconciles a partial failure or duplicate?
- How does the hospital return to the established process?
- What evidence proves that an output reached the intended record?

Patient Square states "EHR-ready export (PDF · HL7 · FHIR)." That is an export-format statement. It is not proof of a live endpoint, named EHR connection, automatic write-back, or conformance certification. Treat every live exchange as separate discovery until the parties document and test it.

## Put privacy terms beside the workflow

HHS says a cloud service provider that creates, receives, maintains, or transmits ePHI for a covered entity or business associate is generally a business associate, even when the information is encrypted and the provider lacks the key. The regulated organization needs an applicable business associate agreement and its own risk analysis ([HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)).

Do not review that obligation in a separate track from the workflow. For each cell, record what data enters, where it goes, whether audio is retained, which derived artifacts persist, who can access them, how access is logged, what subcontractors touch them, and how return or deletion works.

A short-lived pilot still handles real information if real patients are involved. Run the first failure tests with synthetic patients and approved test accounts.

## The demo should break on purpose

One accurate draft proves very little. Use a synthetic case and force the process through conditions the sales path would rather skip:

- two similar patient identities;
- a missing source field;
- a correction after the first draft;
- an unauthorized user;
- an unavailable destination;
- a network interruption;
- a staff handoff; and
- service restoration after queued work exists.

Observe the product and the people. Does the draft remain visibly unreviewed? Can staff tell which system is authoritative? Does a retry create a duplicate? Can the authorized user correct the record without hiding the earlier state? Does the fallback work while the queue grows?

The purchase is ready for a pilot when the hospital can answer those questions in writing. It is ready to expand only after the same workflow passes its stop rules across representative shifts.

## Patient Square's stated boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Hospital Copilot is demo-priced. It lists ten modules and supports either a complete Patient Square HIS/EHR or an incumbent-system path. Module names are the start of discovery, not permission to infer unlisted behavior. The [Hospital Copilot page](../../products/hospital-copilot/) carries the current scope.

Bring the boundary sheet to the call. Pick one hospital workflow for a demo, name its final system and fallback, and make the test fail once before anyone calls it ready.

---

## Running Speech-to-Text on Clinical Audio: The Production Test
https://patientsquare.com/us/blog/running-asr-on-clinical-audio/
Published 2026-09-24 · Tags: speech-to-text, clinical-audio, asr, healthtech-engineering, hipaa

Test clinical speech-to-text for latency, speakers, medical terms, interruptions, PHI handling, recovery, and note usefulness without hiding behind one accuracy score.

Clinical speech-to-text should be tested across latency, speakers, medical terms, interruptions, privacy controls, recovery, and downstream note usefulness. A single accuracy number cannot show whether an ASR pipeline is safe or reliable enough for the specific clinical workflow.

A clean five-minute recording can make almost any speech system look ready. Production clinical audio is less polite. A patient talks over the clinician. A caregiver answers from across the room. The otoscope wrapper crackles beside the microphone. Wi-Fi drops after the plan begins. Then the transcript assigns a denial to the wrong speaker.

That is the test set.

> Takeaways:
> - Score clinical errors by consequence and location, not only by total word count.
> - Treat diarization as a fallible label stream, not proof of identity.
> - Put capture, transient processing, storage, logs, support access, and deletion on one PHI map.
> - Test recovery after interruption before tuning punctuation.

## Define the output before choosing the recognizer

"Transcribe this visit" is too loose for an engineering requirement. State which artifact the system must produce and what happens next.

A live caption stream, a dictated paragraph, and an ambient encounter transcript have different timing and speaker needs. A note-drafting workflow may not need a verbatim transcript to be the final record at all. It needs enough faithful source material for a bounded draft that an authorized clinician reviews.

Write a contract with six fields:

| Field | Decision |
|---|---|
| Capture | Device, room, channel count, sample format, and start/stop control |
| Speakers | Expected roles, unknown speakers, overlap, interpreter, and caregiver cases |
| Timing | Streaming or batch, partial-result policy, and acceptable delay for the next step |
| Language | Supported languages, code-mixing, specialty terms, acronyms, numbers, and units |
| Output | Transcript, speaker turns, timestamps, confidence metadata, or a downstream draft |
| Failure | User-visible state, retry rule, local fallback, and what cannot be reconstructed |

This contract prevents a fast demo from winning the wrong contest. A vendor can return partial words in a few hundred milliseconds and still fail the visit because speaker turns drift or the recovered stream drops the assessment.

## Build the test set from rooms, not podcasts

Clinical audio varies by specialty, room, device, speaker, and task. Assemble consented or synthetic fixtures that cover the intended setting. Do not copy real patient recordings into an engineering folder because the benchmark feels internal.

Include at least these scenes:

- a calm two-person visit with ordinary turn-taking;
- overlapping speech during history-taking;
- a caregiver or interpreter joining midway;
- distant speech while the clinician examines the patient;
- medication names, allergies, abbreviations, dosages, dates, and units;
- explicit negation and later correction;
- a quiet stretch followed by a resumed conversation;
- a device switch or network interruption; and
- a specialty case with locally common terms.

Use a written fixture manifest. Record the audio conditions, intended speakers, required phrases, known ambiguities, and the workflow consequence of each mistake. A benchmark without that context becomes a leaderboard nobody can apply.

## Separate four kinds of failure

One overall word-error number compresses unlike problems. NIST's Speech Recognition Scoring Toolkit includes word-error scoring plus speaker-level and speaker-error reports, which is a useful reminder that the transcript and the speaker map are different evaluation surfaces ([NIST SCTK](https://github.com/usnistgov/SCTK)).

For a clinical workflow, keep four ledgers.

### Words and clinical meaning

Track omissions, substitutions, insertions, negation, drug names, measurements, laterality, dates, and units. Mark the location in the encounter. "No chest pain" losing its first word deserves a different review than a missing filler word.

Do not invent a universal weighting formula. Have clinical reviewers define categories before they see vendor results, then apply the same rubric to every candidate.

### Speakers and provenance

Google's Speech-to-Text documentation describes diarization as detecting distinct speakers and assigning speaker labels to words in a result ([Google Cloud diarization documentation](https://cloud.google.com/speech-to-text/docs/multiple-voices)). A label such as `speaker_2` is not a verified patient identity. The application still needs a way to handle unknown speakers, overlap, label swaps, and a third person entering the conversation.

Review whether a statement remains attached to the correct role after interruptions. A clinically correct sentence under the wrong speaker can be worse than a visible gap.

### Time and interaction

Measure time to first useful partial result, time to a stable segment, and time to the artifact the next step consumes. Record how often prior text changes. A user who edits a partial transcript while it is still being rewritten can create a race between the person and the model.

Latency budgets should follow the workflow. Live captions need a different budget from a note delivered after the encounter. Publish the chosen budget with the result.

### Recovery and operations

Pull the cable. Revoke a token. Send an expired credential. Fill a queue. Restart a worker while audio is arriving. Repeat a request after the client times out.

Then answer the questions that matter: what state is durable, what is lost, what can be retried, how a duplicate is detected, which alert fires, and what the user sees. A transcript that works until the first reconnect is a prototype.

## Put PHI on a data-flow map

Audio, partial transcripts, final transcripts, derived notes, error payloads, and support artifacts can all contain PHI. Draw them as separate objects. For each object, record the processor, storage location, encryption, access role, logging behavior, retention, deletion, backup, and incident route.

HHS says a cloud provider that creates, receives, maintains, or transmits ePHI for a covered entity or business associate is generally a business associate, even if the provider only stores encrypted data and does not hold the key. An applicable BAA and the regulated organization's own risk analysis are still required ([HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)).

NIST SP 800-66 Revision 2 maps HIPAA Security Rule obligations to cybersecurity resources and risk-management activities ([NIST SP 800-66r2](https://csrc.nist.gov/pubs/sp/800/66/r2/final)). Use it to pressure-test the whole path, not just the recognizer endpoint.

Logs deserve their own row. Developers often remove audio retention and then place raw transcript fragments inside request logs, exception trackers, tracing spans, or support tickets. The shortest retention policy in the main database does not repair those copies.

## Use an evidence packet, not a winner slide

The final comparison should let another team repeat the decision. Keep the following together:

1. fixture manifest and consent or synthetic-data basis;
2. audio capture settings and devices;
3. configuration and model identifiers available from the provider;
4. reference-transcript rules and adjudication notes;
5. error ledgers for words, speakers, timing, and recovery;
6. PHI data-flow and contract review;
7. runbooks for interruption, retry, and incident response; and
8. the clinical owner's sign-off on the intended use.

Do not crown a winner from one mean. Show distributions and bad cases. Preserve disputed examples with reviewer notes. If the team changes punctuation cleanup, vocabulary hints, or speaker settings, rerun the same fixture set and record the change.

## Keep recognition and note review separate

Speech recognition converts audio into words and timing information. A downstream system may structure those words into a note draft. The draft then needs clinical review. Mixing all three steps into one accuracy claim makes it impossible to locate a failure.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square does not publish an ASR accuracy percentage or disclose a speech-recognition vendor in this guide. Its stated product boundary is that audio is processed in memory and discarded once the note is drafted; the clinician reviews the note. That boundary is described on the [security page](../../security/). It does not turn a draft into a diagnostic decision or a signed record.

The useful engineering question is not "Which API transcribes best?" It is narrower: which tested pipeline produces reviewable evidence for this room, recovers from its failures, and keeps its PHI promises? Save the worst fixture. It will teach the team more than the clean demo ever did.

---

## ABDM Scan and Share for OPD Registration: How It Works
https://patientsquare.com/in/blog/abdm-scan-and-share-opd-registration-clinics/
Published 2026-09-23 · Tags: abdm, scan-and-share, opd, india

ABDM Scan and Share lets OPD patients scan a facility QR, share an ABHA profile, and receive a queue token without re-keying details. See the flow and clinic setup.

It is an NHA-run token workflow where an OPD patient scans a facility's QR code with an ABHA or PHR app, shares their ABHA profile and demographics, and receives a queue token. The clinic's registration system reads those details, so the front desk skips manual data entry for that patient.

ABDM Scan and Share is a QR-code registration flow for OPD counters. The patient scans a facility QR with an ABHA or PHR app, shares their ABHA profile and demographic details, and gets a queue token, all without dictating name, age, and phone number to a front-desk operator. The clinic's registration system reads those shared details straight into the record, so check-in for that patient becomes a scan instead of a conversation.

That is the whole idea in one paragraph. What follows is how the flow actually runs at the counter, what your clinic has to have in place for it to work, and where it genuinely helps versus where the marketing gets ahead of reality.

> **Key takeaways**
> - Scan and Share is a token workflow run by the NHA: patient scans a facility QR, shares ABHA + demographics, receives a queue token.
> - It cuts front-desk typing and the transcription errors that come with it, and it links the visit to the patient's ABHA at registration.
> - Your facility needs an HFR registration (an ABDM facility ID) and a Scan-and-Share-enabled counter QR from an ABDM-integrated registration system.
> - It only works for patients who have an ABHA and a smartphone app; everyone else still registers the normal way.
> - It handles registration and queueing, not the clinical visit. Your EMR and clinicians still do the rest.

_Source: NHA Scan and Share (Token) service; confirm current details on the ABDM portal._

## What Scan and Share actually does at the counter

Picture a busy OPD at 9am. The old flow: patient reaches the desk, the operator asks for name, father's or spouse's name, age, gender, mobile number, address, keys all of it into the registration screen, then hands over a token or slip. Repeat a few hundred times before lunch. Every entry is a chance to misspell a name or fat-finger a phone number.

Scan and Share replaces the keying step. Here is the sequence:

1. The clinic displays a facility QR code at or near the registration counter. This QR is tied to the facility's ABDM identity.
2. The patient opens an ABHA-enabled app on their phone, or a PHR app such as the ABHA app, and scans that QR.
3. The app asks the patient to share their ABHA profile. The patient consents and shares.
4. The clinic's registration system receives the ABHA number and demographic details, and issues a queue token back to the patient.

The patient walks away with a token. The operator never typed a character for that person. And because the registration is tied to the patient's ABHA, the visit is linked to their digital health identity from the start, which is the point of the whole exercise from the NHA's side. Confirm the exact steps and any app-specific behavior on the official ABDM Scan and Share page, because the service is run by the NHA and the details get updated.

## What your clinic needs to switch it on

Three things, and none of them are optional.

**An HFR registration.** Your facility must be registered in the ABDM Health Facility Registry so it has a facility ID. The QR the patient scans is bound to that identity. No HFR entry, no valid facility QR. If you have not done this yet, it is the first step, and it is separate from any individual doctor's registration in the Healthcare Professional Registry. We cover the provider side in the [HPR registration guide for doctors](../hpr-registration-guide-doctors/).

**A Scan-and-Share-enabled counter QR.** The QR is generated through an ABDM-integrated registration system or a supported app, not printed off a generic QR generator. It has to speak the token workflow to the ABDM gateway so the share actually lands in your registration screen.

**A registration system or HMS that supports the token workflow.** This is the part clinics underestimate. The QR is only half of it. Your software has to be able to receive the shared ABHA profile, populate the registration record, and issue the token. If your current registration desk runs on a spreadsheet or a system with no ABDM integration, Scan and Share is not something you can bolt on by yourself. Your HMS vendor has to build and certify it. When you ask them, make them name the ABDM milestone and say whether it is live in production or only in the sandbox, the same discipline we lay out in the [ABDM Milestone 2 explainer](../abdm-milestone-2-explained-clinics/).

Behind all three sits the ABHA-linking step itself, which is worth understanding on its own if you are new to it. The [ABHA linking clinic workflow](../abha-linking-clinic-workflow/) post walks through what happens when a patient's ABHA gets tied to a visit, and the [ABHA number vs ABHA address explainer](../abha-number-vs-abha-address-explained/) clears up the two identifiers patients routinely mix up.

## The benefits that hold up

Let's be specific rather than glowing.

**Faster registration for enrolled patients.** For a patient who arrives with an ABHA and a working app, check-in collapses from a minute or two of back-and-forth to a scan. On a heavy OPD day that adds up across the queue, and it takes pressure off the front desk during the morning rush.

**Fewer data-entry errors.** Demographics come from the patient's own ABHA profile, not from an operator hearing a name over counter noise and typing it in. That means fewer misspelled names, fewer wrong phone numbers, and fewer mismatched records to clean up later. Cleaner registration data is quietly one of the biggest wins here.

**ABHA linkage from the first touch.** Because registration runs off the ABHA, the visit is connected to the patient's digital health identity at check-in rather than as an afterthought. That linkage is what makes the downstream ABDM benefits possible, and it can matter financially: the NHA's Digital Health Incentive Scheme offers incentives for eligible ABHA-linked digital transactions above a monthly baseline, which we get into in the [ABDM incentives for doctors](../abdm-incentives-for-doctors/) post. Treat the specific scheme figures as NHA-defined and subject to revision; check the current terms before you bank on them.

## The honest limits

Scan and Share is useful, and it is also narrower than the pitch sometimes suggests.

**It needs an ABHA and a smartphone.** A patient without an ABHA, or an elderly patient who does not use a smartphone, or someone whose phone is out of battery, cannot use it. Those patients still register the old way. So your counter does not disappear; Scan and Share runs beside it. Plan for a mixed queue, not an all-QR one.

**Adoption varies a lot.** ABHA coverage and patient familiarity differ enormously across regions and patient mixes. A tech-forward urban clinic might see meaningful uptake; a rural OPD might see very little for a while. Do not size your front desk on the assumption that most patients will scan.

**It registers and queues. It does not treat.** This is the one clinics most often get wrong. Scan and Share gets the patient checked in with their ABHA linked and their details filled. The consultation, the clinical note, the prescription, the diagnostics, the follow-up, all of that still runs through your EMR and your clinicians. It is a front-desk convenience, not a clinical system. If you are separately weighing an ABDM-ready record system for the clinical side, the [ABDM-ready EMR software guide](../abdm-ready-emr-software-india/) is the better place to start.

**The QR and the software have to be right.** A patient can scan a QR and get nothing useful back if the facility is not properly registered or the receiving software does not handle the token flow. Test it end to end before you tell patients it works.

## Where Patient Square fits, plainly

Straight answer: Patient Square is not ABDM-certified, HFR-integrated, or Scan-and-Share-enabled today, and we will not imply otherwise. ABDM integration, including the Scan-and-Share flow, is on our roadmap, not shipped. The QR-registration conversation is one you have with your HMS or registration-software vendor, because that is the system that has to speak the token workflow at the desk.

What Patient Square does is separate from registration. Our AI scribe listens during the consult and drafts a structured clinical note, ICD-10 suggestions, and a prescription draft in about two minutes, in clean clinical English, for the clinician to review and sign. The audio is processed in memory and discarded once the note is drafted; nothing is filed or prescribed until a clinician signs it. So if Scan and Share is about getting the patient to the doctor faster, our part is about getting the note off the doctor's desk faster once the visit starts. The two solve different halves of the same busy-OPD problem. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If you want to see how the note comes together on a real visit, <a href="/in/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and run it on a clinic day. For the data-handling side, including how we approach records with DPDP Act obligations in mind, the [DPDP guide for clinics](../dpdp-act-clinics-guide/) and our [security page](../../security/) lay it out. And if the front-desk load is your real pain, the [AI receptionist for clinics](../ai-receptionist-clinic-india/) post covers the call and scheduling side of the same desk.

## The short version

ABDM Scan and Share turns OPD check-in into a QR scan for patients who have an ABHA and an app. The patient shares their profile, your system fills the record and issues a token, and nobody re-keys the basics. To offer it you need an HFR registration, a proper counter QR, and an ABDM-integrated registration system. It saves time and cuts errors for enrolled patients, it links the visit to their ABHA, and it does exactly one job: register and queue. The visit itself still belongs to your EMR and your clinicians, and if a vendor tells you their product does more than that, ask them to prove it.

---

## AI Scribe Clinical Documentation Audit Guide
https://patientsquare.com/us/blog/ai-scribe-clinical-documentation-audit/
Published 2026-09-23 · Tags: ai-scribe, clinical-documentation, quality-assurance, audit

Audit AI-scribe documentation with a stratified sample, error taxonomy, two-reviewer adjudication log and locally defined stop rules.

An AI-scribe audit should compare source-supported encounter information, signed notes, clinician edits, and workflow events across a stratified sample. Classify meaningful errors, record reviewer decisions, and use locally approved stop rules while clinicians continue reviewing every draft before signing.

An AI-scribe audit should compare the evidence from the encounter with the signed note, classify each meaningful difference and preserve reviewer disagreement. It should also inspect workflow failures such as missing drafts or wrong destinations. One score hides too much. A useful audit tells clinical leadership what failed, how often and who decided severity.

> **Key takeaways**
>
> - Audit signed notes and abandoned drafts, not vendor-selected examples.
> - Stratify by clinician, visit type and operating condition.
> - Separate clinically meaningful errors from style preferences.
> - Preserve two first-pass reviews before adjudication.

## Pull 20 notes, but call it a screen

Start with 20 consecutive eligible notes across the clinicians and visit types in scope. That number is deliberately practical. It is not a statistical threshold and it cannot establish a universal accuracy rate.

Do not take the 20 easiest notes. Build a small stratification grid before sampling:

| Dimension | Example strata | Why keep it visible? |
|---|---|---|
| Clinician | Each pilot clinician | Editing and dictation habits differ |
| Visit type | New, follow-up, procedure or local categories | Content and structure differ |
| Operating condition | Quiet, caregiver present, remote or other approved context | The source encounter differs |
| Draft outcome | Signed, heavily edited, abandoned, missing | Success-only samples hide workflow failure |
| Timing | Morning, late clinic, after-hours completion | Process conditions can change |

Use categories that fit the approved use case. Remove a stratum when it does not apply. Add one when the pilot's risk assessment names it.

The sample record should show the eligible population, selection method, exclusions and denominator. "We reviewed 20 notes" is not interpretable without those four items.

## Keep prospective review separate from the audit

Every AI-generated clinical note is a draft. The [APA's AI-scribe evaluation guidance](https://www.apa.org/topics/artificial-intelligence-machine-learning/evaluating-ai-scribes.html) tells clinicians to review and edit notes before signing and states that clinicians remain responsible for clinical decisions and documentation. A retrospective audit checks how the workflow performed. It does not replace the signer.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot &mdash; an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The [current US plan scope](../../pricing/) does not make those outputs final. ICD-10 items are suggestions, and a prescription output is a draft. The clinician decides what belongs in the signed record.

## Use an error taxonomy reviewers can apply

Give reviewers definitions and examples before they see the sample. Keep clinical meaning separate from prose polish.

| Class | Audit question | Record in the log |
|---|---|---|
| Omission | Is material supported information absent? | Missing concept, note section and potential consequence |
| Unsupported addition | Does the note state something not supported by the approved source? | Exact statement and conflicting evidence |
| Attribution | Is a statement assigned to the wrong person, time or condition? | Incorrect and correct attribution |
| Contradiction | Does one part conflict with another or with the source? | Both statements and reviewer interpretation |
| Specificity loss | Was a documented detail generalized in a way that changes meaning? | Source detail and signed wording |
| Structure or style | Is content hard to find without changing clinical meaning? | Local preference or usability issue |
| Workflow failure | Was the draft missing, duplicated, delayed or sent to the wrong destination? | Event, owner, response and outcome |

Severity belongs to the organization. A clinical quality lead should define the levels and examples for the use case. Do not import a vendor's labels without testing agreement among local reviewers.

## Preserve the edit trail

Use four artifacts when the approved workflow makes them available: the authorized encounter source, original AI draft, clinician edits and signed note. Follow local privacy, retention and access policy. Do not create an extra audio archive merely to run this audit.

The edit trail answers different questions. A corrected draft shows that prospective review worked, while the original still reveals a pattern the vendor or training plan may need to address. An unchanged signed note does not prove the source was captured correctly. Reviewers still compare it with the authorized evidence.

The [CMS Evaluation and Management compliance guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services) says medical records should support the services reported and be complete and legible. Use applicable payer and organizational rules for the actual audit. This article does not decide coding or billing compliance.

## Two reviews, then adjudication

Reviewer A and Reviewer B should complete their first pass independently. Hide the other's ratings until both are locked. Then compare results.

| Field | Reviewer A | Reviewer B | Adjudicated result |
|---|---|---|---|
| Error class | Entry | Entry | Final class |
| Evidence span | Entry | Entry | Cited source and note text |
| Severity | Entry | Entry | Final local severity |
| Rationale | Entry | Entry | Decision and policy reference |

The adjudicator can be one of the reviewers if local policy allows, but the original ratings should remain visible. A large disagreement rate may point to a vague rubric, missing clinical context or insufficient reviewer training. It is a reason to inspect the method before advertising a score.

A peer-reviewed [note-assessment study](https://pmc.ncbi.nlm.nih.gov/articles/PMC12586549/) used a modified PDQI-9 framework and two blinded specialty reviewers for each note. That research can inform local rubric design. It is not a regulator's approval of a product, and the instrument should not be presented as the only acceptable audit method.

## Report counts before percentages

For each class, report the number of notes reviewed, number with the finding and number of findings. One note can contain several findings, so those denominators answer different questions.

Also report:

- signed, abandoned and missing drafts;
- notes with a material clinician correction;
- cases sent to adjudication;
- unresolved cases;
- workflow incidents by type;
- excluded notes and reasons.

Do not compress everything into "accuracy." An omission, a wrong attribution and a comma change should not receive identical weight. We think a one-number vendor leaderboard is the wrong output for a local safety review.

## Write the stop rule before looking at results

Clinical leadership, privacy, security and operations should name the events that pause use. A wrong-patient association, a serious unsupported clinical statement, repeated material omission, loss of review or failure of the fallback may be candidate triggers. The organization sets the actual threshold.

The audit plan should state who receives the report, who can stop the pilot, which workflow resumes and what evidence is required to restart. Without that route, reviewers can discover a serious pattern and still wait for the next monthly meeting.

The [healthcare AI governance charter](../healthcare-ai-governance-committee-charter/) provides a decision record for those owners. The [AI-scribe implementation guide](../ai-scribe-implementation-small-clinic/) covers rollout mechanics outside the audit.

## What a passing audit means

A pass means the sampled use case met the organization's stated criteria for that period. It does not prove perfection, validate every specialty or authorize a new workflow. Record the exact scope and the next review trigger.

An organization may decide that a simpler documentation tool is a better fit when it cannot staff independent review and adjudication. That is an honest operating choice. For a team ready to test its own rubric, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>.

## Frequently asked questions

### Should the vendor choose the audit sample?

No. The organization should define the eligible population and selection method. A vendor may help export permitted artifacts, but it should not remove hard cases or substitute hand-picked notes. Include abandoned and missing drafts so the audit measures the workflow rather than only the outputs that reached signature.

### Can one clinician review their own notes?

Self-review can provide operational feedback, but it does not give an independent quality check. For a formal audit, add a second qualified reviewer and preserve both initial ratings. The organization should define reviewer qualifications, access, conflicts and adjudication authority for the clinical scope being examined.

### Is edit distance a clinical quality measure?

Not by itself. A long stylistic rewrite may leave clinical meaning unchanged, while one short insertion can correct a material omission. Track edit burden as an operational measure and classify clinical meaning separately. Reviewers need the source evidence and signed note, not only a character-difference score.

### Can audit data be reused for model training?

Do not assume so. Training is a separate purpose and data flow that needs its own contractual, privacy, security and governance review. The audit protocol should state who can access each artifact, how long it is kept and what happens at deletion. Keep the audit approval bounded to the stated purpose.

### How often should the audit repeat?

Set a scheduled cadence and event-based triggers. Repeat after a material model, workflow, population, data-use or destination change and after serious findings. Stable lower-risk use may justify less frequent sampling. The governance record should name the next trigger instead of relying on memory.

---

## AI Scribe for Oncology Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-oncology-clinics-india/
Published 2026-09-23 · Tags: ai-scribe, oncology, india, specialty

How an ambient AI scribe handles oncology in India: chemo cycle notes, staging discussions, toxicity review, and bilingual consults as clean English drafts.

It drafts the regimen you dictate. Say the protocol, cycle number, and doses aloud, and the scribe writes them into the note in your words. It does not calculate body surface area, compute doses, or verify the protocol. Chemo dosing stays entirely your call. The drafted regimen is text you review, never a prescription the tool sends anywhere.

An AI scribe fits an Indian oncology OPD if it can keep up with a long, longitudinal narrative, a staging discussion, a chemo cycle note, a toxicity review, spoken across Hindi and English, and hand it back as a clean English draft. It does not stage the cancer, calculate a dose, or remember last cycle. You dictate all of that. What it removes is the writing you never finish on a day-care day that runs to 7pm.

> **Key takeaways**
>
> - The scribe drafts what you dictate. Say the regimen, cycle, and doses and the note reflects them. It does not compute BSA or verify the protocol.
> - It captures Hindi, English, and the mid-sentence mix; the note always comes back in clean clinical English.
> - It has no memory of prior visits. Cycle number, prior lines, and response trend must be spoken to appear.
> - ICD-10 suggestions like C50.911 or C34.90 appear next to the draft. You confirm them. It does not stage or assign TNM.
> - Visit audio is processed in memory and discarded at draft; nothing is stored, in line with DPDP Act 2023 expectations. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

_Pricing is ex-GST; add 18% GST for the all-in figure._

## Why oncology notes are the hardest to write on a busy day

An oncology consult is rarely one thing. A single visit can carry an interval history since the last cycle, a symptom and toxicity review, a performance-status note, an imaging or pathology summary the patient brought, a decision on whether cycle four goes ahead, a dose adjustment, and a plan that reaches to the next scan. Each piece is its own paragraph of dictation. Stack that against a day-care unit clearing thirty-plus chemo patients and a medical oncology OPD running behind by mid-morning, and the note is what gives.

The longitudinal story is what makes oncology different. In a one-off consult a thin note is survivable. In cancer care the record is the treatment history: which line, which cycle, what the last response was, what toxicity showed up and how you managed it. Six months on, that trail is the clinical decision. A one-line "continue chemo" entry loses exactly the information the next visit depends on.

The medico-legal weight is heavier here too. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. In oncology, where consent for a regimen, a discussion of prognosis, and a documented toxicity are all part of the standard of care, the note is not paperwork. It is evidence that the conversation happened. Thin notes in a specialty this consequential are an exposure, not just an inconvenience.

Better clinic software does not solve this. A faster billing screen does not write the tumour-board summary. The constraint is time at the point of care, and there is never enough of it on a full day-care list.

## How the scribe fits an oncology visit

You start a session when the patient sits down and run the consult the way you always do. As you take the interval history and review toxicity, you speak your findings the way you would dictate them: "cycle three of six, FOLFOX, no significant neuropathy, grade one nausea managed with ondansetron, ECOG one, weight stable." The scribe captures it in English, in Hindi, or in the mix of both that a real consult actually uses.

When the patient hands you a recent scan report and you read the relevant line into the record, dictate it. "CT chest shows partial response, target lesions down about thirty percent." That is your read. The scribe writes it as you said it. It is not looking at the images, measuring anything, or deciding the response category. You did that. The scribe is a stenographer for the note, not a reader of the study.

Here is the canonical version of that flow. AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In oncology terms, after the patient leaves you stop the session, and about two minutes later there is a draft: interval history, toxicity review, exam, your imaging and pathology summaries, assessment, and the plan for this cycle. You read it, correct anything wrong, and sign.

The AI Medical Scribe is the ambient module inside Practice Copilot, so it runs alongside whatever oncology records system you already use. There is no HL7, FHIR, or EHR integration involved. You copy or export the finished note into your chart. Three India-specific points matter: the note always comes back in clean clinical English no matter how you dictated it, the audio is never stored, and the regimen output is a draft you review, never something the tool transmits to a pharmacy. Our [multi-specialty scribe guide](../ai-scribe-for-multi-specialty-clinics-india/) covers how the same tool adapts across departments if oncology shares a clinic with other specialties. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## What you say versus what the scribe drafts

The honest way to explain the ceiling is element by element. For every part of an oncology note, you dictate the clinical content and the scribe drafts the text. Nothing in the right column is a calculation, an interpretation, or a check the tool performs on its own.

| Note element | What you say | What the scribe drafts |
|---|---|---|
| Staging | "Clinical stage cT3 N1 M0, confirmed on biopsy" | The stage in your words, verbatim, into the assessment |
| Chemo regimen | "Cycle 4 of 6, FOLFOX, oxaliplatin and 5-FU per protocol" | A regimen draft with the cycle and agents you dictated |
| Dose | "Reduced 5-FU to 80 percent for last cycle's mucositis" | The dose statement as spoken, not a recalculated figure |
| Toxicity | "Grade 2 peripheral neuropathy, oxaliplatin held this cycle" | The toxicity and your management, in the note |
| Response | "Partial response on latest CT, target lesions smaller" | Your stated response read, not a derived category |
| Supportive care | "Started G-CSF, antiemetics stepped up, dietician referral" | The supportive-care plan you dictated |

_The scribe drafts the left column into clean English. It does not compute doses, calculate body surface area, screen for interactions, or verify the protocol. Chemo dosing and protocol verification stay entirely yours._

That distinction is the whole point. If you want the scribe to work out a carboplatin AUC dose or flag an interaction, it will not, and it should not pretend to. Dose and safety are the oncologist's decision. The scribe's job is to stop you retyping the note at 8pm, not to make clinical calls.

## ICD-10 suggestions you confirm, never staging

Alongside the draft, the scribe offers ICD-10 code suggestions pulled from what you dictated. They sit next to the note as suggestions, not entries. You confirm, change, or reject each one, and nothing is auto-coded or posted as a charge.

| What you dictate | ICD-10 suggestion (for you to confirm) |
|---|---|
| Breast cancer, female breast, unspecified site | C50.911 |
| Lung cancer, unspecified part of bronchus or lung | C34.90 |
| Colon cancer, unspecified site | C18.9 |
| Non-Hodgkin lymphoma, unspecified | C85.90 |
| Chronic myeloid leukaemia, BCR/ABL-positive | C92.11 |

_Suggestions are a starting point for your judgement, not a coding action. The scribe does not stage cancers, assign TNM, or select a code on its own. You confirm every one._

Read that carefully, because it is a common misunderstanding. An ICD-10 code is a diagnosis label, not a stage. The scribe suggesting C50.911 tells you it heard "breast cancer," not that it worked out the T, N, and M. Staging is a clinical judgement you make from pathology, imaging, and exam, and you dictate it. The scribe writes it down. It does not derive it.

## No memory, so dictate the trend every time

This is the limit that catches oncologists off guard, so we will be blunt about it. The scribe has no memory of prior visits. It does not know this is cycle four, that the patient was on FOLFIRI first line, or that the last scan showed progression. If you do not say those things in this consult, they will not be in this note.

In most specialties that matters less. In oncology it shapes how you dictate. The value of the record is the trend, so the trend has to be spoken. "Second line since March, cycle four of FOLFOX, previous FOLFIRI stopped for progression, last CT showed partial response" is the kind of sentence that makes the note useful six months later. Say it, and the scribe drafts it. Skip it, and you get a snapshot with no history.

We think this is the honest framing rather than overselling a "longitudinal AI." The scribe is a fast, accurate note-taker for the visit in front of it. It is not a patient timeline that remembers your panel. If you dictate the story each time, it captures the story each time. Our [medico-legal documentation guide](../ai-scribe-medico-legal-documentation-india/) covers why that spoken trail matters when a record is later reviewed.

## Security, DPDP, and the medico-legal record

Oncology consults are about as sensitive as clinical conversations get: a diagnosis, a prognosis, family history, and consent for treatment, often with relatives in the room. The data posture has to match that.

The audio is processed in memory and discarded once the note drafts. There is no recording sitting on a server afterward, which is the cleaner stance under the Digital Personal Data Protection Act, 2023. Notes are encrypted in transit and at rest with TLS 1.2+ and AES-256. On certifications, we will be exact rather than aspirational: a SOC 2 audit is underway and not yet certified, and the product is DPDP-aligned in its handling, not DPDP-certified. We do not claim a certificate we do not hold. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On ABDM, the same honesty applies, because Indian oncology practices are right to ask. Live ABDM record linking is on our roadmap, not shipped, and we are not ABDM-certified. If you need to link a cancer patient's records to their ABHA number today, that is a real requirement and the honest pointer is a platform that already does it. eka.care, for example, offers live ABHA linkage now, and if that is your dealbreaker, they are the better fit for that specific need. We would rather tell you that than pretend a roadmap item is a shipped feature. Our [Hindi and Indian-languages guide](../ai-scribe-hindi-indian-languages/) covers the language handling if bilingual capture is the higher priority for your clinic.

And the note stays a draft until you sign it. Legal responsibility for the chart stays with the signing oncologist, exactly as it should in a specialty where the documentation is part of the standard of care.

## Where the fit stands or falls

Being straight about when this is the wrong tool matters more than a feature list. The scribe fits a busy day-care or medical oncology OPD where the real problem is that notes pile up and get finished at night. It drafts the long narrative, captures the bilingual consult, and hands back clean English about two minutes after the visit. For a high-volume list, getting a minute or two back per note and finishing before you leave is where it earns its place. Our [scribe cost math for an Indian solo doctor](../ai-scribe-cost-for-solo-doctor-india/) has a framework if you want to run your own numbers.

It is the wrong tool if you expected clinical support. It does not compute chemo doses, calculate BSA, screen for drug interactions, verify a protocol, stage the cancer, or remember prior cycles. Those are yours, and they should be. If your bottleneck is dosing safety or a longitudinal timeline rather than the writing itself, an ambient scribe does not solve that problem, and you should not buy it expecting it to.

For the honest verdict: this is a documentation aid, not a clinical-decision tool. It fits oncologists who dictate their reads and drown in after-hours charting. It does not fit anyone hoping the software will make the treatment call. The [best AI scribe for India](../best-ai-scribe-for-india-2026/) roundup compares the India-facing options if you are shortlisting more than one, and our [NMC record-keeping explainer](../nmc-record-keeping-ai-scribe/) covers what the regulations actually expect from a note.

The way to test it is on your own day-care list during the 7-day free trial after the workspace is ready. Dictate a real cycle note with a dose adjustment and a toxicity, in your usual Hindi-English mix, and check whether the draft comes back in oncology English or flattens it. Then run it on your heaviest half-day and see whether the notes stay clean and separate. That is the only accuracy figure worth trusting.

If you want to see draft quality against your own consults before committing anything, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical complex case, or check what each plan includes on the [pricing page](../../pricing/) first. Entry pricing is ₹1,599 per clinician per month on annual billing, ex-GST; Copilot is ₹2,399 and Autopilot ₹3,999. Add 18% GST and the entry invoice is about ₹1,887 a month. For an oncology unit clearing a full list, that is a small test against a real problem.

---

## How to Switch to an AI Practice Copilot in 90 Days
https://patientsquare.com/us/blog/how-to-switch-to-ai-practice-copilot/
Published 2026-09-23 · Tags: practice-copilot, clinical-ai-implementation, change-management, medical-practice, ai-governance

A 90-day rollout plan for moving a medical practice to an AI copilot, with owners, stop rules, staged workflows, and a clean path back.

A 90-day practice-copilot rollout is a planning frame, not a promise: start with one measurable workflow and expand only after testing, training, contract review, and data validation are complete. Keep explicit owners, stop rules, and a way back to the prior workflow.

Day 47 is when rollout plans get honest. The enthusiastic physician is still using the new workflow. Two colleagues have quietly returned to the old one. The front desk has a workaround nobody wrote down, and the project lead is still calling the launch a pilot.

A 90-day plan should make that drift visible early. It needs one owner, one workflow at a time, written stop rules, and a way back that staff can use without improvising. Ninety days is a planning box, not a vendor promise. Extend it when the evidence is incomplete.

> **Key takeaways**
>
> - Baseline the old workflow before touching the new one.
> - Pilot one bounded job with willing users and representative cases.
> - Add modules only after the current workflow meets its pass conditions.
> - Rehearse downtime and rollback before broad use.

## Days 1-15: write the operating brief

Name the sponsor and the working owner. The sponsor can approve budget and remove blockers. The working owner watches the queue, answers staff, records exceptions, and pauses the pilot when a stop rule is met. Those are separate jobs even when one person holds both.

Choose the first workflow. "Implement AI" is not a workflow. "Prepare a reviewable draft note for routine follow-up visits, then complete the signed note in the designated EHR" is.

Record the old numbers for at least one representative week:

- notes completed before the clinician leaves;
- correction or catch-up minutes;
- unsigned or abandoned notes;
- transfers between systems;
- support requests and downtime workarounds.

NIST's AI Risk Management Framework organizes AI risk work around Govern, Map, Measure, and Manage ([NIST AI RMF](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10)). The companion [Playbook](https://airc.nist.gov/airmf-resources/playbook/) offers suggested actions rather than a checklist that guarantees compliance. For a small practice, the useful translation is plain: assign authority, map the workflow, choose evidence, and decide how the team responds.

## Days 16-30: settle contracts, access, and data

No real patient data yet.

Confirm the business associate agreement and the product's role in the workflow. Document what data enters, where it is processed, what is retained, who can access it, and how the practice obtains or deletes it. The HHS Office for Civil Rights describes risk analysis as foundational to Security Rule compliance and expects an accurate assessment of risks to electronic protected health information ([HHS risk-analysis guidance](https://www.hhs.gov/hipaa/for-professionals/security/guidance/guidance-risk-analysis/index.html)).

Build roles with least access needed for the pilot. Test joiners, leavers, password recovery, and an account with the wrong role. Verify support escalation and incident contacts. If the product will work beside an EHR, watch the handoff with fictional data. If it will replace the EHR, do not squeeze migration into a documentation pilot.

Write stop rules before optimism gets involved. Examples:

- wrong-patient content or identity mismatch;
- draft and final status cannot be distinguished;
- a required field repeatedly disappears;
- an output reaches a patient or external party without the intended approval;
- the team cannot recover the workflow during downtime;
- access cannot be removed promptly.

A stop rule is not a declaration that the product is unsafe forever. It is permission to pause while evidence is still cheap.

## Days 31-45: run a shadow pilot

Select two or three willing clinicians and a narrow set of visit types. Keep the established workflow authoritative. Use the copilot output as a comparison draft until the team understands its failure patterns.

Include ordinary and awkward cases: a long history, background noise, a late correction, two similar names, and a visit whose template does not fit. Track missing information and invented or misplaced content. Do not average those differences into one satisfaction score.

The AMA's 2025 principles call for physician consent, final review, and a clear protocol when AI-generated content enters the medical record ([AMA principles](https://www.ama-assn.org/system/files/ama-ai-principles.pdf)). Translate that into the screen and the policy: users see that the note is a draft, they know what to check, and the sign-off event is recorded.

At day 45, decide. Continue only if the owner can explain the common exceptions and the measured workflow is at least as controllable as the baseline.

## Days 46-60: make the first workflow real

Move the bounded workflow from shadow mode into ordinary use for the pilot group. Keep daily office hours short and predictable. Ten minutes at the end of clinic can surface more than a weekly survey because the failed note is still fresh.

Review exceptions by type, not anecdote. Separate transcription errors, missing context, template mismatch, wrong destination, user confusion, and product outage. Each category needs a different remedy.

The ASTP/ONC SAFER Guides address EHR areas such as patient identification, system configuration, result follow-up, and contingency planning ([SAFER Guides](https://healthit.gov/clinical-quality-and-safety/safer-guides/)). Use the relevant guide to challenge the new route. An AI feature should not weaken a safety practice that already exists in the record system.

## Days 61-75: add one adjacent module

Only add a second module if the first workflow has met its pass conditions for two consecutive review periods and the exception owner is not overwhelmed.

Pick an adjacent job with a visible boundary. Scheduling may be a better second step than patient messaging because staff can test availability, double booking, cancellations, and takeover without creating clinical communication. Your order may differ. The rule is one controlled change at a time.

Patient Square's [Practice Copilot](../../products/practice-copilot/) lists documentation, scheduling, messaging, EHR, receptionist, follow-up, and billing-related modules across the product and plan set. Treat each module as a separate rollout row. A bundle is not one workflow just because it has one invoice.

## Days 76-90: rehearse failure and choose the steady state

Turn off the route in a planned exercise. How do staff document? Where do messages wait? Who restores access? How does delayed work return without duplication?

Then test rollback. Export pilot records, remove a user, disable the new module, and return to the established path. A reversible pilot creates negotiating room. A pilot that cannot unwind has already made the purchasing decision.

At day 90, write one page:

| Decision | Evidence required |
|---|---|
| Expand | Pass conditions met, exception load staffed, recovery rehearsed |
| Hold | Workflow useful but unresolved fit, training, or contract work remains |
| Roll back | Stop rule persists, control is weaker, or benefit does not cover the operating cost |

Do not call "hold" a quiet expansion. Freeze the user group and scope until the open items close.

## The weekly project note

Keep the project honest with six lines:

1. workflow in scope;
2. users active;
3. pass measure and current result;
4. top exception by count;
5. open risk and owner;
6. next decision date.

The note is intentionally dull. It prevents a good demo, one vocal champion, or a large feature list from substituting for operating evidence.

If Patient Square is on the shortlist, book a rollout-mapping session. Bring the six-line note and the ugliest exception from the current workflow. That is enough to plan day one.

---

## What Is a Hospital Copilot? An Operating Model, Not One More Bot
https://patientsquare.com/us/blog/what-is-hospital-copilot/
Published 2026-09-23 · Tags: hospital-copilot, clinical-ai, hospital-operations, procurement, workflow

A hospital copilot connects bounded documentation and operations workflows while clinicians and staff retain decisions, review, records, and exceptions.

Hospital copilot software supports defined hospital workflows while leaving a human reviewer and authoritative record system in control. Evaluate each module by its source data, output, approval step, failure owner, and deployment boundary rather than the copilot label alone.

A hospital does not have one workflow. It has queues that collide: rounds, orders, notes, coding questions, discharge work, bed moves, patient calls, and claims. Adding a chatbot to the toolbar leaves those collisions intact.

A hospital copilot is useful only when it gives bounded work a named owner, a review point, a system-of-record destination, and a recovery path.

> Takeaways:
> - A hospital copilot is an operating model across selected workflows, not an autonomous clinician.
> - Start with one patient journey and make every handoff visible.
> - Keep clinical judgment, coding acceptance, prescriptions, and signatures with authorized staff.
> - Prove access, failure recovery, and record ownership before expanding departments.

## Define the copilot by its boundaries

The word "copilot" has become elastic. For a hospital buyer, a defensible definition has four parts:

1. Inputs: the conversations, records, events, and staff actions the workflow can use.
2. Outputs: drafts, suggestions, messages, queues, or operational updates it can prepare.
3. Human authority: the person who reviews, decides, corrects, signs, or escalates.
4. Record boundary: the system that remains authoritative after the task is done.

If a vendor cannot name all four for a module, the label is doing the work.

This boundary matters most for clinical output. CMS says medical records should document the reason for an encounter, relevant history and findings, assessment or diagnosis, rationale for ordered services, plan of care, date, and observer identity, and should support the codes reported ([CMS E/M guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)). A copilot may prepare a draft. The authorized clinician still owns its clinical truth and signature.

## Group the work into three layers

A module list is hard to evaluate. Put the hospital's proposed scope into three working layers instead.

### Encounter layer

This is where conversations become documentation. It may include an AI medical scribe, ICD-10 suggestions, and prescription drafts. The test is not whether text appears quickly. Check whether the clinician can trace, correct, and sign the right note without a silent filing step.

### Flow layer

Scheduling, patient communication, follow-up, discharge work, and bed movement sit here. Each item needs a queue owner and an exception path. A discharge-summary draft has no operational value if the right clinician never sees it or the family waits while two systems disagree.

### Financial and record layer

Claims preparation, the hospital information system, and record handoffs belong here. Treat clean documentation as an input, not a promise that every claim will be paid. Coding, billing, and payer decisions remain governed by their own people and rules.

Patient Square's US [Hospital Copilot](../../products/hospital-copilot/) page lists ten modules: AI Medical Scribe, AI Receptionist, eRx, AI Follow-ups, WhatsApp, Scheduling, AI Copilot EHR, Claims Management, AI Discharge Summary, and Bed/IPD Management. That is Patient Square's product scope, not a universal definition every vendor must share.

## Map one patient journey end to end

Pick an ordinary journey with enough friction to be honest. For example: an emergency admission, inpatient stay, consultant note, discharge, follow-up, and claim packet.

Build one line for every handoff.

| Moment | Copilot output | Human owner | Authoritative destination | Failure route |
|---|---|---|---|---|
| Admission | Draft intake or queue item | Admitting staff | HIS or EHR | Manual intake |
| Rounds | Draft progress note | Treating clinician | Signed chart | Existing note workflow |
| Medication | Prescription draft | Authorized prescriber | Approved eRx path | Current prescribing route |
| Discharge | Summary draft and task | Discharging clinician/team | Signed record | Standard discharge process |
| Bed movement | Operational status | Bed-management staff | Approved census board | Downtime board |
| Claim | Documentation packet or work item | Coding/RCM team | Billing system | Current work queue |

The fourth column prevents a common mistake: letting the newest product quietly become a second system of record.

## Choose incumbent or greenfield deliberately

A hospital can keep its existing HIS or EHR and add selected workflows around it. It can also choose a new platform for a greenfield site. Those are different projects.

For an incumbent deployment, list every interface or manual handoff, who monitors it, and what happens when it fails. Do not accept "integrates" without a named route and acceptance test. Patient Square's product page says an existing HIS or EHR can remain the system of record while selected workflows are defined during discovery; it does not promise an automatic connector to every named system ([Patient Square Hospital Copilot](../../products/hospital-copilot/)).

For greenfield deployment, the hospital must prove the record, identity, downtime, migration, reporting, and operational workflows that the new system will own. A clean demo chart is not a cutover plan.

## Give each risk a person

HHS says regulated entities must perform an accurate and thorough risk analysis for ePHI and implement reasonable and appropriate administrative, physical, and technical safeguards. The Security Rule includes role-appropriate access, activity review, authentication, audit controls, integrity, and transmission security ([HHS Security Rule summary](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html)).

Translate that into named hospital ownership:

- clinical leadership owns review standards and stop rules;
- HIM owns the signed-record boundary and correction path;
- privacy and security own the data map, access model, vendor chain, and incident route;
- IT owns interfaces, monitoring, downtime, and recovery;
- operations owns queues, staffing, and escalation;
- finance owns the local baseline, contract, and measured business case.

The names matter. "The committee" cannot fix a failed discharge handoff at 4:45 p.m.

## Use adoption evidence without borrowing outcomes

The Peterson Health Technology Institute's 2025 report organizes AI adoption around adoption decisions, technical implementation, workforce use, and financial impact. It reports early ambient-scribe experience while warning that financial effects were still unclear ([PHTI, 2025](https://www.phti.org/wp-content/uploads/2025/03/PHTI-Adoption-of-AI-in-Healthcare-Delivery-Systems-Early-Applications-Impacts.pdf)).

That is a useful discipline for a hospital copilot pilot. Measure local outcomes instead of copying a vendor percentage.

Before launch, capture the current turnaround and rework for the chosen journey. During the pilot, record completed drafts, clinician edits, failed handoffs, support work, queue age, downtime events, and any work retired or added. Keep quality and safety measures beside speed and cost.

## Run a failure-first demonstration

Ask the vendor to complete the mapped journey with synthetic data. Then interrupt it.

Remove a user's access. Stop an interface. Put two patients with similar names in the queue. Have the patient decline ambient capture. Correct a signed-document error through the approved process. Request the activity record and run the downtime route.

Score only what the hospital sees. A roadmap item is zero. A canned slide is one. A synthetic workflow completed by your staff is two. The same workflow recovered after a forced failure is three.

## Where Patient Square fits

Patient Square sells Hospital Copilot separately from its per-clinician Practice Copilot plans. Hospital pricing is custom, per bed or per doctor, according to the published [US pricing page](../../pricing/). The product page offers an incumbent-system path and a complete Patient Square hospital platform for greenfield deployments.

Its clinical outputs remain bounded: SOAP notes and discharge summaries are drafts for review, ICD-10 output is a suggestion, and prescription content is a draft for an authorized clinician to sign. Patient Square says audio is processed without retained recordings and states that SOC 2 Type II work is in progress, not complete ([Patient Square security](../../security/)).

Start with one patient journey. If nobody can point to the owner, destination, and failure route for each handoff, the hospital does not have a copilot plan yet.

<a href="/us/products/hospital-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a>

---

## AI Copilot for Specialty Clinics: Test the Workflow, Not the Label
https://patientsquare.com/us/blog/ai-copilot-for-specialty-clinics/
Published 2026-09-22 · Tags: practice-copilot, specialty-clinics, workflow, software-evaluation, clinical-documentation

Use a patient-day replay to test an AI practice copilot for specialty clinics across documentation, scheduling, handoff, review, and exceptions.

An AI copilot is useful for a specialty clinic only when it supports the clinic's actual patient-day workflow with clinician review intact. Test documentation, scheduling, handoffs, exceptions, and record delivery using realistic cases before treating a specialty template or product label as evidence of fit.

Copying a cardiology template into a dermatology account takes seconds. It proves almost nothing. Specialty fit shows up later: in the detail a clinician must correct, the procedure that has nowhere to land, the follow-up instruction divorced from the note, or the handoff that works for routine visits and breaks on the odd one.

An AI copilot for specialty clinics deserves a patient-day replay, not a feature checklist.

> Takeaways:
> - Start with the specialty's real work sequence, then ask software to follow it.
> - Score observable outputs: draft, handoff, exception, access event, and recovery.
> - Keep assessment, diagnosis, coding, prescribing, and signature with the clinician.
> - Treat configuration and custom development as different promises with different costs.

## Build a patient-day replay

Choose five synthetic encounters from the clinic's ordinary week. Remove every real patient identifier. Keep the awkward parts.

One encounter should be routine. One should contain a procedure or a specialty-specific measurement. Add a patient who brings an outside result, a schedule disruption, and a visit where the patient declines ambient capture. The goal is not to trap a vendor. It is to see the workflow you will actually own.

Give every vendor the same replay and score the same artifacts.

| Replay moment | Artifact to inspect | Failure worth recording |
|---|---|---|
| Booking and intake | Visit type, forms, and queue position | Wrong template or missing context |
| Conversation | Draft sections and source trace | Unsupported detail or flattened uncertainty |
| Procedure or test | Structured field and narrative | Data trapped in prose or invented value |
| Review | Edit path and clinician ownership | Suggestion presented as a final decision |
| Record handoff | Signed output in the chosen route | Missing section, duplicate work, or wrong patient |
| Follow-up | Task, message, or next appointment | Action detached from the signed plan |

That order makes the evaluation specific to the clinic without pretending that one specialty workflow is universal.

## Separate note shape from clinical ownership

A useful specialty draft can carry the reason for the encounter, relevant history and findings, an assessment, the rationale for services, and the care plan. CMS lists those elements in its current medical-record guidance and says documentation should support the codes reported on a claim ([CMS E/M guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)). CMS also notes that documentation varies with the service, setting, and patient status.

That is a record requirement, not permission for software to make the clinical decision. In this test:

- the assessment and plan belong to the clinician;
- ICD-10 output is a suggestion to accept, change, or reject;
- a prescription is a draft until the authorized clinician reviews and signs;
- the note does not enter the record until the clinic's review step is complete.

The AAFP's AI-scribe guidance likewise advises clinicians to review generated notes before signing and recommends informing staff and patients and obtaining patient consent before use ([AAFP, 2025](https://www.aafp.org/fpm/2025/0300/virtual-scribe-tips)). Put those actions into the replay rather than a policy document nobody opens during clinic.

## Ask what changes by specialty

Do not ask, "Do you support cardiology?" Ask what the software does when the work changes.

For a longitudinal specialty, test comparison with the last visit without inventing a trend. For a procedure-heavy clinic, test how the procedure name, laterality, site, indication, findings, and follow-up reach the draft. For image-heavy work, identify which image system remains authoritative and make sure the note does not claim to interpret an image it never received.

These are evaluation cases, not claims that every specialty requires the same fields. Let the clinic's physicians select the details before the demo.

Then make one case deliberately ambiguous. A good test preserves the clinician's uncertainty instead of polishing it into a confident diagnosis.

## Draw the configuration boundary

"Customizable" can mean a user changes a heading. It can also mean a six-week engineering project. Put each requested change into one of four buckets:

1. User setting: a clinician can change it without vendor help.
2. Administrator setting: a trained clinic owner controls it.
3. Vendor configuration: support or implementation staff must change it.
4. Product work: code, a new interface, or a future roadmap item is required.

For every bucket, record the owner, lead time, test, rollback, and price. If a sales answer depends on a roadmap, score it as unavailable for today's purchase.

## Test privacy at the actual boundary

The specialty label does not determine the risk analysis. The data path does.

HHS says a HIPAA risk analysis must cover all electronic protected health information an organization creates, receives, maintains, or transmits, including across workstations, networks, portable media, and multiple locations ([HHS risk-analysis guidance](https://www.hhs.gov/hipaa/for-professionals/security/guidance/guidance-risk-analysis/index.html)). Map the replay through microphone, browser, service providers, draft storage, clinician review, export, and the system of record.

Ask who can access each stage. Ask how a patient decline changes the path. Trigger access removal for a synthetic user. Retrieve the evidence. Privacy claims become useful when the clinic can operate them.

## Score proof, not polish

Use a score from zero to three for each replay artifact:

- 0: promised, not shown;
- 1: shown in a canned environment;
- 2: completed with your synthetic case;
- 3: completed with your synthetic case, including the failure and recovery path.

Weight the score before the demo. A specialty clinic may care more about procedure documentation than automated follow-up. Another may reverse those weights. The score should expose that difference rather than hide it under one vendor total.

End with two forced choices. First, would the clinic buy the product if the lowest-scoring workflow never improved? Second, which existing tool or job can actually be removed if the copilot passes? A purchase that adds a dashboard but retires no work is an expensive pilot souvenir.

## Where Patient Square fits

Patient Square's [Practice Copilot](../../products/practice-copilot/) pairs its AI Medical Scribe with scheduling and prescription drafts for review. The Copilot plan adds Patient Square EHR and WhatsApp messaging; Autopilot adds AI Receptionist, AI Follow-ups, priority support, and adoption analytics. The US pricing page lists the annual-billing entry rates at $79, $119, and $199 per clinician per month, with month-to-month options also published ([Patient Square pricing](../../pricing/)).

The practice may keep an incumbent EHR as the system of record. Patient Square also offers its EHR in the Copilot plan. Neither route removes the clinician's review and signature, and the beside-an-EHR route should be tested with the clinic's supported handoff rather than a guessed connector.

Bring the five synthetic encounters. If the product can only show a clean routine visit, you have seen a demo, not specialty fit.

---

## AI Copilot EMR vs Standalone EMR: Follow the Record
https://patientsquare.com/us/blog/ai-copilot-emr-vs-standalone-emr/
Published 2026-09-22 · Tags: ai-copilot-emr, electronic-medical-records, practice-management, ehr-migration, software-buying

Compare an AI copilot EMR with a standalone EMR by chart authority, workflow fit, migration risk, and the handoffs your practice will still own.

An AI copilot EMR supports selected work inside or beside the medical record, while a standalone EMR remains the record system itself. Compare chart authority, workflow handoffs, migration risk, and the functions your practice must still own before choosing a deployment.

Open one patient's chart and follow it for a week. The appointment begins in one screen. The note appears in another. A result lands in a third queue. Billing staff retype two fields. On Friday, someone discovers that the signed note never reached the place everyone assumed it had.

That record trail is a better buying tool than the phrase "AI-native."

An AI copilot EMR can reduce handoffs when the AI-supported work and the record share a controlled workflow. A standalone EMR can be the safer purchase when it already fits the practice and the copilot would require a disruptive migration. Compare the two by tracing the record, not by counting AI features.

> **Key takeaways**
>
> - The authoritative chart must be named before the demo starts.
> - Native AI is useful when it removes a measured handoff.
> - An alongside copilot still needs a tested route into the current EHR.
> - Export, downtime, and correction work belong in the buying score.

## Two architectures, three real choices

The first architecture combines the record and AI-supported workflows in one product. The second keeps a standalone EMR and adds an external copilot. There is also a third choice: keep the standalone EMR without adding AI because the practice's actual problem lies elsewhere.

| Model | Where the record lives | What the buyer must prove |
|---|---|---|
| AI copilot EMR | The new product becomes the designated record system | Migration completeness, role controls, note approval, billing and reporting fit, export, downtime |
| Standalone EMR plus copilot | The incumbent EMR remains authoritative | Exact data route, user matching, correction behavior, duplicate handling, outage recovery |
| Standalone EMR alone | The incumbent EMR remains authoritative | Whether process, staffing, templates, or training can fix the problem without another vendor |

Patient Square publishes both a bundled-EHR path and an alongside-existing-EHR path for Practice Copilot ([product page](../../products/practice-copilot/)). That choice is useful because it forces the buyer to state the record strategy. It does not promise an automatic interface to every named EHR. Scope the transfer method during discovery.

## The native case: fewer seams, bigger move

When capture, draft, review, and record completion live in one controlled workflow, staff may avoid exports and duplicate entry. The practice can also manage user access, templates, and support through one vendor.

The trade is migration. A new record system affects more than notes. Appointment history, demographics, documents, problem lists, medications, results, claims data, user roles, reports, and retention rules may sit in the current product. Some data can move cleanly. Some will arrive as documents. Some may remain in a read-only archive.

List each class before accepting a migration quote. Ask for source format, target field, sample count, reconciliation method, and the person who decides what happens to rejected rows. "We migrate your data" is not a test plan.

The ASTP/ONC SAFER Guides cover practical EHR safety areas including patient identification, system configuration, result follow-up, communication, and contingency planning ([SAFER Guides](https://healthit.gov/clinical-quality-and-safety/safer-guides/)). Use those areas to design acceptance tests. A migrated chart should still identify the right patient, route work to the right owner, and remain usable during a planned failure exercise.

## The alongside case: smaller move, permanent interface

Keeping the current EHR avoids a full record migration. It also creates a daily boundary between products.

That boundary may be a supported interface, a file export, a browser extension, or manual copy and paste. Each has different failure behavior. A buyer should watch the exact route with a fresh test patient and a corrected note. Ask what happens when the patient's name changes, two records look alike, a clinician edits after transfer, or the EHR is unavailable.

Do not grade the route by its best day. Grade it by the exception queue.

If a cloud vendor handles electronic protected health information, the HHS Office for Civil Rights says the covered entity needs an applicable business associate agreement and must perform its own risk analysis ([HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)). That review applies whether the AI sits inside the EMR or beside it.

## The chart-authority test

Take three recent, de-identified workflow examples: a routine follow-up, a new patient with outside documents, and a visit that generates a result or follow-up task. For each, mark the moment when information becomes part of the official record.

Then ask five blunt questions:

1. Can staff tell draft from final at a glance?
2. Who can correct the draft, and where is the correction retained?
3. Who authenticates the clinical entry?
4. Which system owns the final task or message?
5. Can the practice recover the record without the vendor's user interface?

CMS requires the treating physician or non-physician practitioner to sign an entry made by a scribe, including AI technology, to authenticate the documentation and care ([CMS signature guidance](https://www.cms.gov/files/document/mln905364-complying-medicare-signature-requirements.pdf)). Product design can make that step clear. It cannot transfer clinical responsibility to the software.

## Make export a live test

Do not settle for a contract sentence that says data is exportable. Request a representative export during the evaluation. Open it without the vendor's application.

Check patient identifiers, dates, signed notes, attached documents, corrections, author identity, and file naming. Ask whether the same export is available at contract end, how long delivery takes, and what fees apply. The ASTP/ONC Cures Act resources explain federal information-blocking rules and the policy goal of access, exchange, and use of electronic health information ([ASTP/ONC](https://healthit.gov/curesrule/)). Counsel should interpret how those rules apply to a particular actor and contract. The practical buying move is simpler: test access before the relationship becomes difficult.

## Score one week, not one screen

Give each architecture the same week of work. Count:

- clicks or transfers between visit and signed note;
- correction minutes and repeated edits;
- records or tasks that land in the wrong queue;
- duplicate entry by clinicians and staff;
- time to recover after a simulated outage;
- exports that another person can actually read.

Add migration cost only to the option that requires it. Add ongoing handoff cost to the option that keeps the interface. A bundled product does not win because it has fewer logos. A standalone EMR does not win because the migration looks unpleasant. The record trail decides.

Bring the awkward record to the demo: the duplicate name, late addendum, outside PDF, or failed export. Ask Patient Square to trace that chart through both deployment paths and keep the route that your staff can explain afterward.

---

## WhatsApp for Patient Communication: A HIPAA Workflow Test
https://patientsquare.com/us/blog/ai-whatsapp-clinic-patient-communication/
Published 2026-09-22 · Tags: whatsapp, patient-communication, hipaa, clinic-operations, privacy

Map WhatsApp patient messaging across identity, minimum necessary content, vendors, retention, handoff, and failures before a US clinic deploys it.

A clinic should evaluate WhatsApp messaging through the exact service, permitted message content, contracts, access controls, and staff workflow—not the app name alone. Keep sensitive information out of messages until the privacy, security, and operational evidence is clear.

The dangerous message is often the ordinary one. A scheduler chooses the wrong Maria from autocomplete, sends "your biopsy result is ready," and notices the profile photo half a second too late. Encryption did not choose the recipient. A policy PDF did not stop the send.

For a US clinic, using WhatsApp for patient communication is a workflow and data-governance decision. The app name is one row.

> Takeaways:
> - Trace the message through every vendor and inbox before deciding what the clinic will send.
> - Separate identity, patient preference, legal permission, security controls, and record retention.
> - Begin with minimum-necessary templates and an approved route for sensitive content.
> - Test wrong-recipient, lost-device, opt-out, staff-departure, and vendor-outage failures.

## Draw the message path before writing templates

Start at the scheduling or clinical event that creates a message. Follow it through the system that triggers the send, any automation or cloud provider, the WhatsApp delivery path, the patient's device, staff replies, and the medical record.

At each hop, record five things: data, purpose, person or vendor with access, retention, and deletion or correction path.

| Hop | Question that needs an answer |
|---|---|
| Trigger | Which event starts the message, and can staff stop it? |
| Template | Who can edit text or insert patient fields? |
| Vendor chain | Which service creates, receives, maintains, or transmits PHI? |
| Recipient | How is the phone number confirmed and changed? |
| Reply | Which team sees it, and during what hours? |
| Record | What becomes part of the designated record, and how? |
| Retention | Where do copies remain after delivery or account closure? |

HHS says a service provider is a business associate when it creates, receives, maintains, or transmits PHI on behalf of a covered entity for covered functions or certain services. Its current examples include patient-messaging app developers and cloud providers ([HHS business-associate guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html)). HHS also says a cloud provider can be a business associate even when it holds encrypted ePHI without the decryption key ([HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)).

Do not ask only whether WhatsApp encrypts a message. Ask who performs each service and what agreement and safeguard apply to that relationship.

## Classify messages by exposure

Write templates in a sandbox and sort them before launch.

### Low-detail operational prompts

"Please confirm your appointment at 2:30" contains less information than a diagnosis or result, though the context can still reveal a care relationship. Use the least detail that completes the task. Avoid specialty names in a reminder when "your appointment" works.

### Messages that belong behind a safer boundary

A full note, diagnostic result, prescription detail, image, or long clinical history deserves a separate decision. Often the better message is a notification that asks the patient to use the clinic's approved record or portal. The text carries the prompt, not the clinical payload.

### Conversations that change care

If a reply changes a symptom report, medication question, or plan, define the handoff. Who triages it? How quickly? Where is the exchange documented? What happens overnight? WhatsApp cannot be allowed to create a shadow inbox with no clinical owner.

The HIPAA Privacy Rule's minimum-necessary standard generally requires reasonable efforts to limit PHI to what is needed for the intended purpose, with stated exceptions such as disclosures for treatment ([HHS minimum-necessary guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/minimum-necessary-requirement/index.html)). A clinic still benefits from choosing the smallest useful message, especially when a richer payload is unnecessary.

## Do not collapse four different approvals

Teams often write "consent obtained" and stop thinking. Split that line into four records:

1. Contact preference: the patient wants messages at this number and by this channel.
2. Communication permission: the clinic has documented the basis and scope for sending.
3. Vendor authority: contracts and business-associate terms cover the applicable data path.
4. Security decision: the clinic's risk analysis supports the configured workflow.

HHS says the Privacy Rule permits providers to use email for treatment communication when reasonable safeguards are applied. It also discusses honoring a patient's request for unencrypted email after warning the patient of the risk ([HHS electronic-communication FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/570/does-hipaa-permit-health-care-providers-to-use-email-to-discuss-health-issues-with-patients/index.html)). That FAQ is about email. It is not a blanket declaration that every consumer or business-messaging configuration is suitable for PHI.

Have privacy and security counsel review the exact WhatsApp design. Record the answer, including the product, account type, vendors, message classes, and staff workflow that were approved.

## Put safeguards into the send screen

HHS describes the Security Rule as a flexible, scalable framework requiring administrative, physical, and technical safeguards based on risk. It includes role-appropriate access, activity review, authentication, audit controls, integrity, and transmission-security provisions ([HHS Security Rule summary](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html)).

Turn those categories into product tests:

- show only the minimum patient identity staff need to choose a recipient;
- require a deliberate confirmation when a template contains sensitive fields;
- limit who can edit templates or start broadcast sends;
- remove a departing worker and verify that old sessions no longer work;
- retrieve activity for a synthetic wrong-recipient incident;
- test number correction without losing the audit trail;
- define how the clinic exports, retains, and deletes messages under its policy.

A green lock icon cannot answer any of those questions.

## Rehearse five failures

Use synthetic accounts and record the recovery time.

| Failure | The clinic must prove |
|---|---|
| Wrong recipient selected | Stop, escalation, documentation, and incident assessment |
| Patient opts out | Suppression across manual and automated sends |
| Staff phone is lost | Session revocation and access review |
| Reply arrives after hours | Clear expectation and owned queue |
| Messaging vendor is unavailable | Alternate contact route and queued-message behavior |

Add one quiet failure: the appointment changes after the reminder is queued. Confirm whether the old message is canceled or contradicted by a second send.

## Where Patient Square fits

Patient Square lists WhatsApp messaging in the Copilot plan of its [Practice Copilot](../../products/practice-copilot/). Its published US rate is $149 per clinician month to month or $119 per month on annual billing for that plan; the pricing page lists unlimited visits and notes ([Patient Square pricing](../../pricing/)).

That product listing is not the clinic's finished HIPAA analysis. Ask Patient Square to walk through the configured vendor chain, BAA coverage, message types, access roles, retention, opt-out, and record handoff for the US deployment. Use the five failure drills before live patient data enters the path.

The right launch may begin with appointment prompts and no clinical payload. That is not timid. It is a boundary the clinic can explain at 8:05 on a Tuesday, even after somebody clicks the wrong Maria.

<a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">Compare the options</a>

---

## Healthcare AI Governance Committee Charter
https://patientsquare.com/us/blog/healthcare-ai-governance-committee-charter/
Published 2026-09-22 · Tags: ai-governance, clinical-ai, healthcare-compliance, procurement

Use a practical healthcare AI governance charter with decision rights, an inventory, evidence gates, monitoring owners and explicit stop authority.

A healthcare AI governance committee should define which systems it oversees, who may approve or stop use, what evidence it reviews, and how incidents are escalated. A short charter turns broad AI principles into accountable decisions for procurement, implementation, monitoring, and retirement.

A healthcare AI governance committee needs authority, not ceremonial attendance. Its charter should say which systems enter review, what evidence earns approval, who monitors use, who can pause it and what record survives the meeting. If those decisions are missing, the committee is a discussion group with a calendar invite.

> **Key takeaways**
>
> - Give the committee a bounded decision, an owner and a deadline.
> - Keep one inventory record for every AI use case, including quiet departmental pilots.
> - Separate approve, approve with conditions, hold and reject.
> - Put stop and restart authority in the charter.

## A committee without stop authority is a meeting

Picture a Thursday incident: a department reports that an AI-generated draft repeatedly omits a material part of the encounter. Privacy asks who approved the data flow. Clinical leadership asks who can pause use. Procurement points to a signed order form. Everybody was on the steering committee, yet nobody owns the stop decision.

The charter should prevent that scene. It is not a policy anthology. It is a short operating agreement for decisions that cross clinical, technical, privacy and business boundaries.

A published [Veterans Affairs case study](https://pmc.ncbi.nlm.nih.gov/articles/PMC9652023/) describes an AI committee charter approved in 2021 and a structure with seven subcommittees spanning technical, clinical, operations and research concerns. One institution's design is not a universal template. It does show why a single undifferentiated meeting can struggle with specialized evidence.

## Copy this one-page charter skeleton

Adapt the fields to local law and governance. The wording below is an original working artifact, not legal advice.

| Charter field | Required entry | Test question |
|---|---|---|
| Purpose | Decisions the committee owns | Can another body point to a duplicate mandate? |
| Scope | Systems, use cases and material changes that enter review | Would a department know when it must file? |
| Membership | Voting roles, alternates, chair and conflicts | Can quorum be determined from the document? |
| Intake | Owner, intended users, population, data and output | Is there one accountable use-case owner? |
| Evidence gate | Clinical, privacy, security, operational and contract evidence | Can a reviewer mark each item present or absent? |
| Decision | Approve, conditional approval, hold or reject | Does every condition have an owner and due date? |
| Monitoring | Measures, denominators, thresholds and cadence | Who produces the first post-launch report? |
| Stop authority | Trigger, actor, fallback and notification | Can the use case be paused during one shift? |
| Restart | Corrective evidence and approving role | Who decides that the trigger is resolved? |
| Record | Decision log, evidence location and retention owner | Can an auditor reconstruct the decision later? |

The best charter sentence is often blunt: "No AI use case may move from evaluation to production until the named owner supplies the required evidence and the committee records a decision." Then define "AI use case" so teams cannot avoid review by calling a product a feature.

## Use NIST as the filing system, not a badge

The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) is voluntary. The companion [AI RMF Playbook](https://airc.nist.gov/airmf-resources/playbook/) organizes suggested actions under Govern, Map, Measure and Manage and says the playbook is not a checklist.

Those four functions fit a committee record:

- Govern covers authority, policy, accountability and resources.
- Map records intended use, users, affected people, data and context.
- Measure holds the evaluation method, limits, incidents and uncertainty.
- Manage contains the decision, conditions, monitoring, response and retirement.

Do not write "NIST compliant" in the approval because a worksheet has four tabs. Cite the framework as a method. Record the separate authorities, contracts and policies that actually bind the organization.

## The AI inventory is a decision index

An inventory should track use cases, not merely vendors. The same product can support clinical documentation in one service and an administrative task in another. Those contexts can have different users, data, review steps and consequences.

Minimum fields include owner, business purpose, patient population, data inputs, model or product version, output, human review, record destination, vendor, services that handle regulated data, approval status, conditions, monitoring owner, last review and next review trigger.

Give every entry a stable identifier. Put that identifier in the contract file, risk assessment, acceptance test and incident record. When a vendor changes a feature name, the use-case history should not disappear with it.

## Four decisions are clearer than "approved"

Use distinct outcomes:

1. **Approve:** evidence meets the locally defined gate for the stated scope.
2. **Approve with conditions:** use may begin under named limits, owners and due dates.
3. **Hold:** the committee lacks evidence or another authority must decide first.
4. **Reject:** the use case conflicts with policy, risk appetite or an applicable obligation.

Conditional approval is not a place to hide unfinished work. Each condition needs a due date, evidence owner and consequence for missing it. We think an expired condition should turn into a hold automatically; otherwise, the committee becomes a reminder service.

## Clinical drafts need explicit review ownership

The [APA's evaluation guidance for AI scribes](https://www.apa.org/topics/artificial-intelligence-machine-learning/evaluating-ai-scribes.html) tells clinicians to review and edit AI-generated notes before signing and says the clinician remains responsible for clinical decisions and documentation. It also recommends periodic, documented review rather than treating initial adoption as the last evaluation.

For a scribe use case, the committee record should identify who reviews each draft, where unsigned material can appear, what counts as completion, how edits are sampled, how patients are informed under local policy and what happens when the service is unavailable.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot &mdash; an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Its [current plan scope](../../pricing/) does not change the review boundary. The note is a draft, ICD-10 outputs are suggestions and the prescription is a draft. The committee approves a human-reviewed workflow, not autonomous documentation, coding or prescribing.

The [clinical-documentation audit guide](../ai-scribe-clinical-documentation-audit/) supplies a sampling and adjudication board for that monitoring record.

## Data-flow questions belong before procurement approval

The [HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html) says a cloud service provider is a business associate when it creates, receives, maintains or transmits ePHI for a regulated organization. The relationship can apply even when data is encrypted and the provider lacks the decryption key.

Ask for a current data-flow diagram, services handling ePHI, access roles, retention, deletion, recovery, incident duties and return of data. Compare answers with the proposed business associate agreement and the organization's risk analysis. Link the final versions from the inventory entry.

The vendor's [security posture](../../security/) can start the review. It cannot complete the covered entity's own analysis.

## Monitoring needs a denominator and an owner

"Monitor quality" is not an instruction. Name the sample, population, frequency, reviewer, escalation threshold and denominator. Record which changes trigger a fresh review: a new model, new data use, new population, new output, new workflow or material vendor change are reasonable candidates for local policy.

A monthly dashboard is useless when nobody can pause the use case between meetings. Give the monitoring owner a route to the stop decision and name the fallback in advance.

## The honest verdict

A small organization may not need a standing committee with seven subcommittees. A named cross-functional review group and a disciplined record can be the better fit when the AI inventory is small. Larger systems need enough specialist review capacity to keep decisions moving without turning every use case into a full-board seminar.

In both cases, the charter must answer the Thursday question: who can stop this, what happens next, and who can restart it?

If your organization is reviewing a Patient Square use case, <a href="/us/security/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">review the security details</a>. The committee should receive facts in its own format, not a vendor deck.

## Frequently asked questions

### Is an AI governance committee the same as an IRB?

No. An institutional review board governs research involving human subjects under its applicable authority. An operational AI governance committee may review clinical, administrative or business uses outside research. A project can fall under both structures. The intake form should ask about research status and route the case rather than letting one body silently replace another.

### Should the vendor attend committee meetings?

A vendor can answer technical, security and product questions, but it should not vote on the customer's risk decision. Ask for written evidence before the meeting, record unanswered questions and excuse vendor representatives when the committee deliberates. Procurement should preserve the evidence and conditions in the contract record.

### Does every product update need full reapproval?

Not necessarily. The charter should define material changes and allow a triage owner to route minor changes. A changed model, data use, output, intended population or clinical workflow may justify deeper review. Record the triage decision so "minor update" does not become an undocumented exemption.

### What should happen after an incident?

Follow the organization's clinical, privacy, security and legal response processes, then link the incident to the inventory record. The committee should decide the use-case status, corrective evidence and restart authority. It should not investigate beyond its competence or delay urgent reporting while waiting for a scheduled meeting.

### Can a governance charter prove an AI system is safe?

No. A charter assigns work and records decisions. It cannot prove a product's performance or replace clinical evaluation, privacy analysis, security testing, legal review and monitoring. Its value is procedural: evidence has owners, approval has scope, exceptions have a route and stop authority exists before a problem occurs.

---

## Practice Copilot vs AI Scribe: Which Job Are You Buying?
https://patientsquare.com/us/blog/practice-copilot-vs-ai-scribe-standalone/
Published 2026-09-22 · Tags: practice-copilot, ai-medical-scribe, practice-management, software-buying, clinical-documentation

Compare a standalone AI medical scribe with a practice copilot by workflow, record ownership, rollout cost, and the work each option leaves behind.

A standalone AI scribe serves the documentation loop, while a practice copilot can bundle that loop with other named practice workflows. Compare the record authority, handoff work, implementation scope, and total overlap before deciding which job you are buying.

The first demo ends with a clean note. The second ends with a clean note, a patient message, a scheduled follow-up, and a record already open in the same product. That makes the second demo look decisive. It may also hide three extra implementation projects.

A standalone AI medical scribe and a practice copilot solve different-sized problems. Buy the scribe when documentation is the job. Evaluate the copilot when several connected workflows are ready to move together. The right choice depends on what must change this quarter, what must stay, and who owns every exception.

> **Key takeaways**
>
> - A scribe has one main loop; a copilot can span several named workflows.
> - More modules mean more handoffs to test, not automatic savings.
> - Pick the system of record before comparing feature lists.
> - A clinician reviews and signs AI-drafted documentation.

## Start with the work, not the label

Write the current problem in one sentence. "Our physicians finish notes at night" points toward a documentation trial. "Notes, scheduling, reminders, and records sit in separate systems with duplicate entry" points toward a broader platform review.

Do not let either vendor rewrite that sentence during a demo.

A standalone scribe should capture the encounter, prepare a draft, allow correction, and support a clear route into the designated record. A practice copilot may add scheduling, messaging, follow-up, billing work, or an EHR. Patient Square, for example, lists several practice modules and publishes both a bundled-EHR path and an alongside-existing-EHR path on its [Practice Copilot page](../../products/practice-copilot/).

That public scope is a starting point. It is not proof of an interface with a named outside EHR, a migration timeline, or a workflow the buyer has not tested.

## The comparison that matters

| Buying question | Standalone AI scribe | Practice copilot |
|---|---|---|
| Primary job | Turn a visit into a reviewable note | Coordinate several named practice workflows |
| Typical first users | Clinicians and documentation support | Clinicians plus front desk, operations, billing, or follow-up owners |
| Record decision | Usually keep the current EHR and define note transfer | Keep the current EHR or adopt a bundled record system |
| Rollout surface | Consent, capture, review, export, support | All scribe work plus each added module and cross-module exception |
| Main overlap risk | Existing dictation or scribe service | Existing EHR, scheduler, messaging, billing, or phone systems |
| Best proof | Signed notes completed with less repair | Several workflows completed without hidden duplicate work |

The table does not declare a winner. It shows why a copilot trial cannot be graded only on note quality. The scheduler can fail while the note works. A reminder can go to the wrong queue. A record migration can stall while every sample screen looks polished.

## A standalone scribe wins on a narrow problem

Choose the smaller tool when the current EHR is staying, the practice likes its other systems, and charting is the measurable source of pain. A narrow rollout gives the team fewer variables. It can focus on specialty vocabulary, note structure, correction patterns, clinician acceptance, and the final handoff.

The handoff still matters. Ask whether staff copy and paste, download a file, use an approved interface, or work inside the EHR. Ask what happens when the export fails. The HHS Office for Civil Rights says a covered entity using a cloud service for electronic protected health information needs an applicable business associate agreement and its own risk analysis ([HHS cloud guidance](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)). A small product footprint does not remove security review.

Clinical authority stays with the clinician. CMS's signature guidance specifically addresses entries made by scribes using AI technology and requires the treating physician or non-physician practitioner to sign the entry to authenticate the documentation and care ([CMS, July 2025](https://www.cms.gov/files/document/mln905364-complying-medicare-signature-requirements.pdf)). A draft that looks signed is still a draft.

## A practice copilot wins when the handoffs are the problem

A copilot earns its larger scope when the practice wants to change several connected jobs and can staff the rollout. The value is not the module count. It is the removal of a known seam.

Suppose the front desk creates an appointment, the clinician documents the visit, a follow-up task is approved, and the final record remains in one defined system. If each step has an owner and the product supports that exact route, one rollout may be cleaner than four vendor relationships. If the practice intends to keep its scheduler, EHR, and messaging vendor, the same bundle may add overlap instead.

Patient Square's current US pricing separates this scope by plan. Assist lists documentation and scheduling; Copilot adds WhatsApp messaging and the bundled Patient Square EHR; Autopilot adds named receptionist and follow-up modules ([US pricing](../../pricing/)). Buyers should compare the lowest tier that covers work they have actually mapped. The [plan comparison](../assist-vs-copilot-vs-autopilot-plans/) has the current price card.

## Decide where the legal record lives

This decision comes before interface talk.

Draw one box around the system that holds the completed, signed record. Then draw every route into and out of it. The ASTP/ONC SAFER Guides treat system configuration, patient identification, test-result handling, and contingency planning as practical EHR safety concerns ([SAFER Guides](https://healthit.gov/clinical-quality-and-safety/safer-guides/)). A buyer can use that same discipline to question an AI handoff.

For each route, ask:

1. What starts the work?
2. What data may the AI use?
3. What output is only a draft or suggestion?
4. Who checks it?
5. Where is approval recorded?
6. What happens when the route is unavailable?

If a demo cannot answer those six questions, it has shown a feature without showing an operating workflow.

## Run a paired seven-day test

Use the same visit mix for both candidates. Include a routine follow-up, a long new-patient visit, a noisy encounter, a late correction, and one day when the intended handoff is unavailable.

For the standalone scribe, record draft completion, correction minutes, abandoned notes, transfer steps, and signed completion. For the copilot, keep those measures and add every workflow the team intends to buy: appointment exceptions, message approvals, staff takeover, record completion, and duplicate entry.

NIST's AI Risk Management Framework organizes work around govern, map, measure, and manage ([NIST AI RMF](https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10)). A small practice does not need a committee for every verb. It does need an owner, a mapped use case, a measure, and a response when the result misses the mark.

## Price the software you can retire

Subscription comparisons often ignore overlap. Put four lines beneath each quote:

- systems the practice will keep;
- systems it can retire;
- implementation and migration work;
- staff time needed to run and supervise the new workflow.

A copilot that replaces nothing is a larger bill. A standalone scribe that creates daily copy-and-paste work may be cheap software with an expensive handoff. The numbers only become comparable after the workflow is drawn.

Pick one job if one job is broken. Pick the broader product when several seams are broken and the team is ready to own the change. Bring Patient Square one real encounter and one awkward exception; the useful demo is the one that follows both to the final record.

---

## AI Scribe for Multi-Location Group Practices: The Control-Plane Test
https://patientsquare.com/us/blog/ai-scribe-for-group-practices-multi-location/
Published 2026-09-21 · Tags: ai-medical-scribe, group-practice, multi-location, procurement, clinical-documentation

Evaluate an AI scribe across clinic locations with a site-role matrix, a five-scenario demo, rollout stop rules, and one normalized cost sheet.

Multi-location practice software should make patient, schedule, staff, and record ownership clear across every site. Test location-aware permissions, shared identity, reporting, downtime, and cross-site handoffs instead of treating a shared login as proof of operational fit.

At 8:05 on a Tuesday, the downtown clinic needs a new physician activated. The suburban office needs yesterday's access removed. A third site wants its own cardiology template, and the compliance lead wants to know who changed the default assessment. That is the real multi-location AI-scribe test. Note quality matters, but the purchase succeeds or fails in the control plane around the note.

> Takeaways:
> - Buy for the group you operate, not for an imaginary row of identical clinicians.
> - Map every site, role, template owner, handoff, and support path before the demo.
> - Pilot one representative site first, with written stop rules and a named decision owner.
> - Verify access removal and audit evidence as seriously as the generated note.

## Start with a site-role matrix

A solo trial can begin with one login. A group should begin with a spreadsheet. Put locations across the top and roles down the side: physician, advanced-practice clinician, medical assistant, site administrator, central administrator, compliance reviewer, and vendor support.

For every cell, answer four questions:

1. Can this role create or review a draft at this site?
2. Can the role change a template or shared setting?
3. Can the role see another site's patients or reports?
4. What evidence remains after access changes?

HHS says the HIPAA Security Rule requires role-appropriate authorization for electronic protected health information and regular review of records that track access and help detect security incidents ([HHS Security Rule summary](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html)). That requirement does not turn into a universal software checklist. HHS also says each regulated entity must perform a risk analysis suited to its own size, complexity, capabilities, data, and environment ([HHS risk-analysis guidance](https://www.hhs.gov/hipaa/for-professionals/security/guidance/guidance-risk-analysis/index.html)).

So test the matrix. Do not accept "enterprise controls" as an answer.

| Event | Demo action | Evidence to keep |
|---|---|---|
| New clinician | Add a user to one site, not every site | Role and site assignment |
| Clinician transfer | Move access from Site A to Site B | Old and new permissions |
| Departure | Remove access during the demo | Revocation time and active sessions |
| Template edit | Change a shared section | Editor, timestamp, and affected scope |
| Support case | Let support inspect a synthetic error | Approval path and activity record |

## Keep one template owner, not one template

Multi-specialty groups often make one of two mistakes. The first is letting every clinician create a private template until reporting becomes incoherent. The second is forcing one note shape across specialties that do not document the same work.

Use a controlled fork. Keep a small group-owned base for identity, encounter date, signatures, and common handoff fields. Let specialty owners manage the sections their clinicians actually use. Record why a template changed and which sites receive the change.

The generated note remains a draft. The AAFP's implementation guidance tells clinicians to review AI-generated notes before signing and advises practices to inform staff and patients and obtain patient consent before use ([AAFP, 2025](https://www.aafp.org/fpm/2025/0300/virtual-scribe-tips)). A group can standardize that review obligation without pretending every specialty needs identical prose.

## Run a five-scenario vendor demo

Send vendors the script before the meeting. Ask them to use synthetic patients and let your staff drive.

### 1. A clinician works at two sites

Create two same-day visits under different locations. Check schedules, note labels, templates, exports, and reports. A location field that appears only on the dashboard but disappears from the handoff is not enough.

### 2. A patient declines the scribe

The visit still needs a workable documentation path. Test how staff record the choice, stop capture, and complete the note without improvising at the doorway.

### 3. The specialty template changes mid-pilot

Make one deliberate edit. Confirm who can publish it, whether the change is site-specific, and what happens to drafts already in progress.

### 4. A clinician changes locations

Move the user. Then try the old site. This takes three minutes and tells you more about access control than a security slide.

### 5. The handoff fails at closing time

Use the practice's real supported route: reviewed copy, download, or another documented transfer. Record the recovery steps, the owner, and what the clinician sees. Do not let a sales demo silently substitute a promised integration for the workflow you will buy.

## Roll out by cohort, with stop rules

Pick the first site for representativeness, not enthusiasm. A tiny office with one tech-friendly physician may produce a pleasant pilot and no useful evidence for a six-site group.

A stronger first cohort includes different visit lengths, at least two templates, an ordinary front-desk shift, and the actual note handoff. Before day one, publish the reasons to pause:

- an access boundary fails;
- a clinician cannot complete the fallback workflow;
- unresolved note errors cross the group's own threshold;
- support ownership is unclear after a failed handoff;
- the practice cannot produce the evidence its privacy or security lead requested.

These are local acceptance criteria, not national benchmarks. The group sets them before seeing the pilot results, which keeps the decision from moving every time somebody likes a demo.

## Normalize the quote across every site

Put each proposal on one sheet. Use the same number of clinicians, sites, expected start dates, contract months, and support assumptions.

| Cost row | What to request |
|---|---|
| Subscription | Price per clinician, location, or usage unit |
| Implementation | Configuration, training, and project work |
| Identity | SSO or directory work, if required and documented |
| Handoff | Supported export plus any interface work |
| Support | Hours, severity definitions, and response terms |
| Growth | Price for the next site and mid-term seats |
| Exit | Data return, format, notice, and transition support |

Patient Square's published US rate card lists Practice Copilot plans per clinician, with Assist at $99 month to month or $79 per month on annual billing, Copilot at $149/$119, and Autopilot at $249/$199. The page lists unlimited visits and notes; buyers still need a group-specific quote for their rollout assumptions ([Patient Square pricing](../../pricing/)).

## Where Patient Square fits

Patient Square's [Practice Copilot](../../products/practice-copilot/) combines an AI Medical Scribe with scheduling and prescription drafts for review; higher plans list WhatsApp messaging, Patient Square EHR, AI Receptionist, AI Follow-ups, support, and adoption analytics. ICD-10 output is a suggestion. Prescription output is a draft. A clinician reviews and signs.

A practice can keep its existing EHR as the system of record or use Patient Square EHR. For an incumbent system, verify the supported note handoff in the five-scenario demo. Patient Square does not promise automatic filing into every named EHR.

Bring the site-role matrix to the demo. If the vendor cannot complete it with you, the group is still buying forty individual trials.

---

## Assist vs Copilot vs Autopilot: Pick a Plan
https://patientsquare.com/us/blog/assist-vs-copilot-vs-autopilot-plans/
Published 2026-09-21 · Tags: patientsquare-pricing, practice-copilot, ai-medical-scribe, software-buying, practice-management

Match Patient Square's three US practice plans to the work you need now, with exact monthly and annual prices and a no-upgrade test.

Assist covers documentation and scheduling, Copilot adds WhatsApp messaging and the bundled EHR, and Autopilot adds the named reception and follow-up workflows. Choose the smallest plan that supports the work you need now, then test whether an upgrade earns its added cost.

Pick Assist when notes and scheduling are the job. Pick Copilot when you also want the bundled Patient Square EHR or WhatsApp messaging. Pick Autopilot only when the named receptionist and follow-up modules replace work you have actually mapped. The cheapest suitable plan beats a larger plan bought on optimism.

Patient Square prices all three per physician per month. Annual billing lowers the monthly equivalent; month-to-month costs more and keeps the commitment shorter ([US pricing](../../pricing/)).

> **Key takeaways**
>
> - Assist is $99 monthly or $79 on annual billing.
> - Copilot is $149 or $119 and adds WhatsApp messaging plus the bundled EHR.
> - Autopilot is $249 or $199 and adds the named receptionist, follow-up, support, and analytics modules.
> - Do not upgrade for a module that has no owner, workflow, or pilot case.

## The whole price card

These are Patient Square's public US rates per physician per month. The lower number is the monthly equivalent on annual billing, not a month-to-month price ([Patient Square pricing](../../pricing/)).

| Plan | Month to month | Annual monthly equivalent | Publicly listed plan scope |
|---|---:|---:|---|
| Assist | $99 | $79 | AI Medical Scribe, ICD-10 suggestions, prescription drafts, scheduling |
| Copilot | $149 | $119 | Everything in Assist, plus WhatsApp messaging and Patient Square EHR |
| Autopilot | $249 | $199 | Everything in Copilot, plus AI Receptionist, AI Follow-ups, priority support, adoption and ROI analytics |

Every plan lists unlimited visits and notes with no per-note metering. The pricing page also lists a 7-day free trial ([US pricing](../../pricing/)). The trial is useful for workflow evidence. It is not evidence that every module fits every practice.

## Use the no-upgrade test

Start at Assist. For each move up the ladder, write down the job, its current owner, the person who will handle exceptions and the pass condition for a trial.

If the practice cannot name all four, keep the lower tier while it investigates. "We may use it later" is not a workflow.

| Upgrade | Added public scope | Evidence before paying more | Reason to stay put |
|---|---|---|---|
| Assist to Copilot | WhatsApp messaging and bundled EHR | A record-system decision or approved message route with an owner and test case | Existing EHR and messaging remain intentional choices |
| Copilot to Autopilot | AI Receptionist, AI Follow-ups, priority support, adoption and ROI analytics | Call and follow-up workflows, exception owners, and measures the practice will review | Current staff or systems already handle those jobs well |

The table is deliberately strict. A larger feature list does not reduce work if no one has decided what will move, what will stay, and how exceptions return to staff.

## Assist fits a documentation-first practice

Assist lists the AI Medical Scribe, ICD-10 suggestions, prescription drafts, and scheduling. The scribe output remains a draft for clinician review. ICD-10 items are suggestions. A prescription draft is not pharmacy transmission.

This plan fits a practice that wants to test visit documentation without changing its record system. It also fits a buyer that values a shorter list during the first month. Fewer moving parts make it easier to see whether the note workflow works.

The questions are concrete. Does the draft capture what the clinician said? Which corrections repeat? Where does the signed note go? Who fixes a schedule error? Use the [AI scribe trial guide](../ai-scribe-trial-how-to-run/) and prepare a live-demo script rather than grading the sample note a vendor chose.

Stay on Assist if the existing EHR remains the intended record and WhatsApp is not an approved patient channel. There is no prize for paying for overlap.

## Copilot is the record-and-messaging fork

Copilot adds two named items: WhatsApp messaging and the bundled Patient Square EHR ([US pricing](../../pricing/)). That creates two separate buying questions.

First, record strategy. Patient Square's public Practice Copilot page describes a bundled-EHR path and an alongside-existing-EHR path ([Practice Copilot](../../products/practice-copilot/)). A practice keeping its current EHR should document the handoff. A practice adopting Patient Square EHR should scope migration, configuration, training, cutover, export, and downtime. The subscription price is not the whole change project.

Second, messaging. A WhatsApp module name does not settle patient consent, HIPAA contract scope, message content, device controls, replies, retention, or escalation. Use the [WhatsApp clinic routing guide](../ai-whatsapp-clinic-patient-communication/) before treating the module as a reason to upgrade.

Copilot fits when one or both decisions are real now. If neither is, Assist remains the cleaner purchase.

## Autopilot needs an operations owner

Autopilot adds the named AI Receptionist and AI Follow-ups modules, priority support, and adoption and ROI analytics ([US pricing](../../pricing/)). The public names define the top-level scope. They do not specify every call type, follow-up rule, escalation, reporting calculation, or connection a practice might expect.

Assign an owner before the trial. For a receptionist workflow, list five calls, including an exception that must reach staff. For follow-ups, name the trigger, approved message, reply path, stop condition, and clinical escalation. For analytics, write the measure and source before seeing a dashboard.

Autopilot is the wrong choice when those jobs already sit in systems the practice likes. It is also wrong when no one has time to supervise the pilot. Automation without an exception owner is a queue that fails quietly.

## Three worked buying notes

### A two-physician clinic keeping its EHR

The clinic's pain is evening notes. Scheduling works and patients do not use WhatsApp. Start with two Assist seats. Test the same visit types for a week, review corrections, and document the note handoff. Copilot adds no required job yet.

### A new practice choosing its record system

The owner needs documentation, scheduling, and an EHR. Copilot is the relevant plan because the bundled Patient Square EHR starts there. The buyer still needs a record-system implementation scope. If the practice keeps another EHR after comparison, it can revisit whether Assist covers the remaining gap.

### A busy office with missed calls and manual follow-ups

The owner has mapped call types, after-hours escalation, and post-visit follow-up. Autopilot is the candidate because its added module names match those jobs. Run the test with wrong numbers, urgent replies, staff takeover, and an outage. If the workflows do not pass, the tier label does not rescue them.

These examples are decision patterns, not promises of savings. Price the seats and commitment, then judge the actual work.

## Annual billing comes after fit

Annual billing reduces the displayed monthly equivalent by $20 for Assist, $30 for Copilot, and $50 for Autopilot. Across one physician for twelve months, those differences are $240, $360, and $600. The arithmetic follows the current public rate card ([US pricing](../../pricing/)).

Do not let the discount decide scope. Start with the job and tier. Review the trial, contract term, renewal, data return, and implementation work. Then choose billing frequency.

Security review belongs before real patient data on any tier. Patient Square states that BAAs are available, notes are encrypted in transit and at rest, audio is processed in memory and discarded when the note is drafted, and its SOC 2 Type II audit is in progress ([security page](../../security/)). "In progress" does not mean certified.

## The one-page plan decision

Write four lines and keep them with the quote:

1. The job we are buying now.
2. The lowest plan that names that job.
3. The evidence the trial must produce.
4. The person who owns exceptions after launch.

If you need a market comparison before choosing Patient Square, use the [AI medical scribe pricing guide](../ai-medical-scribe-pricing/). If you already know the product and only need to choose a tier, stop there. Book a Patient Square demo with the four-line decision and ask the team to test the lowest plan that fits.

---

## HL7 Integration With Mirth Connect: A Practical Primer
https://patientsquare.com/us/blog/hl7-integration-with-mirth/
Published 2026-09-21 · Tags: hl7, mirth-connect, healthcare-interoperability, interface-engineering, healthtech

Plan an HL7 v2 interface in Mirth Connect before opening the channel editor. Define messages, ACKs, mappings, failures, security and acceptance evidence.

Mirth Connect receives healthcare messages, filters or transforms them, and routes them to one or more destinations. Its user guide lists HL7 and MLLP among supported standards and protocols. The interface design still belongs to the organizations exchanging data.

An HL7 integration with Mirth Connect should begin as a written interface contract, not a half-configured channel. Name the clinical event, message type, sender, destination, field mappings, acknowledgment rule, retry behavior, and owner. Mirth can route and transform the message. It cannot settle an ambiguous workflow for you.

> Takeaways:
> - A channel is an execution path; the interface contract explains what that path means.
> - Test acknowledgments and failure recovery before celebrating a parsed ADT message.
> - Mirth message storage and retention settings can affect both operations and ePHI exposure.
> - "HL7 export" does not prove a live endpoint, mapping, acknowledgment, or write-back integration.

## Start with one event

Suppose a clinic needs a new-patient registration to reach a downstream record system. Write that sentence down. Then make it precise: the source sends an ADT event after registration is confirmed; the destination creates or updates the patient only after matching rules run; both sides retain enough identifiers to reconcile the transaction.

Now list the ugly cases. The date of birth is missing. The sending system retries after a network timeout. Two patients share a name. The destination is unavailable for 20 minutes. A message arrives twice. An update arrives before the create event.

Those cases determine the channel design. Starting with a transformer script is quicker for the first hour and slower for the next six months.

## The six-part interface contract

Keep this packet in version control beside exported channel configuration and test fixtures.

| Part | Decision to record | Acceptance evidence |
|---|---|---|
| Business event | What real-world action causes the message? | Named workflow owner signs the event definition |
| Message | Which HL7 version, trigger, segments, fields, codes, and local variations apply? | Approved sample set with required and optional fields |
| Identity | Which identifiers match patients, visits, orders, and results? | Positive, ambiguous, and no-match test cases |
| Transport | Which endpoint, protocol, certificate, and network boundary carry the message? | Connection test plus expired-certificate failure |
| Acknowledgment | When does the sender receive success or error, and what does it mean? | ACK and NACK cases tied to durable processing state |
| Operations | Who owns retries, queues, alerts, reconciliation, replay, and change control? | Runbook exercised during a simulated outage |

The table is the original artifact that matters. A screenshot of a green channel is not acceptance evidence because it says nothing about duplicates, missing fields, or downstream state.

## What Mirth Connect supplies

NextGen Healthcare describes Mirth Connect as a standards-based healthcare integration engine for bidirectional routing, filtering, and transformation across protocols and formats that include HL7, X12, EDI, DICOM, and XML. Its user guide organizes work around channels and their source and destination connectors.

That makes Mirth useful as the controlled middle. A source connector receives a message. Filters decide whether it continues. Transformers map the content. One or more destination connectors send the result onward. The engine records processing state according to its configuration.

Mirth is not the source-of-truth contract. If the source calls a field "attending provider" and the destination means "billing provider," a JavaScript mapping can move the value without resolving the semantic error. Put local definitions and code-set ownership in the interface packet.

## Acknowledgments are part of the data model

An acknowledgment is not merely a network courtesy. The sender needs to know whether the receiver accepted the message and what it can safely do next. Define success around a durable state you can explain.

If the channel acknowledges before the message is durably queued, a crash can produce a false success. If it waits for every downstream system, one slow destination can stall the source. There is no universal setting. Choose the boundary, document it, and test both the success and failure branches.

The replay rule belongs beside it. State who may replay, how a duplicate is detected, which identifier remains stable, and how the downstream owner reconciles the result. Never rely on someone remembering which dashboard button they clicked during the last outage.

## ePHI inside the interface engine

Mirth may hold raw, transformed, encoded, and queued copies of a message. NextGen's channel-properties guidance says message storage settings control how much message data is retained, whether content is encrypted, and whether persistent queuing can be enabled. It also provides pruning settings for retention and optional archival.

Treat those settings as part of the ePHI inventory. Record which copies exist, their purpose, access roles, encryption, retention period, backup path, and deletion procedure. Limit administrator access and log it. Do not send raw clinical payloads into general application logs just to make troubleshooting convenient.

HHS's Security Rule summary names access control, audit controls, integrity, authentication, and transmission security among the technical safeguards for ePHI. Map each safeguard to both Mirth and the surrounding network. A secure engine between two weak endpoints is still a weak interface.

## The test deck

Build tests from the contract, not from whatever samples happen to parse.

- One valid message for each supported event.
- Missing, malformed, and locally invalid required fields.
- Duplicate control IDs and repeated business events.
- Out-of-order create, update, cancel, and result events where relevant.
- Destination timeout, connection refusal, and recovery after restart.
- Positive ACK, negative ACK, and application-error handling.
- Non-ASCII names, units, delimiters, and the encodings your parties agreed to support.
- Reconciliation from source event through destination record.

Eight categories are enough to expose most design omissions. The exact fixtures will be interface-specific. Keep them de-identified or synthetic and run them after every mapping or engine change.

## Where Patient Square stops

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The Patient Square pricing page states "EHR-ready export (PDF · HL7 · FHIR)." That is an export-format claim. It is not a claim of HL7 conformance, a Mirth endpoint, a named EHR connection, automatic filing, bidirectional exchange, or write-back. A practice may use Patient Square EHR from the Copilot tier or keep its existing EHR as the record-system path. Any live interface needs its own discovery and acceptance evidence.

We think that boundary should appear in every integration conversation. It prevents a file format from turning into an imaginary production interface. Read the [EHR export guide](../ai-scribe-any-ehr-export/) for the product-side distinction and the [migration checklist](../switch-ai-scribe-migration-checklist/) for buyer questions.

Before a demo, write one business event and fill the six-part contract. Bring it to the call. A useful answer may be "export only" or "not supported." That is cheaper than discovering the same fact after a channel has been scoped.

---

## SOAP Note Automation Cost: Build, Buy, or Hire?
https://patientsquare.com/us/blog/what-soap-note-automation-costs/
Published 2026-09-21 · Tags: soap-notes, ai-scribe-cost, build-vs-buy, practice-operations, clinical-documentation

Price SOAP-note automation with a 30-day worksheet. Compare a scribe subscription, custom build and human support without hiding review or integration work.

A product can be priced per clinician, per encounter, or by an enterprise contract. Patient Square's published US entry price is $79 per clinician per month on annual billing. Compare that invoice with review time, setup work, support, and switching cost before calling it total cost.

SOAP-note automation cost is not the price on the invoice. It is the invoice plus clinician editing, rollout work, support, integration, security, and the notes the workflow fails to finish. Compare build, product, and human-support options over the same 30 days. Anything else is a mismatched spreadsheet.

> Takeaways:
> - Use one unit: total cost per clinician-month or per completed, signed note.
> - Patient Square starts at $79 per clinician per month on annual billing, with unlimited visits and notes.
> - A custom build needs product ownership after launch; model and speech charges are only two inputs.
> - Measure edit time and failed notes. They can reverse the apparent price winner.

## The invoice is the easy row

A three-clinician practice can price a subscription in minutes. The annual-billing entry price for Patient Square Assist is $79 per clinician per month, so the visible monthly-equivalent line is $237. That arithmetic is verifiable on the [US pricing page](../../pricing/). It is not yet a business case.

Now count the Thursday failures. One clinician stopped using the tool for procedure visits. Another spent eight minutes fixing a long assessment. The office manager held a support call. Somebody moved the signed note into the record. These costs live in payroll and frustration rather than the invoice, which makes them easy to ignore.

The same rule applies to a custom build. A prototype's speech and model bill is visible. The engineer who handles a broken capture after a browser update is not. Neither is clinical testing after a prompt change, access review for a new support role, or evidence that a deleted visit disappeared from logs and backups.

## A 30-day cost worksheet

Use actual values from the pilot. Do not fill missing cells with zero.

| Cost input | Buy a product | Build a custom workflow | Human documentation support |
|---|---|---|---|
| Direct price | Subscription or contract | Engineering plus cloud and vendor services | Wage or service invoice |
| Setup | Account, templates, training | Discovery, design, development, security review | Recruiting or vendor onboarding |
| Per-visit work | Clinician review and export | Clinician review, operations, exception handling | Clinician handoff and review |
| Reliability | Failed captures and support time | On-call work, retries, monitoring, incident response | Absence, coverage, and turnaround variation |
| Compliance | Vendor review and BAA | Full data-flow risk analysis plus BAAs for subprocessors | Workforce or contractor safeguards |
| Change | Template and workflow adjustment | Regression testing for every material change | Retraining and process updates |
| Exit | Export, notice period, migration | Archive, handoff, decommissioning | Contract exit and workflow replacement |

At the bottom, calculate two numbers:

1. Total 30-day cost divided by clinicians in the pilot.
2. Total 30-day cost divided by completed notes that clinicians reviewed and signed.

The second denominator matters. If 600 visits occurred but only 420 drafts made it to signature, dividing by 600 flatters the workflow. Keep abandoned, missing, and unusable drafts in the failure log.

## When buying is a sensible baseline

A product spreads engineering and operations across customers. That makes buying the sensible starting point when the needed output is a conventional clinical note, the workflow can run alongside the current record, and the practice does not need a private integration no product supports.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For practices, the Assist plan is $99 month to month or $79 per month on annual billing. Copilot is $149 month to month or $119 annual and adds the bundled AI EHR and WhatsApp messaging. Autopilot is $249 month to month or $199 annual and adds AI Receptionist, AI Follow-ups, priority support, and adoption and ROI analytics. The prices are monthly equivalents per clinician; all plans list unlimited visits and notes.

The standalone scribe can work alongside an existing EHR through export, while a practice can choose the bundled record system from the Copilot tier. Patient Square does not claim automatic filing into a named EHR. Count any copy or export step you plan to use.

## Build only for a real product requirement

Building can make sense when the documentation output is inseparable from a proprietary workflow, data must remain inside an architecture a product cannot meet, or a large deployment has the engineering and clinical-operations team to own the system for years. "Our template is unusual" is rarely enough.

Write the requirement before comparing vendors. Describe the input, output, latency, review state, record destination, failure path, audit event, retention, and deletion behavior. Then ask whether an existing product can meet it without inventing a promised integration.

HHS's cloud guidance is a useful cost warning. A cloud provider that creates, receives, maintains, or transmits ePHI for a regulated customer is a business associate, even if the provider cannot decrypt the data. A custom build can create a chain of business associates across cloud, speech, model, logging, support, and monitoring vendors. Each data path needs risk analysis, a suitable agreement, and operational controls.

Price the owner, not the demo. Who handles a missed speaker, a stuck queue, a model change, a security finding, a clinician complaint, and a deletion request six months later? If the answer is "the engineer who built it when they have time," the support budget is fiction.

## Human help is not one hourly rate

Human scribes or documentation staff can handle nuance and organization-specific tasks that a product may not. They also need onboarding, access, coverage, supervision, and a secure work process. Price the service as delivered, including clinician review and the periods when coverage is unavailable.

Do not assume human means error-free, or AI means unattended. Both paths end with a clinician responsible for the signed record. The difference is where work occurs and how it scales.

## The 30-day decision rule

The Peterson Health Technology Institute's ambient-scribe report frames adoption around purchasing rationale, vendor selection, rollout, and impact measurement. It notes that health systems were still working through whether to build or buy and how much IT and operations effort to commit. That is a good reason to keep a cost pilot narrow.

Pick five to ten clinicians with a representative visit mix. Log completion, edit minutes, end-of-day unfinished notes, support contacts, export steps, and abandoned drafts. Add the invoice and staff time. Compare the result with the prior month, but do not turn one practice's change into a universal ROI claim.

The [AI scribe ROI calculator guide](../ai-scribe-roi-calculator-guide/) has a broader worksheet. The [implementation guide](../ai-scribe-implementation-small-clinic/) covers rollout mechanics. If buying remains the likely path, bring the completed 30-day sheet to a demo and test the two rows with the largest current cost.

---

## HIPAA App Architecture Checklist for Healthtech Teams
https://patientsquare.com/us/blog/hipaa-compliant-app-architecture-checklist/
Published 2026-09-19 · Tags: hipaa, healthtech-architecture, ephi, security, software-engineering

Map every ePHI path before launch: identity, access, audit, vendors, backups, support and deletion. Turn HIPAA safeguards into architecture evidence.

HHS does not require covered entities to certify Security Rule compliance or recognize private Security Rule certifications. The regulated organization must identify its ePHI, assess risks, choose reasonable safeguards, document those choices, and operate them. A diagram is evidence for that process, not a government approval stamp.

A HIPAA app architecture review should answer one blunt question: where can electronic protected health information go? Trace the request through every service, log, backup, support tool, and vendor. Then attach an owner and a safeguard to each copy. The checklist is evidence for a risk analysis, not a compliance badge.

> Takeaways:
> - HHS requires administrative, physical, and technical safeguards; an encryption checkbox covers only part of the job.
> - A cloud provider that maintains ePHI is a business associate even if it cannot decrypt the data.
> - Access, audit, integrity, authentication, and transmission security each need design evidence.
> - The architecture packet should survive one test: can an engineer trace and delete every ePHI copy?

## Start with the request path, not the cloud logo

Take a real event. A patient submits a symptom form. The browser sends it to an API. A queue hands it to a worker. The worker writes a record, emits a log, and calls an outside service. A backup copies the database overnight. On Wednesday, a support engineer opens the account after a clinic reports a problem.

That story is the architecture review. Boxes labeled "HIPAA cloud" hide the interesting parts: the queue retry that retains a payload, the error logger that captures a request body, the support console with broad production access, and the backup no one has restored in a year.

HHS says the Security Rule protects the confidentiality, integrity, and availability of ePHI through administrative, physical, and technical safeguards. Its current summary names access control, audit controls, integrity, authentication, and transmission security as technical standards. NIST SP 800-66 Rev. 2 maps those requirements to practical cybersecurity resources. Neither source prescribes one framework or one cloud.

## The architecture evidence table

Use one row for every system that creates, receives, maintains, or transmits ePHI. A blank cell is work, not "not applicable," until somebody proves otherwise.

| Evidence | Question the team must answer | Artifact to keep |
|---|---|---|
| Data inventory | Which fields are ePHI, and why does this service need them? | Field-level inventory with purpose and owner |
| Identity | How is the person or workload authenticated? | Identity-flow diagram and test evidence |
| Authorization | Which role can read, change, export, or delete each record? | Role-permission matrix with denied cases |
| Audit | Which access and administrative actions are recorded? | Event catalog, sample events, and review owner |
| Integrity | How do you detect improper alteration or destruction? | Change history, validation rule, or integrity control |
| Transmission | How is ePHI protected across each network hop? | Protocol and certificate inventory |
| Storage | Where do primary, replica, cache, and search copies live? | Store list with encryption and retention settings |
| Recovery | Can the team restore usable ePHI when the primary system fails? | Dated restore exercise with recovery result |
| Vendors | Which subcontractor touches ePHI, including support and AI services? | BAA register and approved data-flow scope |
| Disposal | What happens to primary data, backups, logs, and exports after deletion? | Tested deletion and retention procedure |

Do not accept "the vendor handles it" as an answer. HHS's cloud guidance says the customer and cloud provider should confirm in writing how each party addresses Security Rule responsibilities. Shared responsibility needs named controls on both sides.

## Four traps found outside the database

### Logs

Request bodies, stack traces, and model prompts can copy ePHI into a logging system with different access and retention. Redact at the source. Then test the redaction with realistic failures, because the happy path is rarely what leaks the chart.

### Support

Support access is production access. Give it a narrow role, a reason code, a time boundary, and an audit event. A shared admin password cannot tell you which person opened a record, which defeats the point of unique identity and audit evidence.

### Backups

Availability is part of the Security Rule. HHS's cloud guidance notes that encryption alone does not keep ePHI available or protect it from corruption. A backup job that reports success is not a recovery test. Restore it into an isolated environment, verify the record count and application read path, then retain the dated result.

### Analytics and session replay

An analytics tag can receive identifiers, form values, URLs, or page content. HHS has separate guidance on online tracking technologies used by regulated entities. The clean architecture default is to keep tracking code off authenticated clinical surfaces unless the data flow and legal basis have been reviewed and documented.

## The BAA follows the data

HHS says a cloud service provider is a business associate when it creates, receives, maintains, or transmits ePHI on behalf of a covered entity or business associate. The rule still applies when the provider stores only encrypted ePHI and cannot decrypt it. Encryption changes risk; it does not erase the relationship.

Keep a vendor register next to the diagram. Record the service, data categories, permitted purpose, subprocessors, contract owner, BAA date, termination path, and evidence that data can be returned or destroyed. HHS's sample BAA guidance covers safeguards, incident reporting, subcontractors, access to records, and return or destruction at termination.

## Apply the same test to an AI scribe

An ambient scribe adds a sensitive input path: clinical audio and the text derived from it. Map capture, processing memory, transcript, draft note, model provider, user edits, signed output, logs, support access, and deletion. Ask which artifacts persist at every hop.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square states that visit audio is processed in memory and discarded after the note drafts, notes use TLS 1.2 or higher in transit and AES-256 at rest, access is role-scoped and logged, and BAAs are available. Its SOC 2 Type II audit is in progress, not complete. Those are product assertions to verify during procurement, alongside your own workflow and risk analysis. The [security page](../../security/) is the right starting artifact.

## A 60-minute design review

Put the request-path diagram on screen. Pick one create event, one support event, one backup restore, and one deletion. Walk each path slowly. For every service, ask: what data arrives, what data leaves, what is retained, who can see it, and what proof exists?

We think one hour spent naming copies beats a week polishing a generic policy. End with a defect list that has owners and due dates. Run the path again after fixes. For a wider vendor review, pair this architecture packet with the [AI scribe security checklist](../ai-scribe-security-checklist/) and the [BAA and consent guide](../ai-scribe-hipaa-baa-consent/).

---

## ABDM Milestone 3 (M3) Explained for Clinics
https://patientsquare.com/in/blog/abdm-milestone-3-explained-clinics/
Published 2026-09-18 · Tags: abdm, milestone-3, india, compliance

ABDM Milestone 3 covers fetching and viewing patient records via consent (HIU). What M3 requires, sandbox-to-production, and what it means for a clinic.

M3 is the milestone where a software product proves it can fetch and view a patient's existing health records from other providers, with the patient's consent, acting as a Health Information User. It sits above M1 (create and link ABHA) and M2 (share and link records), and the exact checklist is defined by the NHA's current milestone guidelines.

ABDM Milestone 3 is the stage where a software product proves it can fetch and view a patient's existing health records from other providers, with the patient's consent, acting as a Health Information User. It builds on M1 (create and link ABHA) and M2 (share and link records). The exact requirements are defined by the NHA's current milestone guidelines, so treat the descriptions here as the well-known structure and confirm the specifics on the official ABDM sandbox.

> **Key takeaways**
> - ABDM milestones (M1, M2, M3) are a vendor-certification path run by the NHA, not something a clinic passes.
> - M1 broadly covers creating and linking ABHA. M2 broadly covers sharing and linking records. M3 broadly adds the Health Information User side: fetching and viewing records under consent.
> - There are 2 gaps to close, not 1: passing a milestone, and running it live. Sandbox is not production.
> - DHIS eligibility depends on the effective policy, eligible records, production capability, API version, and other transaction gates—not an M3 label by itself.
> - Patient Square is not ABDM-certified at any milestone today; ABDM support is on the roadmap.

_Source: ABDM and NHA portals; confirm current milestone definitions there._

## Where M3 sits in the milestone ladder

If you read the [Milestone 2 explainer](../abdm-milestone-2-explained-clinics/), you already know the shape. The NHA certifies software against staged milestones, and each one opens up a bit more of what "ABDM" actually does for a patient sitting in front of you.

Here is the ladder in plain terms. M1 is the entry point: create an ABHA and link it. M2 is where records start moving, sharing and linking a patient's health data so it can travel with consent. M3 is the other half of that exchange. Where M2 is largely about a system putting records into the ecosystem, M3 is about a system pulling records out of it, on the patient's behalf and with the patient's permission.

That distinction is the whole point of this post. The person who wired up M2 built the outbox. M3 is the inbox.

## What Milestone 3 requires

The precise checklist lives with the NHA and gets revised, so we will describe M3 conservatively and point you to the source. Broadly, M3 is the record-retrieval milestone, the Health Information User capability.

A Health Information User, or HIU, is a system that requests and consumes health records held elsewhere. To reach M3, a product generally has to demonstrate the consented-fetch flow end to end: raise a consent request for a specific patient and record type, let the patient grant or deny it through a Consent Manager, and then fetch and display the records that come back. Depending on the vendor's role and how the NHA frames the current path, M3 can also fold in maturity on the linking and scan-and-share flows that earlier milestones introduced.

The consent handshake is the part worth understanding. Nothing gets fetched because a clinic wants it. A record request goes to the patient, the patient approves it through their own consent manager, and only then does the data flow. That is by design. ABDM is built so the patient, not the provider, holds the key to their history. If you want the mechanics of how ABHA identity anchors that consent, the [ABHA number versus ABHA address explainer](../abha-number-vs-abha-address-explained/) clears up the two identifiers patients constantly mix up.

## Why a clinic or its vendor pursues M3

M1 gets a patient onto ABDM. M2 lets a clinic contribute records. Neither, on its own, lets a doctor see what happened at the last hospital.

M3 is what changes that. Picture a Pune OPD at 8pm: a new patient arrives, no file, a vague history, a stack of old prescriptions they forgot at home. With M3-class capability live, the clinician can request that patient's prior records through ABDM, the patient consents on their phone, and the earlier discharge summary or lab reports surface at the point of care. That is the version of "interoperability" most people imagined when they first heard about the digital health mission.

So a vendor pursues M3 because it is the milestone that makes the ecosystem feel like a network instead of a filing cabinet. And a clinic cares because M3 is where ABDM starts saving clinical time and reducing repeat tests, not just generating IDs. There can also be a financial nudge: the NHA's Digital Health Incentive Scheme can pay for eligible transactions when every current gate is met. Do not turn the milestone into a payout claim. The [ABDM incentives for doctors](../abdm-incentives-for-doctors/) guide owns the volatile rates, period, and calculation rules and shows when its official sources must be checked again.

## The sandbox-to-production path

Every ABDM milestone is earned twice. First in the sandbox, then in production. Clinics get burned when a vendor conflates the two.

Here is the rough sequence a vendor follows for M3:

1. **Build against the sandbox.** The [ABDM sandbox](https://sandbox.abdm.gov.in) is the test environment. The vendor registers, gets test credentials, and implements the HIU consent-and-fetch flows against simulated data.
2. **Demonstrate the milestone flows.** The vendor runs the required scenarios, showing that consent requests, grants, denials, and record retrieval all behave as the NHA's guidelines specify.
3. **Go through NHA's process for production.** Passing in the sandbox is a checkpoint, not the finish line. The vendor then works through NHA's steps to enable the same capability in the live environment real patients use.
4. **Run it live.** Only at this stage can a doctor at your clinic actually fetch a real patient's records under consent.

The gap between step 2 and step 4 is where "we support ABDM" often lives. A product can demo an immaculate M3 flow in the sandbox and still do nothing for your Tuesday clinic. That is not the vendor lying, exactly. It is the vendor answering a different question than the one you meant.

## Sandbox certified versus production live

| Question to ask | Sandbox-only answer | Production-live answer |
|---|---|---|
| Which milestone? | "We've built toward M3" | "We're certified at M3" |
| Where does it run? | "In our test environment" | "In production, with live patients" |
| Can a doctor fetch records today? | "Once we go live" | "Yes, with patient consent" |
| Can you show current status? | Screenshots of a demo | Verifiable certified status |
| How is consent captured? | "The flow exists" | Consent Manager, per NHA spec |

That last row is not optional politeness. Fetching a patient's records under M3 sits squarely inside consent-based, lawful data handling. Under the DPDP Act framework, the patient's grant is what makes the retrieval legitimate. Our [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers the consent and data-protection obligations that ride alongside any ABDM record exchange.

## What M3 does and does not mean for a clinic

Let's be precise, because the label oversells easily.

What M3 means, when it is live: your software can pull a patient's consented history from across the ecosystem and show it to the treating clinician. Fewer blind consultations. Fewer repeat investigations because the last report is right there. A genuine step up from an ID-and-linking setup.

What M3 does not mean: it does not turn ABDM into a magic universal record where everything a patient ever did appears automatically. Records only surface for providers who are themselves on ABDM and have shared data, and only after the patient consents each time. It does not remove your DPDP obligations. And it does not, by itself, make a product good at everything else a clinic needs, from scheduling to notes. M3 is a specific interoperability capability, not a quality badge for the whole product. If you are weighing whether to sort out records exchange or documentation first, [which to buy first, an AI scribe or an EMR](../best-ai-scribe-vs-emr-which-first-india/) works through that trade-off for an Indian practice.

One more honest note. Even a vendor certified at M3 in production is not automatically a fit for your clinic. An [ABDM-ready EMR](../abdm-ready-emr-software-india/) still has to handle your OPD flow, your billing, and your front desk. Milestone status answers one question well. It does not answer all of them.

## Where Patient Square fits in all this

Straight answer: Patient Square is not ABDM-certified at any milestone today, M3 included, and we will not imply otherwise. ABDM support is on our roadmap, not shipped. We do not claim Health Information User, HFR, HPR, or NHCX integration, and we do not assert any milestone status for the product.

What the scribe does is separate from certification. It listens during the consult and drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft, all in clinical English, about two minutes after the visit ends. Those ICD-10 entries are suggestions for you to confirm, never auto-applied codes. The prescription is a draft you review and sign, not an e-prescription sent anywhere. Visit audio is processed and discarded, not stored. You stay the author of the record. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

So the M3 conversation is one you have with your HMS or EMR vendor about record retrieval and consent. The scribe is about getting the clinical note written fast and accurately, without an integration project on your side. If you want the note-drafting picture on its own, the [scribe overview for Indian doctors](../scribe-for-doctors-india/) covers it.

## The short version

Milestones belong to vendors, not clinics. M1 is create-and-link ABHA. M2 is share-and-link records. M3 is the Health Information User side: fetching and viewing a patient's records under consent, the milestone that lets a doctor actually see prior history at the point of care. The exact scope is set by NHA's current guidelines, so verify it on the ABDM sandbox rather than trusting a marketing line. And remember the two-gap rule: ask which milestone, and ask whether it is live in production.

Want to see how a signed clinical note comes together in about two minutes, with no ABDM integration required on your side to start? <a href="/in/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch it on a real visit, then read the [security page](../../security/) for how we handle your data.

---

## AI Scribe for Nephrology Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-nephrology-clinics-india/
Published 2026-09-18 · Tags: ai-scribe, nephrology, india, specialty

How an ambient AI scribe drafts CKD, dialysis, and transplant follow-up notes in an Indian nephrology OPD from Hindi or Hinglish dictation.

It drafts the note from what you dictate. Say the stage aloud, eGFR down to 34, stage 3b CKD, and the scribe writes those findings in your words. It doesn't open the lab report or calculate eGFR; the staging is yours. It structures your dictation into a clean English note even when the consult ran in Hindi or a Hindi-English mix.

An ambient AI scribe drafts your nephrology OPD note, the CKD staging follow-up, the HD or PD visit, the transplant check-in, from what you say during the consult, then hands the draft back about two minutes after the patient leaves. It doesn't read the lab report, calculate eGFR, or interpret imaging. The reading stays yours. What it removes is the typing you never have time for on a packed clinic day. Notes come back in English.

> **Key takeaways**
>
> - The scribe writes what you dictate. Say "eGFR 34, stage 3b, potassium 5.4" and the note reflects it. It never opens the KFT report or reads the numbers itself.
> - Input can be Hindi, Hinglish, or English; the note always comes back in clean clinical English.
> - CKD prevalence in the SEEK India cohort was 17.2% (Singh et al., BMC Nephrology 2013), so a nephrology list is mostly serial follow-ups where the trend is the story.
> - ICD-10 suggestions like N18.4 or N18.6 appear next to the draft. You confirm them; nothing is auto-coded.
> - Visit audio is processed in memory and discarded at draft; no recording is stored, which fits DPDP Act 2023 standards. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## Nephrology in India runs on the follow-up, not the first visit

A nephrology diagnosis is one visit. The care is years of them. The SEEK India study, published in BMC Nephrology in 2013, screened 5,588 adults and found CKD in 17.2% of them, with roughly 4% at stage 3 or worse. Every one of those patients comes back: monthly for the newly staged, more often once dialysis starts.

So a nephrology OPD is a review machine. A Tuesday CKD clinic in Chennai might see forty patients, most of them known CKD on their third or thirtieth visit, each arriving with a fresh KFT panel, a urine ACR, sometimes an ultrasound report. The consult itself is short. A 67-country review in BMJ Open put the average Indian consultation near the low end of the global range. The documentation is what doesn't fit.

Here's what a CKD follow-up note actually has to carry: the interval symptoms, the fluid status you examined, the eGFR trend since last visit, the electrolytes, the BP, what you did with the ACE inhibitor or the diuretic, and the next review date. That's six or seven chunks of dictation for a visit that's over in a couple of minutes. On a forty-patient day, the note loses the race every time. It gets squeezed to "CKD, continue," typed from memory at 9pm, or skipped. And thin notes aren't cosmetic here. Under the National Medical Commission's 2023 Professional Conduct Regulations, clinics are expected to keep patient records and produce them on request. In a specialty where the eGFR trend is the clinical argument, a one-line note is useless to future-you and a medico-legal gap.

## How the scribe fits a CKD or dialysis-unit visit

You start a session when the patient sits down and run the consult the way you always do. As you take the interval history and examine, you dictate your findings: "pedal edema reduced, no breathlessness, JVP not raised, weight down 1.5 kg." The scribe captures it whether you say it in English, Hindi, or the natural mix of both.

When the patient hands you this week's KFT and you read it, dictate the read aloud. "eGFR 34, down from 41 last month, creatinine 2.1, potassium 5.4, bicarbonate 19, hemoglobin 9.2." That's your interpretation of the report in front of you. The scribe writes it into the note as you said it. It's not opening the lab PDF or the ultrasound. You did that. The scribe is a stenographer, not a reader.

Here's the canonical version of that flow. AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It's one module inside Practice Copilot, the platform we build. After the patient leaves, you stop the session, and about two minutes later there's a draft: interval history, exam, your lab summary, assessment, plan. You read it, fix anything wrong, and sign.

For a dialysis-unit visit the shape is the same, the content shifts. You dictate the interdialytic weight gain, access site findings, cramping or hypotension during the last session, the Kt/V you're tracking, and the dry-weight adjustment. The scribe drafts an HD or PD visit note from that. It records the adequacy number you state; it doesn't calculate it or read the machine log. Three India-specific things hold across both: the note comes back in clean clinical English no matter how you dictated it, the audio is never stored, and the prescription output is a draft you review, never something the tool sends anywhere on its own. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## Hindi and Hinglish in, English notes out

This is the part that decides whether a scribe survives an Indian nephrology OPD, and it's where imported tools quietly fail.

A real consult isn't in one language. A CKD patient describes swelling and reduced urine output in Hindi, you ask about "namak" and "paani" intake in Hindi, you dictate the eGFR read in English, and you switch back to Hindi to explain the diet and the next visit. Mid-sentence. A scribe built for clean English transcripts falls apart on the first "pairon mein sujan hai" and hands you garbage.

The scribe captures English, Hindi, and 20-plus Indian languages, including that mid-sentence switching. What it does not do is give you a Hindi note. The output is always clean clinical English, structured the way a nephrology note should read, because that's the language your referral letters, your records, and any downstream reader expect. We think that's the honest framing, and worth being precise about: the scribe understands Hindi and Hinglish, it does not write in them. For most Indian nephrology clinics, English notes from bilingual consults are exactly the fit. Our [Hindi and Indian-languages guide](../ai-scribe-hindi-indian-languages/) lays out the full language list, and the [code-mixing explainer](../ai-scribe-hindi-english-code-mixing/) covers the switching if that's your daily reality.

## What a nephrology-ready draft has to show

A generic scribe flattens renal language into mush. Dictate "eGFR 34, stage 3b, K 5.4" and get back "kidney function reduced," and you'll rewrite every note, which defeats the point. The draft has to come back in nephrology language.

| What you dictate | Generic scribe often writes | What a nephrology-ready draft should show |
|---|---|---|
| CKD staging | "Kidney function low" | "eGFR 34, CKD stage 3b, down from 41 last visit" |
| Dialysis adequacy | "On dialysis, doing okay" | "HD thrice weekly, Kt/V 1.3, interdialytic weight gain 2.4 kg, AVF functioning" |
| Electrolyte status | "Some abnormal labs" | "K 5.4, HCO3 19, phosphate 5.8, on potassium binder" |
| Transplant follow-up | "Post-transplant, stable" | "Live-related transplant 2023, creatinine 1.3 stable, tacrolimus level pending, no rejection signs" |
| ICD-10 suggestion | Generic or missing | "N18.4, N18.6 suggested for confirmation" |

If the draft reads like the middle column, it wasn't built for a nephrology OPD. The right column is the bar. Dictate a real CKD read during a trial and see which one you get, not on a vendor's tidy demo script.

## Where the scribe stops, and when it isn't the right buy yet

Being straight about the limits matters more than a feature list. The scribe drafts what you dictate. It has no memory of prior visits, so the eGFR trend, the Kt/V history, the dose changes over months, all of that gets spoken out loud if you want it in the note. It won't catch that your dictated potassium and your dictated plan contradict each other. That's your review.

It also doesn't integrate with your lab system, your dialysis machine, or your clinic's record software. You get a draft, you review it, and you copy or export it into wherever you chart. If your real bottleneck is KFT values flowing automatically from the lab into the record, an ambient scribe is the wrong purchase. That's an interoperability problem, and a scribe doesn't touch it.

And here's the honest concession: if your OPD is small enough that you're already finishing your notes before you leave, a scribe isn't solving a problem you have yet. The value shows up when the after-clinic charting backlog is real. On ABDM, we'll be plain, because Indian clinics are right to ask. Live ABDM record linking is on our roadmap, not shipped. If you need to link nephrology records to a patient's ABHA number today, your shortlist is software that has cleared the National Health Authority's production milestones. We won't claim one we don't hold.

For the verdict: a scribe fits when the after-OPD charting is your real problem and you dictate your reads. It's the wrong tool if your pain is data flow between systems, or if you never want to say the read out loud.

## How to test it on your own nephrology OPD

A single demo note tells you almost nothing. Run it on your own clinic during the 7-day trial and do three specific tests. Dictate a full CKD staging read, in your usual Hindi-English mix, and check whether the draft comes back in nephrology English or flattens it. Narrate one dialysis-unit visit with the adequacy number and access findings, and see whether the structure holds. Then run it on your heaviest half-day, back-to-back rooms with KFT reports piling up, and see whether the notes stay clean and separate instead of bleeding together.

That's the only accuracy figure worth trusting. If you're comparing India-facing options, the [best AI scribe for India](../best-ai-scribe-for-india-2026/) roundup lines them up, and if you're weighing a scribe against a new record system first, [our take on scribe versus EMR ordering](../best-ai-scribe-vs-emr-which-first-india/) walks through it. For a US-focused view of the same specialty, there's a [nephrology scribe explainer](/us/blog/ai-scribe-for-nephrology/) too.

If you want to see the draft quality against your own CKD and dialysis reads before committing anything, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical complex case. Entry pricing is ₹1,599 per doctor per month on annual billing, ex-GST; add 18% GST and the invoice is about ₹1,887 a month, with unlimited visits and no per-note metering, which suits a follow-up-heavy nephrology list. The full ladder is on the [pricing page](/in/pricing/). That's the test we'd run in your shoes.

---

## CDI Software vs Ambient AI Scribe: Two Different Jobs
https://patientsquare.com/us/blog/cdi-vs-ambient-ai-scribe/
Published 2026-09-18 · Tags: clinical-documentation-integrity, cdi-software, ambient-ai-scribe, revenue-cycle, clinical-documentation

CDI software checks whether a record supports coding and payment. An ambient AI scribe drafts the encounter. See where the workflows meet and where they do not.

No. An ambient scribe drafts the clinician's encounter note from the visit. CDI software or a CDI program reviews documentation for gaps that affect coding, quality reporting, or payment. One starts the record; the other checks whether that record supports downstream use.

CDI software and an ambient AI scribe touch the same chart at different times. The scribe drafts what happened during the encounter. Clinical documentation integrity work asks whether the signed record supports the codes, quality measures, and claim that follow. Buying one to do the other's job creates a very polished gap.

> Takeaways:
> - An ambient scribe starts with the visit; CDI starts with the record and its downstream use.
> - CMS tells clinicians to make the record support the codes reported on the claim.
> - A scribe can capture a stated diagnosis, but it cannot decide which diagnosis is supported.
> - The clean handoff is a signed note plus a traceable queue for questions, not one blended score.

## One chart, two work queues

Picture a Tuesday afternoon in an internal-medicine group. The clinician says, "Shortness of breath is worse, weight is up six pounds, increase the diuretic, recheck Friday." An ambient scribe can turn that conversation into a structured draft. The clinician corrects it and signs.

The CDI question begins after that. Does the record contain the assessment that supports the diagnosis selected for the claim? Is a condition merely listed in history, or was it evaluated today? If the documentation conflicts, who asks the clinician for clarification without steering the answer?

CMS's current E/M guidance says the medical record should support the CPT, HCPCS, and ICD-10-CM codes reported on the claim. It also lists the encounter elements the record should carry, including the reason for the visit, relevant findings, assessment, plan, and the identity of the observer. That is a documentation standard. It is not permission for software to invent the missing bridge.

## The handoff map

This is the simplest useful artifact for separating the two purchases.

| Moment | Ambient scribe owns | CDI workflow owns | Human decision that remains |
|---|---|---|---|
| Visit | Capture the words spoken in the encounter | Nothing yet | What the clinician asks, observes, and concludes |
| Draft | Arrange the stated history, assessment, and plan | Define which signed records enter review | Whether the draft is faithful and complete |
| Signature | Return the draft for clinician review | Wait for the authenticated record | Corrections, diagnosis choice, and signature |
| Review | No new clinical facts | Detect a documented gap or conflict | Whether a query is warranted |
| Query | No role | Route a neutral clarification under policy | The clinician's answer |
| Coding and claim | Offer ICD-10 suggestions only | Check whether documentation supports downstream coding | Final code and claim responsibility |

The dangerous design is a shared green check that claims the note is both fast and compliant. Those are two tests. Keep them separate in the user interface and in the pilot report.

## CDI is a program before it is a product

CMS's ICD-10 implementation handbook tells large practices to audit current documentation, focus on common clinical conditions, identify recurring gaps, monitor documentation quality, and create templates that guide required information. The handbook was written for the ICD-10 transition, but the operating lesson still holds: you need a target condition, a review sample, an owner, and a feedback loop before a dashboard means much.

Start with 50 to 100 encounters from one service line. Record why each case entered review. "Missing specificity" is too vague. Write the missing element: laterality, acute versus chronic status, the link between two conditions, the work performed today, or the rationale for an order. Then count repeats by reason and by workflow stage.

That baseline tells you where the gap forms. If the clinician stated the detail but the draft lost it, test the scribe. If nobody stated it and the signed note lacks it, that is a documentation and query problem. If the note contains it but the code does not, the issue sits farther downstream. One chart can fail in three different places.

## What the scribe changes

An ambient scribe removes the blank page. It can preserve the assessment and plan the clinician actually said, which gives the signed record a cleaner starting point. It can also produce more prose than the encounter needs. A long note with a copied problem list is not automatically useful to CDI.

The Peterson Health Technology Institute's 2025 report on early ambient-scribe adoption found that health systems were still defining success across purchasing rationale, vendor selection, rollout, and impact measurement. The report explicitly asks whether organizations want a custom tool or an off-the-shelf product and how much IT and operations effort they will contribute. That uncertainty is useful. It argues for a measured pilot, not a claim that a scribe fixes the revenue cycle.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The operative word is "suggestions." The clinician confirms the diagnosis and code. Patient Square does not claim autonomous coding, compliant-query generation, denial prediction, or a replacement for a CDI team. A practice can use the bundled EHR from the Copilot tier or keep its current EHR and use Practice Copilot alongside it. Named write-back integrations are not part of that claim.

## A pilot that does not confuse speed with integrity

Run the pilot in two lanes. Lane one measures note creation: minutes to draft, minutes of clinician editing, completion by end of day, and abandoned drafts. Lane two measures the signed record: review rate, query reason, answer rate, coding change after clarification, and cases escalated for human review.

Do not merge those measures into one "documentation quality" percentage. A scribe could cut draft time while leaving the CDI queue unchanged. CDI work could reduce recurring gaps while adding a few minutes to a complex chart. Both outcomes can be rational.

We think the best buying sequence is boring: map the current failures, test the scribe against spoken-detail loss, and test CDI against signed-record gaps. Software demos come after the map. The [small-clinic implementation guide](../ai-scribe-implementation-small-clinic/) has a narrow rollout pattern, while the [claim-denial documentation guide](../ai-scribe-claim-denials-documentation/) keeps the claim boundary visible.

If note creation is the first broken step, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Ask the team to mark each one as captured, review-only, or outside product scope. For a purchase centered on coding validation or compliant queries, evaluate CDI software separately.

---

## NHCX Explained for Indian Hospital Claims Teams
https://patientsquare.com/in/blog/nhcx-claims-exchange-explained-india/
Published 2026-09-18 · Tags: nhcx, health-insurance, cashless-claims, hospital, india

Understand what India's National Health Claims Exchange is, its current pilot status, and the workflow questions hospitals should answer before rollout.

The National Health Claims Exchange is a digital exchange intended to support standardized, interoperable health-claim transactions among healthcare providers, insurers, TPAs, and other participants. It is part of the Ayushman Bharat Digital Mission ecosystem and should be understood as exchange infrastructure, not an insurer or claims adjudicator.

NHCX is a route for claim transactions, not a new claims department. It cannot repair a mismatched member number, approve an unsupported treatment, or decide who at the hospital answers a query. The exchange becomes useful only after those owners and records are clear.

> Key takeaways
>
> - NHCX is exchange infrastructure for standardized health-claim transactions among participating organizations.
> - Official updates show participant-specific progress: live participants were reported in July 2024, and an NHCX-HMIS pilot rollout was under review in July 2026.
> - It does not replace insurer adjudication, hospital records, clinical review, or staff ownership.
> - Patient Square claims no live NHCX or ABDM production integration; ABDM work remains on the roadmap.

## Place NHCX between the participants

The National Health Authority and IRDAI have described NHCX as a digital health-claims exchange designed to support standardized, interoperable exchange among healthcare providers, insurers, TPAs, and other participants ([PIB, 2024](https://www.pib.gov.in/PressReleaseIframePage.aspx?PRID=2037634)).

That is different from saying NHCX is an insurer, TPA, hospital system, or payment guarantee. Each participant keeps its own responsibilities. The hospital prepares and sends the defined transaction. The insurer or TPA applies policy and adjudication rules. Both maintain their records, controls, and staff processes.

Think of the exchange as the route in the middle.

| Layer | Owns | Does not become |
|---|---|---|
| Hospital system and claims desk | Patient, treatment, bill, documents, review, submission work | An insurer |
| NHCX | Defined exchange path and transaction specifications | A coverage decision-maker |
| Insurer or TPA systems | Policy checks, queries, authorization, adjudication, response | The hospital's clinical record |

The borders matter whenever a claim is corrected, queried, or disputed.

## Treat current status as a dated fact

A Government of India release dated 26 July 2024 reported 34 insurers and TPAs live on NHCX and about 300 hospitals preparing to send claims ([PIB, 2024](https://www.pib.gov.in/PressReleaseIframePage.aspx?PRID=2037634)). A separate release dated 17 July 2026 said a national review meeting examined rollout of an NHCX-HMIS pilot for standards-based claims exchange between hospitals and payers ([PIB, 2026](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2285825&lang=1&reg=1)).

Those dated statements should not be stretched into a claim that every insurer, TPA, hospital, transaction, or production workflow is live. The 2026 pilot description is specific to the NHCX-HMIS rollout; it does not place the entire exchange in one universal status. Before planning deployment, check the [official NHCX portal](https://nhcx.abdm.gov.in/) and current National Health Authority material for participant eligibility, transaction types, technical requirements, onboarding, testing, and production status.

A vendor roadmap is not evidence of exchange readiness. A sandbox response is not evidence that a payer has accepted a production claim.

## Map the transaction before the API

Take one current cashless pre-authorization or reimbursement workflow and lay it out as events.

1. Hospital staff identify the patient, policy, payer channel, and required transaction.
2. The treating team approves the clinical record used in the request.
3. The claims desk validates identifiers, bill details, codes, and attachments.
4. The hospital sends the defined request and retains submission evidence.
5. A query, authorization, rejection, or other response reaches a named owner.
6. Staff correct or supplement the record without erasing the earlier version.
7. The hospital reconciles the final response with its bill, patient communication, and records.

For each event, record the authoritative system, identifier, required fields, attachment rule, staff role, allowed correction, timestamp, and failure queue. Only then ask how an NHCX transaction changes the step.

This keeps the project anchored to operating work. Otherwise, teams can complete a technical exchange while queries still fall into a shared inbox.

## Keep the regulatory clocks separate

IRDAI's 2024 health-insurance master circular says insurers should decide a cashless authorization request immediately and not later than one hour after receipt, and should grant final discharge authorization within three hours after receiving the hospital's request ([IRDAI health-insurance master circular](https://irdai.gov.in/documents/37343/365525/Master+Circular++on+Health++Insurance+Business++29052024.pdf)).

Those are insurer-side receipt-to-decision periods under the circular. They do not erase hospital preparation time, query-response time, policy conditions, or the distinction between pre-authorization and final adjudication. If NHCX becomes the route for a transaction, keep separate timestamps for hospital preparation, exchange receipt, payer response, query handling, and discharge request.

## Prepare evidence, not declarations

A hospital readiness pack should contain:

- a current transaction map with staff owners;
- a field and terminology inventory linked to authoritative sources;
- sample packets with identity, bill, clinical-document, and attachment exceptions;
- access, consent, audit, retention, and correction requirements;
- failure handling for duplicate, rejected, delayed, and amended transactions;
- reconciliation reports that match exchange events to the hospital record.

Test only in the officially authorized environment and with properly governed data. Record which participant, transaction, and version was tested. "NHCX-ready" without that scope is too broad to evaluate.

Patient Square [Hospital Copilot](../../products/hospital-copilot/) includes Claims Management for internal work tracking. It does not claim live NHCX or ABDM production connectivity, an insurer or TPA connection, automatic submission, or adjudication. ABDM capability remains on the roadmap.

Bring the transaction map to a [review the current Practice Copilot scope](../../products/practice-copilot/). The useful question is not whether the product recognizes the acronym. It is whether every event before and after the exchange still has an owner.

---

## Radiology Information Systems in India: 2026 Buyer Guide
https://patientsquare.com/in/blog/radiology-information-system-software-india/
Published 2026-09-18 · Tags: radiology-information-system, ris-software, pacs, imaging-software, india, buyer-guide

Learn how RIS differs from PACS and HIS, what Indian imaging centres need, what drives cost, and where AI documentation does and does not fit.

A RIS is the software that runs the workflow of a radiology department or imaging centre: it registers the patient, schedules the scan, builds the modality worklist that tells each machine what to acquire, tracks the study through acquisition and reporting, holds the radiologist's structured report, and pushes the charge to billing. It manages the order-to-report journey. It does not, on its own, store the images themselves; that is the PACS's job, and the two run side by side.

Walk into most Indian imaging centres and the "radiology software" is really two jobs bolted loosely together: a billing screen that knows a CT was ordered, and a folder of images somewhere on a viewer that nobody's system properly links to it. When the centre scales past a couple of modalities, that gap starts costing scans, reports, and reputation. This is a buyer's guide to what a Radiology Information System actually does, how it differs from a PACS and an HIS, what an Indian imaging department needs in 2026, and where an AI documentation tool genuinely fits, which is not the RIS lane at all.

> **Key takeaways**
>
> - A RIS runs the radiology workflow and text: scheduling, modality worklists, study tracking, the radiologist's report, and billing. It is the order-to-report engine.
> - A PACS is the separate system that stores and displays the DICOM images. RIS and PACS run side by side; some vendors combine them, but they are two functions.
> - An HMS radiology module usually handles the order and the bill and little else. A busy centre with several modalities feeding a reporting queue tends to need a real RIS.
> - Cost is driven by modality count, cloud versus on-premise PACS storage, per-user versus per-study licensing, and DICOM interfacing. Get the whole number, not the headline.
> - Patient Square is not a RIS or PACS. It does not store images or integrate with imaging systems. Its documentation module drafts the doctor's note around a result, a different job entirely.

_Sources: DICOM Standard (NEMA); MoHFW EHR Standards 2016._

If you already know your imaging centre needs proper radiology software and you only want to see how a documentation layer sits alongside it without pretending to be one, you can book a demo. Otherwise, start with what a RIS is.

## What does a Radiology Information System actually do?

A RIS models radiology as a workflow, not a single transaction. It picks the patient up at the front desk and carries the study all the way to a signed, billed report. Here is what lives in that journey.

- **Registration and scheduling.** The RIS books the study against a modality and a slot, so a CT and an MRI aren't fighting for the same hour, and the patient gets a time that the machine can actually honour.
- **The modality worklist.** This is the heart of it. Using the DICOM Modality Worklist service, the RIS pushes the scheduled order straight to the scanner, so the technologist selects the patient from a list on the machine instead of retyping the name and study. That single link kills a whole class of mismatched-image errors.
- **Study tracking.** As the study moves through acquisition, quality check, and reading, the RIS knows its state. A department head can see what's waiting, what's mid-scan, and what's stuck in the reporting queue, at a glance.
- **Radiologist reporting.** The radiologist reads the images and dictates or types a structured report inside the RIS, often with templates for common studies. The report is versioned, signed off, and tied to that exact accession, not floating in a free-text box.
- **Result distribution.** Signed reports go back to the referring doctor, the patient, or the portal, with the images available on the PACS viewer.
- **Billing and charge capture.** Every study becomes a charge, so the scan that got done is the scan that gets billed, without someone reconciling a register at day's end.

None of this touches the image pixels. The RIS orchestrates the work and owns the words. The pictures themselves live somewhere else, which is exactly the distinction most buyers miss.

## RIS vs PACS vs HIS: what each one is for

The three acronyms get used loosely in Indian sales decks, and buyers pay for the confusion. Read the "owns" column first; every other difference follows from it.

| System | Owns | Handles | Does not do |
|---|---|---|---|
| **RIS** | Workflow + text | Scheduling, modality worklist, study tracking, radiologist report, radiology billing | Store or display the DICOM images |
| **PACS** | The images | DICOM image storage, archiving, the diagnostic viewer, image distribution | Run the scheduling or reporting workflow |
| **HIS / HMS** | The hospital | Registration, OPD/IPD, pharmacy, central billing, the clinical record | Build DICOM worklists or store diagnostic-grade images |

A PACS (Picture Archiving and Communication System) is where the pixels live: it takes the images off the modality, archives them, and serves them to a diagnostic viewer so the radiologist can window, zoom, and compare priors. A RIS never touches those pixels; it points at them. When a study opens, a well-integrated RIS-PACS pair shows the worklist entry and the images together, but they are still two systems doing two jobs.

The HIS, or in Indian usage the HMS, is the hospital's operational spine: registration, wards, pharmacy, and the central bill. Its radiology module usually stops at "a scan was ordered, here's the charge." It rarely builds a DICOM worklist or stores diagnostic-grade images, which is why a busy imaging department needs a RIS and a PACS underneath the HIS, not instead of it. For the wider hospital-stack picture, the [best HIS software in India](../best-his-software-india/) guide maps how these pieces connect.

## What does an Indian imaging centre need in 2026?

The right shape depends on how much imaging you actually run, not on the biggest brochure. A useful checklist to score any RIS on:

- **DICOM modality worklist support**, so the scanner pulls the order rather than the technologist retyping it. If a vendor can't demonstrate this against your machines, keep looking.
- **PACS integration or a bundled PACS**, with a diagnostic-grade viewer and a storage plan you understand. Decide up front whether that storage is cloud or on-premise, because it changes the cost and the failure modes.
- **Structured reporting with templates** for your common studies, plus versioning and sign-off tied to the accession.
- **Multi-modality scheduling** that can juggle CT, MRI, ultrasound, and X-ray without slot collisions.
- **Turnaround-time tracking**, because referring doctors judge you on report speed and you can't manage what you don't measure.
- **NABH-aware records.** If you're pursuing NABH accreditation, the traceability from order to signed report is exactly what an assessor follows, so a system that logs each step with a timestamp makes that audit far easier.

A single-modality clinic with low volume can sometimes run inside its HMS radiology module and skip the standalone RIS. The switch to a real RIS is driven by volume, modality count, and whether reporting has become a queue you need to manage rather than an afterthought.

## What drives the cost of RIS software in India?

Be sceptical of any single price, including one a vendor leads with. Most RIS and PACS software in India is sold through a sales call, and the sticker moves with your setup. We're not going to invent competitor figures here, because we don't sell a RIS and publishing numbers we can't stand behind wouldn't help you. What we can do is name the drivers, so you can read a quote properly.

- **Modality count.** More scanners means more interfaces, more worklist links, and usually a higher licence. A four-modality centre and a one-modality clinic are not in the same price band.
- **PACS storage, cloud or on-premise.** Images are heavy. On-premise storage is a capital cost you own and maintain; cloud storage is a recurring bill that scales with your archive. This choice often dominates the total, and it's easy to under-price at signing.
- **Licensing model.** Per-user licensing suits a fixed team; per-study pricing tracks your volume and can bite hard in a high-throughput centre. Match the model to how your work actually flows.
- **DICOM interfacing and integration.** Connecting each modality, and integrating the RIS with your HMS and PACS, is frequently a separate line item. A "cheap" RIS can get expensive here fast.
- **Implementation, training, and annual support.** A system you can't get live or keep running is not a saving. Ask what year-two support and renewal cost, in writing.

When you ask for a quote, insist on the figure **in rupees, ex-GST with the 18% GST stated**, and price the PACS storage and the DICOM interfacing as their own lines. The licence is often the smaller part of the bill.

## Security and data protection: what to check

Imaging data is personal health data, and under India's **Digital Personal Data Protection Act, 2023**, it carries real obligations. Whatever RIS and PACS you choose should encrypt data in transit and at rest, control who can open a study, and log access so you can answer who saw what. Where images and reports are stored, cloud or on-premise, in India or abroad, is a question worth asking before you sign, not after a breach.

On our own side, the discipline we hold is worth stating so you can compare like with like. Patient Square encrypts data in transit with TLS 1.2 or higher and at rest with AES-256. Our SOC 2 work is underway rather than complete, and we design to be aligned with the DPDP Act without claiming a certification we don't hold. For the imaging records themselves, though, the systems that matter are your RIS and PACS, and their security posture is the one to scrutinise.

## Where does Patient Square fit, honestly?

Not in the RIS or PACS lane, and we won't pretend otherwise. Patient Square does not build modality worklists, store DICOM images, run a diagnostic viewer, or integrate with your imaging systems over HL7 or FHIR. If you need to acquire, archive, and read studies, buy a proper RIS-PACS and score it on the checklist above. Nothing we sell replaces it.

What Patient Square does sit next to is the **clinical note a doctor writes around an imaging result**. Our product is packaged as Practice Copilot for clinics and Hospital Copilot for hospitals. Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR; neither path replaces a required RIS-PACS. The ambient documentation module listens during the consultation and drafts the encounter note for the clinician to review and sign. That draft is a starting point the doctor edits and approves, not a final record, and never a radiology report. Notes always come out in English. Any prescription it produces is a draft the doctor confirms, and any ICD-10 codes are suggestions, not final coding. The audio is processed in memory and discarded once the draft exists; it is not stored. And to be plain about a common India question: ABDM support is on our roadmap, not something we're certified for today, so if you need ABHA and ABDM record linkage right now, a platform like eka.care ships that and is the honest pointer. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

So the split is clean. The RIS owns the study and the radiologist's report. A documentation layer owns the referring or treating doctor's note about the patient. Imaging centres attached to a hospital often run both, because they answer different needs. If your imaging centre has outgrown the HMS radiology module, the move is a real RIS-PACS chosen on the workflow it runs. If, separately, your clinicians are losing time typing notes around every result, that's the part we can help with. For the systems around this decision, the [lab management software guide](../lab-management-software-india-lims/) covers the diagnostic-lab equivalent, [hospital EMR software in India](../hospital-emr-software-india/) covers the clinical record, the [best hospital management software roundup](../best-hospital-management-software-india-2026/) scores the operational spine, and [ABDM-ready EMR software](../abdm-ready-emr-software-india/) covers the interoperability question. When you want to see the documentation layer against a real clinic day, book a demo or check the [India pricing](../../pricing/) first: it starts at ₹1,599 per clinician per month on the annual Assist plan, ex-GST (about ₹1,887 with 18% GST), with a 7-day free trial through the India signup page.

_Sources: DICOM Standard (NEMA), including the Modality Worklist service; NABH Accreditation Standards for Hospitals; MoHFW EHR Standards 2016; Digital Personal Data Protection Act, 2023 (MeitY)._

---

## AI Claims Management for Hospitals: A Buyer Test
https://patientsquare.com/us/blog/ai-claims-management-hospitals/
Published 2026-09-17 · Tags: claims-management, hospital-rcm, clinical-documentation, hospital-copilot, procurement

Trace one claim from eligibility through remittance, then test what hospital claims AI reads, decides, sends, posts, and leaves for staff.

AI claims management is a loose market label for software that may assist with claim preparation, edits, status work, documentation requests, denials, or payment review. The label does not establish which transactions the product supports or whether it can submit, decide, or post anything. Buyers should map each claimed action to evidence.

AI claims management is a category label, not a capability contract. One product may flag missing fields; another may query claim status or draft an appeal. A hospital should trace one claim through eligibility, submission, status, attachments, adjudication, and remittance, then mark exactly where software acts and where staff remain accountable.

> **Buyer rules**
>
> - Start with transactions and work queues, not an AI feature list.
> - Require a source and audit event for every suggestion or automated action.
> - Test rejections, corrected claims, attachments, and partial payments.
> - Hospital Copilot claims chart-based drafting, scrubbing, and payment tracking; buyers still need the transaction details.

## Follow one claim, not one dashboard

Take a fictional inpatient claim with identifier TEST-00047. Give it a coverage change, a diagnosis that needs documentation support, an attachment request, a payer-status delay, and a partial payment. Keep that identifier visible through every demo screen.

CMS administers standard electronic administrative transactions for providers, plans, and clearinghouses ([CMS Administrative Simplification](https://www.cms.gov/initiatives/burden-reduction/overview/administrative-simplification/about-administrative-simplification)). Medicare companion guides identify the 837 professional and institutional claim, the 835 payment or remittance advice, and the 276/277 claim-status request and response among those transaction families ([CMS companion guides](https://www.cms.gov/medicare/coding-billing/electronic-billing/medicare-fee-for-service-compainion-guides)). Eligibility uses its own inquiry and response path.

An AI label says nothing about those connections. The product might read a work queue without sending an 837. It might draft an appeal without attaching it. It might predict a denial without seeing the final 835. The claim trace makes every gap visible.

| Claim stage | Evidence entering the stage | Minimum demo proof | Decision owner |
|---|---|---|---|
| Eligibility | Patient, coverage, service date, payer response | Show the inquiry source, response time, and stale-response handling | Registration or coverage staff |
| Claim preparation | Signed clinical record, codes, charges, patient and payer data | Show every edit, its rule source, and who can override it | Coding, billing, and authorized clinical staff |
| Submission | Approved claim and clearinghouse or payer route | Produce a transmission acknowledgement tied to TEST-00047 | Billing operations |
| Status | 276 request, 277 response, portal, or payer contact | Post the returned status to the right account with an owner | Follow-up team |
| Attachment | Payer request and approved supporting record | Match request, document, signature, route, and receipt | HIM, clinical, and billing owners |
| Adjudication | Payer result, denial reason, allowed amount | Preserve payer language and route the exception | Denials team |
| Payment | 835 or other remittance plus deposit data | Post, reconcile, and expose variance without hiding partial payment | Cash and reconciliation team |

This table is the original acceptance artifact. If the vendor cannot trace TEST-00047 through a row, mark the row unsupported. Don't fill it with a roadmap promise.

## Automation needs a source label

Claims software tends to use the word "AI" for several different acts: extraction, classification, rule matching, prediction, text drafting, or autonomous workflow steps. Those acts carry different risks.

Require each output to show its source. For a missing-field flag, point to the absent field or record section. Payer-rule warnings need a maintained source and effective date; every factual sentence in a draft appeal needs a link to the signed record. A status update should preserve the payer response rather than replace it with a cheerful paraphrase.

The same rule applies to confidence indicators. A green badge is not evidence. Ask what happens when the model and a deterministic edit disagree, whether staff can see both, and which result reaches the claim.

We think the best claims tool is the one that makes an exception boring. The clean claim demo will always look good. TEST-00047 should be awkward on purpose.

## Status automation has a concrete baseline

CMS says providers can send a 276 claim-status request and receive a 277 response. It recommends the electronic process because capable systems can generate queries and post returned status information to patient accounts, reducing manual entry and calls ([CMS claim status](https://www.cms.gov/medicare/coding-billing/electronic-billing/claim-status-request-response)).

That gives a buyer a precise test. Ask the vendor to generate a status request for TEST-00047, show the raw or authoritative response, post it to the correct account, assign the next action, and prevent another staff member from duplicating the work. Then feed an unmatched response and watch the exception queue.

If a vendor instead scrapes a portal or places an automated call, label that route accurately. It may still save work. It isn't the same transaction path, and its audit, consent, security, and downtime behavior may differ.

## Attachments are moving onto adopted standards

In March 2026, CMS finalized the first HIPAA-adopted standards for health-care claims attachments and related electronic signatures. A first under HIPAA. The rule adopts X12 transactions for attachment information and requests plus HL7 implementation guides for included clinical information, became effective May 26, 2026, and sets compliance deadlines 24 months later ([CMS final-rule fact sheet](https://www.cms.gov/newsroom/fact-sheets/administrative-simplification-adoption-standards-health-care-claims-attachments-transactions)).

That doesn't mean every hospital and payer switched on the effective date. It means the transition belongs in the buyer's architecture and contract review. Ask which current routes the product supports, what is planned for the adopted standards, who owns testing with each trading partner, and how electronic signatures are preserved.

The clinical-document boundary stays strict. Software can locate or prepare supporting records only within its proven access. It cannot invent medical necessity, rewrite a clinician's rationale after the fact, or turn an unsigned draft into claim support. Our [documentation and denials guide](../ai-scribe-claim-denials-documentation/) covers the upstream note problem; the [prior-authorization guide](../prior-authorization-documentation/) covers a separate pre-service workflow.

## Patient Square's boundary

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The [Hospital Copilot page](/us/products/hospital-copilot/) says claims are drafted documentation-complete from the chart, scrubbed, and tracked to payment. That is the public scope. The page does not identify eligibility checks, CPT or E/M coding, a clearinghouse or payer connection, 837 submission, 276/277 status exchange, 835 posting, denial prediction, appeal generation, or autonomous adjudication. Patient Square's ICD-10 output remains a clinician-reviewed suggestion, not a coding engine.

An ambient note can still matter upstream. It may give the authorized coding and billing team a more complete signed record to work from. That is a documentation claim, not a promise that a claim will be accepted or paid.

For Patient Square, bring TEST-00047 to a demo and ask the implementation team to annotate the table row by row. Supported, manual, external system, or not available are all useful answers. Vague is not.

## The exception-day pilot

Build a de-identified or synthetic set with twelve deliberately difficult claims. Include a coverage mismatch, a corrected claim, a missing signed note, an attachment request, a duplicate, a payer-status delay, a coding hold, a partial payment, a recoupment, and a claim that should never leave draft. Add two ordinary claims as controls.

Track touches, elapsed time, incorrect flags, missed exceptions, unsupported generated text, duplicate actions, and the final audit trail. Separate time spent inside the tool from time shifted to another team. If the demo makes billing faster by creating a cleanup queue in HIM, the hospital hasn't saved the work.

When the vendor can trace the awkward cases, book a Hospital Copilot working session with your claims owners present. Let TEST-00047 do the selling.

---

## eRx Software for Physicians: Draft vs Transmission
https://patientsquare.com/us/blog/erx-software-for-physicians/
Published 2026-09-17 · Tags: erx, e-prescribing, physician-software, practice-copilot, buyer-guide

eRx software must do more than draft a prescription. Use this physician buying test for transmission, EPCS controls, workflow, and vendor evidence.

eRx software creates and electronically transmits prescription information through the applicable prescribing network and standards. A medication suggestion, a typed prescription, or an AI-generated prescription draft is not enough. The buyer needs evidence of the transmission route, prescriber controls, pharmacy response, cancellation workflow, and record returned to the chart.

eRx software does two jobs a prescription draft cannot: it controls an authorized prescribing workflow and transmits prescription information electronically. Physicians comparing tools should test the route to the pharmacy, prescriber identity, controlled-substance controls, responses, cancellations, and chart reconciliation. A clean draft is only the starting artifact.

> **Before the demo**
>
> - A prescription draft is not proof of pharmacy transmission.
> - Standalone eRx can work without replacing the current EHR.
> - EPCS brings identity proofing, two-factor authentication, and access-control work.
> - Patient Square claims prescription drafts, not a pharmacy network or EPCS capability.

## Draw the boundary before comparing vendors

A physician says, "amoxicillin 500 milligrams, three times daily," and software puts the words into a tidy card. That may save typing. It hasn't prescribed anything.

Electronic prescribing adds the controlled act of sending prescription information through an electronic workflow governed by applicable standards. CMS maintains standards for Part D electronic prescribing and is transitioning covered transactions to NCPDP SCRIPT version 2023011 beginning January 1, 2028 ([CMS e-prescribing standards](https://www.cms.gov/medicare/regulations-guidance/electronic-prescribing/adopted-standard-and-transactions)). A screenshot with drug and dose fields doesn't prove that path exists.

Use four labels during procurement:

| Output | What it proves | Evidence to request |
|---|---|---|
| Medication suggestion | The software proposed text | Source of the suggestion and clinician confirmation step |
| Prescription draft | The software prepared editable fields | Required review, edit history, and discard behavior |
| Electronic prescription | An authorized order can be transmitted | Named network or route, supported transactions, pharmacy response, audit trail |
| EPCS | Controlled substances can be prescribed electronically | DEA-compliant application evidence, identity proofing, two-factor authentication, logical access controls |

These aren't maturity levels. A practice may want drafts but deliberately keep prescribing in its existing EHR. Trouble starts when a buyer treats one row as evidence for the next.

## Standalone software is a real option

CMS's 2026 EPCS setup guide says some e-prescribing programs connect with EHRs and others run as standalone software ([CMS EPCS guide](https://www.cms.gov/files/document/my-2026-cms-epcs-program-getting-started-quick-reference-guide.pdf)). That makes the first architecture choice straightforward: keep prescribing where it already works, add a standalone tool, or replace the broader record system.

Standalone eRx may suit a locum, a small practice whose record system lacks prescribing, or a group that cannot change the incumbent EHR this year. The extra login is not the only cost. Staff must reconcile the prescription record back into the chart, prevent duplicate patient profiles, manage departing prescribers, and define what happens during downtime.

An EHR-connected option can remove some hand entry, but "integrated" needs a noun and a verb. Which patient identity crosses, and does medication history return? Staff should find out whether pharmacy responses are visible, where cancellations land, and whether the signed prescription appears in the legal record. Ask the vendor to perform each action with a fictional patient.

## EPCS turns setup into a control test

For controlled substances, CMS tells prescribers to use software that meets DEA requirements. Its current quick-reference guide names identity proofing, two-factor authentication, and logical access control among the setup steps ([CMS EPCS guide](https://www.cms.gov/files/document/my-2026-cms-epcs-program-getting-started-quick-reference-guide.pdf)). Those are operational controls, not checkbox copy.

Ask who completes identity proofing, who grants prescribing access, how the second factor works, how a lost factor is replaced, and how access is revoked when a prescriber leaves. Then test an unauthorized staff account. A demo that only shows the happy path hasn't shown the control.

The practice also needs a local policy for downtime, failed transmissions, pharmacy changes, refill requests, and a prescription sent to the wrong destination. Software evidence does not replace the prescriber's legal authority or the organization's response process.

## The prescription-draft review

AI can make the first artifact faster and still leave the higher-risk decisions with the clinician. Review the draft in a fixed order:

1. Match the patient and encounter.
2. Confirm the intended drug, strength, formulation, dose, route, frequency, duration, and quantity.
3. Check allergies, interactions, contraindications, renal or hepatic considerations, and the current medication list in the approved clinical source.
4. Confirm pharmacy, substitution instructions, refills, controlled-substance status, and the prescriber's authority.
5. Move the verified information through the actual eRx system, then confirm its final chart record.

The AI draft must not make any of those decisions. It can reflect what the clinician said. It cannot screen, reconcile, authorize, or transmit unless the vendor has separately demonstrated those functions and the organization has approved them.

## Patient Square's claim is deliberately smaller

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The public [Practice Copilot page](/us/products/practice-copilot/) says drug, dose, route, and frequency are pre-filled from the conversation and nothing sends without the clinician's signature. Those words establish a draft and signature gate. They do not identify a Surescripts connection, EPCS evidence, controlled-substance routing, refill exchange, or electronic cancellation workflow. Under the product claims ceiling for this article, Patient Square remains on the prescription-draft side of the boundary.

That means a practice with working e-prescribing can leave it in place. Patient Square can draft the note and prescription text for review, while the verified eRx system remains the sending system. A buyer looking for a new prescribing network should evaluate a product that proves the third or fourth row in the boundary table.

The [pricing page](../../pricing/) lists Practice Copilot plan scope. It isn't evidence of a pharmacy connection. Put that distinction in the procurement record beside the transmission evidence.

## A nine-action demo script

Use fictional patients and ask every shortlisted vendor to perform the same actions:

| Action | Passing evidence |
|---|---|
| Create a routine prescription | Correct fields, named prescriber, review before send |
| Change the pharmacy before sending | Destination changes without creating a duplicate order |
| Receive a pharmacy response | Response lands with an owner and audit trail |
| Cancel or replace an order | Old and new states stay visible |
| Process a refill request | Patient, drug, prescriber, and decision remain linked |
| Attempt EPCS | Verified control path, or a plain statement that EPCS is unsupported |
| Use an unauthorized account | Action is denied and logged |
| Lose connectivity | Downtime state is clear; no false "sent" status |
| Reconcile the chart | Final prescription record appears in the approved source of truth |

Price the labor around the software after the test. Count duplicate entry, identity administration, support calls, and failure cleanup. A low subscription can be expensive if two people reconstruct every prescription in the chart.

If your need is note and draft preparation, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. If your need is pharmacy transmission or EPCS, keep those as explicit, separately verified requirements.

---

## AI Discharge Summaries: What the 2026 Study Found
https://patientsquare.com/us/blog/ai-discharge-summary-hospitalists/
Published 2026-09-16 · Tags: hospitalists, discharge-summary, clinical-ai, hospital-copilot, evidence-review

The Stanford hospitalist pilot found modest time change, frequent omissions, and lower burnout. Here is the evidence a hospital should test next.

The 2026 Stanford study tested MedAgentBrief, a custom workflow that generated draft hospital-course summaries from free-text notes at one Stanford inpatient medicine unit. Eleven attending hospitalists participated. It was a prospective, single-arm quality-improvement pilot, not a randomized comparison and not an evaluation of every commercial discharge-summary product.

The 2026 Stanford study supports a narrow answer: an AI workflow can draft hospital-course text that hospitalists often use, but review still finds omissions and inaccuracies, while measured time savings may be small. It does not prove that every discharge-summary product is safe, fast, or ready for unattended use.

> **Read the study this way**
>
> - The pilot involved 11 attending hospitalists at one inpatient medicine unit.
> - Physicians used AI text in 219 of 384 discharge cases, a 57% use rate.
> - Detailed feedback on 100 summaries found more omissions than hallucinations.
> - Audit-log time changed far less than clinicians felt it changed.
> - Hospital Copilot says its module drafts from the stay's record; it does not claim the Stanford implementation.

## The study was narrower than the headline

The JAMA Network Open paper evaluated MedAgentBrief, a custom agentic workflow at one Stanford Health Care inpatient medicine unit. Eleven attending hospitalists participated in a single-arm prospective quality-improvement pilot from August 1 through October 11, 2025 ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)). There was a before-period for some measures, but no randomized control group.

MedAgentBrief did not write a discharge record from ambient room audio. It pulled free-text history-and-physical notes and daily progress notes, then generated a one-line patient summary, a narrative hospital-course overview, and a problem-based summary. The study says the workflow did not access structured laboratory results, medication lists, or flowsheet data. Physicians received source-linked output and could use, edit, or discard it ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)).

That distinction changes the buying question. A product can be called an AI discharge-summary tool while taking very different inputs: a discharge conversation, selected notes, the whole longitudinal chart, structured medication data, or text pasted by a clinician. The study's outcome belongs to the tested pipeline, not to the label.

## The numbers, with their denominators

During 384 discharges for 331 patients, the workflow generated 1,274 daily hospital-course summaries. Physicians incorporated AI text into final discharge documentation in 219 cases, or 57% of the discharges ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)). That is adoption evidence. It is not a 57% success rate.

Detailed feedback covered 100 summaries: 88 that were used and 12 that were not. Within those reviews, physicians reported omissions in 25, inaccuracies in 20, and hallucinations in two. The categories could overlap. Eighty-eight were rated as having no harm potential, and one was initially rated likely to cause moderate harm, although later adjudication found the disputed directive appropriate ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)).

The denominator deserves a red circle. Feedback covered only part of the used set and a much smaller portion of the unused set. The authors acknowledged that selection could bias the observed safety profile. A buyer shouldn't turn the reviewed-sample percentages into a universal error rate.

| Common claim | What the paper supports | What it does not support |
|---|---|---|
| "Hospitalists used it" | AI text appeared in 57% of final discharge documents during the pilot | Every hospitalist will use it at the same rate |
| "The summaries were safe" | Most of the 100 reviewed outputs were rated as having no harm potential | Outputs were error-free or safe without review |
| "It reduced burnout" | Mean work-exhaustion score fell in 10 paired responses | The tool caused the change in a controlled trial |
| "It saved time" | Five of seven physicians with matched logs had median reductions up to 2.9 minutes | A reliable large time saving across users |
| "It generated the discharge summary" | It drafted the hospital-course portion from free-text notes | It reconciled structured medications, labs, or every discharge field |

This evidence-to-claim table is the part worth taking into procurement. It keeps a good study from becoming a bad sales sentence.

## The omission problem is the useful finding

Omissions appeared in 25 of the 100 reviewed summaries. The paper grouped them around stable chronic conditions, unresolved diagnostic uncertainty, and details that were present but not given enough weight ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)). That failure mode makes sense for a hospital course. A polished summary can omit the thing the outpatient clinician needed most.

So review by fluency is weak. Read against sources. For a synthetic trial case, put the draft beside the admission note, active problem list, daily notes, consultant recommendations, medication record, pending studies, and follow-up plan. Mark every statement that lacks a source and every source fact that never reaches the draft.

Do the medication pass separately. The Stanford workflow did not use structured medication lists, and this post does not claim that Patient Square reconciles discharge medications. A hospital's medication-reconciliation and order workflows remain whatever the approved local system requires.

## Time felt different from time measured

The mismatch between perception and audit logs may be the paper's best operational lesson. Among seven physicians with matched baseline data, five saw median documentation-time reductions of up to 2.9 minutes, while two saw increases of up to 1.5 minutes. The before-versus-pilot difference did not meet the paper's statistical threshold. Yet clinicians reported perceived savings in 67 of the 100 feedback responses, including 32 that estimated more than 15 minutes saved ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)).

Perceived effort matters. So does clock time. Measure both without pretending they are the same variable. A hospital can ask users how draining the task felt, then pull active documentation time from the record system and measure time to signed completion. The intervention may feel easier without creating capacity elsewhere in the shift.

Burnout scores fell from a mean 1.75 to 1.20 among ten paired respondents, while the study did not detect a change in cognitive-burden scores ([Grolleau et al., 2026](https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2848785)). Because this was a small single-site pilot without a concurrent control group, the clean wording is "associated with," not "caused."

## Patient Square claims a draft from the stay record

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The [Hospital Copilot page](/us/products/hospital-copilot/) says its AI Discharge Summary is drafted from the stay's own record during the stay, then reviewed and signed. That establishes a broad source and review boundary. It does not identify which note types or structured fields enter the draft, which record systems connect, whether statements link to source notes, or how authentication works. None of the Stanford performance numbers can be transferred to Patient Square without a direct evaluation.

This is a better sales boundary, frankly. A hospital should bring its own source map and a set of fictional or properly authorized cases to the demo. Ask the implementation team to show what enters the module, what stays outside it, where the draft lands, and what happens when the output omits an unresolved diagnosis.

CMS says entries prepared by scribes must be authenticated by the treating practitioner ([CMS MLN](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/signature_requirements_fact_sheet_icn905364.pdf)). An AI summary has the same practical finish line: the accountable clinician reviews and authenticates the record under hospital policy.

## A twelve-case evidence packet

Don't run a demo on one tidy three-day admission. Build twelve fictional or approved cases that include a long stay, diagnostic uncertainty, a late consultant recommendation, a pending test, a changed medication, an important stable condition, a readmission, and an ordinary short stay. Some cases should contain more than one trap.

For each output, record source-supported statements, clinically material omissions, incorrect statements, unsupported additions, medication or follow-up discrepancies, edit time, and final disposition: use, rewrite, or discard. Have hospitalists review independently before discussing the outputs as a group. The local disagreement is information too.

If your team wants to test that boundary, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. A polished paragraph isn't the acceptance criterion. Traceability is.

---

## AI Scribe for Eye Hospitals in India: High-Volume OPD
https://patientsquare.com/in/blog/ai-scribe-for-eye-hospitals-india/
Published 2026-09-16 · Tags: specialty, ai-scribe, ophthalmology

An ambient AI scribe for high-volume eye OPDs in India: a clean English note per consulting-room encounter, from Hindi or Hinglish. From ₹1,599/mo + GST.

Yes. The scribe drafts a structured note about two minutes after each consult, which matches a doctor's chair that turns over every three to five minutes once workup is done. Pricing is flat per doctor with unlimited notes, so a 120-patient day costs the same as a 30-patient one. Volume is the whole reason to use it.

An eye OPD is one of the fastest-moving rooms in Indian healthcare. Patients move through vision, refraction, and workup counters, then reach the ophthalmologist for a consult that can be over in minutes. AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It hears Hindi, Hinglish, and 20-plus Indian languages; the note always comes out in clean clinical English. Pricing for a practice starts from ₹1,599 per doctor per month on the annual Assist plan, plus 18% GST (about ₹1,887 all-in), with unlimited notes and no per-note metering. A larger eye hospital runs on Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR and is demo-priced.

The bottleneck in a high-volume eye hospital isn't the exam. It's what the exam leaves behind.

> **Key takeaways**
>
> - An eye OPD is a flow of counters; the scribe sits at the one that produces the note, the doctor's chair.
> - A structured English note lands about two minutes after each consult, drafted from what the doctor says.
> - From ₹1,599/mo per doctor (annual Assist, ex-GST) with unlimited notes and no per-note metering: a 120-patient day costs the same as a 30-patient one.
> - It captures spoken findings, not slit-lamp, OCT, or autorefractor output. Those stay on your machines.
> - ABDM integration is roadmap, not live, and we say so before you ask.

## An eye hospital is a flow of counters, and the note is the last one

Walk a busy eye hospital in Hyderabad or Coimbatore at 11am and you see an assembly line, in the best sense. Registration. Vision and refraction. Dilation and wait. Basic workup, sometimes imaging. Then the ophthalmologist. Each counter has its own queue and its own system, and the whole design exists to keep the doctor's chair moving.

That chair is where documentation is born and where it backs up. The consult itself can run three to five minutes once the workup is in hand. The note doesn't move that fast. So at the end of a 90-patient session, the doctor is holding a stack of half-remembered encounters, and the record either gets thin or gets written from memory at 8pm. Neither is good for a chart you may need to defend later.

Picture a cataract camp Tuesday. Two hundred patients screened by lunch, a senior consultant seeing the surgical candidates one after another, three minutes each, calling out lens grades and pressures while the next patient is already being dilated. Nobody is typing during that. The notes get reconstructed after the last patient, or they don't get written properly at all. That's the exact gap an ambient scribe fills: it was listening while the doctor talked, so the draft is already sitting there.

The scribe slots into exactly one point in that flow, the doctor's chair, and drafts the note from the conversation there. The counters upstream don't change. If your OPD runs 80-plus patients a doctor a day, book a demo and watch a consult note draft live.

## A patient-flow documentation map for a high-volume eye OPD

Here's the artifact: a map of where the patient goes, what each stop produces, and where a written note is actually owed.

| Flow stop | What happens | What it produces | Where the note is owed |
|---|---|---|---|
| Registration | Demographics, complaint intake | Queue token, basic details | Your front-desk system |
| Vision + refraction | Visual acuity, refraction | Numbers on your existing record | Not the doctor's note |
| Workup / imaging | IOP, OCT, biometry as needed | Device output on your machines | Not the doctor's note |
| Doctor consult | History, exam findings, diagnosis, plan | The clinical note | Here — the scribe drafts this |
| Prescription + advice | Glasses, drops, next review | Rx draft plus counselling | Draft from the same consult |

The map makes the boundary obvious. The scribe isn't trying to replace your refraction record or read your OCT. It targets the one stop that turns a fast consult into a slow note, and leaves the rest of the flow alone. That's the honest scope, and it's why it works at volume: the busiest, most-repeated step is the one it takes off the doctor's plate.

## The volume math on a 90-patient session

No table can know your hospital, so here's the arithmetic with every assumption showing. Time one session and swap in your own numbers.

| Line item | Written by hand | With the scribe |
|---|---|---|
| Consults per doctor per session | 90 | 90 |
| Writing time per note | ~1.5 min | drafted for you |
| Review-and-sign per note | included above | ~20 sec |
| Documentation time per session | ~135 min | ~30 min |
| Per month, 26 OPD days | ~58.5 hours | ~13 hours |

Ninety seconds per note is deliberately low, because eye notes are short. That's the point: at OPD volume, even a short note times 90 is a couple of hours a doctor loses per session. Twenty seconds to review and sign is an assumption about you, not a product claim, so test it on your floor. Unlimited notes with no per-note metering is what makes this survive the arithmetic, because the cost doesn't climb with the patient count. Book a demo to see the math on your own OPD.

## "Aankh mein irritation": Hindi in, English notes out

An eye consult in India is rarely one language. The patient reports the problem in Hindi or a regional tongue, the doctor answers in a mix, and the exchange is code-mixed: "aankh mein irritation, dhup mein zyada, do din se." Single-language dictation breaks on that.

The scribe listens in English, Hindi, and 20-plus Indian languages, including code-mixed speech, and follows switches mid-sentence. What comes out is always a clean clinical English note, so the chart reads the same whether the consult ran in Hindi, Telugu, or both. The mechanics are in [our post on Hindi and Indian-language capture](../ai-scribe-hindi-indian-languages/).

## What an eye hospital pays at OPD scale

We think flat pricing is the only model that survives eye-OPD volume. Per-note pricing punishes exactly the practice that documents the most: a high-throughput hospital running hundreds of encounters a day.

Patient Square is flat per doctor, ex-GST, billed with 18% GST added. On annual billing: Assist at ₹1,599/mo (₹1,887 with GST) covers the scribe, ICD-10 suggestions, prescription drafts, and scheduling. Copilot at ₹2,399/mo adds the bundled AI Copilot EHR and WhatsApp messaging. Autopilot at ₹3,999/mo adds the AI Receptionist and AI Follow-ups. Every plan: unlimited notes, no per-note metering, no setup fee. The full ladder is on [the pricing page](/in/pricing/).

These per-doctor tiers are Practice Copilot, the fit for a solo or small-group eye clinic. A larger eye hospital running many chairs, an IPD, and hospital-wide records is a Hospital Copilot conversation instead: it's a separate product, quoted on a demo rather than a public per-doctor tier. If that's your scale, book a demo and ask for the Hospital Copilot walkthrough.

## Where the scribe stops, and when EMR software wins

Three limits, plainly.

It captures spoken findings, not device output. IOP, refraction, biometry, and OCT results enter the note only if the doctor says them aloud; the scribe won't pull them from a slit lamp or an autorefractor. If machine integration is your core requirement, a scribe alone isn't that product. For structured refraction records, IOL biometry, and imaging attachment, start with a dedicated system: [our ophthalmology EMR buyer's guide](../ophthalmology-emr-software-india/) covers device integration and names when a full eye-clinic EMR is the better fit than a scribe.

It doesn't make clinical calls. ICD-10 codes are suggestions, the prescription is a draft, and every note waits for the doctor's review and signature. If you're deciding whether to adopt a scribe or a record system first, [our take on scribe-versus-EMR ordering](../best-ai-scribe-vs-emr-which-first-india/) walks the trade-off.

ABDM integration is on our roadmap, not live. If ABHA-linked records are a hard requirement this quarter, verify any vendor's real certification status before signing. What ships today: notes born digital, encrypted in transit and at rest, audio processed in memory and never stored, handled to DPDP Act 2023 standards. Details are on [the security page](/in/security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

None of this needs trust in a blog post. Pick your heaviest OPD session, run the 7-day trial on it, and book a demo to see an eye consult note drafted from a real encounter. If it isn't a note you'd sign, you'll know within a week.

---

## AI Scribe for Vascular Surgery: Spoken Notes vs Data
https://patientsquare.com/us/blog/ai-scribe-for-vascular-surgery/
Published 2026-09-16 · Tags: vascular-surgery, ai-medical-scribe, procedure-documentation, clinical-data, specialty-practice

A vascular scribe can draft the clinic and procedure narrative. Measurements, images, device details, and registry fields need their own source checks.

It can draft the spoken history, vascular exam narrative, assessment, counseling, and plan. It cannot examine pulses, read a duplex study, measure an aneurysm, inspect an angiogram, or pull a prior value. The vascular clinician states the finding and verifies the draft before signing.

One number can travel through a vascular service four times: the lab report, the clinic note, the procedure plan, and a registry record. An AI scribe may draft one of those artifacts from speech. It does not make the number consistent across the other three.

That is the vascular-surgery buying test. Trace the data before judging the prose.

> **Key takeaways**
>
> - The scribe records a clinician's spoken interpretation; it does not read vascular imaging or lab systems.
> - Serial measurements need a source and date in the draft, followed by comparison with the signed report.
> - Procedure narration can save writing, but silent device and access details stay silent.
> - Registry abstraction, CPT/E/M selection, medical necessity, and claims remain outside the scribe.

## Follow one measurement through the day

Take an aneurysm diameter, ABI, or duplex velocity from a fictional training case. Ask where it starts, who verifies it, where it is copied, and which downstream record uses it. The exercise shows how much work the proposed scribe removes and how many copies remain.

The Society for Vascular Surgery says its Vascular Quality Initiative collects pre-operative risk factors, intra-procedural variables, outcomes, and one-year follow-up data ([SVS VQI](https://vascular.org/vascular-specialists/practice-and-quality/vascular-quality-initiative)). Its reporting standards exist to keep definitions and classifications consistent enough to compare data ([SVS](https://vascular.org/vascular-specialists/practice-management/clinical-guidelines-and-reporting-standards)). A fluent paragraph is not a substitute for that structure.

In a standalone scribe workflow, the clinician reads the source report and states the relevant measurement. The scribe drafts the sentence. During review, the clinician checks the value, unit, side, study date, and comparison. Registry staff still abstract from the approved sources their program specifies.

## Build a data-lineage strip

Put this strip beside a de-identified trial note. Draw a line through every cell the value touches.

| Stage | Authoritative source | What the scribe may do | Review question |
|---|---|---|---|
| Vascular lab or imaging | Signed report and original study | Record the clinician's spoken summary | Does value, unit, side, and date match? |
| Clinic assessment | Vascular clinician's judgment | Draft the assessment and plan | Is interpretation attributed to the clinician? |
| Procedure | Operative record, device log, medication record | Draft the operator's narration | Are silent details still blank rather than invented? |
| Follow-up | New study plus prior signed reports | Draft the stated comparison | Did the clinician actually state the baseline? |
| Registry or quality program | Program-defined source hierarchy | No connection claimed | Was every field verified in the normal abstraction process? |

The strip is deliberately tedious. Vascular documentation is full of small numbers that grow teeth downstream.

## Clinic narrative fits better than image interpretation

The consult is ordinary scribe territory: symptom history, walking limits, wound history as described, medication discussion, exam findings the clinician narrates, counseling, and the plan. The tool can organize those words into a reviewable note.

It cannot palpate a pulse, inspect a wound, stage ischemia, or read an ABI, duplex, CTA, MRA, or angiogram. If the clinician says, "Today's duplex report shows..." the draft should preserve that source. If the clinician says nothing about the study, the scribe should say nothing too.

Serial surveillance adds a trap. A spoken comparison such as "4.8 centimeters, unchanged from 4.8 last year" sounds complete. The clinician still needs to verify both measurements and dates against their reports. Patient Square does not retrieve prior values from the chart for this scribe workflow.

## Procedure dictation needs a local checklist

Procedure notes vary with the service and setting, so use the organization's approved template. Turn its required fields into a checklist. Access, laterality, lesion or target, technique, devices, medications, specimens, findings, complications, closure, disposition: include only the fields that apply to the specific procedure and local policy.

The operator can dictate during a suitable pause or immediately afterward. The scribe turns that speech into a draft. It does not watch the screen or device log. If a serial number, dose, or access detail was never spoken, a blank field should remain blank for the operator to complete.

This is where we are stubborn: no "normal" defaults. A scribe that fills silence with familiar procedure language may look efficient during a demo and become expensive during review.

## A scribe is not the vascular stack

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

An established vascular group can run Practice Copilot beside its current record. No vascular-lab, PACS, device, VQI, or named-EHR connection is claimed. The [US pricing page](../../pricing/) lists a bundled AI EHR from the Copilot tier, but we do not describe it as a vascular registry, imaging archive, device log, or specialty billing system.

The scribe can return ICD-10 suggestions based on the assessment the clinician stated. It does not select CPT or E/M codes, determine medical necessity, bundle services, or submit claims. The prescription output is a draft for review, not a transmitted order.

## Review the note in source order

Instead of reading top to bottom, review by risk. Start with measurements and laterality. Move to source attribution and comparisons. Check the procedure fields against the operative sources. Finish with the narrative and wording.

CMS says a treating practitioner authenticates a scribed entry by signing it ([CMS MLN](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/signature_requirements_fact_sheet_icn905364.pdf)). AMA policy says AI-generated record content requires physician consent and final review ([AMA](https://policysearch.ama-assn.org/policyfinder/detail/cybersecurity?uri=%2FAMADoc%2FHOD.xml-H-480.931.xml)). A green check from the software is not authentication.

Use initials beside each source-sensitive correction during the trial. After a week, the correction log will show whether the same failure repeats. One missed unit may be a training issue. The same missed unit twelve times is a product-fit issue.

## The four-note trial

Choose a claudication consult, a surveillance follow-up with serial measurements, a vein visit, and one procedure dictation. Use fictional or properly de-identified cases for procurement unless the vendor agreement and practice controls already permit real protected health information.

Count wrong sides, missing units, source confusion, invented normal findings, absent procedure details, and edit minutes. Also confirm deletion, access controls, BAA terms, and audio retention. Patient Square says audio is processed in memory and discarded at note draft, while notes are encrypted in transit and at rest; BAAs are available and the SOC 2 Type II audit is in progress ([security page](../../security/)).

If the narrative is the bottleneck, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring the data-lineage strip. If the bottleneck is registry abstraction or moving vascular-lab values into the chart, test a product built for that job.

---

## SOAP Notes for Social Workers: A Worked Example
https://patientsquare.com/us/blog/soap-notes-for-social-workers/
Published 2026-09-16 · Tags: social-work, soap-notes, behavioral-health, clinical-documentation, templates

A practical social work SOAP note example, with the progress-note boundary, client-access test, and AI review checks that protect the record.

Subjective captures the client's report and relevant quotations. Objective records observable facts and what occurred. Assessment contains the social worker's clinical synthesis, including progress and risk reasoning when applicable. Plan names the next action, responsible person, timing, and follow-up. Local policy and payer rules still control required fields.

A useful social work SOAP note is a progress record, not a transcript of therapy. It connects the client's report to observable facts, the social worker's assessment, and a dated plan. The hard part is the cut. Some details belong in the shared clinical record; intimate detail often doesn't.

> **The record boundary**
>
> - Write for the next qualified reader, including the client who may request the record.
> - Keep separately maintained psychotherapy notes outside the SOAP progress note.
> - Put interpretation in Assessment, not in Objective dressed up as fact.
> - An AI draft can organize words. It cannot own risk, diagnosis, reporting, or the signature.

## Start with the record boundary

Picture the last appointment on a Thursday. The client discussed a housing notice, missed work, an argument with a sibling, and a panic episode. A transcript could preserve forty minutes. The clinical record needs the smaller set of facts that supports assessment, intervention, progress, and the next step.

NASW's clinical standards say services provided to or for a client belong in the clinical record and should be documented after each encounter, with the record kept private and secure ([NASW clinical standards](https://www.socialworkers.org/Practice/NASW-Practice-Standards-Guidelines/NASW-Practice-Standards-for-Clinical-Social-Workers)). Its health-care standards call for timely documentation of assessment, intervention, outcomes, contacts, referrals, and permissions when indicated ([NASW health-care standards](https://www.socialworkers.org/Practice/NASW-Practice-Standards-Guidelines/NASW-Standards-for-Social-Work-Practice-in-Health-Care-Settings)). Those are useful selection rules. They don't ask for every personal detail a client disclosed.

The federal privacy distinction matters too. HHS says clinical case notes and SOAP notes can be part of a designated record set that an individual may access. Separately maintained psychotherapy notes receive different treatment under HIPAA ([HHS access guidance](https://www.hhs.gov/hipaa/for-professionals/faq/2042/what-personal-health-information-do-individuals/index.html)). HHS also says the psychotherapy-note definition excludes summaries of diagnosis, functional status, treatment plan, symptoms, prognosis, and progress ([HHS mental-health FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/2088/does-hipaa-provide-extra-protections-mental-health-information-compared-other-health.html)).

That gives you a blunt editing test: if a sentence is necessary for care, payment, coordination, or a defensible account of the service, it may belong in the progress note. If it is the therapist's private process note about the conversation and is maintained separately, don't paste it into SOAP by habit. State law, agency policy, contracts, and payer rules can be stricter, so the local template still wins.

## Give each letter one job

SOAP breaks down when the same conclusion appears in all four sections. Keep the jobs separate.

| Section | Its job | Useful material | Common failure |
|---|---|---|---|
| Subjective | Preserve the client's account | Reported symptoms, change since last visit, a short material quotation | Turning the whole session into dialogue |
| Objective | Record what occurred or was observed | Attendance, behavior, affect as observed, intervention used, measurable task result | Smuggling interpretation in as fact |
| Assessment | State the licensed professional's synthesis | Progress toward the goal, clinical formulation, risk assessment when indicated | Repeating Subjective with a diagnosis label |
| Plan | Commit to the next action | Follow-up date, referral, homework, safety step, responsible person | "Continue current plan" with no owner or timing |

Objective doesn't mean emotionless. It means traceable. "Client was evasive" is an interpretation. "Client paused for roughly thirty seconds and declined to answer the housing question" states what the writer observed. The assessment can then explain why that observation matters.

We think Plan is the best quality check. A vague plan often exposes a vague assessment. If the note can't name what happens next, who owns it, and when it will be revisited, the earlier sections probably haven't reached a usable decision.

## A synthetic note, edited down

This example is fictional. It is a writing exercise, not a treatment recommendation or a substitute for an agency's required form.

| SOAP field | Example | Review note |
|---|---|---|
| S | Client reported receiving a seven-day notice from the landlord and missing two shifts after a panic episode. Client said, "I freeze when I open the letter." Client denied current intent to harm self or others when asked by the clinician. | Keep the quotation that explains the barrier. Do not import unrelated family history. |
| O | Client arrived on time. Speech was quiet and slowed at the start of the session. Social worker used paced breathing and broke the housing call into two steps. Client completed a practice call script during session. | Name the intervention and observable response. Do not label the client "unmotivated." |
| A | Housing stress is interfering with work attendance and the current stabilization goal. Client completed the practice task with prompting and identified one support person. Licensed clinician completed the organization's risk assessment and documented the result in the required field. | The draft must not invent a risk level. Use the organization's tool and the clinician's judgment. |
| P | Client will call the local housing service with the script by Friday noon and message the clinic after the call. Social worker will send the approved referral today and review attendance and panic symptoms at the appointment next Tuesday. | Assign an owner and date to each action. |

Notice what's absent. There is no diagnosis generated from a phrase, no prediction about the housing case, and no dramatic retelling of the family argument. The note shows the service, the professional reasoning, and the next handoff.

## Read the draft as the client might

HHS explicitly includes SOAP notes among records that can fall within an individual's access right ([HHS access guidance](https://www.hhs.gov/hipaa/for-professionals/faq/2042/what-personal-health-information-do-individuals/index.html)). That doesn't mean writing timidly. It means describing behavior precisely and separating observation from inference.

Run a second-person test before signing: if the client read this sentence tomorrow, could you explain why it is accurate and necessary? "Manipulative" is hard to defend and rarely useful. A description of the request, response, and boundary is more informative. The same test catches jokes, irritation, copied labels, and unnecessary third-party detail.

Risk documentation needs a different check. The exact requirements vary by jurisdiction and organization. Don't let an ambient tool infer ideation, intent, access to means, protective factors, a reporting duty, or a disposition from conversational fragments. The social worker asks, assesses, decides, and records the decision in the required place.

## Put AI on the drafting side of the line

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For social work, the useful unit is the draft. The scribe can organize spoken material into SOAP sections. It cannot decide what state law requires, diagnose from the conversation, score risk, make a mandated-reporting decision, or determine what belongs in separately maintained psychotherapy notes. ICD-10 output is a suggestion the licensed clinician confirms or rejects. A prescription output is only a draft and may not apply to the social worker's scope.

The privacy review comes before a real client enters the test. NASW's technology standard calls for protecting client information in electronic records and understanding the benefits and risks of technology ([NASW clinical standards](https://www.socialworkers.org/Practice/NASW-Practice-Standards-Guidelines/NASW-Practice-Standards-for-Clinical-Social-Workers)). Patient Square says BAAs are available, visit audio is processed in memory and discarded after the note is drafted, records are encrypted in transit and at rest, and its SOC 2 Type II audit is in progress ([security page](../../security/)). Confirm those terms against the agreement your organization will sign.

## A five-note acceptance test

Use fictional or properly authorized cases until privacy and contracting are settled. Pick notes that force different judgment: a routine follow-up, a care-coordination call, a session with a third party present, a visit with a risk screen, and an encounter where little changed.

For each draft, mark unsupported facts, missing goal links, observation-versus-inference errors, excessive intimate detail, wrong owners or dates, and minutes to a signed note. Then ask a licensed reviewer to compare the draft with the agency's template and record policy. One pretty note proves almost nothing.

If the five-note set survives that reading, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a>. The best outcome isn't longer documentation. It is a shorter path to a record you can defend.

---

## AI Scribe for Occupational Medicine: Keep Two Records
https://patientsquare.com/us/blog/ai-scribe-for-occupational-medicine/
Published 2026-09-15 · Tags: occupational-medicine, ai-medical-scribe, workers-compensation, return-to-work, privacy

Occupational medicine produces a clinical chart and a work-status message. A scribe can draft both only when the disclosure boundary stays explicit.

Yes. It can turn the spoken injury history, exam narrative, assessment, treatment discussion, and stated work restrictions into a draft. It does not decide causation, recordability, maximum medical improvement, disability, or fitness for duty. The clinician reviews and signs the final clinical record.

An occupational medicine visit creates two records with different readers. The clinical chart holds the injury history, exam, assessment, and care plan. The work-status message tells an employer what the worker may do, under the disclosure rules that apply to that case. An AI scribe can help draft words. It should never blur those audiences.

A fast note that leaks a diagnosis to the wrong reader is not efficient. It is a new problem.

> **Key takeaways**
>
> - Keep the clinical chart and employer-facing work-status communication as separate artifacts.
> - HHS allows several paths for workers' compensation disclosures, but generally limits protected information to what is necessary for the purpose.
> - OSHA recordability is the employer's determination; a scribe only captures what the clinician said and did.
> - Test for privacy leakage and unsupported causation language, not just note speed.

## One encounter, two audiences

The worker and treating team need a clinical record. Depending on the case and applicable law, an insurer, state administrator, or employer may need a narrower set of facts to process a claim or arrange work.

HHS says the HIPAA Privacy Rule permits workers' compensation disclosures through several routes, including disclosures authorized by workers' compensation law, required by other law, needed for payment, or made with the individual's authorization. HHS also says covered entities generally must limit the disclosure to the minimum necessary for its purpose ([HHS](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/disclosures-workers-compensation/index.html)). The details vary by state and request.

That is why one giant note is the wrong artifact. Draft the clinical record first. Build the work-status message from an approved form or practice template, with only the information authorized for that reader. Legal and compliance staff should set the rule; the scribe should follow the clinician's words inside it.

## The disclosure-boundary worksheet

Use a four-column worksheet when evaluating any documentation tool. It is simple enough to keep beside the workstation.

| Information | Clinical chart | Work-status message | Release only through the practice's approved path |
|---|---|---|---|
| Mechanism and symptom history | Full relevant history | Usually omit | Confirm when a claim form calls for it |
| Exam and test detail | Full relevant findings | Usually omit | Send only if authorized or required |
| Diagnosis and differential | Clinical record | Do not assume it belongs | Apply state law, authorization, and minimum-necessary policy |
| Functional restriction | Record the clinician's reasoning | State the authorized restriction and duration | Verify exact wording before release |
| Treatment and medication | Clinical detail | Usually omit | Disclose only through the approved route |
| Follow-up date | Clinical plan | Include when needed for status review | Check form and recipient |

This is operational guidance, not a fifty-state legal answer. Workers' compensation rules and forms are state-specific. The clinic should map each recipient and form with counsel or its compliance lead before automation touches the workflow.

The separation also matches the employment side. The EEOC says applicant and employee medical information is confidential, subject to narrow exceptions, and must be kept in medical files separate from personnel files ([EEOC](https://www.eeoc.gov/laws/guidance/health-care-workers-and-americans-disabilities-act)). A clinic cannot control an employer's filing cabinet, but it can avoid sending unnecessary clinical detail into it.

## Record the restriction without making the decision

Work restrictions are both clinical and operational. The clinician recommends them. The employer decides whether suitable work is available and carries its own OSHA recordkeeping duties.

OSHA lists restricted work or job transfer among the criteria that can make a work-related injury or illness recordable, along with days away, treatment beyond first aid, loss of consciousness, and certain diagnoses ([OSHA](https://www.osha.gov/recordkeeping/recording)). In a published interpretation, OSHA explains that a health care professional may recommend a restriction while the employer remains responsible for the final recordkeeping determination ([OSHA](https://www.osha.gov/laws-regs/standardinterpretations/2006-08-03)).

The scribe belongs one step earlier. It can draft: "No lifting above 15 pounds with the right arm through September 22; recheck before full duty." It should not add, "OSHA-recordable," infer an accommodation, or decide causation. Those are separate judgments by the authorized people.

Specific language helps. Name the activity, limit, body side when relevant, duration, and review date. Avoid a vague "light duty" line when the clinician actually gave concrete restrictions. Then compare the draft with the clinician's instruction before releasing anything.

## Causation language is not autocomplete

Occupational notes often contain a history about when symptoms began and what task preceded them. That history is not automatically a causation opinion.

Keep attribution visible in the draft. "The worker reports pain began while lifting a box" states the source. "The workplace caused the injury" is a conclusion. If the clinician makes a causation finding, the note should reflect the clinician's exact position and the basis the clinician chose to document. If no opinion was given, the scribe should not manufacture one to make the assessment sound complete.

This is a strong adversarial test. Give the tool a visit with an uncertain mechanism and inspect whether the draft upgrades a report into a finding. One invented verb can change the whole record.

## What Practice Copilot does here

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

The scribe can draft the occupational visit from the room's conversation. It does not determine work capacity, causation, disability, maximum medical improvement, OSHA recordability, or claim compensability. It does not complete or submit state workers' compensation forms, send a report to an employer, or file a claim.

Practice Copilot can run beside the clinic's current EHR. The [US plans](../../pricing/) also include a bundled AI EHR from the Copilot tier, but no occupational-medicine form set or state reporting connection is claimed. Keep those workflows where they already work.

The module returns ICD-10 suggestions and a prescription draft for clinician review. It does not choose CPT or E/M codes, transmit a prescription, or act on the work-status plan.

## Review and release are separate clicks

CMS says a treating practitioner authenticates a scribed medical-record entry by signing it ([CMS MLN](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/signature_requirements_fact_sheet_icn905364.pdf)). That clinical sign-off is not blanket permission to disclose the whole note to an employer.

Build two controls:

1. Clinical review: patient, mechanism attribution, exam, assessment, treatment, restriction, and follow-up.
2. Release review: recipient, authority, form, minimum necessary content, and delivery channel.

Different staff may own the second control. Good. The separation prevents a signed chart from becoming an accidental employer letter.

Patient Square processes visit audio in memory and discards it once the draft is ready. The [security page](../../security/) states that notes are encrypted in transit and at rest, BAAs are available, and the SOC 2 Type II audit is in progress. Those controls cover the vendor relationship. The practice still owns recipient selection and disclosure.

## A trial should include a privacy trap

Don't test only the easy sprained-ankle visit. Add a case with unrelated medical history, a changed restriction, a disputed mechanism, and an employer request. Use fictional or properly de-identified data during procurement.

Score five things: whether the clinical story is complete, whether attribution survives, whether restrictions stay exact, whether the employer-facing output leaks clinical detail, and how long review takes. Any privacy leak is a stop, even if the note took ten seconds.

We would also ask the vendor to show deletion and export, explain who can access notes, and name what happens to audio. A feature tour is not enough for a two-audience workflow.

If your clinic's real bottleneck is turning a spoken occupational visit into a clean clinical draft, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Bring the blank work-status form too. The useful part of the conversation is where the scribe stops.

---

## AI Scribe for Physiotherapy Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-physiotherapy-clinics-india/
Published 2026-09-15 · Tags: specialty, ai-scribe, physiotherapy

An ambient AI scribe for physio clinics in India: a note per session block, in clean English from Hindi or Hinglish sessions. From ₹1,599/mo + GST.

Yes. The scribe listens during the session and drafts a structured note about two minutes after it ends, which fits a floor where a new patient starts every 20 to 30 minutes. Pricing is flat per therapist with unlimited notes, so a 22-session day costs the same as an 8-session one.

Physiotherapy is a documentation-heavy specialty hiding as a hands-on one. You run a session, then you owe a note: subjective change since last time, what you assessed, what you did, how they responded, the plan for next session. AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It hears Hindi, Hinglish, and 20-plus Indian languages; the note always comes out in clean clinical English. Pricing starts from ₹1,599 per therapist per month on the annual Assist plan (ex-GST; about ₹1,887 once you add 18% GST), with unlimited notes. Copilot and Autopilot add a bundled AI EHR, WhatsApp messaging, and receptionist and follow-up automation as you move up.

The problem in physio isn't one long consult. It's volume of short ones.

> **Key takeaways**
>
> - A physio treatment block is many sessions, not one visit, so you owe many notes, not one.
> - A structured English SOAP note lands about two minutes after each session, drafted from what was said in the room.
> - From ₹1,599/mo per therapist (annual Assist, ex-GST) with unlimited notes and no per-note metering: a 22-session day costs the same as an 8-session one.
> - Same structure every session, so a 12-session block reads as one continuous progress story.
> - The scribe captures spoken numbers, not goniometer or device data, and ABDM is roadmap, not live. We're upfront about both.

## Physio is a per-session note problem, not a per-patient one

Most clinical software is built around the idea of a patient who visits, gets diagnosed, and leaves. Physiotherapy doesn't work like that. A frozen shoulder is 10 to 15 sessions. A post-op knee rehab can be 20 or more. Each one is a separate encounter that produces a separate note, and the notes only earn their keep as a set: the value is in reading session 3 against session 11 and seeing the arc.

A busy floor makes this brutal. Two or three therapists, each turning over a patient every 20 to 30 minutes, six to eight hours a day. A 67-country study in BMJ Open pegged the average Indian outpatient consult at about two minutes; a physio session is longer, but the documentation-to-face-time ratio is the same trap. The hands-on part is the job. The note is the tax, and it comes due after the last patient of the evening.

If your floor runs 40-plus sessions a day across therapists, book a demo and watch one session note draft live.

## A note per session block, drafted while you work

Here's the artifact worth spending time on: a documentation map of a single treatment block, showing where a note is owed and what usually happens to it.

| Session block stage | What you document | Typed by hand at 8pm | With the scribe |
|---|---|---|---|
| Initial assessment | History, objective findings, ROM/MMT, diagnosis, plan | Detailed, because it's the first one | Drafted from the session, same detail |
| Sessions 2–4 (acute) | Subjective change, treatment given, response | Still decent | Drafted, same structure |
| Sessions 5–9 (mid-block) | "Improving," a line or two | Thins out fast | Full note, every time |
| Sessions 10+ (late) | "Continue same" | Often skipped or copy-pasted | Still a real note |
| Discharge / review | Outcome, home program, closure | Rushed at day's end | Drafted from the conversation |

The pattern every physio recognises: the first note is thorough, the middle notes decay, and the block loses its story right where continuity matters most. A scribe flattens that curve. Session 11 gets drafted from the session you actually ran, at the same fidelity as session 1, because you're checking a draft two minutes later instead of reconstructing it from memory at night.

We think that's the real win in physio, more than raw minutes saved. A clean serial record is what protects you when a patient plateaus and you need to show what was tried, or when a colleague covers your floor and picks up a block cold.

## The session-count math on a busy physio floor

No table can know your clinic, so here's the arithmetic with every assumption showing. Time yourself for one shift and swap in your own numbers.

| Line item | Typed by hand | With the scribe |
|---|---|---|
| Sessions per therapist per day | 20 | 20 |
| Writing time per note | ~2.5 min | drafted for you |
| Review-and-sign per note | included above | ~30 sec |
| Documentation time per day | ~50 min | ~10 min |
| Per month, 26 working days | ~21.7 hours | ~4.3 hours |

Two and a half minutes per note is conservative; most therapists we've watched write less because they're rushed, which is exactly the quality problem above. Thirty seconds to review and sign is an assumption about you, not a product claim, so test it. The point isn't the exact figure. Documentation time in physio scales straight with session count, and session count is the number a growing clinic wants to raise, not cut. Book a demo if you'd rather see the math on your own floor first.

## "Kamar mein pain, left side": Hindi in, English notes out

A physio session in India rarely runs in one language. The patient describes the problem in Hindi or Marathi, you switch to English for the objective bits, and the whole exchange is a code-mix: "kamar mein pain, left side, jhukne pe zyada." Single-language dictation tools break on that sentence.

The scribe listens in English, Hindi, and 20-plus Indian languages, including code-mixed speech, and follows the switches mid-sentence. What comes out is always a clean clinical English note, so your record reads the same whether the session ran in Hindi, Tamil, or both. How that capture works is covered in [our post on Hindi and Indian-language notes](../ai-scribe-hindi-indian-languages/).

## What a physio clinic pays as session volume grows

Unlimited notes with no per-note metering is the only honest model for a high-session specialty. Per-note pricing quietly taxes the exact pattern physio depends on: frequent, repeated, short encounters across a long treatment block.

Patient Square is flat per therapist, ex-GST, billed with 18% GST added. On annual billing: Assist at ₹1,599/mo (₹1,887 with GST) covers the scribe, ICD-10 suggestions, prescription drafts, and scheduling. Copilot at ₹2,399/mo adds the bundled AI Copilot EHR and WhatsApp messaging. Autopilot at ₹3,999/mo adds the AI Receptionist and AI Follow-ups. Every plan: unlimited notes, no per-note metering, no setup fee. The full ladder sits on [the pricing page](/in/pricing/). Running a one-therapist practice? [The solo-doctor cost breakdown](../ai-scribe-cost-for-solo-doctor-india/) runs this math at your scale.

## Where the scribe stops, and when other software wins

Three limits, stated plainly.

It captures what's spoken, not what a device measures. If you say a knee flexion is 110 degrees or a pain score is 4 on 10, that lands in the draft. It won't read a goniometer, a dynamometer, or a gait system on its own. Numbers enter because someone said them.

It doesn't run your clinic's operations. Session-pack billing, exercise-plan sharing, and recurring appointment scheduling are a clinic-software job, not a scribe's. If those are your first requirement, start with a physio clinic platform: [our physiotherapy clinic software buyer's guide](../physiotherapy-clinic-software-india/) walks through session-pack billing and assessment records, and names when a dedicated physio tool is the better fit than a general scribe.

ABDM integration is on our roadmap, not live. If ABHA-linked records are a hard requirement this quarter, check any vendor's real certification status before signing. What ships today: notes born digital, encrypted in transit and at rest, audio processed in memory and never stored, handled to DPDP Act 2023 standards. Details are on [the security page](/in/security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

None of that needs trust in a blog post. Pick your busiest evening, run the 7-day trial on it, and book a demo to see a physio session note drafted from a real session. If the note isn't one you'd sign, you'll know inside a week.

---

## AI Scribe for Urology: Consults, Tests, Procedures
https://patientsquare.com/us/blog/ai-scribe-for-urology/
Published 2026-09-15 · Tags: urology, ai-medical-scribe, procedure-notes, clinical-documentation, specialty-practice

A field-by-field guide to what a urology scribe can draft from speech, what remains in test and procedure systems, and how to review it.

It can draft the spoken history, narrated exam, assessment, plan, and procedure account. It cannot perform the exam, read imaging, pull a bladder-scan value, or know a cystoscopy finding that nobody said. The urologist reviews the draft and authenticates the finished record.

A urology scribe can draft three kinds of prose: the consult, the clinician's account of a test, and the procedure narrative. It cannot see the cystoscope, read the ultrasound, fetch the pathology report, or know a bladder-scan value that stayed on the device. Good results start by labeling the source of every fact.

That makes a urology trial less about eloquence and more about provenance. The sentence may be perfect. The practice still needs to know who observed the finding and where the number came from.

> **Key takeaways**
>
> - Spoken histories and plans are the easy fit; device, image, pathology, and procedure facts need source checks.
> - Dictate findings as findings, not as instructions for the scribe to infer.
> - ICD-10 output is a suggestion. CPT, E/M, medical necessity, orders, and claims remain outside the module.
> - Judge a trial by corrections and review time across several visit shapes, not by one clean demo note.

## Start with provenance, not a template

Urology mixes conversation with data produced somewhere else. A hematuria workup may touch history, urinalysis, imaging, cystoscopy, and pathology. A surveillance visit pulls together the new result and several old ones. A procedure note records what the clinician observed and did.

The American Urological Association's AQUA Registry describes both structured and unstructured EHR information as part of the treatment journey and outcomes record ([AUA](https://www.auanet.org/documents/practices-resources/aqua/Value-of-AQUA.pdf)). That is a useful clue for scribe evaluation. A narrative tool handles unstructured words. It should not pretend those words arrived through a structured feed.

Put a source tag beside each trial-note fact:

| Source tag | Example | Safe scribe behavior |
|---|---|---|
| Patient said | Symptom course or treatment response | Draft the history, then let the clinician edit it |
| Clinician observed | Exam or cystoscopy finding | Record only what the clinician narrates |
| Device measured | Bladder scan or flow value | Include only a spoken value and verify it against the device |
| Report stated | Imaging, pathology, or lab result | Capture the clinician's summary and preserve the original report |
| Clinician decided | Assessment, follow-up, medication plan | Draft it for review; never execute the decision |

If a draft cannot survive those five labels, it isn't ready for the chart.

## The consult is the cleanest fit

New-patient and follow-up visits are mostly a conversation until the results enter. The scribe can draft the chief concern, symptom timing, prior treatment, relevant negatives that were actually discussed, and the urologist's assessment and plan. Longer histories are where ambient capture earns a fair trial.

Specific speech helps. Say "left flank pain" rather than "pain on this side." State that a value came from today's bladder scan or last month's report. If a caregiver answers part of the history, identify the speaker. The point is not to narrate for a machine all day; it is to remove the two-second ambiguities that become five-minute chart repairs.

Patient Square does not pull the prior chart into the scribe. If the longitudinal change matters, say it or add it during review. A draft built only from this visit should not quietly imply that it reconciled the full record.

## Tests remain reports, even when the note mentions them

The AIUM/AUA ultrasound guideline says the final interpretation should be included in the patient's medical record ([AIUM/AUA](https://www.auanet.org/documents/advocacy/news-center/urology.pdf)). A scribe is not that interpreting system. It can repeat the urologist's spoken account in the visit note, while the signed source report remains the authoritative artifact.

Use the same rule for urodynamics, pathology, and imaging. The draft may say, "CT urogram reviewed; clinician notes no upper-tract lesion." It should not claim to have opened the study. If the exact measurement matters, compare it with the report before signing.

This sounds fussy until two values disagree. Then provenance is the fastest route to the correction.

## Procedure days need a completeness card

A fluent procedure note can still omit one required local field. Build a card from the practice's approved template and keep it next to the scribe trial. The card might include indication, consent, preparation, procedure performed, clinician-narrated findings, specimens, complications, and disposition. Use the fields your organization and payer require.

The scribe drafts only the details spoken in the room or dictated immediately afterward. It does not observe the procedure. It should not fill a silent field with a normal default. Blank is safer than invented.

We think procedure day is the best stress test because it strips away the novelty. After the fifth cystoscopy, does the review stay quick? Do clinicians remember to say the nonvisual details? Does the note fit the approved template without a second rewrite? Those answers are worth more than a vendor's sample.

## The product boundary is plain

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For an established US urology group, Practice Copilot can run beside the existing record. There is no named-urology-EHR integration, cystoscope feed, imaging interpretation, or automatic chart filing claimed here. The [US pricing page](../../pricing/) also documents a bundled AI EHR from the Copilot plan, but we do not market it as a urology-specific test, procedure, or billing system.

ICD-10 suggestions come from the assessment the clinician stated. They are not CPT or E/M selections. The prescription output is a draft, not e-prescribing, and it does not query a PDMP or run a pharmacy transaction. Keep orders, coding, safety checks, and claims where authorized staff already perform them.

## Authentication is more than clicking sign

CMS says the treating practitioner signs a scribed entry to authenticate the document and the care provided ([CMS MLN](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/signature_requirements_fact_sheet_icn905364.pdf)). AMA policy says AI-generated medical-record content requires the physician's consent and final review ([AMA](https://policysearch.ama-assn.org/policyfinder/detail/cybersecurity?uri=%2FAMADoc%2FHOD.xml-H-480.931.xml)).

Translate that into a short urology review:

1. Match patient and encounter.
2. Check anatomy and laterality.
3. Compare every test value with its source.
4. Remove anything the clinician did not observe, read, or decide.
5. Confirm that the plan and medication draft say exactly what the clinician intends.

Then sign. Fast is fine. Automatic is not.

## Run the trial across a real week

Choose a new consult, a surveillance follow-up, and a procedure block. Add a fourth note from the visit type your group dislikes charting most. For each, count missing values, wrong anatomy or side, unsupported details, and edit minutes.

Also test the boring operational questions. Does the note export in a form your current EHR accepts? Can the practice delete or export a visit? What happens to audio? Patient Square says visit audio is processed in memory and discarded when the note is drafted; notes use encryption in transit and at rest; BAAs are available; and the SOC 2 Type II audit is in progress ([security details](../../security/)).

The winner is the tool that reduces writing without turning source-checking into a second job. If that sounds like the problem your group is trying to solve, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. We will show the draft and its limits on the same screen.

---

## AI Scribe for Ophthalmology: The Structured-Data Gap
https://patientsquare.com/us/blog/ai-scribe-for-ophthalmology/
Published 2026-09-14 · Tags: ophthalmology, ai-medical-scribe, clinical-documentation, ehr-workflow, specialty-practice

An ophthalmology scribe can draft the story of the visit, but it cannot read an OCT, populate a refraction grid, or replace an eye-specific EHR.

Yes, for the spoken part. It can draft the history, the ophthalmologist's narrated findings, the assessment, and the plan. It cannot inspect the eye, read an OCT or visual-field report, or collect measurements from an instrument. Those values enter the draft only when the clinician says them aloud.

An ophthalmology scribe can write the conversation. It cannot fill the rest of the eye chart by magic. The history, the ophthalmologist's spoken findings, the assessment, and the plan can become a draft. Visual acuity, refraction, pressure, drawings, OCT, fields, and imaging still belong in the systems that measured or stored them.

That dividing line matters more here than in a mostly narrative specialty. Buy a scribe for the words. Keep the ophthalmology record for the numbers and pictures.

> **Key takeaways**
>
> - A scribe drafts only what it hears; it does not inspect the eye or read a diagnostic image.
> - Laterality and device measurements need a deliberate spoken-and-review step if they appear in the note.
> - An eye-specific EHR remains the better home for refraction grids, drawings, image links, and longitudinal test data.
> - The signing clinician checks the draft. CMS treats that signature as the practitioner's authentication of the record.

## The eye chart has two different jobs

The first job is narrative. Why did the patient come in? What changed since the last visit? What did the ophthalmologist see, conclude, discuss, and plan? An ambient scribe is useful here because those facts pass through the room as speech.

The second job is structured and visual. The American Academy of Ophthalmology's data-standards work identifies visual acuity, intraocular pressure, pachymetry, visual-field results, and retinal nerve fiber layer measurements as distinct observations that an EHR may need to exchange or track ([AAO EyeWiki](https://eyewiki.aao.org/Glaucoma_Data_Standards)). An OCT image is not a sentence. Neither is a refraction grid.

Mixing those jobs creates bad expectations. A tool can produce a fluent note while leaving the measurements stranded somewhere else. Worse, it can make a dictated number look authoritative even when the clinician misspoke. The useful question is not, "Does the scribe know ophthalmology?" It is, "Which parts of this visit are actually spoken?"

## A spoken-versus-structured map

Use this map before a demo. It stops a polished sample note from hiding a poor fit.

| Visit material | A standalone scribe can draft it when spoken | Keep it in the eye system |
|---|---|---|
| Symptom history and interval change | Yes | Prior values still need chart review |
| Ophthalmologist's narrated exam | Yes, then verify laterality | Structured exam fields and drawings |
| Visual acuity, refraction, IOP | Only when someone says each value | Instrument or technician-entered fields |
| OCT, fundus image, visual field | Only the clinician's spoken interpretation | Original image, report, and serial comparison |
| Assessment and counseling | Yes | Final clinical judgment remains with the clinician |
| Medication discussion | A prescription draft can reflect the discussion | Ordering, safety checks, and transmission stay in the clinical workflow |

This is the original artifact worth carrying into procurement: circle every row that currently costs the ophthalmologist time. If most circles land in the right column, buy or fix the eye system first. If they land in the left column, a scribe trial is sensible.

## Laterality deserves its own test

Eye notes punish casual review. OD and OS are tiny strings with a large clinical difference. A pressure of 18 in the right eye and 28 in the left eye cannot trade places because the prose around them sounds plausible.

The AAO's 2026 registry specifications assume that laterality is recorded in the medical record, and its data standards treat right-eye and left-eye measurements as separate observations ([AAO EyeWiki](https://eyewiki.aao.org/Glaucoma_Data_Standards)). For a scribe trial, build a simple laterality check into every note: compare each dictated side and value against the technician sheet or device report before signing.

Don't ask the scribe to infer the side from context. Say it. "Right eye pressure 18, left eye 28" is safer input than "pressure is 18 and 28." The draft still needs checking, but the source sentence is no longer ambiguous.

## Patient Square sits beside the ophthalmology EHR

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For a US ophthalmology practice, the conservative setup is to keep the eye-specific EHR and run the scribe beside it. There is no claim here of an OCT feed, autorefractor connection, image interpretation, or named-EHR write-back. Review the draft, then move the finished narrative into the record yourself.

Practice Copilot does offer a bundled AI EHR from the Copilot tier, according to the [published US plans](../../pricing/). We don't present it as an ophthalmology system. A clinic that needs structured refraction, imaging links, or a drawing surface should preserve the specialty software that already does those jobs.

The scribe module returns ICD-10 suggestions and a prescription draft. It does not choose CPT or E/M codes, submit a charge, send a prescription, or decide what an image means. Those boundaries are not missing features tucked into a future promise. They are the line between drafting and practicing medicine.

## The sign-off is the control

CMS tells practitioners who use a scribe to sign the entry and thereby authenticate the document and the care provided; the scribe does not need to sign or date it ([CMS MLN](https://www.cms.gov/outreach-and-education/medicare-learning-network-mln/mlnproducts/downloads/signature_requirements_fact_sheet_icn905364.pdf)). AMA policy is equally plain that AI-generated medical-record content requires the physician's consent and final review ([AMA](https://policysearch.ama-assn.org/policyfinder/detail/cybersecurity?uri=%2FAMADoc%2FHOD.xml-H-480.931.xml)).

In ophthalmology, review should be mechanical before it becomes editorial. Check patient, eye, measurement, source, and plan. Five boxes. Only then fix the prose.

| Review box | One fast check |
|---|---|
| Patient | Correct encounter and speaker |
| Eye | OD, OS, or both matches what was examined |
| Measurement | Number and unit match the source |
| Source | Dictated finding is not presented as a device import |
| Plan | Orders and prescriptions reflect the clinician's decision |

We think this is a better trial score than asking whether the note "looks good." A handsome note with one swapped eye is a failed note.

## A four-visit trial exposes the fit

Run a short follow-up first. Then use a new consult, a visit built around test review, and a procedure discussion. Those four shapes reveal whether the scribe handles brevity, a long history, dense measurements, and consent language without flattening them into the same SOAP block.

For each visit, count corrections rather than trusting an impression. Mark laterality errors, omitted numbers, invented facts, and minutes spent editing. Compare those minutes with the time the same clinician normally spends writing. No vendor benchmark can replace that local result; the AMA's 2026 evaluation guide likewise puts clinical use, risk, effectiveness, workflow, and monitoring at the center of an AI assessment ([AMA](https://www.ama-assn.org/practice-management/digital-health/ai-specialty-collaborative-ai-evaluation-guide)).

Security belongs in the same trial. Patient Square processes audio in memory and discards it once the draft is ready. Notes are encrypted in transit and at rest, BAAs are available, and the SOC 2 Type II audit is in progress, as documented on the [security page](../../security/). Ask every vendor the same questions and put the answers in writing.

If narrative charting is the burden, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring one de-identified visit shape from each of the four categories. If device data is the burden, spend that hour with the ophthalmology-EHR team instead.

---

## AI Scribe for athenahealth: Inside athenaOne or Beside It
https://patientsquare.com/us/blog/ai-scribe-for-athenahealth/
Published 2026-09-12 · Tags: ai-scribe, athenahealth, ehr, integration

athenahealth built a scribe slot, not a scribe. How Ambient Notes, athenaAmbient, and a standalone tool differ, and which one your practice should run.

Two answers, and they're different products. Several scribe vendors run embedded inside athenaOne through Ambient Notes, so the note lands in the encounter without a paste step. A standalone scribe like ours runs beside athenaOne instead: it drafts the note and you copy or import it into the chart yourself.

On athenahealth, "AI scribe" almost never means one product. Ambient Notes is a slot inside athenaOne that several scribe companies plug into, and athenahealth is building a first-party scribe of its own. A standalone tool like ours sits outside all of that: it drafts the note, and you paste it into the chart.

So the real athenahealth question is whether to switch on something already embedded in the EHR or run something that sits outside it. Different purchases, different bills. The answer comes down to how much of your week actually happens inside athenaOne.

> **Key takeaways**
>
> - Ambient Notes launched in October 2024 with Suki and iScribe as the embedded models, and Abridge joined in February 2025.
> - At that point it was in limited release to more than 160,000 clinicians on the athenahealth network, with wider rollout through 2025.
> - athenahealth also announced its own scribe, athenaAmbient, in November 2025: user testing from February 2026, delivered through routine updates at no additional cost.
> - We are not an athenahealth Marketplace partner. No athenahealth API, no HL7 or FHIR write-back, no bidirectional sync. You paste or import the note.
> - A standalone earns its place when part of your documentation happens off athenaOne, or your patients speak more than one language, or you want a prescription draft you review and sign.

## athenahealth built a slot, not a scribe

This is the part most comparison pages get wrong, so it's worth getting exact.

athenahealth introduced Ambient Notes on October 30, 2024, with two ambient models available inside it: Suki and iScribe. athenahealth's claim at the time was that athenaOne is the only EHR supporting multiple ambient models at once, letting clinicians in the same practice run different ones ([Healthcare Innovation](https://www.hcinnovationgroup.com/clinical-it/electronic-health-record-electronic-medical-record-ehr-emr/news/55239802/athenahealth-unveils-ambient-notes-orthopedic-focused-ehr)). It shipped in limited release first, with general availability for athenaOne customers signposted for early 2025.

Then Abridge joined. On February 25, 2025, athenahealth and Abridge announced that Abridge's documentation would embed directly in athenaOne through Ambient Notes, reaching a network that at the time counted more than 160,000 clinicians in limited release, with wider availability rolling through the year ([athenahealth](https://www.athenahealth.com/press-releases/athenahealth-and-abridge-partner), [HIT Consultant](https://hitconsultant.net/2025/02/25/athenahealth-partners-with-abridge-to-bring-ambient-ai-to-ambulatory-care/)).

So if you're an athenaOne practice shopping for a scribe, start by looking at what's already switchable inside the chart you're paying for. Three embedded options, and the note lands in the encounter without anyone leaving athenaOne. That's a real advantage. We're not going to talk you out of it.

## And now athenahealth is building its own

In November 2025 athenahealth announced athenaAmbient, a first-party ambient scribe built into athenaOne rather than licensed from a partner. It drafts clinical notes, diagnoses, and prescriptions; it was set to enter user testing in February 2026; and athenahealth said it would reach customers through routine software updates at no additional cost ([TechTarget](https://www.techtarget.com/searchhealthit/news/366633988/Athenahealth-unveils-new-AI-native-EHR-capabilities)).

Read that last clause twice, because it's the whole competitive picture. A scribe that arrives in your next update, costs nothing extra, and writes into the chart you're already in is a very hard thing for any outside vendor to beat on convenience or price. If athenaAmbient covers your documentation, the honest recommendation is to use it.

What we'd add, and it isn't a knock: a tool that ships with your EHR moves on your EHR's schedule. Testing dates slip. Feature sets at launch are narrower than the announcement. If your charting pain is urgent, the timeline matters as much as the price.

## Where a standalone actually sits

Beside the chart. Never inside it, and never connected to it.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It runs on your phone or laptop, and it never logs into athenaOne.

You read the draft, correct what's wrong, and drop the finished note into the open athenaOne encounter, or export it and import it. The ICD-10 suggestions ride alongside so the codes are in front of you instead of behind a search box. They're suggestions. They don't set your E/M level and they don't post a charge.

The prescription draft is exactly that word. The scribe writes down the drug, the dose, and the instructions you discussed, so you're not retyping them. It doesn't screen for interactions, dosing, or pregnancy, and it isn't e-prescribing. You read it against the chart, you adjust, you sign, and you send it through athenaOne yourself. A draft an LLM wrote is still a draft an LLM wrote.

One thing happens well away from athenahealth: the visit audio is processed in memory and discarded the moment the note is drafted. No archive, ours or yours. The note is what survives. Encryption, BAA availability, and our SOC 2 Type II status (audit in progress) are laid out on the [security page](../../security/).

## The Marketplace question, answered plainly: we're not in it

athenahealth runs a Marketplace program: vetted partner apps that integrate with athenaOne through its published APIs, some embedded in the interface, some exchanging data behind it ([athenahealth](https://www.athenahealth.com/solutions/marketplace-program)). It's one of the more open partner programs among the big ambulatory EHRs, and plenty of good tools reach athenahealth customers through it.

We're not one of them. No athenahealth API on our side, no HL7 or FHIR write-back, no bidirectional sync, no Marketplace listing. We could go build one. We chose not to, and we think it's the right call: the moment a scribe depends on one EHR's partner program, it stops being useful to the clinician who documents in two systems, or who might not be on athenahealth in three years.

The cost of that choice is a copy-paste step, every visit, forever. We'd rather name it than bury it. When another vendor tells you they "integrate with athenahealth," ask which thing they mean: embedded in Ambient Notes, listed in the Marketplace, or a paste window with confident marketing. All three exist. Only the first two put the note in the chart for you.

## Three shapes, side by side

| | Embedded in Ambient Notes | athenaAmbient (first-party) | Standalone beside athenaOne (ours) |
|---|---|---|---|
| **How the note reaches the chart** | Written into the encounter | Written into the encounter | You paste or import it |
| **Who you buy from** | The scribe vendor, through athenahealth | athenahealth | Us, directly |
| **Cost shape** | Per the vendor's contract | No additional cost, per athenahealth | Published per-clinician price |
| **Works off athenahealth** | No | No | Yes, EHR-agnostic |
| **Available without athenahealth** | Varies by vendor | No | Yes |
| **Prescription draft you review and sign** | Per that vendor | Drafts prescriptions in-chart | Yes, a draft only, never sent to a pharmacy |
| **ICD-10 handling** | Per that vendor | Per athenahealth's tooling | Suggestions you confirm |
| **Multilingual capture** | Per that vendor | Per athenahealth's build | Yes, note always returned in English |
| **Visit audio retention** | Per that vendor's policy | Per athenahealth's policy | Never stored, in-memory only |

The column that wins depends on one number: what share of your documentation happens inside athenaOne. At 100%, the left two columns are better products for you. Below about 70%, the right column starts covering visits the other two can't reach at all.

## When the in-EHR option is simply the better buy

Turn on what's already there if athenaOne is where your day happens. Every visit documented in the chart, no second location on a different system, no telehealth notes kept outside, patients speaking the language your build handles, and no appetite for a second vendor relationship. For that practice, an embedded model in Ambient Notes or athenaAmbient when it lands is the right answer, and paying us to draft a note you then paste in by hand would be paying twice for less convenience. Don't do it.

There's a budget version of the same call. If athenaAmbient really does arrive at no additional cost, an independent practice watching every line item should wait for it before signing anything. We'd rather you did that than churn off us in month three.

## Where a standalone still earns its keep

The clearest case is a week that isn't all athenaOne. A satellite clinic that came in on a different EHR after an acquisition. Nursing-home rounds. A locums shift. Telehealth you document outside the main system. An embedded scribe covers the athenaOne slice and stops there, while a standalone doesn't notice the boundary at all.

Language is the second one. The scribe can capture a visit spoken in another language and return the note in clinical English for the clinician to review and sign. Test that on your actual patient languages during a trial, not on a demo script that was written to pass.

Then there's the prescription. Note-only tools stop at the note; ours writes down the medication you discussed so you're reviewing text instead of retyping it. The safety call stays exactly where it is today, with you.

The last one is the quiet one. If the percentage-of-collections math is part of why you're reading this, a scribe bolted into athenaOne becomes one more thing to unpick later. Our [athenahealth cost breakdown](../athenahealth-ehr-cost/) runs that math, and the [migration guide](../switch-from-athenahealth/) covers what leaving actually takes. A tool that travels with the clinician instead of the chart is one fewer item on that list.

Two or more of those describing your practice? Then settle it on a real clinic day rather than a slide deck. The price ladder with no asterisks is on the [pricing page](../../pricing/), starting at $79 per clinician per month on the annual Assist plan.

## Four questions before you switch any scribe on

1. Which shape is this, exactly: embedded in Ambient Notes, a Marketplace app, first-party athenahealth, or a standalone paste window? Make the vendor point at one.
2. What happens to it if you leave athenahealth? An embedded tool leaves with the EHR. A standalone doesn't care.
3. What's the total bill, including anything that rides on your athenahealth contract? "Included" and "no additional cost" are worth confirming in writing.
4. Where does the visit audio go, and when is it deleted? Accept a one-sentence answer with a timeline. Ours: processed in memory, discarded at note draft, no archive.

## The honest verdict

If you're an athenaOne-only practice, use what athenahealth gives you. Ambient Notes already puts three vendors a toggle away, athenaAmbient is arriving inside the price you already pay, and for a practice that never documents anywhere else, in-chart beats copy-paste. We'd say the same thing to a friend running a five-provider clinic.

Pick a standalone when the EHR isn't the whole story: split systems, multiple languages, visits captured away from a workstation, or a real chance you won't be on athenahealth in a few years. That's the buyer we built for, and it's a bigger group than the athenahealth-shaped pages on the internet suggest. For how the same trade plays out on other systems, our [any-EHR export guide](../ai-scribe-any-ehr-export/) walks the workflow across athenahealth, Epic, and the rest, and the [Epic version of this page](../ai-scribe-for-epic/) covers the equivalent choice there.

If you're genuinely split, book a short demo and judge the note against your own visit types, then run the 7-day trial on a week you'd normally spend charting at 8pm. The paste step is either a nuisance you forget by Wednesday or a dealbreaker by Tuesday. Only your own clinic tells you which.

---

## AI Scribe for FQHCs and Community Health Centers
https://patientsquare.com/us/blog/ai-scribe-for-fqhc-community-health-centers/
Published 2026-09-11 · Tags: ai-scribe, fqhc, community-health

AI scribe for FQHC visits drafts the English note across high-volume, multilingual panels. What it fixes, what it won't touch (UDS, sliding-fee), how to decide.

Not directly, and be skeptical of anyone who says it will. UDS pulls structured, coded data from your EHR across a full reporting year. A scribe drafts one visit note at a time in English, and the clinician signs it. A cleaner, more complete note can make the coded data behind UDS more reliable, but the scribe does not build the report or submit anything to HRSA.

If you run a community health center, a scribe fixes exactly one thing: the note. It listens to the visit, drafts a structured SOAP note in English, and hands it back for the clinician to review and sign. It does not build your UDS report, it does not touch sliding-fee eligibility, and it does not chase down a 330-grant requirement. Knowing that boundary is most of the decision.

The reason a scribe is even on the table at an FQHC is volume. HRSA-funded health centers served over 31 million patients in 2023, the most in the program's history, and more than 90% of those patients had incomes under 200% of the Federal Poverty Guidelines ([HRSA press release, 2023](https://www.hrsa.gov/about/news/press-releases/new-data-health-center-patients)). That's a lot of visits per provider, on a payer mix that leaves thin margins for anything that doesn't earn its keep.

> **Key takeaways**
>
> - A scribe drafts the clinical note only. UDS reporting, sliding-fee docs, and enabling-services encounters stay with your staff and EHR.
> - Notes come back in English, but the scribe can capture a visit spoken in another language, which matters on a multilingual panel.
> - Rotenstein et al. found practice in a community health center was associated with *lower* EHR time, so the note burden here is real and worth measuring.
> - About 30% of primary care providers at FQHCs report burnout (Quigley et al., 2025); documentation load is one lever you can actually pull.
> - ICD-10 codes are suggestions the clinician confirms. Nothing auto-codes, and nothing posts a charge on its own.

## Where the documentation load actually sits

A health-center Tuesday isn't a boutique-practice Tuesday. Panels run long, patients arrive with stacked chronic conditions, and the visit is often the only touch that month. Somebody still has to write all of it down.

Here's the part people miss. Rotenstein and colleagues, in a 2023 JAMA Network Open study of primary care physicians, found that practicing in a community health center was one of the factors *associated with lower* EHR time ([Rotenstein et al., 2023](https://pmc.ncbi.nlm.nih.gov/articles/PMC10665969/)). Team-based care and shared workflows help. But the same study pegs median EHR time at 36.2 minutes per visit across the sample, with real after-hours "pajama time" on top. Even a below-average note burden at a health center is a heavy note burden.

That's the wedge a scribe fits into. It doesn't reorganize your care team. It takes the typing off the clinician's plate so the 8pm charting session gets shorter or disappears. On a high-volume panel, that's the difference between a provider who signs out at 6 and one who's still documenting at home.

Burnout is the other half of this. Quigley et al. reported roughly 30% of primary care providers at the FQHCs they studied experienced burnout, with high patient demands and thin leadership support named as drivers ([Quigley et al., 2025](https://link.springer.com/article/10.1007/s11606-025-10154-z)). Documentation isn't the whole story there. It is, though, one of the few contributors you can address with a tool instead of a hiring plan you can't afford.

## What a scribe does not do at a health center

This is where honest matters more than persuasive, because the mismatch here burns real money.

**UDS reporting.** The Uniform Data System is a full-year, structured pull from your EHR covering patient characteristics, services, clinical processes, outcomes, staffing, and revenue ([HRSA UDS Data Overview](https://data.hrsa.gov/topics/healthcenters/uds/overview)). A scribe drafts one note at a time. It has no view of your reporting year and files nothing with HRSA. If a vendor's pitch implies the scribe "handles UDS," slow down and read the fine print.

**Sliding-fee and enabling-services documentation.** HRSA's Compliance Manual requires a board-approved sliding fee discount schedule, evaluated at least every three years, that gives a full discount at or below 100% of the Federal Poverty Guidelines and no discount above 200% ([HRSA Compliance Manual, Chapter 9](https://bphc.hrsa.gov/compliance/compliance-manual/chapter9)). Enabling services (transportation, case management, interpretation) get documented under program rules too ([HRSA Compliance Manual](https://bphc.hrsa.gov/compliance/compliance-manual)). None of that is a clinical-note task. Your intake staff and EHR own it. The scribe stays in its lane.

**330-grant and PCMH program requirements.** These live at the organization and workflow level, not inside a visit note. A scribe can make the underlying clinical documentation cleaner, which is helpful downstream. It is not a compliance product.

So the fair claim is narrow: a scribe improves the raw material (the note and the codes behind it), and better raw material makes the coded data that eventually feeds UDS more trustworthy. It does not do the reporting.

## The multilingual reality

Health centers see patients in a lot of languages. A single afternoon might run Spanish, Haitian Creole, Vietnamese, and English, sometimes with a family member or a phone interpreter filling gaps.

A scribe helps here in a specific way. It can capture a visit conducted in another language and draft the note in clean clinical English for the clinician to review and sign. The output is always English. So is the point: the provider gets a usable note out of a Spanish-language visit without stopping to type it in real time. If an interpreter is on the call, the scribe captures that too.

We'll be blunt about the limit. "Multilingual" with no named language list is marketing, and accents, cross-talk, and a relative answering half the questions are genuinely hard for any speech model. Don't take a vendor's word for it. Run a trial on your actual patient languages, on a real clinic day, and read the drafts yourself before you decide.

## Where Patient Square fits, and where it might not

AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It's one module of a broader Practice Copilot, which matters at a health center because you're rarely buying a single point tool; you're deciding what fits the whole operation.

A few things line up with FQHC realities. The scribe captures non-English visits and drafts the English note, which fits a multilingual panel. It processes visit audio in memory and does not retain it, so there's no growing archive of patient recordings to secure or explain to your board. ICD-10 comes back as suggestions the clinician confirms, never auto-coded and never posting a charge, which keeps a human on the codes your revenue and quality data depend on. Notes are yours to copy into or export to your EHR; we don't claim a direct integration, so factor a copy-paste or export step into the workflow.

Now the honest counterweight. If your clinicians already finish notes fast, or your panels are light, the time returned may not clear the cost of a per-clinician subscription on a tight budget. If your bottleneck is front-desk coverage, interpretation capacity, or care-coordination staff, a scribe won't touch it, and you'd get more from spending there first. And if you need something that pushes structured data straight into your EHR without a manual step, that's a different requirement than what an ambient scribe delivers today.

## Deciding it, on a health-center budget

Start with one number: how much after-hours charting your providers actually do now. If it's real and it's daily, the case is strong. If it's already minimal, the case is weak, and no demo should talk you past that.

Then run a paid trial the way you'd run it in production. Put it on a couple of your busiest clinic days, across your actual patient languages, and have the clinicians who'll use it read the drafts and time their sign-off. Watch the ICD-10 suggestions on a few complex chronic-care visits, since that's where coding accuracy earns or loses you money. If you want to see it against your real Tuesday, book a demo and bring your hardest visit types to the call; our [pricing](../../pricing/) is published per clinician so you can model it against your provider count before you commit.

For the underlying mechanics of ambient documentation, the [what-is-an-AI-medical-scribe](../what-is-an-ai-medical-scribe/) explainer covers how the note gets built and what "review" really means when you're deep in a panel. If you're weighing this against a bigger system change, [AI scribe vs. a new EHR](../ai-scribe-vs-new-ehr/) lays out why the two aren't the same purchase. And if audio handling is a board-level question, our [security page](../../security/) spells out how visit audio is processed and discarded.

The short version: a scribe is a narrow, useful tool at a health center, not a program solution. Buy it for the note. Measure the note. Leave UDS, sliding fee, and your 330 requirements exactly where they already live.

---

## AI Scribe for IVF Clinics in India: Cycle Documentation
https://patientsquare.com/in/blog/ai-scribe-for-ivf-clinics-india/
Published 2026-09-11 · Tags: specialty, ai-scribe, ivf, fertility

An ambient AI scribe for IVF and fertility clinics in India: every cycle conversation becomes a clean English note. From ₹1,599/mo + GST per doctor.

Yes, and frequent short visits are where flat pricing earns its keep. The scribe drafts a structured note about two minutes after each visit, and there's no per-note charge, so a stimulation phase that brings a patient in several times in a week adds nothing to the bill. Every monitoring conversation still ends up documented.

An IVF cycle is one clinical story told across a dozen or more conversations: the work-up, the monitoring reviews, the counselling before retrieval, the transfer, the call that follows the two-week wait. AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Every conversation in the cycle becomes a clean English note. Pricing starts from ₹1,599 per doctor per month on the annual Assist plan, plus 18% GST (about ₹1,887 all-in), with unlimited notes and no per-note metering. Copilot and Autopilot add a bundled AI EHR, WhatsApp, and receptionist and follow-up automation as you move up.

> **Key takeaways**
>
> - Every consult in a cycle gets a structured English note about two minutes after it ends, monitoring reviews included.
> - Counselling conversations, often the longest in the building, become records instead of memories.
> - From ₹1,599/mo per doctor (annual Assist, ex-GST) with unlimited notes: a stimulation week with three reviews costs nothing extra.
> - The ART (Regulation) Act, 2021 put fertility clinics under a registration and record-keeping regime. Contemporaneous notes are the raw material.
> - A scribe is not clinic-management software. Different jobs; most IVF clinics will run both.

## One cycle, a dozen conversations

Fertility medicine has an unusual documentation shape. Most specialties document encounters; an IVF clinic documents a narrative arc. Two patients, not one. A work-up that ranges across years of history. Then a cycle whose monitoring phase can put the couple in your clinic several times in a single week, each visit short, each one carrying a decision.

Here's what usually happens to that arc on paper: the work-up gets a solid note, the monitoring visits get two-line entries, and the counselling conversations, the longest and most consequential talks in the building, often get nothing beyond a signed consent form. The story exists in the doctor's memory and the embryologist's worksheet, and in between sits a gap.

If that gap sounds familiar, book a demo and watch a fertility consult turn into a structured note in real time.

## The cycle-stage documentation map

Map the cycle by what's said at each stage and what the note has to carry, and the scribe's job gets concrete.

| Cycle stage | The conversations | What the note has to carry |
|---|---|---|
| First consult and work-up | Two histories, prior attempts, investigations planned | Both partners' accounts, findings discussed, the agreed plan |
| Stimulation and monitoring | Short, frequent reviews | Findings as discussed, adjustments as spoken, next visit |
| Before retrieval | Procedure counselling, questions, expectations | What was explained, what was asked, what was decided |
| Transfer | Day-of counselling and instructions | Instructions given, plan for the wait |
| Outcome and next steps | The result conversation, options ahead | Outcome discussed, choices laid out, follow-up agreed |

Read the right-hand column again: almost all of it is spoken material. That's the point. An ambient scribe drafts each of these notes from the conversation itself, at the visit, in the same structure every time. It documents the cycle; it doesn't run it. Scheduling, stimulation charts, and the embryology lab stay in the systems built for them.

## The counselling visit is the longest conversation in the building

A retrieval or transfer counselling session can run past half an hour, and it's dense: what the procedure involves, what the chances honestly look like, what happens if the news is bad. Couples ask questions in whichever language reaches first. Hindi to English and back within one sentence is normal, and so is a third language when a parent joins.

The scribe listens through all of it, in English, Hindi, and 20-plus Indian languages including code-mixed speech, and drafts a clean clinical English note of what was explained and decided. Months later, when someone asks "were we told this?", the answer is in the record instead of in recollection. In a specialty where outcomes disappoint often and emotions run high, that written trail protects both sides; [our post on records as medico-legal defence](../ai-scribe-medico-legal-documentation-india/) goes deeper on why.

## A scribe is not IVF clinic-management software

Worth stating plainly, because the two get shopped together. Clinic-management systems for fertility practices handle appointments, cycle scheduling, packages and billing, and lab paperwork. We compared the Indian options honestly in our [IVF clinic management software roundup](../ivf-clinic-management-software-india/); if that's the purchase you're researching, start there.

The scribe solves the problem those systems leave alone: the conversation-to-note gap. It runs standalone, needs no integration project, and hands over an EHR-ready export (PDF · HL7 · FHIR) for whatever system you already run. Most fertility clinics end up wanting both, and we think that's the right instinct: one system to run the clinic, one tool to make sure the clinical conversations survive as records. When the record side itself needs an upgrade, the bundled AI Copilot EHR arrives at the Copilot tier without a separate migration.

## The ART Act backdrop

Since the Assisted Reproductive Technology (Regulation) Act, 2021, fertility clinics in India operate under a registration regime with record-keeping duties attached, overseen through a National Registry. This post isn't legal advice, and the scribe isn't a compliance product. But the direction is one-way: fertility care is becoming more documented, not less.

Contemporaneous notes, drafted at the visit rather than reconstructed at week's end, are the raw material every record obligation builds on. Structured, dated, in consistent clinical English, exportable on demand. Starting there beats retrofitting.

One more honest line while we're here: ABDM integration is on our roadmap, not live. If ABHA-linked records are a hard requirement for your clinic this quarter, verify every vendor's actual status, ours included.

## What an IVF practice pays

Per doctor, flat. Not per cycle, not per note, not per patient.

On annual billing, Assist is ₹1,599/mo ex-GST, ₹1,887 with 18% GST: the scribe, ICD-10 suggestions, prescription drafts, and scheduling. Copilot at ₹2,399/mo adds the bundled AI Copilot EHR plus WhatsApp messaging. Autopilot at ₹3,999/mo adds the AI Receptionist and AI Follow-ups. Unlimited visits at every tier, so the monitoring-heavy weeks of a stimulation phase cost exactly nothing extra. Full details on [the pricing page](/in/pricing/).

For the gynaecology and obstetrics side many fertility practices also run, [the gynaecology scribe post](../ai-scribe-for-gynaecology-clinics-india/) covers that workflow separately.

Audio, for the record: processed in memory, discarded once the note is drafted, never stored. Handling is built to DPDP Act 2023 standards, consent-first and purpose-limited, detailed on [the security page](/in/security/). In a specialty this private, that design choice is load-bearing. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Run the 7-day trial across one full week of a cycle: work-up, monitoring, counselling. If the notes aren't ones you'd sign, you'll know fast. Book a demo to start with a real consult instead of a sales deck.

---

## AI Medical Scribe for Rheumatology: RA & Lupus Notes
https://patientsquare.com/us/blog/ai-scribe-for-rheumatology/
Published 2026-09-11 · Tags: rheumatology, ai-medical-scribe, ra-notes, dmard-documentation, clinical-documentation

An ambient AI scribe drafts rheumatology notes for RA, lupus, and gout from what you say about joint counts, DAS28, and DMARD changes. You review and sign.

No. The scribe has no memory of prior visits. If you want the DAS28 trend in the note, say it out loud during the visit, for example that the score fell from 5.1 to 3.2 since starting methotrexate. Then the scribe captures the trend you narrated.

Rheumatology is a long game. You watch a rheumatoid arthritis patient across years of DMARD changes, read a lupus flare against a dozen prior visits, and reason about a gout patient's urate over time. Half the visit is a running list of medications with monitoring attached to each. An ambient AI medical scribe drafts your RA, lupus, gout, and psoriatic arthritis notes from what you say during the visit, then hands the draft back about two minutes after the patient leaves. Here is the catch up front: the scribe has no memory of the last visit, so any trend you want in the note is a trend you speak. You review the draft, confirm the coding, and sign.

> **Key takeaways**
> - The scribe drafts rheumatology notes plus ICD-10 suggestions about two minutes after the visit; you review and sign.
> - It has no memory of prior visits, so DAS28 history, DMARD escalation, and disease-activity trends must be spoken during the visit.
> - It captures joint counts and disease-activity scores from your dictation. It does not examine the patient or calculate a score.
> - The prescription draft reflects the dose you dictated; monitoring and toxicity checks stay your call, since the scribe does not screen labs.
> - Audio is discarded the moment the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## How an ambient scribe fits a rheumatology visit

A rheumatology follow-up has a shape. You ask how the joints have been, run a joint count, gauge disease activity, and review the medication list against what the labs are doing. You decide whether the current DMARD is holding, whether to escalate, whether a biologic is next, whether an infusion is due. Then you set the monitoring interval and the follow-up.

The scribe listens through all of it. When you say the DAS28 is 3.2 and the patient has moved from moderate to low disease activity on methotrexate, that goes in the note. When you count five tender and three swollen joints and name them, that lands in the note. When you decide to add a TNF inhibitor because the methotrexate has plateaued, the plan reflects it. Two minutes after the patient leaves, you have a draft.

Because the story is longitudinal, your narration during the visit is what builds the note. The scribe carries nothing forward and infers nothing about where the patient was six months ago.

## The no-memory design and the disease-activity trend

This is the part that changes how you dictate in rheumatology. A DAS28 of 3.2 tells you almost nothing on its own. It matters because it was 5.1 before you started treatment, and now the patient is close to remission. The scribe does not know that. It has no memory of the prior visit and no view into your flowsheet.

So the habit is to speak the arc. Say the DAS28 came down from 5.1 to 3.2 over the last four months on methotrexate, and the trend, the drug, and the response are all in the note because you said them. Leave it out and the note holds only the single number you mentioned this visit.

You are probably already saying most of this to the patient. "Your disease activity has dropped from 5.1 to 3.2 since we started the methotrexate, which is real progress, so I want to hold the current dose and recheck in three months." Say that out loud and the trend, your read on it, and the plan land in the draft. The scribe turns the conversation you are already having into the record.

## What a rheumatology scribe must capture

The vocabulary here is specific, and the scribe has to land it when you speak it. The American College of Rheumatology's treatment-to-target guidance leans on documented disease-activity measures and joint assessment, so getting these into the note is what makes the record defensible.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| Joint count | "Five tender, three swollen: both wrists, right MCP 2 and 3, left knee" | Tender and swollen counts with joints named |
| Disease-activity score | "DAS28 down from 5.1 to 3.2, low activity now" | Score and trend as narrated |
| DMARD management | "Holding methotrexate 20 milligrams weekly, tolerating well" | Current DMARD and dose |
| Biologic escalation | "Adding adalimumab, methotrexate has plateaued" | Escalation decision in the plan |
| Infusion note | "Rituximab infusion given, no reaction, premedicated per protocol" | Infusion event as stated |
| Extra-articular findings | "No rash, no serositis, no new sicca symptoms" | Review of systems as narrated |
| Medication monitoring | "Ordering CBC and LFTs for methotrexate, due this month" | Monitoring labs in the plan |
| Follow-up interval | "Recheck DAS28 and labs in three months" | Interval and orders |

The joint count and the disease-activity score carry weight for both management and coding. If you count the joints, name them, and state the score, the note supports the complexity of the visit. If you skip them, the scribe cannot supply them, because it never saw the patient's hands.

## Joint counts and scores, captured not calculated

Worth being blunt about this. The scribe does not examine the patient, it does not count joints, and it does not compute a DAS28 or CDAI. It records what you say. If you state five tender and three swollen joints and call the DAS28 low at 3.2, that goes in the note because you spoke it. If you assess an infusion patient and describe no reaction, the scribe writes down your assessment.

The judgment about disease activity, about whether the current regimen is working, about whether the patient is in remission, that is yours. The scribe documents your assessment. It does not produce it, and it does not know a CDAI from a coffee order unless you say the number.

## The prescription draft, and where monitoring stays

Rheumatology needs a hard line here, because so much of the specialty is high-stakes drug management. When your plan includes a medication change, the scribe drafts a prescription from what you said. If you start adalimumab or continue methotrexate at 20 milligrams weekly, the draft reflects that because you dictated it. It writes the order out so you are not retyping it.

What the scribe does not do is screen labs, check the dose, or flag toxicity. There is no logic that reads a rising transaminase and warns you off the methotrexate, no alert for a low white count before a biologic. DMARD and biologic monitoring, the CBC and LFTs, the TB screen before a TNF inhibitor, the decision to hold a dose, all of that is exactly the clinical judgment you make on every one of these patients, and it stays entirely with you. You read the draft, confirm the dose and the monitoring against the labs you are looking at, and sign.

The draft never goes to a pharmacy. There is no e-prescribing connection and nothing transmits. You act on it in your own workflow. Our post on [prescription draft safety](../ai-scribe-prescription-draft-safety/) covers how the draft works and why the clinician stays the safety check.

## ICD-10 suggestions for the rheumatology visit

After the visit the scribe offers ICD-10 suggestions from what you said. Common ones in this specialty:

| Condition | ICD-10 suggestion |
|---|---|
| Rheumatoid arthritis with rheumatoid factor | M05.- family |
| Systemic lupus erythematosus | M32.- family |
| Gout | M10.- family |
| Psoriatic arthritis | L40.5- family |

These are suggestions to speed your coding, not a final answer. RA coding in ICD-10 wants the site and often the serostatus and organ involvement, so you confirm the specificity. Lupus with organ involvement codes differently from lupus without, and that distinction is yours to resolve. Our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) has the detail.

## Security and ownership

Rheumatology records, with their long medication histories and immunosuppression, are protected health information and are handled accordingly. Audio is processed in memory and discarded the moment the note drafts, so no recording persists. Notes are always in English, they are encrypted in transit with TLS 1.2 or higher and at rest with AES-256, they belong to your practice, and you can export or delete them any time.

We maintain HIPAA compliant safeguards, offer a signed BAA to every customer, and have a SOC 2 Type II audit underway rather than complete. If compliance is a gate for you, start with the [security page](../../security/) and our detail on [BAAs and consent](../ai-scribe-hipaa-baa-consent/).

## Where rheumatology fit stands or falls

If you run full RA, lupus, and gout clinics and your notes are eating your evenings, the trade is clear. Speak the joint counts, the scores, and the DMARD reasoning you already discuss with the patient, and the note drafts for your review, with any prescription draft reflecting the dose you set. The fit is strongest for high-volume follow-up practice where the narration is already happening out loud.

Where it stands or falls: the scribe helps most if you narrate the trend and the numbers. If your visits are quiet, or you prefer to reason silently and type your own count, the gain is smaller, and an honest look at your own dictation habits will tell you which camp you are in. Before you commit to anyone, read [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) and our [comparison of AI medical scribes](../best-ai-medical-scribes/). If you co-manage inflammatory patients with primary care, the [primary care scribe overview](../ai-scribe-for-primary-care/) covers that side.

Pricing starts from $79 per clinician per month on the annual Assist plan, with unlimited visits and notes and a 7-day free trial to run it on a real clinic day. It steps up to Copilot at $119 and Autopilot at $199 as you add a bundled AI EHR, messaging, and receptionist and follow-up automation. On Assist the scribe works alongside your existing rheumatology EHR with no integration and no IT project.

Want to see it draft a real RA follow-up? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Pricing is on the [pricing page](../../pricing/).

---

## AI Scribe for Split/Shared and Incident-To Documentation
https://patientsquare.com/us/blog/ai-scribe-split-shared-incident-to-documentation/
Published 2026-09-11 · Tags: ai-scribe, coding, compliance, split-shared

How ambient AI notes capture who did what and how long for split/shared and incident-to visits under CMS substantive-portion rules. Scribe drafts; you attest.

For CMS, the substantive portion is more than half of the total time both practitioners spent on the visit, or a substantive part of the medical decision making. The billing practitioner has to have performed that portion. CMS planned a time-only definition years ago, postponed it, and has kept the time-or-MDM option in place through 2026. Check the current-year Physician Fee Schedule before you set policy.

The hard part of a split/shared or incident-to visit was never the software. It's the record. Two people touch the patient, one bills, and the note has to prove who did which part and, for split/shared, how long each of them spent. Get that wrong and it's a documentation denial or a clawback on audit. An ambient AI scribe helps here by writing down the who, the what, and the how-long as it happens. It does not decide who bills, and it does not attest for you.

That distinction runs through this whole piece. So let's be clear up front: the scribe drafts a note in English; your clinician reviews it, adds the attestation, and signs. The billing choice belongs to your clinician and biller, not the tool.

> **Key takeaways**
>
> - For CMS, the "substantive portion" of a split/shared visit is more than half the combined time, or a substantive part of the MDM. The billing practitioner has to have done that part.
> - Split/shared billing applies in facility settings (hospital inpatient, hospital outpatient, ED). Incident-to lives in the office and has its own separate rules.
> - CMS floated a time-only definition years ago, delayed it, and kept the time-or-MDM option through 2026. Check the current Physician Fee Schedule before writing policy.
> - The note must name both practitioners and be signed and dated by the billing professional. A scribe can draft all of that; the clinician verifies and attests.

## Split/shared and incident-to are two different rules people mix up

They get lumped together because both involve a physician and an advanced practice provider (an NP or PA) on the same patient. The billing logic is not the same, and neither is the setting.

Split (or shared) visits happen in a facility. Think a hospital inpatient floor, a hospital outpatient department, or the emergency department. A physician and an NPP each contribute to one E/M encounter, and one of them bills it. CMS spells this out in its MLN Matters guidance and the Physician Fee Schedule, and the facility-setting limit is explicit: shared services are billed only in a facility setting.

Incident-to is an office thing. It's how an established patient's follow-up, performed by an NPP under a physician's direct supervision, gets billed under the physician's NPI at the full rate. The conditions live in federal regulation at 42 CFR 410.26: a noninstitutional setting, an established plan of care the physician set, and direct supervision. As of January 1, 2026, that supervision can be met through real-time audio-video presence, not just being down the hall. Audio-only doesn't count.

Same two people, different building, different rules. A scribe that drafts the note doesn't change which rule applies. It just makes the note reflect what actually happened.

## What the note has to show for a split/shared visit

Start with the substantive portion, because that word is doing all the work. CMS defines it as more than half of the total time spent by the physician or NPP performing the visit, or a substantive part of the medical decision making. The practitioner who did the substantive portion is the one who bills.

Two things follow from that.

If you're billing on time, the note needs to support more than half of the combined time, and time both people spend jointly with the patient counts once, not twice. So a running record of who was in the room, doing what, for how long, is the documentation you actually need. Not a vague "seen with the resident" line.

If you're billing on MDM, the note has to show the billing practitioner performed the substantive part of the decision making. That's harder to capture as a timestamp and easier to capture as content: who ordered what, who weighed the differential, who made the call on the plan.

CMS also closed an old shortcut. You can no longer use history or exam alone to decide who did the substantive portion, because those aren't in the split/shared code definitions anymore. And critical care split/shared is a special case: it's time only, never MDM. If your ICU teams bill shared critical care, that's a rule your compliance staff should flag separately.

One more requirement from the CY 2026 Physician Fee Schedule: the record has to identify both individuals who performed the service, and the billing professional signs and dates it. Two names in the note, one signature that owns it.

## Where an ambient scribe genuinely helps, and where it stops

AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

For split/shared documentation, the useful part is the listening. When the physician steps in during an NPP's encounter, the scribe hears both voices and can draft a note that attributes who covered which parts of the assessment and plan. That attribution, who did what, is exactly the thing thin notes leave out and auditors ask about. The scribe writes it down while it's fresh, instead of the physician reconstructing it at 8pm.

Here's the line we won't cross, and you shouldn't let any vendor cross it either. The scribe does not:

- decide who bills the visit or whether split/shared applies,
- select the E/M level,
- calculate whether more than half the combined time was met,
- confirm that direct supervision or an established plan of care existed for incident-to,
- write or sign the attestation.

Those are judgment calls and factual assertions about your workflow. The ICD-10 references the scribe surfaces are suggestions for your clinician to confirm, not codes it posts. It never auto-codes and it never selects a level for you. On the split/shared attestation specifically, the scribe drafts the encounter narrative; the clinician adds the line that says "I personally performed the substantive portion" (or your compliance team's approved wording) and signs. We think that's the honest boundary. A tool that claims to attest for the clinician is claiming something no software should.

## Incident-to: the note is the easy part, the facts are the hard part

Incident-to trips people up because the documentation people worry about isn't really where the risk sits. The risk sits in the facts around the visit.

For an incident-to claim to hold, the patient has to be established, not new. There has to be a plan of care the physician set, not the NPP starting from scratch. And the supervising physician has to be present under the supervision standard (physically in the office suite, or, from 2026, via real-time audio-video). A perfectly written note doesn't create any of those facts. It can only reflect them.

So an ambient scribe helps by producing a clean, complete record of the follow-up encounter itself: what the patient reported, what the NPP found, what was done, how it maps to the existing plan. That's real value, a legible note beats a rushed one every time. What it can't do is establish that supervision happened or that the plan of care was already in place. Those are compliance facts your team confirms. If the requirements weren't met, no note fixes it, and you'd bill under the NPP's own NPI instead.

Run your incident-to setup past your compliance team and your payer. Commercial payers don't all follow Medicare's incident-to rules, and some don't recognize the concept at all.

## A quick reference: who owns what

| Task | AI scribe | Your clinician / biller |
|---|---|---|
| Capture who did which part of the visit | Drafts it from the conversation | Verifies it's accurate |
| Record time each practitioner spent | Notes what it heard | Confirms and totals it |
| Decide substantive portion (time vs MDM) | Does not decide | Decides |
| Select the E/M level | Does not select | Selects |
| Write the attestation statement | Does not write | Writes and signs |
| Confirm incident-to supervision / plan of care | Cannot confirm | Confirms |
| ICD-10 for the encounter | Suggests, never posts | Confirms and codes |

Read that table as the contract. Everything in the left column is drafting. Everything in the right column is judgment and legal attestation, and it stays with people.

## The honest verdict

An AI scribe is worth it here for one specific reason: it captures the who-did-what and how-long that split/shared documentation turns on, at the moment it happens, so your clinician isn't rebuilding the encounter from memory hours later. That's a real reduction in documentation risk and after-hours charting. It is not a compliance product. It doesn't attest, it doesn't bill, and it doesn't decide whether split/shared or incident-to even applies.

If your practice's problem is that split/shared notes are thin and inconsistent, a scribe is a strong fix for the note. If your problem is that the underlying facts (supervision, established plans of care, who actually did the substantive portion) are shaky, software won't save the claim, and you should sort out the workflow first.

When is skipping the scribe the better call? If your NPPs and physicians already document attribution and time cleanly, and the bottleneck is elsewhere in your revenue cycle, the note isn't your constraint and a scribe won't move your denial rate. Buy for the problem you actually have.

If you want to see how the draft handles a two-voice encounter and where the attestation line lands, book a demo and bring a real split/shared scenario. And nothing here is legal or billing advice; confirm your split/shared and incident-to policies with your own compliance team and payer, against the current-year Physician Fee Schedule.

For related reading, our note on [audio retention](../ai-scribe-audio-retention/) covers what happens to the recording (short version: audio is never stored), and the piece on [documentation and claim denials](../ai-scribe-claim-denials-documentation/) covers the narrow set of denials better notes actually touch. Pricing for the US plans is on the [pricing page](../../pricing/).

---

## AI Scribe for Diabetes Clinics in India: Follow-Up Notes
https://patientsquare.com/in/blog/ai-scribe-for-diabetes-clinics-india/
Published 2026-09-10 · Tags: specialty, ai-scribe, diabetes

An ambient AI scribe for diabetes clinics in India: serial follow-up notes in clean English from Hindi or Hinglish consults. From ₹1,599/mo + GST.

Yes. The scribe listens during each visit and hands back a structured SOAP note about two minutes after the patient leaves, so it matches a review queue that turns over every few minutes. Pricing is flat per doctor with unlimited visits and no per-note charge, so 40 review visits a day cost the same as 10.

Run a diabetes clinic and you write the same visit all day: sugars, weight, BP, a medication tweak, the next review date. AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It hears Hindi, Hinglish, and 20-plus Indian languages; the note always comes out in clean clinical English. Pricing starts from ₹1,599 per doctor per month on the annual Assist plan, plus 18% GST (about ₹1,887 all-in), with unlimited visits and no per-note metering. Copilot and Autopilot add a bundled AI EHR, WhatsApp, and receptionist and follow-up automation as you move up.

That last part matters more in diabetology than almost anywhere else, because your patients come back. Every month, for years.

> **Key takeaways**
>
> - India has an estimated 101 million people with diabetes (ICMR-INDIAB, 2023). Nearly all of that care runs on review visits.
> - A structured English SOAP note lands about two minutes after each patient, drafted from the conversation itself.
> - From ₹1,599/mo per doctor (annual Assist, ex-GST) with unlimited visits and no per-note metering: 40 reviews a day cost the same as 10.
> - Serial notes keep the same structure visit after visit, so a sugar trend is readable across months of records.
> - The scribe won't pull glucometer or CGM data, and ABDM integration is roadmap, not live. We say so up front.

## Diabetes care in India is a follow-up business

The ICMR-INDIAB study, published in The Lancet Diabetes & Endocrinology in 2023, put diabetes prevalence at 11.4% of Indian adults, an estimated 101 million people. A diagnosis is one visit. Management is decades of them: monthly reviews for the newly started, quarterly for the stable, weekly when something's off.

So a diabetology OPD, whether it's a solo sugar clinic in Indore or a multi-city chain, is a review machine. The consult itself is quick. A 67-country study in BMJ Open found the average Indian consultation runs about two minutes, and a stable diabetes review often fits that. The documentation doesn't. Forty reviews means forty notes, and they land on you after the last patient leaves.

If your OPD list is mostly reviews, book a demo and watch one get drafted live.

## The same note, twelve times a year

Here's the specific grind of diabetes documentation: every review restates the same skeleton. Interval history. Home readings. Weight, BP. Current medications. What changed and why. Next review date.

Write that skeleton by hand at 9pm and it thins fast. By the fifteenth note, "continue same" starts standing in for actual content. Thin serial notes fail you at exactly two moments: when a complication surfaces and you need the trail of what was tried and when, and when another doctor picks up the file and can't reconstruct the story.

A scribe changes what the note is made from. It drafts from the conversation you actually had, while you're having it, so visit twelve gets the same fidelity as visit one. You're not summoning details from memory at night; you're checking a draft two minutes after the patient walks out.

## The follow-up math on a 30-review day

No vendor table can know your clinic, so here's the arithmetic with every assumption visible. Time yourself for one session and swap in your own numbers.

| Line item | Typed by hand | With the scribe |
|---|---|---|
| Review visits in a day | 30 | 30 |
| Writing time per note | ~3 min | drafted for you |
| Review-and-sign per note | included above | ~30 sec |
| Documentation time per day | ~90 min | ~15 min |
| Per month, 26 OPD days | ~39 hours | ~6.5 hours |

Three minutes per typed note is conservative; most doctors we've watched take longer once the day's backlog piles up. Thirty seconds to review and sign is an assumption about you, not a product claim, so test it. Run the 7-day trial on your busiest review session and time both halves yourself.

The point isn't the exact figure. It's that documentation time in a follow-up specialty scales with visit count, and visit count is the one thing a diabetes practice can't reduce. Book a demo if you'd rather see the math run on your own OPD first.

## Serial notes a sugar trend can be read from

Continuity is the clinical argument, separate from the time argument. When every note follows the same SOAP structure, in the same clinical English, flipping back through six visits actually tells you something: readings drifting up since March, the metformin dose change in May, the complaint that appeared twice and got worse.

The scribe gives you that consistency without effort. The readings a patient reports and the adjustments you say out loud land in the note. ICD-10 suggestions come attached. And every note exports as an EHR-ready export (PDF · HL7 · FHIR) into whatever record system your clinic already runs.

To be clear about the boundary: the scribe writes consistent notes; it doesn't chart trends or store your longitudinal record. That's a record system's job. When you want visit history in one place under the same roof, the bundled AI Copilot EHR arrives at the Copilot tier. If you're weighing which to adopt first, [our take on scribe versus EMR ordering](../best-ai-scribe-vs-emr-which-first-india/) walks through it.

## "Sugar high hai": Hindi in, English notes out

A diabetes consult in India is rarely monolingual. The patient reports "khaali pet one-forty, khaane ke baad two-ten," asks about "sugar ki goli" in Hindi, and hears your answer in a mix. That sentence pattern breaks single-language dictation tools.

The scribe listens in English, Hindi, and 20-plus Indian languages, including code-mixed Hinglish, and follows the switches mid-sentence. What comes out is always a clean clinical English note, so the record reads the same whether the consult ran in Hindi, Tamil, or both. More on how that works in [our post on Hindi and Indian-language capture](../ai-scribe-hindi-indian-languages/).

## What a diabetes clinic pays when patients return monthly

We think flat pricing is the only honest model for a follow-up-heavy specialty. Per-note pricing quietly taxes exactly the practice pattern diabetology depends on: frequent, short, repeated visits.

Patient Square is flat per doctor, ex-GST, billed with 18% GST added. On annual billing: Assist at ₹1,599/mo (₹1,887 with GST) covers the scribe, ICD-10 suggestions, prescription drafts, and scheduling. Copilot at ₹2,399/mo adds the bundled AI Copilot EHR and WhatsApp messaging. Autopilot at ₹3,999/mo adds the AI Receptionist and AI Follow-ups. Every plan: unlimited visits, unlimited notes, no setup fee. The full ladder is on [the pricing page](/in/pricing/).

Running a one-doctor sugar clinic? [The solo-doctor cost breakdown](../ai-scribe-cost-for-solo-doctor-india/) does this math at your scale.

## Where the scribe stops

Three limits, stated plainly.

It doesn't pull data from glucometers, CGMs, or lab systems. Readings enter the note because someone in the room said them. If device integration is your core requirement, this isn't that product.

It doesn't make clinical calls. ICD-10 codes are suggestions, the prescription is a draft, and every note waits for your review and signature. Dose decisions stay where they belong.

ABDM integration is on our roadmap, not live. If ABHA-linked records are a hard requirement this quarter, check any vendor's actual certification status before signing. What ships today: notes born digital, encrypted in transit and at rest, audio processed in memory and never stored, handled to DPDP Act 2023 standards. Details are on [the security page](/in/security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

None of that requires trust in a blog post. Pick your heaviest review day, run the trial on it, and book a demo to see a diabetes follow-up note drafted from a real consult. If the note isn't one you'd sign, you'll know within a week.

---

## AI Scribe for Psychiatry Clinics in India: Consent First
https://patientsquare.com/in/blog/ai-scribe-for-psychiatry-clinics-india/
Published 2026-09-10 · Tags: specialty, ai-scribe, psychiatry

Consent-first psychiatry scribe: live session audio is discarded after drafting; uploaded recordings use a separate, consented retention mode.

Treat consent as required, always. Patient Square's data handling is built to DPDP Act 2023 standards, consent-first and purpose-limited, and psychiatric confidentiality carries its own legal weight under Section 23 of the Mental Healthcare Act, 2017. Ask out loud at the start of the session; this post includes a script you can use as-is.

Can an ambient AI scribe sit in a psychiatry consult without damaging the trust the whole session runs on? Yes, under two conditions: the patient agrees out loud before it listens, and live session audio is discarded when the note is drafted. Uploaded recordings use a separate retention mode with explicit consent. Capture runs only when you start it, and the note itself waits for your edit and signature before it becomes the record. Pricing is flat: ₹1,599 per doctor per month on annual billing, plus 18% GST, unlimited sessions.

> **Key takeaways**
>
> - Consent leads. Capture runs only when you start it, and this post includes a spoken consent script you can lift as-is.
> - Live session audio is processed in memory and discarded once the note drafts. Uploaded recordings use a separate retention mode with explicit consent.
> - Section 23 of the Mental Healthcare Act, 2017 already makes confidentiality your legal duty, digital records included. Your tools have to clear that same bar.
> - A 50-minute first assessment and a 10-minute review cost the same: flat ₹1,599/mo per doctor, annual, ex-GST.
> - If the patient declines, you dictate a summary after the session instead. Their voice never touches the system.

## The longest consults in medicine produce the hardest notes

The average Indian outpatient consultation runs about two minutes, per a 67-country study in BMJ Open. Psychiatry is the outlier, and every psychiatrist knows it: a first assessment commonly takes half an hour or more, and even follow-ups carry more conversation than most specialties' new-patient visits.

More conversation means more note. History of presenting illness, past episodes, family history, substance use, mental status, risk discussion, the plan and its reasoning. Reconstructing that from memory after a full OPD flattens it: the phrasing the patient used, the sequence things emerged in, the exact concern you flagged. Those details are the clinical record in psychiatry. They're also what evaporates first at 9pm.

An ambient scribe writes from the session itself, not from your recall of it. Book a demo and watch it draft a psychiatric note from a real conversation before deciding anything.

## Consent comes first. Here's a script.

We think spoken consent, at the start of the session, beats a clause buried in a registration form. It's better practice, it fits how DPDP-era consent is supposed to work, and it takes ten seconds. Use this or adapt it:

> "I use a documentation assistant that listens during our conversation and drafts my clinical note, so I can pay attention to you instead of a keyboard. Live session audio is processed in memory and discarded as soon as the note is written. Uploaded recordings are handled separately and require explicit consent. Are you comfortable with that?"

For a returning patient, shorter:

> "Same as last time, my notes assistant will be listening. Alright?"

Two rules make the script honest. First, it stays accurate: live session audio is discarded when the note is drafted, while uploaded recordings use a separate retention mode and require explicit consent. Second, a no costs the patient nothing. If they hesitate or decline, capture stays off, the session runs as it always has, and afterward you dictate a summary in your own words for the scribe to structure. The patient's voice never enters the system. That fallback is the difference between consent-first and consent-theatre.

## What happens to live session audio?

This is the question psychiatric patients, and psychiatrists, should ask hardest, so here's the plain answer. Live session audio is processed in memory and discarded the moment the note is drafted. Uploaded recordings use a separate retention mode with explicit consent. What persists from live capture is the note you signed.

Around that: TLS 1.2+ encryption in transit, AES-256 at rest, role-scoped and logged access, and handling built to DPDP Act 2023 standards, consent-first and purpose-limited. A SOC 2 Type II audit is in progress (that means in progress, not certified, and we won't blur the two). ABDM integration is on our roadmap, not live today.

The legal backdrop makes this non-optional. Section 23 of the Mental Healthcare Act, 2017 gives every person with mental illness a right to confidentiality covering their mental health, care, and treatment, and applies it explicitly to information stored in electronic or digital form. That duty is yours; any tool in the room has to be defensible under it. The receipts live on [the security page](/in/security/), and [our post on where patient data lives](../ai-scribe-data-residency-india/) covers residency in detail.

## What lands in the note, and who controls it

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

In psychiatry, the review step is the point, not a formality. Sessions surface material patients say in the worst hour of their month, and you decide how it's phrased in the permanent record. The draft gives you everything from the conversation, structured; you edit down or rephrase before signing. Nothing becomes the record without you.

Ownership follows the same line. Notes belong to your practice. Export or delete any visit, anytime, with EHR-ready export (PDF · HL7 · FHIR) into whatever record system you run. And the language flexibility sits on the input side: sessions in Hindi, Bengali, or code-mixed conversation come out as clean clinical English notes, every time. For how India's privacy regime compares to the US one your journals discuss, see [HIPAA vs DPDP for AI scribes](../ai-scribe-hipaa-vs-dpdp/).

## A 50-minute session costs the same as a 5-minute review

Psychiatry's session lengths make per-note or per-minute pricing hostile. Ours is flat per doctor: unlimited visits, unlimited notes, no metering of any kind.

On annual billing, Assist is ₹1,599/mo ex-GST, which is ₹1,887 with 18% GST. That covers the scribe, ICD-10 suggestions, prescription drafts, and scheduling. Copilot at ₹2,399/mo adds the bundled AI Copilot EHR and WhatsApp messaging; Autopilot at ₹3,999/mo adds the AI Receptionist and AI Follow-ups. No setup fee at any tier. The full comparison is on [the pricing page](/in/pricing/).

A useful test: take one heavy assessment day, run the 7-day trial on it, and compare the evening you get back against ₹1,887 a month. Book a demo if you want to see a long-session note first.

## When you should leave it off

Honesty about limits, because psychiatry deserves it more than any specialty.

When the patient declines: off, no persuasion, no second ask that session. When you judge a session shouldn't be ambient-documented at all, sensitive disclosures you'd rather summarize yourself: off, dictate afterward. The tool bends to your clinical judgement, not the reverse.

And it's a documentation tool, full stop. It doesn't advise on treatment, doesn't screen, doesn't interpret what the patient said. If your bigger problem is records scattered across years rather than notes per session, that's an EHR question first; [our take on which to adopt first](../best-ai-scribe-vs-emr-which-first-india/) is the honest version.

If the consent script, the live-audio handling, and the flat price add up for your practice, book a short demo. Bring your hardest documentation case to it.

---

## AI Medical Scribe for Pulmonology: COPD, PFT & Sleep Notes
https://patientsquare.com/us/blog/ai-scribe-for-pulmonology/
Published 2026-09-10 · Tags: pulmonology, ai-medical-scribe, copd-documentation, pft-notes, clinical-documentation

An ambient AI scribe drafts pulmonology notes from what you dictate about PFTs, COPD, and sleep visits. It never reads the tracing. You review and sign.

No. It captures the interpretation you dictate. If you say the FEV1 is 58 percent predicted with an obstructive pattern and a bronchodilator response, that's what the note reflects. The scribe does not read the spirometry tracing or interpret the study. The reading stays yours.

An ambient AI scribe drafts your pulmonology note from what you say during the visit, then hands the draft back about two minutes after the patient leaves. It documents the COPD interval history, the PFT read you dictate, the CPAP numbers you state. One boundary matters most: it never reads the spirometry tracing or interprets the study. That reading is yours. You review, confirm codes as suggestions, and sign.

> **Key takeaways**
> - The scribe drafts pulmonology notes about two minutes after the visit; you review and sign.
> - It captures the PFT and imaging read you dictate. It does not open the tracing or the CT. The interpretation stays yours.
> - COPD exacerbation counts, CPAP adherence hours, and inhaler regimens come from what you say, not from any device or portal.
> - ICD-10 suggestions like J44.1 or J45.909 are starting points you confirm, not auto-coded charges.
> - Audio is discarded the moment the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## Why pulmonology charting runs long

Think about a Monday clinic stacked with COPD follow-ups. Each one carries an interval history, a focused respiratory exam, a PFT summary to document, an inhaler regimen to reconcile, a smoking-status update, and a plan that often references the next spirometry or CT. That's a dense note, repeated fifteen times before lunch. Then the sleep-apnea slots in the afternoon each need the CPAP report transcribed. None of it is one-liner charting.

The burnout data lines up with that load. The AMA's 2023 Organizational Biopsy found 20.9% of physicians spend more than eight hours a week on the electronic record outside normal work hours, the after-hours "pajama time" that hasn't moved in years. If you've ever cleared a PFT backlog at 6pm from your kitchen table, you know the shape of that number.

An ambient scribe doesn't shrink the clinical thinking. It shrinks the gap between saying the finding and having it written down. A 2025 JAMA Network Open study of 263 ambulatory clinicians across six US health systems found burnout dropped from 51.9% to 38.8% after 30 days on an ambient scribe, with measured improvement in after-hours documentation time. That's a burnout signal, not a stopwatch. It points the same direction the arithmetic does.

## How an ambient scribe fits a pulmonology visit

You start the session when the patient sits down, then run the visit the way you always do. As you take the interval history and examine the patient, you speak your findings the way you'd dictate them: "dyspnea on exertion at one flight, no orthopnea, breath sounds diminished at the bases, no wheeze, oxygen sat 94 on room air." The scribe captures it.

When you pull up the PFT and read it, dictate the read aloud. "FEV1 58 percent predicted, ratio reduced at 0.62, obstructive pattern, positive bronchodilator response." That's your interpretation. The scribe writes it into the note as you said it. It isn't looking at the flow-volume loop or the numbers on the report. You did that. The scribe is a stenographer, not a technician.

AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

After the visit you stop the session. Two minutes later there's a draft: interval history, exam, your PFT and imaging summaries, assessment, plan. You read it, fix anything wrong, and sign. The note comes back in English, the audio is never stored, and the prescription output is a draft you review, never something sent to a pharmacy. Our [HIPAA, BAA, and consent guide](../ai-scribe-hipaa-baa-consent/) covers how the PHI handling works.

## The tracing boundary, stated plainly

This is the line that matters most in pulmonology. The scribe does not read the spirometry tracing. It does not interpret the flow-volume loop. It does not open the HRCT or measure a nodule. It has no imaging or waveform capability at all.

What it does is capture your words about the study. When you dictate that the spirometry shows an obstructive pattern with a bronchodilator response, or that the six-minute walk desaturated to 86 percent, the scribe writes down that you said it. The DLCO you read off the report goes in because you spoke it. The interpretation is yours, recorded as your reading.

Why labor this? Because a scribe that appeared to interpret a PFT would be making a clinical call it has no business making, and in pulmonology that call drives the diagnosis. A restrictive pattern versus an obstructive one, a reduced DLCO pointing toward ILD versus emphysema, these are your reads. Same holds for imaging: you state the HRCT pattern, the scribe records it. It does not read the CT and tell you what it means.

## What a pulmonology scribe has to capture

The vocabulary is specific, and a generic scribe that flattens it into primary-care language will frustrate you on every note. The draft has to come back in pulmonary terms.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| PFT read | "FEV1 58% predicted, ratio 0.62, obstructive, positive bronchodilator response" | Spirometry findings as dictated |
| COPD interval | "Two exacerbations since last visit, one needing prednisone, CAT score 22" | Exacerbation count and severity |
| Asthma control | "ACT score 17, uncontrolled, nighttime symptoms twice weekly" | Control status with score |
| CPAP adherence | "Usage 6.2 hours nightly, 88% of nights, residual AHI 3.1" | Adherence numbers as stated |
| Nodule follow-up | "8mm solid nodule RUL, stable, Fleischner 12-month interval" | Nodule detail and interval |
| ILD assessment | "HRCT shows UIP pattern per report, declining DLCO at 48%" | Your read of the pattern |
| Tobacco counseling | "10 pack-year history, still smoking half a pack, offered varenicline" | Cessation counseling detail |

If the draft reads like "patient has breathing issues," it wasn't built for you. Dictate the FEV1 as a number and the exacerbation count as a count, and the note carries them. Say "some shortness of breath" and that's what you'll get back, which is why stating the figure out loud is worth the two seconds.

## COPD and asthma follow-ups: narrate the trend

Chronic airway disease is about the delta between visits. A COPD note that just says "stable" is nearly worthless three months later. The scribe has no memory of the last visit. None. It only knows what you say in this room, so the trend has to be spoken. Say "two exacerbations since last visit, one requiring a prednisone burst, we added a LAMA and the CAT dropped from 26 to 22," and the note captures that arc. Say "doing about the same," and future-you gets nothing.

Asthma runs the same way. State the ACT score, the control category, the trigger pattern, and the step you're making. The scribe drafts it cleanly. What it can't do is pull the prior ACT forward or flag that control slipped since the last visit. That judgment is yours, at the review step.

We think this is a quiet upside. Dictating the interval trend out loud, while the patient is in front of you, tends to produce a sharper history than reconstructing it from a template at night. If you've read our [primary-care time-back model](../ai-scribe-for-primary-care/), the pulmonology math is similar with heavier note types stacked on top.

## Sleep visits, CPAP data, and the numbers you dictate

Sleep-apnea follow-ups are their own documentation pattern, and they're data-heavy in a specific way. The value of the visit lives in the adherence report: nightly usage, percent of nights used, residual AHI, mask-fit and pressure issues.

The scribe records those numbers when you read them aloud. Dictate "usage averaging 6.2 hours a night, used 88 percent of nights, residual AHI 3.1, morning headaches resolved," and the note reflects it. What it does not do is reach into the CPAP machine, the SD card, or the compliance portal and pull the data itself. There's no device connection. You read the report, you say the figures, the note captures your account of them. If your real bottleneck is getting adherence data to flow automatically from the DME portal into your chart, a scribe doesn't solve that. It's an interoperability problem, and a scribe doesn't touch it.

## Nodules, ILD, and tobacco cessation

Pulmonary nodule surveillance is where the imaging boundary and the longitudinal problem meet. The scribe has no prior scan on file, so the comparison you want in the note is the one you speak. State the current size, the prior size, the Fleischner or Lung-RADS interval, and your read of stability, and the note reflects it as your assessment. It never opens the CT. ILD visits work the same: dictate the HRCT pattern as reported and as you read it, the DLCO trend, the symptom trajectory, and the note carries your words rather than any interpretation of the scan.

Tobacco cessation counseling is the part that gets clipped in a rushed note, and it matters for the patient and the coding both. Dictate the pack-year history, current use, readiness to quit, and the intervention you offered, and the scribe drafts the counseling detail. Say it out loud and it lands; skip it and the note skips it too.

## ICD-10 for pulmonology: suggestions to start from

Pulmonology coding rewards specificity. COPD alone splits across J44.0, J44.1, and J44.9 depending on whether there's an acute exacerbation or a lower-respiratory infection. The scribe reads your dictated assessment and suggests codes to match: J44.1 for COPD with acute exacerbation, J45.909 for unspecified asthma, G47.33 for obstructive sleep apnea, J84.9 for unspecified interstitial lung disease.

Those are suggestions. They show up next to the draft. You confirm the ones that fit, change the ones that don't, and drop the rest. The scribe has no line into your billing system and posts no charges. And the specificity that drives correct coding also drives denials when it's missing: say "COPD" without the exacerbation detail and the suggestion comes back vague too, because the scribe only has what you gave it. Our [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/) walks through why review matters here.

## Inhaler teaching and the prescription draft

Pulmonology visits generate prescriptions constantly: inhalers, oral steroids, exacerbation antibiotics, cessation aids. When your plan includes one, the scribe drafts it from what you said, writing out the drug and dose so you don't retype the order.

It does not screen the draft for interactions or check technique. Inhaler teaching stays a hands-on task: you demonstrate, the patient teaches back, you correct. The scribe can document that you did it if you narrate it, but it can't do the coaching. The draft never goes to a pharmacy and there's no e-prescribing link. You review it, adjust what needs adjusting, and act on it in your own workflow. See our post on [prescription draft safety](../ai-scribe-prescription-draft-safety/) for why the clinician is the safety check.

## Security and ownership

Respiratory and sleep records are sensitive health data. Audio is processed in memory and discarded the moment the note drafts, so no recording of the visit exists afterward. Notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256, they belong to your practice, and you can export or delete them anytime. We maintain HIPAA compliant safeguards, offer a signed BAA to every customer, and have a SOC 2 Type II audit underway. If compliance gates your decision, start with the [security page](../../security/).

## When it earns a place, and when it doesn't

Pulmonology notes are long and the visits are cognitively heavy. If charting is stealing time you'd rather spend on treatment planning or with patients, the trade is worth weighing: narrate your PFT and imaging reads as you already do, and the note drafts for your review, with the reading always kept as yours.

One concession worth stating up front. If what you actually need is structured data flowing between your PFT lab, your sleep-lab database, and your EHR, a scribe isn't that purchase. It captures spoken clinical work and hands you an export. If you never want to say the read out loud, or if your bottleneck is device-to-chart automation rather than typing, this isn't the right buy for you yet.

Pricing starts from $79 per clinician per month on the annual Assist plan, then steps up to the Copilot and Autopilot tiers, which add a bundled AI EHR, messaging, and receptionist and follow-up automation. On the scribe-only plan it runs alongside your pulmonology EHR and hands you an export; it does not write back into your system. See our [comparison of AI medical scribes](../best-ai-medical-scribes/), the [cardiology scribe overview](../ai-scribe-for-cardiology/) if you co-manage cardiopulmonary patients, and [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before committing to any vendor.

Want to see the draft quality against your own PFT reads and CPAP notes? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical complex case. Pricing is on the [pricing page](../../pricing/).

---

## Hospital Information System vs HMS vs EMR (India)
https://patientsquare.com/in/blog/hospital-information-system-vs-hms-india/
Published 2026-09-10 · Updated 2026-08-30 · Tags: hospital-information-system, hms, emr, india, buyer-guide

HIS, HMS, HMIS, EMR: the terms overlap and vendors blur them. Here is what each label actually means for an Indian facility, and how to pick the right category.

HIS is often used for a broad clinical-and-administrative information estate, while HMS often describes an operational core such as registration, OPD/IPD, billing, or pharmacy. In Indian marketing the terms can overlap, so ask the vendor which modules are actually included, not which acronym they print.

Hospital Information System (HIS), Hospital Management System (HMS), and EMR are labels vendors use differently. HIS can describe a broad clinical-and-administrative information estate; HMS can describe an operational core; an EMR is the clinical record. This guide uses those as a buyer framework, then asks you to verify the modules and handoffs in the quoted configuration.

The repository's retained Google Ads Keyword Planner export dated 2026-07-01 records `hospital information system` at 2,400 India average monthly searches and `hospital management software` at 1,900. Its LOW competition label is paid-advertiser competition, not an organic difficulty score.

> **Key takeaways**
>
> - HIS, HMS, HMIS, and EMR are overlapping labels. Treat the module list and actual handoffs as the specification.
> - Match the required workflows to the facility, then verify them in the quoted configuration.
> - Many traditional deployments store clinician-entered notes. Ask how notes are created, reviewed, approved, and retrieved before assuming a documentation workflow.
> - Patient Square supports both record-system choices: its EHR/HIS can be the system of record, or either Copilot can work alongside an incumbent EHR/HIS.
> - Get price, scope, implementation, renewal, and data-exit terms in writing. The HIS/HMS label does not establish them.

_Sources: Irving et al., BMJ Open 2017._

## What does each label actually mean?

The acronyms sound like a tidy hierarchy. In practice, vendors print whichever one sounds biggest. Here's what they mean when someone uses them precisely.

A **Hospital Information System (HIS)** can mean the full software estate of a hospital: clinical record, registration, billing, pharmacy, lab, and radiology. Confirm which of those systems are included and how they connect.

A **Hospital Management System (HMS)** can describe an operational engine: registration, OPD queue, IPD/ward management, billing, revenue, and pharmacy. In Indian sales decks, HMS and HIS are often swapped, so do not read the acronym as a specification.

**HMIS (Hospital Management Information System)** is a common Indian variant. Most of the time it points at the same thing as HIS. In some government contexts it leans toward the reporting and analytics layer specifically. Treat it as a member of the same family.

An **EMR (electronic medical record)** is the clinical record itself: the patient's history, notes, diagnoses, prescriptions. An EMR can be a standalone product for a clinic, or a module inside a bigger HIS. It is the smallest, most specific of the four.

If you want the pure EMR-versus-EHR-versus-HMS breakdown at the clinic level, our [EMR vs EHR vs HMS explainer](../emr-vs-ehr-explained-india/) covers that decision directly, and [EHR vs HMS in India](../ehr-vs-hms-india/) takes the two-way version. This page is about the confusion one level up: when a hospital brochure says HIS but sells you an HMS, and you're not sure which you need.

## Why the labels blur, and why it costs you money

The blur isn't an accident. A bigger acronym justifies a bigger price and a longer contract. So a product that is really an OPD-and-billing HMS gets marketed as a full HIS, and a clinic that needed an EMR ends up in a hospital-scale enterprise deal.

The cost of getting this wrong runs both directions.

Overbuy, and you pay for lab and radiology information systems your clinic doesn't run, plus the setup time and annual maintenance that come with enterprise software. The modules sit unused. The renewal still arrives.

Underbuy, and you hit a wall the day you add inpatient beds or an in-house pharmacy and discover your clinic EMR was never built to coordinate departments. Now you're migrating mid-growth, which is the worst time.

The way out is to ignore the acronym on the cover and read the module list underneath it. Ask the vendor to name exactly which functions ship: registration, OPD, IPD, billing, pharmacy, lab, radiology, ABDM linking. That list, not the label, tells you what category you're actually buying.

## HIS vs HMS vs EMR: which fits your facility?

Match the category to what you run, not to the biggest brochure on your desk. Here's the decision laid out by facility type.

| Your facility | Starting category to verify | Workflows to test | Scope to question |
|---|---|---|---|
| Solo GP or single-doctor clinic | EMR + scheduling + billing | Registration, note, prescription, bill | Whether lab/radiology scope is actually needed |
| Multi-doctor OPD clinic, no beds | Clinic EMR / light HMS | Queue, notes, billing, pharmacy if required | Whether IPD and ward modules are needed |
| Small hospital with a few beds | HMS / HIS candidate | Registration, OPD, IPD, billing, pharmacy | Whether the quoted product supports its required departments |
| Multi-department hospital | HIS / HMIS candidate | IPD, OT, pharmacy, lab, radiology handoffs | Whether each module and interface is included |
| Any of the above, drowning in notes | A Copilot deployment choice | Patient Square record system or an incumbent path | Assuming replacement or retention before discovery |

_Decision matrix by facility type. Match the category to your scale, then choose whether Patient Square or an incumbent platform remains the record system._

The buyer question is not which label wins. It is whether the quoted product covers the required record, front-office, department, and documentation workflows, with demonstrated handoffs.

For the hospital-side detail, [hospital management system modules, explained](../hospital-management-system-explained/) walks through what each module in an HMS actually does, and the [best HIS software roundup](../best-his-software-india/) scores the enterprise options if you've decided you need the full stack.

## Where does ABDM fit across HIS, HMS, and EMR?

If your shortlist mentions "ABDM compliant," slow down, because that phrase hides three different things regardless of which acronym the product wears.

The National Health Authority certifies software against separate milestones. M1 lets a product create and verify an ABHA number and register the facility on the Health Facility Registry (HFR) and Health Professional Registry (HPR). M2 lets it share a patient's records as FHIR bundles on consent. M3 lets it pull records from other providers. A product that can create ABHAs but hasn't reached record-sharing is "ABDM-ready" in marketing and half-built in practice.

Certification is per-software, not per-facility. The vendor clears the sandbox once; each hospital or clinic registers itself separately. So the question is the same for a clinic EMR and a hospital HIS: which milestone has this product cleared in production, and can you see the NHA reference? Ask for the milestone number, not the badge on the pricing page. We think that one question sorts serious ABDM vendors from the ones printing a badge.

## A documentation workflow to verify separately

Many traditional deployments store a note entered by the clinician or staff. Do not assume that a HIS, HMS, or EMR label proves how the note is created, reviewed, approved, or transferred.

That sounds minor until you count the time. Average primary-care consultation time in India is about two minutes, per Irving et al.'s 67-country BMJ Open review, which put India near the short end of a huge global range. Two minutes to listen, examine, decide, and prescribe. On a ward round, the doctor moves bed to bed with a registrar taking notes on paper to be typed in later. Either way, the software holds the record but the human writes it, and the writing loses the race.

So one of three things happens. The note gets compressed to a line that says nothing useful later. Or it gets typed hours afterward from memory, blurred. Or it gets skipped, and the record has a registration and a bill but no clinical substance behind it. Define the record, retention, retrieval, approval, and audit requirements with appropriate current legal and operational advice, then test them in the quoted workflow.

Test the documentation workflow as its own requirement. A faster billing or registration screen does not demonstrate how a note reaches approval in the clinical record.

## Where Patient Square fits, for clinics and hospitals

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For a clinic, Practice Copilot can use Patient Square EHR from the Copilot tier as its system of record or work alongside an existing EHR. Its published India pricing is per clinician: ₹1,599 monthly-equivalent on annual billing for Assist, with 18% GST added; Patient Square EHR begins at Copilot, ₹2,399 monthly-equivalent on annual billing plus GST.

For a hospital, Hospital Copilot is a separate demo-priced product. A greenfield hospital can use the complete Patient Square HIS/EHR as its system of record. An established hospital can keep its current HIS/EHR and use Hospital Copilot alongside it. Hospital Copilot lists AI Medical Scribe, AI Receptionist, eRx, AI Follow-ups, WhatsApp, AI Copilot EHR, Claims Management, AI Discharge Summary, and Bed / IPD Management. Treat those names as product scope and confirm the workflows, interfaces, and ownership rules in procurement; they do not promise automatic write-back or unlisted departmental functionality.

The scribe supports English, Hindi, and 20+ Indian languages with code-mixing; it returns a clean clinical-English note, ICD-10 suggestions, and a prescription draft for clinician review. Audio is processed in memory and discarded after the note is drafted. EHR-ready export (PDF · HL7 · FHIR) is an export claim only. ABDM integration is on the roadmap. Book a demo to compare the complete-HIS/EHR and incumbent-HIS/EHR paths against your hospital's required workflows. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## How do you decide in one pass?

Three questions get you to the right category without a month of enterprise demos.

What's your scale, honestly? No beds means an EMR and front-office basics, not a HIS. Beds, an OT, a pharmacy, and a lab that need to coordinate mean an operational HMS or HIS. Buy for the facility you run, not the one on the brochure.

What does the vendor actually include, module by module? Ignore the acronym and get the list in writing: registration, OPD, IPD, billing, pharmacy, lab, radiology, ABDM milestone. The list is the spec; the label is marketing.

And what's actually breaking day to day? If it's registration, billing, or department coordination, compare the required modules carefully; our [best HIS roundup](../best-his-software-india/) helps. If it's the note that never gets written, evaluate the ambient documentation workflow too. Clinics start with [Practice Copilot pricing](/in/pricing/); hospitals start with a Hospital Copilot demo. Sort the scale and module list first, then decide whether Patient Square or the incumbent remains the record system.

---

## AI Scribe for Cardiology Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-cardiology-clinics-india/
Published 2026-09-09 · Tags: ai-scribe, cardiology, india, specialty

How an AI scribe handles echo and ECG-heavy cardiology OPD in India: Hindi and Hinglish capture, clean English notes, ICD-10 suggestions, two-minute consults.

It captures the read you dictate. Say the echo aloud, EF 45 percent, moderate MR, mild LVH, and the scribe drafts a note with those findings in your words. It doesn't look at the images or measure anything; the interpretation is yours. It structures what you said into a clean English note, even when you dictate in Hindi or a Hindi-English mix.

An AI scribe fits an Indian cardiology OPD if it captures the language you actually dictate, the echo read, the ECG interpretation, the interval change in a heart-failure patient, and hands it back as a clean English note about two minutes after you finish. It doesn't read images or measure anything. The reading stays yours. What it removes is the typing you never have time for on a two-minute consult.

> **Key takeaways**
>
> - The scribe captures what you say. Dictate "EF 45 percent, moderate MR" and the note reflects it. It doesn't interpret the echo or ECG for you.
> - Input can be Hindi, Hinglish, or English; the note always comes back in clean clinical English.
> - On a two-minute Indian consult (Irving et al., BMJ Open 2017), the note is the bottleneck, not the exam. The scribe drafts it so you review instead of type.
> - ICD-10 suggestions like I50.32 or I48.0 appear next to the draft. You confirm them; nothing is auto-coded.
> - Visit audio is processed in memory and discarded at draft; no recording is stored, which fits DPDP Act 2023 standards. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

_Sources: Irving et al., BMJ Open 2017._

## Why cardiology notes break on a two-minute Indian consult

A cardiology follow-up is rarely just a complaint and a plan. One visit can carry an interval history, a focused cardiac exam, an ECG read, an echo summary, a medication titration, and a plan that references the next visit. Each piece is its own chunk of dictation. In an Indian OPD, all of it has to fit inside a consult that averages about two minutes.

That two-minute figure comes from Irving et al.'s 67-country BMJ Open review, which put India near the short end of an enormous global range, from 48 seconds in Bangladesh to over 22 minutes in Sweden. Two minutes to listen, examine, read the ECG the patient brought, decide, and prescribe. The documentation loses that race every single time.

So one of three things happens on a packed cardiology day. The note gets compressed to "CHF, continue meds," which tells future-you nothing about the trend. Or it gets typed from memory after the OPD clears, hours and forty patients later, by which point the details have blurred. Or it gets skipped, and the record has a token number and a fee but no clinical substance. And thin notes aren't cosmetic. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. In cardiology, where the interval trend is the clinical story, a one-line note is both useless and a medico-legal exposure.

Better clinic software doesn't fix this. A faster registration screen doesn't make the echo read write itself. The constraint is upstream: there's no spare time in a two-minute consult to type.

## How the scribe fits a cardiology OPD visit

You start a session when the patient sits down, then run the OPD the way you always do. As you take the interval history and examine, you speak your findings the way you'd dictate them: "no orthopnea, effort tolerance same, JVP normal, no S3, trace pedal edema." The scribe captures it, whether you say it in English, Hindi, or the natural mix of both.

When the patient hands you last week's echo and you read it, dictate the read aloud. "Ejection fraction 45 percent, moderate mitral regurgitation, mild concentric LV hypertrophy, no pericardial effusion." That's your interpretation. The scribe writes it into the note as you said it. It's not measuring the EF or looking at the images. You did that. The scribe is a stenographer, not a reader.

Here's the canonical version of that flow. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. After the patient leaves, you stop the session, and about two minutes later there's a draft: interval history, exam, your ECG and echo summaries, assessment, plan. You read it, fix anything wrong, and sign.

Three India-specific things matter here. The note comes back in clean clinical English no matter how you dictated it. Live consultation audio is processed in memory and discarded once the note drafts; uploaded recordings use a separate retention mode with explicit consent. And the prescription output is a draft you review, never something the tool sends to a pharmacy on its own. Our [Hinglish capture explainer](../ai-scribe-hindi-english-code-mixing/) covers exactly how the code-mixing is handled if that's your daily reality.

## Hindi and Hinglish in, clean English out

This is the part that decides whether a scribe survives an Indian cardiology OPD, and it's where imported tools quietly fail.

A real consult isn't in one language. The patient describes chest discomfort in Hindi, you ask a follow-up in Hindi, you dictate the echo read in English, and you switch back to Hindi to explain the plan. Mid-sentence. A scribe that only handles clean English transcripts falls apart on the first "seene mein bhaari lagta hai" and produces garbage.

The scribe captures English, Hindi, and 20-plus Indian languages, including that mid-sentence switching. What it does not do is hand you a Hindi note. The output is always clean clinical English, structured the way a cardiology note should read, because that's the language your referral letters, your records, and any downstream reader expect. Input is flexible; output is standardised.

We think this is the honest framing, and it's worth being precise about. The scribe understands Hindi and Hinglish; it does not write in them. If your practice needs the final note in a regional language, that's not what this tool produces today. For most Indian cardiology clinics, English notes from bilingual consults are exactly the fit, and our [Hindi and Indian-languages guide](../ai-scribe-hindi-indian-languages/) lays out the full language list.

## What a cardiology-ready draft has to show

A generic scribe flattens cardiac language into mush. Ask "EF 45, moderate MR" and get back "patient has heart problems," and you'll rewrite every note, which defeats the point. The draft has to come back in cardiology language.

| What you dictate | Generic scribe often writes | What a cardiology-ready draft should show |
|---|---|---|
| Echo read | "Heart function reduced" | "LVEF 45%, moderate MR, mild concentric LVH, no effusion" |
| ECG interpretation | "Abnormal ECG" | "Sinus rhythm, rate 78, no acute ST-T changes, poor R-wave progression" |
| CHF interval history | "Feeling about the same" | "Effort tolerance stable, dry weight down 1 kg, no orthopnea or PND, diuretic continued" |
| AFib status | "Irregular heartbeat" | "Paroxysmal AFib, rate-controlled on metoprolol, CHA2DS2-VASc 3, on anticoagulation" |
| ICD-10 suggestion | Generic or missing | "I50.32, I48.0 suggested for confirmation" |

_If the draft reads like the middle column, it wasn't built for cardiology. The right column is the bar. Dictate a real echo read during a trial and see which one you get._

The only way to know which you're getting is to test it on your own reads during the trial, not on a vendor's tidy demo script.

## The documentation-time math for an Indian cardiology clinic

Here's a concrete Tuesday. A cardiologist in a Pune OPD is booked to 6pm. Fifty-plus patients on the list, mostly follow-ups: hypertension reviews, heart-failure titrations, post-MI check-ins, each arriving with an ECG strip or a recent echo report to read into the note. By 1pm the doctor is a dozen patients behind and the notes have shrunk to two-word entries to keep the queue moving. The real charting is waiting for 8pm.

The value of a scribe isn't a dramatic hour count. It's a minute or two shaved off each note, multiplied across the panel, plus the bigger shift in when the notes finish. Below is illustrative arithmetic, not a trial result, so treat it as a way to frame your own numbers.

| OPD shape | Notes per day | Rough note time without scribe | With scribe | Daily difference |
|---|---|---|---|---|
| Follow-up-heavy OPD, 50 visits | 50 | ~100 min | ~65 min | ~35 min |
| Mixed clinic, 40 visits + 10 echo reads | 40 + 10 | ~120 min | ~80 min | ~40 min |
| Consult-heavy day, 30 longer notes | 30 | ~105 min | ~72 min | ~33 min |

_Illustrative estimates, not a measured result. Your real number depends on note length, how much you correct drafts, and reading speed._

The headline isn't the daily minutes. It's that the after-OPD charting backlog shrinks toward zero, because the notes are drafted as you go instead of reconstructed at night. That's the shift a cardiologist on a 50-patient day actually feels. If you want to run your own figures, our [scribe cost math for an Indian solo doctor](../ai-scribe-cost-for-solo-doctor-india/) has the framework.

## Where the scribe stops, and when it isn't the right tool

Being straight about the limits matters more than a feature list. The scribe drafts what you dictate. It doesn't read your echos, calculate an EF, interpret the ECG, or catch that your dictated exam and assessment contradict each other. If you call the rhythm sinus and then dictate an AFib plan, it won't flag the mismatch. That's your review.

It also doesn't integrate with your echo lab software or your clinic's record system. You get a draft, you review it, and you copy or export it into wherever you chart. If your real bottleneck is structured data flowing between your echo machine and your records, an ambient scribe is the wrong purchase; that's an interoperability problem, and a scribe doesn't touch it.

And on ABDM, we'll be plain, because Indian clinics are right to ask. Live ABDM record linking is on our roadmap, not shipped. If you need to link cardiology records to a patient's ABHA number today, your shortlist is software that has cleared at least the NHA's M1 and M2 milestones in production. We won't claim a milestone we don't hold.

For the honest verdict: a scribe fits when the after-OPD charting is your real problem and you dictate your reads. It's the wrong tool if you never want to say the read out loud, or if your pain is data flow rather than documentation.

## How to test it on your own cardiology OPD

A single demo note tells you almost nothing. Run it on your own clinic during the 7-day trial, and do three specific tests.

Dictate a full echo and ECG read, in your usual Hindi-English mix, and check whether the draft comes back in cardiology English or flattens it. Narrate one heart-failure interval history with a real trend, weight change, effort tolerance, med adjustment, and see whether the note captures the delta rather than just "stable." Then run it on your heaviest half-day, back-to-back rooms with reads piling up, and see whether the notes stay clean and separate instead of bleeding together.

That's your accuracy figure, and it's the only one worth trusting. The [best AI scribe for India](../best-ai-scribe-for-india-2026/) roundup compares the India-facing options if you're shortlisting more than one.

If you want to see the draft quality against your own echo reads and your OPD's language mix before committing anything, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical complex case, or check what each plan includes on the [pricing page](/in/pricing/) first. Entry pricing is ₹1,599 per clinician per month on annual billing, ex-GST; add 18% GST and the invoice is about ₹1,887 a month. That's the right test for a cardiology clinic, and it's the one we'd run in your shoes.

---

## AI Medical Scribe for Gastroenterology: Clinic Notes
https://patientsquare.com/us/blog/ai-scribe-for-gastroenterology/
Published 2026-09-09 · Tags: gastroenterology, ai-medical-scribe, clinic-notes, ibd-documentation, clinical-documentation

An ambient AI scribe drafts your GI clinic notes for IBS, GERD, IBD, and hepatology from what you say. It doesn't write the endoscopy report or read pathology.

No. It drafts the clinic note from what you say during an office visit. The procedure report, with photo documentation, withdrawal time, and findings by segment, is written in your endoscopy system after the case. The scribe never touches it.

An ambient AI scribe listens during your GI clinic visit and drafts the office note from what you say, then hands it back about two minutes after the patient leaves. It documents the talking part of your day: IBS, GERD, IBD follow-ups, hepatology, celiac. It does not write your colonoscopy or endoscopy report, and it doesn't read pathology or images. You review the draft, confirm the codes as suggestions, and sign.

> **Key takeaways**
> - The scribe drafts your clinic note about two minutes after the visit; the procedure report is a separate document it never touches.
> - It captures what you say, so a Bristol type 6, an ALT of 90, or "moderate Crohn's on infliximab" all go in the note as you stated them.
> - It doesn't read biopsies, labs, or scans. If you say the path showed active colitis, that's your reading, recorded.
> - ICD-10 suggestions are starting points, because GI coding is fussy about site and complication.
> - Audio is discarded the moment the note drafts. Nothing gets recorded and kept.

_Source: Patient Square product specifications, 2026._

## Where the documentation actually piles up in GI

A GI practice runs on two very different note types. There's the procedure report, structured and generated in your endoscopy software after each case. And there's the clinic note, written by you, in prose, about the conversation you just had. The scribe is for the second one.

Think about a Thursday afternoon clinic. A GERD patient who wants off their PPI. An IBS follow-up who tried the low-FODMAP diet. Two IBD patients, one flaring, one stable on a biologic. A hepatology visit with a fresh set of labs. By 4pm you've had eight conversations and written maybe two of the notes. The rest wait.

That backlog is well documented. The AMA reports primary-care visits average about 36 minutes of EHR time per encounter, and its 2023 Organizational Biopsy found roughly 21% of physicians spend more than eight hours a week on the record outside normal hours. GI clinics carry the same weight because the histories are long and the plans are detailed. The scribe drafts that clinic note from your narration so it isn't waiting for you at 6pm.

## The procedure boundary, said plainly

This is the line to be clear about. The scribe does not write your endoscopy or colonoscopy report. It has no view into your scope images, it doesn't know the withdrawal time, and it can't populate findings by colonic segment. That report lives in your procedure system, with its photo documentation and its structured fields, and it stays there.

The scribe handles the office visit around the procedure. The pre-procedure consult where you explain a screening colonoscopy and go over prep. The post-procedure follow-up where you discuss what the path came back showing. In that follow-up, if you say the biopsies from the sigmoid showed active colitis and you're stepping up therapy, the note reflects your words. The scribe records that you said it. It never opened the report or read the slides.

Same for imaging and labs. You state that the MRE showed a stricture, or that the ALT is 90 and the platelets are down. Those are your findings, spoken by you, recorded as stated. The scribe is a stenographer for your assessment, not a radiologist and not a pathologist. Honestly, that's the whole design point: keep the reading with the physician and let the tool write down what the physician says.

## What a GI clinic note has to capture

The vocabulary is specific and the plans are conditional, so getting your spoken terms down accurately is most of the job.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| IBD activity | "Crohn's in clinical remission, HBI 3, no bleeding" | Disease activity as you stated it |
| Stool pattern | "Bristol type 6, three loose stools a day" | Stool scale and frequency, as dictated |
| Hepatology labs | "ALT 90, bilirubin normal, platelets 130" | Lab values, as you read them out |
| Screening plan | "Average risk, repeat colonoscopy in ten years" | Interval you specified |
| GERD management | "Trial off the PPI, back on H2 blocker as needed" | Plan with the step you chose |
| Biologic status | "Cycle continues on infliximab, next infusion in eight weeks" | Treatment and timing |
| Biopsy narration | "Path from the last scope showed active colitis" | Your account of the result |

Notice the pattern. Every row is something you say, not something the scribe figures out. A screening interval is a decision you make from risk and prior findings; the scribe writes the interval you state, it doesn't compute one. The American College of Gastroenterology recommends average-risk colorectal cancer screening start at age 45, but which patient is average risk and when they come back is your call, dictated and recorded.

## IBD follow-ups are where it earns its keep

IBD clinic notes are dense. Disease and phenotype, current therapy and how long they've been on it, symptom activity, extraintestinal stuff, the last scope, the last labs, and the plan that hangs off all of it. Rebuilding that from memory after clinic is exactly the kind of note that slides into the evening.

Narrate it as you already do in the room. "Ulcerative colitis, left-sided, in clinical remission on mesalamine, no bleeding, Mayo endoscopic subscore 1 from the last scope, continue current dose, recheck in a year." The scribe drafts that while it's fresh. You confirm the activity index and the plan, fix anything it misheard, and sign. The disease-activity judgment was yours the whole time. The tool just kept you from typing it out twice.

## ICD-10 for GI: suggestions, not final codes

GI coding gets specific fast. Crohn's versus ulcerative colitis, with or without complications, the site, the bleeding status. The scribe offers ICD-10 suggestions from what you said, and here they're a starting point more than usual.

Say "Crohn's with a fistula" and it might surface a K50 family suggestion; a GERD visit, a K21 suggestion; a screening colonoscopy, a Z12.11 suggestion. Each one needs you to confirm the exact variant, including complications and whether the code matches the encounter reason. The scribe can't resolve "with abscess" versus "without" from one spoken sentence, so it hands you a candidate and you finalize it. Our post on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) covers why the review step isn't optional.

## Prescriptions and the draft you still check

GI visits generate orders: PPIs, mesalamine, budesonide, antiemetics, sometimes a biologic plan. When your plan includes a medication, the scribe drafts it from what you said, spelling out the drug and dose so you're not retyping the order.

It doesn't screen the draft for interactions or dosing, and it doesn't send anything anywhere. There's no e-prescribing link. For a patient on a biologic with a stack of other meds, the interaction check is the read you already run, and it stays yours. You review the draft against the regimen, adjust what needs adjusting, and act on it in your own prescribing workflow. Our note on [prescription draft safety](../ai-scribe-prescription-draft-safety/) explains how the draft works and why you're the safety check.

## Security in a specialty with sensitive records

GI records hold sensitive material, from IBD histories to hepatitis and liver-disease status. Audio is processed in memory and discarded the moment the note drafts, so no recording of the visit sticks around. Notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256, they belong to your practice, and you can export or delete them whenever you want.

We maintain HIPAA compliant safeguards, offer a signed BAA to every customer, and have a SOC 2 Type II audit underway. If compliance drives your decision, start with the [security page](../../security/) and our detail on [BAAs and consent](../ai-scribe-hipaa-baa-consent/).

## When it's the right buy, and when it isn't yet

Here's the honest verdict. AI Scribe by Patient Square is an ambient AI medical scribe that runs alongside any EHR: you copy or export the finished note, so there's no integration project and no write-back into your system. That's a Practice Copilot with the scribe as one module. If your clinic notes are eating your evenings, if the IBS and IBD and hepatology histories are long and you'd rather talk than type, the trade is easy to weigh. Narrate as you already do, and the note drafts for your review.

But a scribe isn't the right buy for you yet if your bottleneck is the procedure side. If your evenings go to endoscopy reports, prep instructions, and pathology reconciliation rather than clinic prose, the ambient note won't touch that work, and you'd be paying for a tool aimed at the lighter half of your documentation. In that case, wait. When your clinic volume and note burden justify it, come back.

The published evidence points the useful direction for clinic-heavy practices. A 2025 JAMA Network Open study of 263 ambulatory clinicians across six health systems found burnout dropped from 51.9% to 38.8% after 30 days on an ambient scribe, with measured improvement in after-hours documentation time. That's a burnout signal from an office-visit setting, not a promise about your exact numbers.

Pricing starts from $79 per clinician per month on the annual Assist plan, then steps up to the Copilot and Autopilot tiers, which add a bundled AI EHR, messaging, and follow-up automation. If you want to compare vendors first, see our [roundup of AI medical scribes](../best-ai-medical-scribes/) and [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before you commit to anyone.

Want to see it run on a real GI clinic afternoon? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Pricing is on the [pricing page](../../pricing/).

---

## Free Clinic Management Software India: What's Real
https://patientsquare.com/in/blog/free-clinic-management-software-india/
Published 2026-09-09 · Tags: clinic-management-software, free, india, buyer-guide

An honest look at free clinic management software in India: which options are genuinely free, which are just trials, and where free stops paying off.

Open-source projects can have a zero licence cost, but that is not a zero-cost operating model. OpenEMR and Bahmni are open-source projects; confirm the operating owner, hosting, backup, updates, and support before adopting any system. A trial is not a free plan.

"Free clinic management software" can mean source code you operate, an ongoing free tier, a temporary trial, or programme software with eligibility rules. Only the first two can remain free after evaluation, and neither makes the clinic's operating cost zero.

> **Decision summary**
>
> - Open-source licence cost and total operating cost are different questions.
> - A trial is not a free plan; read the current first-party pricing page.
> - Keep hosting, implementation, backup, support, and labour as separately quoted lines.
> - Patient Square's 7-day free trial lets a clinic test documentation on its own workflow before choosing a paid plan. Assist is ₹1,599 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST.

_Sources: OpenEMR, Bahmni, Practo Ray, KiViHealth, and Patient Square first-party pages, checked 11 August 2026._

## Four different meanings of free

Start by naming the model. A search result can put open-source code, a capped free tier, a trial, and programme software in the same list even though their costs and access rules differ.

**Open source** can remove the proprietary licence fee for the core code. It does not provide a maintained clinic service by itself. Two current examples are:

| Project | First-party description used here |
|---|---|
| OpenEMR | Open-source medical-record and practice-management project |
| Bahmni | Open-source hospital and clinic system with a wider operational footprint |

**Trials** are temporary access to a paid product. Practo Ray, KiViHealth, and Patient Square each publish a seven-day trial on the referenced first-party pages. A trial can be useful, but it is not an ongoing free plan.

**Free tiers** are ongoing hosted access within published caps. **Programme software** depends on eligibility, scope, rollout, and support. Keep those two categories separate from open source and trials.

| Label | What you receive | What happens after evaluation |
|---|---|---|
| Open source | Code under an open-source licence | You or a partner operate, secure, update, and support it |
| Free tier | Ongoing hosted access within stated caps | You stay inside the limits or move to a paid tier |
| Free trial | Temporary access to a paid product | Access expires or converts according to the terms |
| Programme software | Access subject to eligibility and programme scope | Rollout, support, and limits follow the programme rules |

### Current trials are paid products

The following first-party pages were checked on 11 August 2026:

| Product | Trial | Paid price signal |
|---|---|---:|
| Practo Ray | Seven days | CM Atom ₹999 per month and Clinic Management ₹1,499 per month on one-year plans |
| KiViHealth | Seven-day trial | ₹12,000 plus GST for one year |
| Patient Square | Seven days | Assist ₹1,999 month to month or ₹1,599 monthly equivalent on annual billing per clinician, plus 18% GST |

Use synthetic data first. Decide whether the paid economics work before importing patient history.

## Test coverage instead of assuming it

Do not infer the exact clinic workflow from the project name. Ask the implementation owner to demonstrate registration, scheduling, notes, prescriptions, billing, reports, downtime, backup, restore, and bulk export on the version you would deploy. A module listed on a project page is not proof that it is configured for your clinic.

Keep integrations equally specific. Ask for the exact ABDM milestone and production status, not an "ABDM-ready" badge. Patient Square's ABDM integration is roadmap-only and must not receive credit for a live workflow.

Our [free EMR software guide](../free-emr-software-india-honest/) goes deeper on OpenEMR versus Bahmni specifically, and the [EMR software buyer guide](../emr-software-india-guide/) covers the cloud-versus-on-premise and DPDP Act 2023 decisions that sit underneath any clinic system, free or paid.

## The real operating-cost sheet

The licence can be zero. Total cost depends on work that must be owned and priced. Use this sheet for a self-hosted option, a managed open-source offer, and a hosted subscription:

| Cost row | Year one | Later annual | Owner | Evidence |
|---|---:|---:|---|---|
| Licence or subscription |  |  |  |  |
| Hosting, domain, certificates, storage |  |  |  |  |
| Installation and configuration |  |  |  |  |
| Data cleaning and migration |  |  |  |  |
| Forms, templates, masters, roles |  |  |  |  |
| Messaging, payment, lab, other interfaces |  |  |  |  |
| Security review and patching |  |  |  |  |
| Backup, restore test, disaster recovery |  |  |  |  |
| Training and user support |  |  |  |  |
| Upgrade testing and correction |  |  |  |  |
| Internal doctor and staff time |  |  |  |  |
| Export, termination, transition |  |  |  |  |
| GST and other applicable tax |  |  |  |  |

Unknown is not zero. Keep it visible until a vendor, implementation partner, or named employee supplies the answer.

### Test the exit before the import

Ask for a sample export before loading live data. Check patient identity, encounters, notes, authorship, prescriptions, attachments, appointments, billing data if used, and audit information. Find out which fields remain structured, which arrive as documents, and how bulk export works.

Then test a restore. A backup file that nobody has restored is not continuity evidence. Record the recovery time, missing fields, responsible person, and correction process.

## The operating-owner decision

Open source is sensible when a named technical owner can operate it, the clinic values deployment control, and the buyer has budgeted implementation and continuity. It is a poor shortcut when the clinic expects community code to arrive with local configuration, support, security, migration, and a contractual recovery time.

Run a peak-day acceptance test. Time registration, note completion, prescription review, billing correction, backup, restore, and export. The result is evidence for your own clinic; a universal patient-volume threshold is not.

## A documentation layer alongside free software

You don't have to choose between free records software and complete notes. They solve different problems, and they stack.

Practice Copilot's AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. A clinic can use Patient Square EHR from the Copilot tier or keep its existing record system and run Practice Copilot alongside it.

The prescription is a draft, not a pharmacy transmission. Visit audio is processed in memory and discarded when the note is drafted. The product lists `EHR-ready export (PDF · HL7 · FHIR)`; that is an export claim, not certified interoperability or automatic write-back. Patient Square's ABDM integration remains roadmap-only. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Practice Copilot's Assist tier is ₹1,999 per clinician month to month or ₹1,599 monthly equivalent on annual billing, ex-GST plus 18% GST. Put that paid row beside the buyer-entered operating costs above. The seven-day trial is for testing the workflow, not evidence that Patient Square is free software.

## A one-pass decision

Three questions get most clinics to an answer without a month of vendor calls.

Can someone on your staff install, update, secure, back up, restore, and support the system? If not, obtain a managed-service quote before calling the open-source path free.

What breaks on your busiest day? Test the exact workflow. If documentation is the bottleneck, compare a documentation layer alongside the record system you keep.

Is ABDM linking a near-term need? If live ABHA record sharing is a near-term need, ask the vendor to demonstrate the exact production transaction, consent flow, failure path, and audit evidence. Patient Square's ABDM integration remains roadmap-only.

Sort those out and the choice mostly makes itself. If your real problem is thin notes on a busy OPD, test the documentation workflow alongside the record system you keep. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> or read the [pricing](/in/pricing/) first.

---

## HealthPlix vs eka.care in India: And a Third Option (2026)
https://patientsquare.com/in/blog/healthplix-vs-eka-care-india/
Published 2026-09-09 · Tags: comparison, healthplix, eka-care, ehr, ai-scribe

HealthPlix wins on specialty-template speed; eka.care wins on ABDM. Here's an honest head-to-head, plus where an ambient scribe with a bundled EHR fits.

They win on different things. HealthPlix is a mature specialty EMR built for fast, template-driven prescription writing across many specialties. eka.care is an ABDM-native platform with a built-in scribe and live ABHA record linking. If your priority is template speed, HealthPlix; if it's interoperability, eka.care. Neither is universally better; the right pick depends on which axis matters most to your practice.

HealthPlix and eka.care are two of the biggest clinic-software brands an Indian doctor shortlists, and they don't really compete on the same axis. HealthPlix wins on specialty-template speed. eka.care wins on ABDM. So "which is better" is the wrong question; "better at what" is the right one. This page lays out the honest head-to-head, then names where a third option, an ambient scribe with a bundled EHR at ₹2,399 a month per doctor, ex-GST (add 18%), fits between them. You can check that [India pricing](/in/pricing/) before reading further.

> **Key takeaways**
>
> - HealthPlix is a mature specialty EMR: fast template-driven prescriptions, Pro ₹11,999/yr, Elite ₹17,999/yr per doctor.
> - eka.care is ABDM-native with a built-in scribe (EkaScribe, ₹1,499/month) and live ABHA record linking.
> - They win on different axes: template speed versus interoperability. Match the axis to your practice.
> - A third route puts an ambient scribe and a bundled AI EHR under one published price: ₹2,399/month per doctor, ex-GST. Its gap is live ABDM, which is roadmap.

## HealthPlix vs eka.care at a glance

Read the axis that matters to you first. Prices are per doctor and change, so confirm current figures with each vendor.

| | HealthPlix | eka.care |
|---|---|---|
| Core strength | Specialty-tuned template EMR, fast Rx | ABDM-native platform, built-in scribe |
| Documentation | You drive templates | EkaScribe drafts ambiently |
| ABDM / ABHA | Listed in Pro tier | Native, live, core design |
| Published price | Pro ₹11,999/yr, Elite ₹17,999/yr | EkaScribe ₹1,499/mo; EMR tiers listed third-party |
| Best for | High-volume specialists comfortable typing | Clinics that need interoperability |

If the ABDM row is the one you keep re-reading, eka.care is probably your answer already. If it's the template-speed row, HealthPlix. If neither row is the thing that actually hurts, keep going, because the pain might be documentation itself.

## Where HealthPlix genuinely wins

Give HealthPlix its due. It's a mature EMR with a deep, specialty-tuned template library, and its whole design is speed: open the patient, pick the template, write a legible digital prescription fast, move to the next. HealthPlix publishes Pro at ₹11,999 a year and Elite at ₹17,999 a year per doctor, roughly ₹1,000 to ₹1,500 a month, which is competitive for that breadth. Pro alone covers OPD records, billing, pharmacy, IPD and lab management, queue management, teleconsultation, and ABDM.

For a high-volume specialist who sees the same conditions all day and is fast on templates, that maturity is a real advantage, and the ambient layer would be paying for a step they don't need. If you want the full pricing breakdown, the [HealthPlix pricing decode](../healthplix-pricing-india/) walks the tiers and the metered credits line by line.

## Where eka.care genuinely wins

eka.care's edge is interoperability, and it's not close on that axis. It's ABDM-native: ABHA verification and consent-based record sharing are built into the core, not bolted on, and it participates in India's interoperable digital-health network by design. On top of that it ships EkaScribe, its own ambient scribe, published at ₹1,499 a month per doctor, so a clinic can get both the interoperability layer and ambient documentation from one India-native vendor.

That combination is genuinely strong. If patient records travelling across the ABDM ecosystem is central to how you want to run, eka.care is built for exactly that, and it's the fit we'd point you to. The [eka.care pricing decode](../eka-care-pricing-india/) untangles the scribe-versus-EMR pricing, which is the confusing part of their model.

## The axis both rivals leave open

Here's the gap neither brand fully closes for every clinic: the two-minute consult and the note that never gets written properly in it. Irving et al.'s 67-country BMJ Open review put India's average primary-care consultation at about two minutes. HealthPlix makes typing the note faster, but you're still typing. eka.care drafts it ambiently, which is the right direction, but ties its strongest value to ABDM, which not every clinic needs today.

So if your single biggest drain is documentation, and ABDM is a later-quarter concern rather than a this-quarter requirement, there's a third shape worth weighing: an ambient scribe with the record system bundled in at one price.

The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. It follows English, Hindi, and 20+ Indian languages, code-mixed the way real consults sound, and always returns the note in clean clinical English. At the Copilot tier, ₹2,399 a month per doctor on annual billing, the bundled AI Copilot EHR makes it the record system too, not just the note-writer. Add 18% GST and that's about ₹2,831 all-in.

We'll be plain about the gap. Patient Square's ABDM integration is on the roadmap and not live, so on the exact axis eka.care leads, we don't match it today. ICD-10 comes as suggestions and the prescription is a draft you sign. If live ABDM is your hard requirement, eka.care is the safer pick and this comparison is mostly decided for you. If it isn't, book a demo and put our note next to theirs on a real consult.

## The three-way price picture

Line them up on the same basis, per doctor per month, and the spread is narrow at the entry.

| Option | Entry price (per doctor) | With bundled EHR | ABDM |
|---|---|---|---|
| HealthPlix Pro | ~₹1,000/mo (₹11,999/yr) | EHR in Pro/Elite | Listed |
| eka.care EkaScribe | ₹1,499/mo | EMR priced separately | Native, live |
| Patient Square | Assist ₹1,599/mo | Copilot ₹2,399/mo | Roadmap, not live |

_Prices from each vendor's pages, July 2026; Patient Square figures ex-GST, add 18%. eka.care EMR tiers are third-party-listed._

The numbers cluster close enough that price alone won't decide it. What decides it is which axis is bleeding: template speed, interoperability, or documentation. Buy against that, not against a ₹100 monthly difference.

One caveat the table can't show: eka.care's total depends on whether you buy the scribe, an Eka Doc EMR tier, or both. Stack the ₹1,499 scribe on top of an EMR subscription and eka.care's real monthly cost climbs above the sticker for either the scribe or the EMR alone. HealthPlix folds its EMR into the Pro fee, and Patient Square folds the AI EHR into the ₹2,399 Copilot tier. So if you want scribe plus a full record system from one vendor at one predictable price, the bundled tiers read cleaner than adding two eka.care lines together. That's not a reason to skip eka.care if you need its ABDM depth; it's just a reason to get the combined number before you compare.

## When each is the better choice

Pick HealthPlix when you want a proven, specialty-tuned EMR with a deep template library and you're comfortable driving the prescription yourself. For a fast specialist, that's a strong, well-worn tool at a fair price.

Pick eka.care when live ABDM and ABHA linking are non-negotiable this year, or you want one India-native vendor spanning the scribe and the interoperability layer. On that axis it's the leader, and switching away to save on a seat would cost you the thing you most wanted.

Pick the ambient-plus-bundled-EHR route when documentation is your single biggest drain, you'd rather the note be written for you than typed faster, and you want the scribe and the record system under one transparent price. If that's the shape of your problem, book a demo and run the note against a real clinic day.

Here's the trap to avoid: buying for the axis that's loudest in the sales pitch rather than the one that's actually costing you. ABDM is easy to say yes to because it sounds future-proof, but if you're not linking ABHA records this year, you'd be paying for a strength you won't use while the note still gets written at 9pm. Template speed is easy to admire in a demo, but it doesn't help if the real problem is that there's no time to type at all. Be honest about which minute is expensive in your clinic, and let that pick the tool. The three-way choice only looks hard when you haven't named the axis yet.

## Decide in a week

1. Name the axis that's actually bleeding: template speed, ABDM, or documentation. Everything below flows from that.
2. If ABDM is required now, shortlist eka.care first and confirm its live milestone status.
3. Get all three prices on the same basis, per doctor per month ex-GST, then add 18% once.
4. Trial the ambient note quality on your own consults, in the languages your OPD speaks, before you assume any of them handles a real Tuesday.

If the axis is interoperability or template speed, the rivals lead and you have your answer. If it's the note that never gets finished, book a short demo and see one of your own consults come back as a signed record before you decide.

---

## Practo Ray Pricing in India: What It Actually Costs (2026)
https://patientsquare.com/in/blog/practo-ray-pricing-india/
Published 2026-09-08 · Tags: pricing, practo-ray, clinic-software, ehr

Practo Ray gates its price behind a sales call. Here's what third-party listings show, the hidden per-booking cut, and a flat ₹ anchor to compare against.

Practo doesn't display a first-party price for Ray; its plans page routes you into a sales flow. Third-party software listings put Ray roughly between ₹1,000 and ₹6,000 per doctor per month, depending on plan tier, clinic size, and add-ons, as of 2026. Treat that as a range to negotiate against, not a quote, and get your actual number from Practo in writing.

Practo Ray doesn't tell you its price. The plans page routes you into a sales conversation instead of showing a rate card, so any number you see online is a third-party estimate. Those listings put Ray roughly between ₹1,000 and ₹6,000 per doctor per month, depending on tier, clinic size, and add-ons. This page decodes what's actually behind that range, where the per-booking cost hides, and gives you a published flat number to negotiate against. If you're weighing whether to stay on Ray at all, the [alternatives comparison](../practo-ray-alternatives-india/) is the better starting point.

> **Key takeaways**
>
> - Practo Ray publishes no first-party price; its plans page is sales-gated. Third-party listings put it roughly ₹1,000 to ₹6,000 per doctor per month.
> - The subscription and Practo's consumer-marketplace per-booking cost are separate lines. Sort out which is which before you sign.
> - Sales-gated pricing flexes with negotiation and module mix, so the number you're quoted isn't the number the clinic next door pays.
> - Patient Square publishes a flat anchor: Assist ₹1,599/month and Copilot ₹2,399/month with a bundled AI EHR, both annual, ex-GST plus 18%.

## What Practo Ray actually costs

Start with the honest gap: there's no published first-party rupee figure to quote. Practo's Ray plans page collects your details and hands you to a rep. So the numbers below come from third-party software directories, not from Practo, and they should be read as a range you negotiate inside, not a rate card.

| Source | What it shows | Read it as |
|---|---|---|
| Practo Ray plans page | Sales flow, no displayed price | Your number comes after a call |
| Third-party listings (e.g. Capterra) | Roughly ₹1,000 to ₹6,000 per doctor per month | A wide band; where you land depends on size and add-ons |
| Practo marketplace | Possible per-booking or revenue-share cost | A separate line from the software subscription |

_Practo publishes no first-party Ray price as of July 2026; range from third-party directories._

That ₹1,000-to-₹6,000 spread is enormous, and the width is the point. A solo doctor and a multi-doctor clinic with every add-on aren't paying anything like the same rate. Sales-gated pricing is designed to scope to your size, which is fair, but it also means the quote flexes with how you negotiate and which modules the rep attaches. If you'd rather start from a published number, you can book a demo and see exactly what a seat costs before any of that.

## Why the price is gated, and what that costs you

Ray is a broad clinic-management suite tied into Practo's consumer marketplace. Gating the price lets Practo bundle the software subscription with marketplace access and up-sell add-ons per clinic. For a practice that wants Practo's patient-booking demand, that bundle is part of the value.

But two things are worth pinning down before you commit. First, the software subscription and the per-booking or revenue-share cost from marketplace appointments are separate. If you only want the clinic software and not the booking demand, make sure you're not being priced for both. Second, get the renewal figure in writing. A sign-up rate negotiated down in month one can drift up at renewal, and with no published anchor you have less to hold it to.

We think that's the real cost of sales-gated pricing: not that the number is high, but that it's opaque, and opacity favours the vendor at renewal.

The other thing opacity hides is what you're actually comparing. When one vendor posts ₹1,599 a month and another routes you through a rep, you can't line them up on a spreadsheet, which is the whole idea. The rep frames the quote as a bundle, so the price of the clinic software alone gets blurred into marketplace access, add-on modules, and whatever discount you negotiated. By the time you've got a number, you've lost the clean per-doctor software cost that would let you compare it against anything else. That's not a knock on Ray specifically. It's how gated pricing works across the category, and it's why we'd push you to separate the software line from the marketplace line before you agree to anything.

## The flat-price anchor to compare against

Now compare that against a number you can read without a call. Patient Square publishes its India tiers per doctor: Assist at ₹1,599 a month on annual billing, Copilot at ₹2,399 with the bundled AI Copilot EHR and WhatsApp messaging, and Autopilot at ₹3,999, all ex-GST with 18% added on the invoice. So Assist is about ₹1,887 all-in and Copilot about ₹2,831. The whole ladder sits on the [pricing page](/in/pricing/), no form required.

Line those up against Ray's third-party band. At the ₹1,000 low end, Ray undercuts the Assist tier; at the ₹6,000 high end, it runs well past Autopilot. The difference is what the money buys. Ray is a marketplace-connected clinic suite. Practice Copilot is an AI clinical platform that can use Patient Square EHR or work alongside an existing EHR. It includes the AI Medical Scribe, ICD-10 suggestions, prescription drafts, and messaging as you move up the plan. The scribe captures the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft to review and sign. Ray brings patient bookings; Practice Copilot drafts notes and supports the selected record path. They're not the same purchase, and price alone won't tell you which you need.

To be plain about the limits on our side: ICD-10 comes as suggestions, the prescription is a draft you sign, ABDM integration is on our roadmap and not live, and Patient Square isn't a patient marketplace, so it won't bring you Practo's booking demand. If new-patient acquisition is your priority, that's a real reason to stay with Ray. If documentation is the priority, book a demo and judge the note on one of your own consults.

## Where the price meets the two-minute consult

The pricing decision only matters if it fixes what's actually breaking. For most Indian clinics, the expensive thing isn't the software fee; it's the documentation. Irving et al.'s 67-country BMJ Open review put India's average primary-care consultation at about two minutes. A clinic suite, marketplace and all, doesn't lengthen that window. It stores the note; it doesn't write it. So the doctor still types after hours, and the OPD register still fills with one-line entries.

That's the lens to price against. If Ray's fee is buying you booking demand you use, it's earning its keep. If it's mostly buying you a records suite whose note field nobody has time to fill, you're paying suite money for a documentation problem it doesn't solve. A focused tool at a published ₹1,599 to ₹2,399 a month, unlimited visits and notes, is often the more predictable spend for that specific job.

Run one honest test before you decide. Look at how many of your new patients this month actually came through Practo versus a referral, a board outside the clinic, or a WhatsApp forward. If the marketplace is a real acquisition channel for you, the gated bundle can pay for itself many times over. If most of your patients find you some other way, you're funding a marketplace you barely use, and the documentation you do need every day is the part the fee doesn't fix.

## When Practo Ray's price is worth it

Pay for Ray when you want Practo's patient marketplace and you'll use it. A clinic that fills chairs through Practo bookings, wants appointments, records, and billing in one connected suite, and treats new-patient demand as the main return is buying exactly what the price includes. For that practice, the marketplace tie-in is the feature, not a tax, and a documentation tool wouldn't replace it.

Choose the published-price route when your priority is records and notes without the marketplace, and predictability matters more than reach. If documentation is the real drain, book a demo and see the note against a live clinic day. If you've already decided to leave, the [switching guide](../switch-from-practo-ray-india/) covers what exports cleanly and how to move without a records gap.

## Decide before the sales call decides for you

1. Get Practo's actual quote in writing, and ask which lines are subscription and which are per-booking.
2. Nail down the renewal figure before you sign, since there's no published anchor to hold it to.
3. Compare against the flat ladder on our [pricing page](/in/pricing/), ex-GST, then add 18% once.
4. Decide honestly whether you're buying booking demand or documentation. Price the one you actually need.

If Practo's marketplace is the reason you're there, the gated price can be worth it. If you're really shopping for records and notes, a published flat number is the easier thing to plan around, and a documentation tool is the more direct fix for the two-minute consult.

---

## Switching From KiviHealth: Timing, Export, First Week
https://patientsquare.com/in/blog/switch-from-kivihealth-india/
Published 2026-09-08 · Tags: switching, kivihealth, migration, clinic-software

Leaving Jio KiviHealth? The prepaid-package exit math, the export questions to ask in writing, and a first-OPD-week plan for an ambient AI scribe.

KiviHealth's public pages don't document a self-serve bulk export, so don't assume one exists or doesn't. Its doctor app shares prescriptions as PDFs per patient, and the platform advertises migration support for importing records in. Before you plan anything, email support and get the full export contents, format, and timeline in writing.

Leaving KiviHealth is a timing question before it's a technology question. The platform sells prepaid packages that run as long as ten years, published from ₹12,000 plus 18% GST for one year, so the first thing to work out is how much prepaid value you'd strand by moving now. The second is the export, which KiviHealth's public pages don't document. Both have clean answers below.

If you haven't actually decided to leave yet, start with the [KiviHealth alternatives comparison](../kivihealth-alternatives-india/) instead. That post weighs the options. This one is for the clinic that has picked a destination and wants the move to go quietly.

> **Key takeaways**
>
> - KiviHealth publishes flat packages: ₹12,000 + GST for 1 year up to ₹75,000 + GST for 10 years. Longer terms drop the effective rate to roughly ₹625 a month.
> - Prepaid years change the switch math. Leaving a 3-year package after year one strands about ₹16,700 of prepaid value, assuming no refund.
> - No self-serve bulk export is documented on KiviHealth's public pages. Send the 5 export questions below in writing before you plan a date.
> - Run a 60–90 day overlap either way. New visits start clean; old records stay reachable.
> - Patient Square's Assist plan is ₹1,599 per clinician per month on annual billing + 18% GST; the bundled AI EHR arrives at ₹2,399 (Copilot).

## The prepaid-package math comes first

KiviHealth, now branded Jio KiviHealth after Netmeds acquired it in 2019, prices differently from most Indian clinic software. Instead of a monthly per-doctor fee, its pricing page lists flat packages: ₹12,000 for one year, ₹17,000 for two, ₹25,000 for three, ₹38,000 for five, ₹60,000 for seven, ₹75,000 for ten, all plus GST. The page doesn't state a per-doctor basis, so a multi-doctor clinic should confirm what it's actually buying.

Those long packages are the loyalty mechanism. They're also the exit cost. Here's the straight-line math on what leaving after year one strands, assuming no refund (refund terms aren't published; ask):

| Package (ex-GST) | Effective monthly rate | Prepaid value stranded if you leave after year 1 |
|---|---|---|
| 1 year, ₹12,000 | ₹1,000 | ₹0 at term |
| 2 years, ₹17,000 | ₹708 | ~₹8,500 |
| 3 years, ₹25,000 | ₹694 | ~₹16,700 |
| 5 years, ₹38,000 | ₹633 | ~₹30,400 |
| 7 years, ₹60,000 | ₹714 | ~₹51,400 |
| 10 years, ₹75,000 | ₹625 | ~₹67,500 |

_Arithmetic from KiviHealth's published package prices, July 2026. Straight-line assumption; confirm refund terms with the vendor._

Read your own row honestly. A two-chair clinic in Nashik three years into a five-year package is staring at a real stranded amount, and "wait for renewal" might be the right answer. But weigh it against the monthly cost of the problem pushing you out. If your evenings go to typing notes, that has a price too, and it recurs.

## What comes out of KiviHealth when you leave?

Here's the honest state of it: we couldn't find a documented, self-serve bulk export on KiviHealth's public pages, and we're not going to pretend one exists or claim one doesn't. What the public materials do show is a template-driven EMR, per-patient prescription sharing as PDFs from the doctor app, and migration support for bringing records *into* the platform. Imports being normal cuts both ways; vendors move data in this market all the time. You just need the reverse direction confirmed.

So the first concrete step of this migration is an email, not a login. Send KiviHealth support these five questions and keep the thread:

1. What does a complete export of my account include, patient by patient?
2. In what format does it arrive, and is clinical history structured or PDF?
3. How long does the export take from request to delivery?
4. What happens to my records once the subscription lapses?
5. Is there a charge for any of this?

Their answers decide your timeline. Structured export in a week: plan a fast cutover. PDFs only, or silence: extend the overlap and front-load your busiest repeat patients, pulling their records first so the top of your OPD is covered before the long tail.

## The overlap plan when the export is uncertain

Run both systems for 60 to 90 days, and keep KiviHealth read-only from your switch date. Nothing about that changes with export uncertainty. What changes is the order of work.

Week one, work the head of the distribution. Most clinics see a familiar core: the diabetics, the hypertensives, the families who come for everything. Identify your 200 most frequent patients and make sure their essentials, ongoing medication, allergies, and last prescription, exist in the new system before their next visit, even if that means saving per-patient PDFs from the app. It's tedious for an afternoon. It buys you a calm first month.

From day one, every new consult documents itself. The AI Medical Scribe by Patient Square is one module inside Practice Copilot, our AI platform for the whole practice, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The consult can run in Hindi, Marathi, or mid-sentence Hinglish; the note comes out in clean clinical English. Because the record rebuilds at OPD speed, the imported history matters less with every passing week. Book a demo and watch a note drafted live before you fix the switch date.

Only close the KiviHealth account once three things are true: the export answers arrived in writing, the overlap window passed without you needing edit access, and one billing cycle closed cleanly on the new side.

## Flat packages against a per-clinician ladder

The price comparison is lopsided in an interesting way, so let's state it plainly instead of hiding it.

On record-keeping alone, KiviHealth wins. Its one-year package works out to about ₹1,000 a month ex-GST, and the ten-year package drops that near ₹625. Patient Square's Assist plan is ₹1,599 per clinician per month on annual billing, ex-GST, which is about ₹1,887 once 18% GST is added. Copilot, with the bundled AI Copilot EHR and WhatsApp messaging, is ₹2,399 ex-GST. Nobody switches to us to save on the licence line.

What the difference buys is the writing. KiviHealth's EMR is template-driven; its own materials pitch templates that minimise typing, and templates do help. But a template still needs a doctor filling it while the queue builds. An ambient scribe removes that step: you talk to the patient, the note drafts itself, you review and sign. Unlimited visits, no per-note charges, no setup fee, on every plan. The full ladder, including what Autopilot adds, is on the [India pricing page](/in/pricing/), and the 7-day trial fits inside your overlap window; run it on your heaviest OPD day, not a quiet one.

We think the fair way to frame it: KiviHealth prices the record, Patient Square prices the record plus the labour of writing it. Compare against what your evenings are worth, not licence against licence.

## When KiviHealth is the better fit

Stay on KiviHealth if the budget line rules and typing doesn't bother you. A flat ₹12,000-a-year package covering EMR, billing, inventory, and SMS tools is genuinely hard to beat on price, and if your notes get written adequately inside their templates, your problem is already solved. The long packages reward exactly that clinic.

Stay, for now, if you're deep into a multi-year package and the stranded value dwarfs the pain. Mark the renewal date, send the export questions this month anyway, and revisit with the answers in hand.

Switch when documentation is the bottleneck the templates never fixed: one-line notes at 9pm, records that wouldn't stand up in a dispute, a register that's thinner than your patient load deserves. That's the specific problem an ambient scribe removes. How we handle the data, audio processed in memory and discarded once the note drafts, DPDP Act 2023 standards, and ABDM on the roadmap rather than claimed, is on the [security page](/in/security/). When the timing works, book a short demo and bring your KiviHealth export answers to the call. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

---

## Switching From Practo Ray: A Clinic Migration Guide
https://patientsquare.com/in/blog/switch-from-practo-ray-india/
Published 2026-09-08 · Tags: switching, practo-ray, migration, clinic-software

What Practo Ray's own export covers, what it doesn't, and a first-OPD-week plan for moving your clinic to an AI-native scribe and EHR without a records gap.

Yes, partly self-serve. Ray's settings include an Import/Export screen that emails you four kinds of data: Contact, Treatment, Expenses, and Appointments, per Practo's own help pages. Prescriptions and uploaded files aren't named in that list, so ask Practo support in writing what a full export includes before you cancel anything.

You can leave Practo Ray without losing your patient base. Ray's settings include a self-serve Import/Export screen that emails you four kinds of data: Contact, Treatment, Expenses, and Appointments, per Practo's own help pages. That covers the patient list. It doesn't promise structured clinical history, so the safe plan treats old records as a reference archive and starts new visits clean.

This guide is the mechanics of the move. If you're still deciding whether to leave at all, read the [Practo Ray alternatives comparison](../practo-ray-alternatives-india/) first. This page assumes you've decided, and its whole job is to make the switch boring.

> **Key takeaways**
>
> - Ray's help pages document a self-serve export of 4 data types (Contact, Treatment, Expenses, Appointments), delivered by email.
> - Prescriptions and uploaded files aren't named in that export list. Get their handling confirmed in writing before you cancel.
> - Your free Practo listing is independent of Ray. Leaving the software doesn't delist you from the marketplace.
> - Keep Ray read-only for 60–90 days of overlap. New visits start clean on day one.
> - Patient Square starts at ₹1,599 per clinician per month on annual billing plus 18% GST; the bundled AI EHR arrives at the ₹2,399 Copilot tier.

## What does Practo Ray actually export?

Start with what's documented, because most migration horror stories begin with assumptions.

Practo's help pages describe an Import/Export section inside Ray's settings. You tick the data you want, enter an email address, and click Export to email. Four categories are named: Contact, Treatment, Expenses, and Appointments. There's also a Completed Exports list showing everything already sent from your account. That's a real, self-serve exit door, and Practo deserves credit for shipping one. Plenty of Indian clinic software makes you beg.

Now the gaps. The help page doesn't state the file format, and prescriptions and uploaded documents don't appear among the four categories. Maybe support pulls those for you on request. Their public pages don't promise it, so treat it as unconfirmed until you have an answer in writing. One email settles it: ask support exactly what a complete export includes, in what format, and how long it takes. Send that email before you touch anything else.

We think this export-first habit is the best single test of any clinic software vendor, including us. A vendor confident you'll stay makes leaving easy.

## Your Practo listing doesn't leave with Ray

Here's the part that stops many clinics from switching, and it's based on a misreading. Practo states that the doctor listing itself is free and independent of its paid products. Ray is the practice-management subscription. The profile that brings you bookings is a separate, free thing.

So cancelling Ray doesn't delist you. Patients still find your profile, still book you. What changes is the plumbing: those bookings stop flowing into a Ray calendar you're paying for. Your front desk needs a new place to watch for them, whether that's the free Practo tools, a phone confirmation habit, or the scheduling module in whatever you move to.

Decide that routing before the switch, not during it. A booking nobody saw is a no-show you caused.

## Map the export to the system you're joining

Four export categories, four different destinations. This table is the whole migration on one screen.

| Ray export category | What it holds | Where it should land | Watch for |
|---|---|---|---|
| Contact | Your patient list: names, numbers, registration details | The new system's patient directory | Duplicate patients under slightly different spellings; verify mobile numbers are 10 digits |
| Appointments | Past and upcoming bookings | Only the next 2–3 weeks matter; enter upcoming visits by hand if needed | Reconfirm the next fortnight by phone or WhatsApp so nobody falls through |
| Treatment | Treatment records as Ray stores them | A read-only reference archive | May not map to structured fields in another system; don't budget time for re-keying it |
| Expenses | Clinic expense entries | Your accounting workflow, not the EMR | GST filings need continuity; hand this to whoever does your books |
| Not listed: prescriptions, files | Unconfirmed | Written request to Practo support | Get the answer in writing before cancelling |

The pattern to accept early: the patient *list* moves as data, the patient *history* mostly moves as documents. Indian EMR-to-EMR migrations almost never carry structured clinical history cleanly, whoever the vendors are. Fighting that costs weeks. Planning around it costs a spreadsheet.

## Your first OPD week off Ray, day by day

A 60-patient Monday is not the day to discover a login problem. Sequence it like this.

**The Friday before.** Run the Ray export. Open every file and spot-check five real patients against what you remember. Load the contact list into the new system. Keep your Ray login alive; you're overlapping, not cancelling.

**Monday.** Front desk works from the imported patient directory. The doctor starts the scribe on every visit, so each consult produces a structured note minutes after the patient leaves. Nothing needs to be back-filled tonight.

**Tuesday.** A regular asks about the tablet she was given in March. This is the read-only moment: look it up in Ray, attach the old record to her chart in the new system, move on. Expect a handful of these a day for the first month, then almost none.

**Wednesday to Saturday.** Reconcile the appointment book each evening against Practo-profile bookings and walk-ins. By the weekend you'll know exactly which routing gaps exist, while they're still cheap to fix.

The reason week one stays calm is that the documentation isn't manual. The AI Medical Scribe by Patient Square is one module inside Practice Copilot, our AI platform for the whole practice, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Your searchable record rebuilds at OPD speed because every visit writes itself. Consults can run in English, Hindi, or code-mixed Hinglish; the note always comes out in clean clinical English. Book a short demo and watch one drafted from a real consult before you commit to a date.

## What does the other side cost?

Ray's site puts pricing behind a sales flow, so any figure you've seen is third-party. Listings cluster roughly between ₹1,000 and ₹6,000 per doctor per month depending on plan and clinic size. Our [Practo Ray pricing decode](../practo-ray-pricing-india/) digs into the tiers properly, so we won't repeat it here.

Patient Square publishes its numbers. Assist, the scribe-led documentation plan, is ₹1,599 per clinician per month on annual billing, ex-GST. With 18% GST the invoice reads about ₹1,887. Copilot, which adds the bundled AI Copilot EHR and WhatsApp messaging, is ₹2,399 per month annual, ex-GST. No per-note charges, no setup fee, unlimited visits on every plan. The full ladder is on the [India pricing page](/in/pricing/).

One symmetry worth checking while you're evaluating exit doors: every Patient Square plan includes EHR-ready export (PDF · HL7 · FHIR), stated on the pricing page. Judge the software you're joining by the same standard as the one you're leaving. There's also a 7-day trial, which fits neatly inside your overlap window; run it on a real clinic day, not a quiet one.

## When staying on Practo Ray is the right call

Not every clinic should make this move, and pretending otherwise would make the rest of this page less useful to you.

Stay if Practo's marketplace is what fills your chairs. Ray plus the consumer app is a demand engine, and if new-patient bookings matter more to you than charting time, that combination is genuinely hard to replace with a standalone clinical tool. Ray is the better fit for that clinic.

Stay if you're mid-subscription and the pain is mild. Time the switch to your renewal date and use the months in between to run the export test and a trial.

Switch when documentation is the drain: notes compressed to one line, evenings spent on records, a register that wouldn't defend you in a dispute. That's the problem Ray was never built to solve and the one an ambient scribe removes. Our data handling, DPDP Act 2023 posture, and the honest note that ABDM integration is on our roadmap, not live, are all on the [security page](/in/security/). When you're ready, book a demo and bring your export files to the call.

---

## Praxis EMR Alternatives: Concept Processor vs Ambient AI
https://patientsquare.com/us/blog/praxis-emr-alternatives/
Published 2026-09-04 · Tags: alternatives, emr, praxis-emr, comparison

Praxis EMR learns your charting style, but you still type. Alternatives where ambient AI drafts the note for you, plus a bundled EHR from $119.

Praxis EMR is a template-free EMR built around a Concept Processor, a neural-network engine that learns each physician's charting patterns and adapts with every encounter. Instead of clicking through templates, you chart in natural language and the system speeds up as it learns your style. It's a genuinely different design from template-driven EMRs, aimed at physicians who value documentation autonomy.

If you're looking at Praxis EMR alternatives, it helps to name what makes Praxis distinctive first. It's template-free and built around a Concept Processor that learns your charting style, so you compose notes in natural language and the tool gets faster as it learns you. That's clever, and some physicians love it. But you're still writing the note. If your real problem is that charting eats your evenings, an ambient scribe that drafts the note from the visit is a different fix. Patient Square's Copilot plan is **$119 per provider per month** on annual billing with that scribe bundled in.

Fair framing: Praxis and ambient AI solve different problems. One makes your typing smarter; the other removes the typing. This page is about which you actually want.

> **Key takeaways**
>
> - Praxis EMR is template-free, built around a Concept Processor that learns each physician's charting style.
> - Praxis licenses the first provider at about $219/mo over 60 months per third-party pricing; additional providers at ~50%.
> - You still author the note in Praxis. Ambient AI drafts it for you to review and sign.
> - Patient Square Copilot is $119/provider monthly (annual) with an ambient scribe and bundled AI EHR.
> - Praxis wins for physicians who love composing their own notes and prefer a licensing-and-ownership model.

## What makes Praxis EMR different from a template EMR?

Praxis isn't a template EMR, and that's the whole pitch. Most EMRs make you click through pre-built templates and pick-lists. Praxis throws that out. Its Concept Processor, described on the vendor's pages and third-party listings as a neural-network engine, learns directly from how each physician charts and adapts with every encounter. You write in natural language, and the system speeds up as it learns your style.

For a physician who thinks template medicine flattens clinical reasoning, that's genuinely appealing. Your notes read like you, not like a form. The tool is ONC-certified, and it's been around long enough to have a loyal base of physicians who chart fast because Praxis learned them years ago.

The catch is in the mechanism: it makes *your* charting faster. You're still the author, still composing. Praxis optimizes the act of writing the note. It doesn't remove it.

## Praxis EMR pricing and the licensing model

Praxis prices differently too, and it's worth understanding before you compare.

| Praxis EMR (per third-party pricing) | Figure |
|---|---|
| First provider | ~$219/mo over 60 months, or ~$259/mo over 48 months |
| Additional providers | ~50% of the first-provider rate |
| Support, updates, upgrades | ~$70/mo, ongoing |
| Model | Licensing and ownership, term commitment |

These figures come from third-party pricing pages as of this writing; confirm current terms with Praxis directly. The structure is a licensing-and-ownership model over a multi-year term, not a cancel-anytime subscription. Some physicians prefer that: pay it down, own the license, keep the support line. Others want a monthly bill they can leave. Neither is wrong, but they're different commitments, and the term length is the part to read closely.

If a flat, published, month-friendly bundle is more your speed, [see what ships on each Patient Square plan](/us/pricing/) and compare the commitment side by side.

## Concept Processor vs ambient AI: which removes more work?

This is the real comparison, so let's be precise about it.

Praxis's Concept Processor learns your style and makes composing a note faster over time. The work it removes is *slowness*, the clicks and re-typing of template medicine. You still sit down and author each note; Praxis just helps you do it quicker and in your own voice.

An ambient AI scribe removes a different thing: the composing itself. It listens to the visit, captures the conversation, and drafts a structured note. You review, correct a line or two, and sign. You're not authoring from a blank page or a learned shortcut; the draft is already there when the visit ends.

| | Praxis Concept Processor | Ambient AI scribe |
|---|---|---|
| What it optimizes | How fast you type your note | Whether you type it at all |
| Your role | Author, composing in natural language | Reviewer, correcting a draft |
| Learns your style | Yes, over many encounters | Adapts to your note format |
| Best when | You love writing your own notes | Charting after hours is the pain |

Here's the canonical version of the ambient flow. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. Book a demo and watch it draft a note on your own visit type, then decide whether you want a faster pen or no pen.

## What an ambient bundle covers, honestly

If you move from Praxis toward ambient AI, here's what you get and what you don't:

- **The note drafts from the visit**, structured and ready about two minutes after you finish, not composed by you.
- **ICD-10 suggestions and a prescription draft** with the note, both draft-only until you sign. Not a coding engine, not pharmacy transmission.
- **A bundled AI EHR** at the Copilot tier, so the note and the record live in one place, one bill.
- **EHR-ready export (PDF, HL7, FHIR)** on every plan. An export, not a certified two-way interface.
- **What you give up:** Praxis's decades of clinical-autonomy features and its learned-style depth. Patient Square is younger and built around drafting the note, not perfecting how you write one.

Our safeguards are HIPAA compliant with BAAs available for every US customer, and the details are on the [security page](/us/security/). If you want the broader field, our [best EHR with AI scribe built in](../best-ehr-with-ai-scribe-built-in/) roundup and the [ambient AI vs dictation](../ambient-ai-vs-dictation/) explainer put the categories side by side.

## Why the Praxis pitch ages differently now

Praxis's core idea, learn the physician's style so charting gets personal and fast, was ahead of its time when template EMRs ruled. It solved a real problem: template medicine flattens your notes into checkboxes. A tool that learned your voice was a genuine step up from clicking pick-lists.

Ambient AI shifts the frame. The premise now isn't "how do I chart faster in my own voice." It's "why am I composing the note at all." When a scribe can listen to the visit and hand back a structured draft, the value of a faster pen shrinks against the value of no pen. That's not a knock on the Concept Processor's engineering, which is real. It's a change in what the job even is. A physician who spent years training Praxis to write like them has a sunk-cost pull toward staying, and that's understandable. The honest question is whether the thing you optimized, your typing, is still the thing worth optimizing.

For some physicians it is. If you genuinely enjoy composing your notes and the after-hours pile isn't your problem, Praxis's learned-style speed is hard to give up, and you shouldn't. For the physician charting at 8pm who'd trade authorship for a signable draft, the ground has moved, and the upgrade path runs toward ambient capture, not a better typing engine.

## When Praxis EMR is the better choice

The honest verdict. Keep or pick Praxis if you love composing your own notes and want a tool that learns your exact style, especially if you prefer a one-time licensing-and-ownership model over a subscription and you value the ONC certification. If clinical-documentation autonomy is your priority and after-hours charting genuinely isn't your main pain, Praxis's Concept Processor is a strong, distinctive tool, and we wouldn't tell you to trade it for an ambient scribe you don't need.

Choose ambient AI if the charting itself is the problem, not the speed of it. If you're finishing notes at 8pm and you'd rather review a draft than compose one, a faster pen isn't the answer; a scribe that writes the first draft is. Run the 7-day trial on a real clinic week, [see the note on your own visits](/us/), and let the mechanism, faster typing versus no typing, make the call for you.

---

## How to Switch From SimplePractice: A Migration Guide
https://patientsquare.com/us/blog/switch-from-simplepractice/
Published 2026-09-04 · Tags: migration, behavioral-health, simplepractice, how-to

The actual mechanics of leaving SimplePractice: data export, client comms, calendar cutover, and a week-by-week checklist so you don't lose a session.

Yes. As the account owner you can run a complete data export that includes clinical notes, billing documents, and other records. The export downloads as files, and the download links expire about one week after you generate them, so grab them promptly. Plan the export for a quiet day, because pulling a full practice's history takes time.

Switching from SimplePractice comes down to three moving parts: getting your data out, keeping clients informed, and cutting over the calendar without dropping a session. As the account owner you can run a complete export of clinical notes and billing docs, but the download links expire about a week later, and notes don't move automatically to a new tool. Plan it as a two-to-four-week sequence, not a weekend. This page is the checklist.

If you're still deciding *whether* to leave, that's a different question. Our [SimplePractice alternatives](../simplepractice-alternatives/) page covers the evaluation side, when the switch is worth it and when it isn't. This one assumes you've decided and want the mechanics.

> **Key takeaways**
>
> - As account owner, you can export clinical notes, billing docs, and records; download links expire about 1 week after you generate them.
> - Notes don't transfer automatically. SimplePractice can't even move clinical notes between its own accounts, so confirm which fields your new tool imports.
> - Budget 2 to 4 weeks for a solo or small practice: trial week, export-and-import week, cutover week.
> - Keep SimplePractice read-only through cutover so you can reference old notes and close open invoices.
> - Protect continuity of care first: client comms, reachability, and telehealth links matter more than the software.

## What can you actually export from SimplePractice?

Start here, because the export defines everything downstream. As the account owner, per SimplePractice's support docs, you can run a complete data export that includes clinical notes, billing documents, and other records. It comes out as downloadable files.

Two catches worth writing on a sticky note. First, the download links expire about one week after you generate them, so don't export a month before you're ready to import. Second, the export is a snapshot of files, not a live feed into your next tool. SimplePractice can't even transfer clinical notes, billing documentation, and appointments between two SimplePractice accounts. So don't assume a rival platform will magically absorb all of it either.

| SimplePractice export | What it holds |
|---|---|
| Clinical notes | Yes, in the complete owner export |
| Billing documents | Yes |
| Client demographics | Yes, exportable as a list |
| Appointments / calendar | Limited; often re-created, not migrated |
| Download link lifespan | ~1 week, then expires |

Before you pick a destination, [check what a new tool actually imports](/us/) and get the field list in writing.

## Which fields survive the move, and which you rebuild

This is the part that trips people. Different destinations import different things. Some tools take client demographics plus chart notes from a SimplePractice export. Others import only a client spreadsheet and expect you to attach the historical notes as reference files. Neither is wrong; you just need to know which one you're dealing with before cutover, not after.

A useful way to sort it: split your data into *live* and *reference*. Live data is what you'll actively use day one: current clients, active demographics, upcoming appointments. Reference data is the history you need to look up but rarely edit: closed notes, old invoices. Import the live data. Keep the reference data as your downloaded export files, backed up, and searchable. You rarely need to retype years of notes by hand, and any vendor who tells you that you do hasn't thought about it.

Patient Square offers **EHR-ready export (PDF, HL7, FHIR)** on every plan, which is the same principle in reverse: your notes should always be able to leave in a portable format. That's an export, not a certified two-way interface, and it's the question to ask any tool you're moving to. If a platform can't tell you how your data gets *out*, that's your answer about lock-in.

## The client-communication piece people skip

Your clients don't care which EHR you run. They care that they can reach you and that their telehealth link works. So the comms are simple, but skipping them is how a smooth migration turns into a scramble.

Send one short message before cutover: the practice is updating its systems, here's how to reach you during the transition, and here's your new portal or telehealth link if it's changing. Don't move telehealth links mid-week for someone with a Wednesday session. Don't cancel the old system until you've confirmed the new one holds a full clinic week. Continuity of care is the thing to protect. The software is just plumbing.

If you prescribe, note that a prescription draft in a new tool is a draft you review and sign, not an automated transmission, so nothing changes about your prescribing responsibility during a switch. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it on a real session before you commit to moving anyone.

## The week-by-week SimplePractice migration checklist

This is the artifact. Adjust the pace to your size, but keep the order.

| Phase | Week | What you do |
|---|---|---|
| Decide + trial | Week 1 | Confirm the note quality holds on real sessions. Run the new tool's 7-day trial. Get the import field list in writing. |
| Prep + comms | Week 2 | Draft your client heads-up. Set the cutover date on a low-volume week, not month-end. Reconcile open invoices in SimplePractice. |
| Export + import | Week 3 | Run the complete SimplePractice export as account owner. Download files before the ~1-week link expiry. Import live data; back up reference files. |
| Cutover | Week 4 | Run the new calendar live. Keep SimplePractice read-only. Send client comms and any new links. Verify a full clinic week before canceling. |

A few rules that save the week:

1. **Never export early.** The links expire in about a week. Export when you're ready to import, not before.
2. **Cutover on your quietest day.** Not the Monday of a packed week, and never at month-end when billing is live.
3. **Keep the old system read-only.** You'll reference old notes and close invoices for weeks. Cancel last, not first.
4. **Verify before you cancel.** Confirm the new tool held a real clinic week and your export files are downloaded and backed up.
5. **Test the note first.** If the new tool's note quality doesn't hold on your real sessions, none of the rest matters. That's the week-1 gate.

For the scribe-specific version of this, our [AI scribe migration checklist](../switch-ai-scribe-migration-checklist/) covers switching documentation tools without losing a clinic day, and the [pricing page](/us/pricing/) lists what ships on each plan. The [security page](/us/security/) has the encryption and audit details if compliance is part of your sign-off.

## Run the trial before you touch a single record

The most common migration mistake isn't a botched export. It's moving your whole practice to a tool you never really tested, then discovering in week two that the note quality doesn't hold.

So flip the order. Before you export anything, run the new tool's trial on real sessions, a full week if you can. For a therapist, that means seeing whether the note actually reads like your clinical voice, whether the structure fits your modality, and whether you'd sign it without a heavy rewrite. Ambient capture is a real workflow change from typing your own notes or filling a template, and some clinicians love it while others want more control. You want to know which camp you're in before you've migrated three years of client history.

Time yourself editing three real drafts during the trial. If you're correcting a line or two and signing, the tool works for you. If you're rewriting from scratch, it doesn't, and no export plan fixes that. This is why the checklist above puts "confirm note quality" in week one, ahead of everything. The data move is the easy part. The question of whether the destination actually solves your problem is the one worth a full trial week, because it's the only part you can't undo cheaply.

## When you should not switch from SimplePractice

The honest counter-case. If SimplePractice's therapy-native admin fits your practice, superbills, insurance panels, treatment-plan templates, and your complaint is minor, staying is cheaper than migrating. Every switch costs you a few weeks of attention you could spend seeing patients. Don't pay that for a small annoyance.

Switch when a specific, recurring pain justifies the work. The most common one we hear is note-writing: a therapist charting until 7pm every night, where an ambient scribe drafts the note from the session and hands the evening back. That's a real reason. "The new logo is ugly" is not. Review the [product workflow](/us/products/practice-copilot/) against your real visit types first, [see the note against your own visit type](/us/), and only start the export once you're sure the destination fixes the thing that made you shop in the first place.

---

## eka.care Pricing in India: The Doctor Plans, Decoded (2026)
https://patientsquare.com/in/blog/eka-care-pricing-india/
Published 2026-09-03 · Tags: pricing, eka-care, ai-scribe, ehr, abdm

EkaScribe publishes ₹1,499/month; eka.care's wider doctor tools are quote-or-listing priced. Here's what each covers, the ABDM edge, and a clear per-doctor ₹ to compare.

EkaScribe publishes ₹1,499 per month per doctor on its own site as of July 2026, with an annual option that saves about 17%. There's a free tier capped at 5 consultations a day, and the paid Pro tier lifts that to unlimited. That's the scribe specifically; eka.care's wider EMR and EHR tools are priced separately.

eka.care prices in pieces, which is why the total is confusing. The scribe, EkaScribe, publishes a clean ₹1,499 per month per doctor on its own site. The wider doctor EMR tools don't show a first-party price on eka.care's main plans page, so the numbers you find for those come from third-party listings. This page decodes each line, is honest about eka.care's real ABDM edge, and gives you a clear per-doctor Patient Square number to compare against. If you want the full head-to-head rather than just the price, start with the [alternatives comparison](../eka-care-alternatives-india/).

> **Key takeaways**
>
> - EkaScribe publishes ₹1,499/month per doctor first-party, with a free tier capped at 5 consults/day and unlimited on Pro, as of July 2026.
> - eka.care's EMR doctor tools aren't priced on its main plans page; third-party listings show Eka Doc Plus ~₹16,999/yr and Pro ~₹18,749/yr.
> - eka.care is ABDM-native with live ABHA linking. Patient Square's ABDM is roadmap, not live. That edge is real and worth naming first.
> - Patient Square's per-doctor anchor: Assist ₹1,599/month, Copilot ₹2,399/month with a bundled AI EHR, both annual, ex-GST plus 18%.

## What eka.care actually costs

The tricky part is that "eka.care pricing" is at least two different price tags. Here's how they split, as of July 2026.

| Product | Price | Source | Notes |
|---|---|---|---|
| EkaScribe (ambient scribe) | ₹1,499/month per doctor; ~17% off annual | First-party (ekascribe.ai) | Free tier 5 consults/day; Pro unlimited |
| Eka Doc Plus (EMR) | ~₹16,999/year (1 doctor, 2 staff) | Third-party listing | Not on eka.care's own plans page |
| Eka Doc Pro (EMR) | ~₹18,749/year (1 doctor, 2 staff) | Third-party listing | Not on eka.care's own plans page |

The scribe number is solid because it's on eka.care's own page. The EMR numbers are third-party, which means they could be stale or promotional, so treat them as a starting map and confirm with eka.care before you budget. The honest read: the scribe is cleanly priced and competitive; the EMR side is the part where you'll need a conversation to know your real total.

Notice the shape of those third-party EMR tiers, too. Eka Doc Plus and Eka Doc Pro are both listed as one doctor plus two staff, and the jump to Eka Clinic Pro at around ₹1,00,000 a year covers five doctors and fifteen staff. So the per-doctor cost actually falls as you scale up into a clinic tier, which is normal for suite pricing but easy to misread if you only look at the solo numbers. A two-doctor practice sits in an awkward middle: too big for the single-seat tiers, not yet at the clinic tier's break-even. That's exactly the size where a straight per-doctor price is easier to reason about than a staggered suite.

## What the ₹1,499 scribe includes

EkaScribe's ₹1,499 a month is a straightforward scribe subscription. It listens to the consult and drafts the note, and eka.care says it handles more than 20 languages, including English, Hindi, Bengali, Telugu, Tamil, Marathi, Gujarati, Kannada, Malayalam, Punjabi, and Urdu, and is tuned for varied medical accents. The free tier caps you at 5 consultations a day, which is a genuine trial-in-production allowance; Pro lifts that to unlimited.

For a doctor who mainly wants ambient documentation and doesn't need a new EMR, that ₹1,499 scribe is a clean, cheap entry. It's one of the more transparently priced scribes in the Indian market, and we'll say plainly that the number is fair for what it does.

The free tier deserves a note of its own, because 5 consults a day is a real trial, not a toy. A solo doctor can run EkaScribe on their first five patients every morning for weeks and learn exactly how the note reads before paying a rupee. That's a more honest way to evaluate a scribe than a scripted demo, and it's worth using. If you're comparing India-native scribes head to head, the [EkaScribe alternatives roundup](../ekascribe-alternatives-india/) lines them up on note quality and price rather than marketing.

## Where eka.care is genuinely ahead: ABDM

This is the concession that matters, and it goes at the front, not buried in a footnote. eka.care is an ABDM-native platform. ABHA verification and consent-based record sharing are built in, not bolted on, and eka.care participates in India's interoperable digital-health network as a matter of core design.

Patient Square's ABDM integration is on the roadmap and not live. We won't dress that up. If ABHA linking is a hard requirement for your clinic this quarter, eka.care holds a real, present-day advantage, and no amount of pricing analysis changes that. A clinic that needs records to travel across the ABDM ecosystem today should weigh that edge heavily, because switching away from it to save on a per-seat price would cost you the exact thing you wanted. If ABDM isn't your deciding factor, though, book a demo and compare the two notes on your own consults before price enters it.

## The per-doctor price anchor to compare against

Set that against a number you can read without a conversation. Patient Square publishes its India tiers per doctor: Assist at ₹1,599 a month on annual billing, Copilot at ₹2,399 with the bundled AI Copilot EHR and WhatsApp messaging, and Autopilot at ₹3,999, all ex-GST with 18% added. So Assist is about ₹1,887 all-in and Copilot about ₹2,831. The full ladder sits on the [pricing page](/in/pricing/).

Lined up against eka.care, the entry prices are close. EkaScribe's ₹1,499 scribe sits just under Patient Square's ₹1,599 Assist tier. The divergence is the bundle. Patient Square folds the AI EHR into the ₹2,399 Copilot tier, one product, one price. eka.care prices its EMR tools as a separate line on top of the scribe, so a clinic wanting both the scribe and a full EMR is likely adding the ₹1,499 scribe to an Eka Doc EMR subscription, and the combined total is the figure to ask about.

The AI Medical Scribe is the core module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Both tools do ambient documentation, so this isn't a scribe-versus-no-scribe choice. The pricing question is really about bundle shape and ABDM: one bundled ladder with roadmap ABDM, versus separately priced scribe and EMR with live ABDM.

One more thing to price in that the sticker doesn't show: what happens to the audio. Patient Square uses the recording to draft the note and then discards it. Only the structured output persists, which is the cleaner posture under the DPDP Act 2023 and the one we'd want if the roles were reversed. Ask eka.care the same question directly and get the retention policy in writing, because how a vendor handles consult audio tends to predict how it handles the rest of your patient data. It's not a line item, but it's a real part of the cost of trust.

## When eka.care's price is the right buy

Choose eka.care, on price, when ABDM sits at the centre of what you need, or when you want an India-native vendor covering both the scribe and the interoperability layer. The ₹1,499 scribe is competitively priced, and the ABDM depth is a present-day capability Patient Square can't match. For a clinic whose top concern is record continuity across the ABDM network, eka.care's price is buying the thing you most want, and that's the right reason to pick it.

Choose Patient Square when you want a single bundled price for the scribe and the EHR, transparent per-clinician tiers you can read without a call, and you're comfortable that ABDM linking is roadmap rather than live. For a clinic whose priority is documentation and a clean, predictable total, that fit is strong. Book a demo if you want to see the note and the bundled EHR against your own visits, or read the security posture under the DPDP Act 2023 on the [security page](/in/security/).

## Decide in one pass

1. Rank ABDM. If ABHA linking is required now, eka.care's live integration is the deciding factor, and price is secondary.
2. Separate the eka.care lines. Confirm whether you're buying the ₹1,499 scribe, an Eka Doc EMR tier, or both, and get the combined total from eka.care directly.
3. Compare like for like against the published ladder on our [pricing page](/in/pricing/), per doctor per month, ex-GST, then add 18% once.
4. Trial both scribes on your own consults, not a scripted demo, and check the note comes back in clean clinical English.

If ABDM is the job, eka.care's price buys it and this is mostly decided. If a single bundled price for documentation and records is what you're after, book a demo and test the note against a real clinic day before you assume the separately priced route is cheaper once you add it all up.

---

## How to Switch From eClinicalWorks: The Data-Export Reality
https://patientsquare.com/us/blog/switch-from-eclinicalworks/
Published 2026-09-03 · Tags: migration, ehr, eclinicalworks, how-to

Leaving eClinicalWorks means facing slow, fee-bearing data export. A realistic migration guide: export timelines, hidden costs, and a first-week plan.

Longer than most practices expect. In at least one reported case, a practice switching away was told it would take four to five weeks to get their data out of eClinicalWorks. Timelines vary by data volume and the export method, but treat data extraction as a multi-week line item in your plan, not a same-day download.

Leaving eClinicalWorks is less about the new tool and more about getting your data out of the old one. That part is slow and often fee-bearing. In at least one reported case, a practice was told extraction would take four to five weeks, and third-party trackers put migration around $500 to $1,500 per provider. So plan the export as a real project with a timeline and a budget, then keep the first week on the new system focused on today's visits, not a decade of history. This guide walks both.

If you're still pricing the decision, our [eClinicalWorks cost](../eclinicalworks-cost/) breakdown covers the base fee plus the per-encounter Sunoh scribe. This page picks up after you've decided to move.

> **Key takeaways**
>
> - Data extraction from eCW can take weeks. One reported switch was quoted 4 to 5 weeks; plan accordingly.
> - Export often carries a fee. Third-party trackers cite ~$500 to $1,500 per provider for migration.
> - eCW's 2017 DOJ settlement required data transfer on request, but some customers reported non-compliance, so push early.
> - C-CDA export covers structured clinical records; billing history and archives may need a separate service.
> - First week on the new tool is about running current visits cleanly, not migrating everything at once.

## Why getting data out of eClinicalWorks is the hard part

Most migration guides start with the new tool. This one starts with the exit, because that's where practices get stuck.

When a healthcare organization asked about switching away from eClinicalWorks, per Healthcare IT News, they were told it would take four to five weeks to get their data out. That's not a download; that's a project. Practices have also reported being pushed to keep paying while extraction dragged, rather than getting a clean glide path to close out accounts receivable. Other vendors, the same reporting notes, give departing customers a smoother off-ramp. eCW's reputation on this is the reason to plan hard.

There's a legal backdrop too. eCW's 2017 DOJ settlement, which resolved a $155 million False Claims case, required the vendor to transfer customer data to a rival EHR on request. But some customers publicly reported that eCW hadn't fully complied. So don't treat the settlement as a guarantee of fast, free extraction. Assume you'll have to actively push for your data, and start that conversation early.

Before you sign anywhere new, [confirm the destination can take your data cleanly](/us/) and give you a portable export back out.

## What the export actually covers, and what it doesn't

eCW supports C-CDA data portability, which lets you export clinical records and pick specific patient records before exporting. That's the structured clinical piece, and it's genuinely useful. What it doesn't automatically hand you is everything.

| eCW data type | Extraction path |
|---|---|
| Structured clinical records | C-CDA data portability export |
| Full historical archive | Often a separate migration / archiving service |
| Billing and AR history | Frequently a paid extraction; plan a wind-down window |
| Documents and scanned files | Confirm coverage; may need bulk EHI export |

The practical read: your live clinical data can move via C-CDA, but the long tail, years of billing history, scanned documents, closed encounters, may need a separate paid extraction or a migration vendor. Third-party trackers put that migration around $500 to $1,500 per provider depending on volume. Ask eCW, in writing, exactly what the C-CDA export includes and what costs extra. The gap between those two answers is your migration budget.

## Split your data into live and archive

Here's the mindset that keeps a big-EHR switch from stalling: you do not have to move everything before go-live. Split the data.

Live data is what you need on day one: your active patient panel, current demographics, upcoming appointments, and recent clinical context. Move that first. Archive data is the history you look up but rarely edit: old billing, closed encounters, scanned records from five years ago. That can follow as a downloaded C-CDA and document set you keep accessible for reference, or via an archiving service if your specialty needs deep lookback.

This matters because trying to migrate ten years of history before you see a single patient on the new tool is how practices delay a switch for months. Run current visits cleanly first. Backfill the archive on its own timeline.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. It ships EHR-ready export (PDF, HL7, FHIR) on every plan, so whatever you bring in can also leave, which is the lock-in question you just learned to ask. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it on a real visit type before you set a go-live date.

## The first-week plan on a new EHR

The switch checklist, ordered so nothing blocks a patient visit.

1. **Get the eCW extraction quote and timeline in writing.** Start this weeks before go-live, given the reported 4-to-5-week windows. This is the long pole.
2. **Trial the new tool on real visits.** Confirm the note quality and the record flow hold on your actual patient mix, not a demo script. Run the 7-day trial.
3. **Import live data only.** Active panel, demographics, upcoming appointments. Leave the archive for later.
4. **Set go-live on a low-volume week.** Not month-end, not the Monday of a packed schedule. Brief your front desk on the new check-in and note flow.
5. **Keep eCW read-accessible.** You'll reference old charts and close out open AR for weeks. Cancel only after the new system holds a full clinic week and your export files are downloaded and backed up.

For the documentation-tool version of this cutover, our [AI scribe migration checklist](../switch-ai-scribe-migration-checklist/) covers switching without losing a clinic day, and the [pricing page](/us/pricing/) lists exactly what ships per plan. Compliance sign-off details, encryption, access, audit status, are on the [security page](/us/security/).

## Protect your accounts receivable during the switch

The clinical data gets the attention. The money is where a rushed eCW exit quietly costs you.

When you flip to a new system, you still have open claims and unpaid balances sitting in eCW. Some vendors give departing customers a glide path: keep the old account read-accessible so you can work down existing accounts receivable while the new system runs current visits. The reporting on eCW's DOJ-settlement compliance suggests you should not assume a generous off-ramp here. Plan for a wind-down window where you keep eCW live long enough to close out billing, even after clinical go-live on the new tool.

Practically, that means two overlapping timelines. Clinical cutover happens on your chosen go-live week: new visits, new notes, new scheduling. Billing cutover trails it, sometimes by a month or two, while your team finishes collecting on claims that were already in flight. Don't cancel eCW the day you love the new EHR. Cancel it once the AR is worked down and your export files are safely in hand. A practice that rushes this can strand thousands in unpaid claims inside a system it can no longer log into. That's an avoidable, expensive mistake, and it's the one we'd flag hardest before you set a cancellation date.

## When you should stay on eClinicalWorks

The honest counter-case, because a switch this heavy needs a real reason. Stay on eCW if billing depth runs your practice. Its revenue-cycle engine, claims workflows, and enterprise support are deep and battle-tested across large multi-provider groups. Patient Square offers ICD-10 *suggestions* to speed coding, not a claims-scrubbing platform, and it isn't trying to replace a full RCM suite. If your evaluation centers on billing capability and scale, the export friction and switching cost probably aren't worth trading that away.

Move if your day is mostly visits and notes, you're tired of the per-encounter scribe meter climbing every busy Tuesday, and you want one predictable bill for documentation and the record. We think a lot of independent practices are paying enterprise-EHR prices for capability they never touch, and the flat bundle is the honest fit there. Review the [product workflow](/us/products/practice-copilot/) against your real visit types, [see the note against your own visits](/us/), and start the eCW extraction conversation early, because that timeline, not the new tool, is what decides your go-live date.

---

## Best EMR for Med Spa (2026): An Honest Roundup
https://patientsquare.com/us/blog/best-emr-for-med-spa/
Published 2026-09-02 · Tags: roundup, med-spa, comparison, ehr

The best med spa EMR depends on whether you need POS, booking, and before-after photos in one place, or just fast clinical notes. An honest 2026 comparison.

There's no single best; it depends on what runs your day. For an all-in-one aesthetics platform with POS, booking, memberships, and before-after photos, AestheticsPro and Zenoti are the usual picks. If your bottleneck is clinical notes rather than the front desk, a bundled AI scribe like Patient Square handles documentation, but not med-spa retail or booking.

The best EMR for a med spa depends on one question: is your bottleneck the front desk or the chart? If you need POS, booking deposits, memberships, and before-after photos in one system, an aesthetics-built platform like AestheticsPro or Zenoti is the core to buy. If your notes are the pain and booking is already handled, a bundled AI scribe drafts the clinical documentation at a published price. We'll be honest up front: Patient Square wins on exactly one axis, built-in ambient notes, and doesn't touch the med-spa business stack at all. Our [pricing page](/us/pricing/) shows what it does cover.

> **Key takeaways**
>
> - Med spas need two things that rarely live in one product: a business system (booking, POS, deposits, memberships, photos) and clinical records.
> - Aesthetics-built platforms (AestheticsPro, Zenoti, Boulevard, Pabau) own the business stack; third-party listings put them roughly $150 to $350+ a month or on custom quotes.
> - An ambient AI scribe drafts treatment notes from what you voice: injectable units, laser settings, consent. It won't manage before-after photos or run your POS.
> - Patient Square publishes $79 to $199 per clinician per month for documentation and a bundled AI EHR at the Copilot tier, but has no booking, deposits, or photo tooling.
> - Our honest verdict: for a med spa's core system, pick an aesthetics platform. Add a scribe only if clinical notes are eating your time.

## What does a med spa actually need from software?

More than most people shopping "med spa EMR" expect, which is why the category is confusing.

A med spa is a retail business and a medical practice at once. The retail side needs booking with deposits (no-shows are expensive), point-of-sale for product and package payments, membership and gift-card billing, and marketing to fill the calendar. The medical side needs charting for injectables and lasers, consent forms, controlled-substance documentation where it applies, and before-and-after photos tied to the record.

Almost every "best med spa software" list is really ranking business platforms that also do clinical charting to varying depth. That's the right lens: you're buying a system to run the spa, and the EMR is a module inside it. Where the lists disagree is how deep that clinical module goes, and how good the photo tooling is.

Here's the day that decides which problem you're really solving. A Tuesday, twenty-two appointments, mostly tox and filler with a couple of laser packages. Your booking tool kept the calendar full and took the deposits, your POS rang up the retail, the photos got captured. Good day. Then at 6:30 the front desk is gone and you've got a stack of treatment notes to write: units per site, lot numbers, the consent you talked through, the follow-up plan. If that pile is the part that keeps you late, your software gap isn't booking or payments. It's documentation. Naming which of those two hurts more is the whole decision.

## Who owns the med-spa business stack?

These are the platforms built for aesthetics from the ground up. If you want one login for the whole operation, your core system is one of these.

### AestheticsPro

The aesthetics-specialist pick with genuinely deep clinical charting. Reviewers describe it as among the most clinically detailed platforms for med spas, with a POS system, before-after photo tooling (alignment guides, ghosting, side-by-side comparison), and treatment-plan documentation. Third-party listings put pricing roughly in the $150 to $350 a month range depending on tier and user count, with per-user fees on top; treat those as estimates and confirm with the vendor. If controlled-substance documentation and detailed outcome tracking matter, this is a strong core.

### Zenoti

The pick for growing and multi-location med spas. Zenoti combines HIPAA-compliant clinical charting, before-after photo management, and e-prescriptions with booking, an AI receptionist, marketing automation, and memberships. Pricing is custom-quote, reflecting the full business-management scope. If you're scaling across locations and want one platform for everything, Zenoti competes hard here.

### Boulevard

Better described as premium booking and client experience with basic clinical compliance. Third-party listings cite around $175 a month. Reviewers position it for salons and spas that prioritize a sleek booking and payments flow over deep medical EMR tooling. If your clinical documentation is light and client experience is the priority, it fits; if injectable and laser records are complex, weigh the clinical depth carefully.

### Pabau

An all-in-one clinic-and-spa platform that bundles booking, EMR, forms, and marketing. It's a common AestheticsPro and Zenoti alternative for aesthetic clinics that want the business stack and the charting together. Pricing scales by clinic size; get a quote for your setup.

## Where an AI scribe fits (and where it doesn't)

Here's the part we can speak to directly, and the part where we'll draw a hard line so you don't buy the wrong thing.

AI Medical Scribe by Patient Square is one module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit; move up to the Copilot plan and it comes bundled with an AI EHR. In an aesthetics visit, that means the injectable units, product and lot numbers you call out, laser settings, and the consent conversation land in the draft when you voice them. You review and sign. For a med spa where the physician or NP is drowning in treatment notes after a full day of injectables, that's the exact burden it targets. If your practice leans dermatologic, our [AI scribe for dermatology](../ai-scribe-for-dermatology/) piece covers lesion and procedure notes in the same vein.

What it does not do, and we want this unmistakable:

| Med-spa job | Patient Square | Aesthetics platform |
|---|---|---|
| Clinical treatment notes | Ambient draft, review and sign | Manual or template entry |
| Before-and-after photos | Not managed | Built-in, with comparison tooling |
| Point-of-sale / retail | No | Yes |
| Booking with deposits | No | Yes |
| Memberships / packages | No | Yes |
| Published price | Yes, $79–$199/clinician/mo | Mixed; several quote-only |

Patient Square is documentation and records, not a med-spa business system. There's no POS, no deposit handling, no membership billing, and no before-after photo management. If you buy it expecting those, you'll be disappointed, and we'd rather say so now than after a demo.

## Our honest verdict for a med spa

We'll be straight, because a documentation tool is not the core system for most med spas.

For your core, pick an aesthetics-built platform. If you want maximum clinical charting depth and strong photo tooling, AestheticsPro is a leading option. If you're multi-location and want everything under one roof, Zenoti competes hard. If booking and client experience matter more than deep clinical records, Boulevard is the lighter pick.

Add an ambient scribe only when clinical notes are the specific thing eating your time. A high-volume injector writing detailed treatment notes after every patient has a documentation problem a scribe solves, running alongside whatever platform handles booking and payments. Notes leave via EHR-ready export (PDF · HL7 · FHIR), so they can live in your aesthetics record. Patient Square's plans publish at $79 to $199 per clinician per month, with a bundled AI EHR at the Copilot tier if you want a records home too; details are on the [security page](/us/security/) and the [pricing page](/us/pricing/). If you're a small cash-pay practice weighing scribe-plus-records at one price, our [best EMR for solo practice](../best-emr-for-solo-practice/) roundup runs that math.

So the verdict: aesthetics platform for the business, a scribe for the notes, and don't expect either to be the other. If notes are your pain, book a short demo and run the scribe on a real injectable visit.

## How to choose in one week

1. Separate the two problems: business operations (booking, POS, deposits, photos) versus clinical documentation. Rank which hurts more.
2. For the business core, demo two aesthetics platforms and price them all-in for your user count.
3. Check photo tooling specifically. If progress photos drive your records, test the capture-and-compare flow.
4. If notes are the real drag, run an ambient scribe on your busiest day, then confirm it exports into your chosen platform.
5. Compare total monthly cost, side by side, for everything you'd actually run.

For the documentation side, our guide on [how to evaluate an AI medical scribe](../ai-scribe-for-medical-notes/) lists the questions worth asking, and a short demo shows a finished note from a real aesthetics conversation.

## Frequently asked questions

The FAQ above covers the recurring ones: the best pick by need, whether a med spa needs a real EMR, what a scribe does and doesn't handle, and cost. For a scribe-buyer's checklist, see [how to evaluate an AI medical scribe](../ai-scribe-for-medical-notes/).

---

## HealthPlix Pricing in India: The Tiers, Decoded (2026)
https://patientsquare.com/in/blog/healthplix-pricing-india/
Published 2026-09-02 · Tags: pricing, healthplix, clinic-software, ehr

HealthPlix publishes Pro at ₹11,999/yr and Elite at ₹17,999/yr. Here's what each tier includes, the per-month math, and how it compares to a flat AI bundle.

HealthPlix publishes two paid tiers per doctor: Pro at ₹11,999 a year and Elite at ₹17,999 a year, per its own pricing page as of July 2026. That works out to roughly ₹1,000 and ₹1,500 a month respectively. Both are annual commitments, and add-on Plix Credits for patient communications are metered on top.

HealthPlix publishes real numbers, which already puts it ahead of most Indian clinic software. Two paid tiers per doctor: Pro at ₹11,999 a year and Elite at ₹17,999 a year, per its own pricing page as of July 2026. That's roughly ₹1,000 and ₹1,500 a month. This page decodes what each tier actually includes, where the metered costs hide, and how the whole thing reads against a flat AI bundle. If you've already decided HealthPlix isn't the shape you want, the [alternatives comparison](../healthplix-alternatives-india/) is the better start.

> **Key takeaways**
>
> - HealthPlix Pro is ₹11,999/year and Elite is ₹17,999/year per doctor, published first-party as of July 2026. That's about ₹1,000 and ₹1,500 a month.
> - Pro covers the working EMR; Elite adds analytics, multi-clinic support, a relationship manager, and double the messaging credits.
> - The metered line to watch is Plix Credits for patient communications, topped up separately once the tier's pool runs out.
> - Patient Square's Assist tier is ₹1,599/month annual and the Copilot tier with a bundled AI EHR is ₹2,399, both ex-GST plus 18%. The gap buys the ambient scribe.

## What HealthPlix actually costs

Here's the published rate card, as of July 2026, straight off HealthPlix's own pricing page.

| Tier | Published price | Rough per-month | Plix Credits included |
|---|---|---|---|
| HealthPlix Pro | ₹11,999/year per doctor | ~₹1,000/month | 5,000 |
| HealthPlix Elite | ₹17,999/year per doctor | ~₹1,500/month | 10,000 |

Both are per-doctor, annual. The per-month figures are computed from the annual fee, so treat them as an average rather than a monthly billing option. Two doctors on Pro is roughly ₹24,000 a year before any credit top-ups.

The honest read: for a specialty EMR that bundles OPD records, billing, pharmacy, queue management, and ABDM, ₹1,000 to ₹1,500 a month is a fair price. HealthPlix isn't expensive for what it packs in. The pricing question that matters isn't "is this cheap," it's "am I paying for the right thing." If what you're really paying to fix is the note, book a demo and see the ambient version before you commit to a year.

## What you get in Pro versus Elite

The tiers aren't a lite-versus-full split. Pro is a complete working EMR on its own.

**Pro** carries the specialty-specific OPD EMR, patient and clinic management, billing, pharmacy, IPD and lab management, queue management, clinical decision support, teleconsultation, patient communications, ABDM features, a patient app, and clinic reports. For a solo doctor or a small clinic, that's the whole job. The 5,000 Plix Credits handle a moderate volume of patient messages.

**Elite** keeps all of that and adds the operational and analytics layer: Robin analytics for the clinic and prescriptions, a private database, satellite-clinic support for a multi-location practice, a dedicated relationship manager, a virtual clinic, and 10,000 credits. If you run one location and don't live in dashboards, most of the Elite delta doesn't touch your day. If you run three clinics and want prescription-level analytics, it earns its keep.

So the tier decision is really about breadth of operation, not depth of the core EMR. A single-clinic doctor rarely needs Elite. A growing multi-site group often does.

## Where the metered costs hide

The line that isn't in the headline number is Plix Credits. Patient communications, the reminders and messages that go to patients, draw down the credit pool included in your tier. Run through 5,000 on Pro and you top up separately. It's not a hidden fee exactly, it's disclosed, but it's a variable cost that scales with how much you message patients, and it's easy to under-budget if you send a lot of reminders.

The other line to pin down before you sign is renewal. The rate you sign up at and the rate you renew at aren't guaranteed to match, and that's true across clinic software, not a HealthPlix-specific quirk. Ask for the year-two figure in writing. A published price is a good sign, but a published sign-up price with a negotiated renewal is a weaker one.

There's also the multi-doctor math to run before you assume a per-doctor suite is cheap at scale. Pro is per doctor, so a three-doctor clinic is roughly ₹36,000 a year in software before credits, and every extra clinician adds a full seat. That's fine if each doctor genuinely uses the EMR, but a clinic with one heavy user and two occasional ones pays the same three seats. Count the seats that will actually log in daily, not the ones on the org chart, and price against that.

## How this reads against a flat AI bundle

HealthPlix and Patient Square price similarly at the entry, then diverge on what the money buys.

| | HealthPlix | Patient Square |
|---|---|---|
| Entry tier (per doctor) | Pro ₹11,999/yr (~₹1,000/mo) | Assist ₹1,599/mo annual, ex-GST |
| With bundled EHR | Included in Pro/Elite | Copilot ₹2,399/mo annual, ex-GST |
| Core approach | Template-driven EMR, you write the note | Ambient AI drafts the note, codes, and Rx |
| Metered add-ons | Plix Credits for messaging | Unlimited visits and notes, no per-note metering |
| ABDM | Live features today | Roadmap, not live |

_Prices from each vendor's pages, July 2026; Patient Square figures ex-GST, add 18%._

The structural difference is where the price lands you. HealthPlix gives you a mature EMR and asks you to drive the documentation faster. Patient Square asks you to pay a bit more per month and removes the typing: its AI Medical Scribe, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. You can book a demo and watch that happen on a real consult before you weigh it against the sticker. Add 18% GST and the Assist tier is about ₹1,887 all-in; the Copilot tier with the bundled AI Copilot EHR is about ₹2,831. The full ladder, ex-GST, sits on the [India pricing page](/in/pricing/).

Why this matters at all comes back to the two-minute consult. Irving et al.'s 67-country BMJ Open review put India's average primary-care consultation at about two minutes. A cheaper EMR doesn't buy you time in that window; it just gives you a faster place to type when there's no time to type. If your notes are getting finished at 9pm, the per-month price gap is buying back your evenings, and that math usually favours the tool that writes the note during the visit.

Put a rough number on it. Say the ambient tier costs you about ₹900 more a month than HealthPlix Pro after GST. If it saves you 45 minutes of after-hours charting a day, five days a week, that's roughly 15 hours a month. You're paying under ₹60 an hour to not do the charting yourself. For most doctors that's the cheapest hour they'll buy all month. Whether the trade lands that cleanly depends on how much charting you actually carry into the evening, which is exactly the thing to measure before you decide, not assume.

## When HealthPlix's pricing is the right buy

Choose HealthPlix, on price, when you want a proven specialty EMR with a deep template library and live ABDM features, and you're comfortable writing the prescription yourself. For a high-volume specialist who's fast on templates and doesn't want to change how they document, ₹1,000 to ₹1,500 a month for that breadth is a genuinely good deal, and the ambient layer would be paying for something you don't need. HealthPlix has years of refinement and ABDM linking today, which Patient Square's roadmap doesn't yet match.

Choose Patient Square when your single biggest drain is documentation and you'd rather have the note drafted for you than type it faster. The extra per month is the ambient scribe, and for a doctor losing an hour a night to charting, that trade usually pays for itself. If you've decided to move, the [switching guide](../switch-from-healthplix-to-ai-native-ehr-india/) covers what exports cleanly and what doesn't.

## Decide in one pass

1. Confirm the current published price and the renewal figure with HealthPlix, in writing, ex-GST.
2. Estimate your Plix Credit usage. Heavy patient messaging adds a variable line on top of the tier.
3. Time your charting for two clinic days. If most of your evening is notes, price the ambient tool against the hours it gives back, not just the sticker.
4. Trial the note quality on your own consults. A demo flatters everything.

If HealthPlix at ₹11,999 or ₹17,999 a year covers your job and the notes get written, it's a fair buy. If the notes are the thing that never gets done because there's no time in the consult, book a short demo and watch a real Tuesday clinic turn into signed notes before you assume the cheaper tier does the job you actually have.

---

## MocDoc Pricing (2026): What Indian Clinics Actually Pay
https://patientsquare.com/in/blog/mocdoc-pricing-india/
Published 2026-09-02 · Tags: pricing, mocdoc, hms, clinic-software

MocDoc doesn't print a price. What third-party estimates suggest, what drives the quote up, and how a published ₹1,599/mo rate card compares.

MocDoc doesn't publish pricing. Every quote is scoped to your modules, doctor and bed counts, and lab or pharmacy setup after a demo call. A third-party analysis estimates annual tiers from about ₹60,000 (Starter) to ₹3,00,000 (Advanced), with a contact-us tier above, but MocDoc hasn't confirmed those figures.

MocDoc doesn't publish a price. Not on the homepage, not in a footer, not behind a pricing tab. Every path on the site ends at a Book a Demo form, and the quote that follows is scoped to your module mix, your scale, and whether a lab or pharmacy runs inside the software. Third-party analyses estimate annual tiers from about ₹60,000 to ₹3,00,000 and up. That's the short answer.

The longer answer is more useful, because a quote-only price isn't a mystery. It moves on five predictable things, and you can walk into the sales call knowing every one of them.

> **Key takeaways**
>
> - MocDoc publishes no ₹ figure. Pricing is quote-only, behind a demo form, scoped per deal.
> - A third-party pricing analysis estimates ₹60,000/yr (Starter) to ₹3,00,000/yr (Advanced), with a contact-us tier above. MocDoc hasn't confirmed these numbers.
> - Quotes move on module list, scale, customization, add-ons, and renewal. Pin each one in writing.
> - Pricing documentation instead of operations? A printed rate card exists: Patient Square from ₹1,599 per doctor per month on annual billing, ex-GST (add 18%).

## Why isn't MocDoc's price on the page?

Because MocDoc isn't one product. It's a suite: hospital management, clinic and polyclinic management, a laboratory system, pharmacy, dental, ophthalmology, even an ART module for fertility centres, and the company reports 1500+ institutions across 25+ states. A 30-bed hospital switching on IPD billing and a two-room Salem clinic that wants OPD records are not buying the same thing, so MocDoc prices the deal, not the product.

That's a defensible way to sell an operations suite. It's a slow way to buy one. If you came here wanting a number for a budget row, MocDoc's site won't give you one today, and any figure you find elsewhere is somebody's estimate. Our [HMS cost breakdown](../hms-software-cost-breakdown-india/) walks through how these suite quotes get assembled line by line, and it's worth ten minutes before any vendor call.

## What do the estimates actually say?

One third-party pricing analysis, published by Scispot and fetched in July 2026, breaks MocDoc into four estimated tiers:

| Estimated tier | Estimated annual cost | Rough per-month math |
|---|---|---|
| Starter | ₹60,000/yr | ₹5,000/mo |
| Growth | ₹1,50,000/yr | ₹12,500/mo |
| Advanced | ₹3,00,000/yr | ₹25,000/mo |
| Ultimate | Contact for pricing | Scoped per deal |

Treat every row as an estimate. MocDoc hasn't published or confirmed these figures, and your quote will reflect your module list, not a table on someone else's blog.

Two smaller line items from the same analysis deserve attention. It estimates customization at 500 to 5,000 US dollars for workflow changes, and it quotes a user review describing video consultation as a separately charged add-on. Neither shows up in a headline quote unless you ask.

Also note the shape of these numbers: they're clinic-level or hospital-level, not per-doctor. Spread the Growth estimate across a three-doctor clinic and you're near ₹4,167 per doctor per month. Spread Starter across the same clinic and it's about ₹1,700. The per-doctor cost of a suite depends entirely on how many doctors share it, which is exactly why MocDoc asks about your scale before quoting. If you'd rather skip the scoping call for the documentation half of the problem, book a demo and test a scribe on a live OPD morning instead.

## What moves a MocDoc quote? Pin these five

| Quote driver | Why it moves the number | Get this in writing |
|---|---|---|
| Module list | HMS, clinic, LIMS, pharmacy, dental, ART are each scoped separately | The exact modules your quote covers, named |
| Scale | Doctors, beds, and locations set the band | The counts your price assumes |
| Customization | Estimated at 500–5,000 US dollars for workflow changes | What's standard versus billable |
| Add-ons | Video consultation described in a review as a separate charge | Every metered or add-on line item |
| Renewal | Year-one pricing doesn't bind year two | The year-two figure, on paper |

Ten minutes of questions. That's all this is. Clinics that get burned on suite pricing are rarely quoted wrong; they're quoted narrowly, and the width shows up in year two.

## What a printed rate card looks like

Now the other half of the comparison, because plenty of readers pricing MocDoc don't actually have an operations problem. They have a documentation problem: OPD notes that never get written, because nothing fits between token 41 and token 42.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It listens in English, Hindi, and 20+ Indian languages, Hinglish included, and the note always comes out in clean clinical English. And the price is on the page:

| Practice Copilot plan | Monthly | Annual billing | What it adds |
|---|---|---|---|
| Assist | ₹1,999/mo | ₹1,599/mo | The scribe and scheduling essentials |
| Copilot | ₹2,999/mo | ₹2,399/mo | Bundled AI Copilot EHR + WhatsApp messaging |
| Autopilot | ₹4,999/mo | ₹3,999/mo | AI Receptionist, AI Follow-ups, priority support, ROI analytics |

All prices are per clinician, ex-GST, with 18% GST added at billing. With GST, the annual-billing tiers land at about ₹1,887, ₹2,831, and ₹4,719 a month. Every plan carries unlimited visits and notes with no per-note metering, EHR-ready export (PDF · HL7 · FHIR), and specialty-aware templates ready out of the box. There's a 7-day trial if you want to check note quality on your own patients before talking to anyone.

We think per-doctor printed pricing should be the default for anything a solo doctor or a small clinic buys. You can budget it in one glance and compare it in two, and nobody sits through a discovery call just to learn a number. The full tier detail is on the [India pricing page](/in/pricing/).

One honest scope note: Patient Square does not claim MocDoc's LIMS or pharmacy depth. Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside MocDoc as the incumbent system. It is demo-priced, so a hospital-scale conversation looks like MocDoc's: scoped, and fairly so.

## When is MocDoc the better buy?

When the software has to run your operation, MocDoc earns the quote process. A multi-department clinic, a small hospital, or a diagnostic lab that needs sample tracking, pharmacy stock and expiry control, and OP/IP billing under one login is exactly the buyer MocDoc built for, and per-deal pricing is reasonable when deals genuinely differ that much. The [full MocDoc comparison](../mocdoc-alternatives-india/) walks the breadth-versus-depth decision in detail.

Just don't price a fifteen-module suite to fix a notes problem. That's buying a hospital to get a consultation room.

## How to run the price conversation

Ask for the quote itemized by module, with your doctor and bed counts stated on it. Ask for the year-two renewal in the same document. Ask which line items are metered, including video consultation and customization. Then put that number next to what the narrower tool costs for your actual bottleneck. Our [EHR cost guide for India](../ehr-software-cost-india-buyers-guide/) has a fuller list of the fees that hide in scoped quotes.

If the bottleneck is documentation, the math is already public: from ₹1,599 a month per doctor, ex-GST, with the note drafted while the patient is still in the room. Book a demo and bring your busiest OPD day as the test case.

---

## Best EHR for Direct Primary Care (2026): Honest Picks
https://patientsquare.com/us/blog/best-ehr-for-direct-primary-care/
Published 2026-09-01 · Tags: best, direct-primary-care, ehr-comparison, membership-medicine

Elation, Atlas.md, Hint, Cerbo, and a published-price scribe-plus-EHR bundle compared for DPC. Membership-first vs documentation-first, no quote-form runaround.

It depends on what you're solving. For DPC-native membership and billing, Elation, Atlas.md, and Hint are purpose-built. For documentation speed on long DPC visits at a flat published price, Patient Square bundles an ambient scribe and an AI EHR at $119 per clinician monthly. Membership-first and note-first are different problems.

The honest answer splits by what you're actually buying. If you need DPC-native membership billing, employer contracts, and payments wired into the chart, the purpose-built options are Elation, Atlas.md, and Hint, with Cerbo and Akute in the mix. If your real problem is documentation time on long membership visits and you want a flat published price, Patient Square bundles an ambient AI scribe and an AI EHR at $119 per clinician per month.

Those are two different problems, and most "best DPC EHR" lists blur them. This page keeps them apart, names where each vendor wins, and says plainly where we don't. If you already know charting is your bottleneck, book a demo and skip to the table.

> **Key takeaways**
>
> - DPC-native platforms handle what makes DPC different: recurring membership billing, payments, and employer-panel management. Elation, Atlas.md, and Hint are built for that.
> - Elation's DPC pricing lands around $349 per provider monthly per third-party listings; Atlas.md and Hint are quote-priced by panel. Those are outside estimates.
> - DPC sells a flat membership with no per-visit billing, so a flat, unmetered per-clinician scribe price fits the model instead of fighting it.
> - As of 2026, federal changes let patients pay DPC memberships from an HSA, removing a long-standing friction point for the model.
> - Patient Square has no membership billing. It has an ambient scribe, a bundled AI EHR, and a price on a page: $119 per clinician monthly, annual.

## The two problems a DPC EHR gets bought to solve

Problem one is the business model. Direct primary care runs on a flat monthly membership instead of insurance claims, per the AAFP's framing of the model. That means the software has to do things a claims-based EHR never touches: charge a recurring subscription, handle failed payments, manage employer-sponsored panels, and keep the whole thing running without a billing department. DPC-native platforms exist precisely because generic EHRs assume a claim at the end of every visit, and DPC doesn't have one.

Problem two is documentation. DPC's whole pitch is time. A member pays a retainer for a physician who isn't rushing and isn't half-watching a screen. So a keyboard between you and the patient undercuts the product, and reconstructing six long visits at 9pm undercuts your evening. That's not a billing problem. It's a "who writes the note" problem, and an ambient scribe is what attacks it.

Work out which one is yours before you shortlist. The vendors below split cleanly along that line, and plenty of practices end up wanting both layers.

## How the options compare for DPC

| Platform | DPC-native billing? | Known for | Pricing |
|---|---|---|---|
| Elation | Yes | Unified clinical, membership, and payments for DPC | Third-party estimate ~$349/provider/mo |
| Atlas.md | Yes | One of the first DPC-built EHRs, lean solo focus | Quote-only |
| Hint | Yes | Membership management at scale, employer panels | Quote-only |
| Cerbo | Partial | Integrative/DPC crossover, supplement tracking | Third-party estimate ~$281/provider/mo |
| **Patient Square** | **No; not a membership-billing tool** | **Ambient scribe + Patient Square EHR or an existing EHR** | **Published: $119/mo annual with EHR** |

All rival figures here are third-party estimates, not vendor quotes, and Atlas.md and Hint don't post a public number at all. Only one row has a price you can read without a sales call. We think that fact earns its place in the table. For the deeper Elation number, our [Elation pricing breakdown](../elation-ehr-pricing/) walks through what the tiers actually include.

## The DPC-native platforms, one by one

### Elation

Elation is built to run a DPC practice end to end: clinical documentation, membership management, and payments in one platform, in its own framing. That unification is the draw. You sign a member, bill the subscription, and chart the visit without stitching three tools together. Third-party listings put it around $349 per provider per month, higher for plans that add insurance-billing features. If you want the record and the membership engine as one system, Elation is the default DPC answer.

### Atlas.md

Atlas.md was one of the first EHRs designed specifically for the DPC model, and it shows in the fit for lean, independent solo physicians. It's cloud-based and built to cut administrative overhead so a one-doctor practice can run without a back office. Pricing isn't public. For a solo DPC doc who wants a system that assumes the DPC model from the ground up rather than bolting it onto a claims EHR, Atlas.md has genuine product-market fit.

### Hint

Hint's strength is membership at scale. It powers recurring billing, network solutions, and employer-contract management for direct-care organizations, which matters most once you're past a single solo panel. If your DPC growth runs through employers or a large member base, Hint's subscription-management depth is where it pulls ahead. Pricing is quote-based.

### Cerbo

Cerbo sits at the integrative-and-DPC crossover. It's charting, scheduling, messaging, and supplement tracking in one interface, and it shows up in both DPC and functional-medicine roundups. Third-party listings estimate around $281 per provider monthly. If your DPC practice leans wellness or integrative, Cerbo is worth a look alongside the pure-DPC names.

## Where Patient Square fits a DPC practice

Straight up: we don't do membership billing, payment processing, or employer-panel management. There's no subscription dunning and no recurring-charge engine. If those are your core requirement, pick a DPC-native platform and don't look back.

What Patient Square does is the documentation half, and it fits DPC's economics unusually well. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. A DPC annual might run forty-five minutes through family history, sleep, stress, and a plan you talk through together. That length is signal, not noise, for an ambient scribe. You keep eye contact the whole visit and still walk out with the note mostly written.

Here's the part that suits DPC specifically: the pricing shape matches yours. DPC sells a flat membership with no per-visit billing, and Patient Square is a flat $119 per clinician per month on annual billing, unlimited visits and notes, no per-note metering. There's no claim volume to meter against, so usage-based documentation pricing would make no sense for your panel. The Copilot plan bundles the scribe with the AI Copilot EHR, and every note exports as PDF, HL7, or FHIR, so it drops into Elation or Atlas.md if you keep one of those. Audio is captured, drafted, and discarded, worth telling members plainly in a trust-first practice. Security posture, BAAs for every US customer, is on the [security page](/us/security/).

The adjacent workflow, how the scribe behaves across long membership visits, is covered in our [scribe for concierge and DPC practices](../ai-scribe-for-concierge-medicine/) guide. So the fit is specific: DPC practices whose charting outweighs their need for a new billing engine, or who want the note drafted and are happy to keep their membership platform. Real segment. Not every segment.

## When Elation, Atlas.md, or Hint is the better fit

Choose Elation if you want the record system, membership billing, and payments unified in one DPC-built platform and you'll use all three. For a practice that wants to run the whole business inside one login, that unification is worth the premium.

Choose Atlas.md if you're a lean solo DPC physician who wants software that assumes the DPC model from the start and keeps overhead minimal. It was built for exactly that shape of practice.

Choose Hint if membership at scale is the point: employer contracts, network deals, a large panel where subscription management is the hard part.

Choose Patient Square if the notes are the pain, you want the scribe and a record system at a flat published price, and you'd rather keep or skip a separate billing platform than pay for one you won't fully use. That's the honest split. For the bundled category beyond DPC, our [best EHR with an AI scribe built in](../best-ehr-with-ai-scribe-built-in/) roundup covers it, and [primary care documentation](../ai-scribe-for-primary-care/) covers the adjacent visit type.

## A one-week way to decide

Test the two layers on their own terms. For the DPC-native platform, run a real membership signup end to end in each vendor's demo, then ask for the full price in writing including membership-billing and payment-processing fees, because on a subscription business those percentages compound. Book demos with Elation, Atlas.md, and Hint and watch each run a member from signup to charge.

Then test the documentation half on your own patients. Request an assisted 7-day trial after workspace setup. Run it on a real long-form DPC day, count minutes from room exit to signed note, and set that against whatever you do now. That number is the decision. Pricing is on the [pricing page](/us/pricing/), and a short demo shows the note on a DPC visit before you commit the week.

Two problems, several vendors, one call. Buy for the problem you actually have.

---

## Best EHR for Neurology (2026): An Honest Roundup
https://patientsquare.com/us/blog/best-ehr-for-neurology/
Published 2026-09-01 · Tags: roundup, neurology, comparison, ehr

The best neurology EHR depends on whether you need imaging integration and specialty templates or fast notes for long cognitive exams. An honest 2026 roundup.

It depends on your priorities. For deep specialty templates and imaging integration, AdvancedMD and PrognoCIS are common neurology picks, and NextGen offers an ambient assist option. If your bottleneck is documenting long cognitive and neuro exams, a bundled ambient scribe like Patient Square drafts those narratives fast, but doesn't replace neurology-specific billing or imaging tooling.

The best EHR for neurology depends on what actually slows you down. If you need imaging integration, specialty templates for epilepsy and movement disorders, and neurology billing in one system, a neurology-built EHR like AdvancedMD, PrognoCIS, or NextGen is the safer core. Practice Copilot then works alongside it. If those specialty capabilities are not requirements, Patient Square EHR can be the system of record from the Copilot tier, with ambient notes built in. Our [pricing page](/us/pricing/) shows the documented scope.

> **Key takeaways**
>
> - Neurology documentation is heavy by design: a long structured exam plus cognitive assessment, much of it narrative rather than checkbox.
> - Neurology-built EHRs (AdvancedMD, PrognoCIS, Praxis, NextGen) own specialty templates and imaging integration; most are quote-only.
> - NextGen ships Ambient Assist for structured notes from the visit; a standalone ambient scribe is the alternative if you don't want a large enterprise EHR.
> - Patient Square publishes $79 to $199 per clinician per month, with a bundled AI EHR at the Copilot tier, but has no CT/MRI/EEG integration or neurology billing.
> - Our honest verdict: for a full neurology practice, pick a neurology-built EHR. Add a scribe when the exam narratives are the specific time sink.

## Why neurology carries such a documentation load

More than most specialties, and it's structural, not a workflow you can shortcut away.

The neurological exam is one of the longest in medicine: cranial nerves, motor and sensory testing across multiple domains, reflexes, coordination, gait. Layer on cognitive assessment for dementia, TBI, ADHD, and related conditions, which demands detailed narrative about test results and behavioral observations, and a single new consult generates a lot of writing. A 2022 Frontiers in Digital Health article by Rodríguez-Fernández and colleagues, arguing for shorter neurology notes, cites an estimate that around 40% of physician EHR time goes to documentation. In neurology, the note itself is longer than average, so that burden lands hard.

For context on the broader problem, primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit, per the American Medical Association. Neurology's per-patient documentation tends to run heavier than that baseline. The point isn't a precise neurology figure; it's that the writing, especially the narrative parts, is the bottleneck.

## Who owns the neurology-EHR stack?

These are the systems built for neurology practices. If you need imaging integration, specialty templates, and neurology billing in one place, your core is one of these.

### AdvancedMD

A common neurology pick for its flexible, neurology-tailored templates covering conditions like Alzheimer's, ALS, epilepsy, migraine, Parkinson's, and stroke, plus centralized lab and imaging integration. If specialty templates and an all-in-one practice-management-plus-EHR are the priority, it competes strongly. Pricing is quote-based; get a number for your provider count. Our [AdvancedMD alternatives](../advancedmd-alternatives/) piece covers the flat-bundle-versus-modules tradeoff.

### PrognoCIS

A cloud EHR for practices that want clinical and administrative functions in one system, with customizable neurology templates for documenting complex exams and procedures. A solid core for a practice that wants specialty depth and doesn't need the very largest enterprise footprint.

### Praxis EMR

Template-free by design: it learns each neurologist's documentation habits to cut charting time, which appeals to clinicians who dislike click-heavy templates. Worth a look if your objection to most EHRs is the template forest itself.

### NextGen (with Ambient Assist)

The enterprise option that also ships ambient documentation. NextGen Ambient Assist turns the visit conversation into a structured SOAP note placed in the NextGen chart, pending your review. If you want a large neurology EHR and ambient notes from the same vendor, this is the built-in path. The trade is the footprint and cost of an enterprise EHR. Our [AI scribe for NextGen](../ai-scribe-for-nextgen/) piece covers what that integration gets you.

## Where an ambient scribe fits (and where it doesn't)

Here's the part we can speak to directly, with a clear line so you don't buy the wrong thing.

AI Medical Scribe by Patient Square is one module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit; move up to the Copilot plan and it comes bundled with an AI EHR. Neurology is unusually well suited to this because you already narrate much of the exam out loud, and the visit is conversation-heavy: a dementia workup, a headache history, a movement-disorder assessment. The cognitive-exam narrative, the reasoning, and the plan land in the draft when you voice them. You read it and sign.

Think about a first-visit dementia consult. Forty-five minutes: family history, medication reconciliation, a cognitive screen, the caregiver filling in gaps the patient can't, then your assessment and a plan that has to hold up for the next visit and maybe for a disability determination. That's a long narrative note, the kind you used to reconstruct at 7pm from a few scribbled lines. When you talk through the screen and your reasoning the way you already do for the family, the draft is waiting before the next patient is roomed. What you don't hand off is the clinical judgment: you confirm the ICD-10 suggestions, you own the assessment, and you decide what the plan says.

What it does not do, and this matters in neurology specifically:

| Neurology job | Patient Square | Neurology-built EHR |
|---|---|---|
| Long exam / cognitive narrative notes | Ambient draft, review and sign | Template or narrative entry |
| CT / MRI / PET / EEG integration | No | Yes, typically built in |
| Neurology-specific templates | No; general SOAP | Yes, condition-specific |
| Procedure documentation (EMG, Botox) | Only what you narrate | Specialty templates |
| Neurology billing engine | No | Yes |
| Published price | Yes, $79–$199/clinician/mo | Mostly quote-only |

Patient Square EHR is a record-system option, but it is not a neurology-specific suite. There's no verified imaging integration, EEG interface, neurology-specific billing, or EMG or injection templates. If those run your practice, keep a neurology-built EHR and use Practice Copilot alongside it; otherwise, evaluate Patient Square EHR as the system of record.

## Our honest verdict for a neurology practice

We'll be direct, because a scribe is not the whole system for a full neurology practice.

For your core, pick a neurology-built EHR. If specialty templates and imaging integration are the priority, AdvancedMD and PrognoCIS are strong. If you hate templates, Praxis is worth the demo. If you want enterprise scale with ambient notes from one vendor, NextGen with Ambient Assist fits.

Add a standalone ambient scribe when the exam narratives are the specific thing eating your evenings, and especially if you don't want to migrate your whole EHR to get ambient notes. A neurologist writing long cognitive and neuro-exam narratives after every patient has a documentation problem a scribe solves, running alongside the record system you already keep. Notes leave via EHR-ready export (PDF · HL7 · FHIR), and the Copilot plan bundles an AI EHR if you want a records home too. Safeguards are HIPAA compliant with BAAs available, and our SOC 2 Type II audit is in progress; the [security page](/us/security/) has the detail.

So the verdict: neurology-built EHR for imaging and billing depth, an ambient scribe for the narrative burden, and don't expect either to be the other. If the exam notes are your pain, book a short demo and run the scribe on a real cognitive consult.

## How to choose in one week

1. Rank your two problems: neurology-specific tooling (imaging, templates, billing) versus documentation time. Weight the one that hurts more.
2. For the core, demo two neurology-built EHRs and confirm your imaging and EEG integrations work end to end.
3. If notes are the drag, run an ambient scribe on a real dementia or headache consult, your longest narrative visit.
4. Confirm the export path so notes reach your neurology record cleanly.
5. Compare all-in monthly cost for your provider count in one spreadsheet column.

For the documentation side, our guide on [how to evaluate an AI medical scribe](../ai-scribe-for-medical-notes/) lists the questions worth asking, and a short demo shows a finished neurology note from a real conversation.

## Frequently asked questions

The FAQ above covers the recurring ones: the best pick by need, why neurology notes run long, what a scribe captures, imaging integration, and cost. For the enterprise-EHR ambient path, see [AI scribe for NextGen](../ai-scribe-for-nextgen/).

---

## Functional Medicine EMR: A 2026 Buyer Guide
https://patientsquare.com/us/blog/functional-medicine-emr/
Published 2026-09-01 · Updated 2026-08-29 · Tags: functional-medicine, emr-comparison, integrative-medicine, ambient-documentation

Evaluate functional-medicine EMRs with real lab, supplement, intake, charting, billing, security, migration, and documentation tests.

Test the workflows the practice actually uses: detailed intake, longitudinal history, conventional and specialty labs, medications and supplements, treatment plans, inventory or dispensing, patient communication, payments, reporting, and data export. Vendor claims should be checked in the exact product and plan being quoted.

A functional-medicine EMR has to fit the practice's actual care and business model. That may include lengthy intake, a longitudinal patient story, conventional and specialty labs, medicines and supplements, detailed plans, inventory or dispensing, direct-pay programs, and frequent patient communication. A generic feature grid will not tell you whether those jobs work in the product being quoted.

Power2Practice and Cerbo both present software for functional or integrative practices. That makes them reasonable demonstration candidates, not automatic winners. Patient Square belongs in the evaluation when ambient documentation is part of the problem. Its published scope should not be stretched into specialty functions it does not claim here.

> **Key takeaways**
>
> - Build the shortlist from real workflows and partner requirements.
> - Make vendors demonstrate the same intake, lab, supplement, plan, payment, and record-exit cases.
> - Ask for a complete written quote instead of relying on third-party price estimates.
> - Treat Patient Square as a scribe and EHR option within its published scope, not as proof of specialty lab or dispensing functions.
> - Test any export against the receiving system before making it part of clinical operations.

## Separate specialty operations from documentation

Start by listing the work that is specific to your practice. Which laboratories send orders and results? How are supplements recommended, reconciled, sold, or dispensed? Does the practice hold inventory? Are visits billed to insurance, paid directly, sold in programs, or covered by memberships? Which forms, consents, reports, and patient messages are required?

Then list the documentation burden. Note the encounter types that take the longest to finish, the histories clinicians repeatedly reconstruct, and the plan sections that require the most correction.

These lists may point to one product or to two products used alongside each other. Do not assume a scribe supplies a lab or dispensing workflow. Do not assume a specialty EMR solves the note-review problem. Test each job.

## Build a requirements matrix

Use a pass, fail, or unresolved score. Avoid vague ratings such as "strong" or "modern."

| Requirement | Evidence to collect |
|---|---|
| Intake | Staff and patient complete a representative intake, including corrections |
| Longitudinal record | Clinician finds the relevant history and sees what changed over time |
| Labs | Practice demonstrates orders, inbound results, review, patient release, and error handling for named partners |
| Medicines and supplements | Team demonstrates reconciliation, plan changes, and the approved ordering or dispensing path |
| Inventory | Staff receives, adjusts, dispenses, and audits a test item if inventory is required |
| Treatment plan | Clinician creates, revises, shares, and retrieves the practice's normal plan |
| Payments | Team runs the actual insurance, direct-pay, program, or membership case |
| Reporting | Product produces each required clinical, operational, and financial report |
| Security | Vendor supplies contract terms, access controls, audit information, incident duties, and deletion process |
| Exit | Practice receives a usable sample of clinical and administrative data |

If a partner or feature is essential, name it. "Supports labs" is not enough when the practice depends on a particular laboratory and result format.

## Evaluate Power2Practice and Cerbo from first-party evidence

Power2Practice markets its platform to functional and integrative medicine. Ask the team to demonstrate the exact workflows in your matrix and identify which product, module, partner, and fee supports each one.

Cerbo's functional and integrative medicine page describes supplement ordering, treatment plans, inventory, patient communication, lab connections, and intake forms. Those are vendor-published claims. They still need to be confirmed for your account, named partners, plan, and configuration.

For either vendor, ask what is native, what comes from a third party, what requires setup, and who owns support when two systems are involved. Put material answers in the contract or statement of work.

## Keep Patient Square inside its published boundary

AI Medical Scribe by Patient Square produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The prescription draft is not sent to a pharmacy. The clinician is responsible for checking and approving the note, codes, and prescription details.

Patient Square EHR is included from the Copilot tier in Practice Copilot. A practice can choose that bundled route or keep an existing EHR or EMR alongside Patient Square. This page does not claim specialty lab ordering, supplement dispensing, inventory, or a named functional-medicine-system integration for Patient Square. Verify those requirements separately.

The public portability claim is **EHR-ready export (PDF · HL7 · FHIR)**. It does not promise automatic filing, certification, conformance, or a successful import into Power2Practice, Cerbo, or another product. Ask the receiving vendor which formats, versions, fields, and identifiers it accepts. Then test with non-production data.

## Compare documentation with real encounters

Use consented encounters that reflect the practice's normal work. Include a new-patient intake, a follow-up with several plan changes, a medication or supplement reconciliation, and a visit with outside results.

For every draft, record omissions, incorrect statements, material edits, time to final review, and any medicine detail that needed correction. Check whether the structure matches the practice's approved note and whether staff can move the final record through the tested workflow.

Patient Square says the draft is normally ready about two minutes after the visit. Measure that claim in your environment, along with review time. A fast draft that needs extensive correction is not a finished note.

## Compare complete commercial terms

Ask every vendor for a quote that states:

1. Price unit and contract term.
2. Included users, locations, modules, storage, and support.
3. Implementation, training, conversion, and interface work.
4. Lab, transaction, messaging, payment, clearinghouse, or partner fees.
5. Taxes and other variable charges.
6. Renewal rules and notice periods.
7. Termination, data export, and post-termination access.

Patient Square publishes Copilot at a $119 per-clinician monthly equivalent on annual billing or $149 month to month. Check the current [pricing page](/us/pricing/). Do not compare that figure with a functional-medicine platform quote until the included scope and operational work are aligned.

## Review privacy, security, and exit

Patient Square says visit audio is processed in memory and discarded when the note is drafted. It says notes are encrypted in transit and at rest, a BAA is available to US customers, and visits can be exported or deleted. Have the practice's privacy or security lead review the current [security page](/us/security/) and agreement.

Apply the same review to every candidate. Include subcontractors, lab partners, payment services, access logs, breach duties, backups, retention, and deletion. Ask for a sample export early enough to inspect it before contract signature.

## Buy for the workflow you can prove

The right product is the one that passes the practice's named tests at an acceptable complete cost. A purpose-built claim is a reason to schedule a demonstration. It is not a substitute for one.

If you want to test Patient Square's documentation and bundled-EHR scope, Request your 7-day trial. Keep specialty requirements visible, score the result, and leave unresolved claims out of the decision.

---

## Best EMR for Home Health (2026): Honest Picks
https://patientsquare.com/us/blog/best-emr-for-home-health/
Published 2026-08-31 · Tags: best, home-health, emr-comparison, ambient-documentation

Axxess, Homecare Homebase, and WellSky run the agency. A published-price ambient scribe handles the note. Which layer you actually need, compared honestly.

For agency operations, the three names that run the industry are Axxess, Homecare Homebase, and WellSky. They handle OASIS, EVV, scheduling, and Medicare billing end to end. If your bottleneck is documentation time on visits rather than agency plumbing, Patient Square adds an ambient scribe at a published $119 per clinician monthly.

If you run a Medicare-certified home health agency, the best "EMR" for you is an agency platform, and the three that run the category are Axxess, Homecare Homebase, and WellSky. They own OASIS, EVV, scheduling, and PDGM billing. But if what's actually eating your clinicians is charting six visits from the front seat between drives, that's a documentation problem, and Patient Square bundles an ambient scribe and an AI EHR at a published $119 per clinician per month.

Two different problems, and most "best home health EMR" lists smash them together. This page keeps them apart. If the note is your bottleneck and you already have an agency system, book a demo and skip to the table.

> **Key takeaways**
>
> - The agency-scale platforms are Axxess, Homecare Homebase, and WellSky (formerly Kinnser). They run OASIS-E, EVV, and Medicare PDGM billing, which a scribe or a general EMR does not.
> - Those three are quote-priced by census and agency size, so there's no public per-clinician number to compare.
> - Home visits break connectivity in ways a clinic never does. Offline, encrypted capture is the feature that decides whether a scribe survives in the field.
> - Patient Square has no OASIS or EVV module. It has an ambient scribe, a bundled AI EHR, and a price on a page: $119 per clinician monthly, annual.
> - The honest split: keep the agency platform for compliance and billing, add a scribe if the visit note is where the hours go.

## The two jobs a home health "EMR" is bought to do

Job one is running the agency. Home health has requirements no other setting carries. OASIS-E is a structured assessment CMS ties to reimbursement and outcomes. Electronic Visit Verification proves the clinician was in the home. PDGM decides what Medicare pays. Plan-of-care oversight, physician orders, aide scheduling across a territory: this is agency plumbing, and Axxess, Homecare Homebase, and WellSky exist because generic software handles none of it. As Homecare Homebase's own explainer lays out, OASIS-E documentation alone is a heavy, standards-bound assessment tied directly to payment.

Job two is writing the visit note. A field nurse does a wound check at 9, a med reconciliation at 10:30, a fall-risk assessment after lunch, each in someone's living room, then reconstructs the narrative later. Home Health Care News reported in 2025 that agencies adopting AI documentation tools describe "dramatic" cuts to time spent on that charting. That's a different job from filing OASIS, and it's the one an ambient scribe attacks.

Figure out which one hurts before you shortlist. If it's OASIS and billing, you need an agency platform. If it's the note, you need a documentation layer. You might need both.

## How the options compare for home health

| Software | Runs the agency? | Known for | Pricing |
|---|---|---|---|
| Axxess | Yes | OASIS, EVV, offline field charting, no long lock-in | Quote-only by agency size |
| Homecare Homebase | Yes | Scheduling optimization, field visibility, RCM | Quote-only, enterprise-tier |
| WellSky (ex-Kinnser) | Yes | Mature OASIS and billing, large user base | Quote-only by census |
| **Patient Square** | **No; not an agency-operations system** | **Ambient scribe + Patient Square EHR or an existing EHR** | **Published: $119/mo annual with EHR** |

Only one row has a number you can read without a sales call. We think that belongs in the comparison, not buried behind a form. The agency platforms price by census and service lines because that's genuinely how their cost scales; the trade is you can't compare them on a page.

## The agency platforms, one by one

### Axxess

Axxess is the all-in-one cloud platform agencies reach for when they want OASIS automation, EVV, billing, and PDGM analysis in one system, with mobile apps that let field staff chart offline and upload wound photos. Agencies also like not being locked into multi-year contracts. If you're a growing home health or hospice agency that needs the full compliance-and-billing stack, Axxess is a real answer.

### Homecare Homebase

Homecare Homebase (HCHB) leans operational. Its strength is scheduling optimization, real-time visibility into the field, and revenue-cycle management across a large clinician workforce. Agencies tend to pick HCHB for the logistics of moving staff and managing cash more than for the charting experience itself. It fits larger, multi-branch operations.

### WellSky

WellSky, formerly Kinnser, is one of the most widely deployed home health systems, with a long track record in OASIS documentation, billing, and mobile point-of-care use. Clinicians often find it intuitive in the field. For an agency that wants a mature, proven platform with a big user base, WellSky is the safe institutional choice.

## Where Patient Square fits a home health agency

Straight up: we don't file OASIS, run EVV, or bill PDGM. There's no plan-of-care oversight module and no aide scheduling. If those are what you're shopping for, one of the three above is your system of record, and you should buy it.

What Patient Square does is the note. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In a home, the winning feature is what happens when the signal drops. The scribe captures visit audio encrypted on the device (AES-256-GCM) and drafts the note once you're back on a connection, so a basement wound check in a dead zone still becomes a note. Audio is processed and then discarded; there's no recording kept after the draft.

The Copilot plan bundles that scribe with the AI Copilot EHR at $119 per clinician per month on annual billing, unlimited visits and notes, no per-note metering. Every note leaves as an EHR-ready export (PDF · HL7 · FHIR), so it moves into your agency system without retyping. How that export works across any record system is covered in our [work-with-any-EHR guide](../ai-scribe-any-ehr-export/), and the field workflow for spotty coverage is in [offline capture in low-signal clinics](/in/blog/ai-scribe-offline-low-connectivity/). Security posture, BAAs included for every US customer, sits on the [security page](/us/security/).

So the fit is narrow and honest: agencies whose clinicians lose the evening to charting, that want the note drafted per visit and a price they can read. That's a real segment. It isn't every agency.

## When Axxess, HCHB, or WellSky is the better fit

Choose Axxess, Homecare Homebase, or WellSky, no contest, if you need OASIS, EVV, and Medicare billing. A scribe cannot and does not do those jobs, and a Medicare-certified agency without a compliant agency platform is not a real option. Buy the platform first.

Pick Axxess if you want the full compliance-and-billing stack with offline field apps and flexible contracts, especially as a growing agency. Pick Homecare Homebase if your pain is logistics: scheduling a large field workforce and tightening the revenue cycle across branches. Pick WellSky if you want the mature, widely-used option your billers and clinicians likely already know.

Pick Patient Square when the remaining pain is the clinical record rather than agency operations. Practice Copilot can use Patient Square EHR as the practice record or work alongside an agency's existing EHR, but it does not replace OASIS, EVV, Medicare billing, or workforce logistics. If that split matches your problem, our roundup of [EHRs with an AI scribe built in](../best-ehr-with-ai-scribe-built-in/) covers the bundled category more broadly.

## A one-week way to decide

Test the two layers separately, because they solve different things. For the agency platform, run demos with Axxess, HCHB, and WellSky, and push for the full quote in writing: base, implementation, and per-clinician add-ons by your actual census. The sticker is never the total, and OASIS-and-billing implementations are real projects.

For the documentation half, run it on your own field day. Request an assisted 7-day trial after workspace setup. Send a nurse out with it on a normal route, including at least one home where coverage is bad, and count minutes from visit end to signed note against whatever they do now. That number is the whole decision. Pricing is on the [pricing page](/us/pricing/), and a short demo shows the note on a home visit before you spend the week. For the broader charting-time picture, [how clinicians cut charting time](../reduce-charting-time-clinicians/) has the field-wide math.

Two jobs, three platforms, one add-on. Buy for the job that actually hurts.

---

## Medinous Alternatives: Hospital or Clinic? An Honest Split
https://patientsquare.com/in/blog/medinous-alternatives-india/
Published 2026-08-31 · Tags: alternatives, his, hospital-software, comparison

Medinous is a 25-year enterprise HIS for hospitals across India and the GCC, quote-priced. The right alternative depends on your door: hospital or clinic.

Running a whole hospital as one system. Medinous is an enterprise hospital information system with 25-plus years of implementations across India, the GCC, and the wider Middle East. Its strength is operational breadth: clinical, billing, pharmacy, supply chain, and insurance claims under one platform, with editions for large hospitals, mid-size hospitals, and clinics.

"Medinous alternatives" is two searches wearing one query, and they want different answers. Medinous is a 25-year enterprise hospital information system, built to run a whole hospital across India and the GCC, and quote-priced. Hospital Copilot offers a complete Patient Square HIS/EHR for a greenfield hospital or an alongside path that keeps Medinous as the incumbent system. A clinic gets the same choice through Practice Copilot: Patient Square EHR from the Copilot tier or an existing EHR. You can book a demo to map either path against your workflow.

> **Key takeaways**
>
> - Medinous is an enterprise HIS with 25-plus years of implementations across India, the GCC, and the Middle East, in editions for large hospitals, mid-size hospitals, and clinics.
> - Pricing is quote-only. Expect a scoping cycle, not a rate card.
> - Patient Square splits by segment: Practice Copilot for clinics from ₹1,599/month per doctor + 18% GST, Hospital Copilot for hospitals, demo-priced.
> - If you need hospital-wide operations, Medinous's class fits. If your doctors can't finish notes, that's our lane.

## Which buyer are you?

Match your row before anything else. Most "alternatives" pages skip this and end up comparing a hospital-wide platform against a documentation tool, which helps no one decide.

| You are | What Medinous offers you | What Patient Square offers you | Honest call |
|---|---|---|---|
| A large or mid-size hospital | Enterprise HIS: admissions, billing, pharmacy, supply chain, insurance claims, multi-site | Hospital Copilot: complete Patient Square HIS/EHR or alongside an existing HIS/EHR, demo-priced | Compare required modules, then choose the record-system path |
| A clinic or small practice | A clinic edition of an enterprise-grade platform | Practice Copilot: ambient scribe + bundled AI EHR, published per-doctor pricing | Depends on whether operations or documentation is what actually hurts |

If you're a hospital and operations are the fire, the [HIS software roundup](../best-his-software-india/) covers that field more broadly. If you're a clinic, keep reading; the split gets sharper below.

## What Medinous is genuinely built for

Give Medinous its due. It has spent 25-plus years putting hospital software into large facilities, and it says so plainly: a presence across 10-plus countries, deep in the GCC and Middle East as well as India. That's not a first-year vendor. Running a large hospital as one system, where registration flows into the chart, the chart into billing, and billing into an insurance claim, is genuinely hard, and Medinous has done it at scale for a long time.

The product is broad by design. It ships in tiers, an enterprise edition for large hospitals, a lighter edition for mid-size ones, and a clinic edition, so a group can standardise on one vendor across very different sites. In GCC markets, where national claim platforms and Arabic-English record-keeping are the norm, that operational depth is a real reason hospitals pick it.

None of what follows argues that machinery is weak. The question is narrower: is that the machine your problem actually needs?

## What does Medinous cost?

You find out after a sales conversation. Medinous publishes no price list, which is standard for hospital software at this class. A 300-bed hospital and a two-doctor clinic genuinely can't be priced off the same card, and enterprise HIS deals get scoped by size, modules, and number of sites. That's fair.

But be clear-eyed about what it means for your timeline. You're committing to a discovery cycle before you see a number, and the number will be negotiated rather than posted. The renewal, the per-module add-ons, and the implementation cost all live inside that quote, so get them in writing before you sign anything.

Patient Square takes the opposite posture for clinics: the price is on the page. Assist is ₹1,599 a month per doctor on annual billing, Copilot is ₹2,399 with the bundled AI Copilot EHR and WhatsApp messaging, and Autopilot is ₹3,999, all ex-GST with 18% added on the invoice. So Assist lands around ₹1,887 all-in per doctor. The full ladder sits on the [pricing page](/in/pricing/). Hospital Copilot is demo-priced, because hospital scope honestly does need scoping. If you want to see where the quote-only model comes from and what it hides, our [HMS cost breakdown](../hms-software-cost-breakdown-india/) walks through it.

## The clinic door: platform breadth vs documentation depth

An enterprise platform, however capable, doesn't change the one number that runs an Indian OPD: the two-minute consult. Irving et al.'s 67-country BMJ Open review put India's average primary-care consultation at about two minutes, near the short end of a global range that runs from under a minute to 22.5 minutes. A registration screen doesn't lengthen that. A better dashboard doesn't write the note. At 6pm the OPD register is full and the records are thin, and that's the gap a clinic feels every single day.

That gap is where the platform starts. The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It follows English, Hindi, and 20+ Indian languages, code-mixed the way real consults sound, and always returns the note in clean clinical English. Every plan carries unlimited visits and notes and EHR-ready export (PDF · HL7 · FHIR). At the Copilot tier, the bundled AI EHR makes it the record system too, not just the note-writer.

To be equally plain about the limits: ICD-10 comes as suggestions, the prescription is a draft you sign, ABDM integration is on our roadmap and not live, and SOC 2 Type II is in progress rather than certified. Encryption, access controls, and data-ownership specifics are on the [security page](/in/security/). We think a clinic buying a documentation tool should be able to read all of that before a sales call, not after. If the note is your problem, book a demo and run it on a live consult.

The split below is documentation only, on a busy OPD day. The note burden is the part that breaks at volume, not the queue or the bill.

| On a packed OPD day | Type the note yourself, mid-OPD | Ambient layer drafts the note |
|---|---|---|
| The note | Compressed to one line, or skipped, to keep the queue moving | Structured SOAP note ready to review about two minutes after the visit |
| After the last patient | Charting backlog cleared from memory, hours later | Nothing to catch up on; the notes are already written |
| Medico-legal exposure | Thin records, a weak spot if ever questioned | Complete, retrievable records without slowing the queue |
| Attention in the room | Split between the screen and the patient | On the patient, not the keyboard |

_Source: Irving et al., BMJ Open 2017; Indian Medical Council medical ethics code, 2002; clinic workflow estimate._

Thin notes aren't cosmetic. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. Whatever the regulatory status, a register full of one-line entries is a weak spot that sits with the clinician, not the software vendor.

## The hospital door

Hospitals are the more interesting case, because here it isn't Medinous versus Patient Square at all. An HIS in Medinous's class runs the operation: admissions, billing, pharmacy, supply chain, insurance claims, multi-site reporting. What it historically hasn't fixed is clinicians typing discharge-quality documentation from memory at 9pm after a full ward round.

Hospital Copilot supports two deployment paths, both priced through a demo conversation. A greenfield hospital can use the complete Patient Square HIS/EHR as its record system. An established hospital can keep Medinous as the incumbent HIS/EHR and run Patient Square alongside it. Medinous remains the stronger fit when its supply-chain, insurance, or national-claims workflows are requirements; the Patient Square path should not imply those modules exist when they do not. The [Suvarna comparison](../suvarna-alternatives-india/) walks the same choice against another long-running enterprise HIS, and the [Attune comparison](../attune-alternatives-india/) does it for a lab-heavy platform.

## When Medinous is the better choice

Pick Medinous, or something in its class, when the problem is operational scale. A multi-site hospital group that needs one cloud view across departments. A facility that lives on insurance-claim throughput and wants billing, pharmacy, and claims integrated. A management team that wants enterprise reporting more than it wants faster notes. That's what a 25-year HIS is built to do, and a documentation tool is not a substitute for it. If you're a GCC hospital that needs national-claim-platform integration and Arabic-English records, that's squarely Medinous territory, not ours.

Pick Patient Square when the expensive minutes are clinical. Doctors typing after hours. Notes compressed to a line. Records that wouldn't survive scrutiny. A clinic can use Patient Square EHR or keep an existing EHR through Practice Copilot. A hospital can use the complete Patient Square HIS/EHR or keep Medinous through Hospital Copilot's incumbent-system path.

## How to decide without a committee

1. Name your door: hospital or clinic. The table at the top ends the search for one of them.
2. Write down the one metric that's actually bleeding: claim rejection rate, billing leakage, or unfinished notes. Buy against that metric only.
3. Get both numbers on the table. A scoped Medinous quote, and the published per-doctor ladder on our [pricing page](/in/pricing/).
4. Trial the documentation claim on real consults, in the languages your OPD actually speaks. The 7-day trial exists so you can run it on a live clinic day, not a scripted demo.

If operations are the fire, scope Medinous seriously and get the renewal in writing. If it's the notes, book a short demo and watch one of your own consults come back as a structured, signable record.

---

## Birlamedisoft Alternatives: Beyond the 42-Module HMS (2026)
https://patientsquare.com/in/blog/birlamedisoft-alternatives-india/
Published 2026-08-29 · Tags: alternatives, hms, hospital-software, comparison

Quanta HIMS covers 42+ hospital modules, quote-priced. What the module list doesn't fix, what implementation takes, and the AI-native option from ₹1,599/mo.

A hospital information management system from Pune-based Birlamedisoft, operational since 2001. Quanta spans 42+ modules across registration, OPD, IPD, EMR, nursing, OT, pharmacy, lab, PACS, blood bank, billing, insurance, and NABH indicator reporting, sold on-premise as Quanta V4 or cloud as Quanta V5. It's a full department-by-department hospital suite.

Birlamedisoft's Quanta HIMS is one of the older names in Indian hospital software: Pune-based, operational since 2001, and sold as a suite of 42-plus modules covering nearly every department a hospital runs. If you need that suite, it belongs on your shortlist. The reason people search for alternatives is usually narrower: none of those modules writes the doctor's note, and the pricing is a quote, not a number. Patient Square starts at a published ₹1,599 a month per doctor plus 18% GST, and you can book a demo before any sales cycle starts.

> **Key takeaways**
>
> - Quanta HIMS is a genuine department suite: 42+ modules, on-premise (V4) or cloud (V5), NABH-aligned reporting, from a vendor operational since 2001.
> - Pricing is quote-only, and Birlamedisoft's own material puts go-live at roughly 2-4 weeks for small clinics and 10-16 weeks for large hospitals.
> - A module list maps to departments. It doesn't buy back the minutes doctors spend typing notes, which is the cost clinics feel daily.
> - Practice Copilot publishes per-doctor pricing (₹1,599-₹3,999/month annual, ex-GST) and supports Patient Square EHR or an existing EHR.

## What Quanta HIMS actually is

Give the suite its due. Birlamedisoft has been building hospital software from Pune since 2001, and Quanta HIMS is the accumulated result: registration, OPD and IPD management, ADT and queue handling, an EMR with doctor desk and nursing notes, OT scheduling, ICU flows, pharmacy, laboratory via its own LIMS, radiology with PACS, blood bank, billing with insurance, TPA and GST handling, and NABH indicator reporting, running to 42-plus modules by Techjockey's product breakdown. It ships two ways: Quanta V4 on-premise for hospitals whose IT policy wants servers in the building, and Quanta V5 on the cloud. The company's site claims deployments across 30-plus countries.

That's a department-complete hospital system from a vendor that has survived two decades of Indian healthcare IT. Hospitals that need one vendor across pharmacy, lab, blood bank, and billing are the buyers Quanta was built for, and nothing below argues otherwise.

## The module-count trap

Here's the pattern we think hospital buyers should resist: scoring HMS vendors by module count. Forty-two modules beats thirty-five, on paper. But a module list answers "which departments get software" and says nothing about the question that decides whether doctors adopt any of it: what changes for the person in the consult room on Monday morning?

Walk the list again with that question. Registration module: the front desk wins. Billing: accounts wins. Pharmacy, LIMS, PACS, blood bank: those departments win. The doctor's line item, the clinical note, appears as an EMR module, which means a screen the doctor types into. The suite computerises where the note is stored. The typing, at 9pm, from memory of a patient seen at 11am, stays exactly where it was. The operative 2002 medical ethics code requires three-year retention for indoor records and timely production of requested records. Thin OPD notes still leave the clinician exposed when a patient asks for a record; the abeyed 2023 regulations do not impose a current three-year OPD rule.

So a 42-module suite and an unwritten note coexist happily. They just never meet. That's not a flaw in Quanta. It's a category limit: HIMS is operational software, and documentation is a clinical-minutes problem.

## What does Quanta cost, in money and in weeks?

Birlamedisoft doesn't publish pricing. Quanta is quoted per hospital, sized by beds, modules, and deployment, which is normal for the category. The number you negotiate is also not the whole cost: the company's own FAQ material puts implementation at roughly 2-4 weeks for small clinics, 6-8 for medium hospitals, and 10-16 weeks for large ones. Add training, data migration, and the annual maintenance line, and the licence becomes one row in a project budget. Our [HMS cost breakdown](../hms-software-cost-breakdown-india/) decodes that quote structure line by line if you're building the spreadsheet.

Patient Square's clinic pricing is public instead: Assist at ₹1,599 a month per doctor on annual billing, Copilot at ₹2,399 with the bundled AI Copilot EHR and WhatsApp messaging, Autopilot at ₹3,999, all ex-GST with 18% GST added, so Assist invoices at about ₹1,887 all-in. No implementation project; a clinic can be capturing visits the same week. Hospital Copilot, the hospital-scale product, is demo-priced, because hospital scope does genuinely need scoping. The ladder is on the [pricing page](/in/pricing/), and if a published number reads better than a quote cycle, book a demo and skip the discovery calls.

## The module no HIMS ships

The module that writes the note is the whole of Patient Square's wedge. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It captures consultations in English, Hindi, and 20+ Indian languages, including code-mixed Hinglish, and always returns clean clinical English. Every plan includes unlimited visits and notes with no per-note metering, plus EHR-ready export (PDF · HL7 · FHIR), so notes can flow into whatever HIMS your hospital already runs.

Boundaries, stated plainly because vendor pages rarely do: ICD-10 arrives as suggestions, not a coding engine. The prescription is a draft you review and sign, not e-prescribing. ABDM integration is on our roadmap, not live, so if ABHA linking is a hard requirement today, weigh that honestly. SOC 2 Type II is in progress; data handling follows DPDP Act 2023 standards, with audio processed in memory and discarded once the note drafts. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## Suite vs copilot: what changes on Monday

| | Quanta HIMS | Patient Square |
|---|---|---|
| Built as | Department suite, 42+ modules | AI clinical platform: Patient Square EHR or existing-EHR path |
| Who feels it first | Front desk, billing, pharmacy, lab | The doctor mid-consult |
| Time to live | ~2-16 weeks by hospital size, per vendor FAQ | Clinics: days. Hospitals: scoped |
| Pricing | Quote per hospital | Published: ₹1,599-₹3,999/mo per doctor + GST; hospital product demo-priced |
| Deployment | On-premise (V4) or cloud (V5) | Cloud, web or mobile capture |
| The clinical note | An EMR screen the doctor types into | Drafted from the conversation, reviewed and signed |
| NABH indicator reporting | Built in, per vendor | Not our product; keep your HIMS for this |

One table, one honest summary: Quanta changes how the hospital runs. Patient Square changes how the doctor's day ends.

## When Birlamedisoft is the better choice

Choose Quanta when you're buying hospital operations. A 100-bed multispecialty that wants pharmacy, LIMS, PACS, blood bank, billing, and NABH reporting from a single vendor with two decades of installs has a real case, and an on-premise mandate makes V4 one of the few serious options in that class. An ambient scribe does not replace any of that, and pretending it could would waste your evaluation.

Choose Patient Square when the bleeding is documentation and its verified module scope fits. A clinic can run Practice Copilot on Patient Square EHR or alongside an existing EHR. A hospital can use the complete Patient Square HIS/EHR or keep Quanta through Hospital Copilot's incumbent-system path. Compare blood bank, OT, pharmacy, billing, and reporting requirements before choosing. The [hospital-management-system explainer](../hospital-management-system-explained/) maps the module landscape, and the [Suvarna comparison](../suvarna-alternatives-india/) runs the same deployment decision against another veteran enterprise HIS.

## How to decide without a 16-week pilot

Ask three questions of your own hospital or clinic this week. Which department's failure costs you the most money: billing, pharmacy, or records? Whose hours are you actually trying to buy back: administrators' or clinicians'? And can you get a written quote, with implementation weeks and AMC, to put next to a published per-doctor price?

If the answers point at operations, get the Quanta demo and scope it properly. If they point at the note, the test is cheap: a 7-day trial on real consultations, your languages, your OPD pace. Book a demo and read the first note it hands back. That single artifact settles more than any module list.

---

## Ezovion Alternatives in India: Depth vs Breadth (2026)
https://patientsquare.com/in/blog/ezovion-alternatives-india/
Published 2026-08-29 · Tags: alternatives, hms, ai-scribe, comparison

Ezovion is an emerging cloud HMS with 50+ modules and a voice feature, quote-priced. How ambient AI documentation differs, and what a published ₹1,599 buys.

Ezovion Solutions is an Indian cloud hospital management platform, now part of QuantumNexis, a Healthcare Triangle subsidiary, per its own site. It spans 50+ modules including OPD, IPD, EMR, operation theatre, pharmacy, lab, radiology with PACS, revenue cycle, blood bank, and HR, with cloud and on-premise deployment plus mobile apps.

Ezovion is one of the newer names in Indian hospital software: a cloud-first HMS with 50-plus modules, mobile apps, and, unusually for the category, a voice story of its own. Pricing is quote-only. So an honest comparison with Patient Square turns on two questions: is your problem hospital breadth or documentation depth, and is speech-to-text the same thing as an ambient scribe? Short answers: they're different purchases, and no. Patient Square publishes its price, from ₹1,599 a month per doctor plus 18% GST, and you can book a demo to test the documentation claim directly.

> **Key takeaways**
>
> - Ezovion covers 50+ HMS modules (OPD, IPD, EMR, OT, pharmacy, lab, PACS, RCM, blood bank, HR) on cloud or on-premise, per its site. Pricing is quote-only.
> - Ezovion markets a speech-to-text feature it says saves an hour or more per clinical documentation. That's a voice-input claim; verify the workflow in a demo.
> - An ambient scribe is a different mechanism: it listens to the consultation itself and drafts a structured SOAP note with ICD-10 suggestions and a prescription draft.
> - Patient Square's published ladder runs ₹1,599 to ₹3,999 per doctor per month (annual, ex-GST). Hospital Copilot is demo-priced.

## What Ezovion covers

The breadth is real. Ezovion's platform, by its own product pages, spans outpatient and inpatient management, an EMR, operation theatre management, pharmacy, a laboratory information system, radiology with PACS, revenue cycle management, blood bank, nursing, inventory and assets, HR, and finance: 50-plus modules in total. Deployment is flexible for the Indian market: cloud, an on-premise option, and mobile apps its site says support offline data entry. The company states it's now part of QuantumNexis, a subsidiary of US-listed Healthcare Triangle, which matters if vendor ownership and continuity are on your diligence list.

It also leans into AI language more than most Indian HMS vendors: speech-to-text for clinical documentation, robotic process automation that its site says auto-generates documentation, and AI-driven analytics. For an emerging suite, that's an ambitious surface area. If what your hospital is buying is one vendor for everything, Ezovion has earned a look, alongside the more established names our [cloud HMS buyer's guide](../cloud-based-hospital-management-system-india/) walks through.

## A voice feature isn't automatically an ambient scribe

Here's where buyers get burned by vocabulary. "AI documentation" now appears on nearly every HMS brochure, and it can mean three very different mechanisms.

Dictation, or speech-to-text, means you compose the note with your voice. After the patient leaves, you narrate: chief complaint, history, findings, plan. The software types what you say. It genuinely saves typing time, and Ezovion's site claims its version saves an hour or more per clinical documentation. But you're still authoring every sentence. The note still costs you attention, after every single visit.

Template automation, including RPA, fills structured fields from data the system already holds. Useful for repeatable paperwork; it doesn't know what happened in the room.

Ambient documentation means the consultation itself is the input. You talk to the patient, normally. The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. In an Indian OPD, where Irving et al.'s BMJ Open review measured average consultations near two minutes, that mechanical difference is the entire game. There's no spare minute to dictate a note you already lived through. The scribe follows English, Hindi, and 20+ Indian languages, code-mixed mid-sentence the way real consults run, and returns clean clinical English every time.

To be fair to Ezovion: its public pages describe voice input and automation, and we're not going to assert what its tooling can't do. Ask the demo question precisely. Who does the talking, and to whom?

## Who does the talking: line by line

| | Speech-to-text dictation | Ambient scribe (Patient Square) |
|---|---|---|
| Your input | You narrate the note after the visit | You talk to the patient during the visit |
| When the note exists | After you've dictated it | Drafted about two minutes after the visit ends |
| What you review | Your own transcription, for errors | A structured SOAP draft, ICD-10 suggestions, prescription draft |
| Time cost per visit | Minutes of narration, every visit | Review and sign |
| Languages in a real OPD | Depends on the dictation engine | English, Hindi, 20+ Indian languages, code-mixed; English notes out |
| What it fixes | Typing speed | Authorship itself |

_Mechanism comparison based on Ezovion's published feature descriptions and Patient Square's shipped product, July 2026. Confirm specifics with each vendor._

One row matters more than the rest: what you review. Reviewing a draft someone else structured is a fundamentally lighter task than proofreading your own dictation. That's the depth half of depth-versus-breadth, and it's why we think documentation-first is the right first purchase for most clinics. If the table raises the question, book a demo and watch a live consult become a signed note.

## What does Ezovion cost?

No published number. Ezovion's site routes pricing through a demo request, scoped per facility, standard for suites but opaque for budgeting. Factor the usual suite arithmetic too: per-module licensing, implementation, training, and the annual maintenance line that follows enterprise deals.

Patient Square posts its clinic prices instead. Assist is ₹1,599 a month per doctor on annual billing (₹1,999 month-to-month), Copilot is ₹2,399 and adds the bundled AI Copilot EHR plus WhatsApp messaging, Autopilot is ₹3,999 with the AI Receptionist and AI Follow-ups on top. All ex-GST; add 18%, so Assist bills about ₹1,887 all-in. Unlimited visits and notes, no per-note metering, no setup fee, and a 7-day trial to run it on a real clinic day. Full ladder on the [pricing page](/in/pricing/). Hospital Copilot, the separate hospital product, is demo-priced. On data: audio is processed in memory and discarded once the note drafts, records belong to the practice, handling follows DPDP Act 2023 standards, SOC 2 Type II is in progress, and ABDM integration is roadmap, not live. Details sit on the [security page](/in/security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## When Ezovion is the better choice

Choose Ezovion when the mandate is one suite for the whole hospital. If you need OPD, IPD, pharmacy, lab, PACS, revenue cycle, blood bank, and HR from a single emerging cloud vendor, with an on-premise option in reserve, that's exactly the category Ezovion competes in, and a documentation platform is not a substitute for it. A hospital administrator consolidating five legacy systems into one has an Ezovion-shaped problem, not a scribe-shaped one.

Choose Patient Square when the expensive thing is the clinical record. A clinic can run Practice Copilot on Patient Square EHR or alongside an existing EHR. A hospital can use the complete Patient Square HIS/EHR or keep Ezovion through Hospital Copilot's incumbent-system path. Required operations modules decide which record system fits. For the wider field, the [Attune comparison](../attune-alternatives-india/) covers the established enterprise end, and the [clinic software scorecard](../best-clinic-management-software-india/) scores the clinic-scale options side by side.

## The one demo question that settles it

Run both demos in the same week and ask each vendor the same question: "Show me a real consultation, in Hindi and English mixed, becoming a finished note. Time it. Tell me who talked." Suites will show you dashboards first; make them show you the note. Scribes should show you nothing else.

Then put your own numbers next to each answer: what a scoped Ezovion quote totals over three years, against a published ₹1,599 a month per doctor. If breadth wins, buy breadth. If the note wins, book a demo and let a Tuesday OPD make the case.

---

## Best EHR for OB/GYN: The Prenatal Flowsheet Question
https://patientsquare.com/us/blog/best-ehr-for-obgyn/
Published 2026-08-28 · Tags: best, ob-gyn, ehr-comparison, emr-for-obgyn

ModMed EMA, eClinicalWorks, athenahealth, digiChart, CureMD, and Epic compared for OB/GYN, plus where an ambient scribe fits the prenatal documentation load.

For prenatal-heavy practices, pick a system with a real OB flowsheet: eClinicalWorks, ModMed EMA, digiChart, or CureMD all build the antepartum record natively. Hospital-employed groups usually land on Epic. If your mix is gyn-heavy and documentation time is the bigger pain, Patient Square bundles an ambient scribe and AI EHR at a published $119 per clinician monthly.

Buying an EHR for OB/GYN comes down to one question first: how much of your week is prenatal volume? If the answer is "a lot," you want a system with a native OB flowsheet, and the field narrows fast to eClinicalWorks, ModMed EMA, digiChart, CureMD, and Epic. If your practice runs gyn-heavy and the real pain is note time, Patient Square pairs an ambient scribe with a bundled AI EHR at a published $119 per clinician per month.

Both answers are on this page, with the trade-offs stated plainly. If the second one sounds like your practice, book a demo and watch it draft a note on a real visit type.

> **Key takeaways**
>
> - A routine pregnancy generates roughly 13 prenatal visits, and a flowsheet-native EHR charts them as one running record instead of 13 disconnected notes.
> - eClinicalWorks builds an OB Flowsheet with timelines and benchmarks tracking weight, blood pressure, fetal heart rate, and dilation across the pregnancy.
> - ACOG has cited estimates that 40 to 75 percent of ob-gyns experience burnout, with EHR expectations among the named drivers.
> - Nearly every OB-capable EHR is quote-priced; athenahealth charges a percentage of collections, estimated by third parties at 4 to 8 percent.
> - Patient Square has no OB flowsheet. It has a built-in ambient scribe, a bundled AI EHR, and a published price: $119/mo per clinician, annual.

## The flowsheet is what makes an OB/GYN EHR different

Most specialties chart visit by visit. Obstetrics charts a nine-month arc. The antepartum record, the thing OB practices ran on paper ACOG forms for decades, tracks one pregnancy across every visit: weight, blood pressure, fundal height, fetal heart rate, urine dips, labs, gestational age ticking forward each row. When a covering physician opens the chart at 2am before a delivery, that single-screen history is what they read.

So the first cut in any OB/GYN EHR decision is blunt: does the system build that record natively, or are you assembling it from loose notes? A generic EHR can store 13 prenatal visits. A flowsheet-native one connects them. That difference decides your shortlist before price ever enters the room.

Then there's the second problem, the one the flowsheet doesn't solve. Every one of those visits still needs a narrative note, and ob-gyn burnout runs high. ACOG has cited estimates of 40 to 75 percent of ob-gyns experiencing burnout, with electronic medical record expectations named among the pressures. So the decision hides two separate purchases: the record structure, and the writing.

## Six options for OB/GYN, compared

| EHR | OB flowsheet | Built for OB/GYN? | Documentation help | Pricing |
|---|---|---|---|---|
| eClinicalWorks | Yes, native OB Flowsheet | OB module in a general platform | healow Mom patient app | Quote-led |
| ModMed EMA | Yes, per EHR Source's guide | Yes, specialty suite | Suite AI tooling | Quote-only |
| athenahealth | Prenatal workflows | General platform, strong RCM | Abridge partnership (2025) | ~4–8% of collections, estimated |
| digiChart | Yes, ACOG-aligned | Yes, OB/GYN-only | AI-forward repositioning | Demo-led |
| CureMD | Yes, ACOG-aligned | General platform, OB module | Standard tooling | Positioned as budget option |
| **Patient Square** | **No** | **No, specialty-aware templates** | **Ambient scribe, built in** | **Published: $119/mo annual** |

Rival characterizations follow EHR Source's 2026 OB-GYN buyer guide and each vendor's own site; the athenahealth percentage is a third-party estimate, not a published rate. The pattern to notice: five of six rows say some version of "call sales." One row is a number.

## The flowsheet-native systems, grouped honestly

### eClinicalWorks and athenahealth: the big-platform route

eClinicalWorks makes the strongest first-party OB case of the general platforms. Its OB Flowsheet carries timelines and benchmarks for the pregnancy, per visit: weight and blood pressure, fetal heart rate and movements, dilation and effacement, with a history tab for gynecological, surgical, and family history. The healow Mom app gives patients appointment tracking and secure messaging. For a mid-size OB group that wants one platform for clinical plus billing, it's the default candidate to beat.

athenahealth's OB strength, per EHR Source, is prenatal workflow plus one of the strongest revenue-cycle engines in the market, and its pricing model matches that framing: a percentage of collections rather than a seat fee, estimated by third parties at 4 to 8 percent. On documentation, it announced an ambient-AI partnership with Abridge in early 2025. If billing complexity is your practice's biggest operational risk, athena's model is built for exactly that; you'll pay for it as a slice of revenue.

### digiChart and CureMD: the OB/GYN-only and budget lanes

digiChart is the single-specialty pick, an OB/GYN-only system now marketing itself as an AI-powered platform for OB practices, with ACOG-aligned prenatal documentation as the core. EHR Source slots it for smaller practices, under 10 providers. CureMD takes the budget lane with ACOG-aligned prenatal flowsheets and an antepartum record module. Both are demo-led on pricing.

### ModMed EMA and Epic: the suite and the system

ModMed EMA's OB-GYN edition took first place in the 2024 Black Book survey, per EHR Source's guide, and brings the specialty-suite depth ModMed is known for. Epic, with its L&D integration, is what you'll use if a hospital system employs you; it's rarely a practice-level purchase decision so much as an ecosystem you join.

## What the prenatal documentation load actually adds up to

Here's arithmetic worth doing before you buy anything. A routine pregnancy runs about 13 prenatal visits plus a postpartum check, call it 14 documented encounters. Type each note at 6 to 10 minutes and one uncomplicated pregnancy costs you 84 to 140 minutes of writing. Review-and-sign an ambient draft at 2 to 3 minutes per visit instead and the same pregnancy costs 28 to 42 minutes.

That's roughly an hour to an hour and a half of documentation returned per pregnancy, per patient. A practice managing 60 active OB patients is carrying that math 60 times over, on a rolling basis, forever. These are conservative estimates, not a trial result; your notes may run shorter or longer. The point is that the flowsheet organizes the record, but it never wrote a note for you. The writing is a separate cost, and it's the one that follows you home.

## Where Patient Square fits an OB/GYN practice

No flowsheet. No antepartum record module. If your week is 30 prenatal visits, pick from the section above, and we mean that.

The fit is the practice where gyn volume dominates, annuals, colposcopy follow-ups, contraception visits, menopause care, with OB as a minority of the schedule, and where the charting burden is the thing breaking the day. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Dictate "fundal height 30 centimeters, fetal heart rate 150 by Doppler" and the draft carries it in your words; the [OB/GYN scribe guide](../ai-scribe-for-ob-gyn/) covers the two-patients-one-room narration problem in detail, including consent in sensitive visits.

The Copilot plan bundles the scribe with the AI Copilot EHR at $119 per clinician per month, annual billing, unlimited visits and notes. Every note is available as an EHR-ready export (PDF · HL7 · FHIR), so a practice keeping a flowsheet system for OB can still move notes where they need to go. Full plan detail is on the [pricing page](/us/pricing/), and the audio-handling posture, processed in memory, never stored, is on the [security page](/us/security/).

## When the flowsheet-native EHR is the better fit

If prenatal volume is your practice's center of gravity, a flowsheet-native system wins, full stop. eClinicalWorks for a group that wants OB depth inside a broad platform. digiChart if you want a vendor that thinks about nothing but OB/GYN. athenahealth if revenue cycle is the bigger risk than documentation. Epic if the hospital already decided for you. We think buying a scribe-first bundle for a 70-percent-OB practice would be buying the wrong tool, and we'd rather say so here than in your first support ticket.

The reverse holds too. A gyn-heavy practice buying a full OB suite for four deliveries a year is paying specialty-platform prices for a flowsheet it rarely opens.

## How to decide in two weeks

Week one: demo the flowsheet systems on a real chart review. Have them show you a 28-week visit charted end to end, then ask what the covering doc sees at 2am. Get total pricing in writing, base, implementation, and the collections percentage if there is one.

Week two: request an assisted 7-day trial after workspace setup and run the documentation half on your own schedule. Try it through a full clinic day, gyn visits included, and count minutes from room exit to signed note. Our [family practice EHR roundup](../best-ehr-for-family-practice/) covers the adjacent generalist field if your practice straddles both. Then book a demo if you want the note output walked through on your own visit types.

Chart structure or charting time. Figure out which one is costing you more, and buy against that.

---

## AI Scribe for Dentists: Procedure Notes, Not Data Entry
https://patientsquare.com/us/blog/ai-scribe-for-dentists/
Published 2026-08-27 · Tags: ai-scribe, dental, documentation, buyers-guide

What an ambient AI scribe covers chairside (procedure notes, perio narratives, consent talks) and what stays in Dentrix, Eaglesoft, or Open Dental.

Alongside them, yes. The AI Medical Scribe by Patient Square drafts the narrative note and hands it off via EHR-ready export in PDF, HL7, and FHIR formats; for most dental practice management systems that means pasting or attaching the note into the chart. It does not write into Dentrix or replace any PM function.

An AI scribe for dentists listens chairside, with consent, and drafts the narrative half of dental documentation: procedure notes, exam findings, perio discussions, consent conversations, post-op instructions. You review, edit, and paste or attach the note into Dentrix, Eaglesoft, or Open Dental. It's a documentation layer that sits alongside your practice management system, not a replacement for it.

That scope line matters more in dentistry than anywhere else we write about, because dental software already does a lot. So let's be precise about the division of labor before any pitch. If you'd rather watch it run on a crown-prep conversation than read about it, book a short demo and bring your messiest procedure.

> **Key takeaways**
>
> - The scribe layer covers narrative documentation: procedure notes, perio and treatment-plan discussions, consent conversations, post-op instructions. A structured draft lands about 2 minutes after the conversation ends.
> - Your PM keeps its jobs: the odontogram, the numeric perio grid, imaging, CDT billing, scheduling and recall. Nothing here replaces Dentrix, Eaglesoft, or Open Dental.
> - Voice perio charting (calling pocket depths into the grid) is a different product category; dental-native tools like Bola AI and Denti.AI own that job, and we'll say so plainly.
> - Practice Copilot starts at $79 per dentist per month on annual billing, unlimited notes, with a 7-day trial to test it against a real hygiene-day schedule.

## What the scribe layer covers in an operatory

Take an ordinary Thursday: eight hygiene checks, three crown preps, one emergency pulpitis workup, and a consult where a patient finally says yes to the implant after declining it twice. Every one of those produced a conversation. Almost none of that conversation makes the chart, because between patients you have four minutes, and the chart gets the abbreviated version: "Reviewed findings, pt consents."

Ambient capture flips the economics of that. The conversation itself becomes the draft. The pulpitis workup comes back structured: what the patient reported, what you found, what you diagnosed, what you planned. The implant consult comes back with the risks, benefits, and alternatives you actually said out loud, in order, ready to trim. The hygiene checks come back as short narratives of what you told the patient about bleeding points and the recall interval you agreed on. You review each one, fix what's off, and move it into the chart. For a fuller primer on how the capture-transcribe-structure pipeline works, our explainer on [what an AI medical scribe is](../what-is-an-ai-medical-scribe/) covers the mechanics.

Here's the sentence that describes the product doing this. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In a dental context, read that honestly: the SOAP structure fits exams and emergencies cleanly, operative notes need your procedural format, the ICD-10 suggestions earn their keep where dentistry crosses into medical billing, and the prescription draft covers the amoxicillin and ibuprofen conversations you have daily. All of it stays draft until you sign.

## What stays in Dentrix, Eaglesoft, or Open Dental

This table is the whole positioning, so we'll put it early.

| Job | Who owns it |
| --- | --- |
| Procedure note narrative, exam findings, consent discussion | Scribe layer drafts it; you edit and sign |
| Post-op instructions given verbally | Scribe layer captures them into the draft |
| Perio discussion narrative (staging, plan, patient response) | Scribe layer |
| Numeric perio grid (pocket depths, recession, BOP charting) | Your PM, entered by hand or a voice-perio tool |
| Odontogram and tooth charting | Your PM |
| Imaging, radiographs, and anything diagnostic on a screen | Your PM and imaging stack |
| CDT procedure codes, fee schedules, claims | Your PM and billing workflow |
| Scheduling, recall, patient communication | Your PM |

Two honest notes on that table. First, the handoff between layers is an export, not an integration: every plan includes EHR-ready export (PDF · HL7 · FHIR), and in dental practice that realistically means paste or PDF-attach into the chart, since dental PMs take documents more readily than HL7 feeds. We don't write into Dentrix, and any vendor's "integrates with your PM" claim deserves one clarifying sentence before you believe it. Our piece on [using a scribe with any EHR via export](../ai-scribe-any-ehr-export/) explains that posture and why we think it beats waiting for a certified interface. Second, ICD-10 is not CDT. Your procedure coding lives where it always has.

## Voice perio is a different product, and the dental-native tools are better at it

If what you want is to call out "three, two, three... four, three, four" and have the numbers land in the perio chart, buy a dental-native voice tool. Bola AI, which maintains a Dentrix partnership page, and Denti.AI, whose homepage leads with voice perio alongside its dental scribe, built their products around exactly that structured data-entry job, hygienist workflows included. An ambient medical scribe drafts prose from conversation; it does not populate a numeric grid, and pretending otherwise would earn us an annoyed hygienist by Tuesday.

So the honest verdict for this category: when perio data entry and deep PM integration are the problem, a dental-native platform is the better fit, full stop. Where the general ambient scribe wins is the other half of the day, the conversations. Consent discussions before an extraction. The treatment options a patient declined, and why. The emergency exam with a medical history tangled into it. Post-op instructions you delivered while pulling your gloves off. Dental-native tools are built around chart transactions; an ambient scribe is built around the room's dialogue. Some practices will genuinely want one of each, and that's a defensible stack, not a failure to choose.

We think the consent conversation alone justifies testing the ambient side. It's the most defensibility-dense speech in your practice and the least documented, precisely because it happens at the human-est moment of the visit, when nobody's typing.

## What it costs, and the trust questions dental offices should ask

Practice Copilot starts at $79 per dentist per month on the annual Assist plan ($99 month-to-month), with unlimited visits and notes and no per-note metering. The Copilot tier at $119 monthly annual adds a bundled AI EHR, though in a dental office your PM stays the system of record, so most dental buyers start and stay at Assist. Full tier detail is on the [pricing page](/us/pricing/).

The trust floor is the same as any practice handling PHI: a signed BAA, which we offer every customer, HIPAA-compliant safeguards, a SOC 2 Type II audit in progress, and encryption in transit and at rest. Visit audio is processed in memory and discarded once the note is drafted; there's no audio archive sitting anywhere, which is the first question a records request or a nervous patient will surface. The rest of the posture is on the [security page](/us/security/), and our guide to [HIPAA, BAAs, and recording consent](../ai-scribe-hipaa-baa-consent/) covers how to script the chairside consent ask so it takes five seconds and nobody flinches.

## Try it against one real clinic day

Pick your fullest hygiene-and-operative day next week. Run the morning on your normal workflow and the afternoon with ambient capture on, consent obtained, and count two things: how many conversations made it into the chart in full, and what time you left. The 7-day free trial exists for exactly this experiment, and if you want help setting the note formats to your operative style first, book a demo and we'll configure it around your procedure mix before you start.

---

## Attune Alternatives India: Lab, Hospital, or Clinic? (2026)
https://patientsquare.com/in/blog/attune-alternatives-india/
Published 2026-08-27 · Updated 2026-08-28 · Tags: alternatives, his, hospital-software, comparison

Attune is cloud HIS and LIMS for hospitals and lab chains, quote-priced. The right alternative depends on your door: lab, hospital, or clinic. An honest split.

Cloud-based enterprise healthcare IT, with diagnostics as the standout. Attune's SaaS platform covers hospital information systems and laboratory information systems, and its LIS runs serious scale: Attune's own case material describes a lab chain operating 105 labs and 700 collection centres on it. For multi-site labs and mid-to-large hospitals, that depth is the draw.

"Attune alternatives" is really three different searches wearing one query. Attune Technologies sells cloud-based hospital information systems and one of India's more proven laboratory information systems, quote-priced, built for scale. So the right alternative depends on which door you're standing at: diagnostic lab, hospital, or clinic. Labs should shortlist LIMS vendors; we're not one. Hospitals and clinics with a documentation problem are who Patient Square is built for, and you can book a demo to see it against your own workflow.

> **Key takeaways**
>
> - Attune is a Chennai-born, cloud-first healthcare platform. Its LIS credentials are real: Attune's case material describes a lab chain running 105 labs and 700 collection centres on it.
> - Pricing is quote-only. Expect a scoping cycle, not a rate card.
> - Patient Square splits by segment: Practice Copilot for clinics from ₹1,599/month per doctor + 18% GST, Hospital Copilot for hospitals, demo-priced.
> - If you're a lab, compare LIMS vendors. If your doctors can't finish notes, that's our lane.

## Which of the three buyers are you?

Match your row before reading anything else. Most "alternatives" pages skip this step and end up comparing a sample-routing platform against a scribe, which helps nobody.

| You are | What Attune offers you | What Patient Square offers you | Honest call |
|---|---|---|---|
| A diagnostic lab or collection-centre chain | Attune LIS: multi-site sample tracking, billing, reporting at chain scale | Nothing in this lane. We don't sell a LIMS | Shortlist LIMS vendors including Attune. Skip us |
| A mid-to-large hospital | Cloud HIS: departments, billing, pharmacy, lab, multi-location visibility | Hospital Copilot: complete Patient Square HIS/EHR or alongside an existing HIS/EHR, demo-priced | Compare required modules, then choose the record-system path |
| A clinic or small practice | A clinic edition of an enterprise-grade platform | Practice Copilot: ambient scribe + bundled AI EHR, published per-doctor pricing | Depends on whether operations or documentation is what hurts |

If the first row is you, this is your exit. The [HIS software roundup](../best-his-software-india/) covers the enterprise field more broadly. Everyone else, keep going.

## What Attune is genuinely built for

Attune earned its reputation the credible way. Founded in Chennai in 2009, it raised institutional money when that was rare for Indian health-tech: Norwest Venture Partners led its Series A, and in October 2015 Qualcomm Ventures and Norwest put in another $10 million, Qualcomm's first cheque from its India fund, per Business Standard. Coverage from that raise put the platform at 200-plus hospitals, labs, and clinics with over 9 million patient records across 15 countries.

The product thesis was cloud-first before most Indian hospital software was: SaaS delivery, multi-location operations under one view, and integration across pharmacy, diagnostics, imaging, and billing. And the LIS is the flagship in practice. Running 105 labs and 700 collection centres for a single chain, processing tens of thousands of samples a day by Attune's own account, is not a claim most Indian LIMS products can make.

None of what follows argues that machinery is weak. The question is narrower: is that the machine your problem needs?

## What does Attune cost?

You'll find out after a sales conversation. Attune publishes no price list; HIS and LIMS pricing is scoped to facility size, modules, and site count. For enterprise software, that's fair, a 20-site lab network genuinely can't be priced off a card. But budget-wise you're committing to a discovery cycle before you see a number, and the number will be negotiated, not posted.

Patient Square takes the opposite posture for clinics: the price is public. Assist is ₹1,599 a month per doctor on annual billing, Copilot is ₹2,399 with the bundled AI Copilot EHR and WhatsApp messaging, Autopilot is ₹3,999, all ex-GST with 18% added on the invoice, so Assist lands around ₹1,887 all-in. The full ladder sits on the [pricing page](/in/pricing/). Hospital Copilot is demo-priced, because hospital scope honestly does need scoping. Where the quote model came from, and what it hides, gets a fuller treatment in our [HMS cost breakdown](../hms-software-cost-breakdown-india/).

## The clinic door: platform breadth vs documentation depth

Here's the thing an enterprise platform, however good, doesn't change: the two-minute consult. Irving et al.'s 67-country BMJ Open review put India's average primary-care consultation at about two minutes. Registration software doesn't lengthen it. A better dashboard doesn't write the note. At 5pm the OPD register is full and the records are thin, and that's the gap a clinic actually feels daily.

That gap is the product. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It follows English, Hindi, and 20+ Indian languages, code-mixed the way real consults sound, and always returns the note in clean clinical English. Every plan carries unlimited visits and notes and EHR-ready export (PDF · HL7 · FHIR). At the Copilot tier, the bundled AI EHR makes it the record system too, not just the note-writer.

To be equally plain about limits: ICD-10 comes as suggestions, the prescription is a draft you sign, ABDM integration is on our roadmap and not live, and SOC 2 Type II is in progress, not certified. Encryption, access controls, and data-ownership specifics are on the [security page](/in/security/).

## The hospital and lab doors

Labs first, because it's the shortest answer we'll ever write: we don't make a LIMS. A chain evaluating Attune LIS should run a LIMS bake-off. Full stop.

Hospitals are more interesting. Hospital Copilot supports two deployment paths: the complete Patient Square HIS/EHR can be the hospital's record system, or Patient Square can work alongside an incumbent HIS/EHR such as Attune. Attune remains the stronger fit when its laboratory routing, multi-location reporting, or other enterprise modules are requirements; the existing-system path keeps those workflows in place while adding Patient Square's AI documentation. The choice is made during a demo and discovery conversation, not assumed from a module-count table. The [Suvarna comparison](../suvarna-alternatives-india/) walks the same decision against another long-running enterprise HIS.

## When Attune is the better choice

Pick Attune, or something in its class, when the problem is operational scale. A lab network that lives or dies on sample routing and turnaround. A hospital group that needs one cloud view across sites, integrated billing, pharmacy, and diagnostics. A management team that wants enterprise reporting more than it wants faster notes. That's what Attune was funded and built to do, and a documentation tool is not a substitute for it.

Pick Patient Square when the expensive minutes are clinical. Doctors typing after hours. Notes compressed to a line. Records that wouldn't survive scrutiny. For a clinic, Practice Copilot can use Patient Square EHR from the Copilot tier or work alongside an existing EHR. For a hospital, Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an incumbent HIS/EHR such as Attune.

## How to decide without a committee

1. Name your door: lab, hospital, or clinic. The table above ends the search for labs.
2. Write down the one metric that's actually bleeding: turnaround time, billing leakage, or unfinished notes. Buy against that metric only.
3. Get both numbers on the table. A scoped Attune quote, and the published per-doctor ladder on our [pricing page](/in/pricing/).
4. Trial the documentation claim on real consults, in the languages your OPD actually speaks. The 7-day trial exists so you can run it on a live clinic day.

If operations are the fire, scope Attune seriously. If it's the notes, book a short demo and watch one of your own consults come back as a structured, signable record.

---

## Best EHR for Dermatology in 2026: The Real Contenders
https://patientsquare.com/us/blog/best-ehr-for-dermatology/
Published 2026-08-27 · Tags: best, dermatology, ehr-comparison, emr-for-dermatology

ModMed EMA, eZDERM, Nextech, DrChrono, and a published-price scribe-plus-EHR bundle compared for dermatology. Honest verdicts, no quote-form runaround.

For derm-specific clinical depth, ModMed EMA is the benchmark: Black Book has ranked it first in dermatology for 13 straight years. eZDERM competes hard on medical derm with its 3D body map. If documentation time and price transparency matter more than specialty tooling, Patient Square bundles an ambient scribe and AI EHR at a published $119 per clinician monthly.

The honest answer splits in two. If your dermatology practice needs derm-built clinical tooling, body mapping, deep procedure workflows, cosmetic and medical under one roof, the real contenders are ModMed EMA and eZDERM, with Nextech in the mix for aesthetics-heavy practices. If your actual problem is documentation time and quote-only pricing, Patient Square bundles an ambient AI scribe and an AI EHR at a published $119 per clinician per month.

Those are different problems, and most "best derm EHR" lists blur them. This page keeps them separate, names where each vendor genuinely wins, and tells you plainly where we don't. If you already know documentation is your bottleneck, book a demo and skip to the table.

> **Key takeaways**
>
> - ModMed EMA has been ranked first in dermatology by Black Book Research for 13 consecutive years, including the 2026 survey. For derm-specific depth, it's the benchmark.
> - The derm-built platforms are quote-priced. Third-party estimates for ModMed EMA run anywhere from $200 to $900+ per provider per month depending on which tracker you read.
> - eZDERM is dermatology-only and documents on an anatomical 3D body map tied to location-specific ICD-10 and CPT codes, per its own site.
> - A 2020 Journal of the American Academy of Dermatology study put dermatologists' documentation share at roughly 36% of work time.
> - Patient Square has no derm-specific tooling. It has a built-in ambient scribe, a bundled AI EHR, and a price on a public page: $119/mo per clinician, annual.

## The two problems a derm EHR gets bought to solve

Problem one is clinical: dermatology documentation has structure most specialties don't. Lesions need a location precise enough to find again in six months. Biopsies need tracking from shave to path report. A practice running both medical and cosmetic lines needs the record system to handle each without pretending they're the same business. Derm-built platforms exist because generic EHRs handle this badly.

Problem two is throughput. A general derm schedule runs 30-plus patients a day, and the notes stack up. The 2020 JAAD analysis found dermatologists spending about 36% of their work time on documentation. That's not a template problem. That's a "who writes the note" problem, and it's the one an ambient scribe attacks.

Figure out which problem is actually yours before you shortlist anything. The vendors below split cleanly along that line.

## How the five options compare

| EHR | Built for derm? | Known for | Pricing |
|---|---|---|---|
| ModMed EMA | Yes | Black Book #1 in dermatology, 13 straight years | Quote-only; third-party estimates $200–$900+ |
| eZDERM | Yes, derm-only | 3D body map on location-specific ICD-10/CPT | Quote-only; third-party estimate $250–$500 |
| Nextech | Yes | Aesthetic and cosmetic derm focus | Custom, typically enterprise-tier |
| DrChrono | No, multi-specialty | Small-practice option with ambient AI | Third-party estimate $199–$499 |
| **Patient Square** | **No, specialty-aware templates** | **Built-in ambient scribe + bundled AI EHR** | **Published: $119/mo annual** |

All rival figures are third-party estimates from Edvak's 2026 dermatology buyer guide and Software Finder, not vendor quotes. The spread on ModMed alone ($200 versus $900+) tells you how much a "typical" number hides. Only one row on this table has a price you can read without a sales call, and yes, that's our row. We think that fact belongs in the comparison itself.

## The derm-built platforms, one by one

### ModMed EMA

EMA is the default answer in dermatology, and the record backs it: first place in Black Book Research's dermatology EHR rankings for 13 consecutive years, part of a 2026 sweep across all 11 of ModMed's specialty EHRs. It was built as a single-specialty system, and the depth shows in derm-specific workflows that generic platforms bolt on later, if ever. The trade-offs are the ones that come with depth: quote-based pricing, implementation costs that third parties peg at $2,000 to $10,000, and real lock-in once your staff is trained into it. Our [ModMed alternatives breakdown](../modmed-alternatives/) covers the leaving-versus-staying math in detail.

### eZDERM

eZDERM's pitch is purity: "built only for dermatologists by a practicing dermatologist," in its own words. The signature feature is the 3D body map, an anatomical model you document on directly, with the site claiming it's built on location-specific ICD-10 and CPT codes. For medical and surgical derm where lesion location drives everything, that's a genuinely different way to chart. Pricing isn't published; Edvak's estimate lands at $250 to $500 per provider per month.

### Nextech

Nextech plays strongest where dermatology shades into aesthetics. Edvak's 2026 dermatology buyer guide frames it as the pick for cosmetic-forward and high-volume aesthetic practices, with custom, enterprise-tier pricing. If your revenue mix leans cosmetic, it belongs on your shortlist. If you run mostly medical derm, the platforms above fit tighter.

### DrChrono

DrChrono isn't derm-built. It's a multi-specialty EHR that shows up in derm roundups as the small-practice option, with an ambient AI assistant and third-party pricing estimates of $199 to $499 per provider. It's the middle path: less specialty depth than EMA or eZDERM, more clinical breadth than a documentation-first bundle.

## Where Patient Square fits a dermatology practice

Straight up: we don't have a 3D body map, a biopsy log module, or cosmetic inventory tooling. If those are hard requirements, pick a derm-built platform and don't look back.

What Patient Square does have is the other half of the problem. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Say "8 millimeter hyperpigmented plaque, left medial calf, irregular border" during the exam and that's what the note carries, in your words. The Copilot plan bundles that scribe with the AI Copilot EHR at $119 per clinician per month on annual billing, unlimited visits and notes, no per-note metering. Specialty-aware templates ship ready out of the box, and every note is available as an EHR-ready export (PDF · HL7 · FHIR).

How the scribe handles lesion descriptions and spoken procedure narration is its own topic; the [dermatology scribe guide](../ai-scribe-for-dermatology/) walks through it finding by finding. Security posture, BAAs included for every customer, is on the [security page](/us/security/).

So the fit is a specific one: derm practices whose charting burden outweighs their need for specialty modules, and practices that want a number on a page instead of a quote form. That's a real segment. It's not every segment.

## When ModMed EMA or eZDERM is the better fit

Choose ModMed EMA if your practice lives inside medical and surgical dermatology at scale and you'll actually use the deep workflows. Thirteen straight years at the top of the specialty's own survey is derm groups re-choosing it with their own money, year after year. The premium and the lock-in are the price of that depth, and for a mid-size or large derm group, usually a fair one.

Choose eZDERM if precise anatomical documentation is the center of your clinical day, high-volume skin checks, lots of biopsies, lesions you track across years. A 3D body map beats a text field for that job.

Choose Nextech if cosmetic revenue drives the practice.

Choose Patient Square if the notes are the pain, you want the scribe and the record system in one subscription, and you'd rather spend $119 than an unknown number. That's the honest split. For the broader field beyond dermatology, our [EHRs with a scribe built in](../best-ehr-with-ai-scribe-built-in/) roundup covers the bundled category.

## A one-week way to decide

Book demos with the derm-built vendors and push past the script: bring your three messiest real cases, a complex skin check, a multi-procedure morning, a cosmetic consult, and watch each system chart them end to end. Ask every vendor for the full invoice in writing, base plus implementation plus add-ons, because the sticker is never the total.

Then run the documentation half on your own patients. Request an assisted 7-day trial after workspace setup. Run it on a real Monday clinic, count minutes from room exit to signed note, and compare that number against whatever you do today. Pricing is on the [pricing page](/us/pricing/), and a short demo will show the note output on a dermatology visit before you commit the week.

Two problems, five vendors, one decision. Buy for the problem you actually have.

---

## SoftClinic Alternatives in India: Cloud + AI in 2026
https://patientsquare.com/in/blog/softclinic-alternatives-india/
Published 2026-08-27 · Tags: softclinic, alternatives, hms, clinic-software, india

SoftClinic GenX packs EHR, HIMS, lab, and pharmacy into one quote-priced suite. Here's how an AI-first platform with published pricing compares for 2026.

SoftClinic GenX is the current cloud product from JVS, an Ahmedabad-based healthcare-IT company with roots in the desktop-EMR era. Their site describes an end-to-end platform spanning EHR, hospital information management, laboratory, pharmacy, and back-office modules, and claims more than 25,000 registered physicians across 45 countries.

SoftClinic has been selling practice software since before most of its competitors existed; the JVS lineage runs back to the desktop-EMR era, and the current cloud product, SoftClinic GenX, claims 25,000+ registered physicians across 45 countries. Doctors shopping for an alternative usually want one of two things it doesn't lead with: a price you can read without a demo call, or documentation that writes itself instead of another suite to type into. Patient Square publishes both answers, an ambient AI scribe from ₹1,599 per clinician a month on annual billing, plus 18% GST, and a bundled AI EHR at the ₹2,399 tier. Book a demo to see a consult become a signed note.

> **Key takeaways**
>
> - SoftClinic GenX spans EHR, HIMS, lab, pharmacy, and back-office modules; the site claims 25,000+ physicians, 5.3M+ patients, and 45 countries.
> - Pricing isn't published. Budget the quote call, and ask about per-module costs, implementation, and the annual maintenance renewal in writing.
> - Their genx site pitches a zero-cost e-prescription app; the full suite is the paid product. Two different offers, one brand.
> - A 2026-wide suite still leaves the note typed, and India's ~2-minute consults are where typing loses.
> - Patient Square publishes ₹1,599 / ₹2,399 / ₹3,999 annual tiers per clinician, ex-GST. Hospitals get Hospital Copilot, demo-priced.

## What SoftClinic is in 2026 (not just desktop anymore)

Be fair to the incumbent first. Writing SoftClinic off as legacy desktop software would be out of date: SoftClinic GenX is cloud-based, carries portals and apps, and their site describes an end-to-end platform covering EHR, hospital information management, laboratory, pharmacy management, and supporting modules like HR, inventory, and accounting. Specialty pages run from cardiology to Ayurveda. The installed-base claims are big round numbers from their own homepage, 25,000+ registered physicians, 5.3 million+ registered patients, operations in 45 countries, and while we can't audit them, longevity of that sort is evidence of a product that does what its buyers needed.

Two details from the wider footprint are worth a buyer's attention. Third-party listings still describe a desktop, in-house installation option alongside cloud, a genuine plus if your connectivity or your data-residency preference points on-premise; our [cloud vs on-premise decision guide](../cloud-emr-vs-on-premise-india/) walks that fork under the DPDP Act. And their separate genx site pitches a "Zero Cost ePrescription Software" with an AI-powered digital prescription app, which is a different offer from the paid suite. Free entry products are fine; just get in writing where free ends and the quote begins.

## The quote call vs the pricing page

Here's the structural difference before any feature is compared. SoftClinic's price, as of this writing, is not published; the site offers free trials and a demo path, and the number arrives in a conversation. Patient Square's price is a table on a public page. Neither approach is immoral, but they produce different buying experiences, and we think a clinic owner deserves the number before the pitch.

If you take the SoftClinic call, and for a hospital-grade requirement you probably should, walk in with a checklist and leave with every line in writing:

1. The licence or subscription itself, per doctor or per facility.
2. Per-module pricing: which of lab, pharmacy, inventory, and accounting are included and which bill separately.
3. Implementation, data migration, and training, in rupees, not "included".
4. The annual maintenance or support renewal, and what it rises to in year two.
5. Upgrade costs when the next version lands, especially if you're quoted the desktop deployment.

None of those questions is hostile. They're the five places a quote-priced suite's total cost hides. A vendor with good answers will give them quickly.

## A suite this wide still can't write the note

The width is the pitch: one vendor, every module. But walk it into a consult room. A Nashik nursing home runs the whole operation on one system, registration through pharmacy, and at 9pm the resident doctor is still typing the day's notes into the EHR module, because no module in any suite authors the clinical narrative. Indian consultations average about two minutes, per a 67-country BMJ Open review. Published estimates put medical-negligence matters reaching Indian courts and consumer forums in the tens of thousands a year, and the defence that tends to hold is a complete contemporaneous note. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. The module count doesn't touch any of that. The note is either written or it isn't.

That's the actual fork in this comparison. SoftClinic's answer to documentation is a place to put it. An ambient platform's answer is to produce it.

## SoftClinic vs Patient Square: different jobs, one table

| | SoftClinic GenX | Patient Square |
|---|---|---|
| Built as | End-to-end EHR / HIMS suite, decades of lineage | AI documentation platform; Copilot tiers with bundled EHR |
| Deployment | Cloud; desktop in-house option per third-party listings | Cloud, with offline encrypted capture for low-signal clinics |
| The clinical note | Typed into the EMR module | Drafted by the ambient scribe; you review and sign |
| Lab, pharmacy, accounting | Included in the suite | Not offered, and we won't pretend |
| Hospital fit | Hospital-grade by design | Hospital Copilot: complete Patient Square HIS/EHR or alongside an existing HIS/EHR; demo-priced |
| Pricing | Not published; quote after demo | Published: ₹1,599 / ₹2,399 / ₹3,999 per clinician, annual, ex-GST |
| Trial | Free trials offered | 7-day trial |

If the note row is why you're reading, book a demo and test the scribe against a real OPD morning before you sit through anyone's quote call.

## When SoftClinic is the better choice

Choose SoftClinic when the requirement is genuinely the whole hospital under one contract: a nursing home or small hospital that needs EHR, lab, pharmacy, inventory, and accounting from a single vendor, values a desktop or on-premise option, or operates across borders where a 45-country footprint means the vendor has seen your problem before. A two-decade install base is not a feature list, but it is reassurance, and for infrastructure-grade purchases reassurance is worth money. If that's your buy, take the demo call and use the five-question checklist above.

If you're hospital-scale and want the AI-first route, Hospital Copilot offers two deployment paths: use the complete Patient Square HIS/EHR as the record system, or keep SoftClinic or another incumbent HIS/EHR and run Patient Square alongside it. The product is priced by demo, not a public card, because module requirements and migration scope must be reviewed. Clinics and solo practitioners use Practice Copilot and can make the same record-system choice at practice scale.

## The published-price, AI-first alternative

The AI Medical Scribe by Patient Square is one module inside Practice Copilot, our AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It listens in English, Hindi, and 20+ Indian languages, code-mixed the way OPD conversations actually run, and returns clean clinical English. Audio is processed in memory and discarded once the note drafts. Prescriptions stay drafts; ICD-10 stays suggestions. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The plan ladder is public and short. Assist at ₹1,599 a month per clinician on annual billing (₹1,999 monthly). Copilot at ₹2,399, adding the bundled AI Copilot EHR and WhatsApp messaging; with 18% GST that's about ₹2,831 a month. Autopilot at ₹3,999, adding the AI Receptionist and AI Follow-ups. Unlimited visits and notes on every plan, no per-note metering, no setup fee, and EHR-ready export (PDF · HL7 · FHIR) so your records leave with you if you ever do. Data handled to DPDP Act 2023 standards; SOC 2 Type II audit in progress; ABDM integration on the roadmap, not live, stated plainly. Numbers on the [India pricing page](/in/pricing/), security posture on the [security page](/in/security/).

For a second opinion on how AI-first platforms stack against another long-serving Indian suite, the [Suvarna comparison](../suvarna-alternatives-india/) runs the same honest split for hospital HIS buyers.

The decision reduces to what you're actually buying this year. Whole-hospital infrastructure: SoftClinic has earned the shortlist, go extract a written quote. The end of 9pm typing: that's not a module, and no suite sells it. Book a demo and let the scribe write the first note.

---

## MyOPD Alternatives: What ₹1,599 a Month Adds (2026)
https://patientsquare.com/in/blog/myopd-alternatives-india/
Published 2026-08-26 · Tags: alternatives, clinic-software, opd, pricing

MyOPD is genuinely cheap at ₹18,700 one-time. When that's enough for an Indian clinic, when it isn't, and what ₹1,599/month per doctor actually buys.

MyOPD publishes its prices. As of July 2026, the Clinic version is ₹18,700 one-time (GST included) or ₹8,000 a year on subscription, and the Polyclinic version is ₹24,000 one-time. A free version exists for a limited number of patients. From year two, an annual maintenance charge covers updates, cloud backup, and app access.

MyOPD is one of the cheapest legitimate ways to computerise an Indian clinic: appointments, billing, and a printed prescription for a one-time ₹18,700, GST included. If that covers your day, keep it. The case for paying ₹1,599 a month per doctor instead is a different problem entirely: the clinical note nobody has time to type. That's the real subject of this comparison, and you can book a demo to see the difference on one of your own consults.

> **Key takeaways**
>
> - MyOPD publishes real prices: ₹18,700 one-time for the Clinic version (GST included) or ₹8,000/year on subscription, as of July 2026. That's hard to beat on cost.
> - MyOPD digitises the front desk and the prescription. The clinical note is still yours to write, consult after consult.
> - Patient Square's Assist plan is ₹1,599/month per doctor on annual billing + 18% GST, with an ambient AI scribe and unlimited notes. Over 3 years it costs roughly 3x MyOPD.
> - The decision isn't which is cheaper. It's whether your documentation hours are worth more than the price gap.

## What MyOPD gets right at its price

Credit first. MyOPD's pricing page, as of July 2026, lists a Clinic version at ₹18,700 one-time (inclusive of ₹2,853 GST) or ₹8,000 a year as a subscription, a Polyclinic version at ₹24,000 one-time for multiple OPD desks, and a free version for a limited number of patients. A hospital version with IPD and bed management exists too, priced on request. From year two, an optional annual maintenance charge keeps updates, cloud backup, and app access running; MyOPD's own pages say the one-time licence keeps working even if you skip it.

The feature set is squarely aimed at the Indian solo practice: prescription entry designed to be fast, printing in 13 Indian languages, thermal printer support, prescription PDFs over WhatsApp, SMS and WhatsApp appointment reminders, UPI payments, and a simple income-and-expense view.

For a doctor with a receptionist, thirty patients a day, and a hard budget cap, that's a sensible purchase. We think clinics in exactly that spot should buy it and move on. No subscription guilt, no per-month meter.

## The honest cost table

Here's the money over three years, using each vendor's own published figures. MyOPD's listed prices include GST; Patient Square's are ex-GST, so we've shown the GST-inclusive math once.

| | MyOPD Clinic (one-time) | MyOPD Clinic (subscription) | Patient Square Assist | Patient Square Copilot |
|---|---|---|---|---|
| Price basis | ₹18,700 once, GST included | ₹8,000/year | ₹1,599/mo per doctor, annual billing, + 18% GST (≈₹1,887 with GST) | ₹2,399/mo per doctor, annual billing, + 18% GST |
| 3-year software cost | ₹18,700 + AMC from year 2 | ₹24,000 | ₹57,564 ex-GST | ₹86,364 ex-GST |
| Appointments + billing | Yes | Yes | Scheduling included | Scheduling included |
| Prescription | You type it; prints in 13 languages | Same | Drafted from the consult, you review and sign | Same, plus bundled AI EHR and WhatsApp messaging |
| The clinical note | You write it | You write it | Drafted by the ambient scribe, unlimited | Same, stored in the bundled EHR |

_Sources: myopd.in pricing page and Patient Square pricing page, both July 2026. AMC amount varies; confirm with MyOPD._

Read the bottom two rows again. That's the entire comparison. On price, MyOPD wins and it isn't close. What you're actually weighing at [Patient Square's pricing](/in/pricing/) is a different line item: your evenings. If the table already settles it for you, book a demo and test the claim on a real patient.

## What does ₹1,599 a month actually add?

One thing, done properly: the consultation documents itself.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. You talk to the patient. The note gets written. You read it, correct anything, sign it. Every plan includes unlimited visits and notes with no per-note metering, capture on web or mobile, and EHR-ready export (PDF · HL7 · FHIR), so the record can land wherever you keep records today, including alongside software you already own.

Why does that matter in an Indian OPD specifically? Because the consult itself is about two minutes long. That's the average Irving et al. found for India in their 67-country BMJ Open review. Two minutes to listen, examine, decide, prescribe. There is no third minute for typing a proper note, which is why most OPD records are one scribbled line, and why the National Medical Commission's 2023 conduct regulations, which set an expectation of outpatient records kept for three years (the 2023 regs are in abeyance rather than in force, but the expectation is the direction of travel), are quietly uncomfortable reading for a busy clinic.

Picture the 8:40pm version of this. A Nashik GP, 61 patients seen, register full of token numbers and fees, and 22 consultations with no real note behind them. MyOPD did its job all day: patients booked, bills printed, prescriptions out the door. The note gap isn't MyOPD's failure. It was never built to close it. It's a front-desk tool, and the note is a consult-room problem.

The scribe also handles how Indian consultations actually sound: English, Hindi, and 20+ Indian languages, switched mid-sentence, with the note always returned in clean clinical English. Hindi in, English record out.

One boundary worth stating plainly: the prescription output is a draft for your review and signature, not an e-prescribing transmission, and the ICD-10 output is suggestions, not a coding engine. You stay the clinician of record.

## And what ₹2,399 adds on top of that

The Copilot tier, at ₹2,399 a month per doctor on annual billing ex-GST, adds the bundled AI Copilot EHR and WhatsApp messaging. That's the point where Patient Square stops being a documentation layer next to your existing software and becomes the record system itself. Solo doctors who mostly want their evenings back start at Assist; clinics replacing a patchwork of tools land on Copilot. The [OPD software buyer guide](../opd-software-for-clinic-india/) walks the full stack decision if you're rethinking more than the note.

Data handling, since a scribe listens to consults: audio is processed in memory and discarded once the note drafts, nothing is sold or shared, and the practice owns its notes with export or delete anytime, handled to DPDP Act 2023 standards. SOC 2 Type II audit is in progress, not certified, and ABDM integration is on our roadmap, not live. If live ABHA linking is a requirement today, say so in the demo and we'll tell you honestly what's there. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## When MyOPD is the better choice

Buy MyOPD, or keep it, if any of these fit:

1. Your budget is a hard cap near ₹20,000 total, not per year. Nothing with a monthly per-doctor price competes with a one-time licence.
2. Your OPD runs under about 30 patients a day and you genuinely have time to write your notes, or you've made peace with short ones.
3. What you want is front-desk order: bookings, tokens, bills, reminders, a printed prescription in your patient's language. MyOPD was built for exactly this.
4. You want to own the software outright and hate recurring fees on principle.

That's a real constituency, and for it, MyOPD is the right answer. A ₹1,599-a-month scribe only earns its fee when documentation time is the thing being bought back. Our [clinic software scorecard](../best-clinic-management-software-india/) scores the wider field if neither product here fits, and the [MocDoc comparison](../mocdoc-alternatives-india/) covers the suite-style middle ground between a budget app and an AI platform.

## A 15-minute way to decide

Count one thing today: minutes spent writing notes and prescriptions after the patient has already left, across the whole day. Under 20 minutes, MyOPD-class software is enough; you'd be buying convenience. Over an hour, you're paying a ₹1,599 problem out of your own evening, every day, and the maths flips fast.

Then test rather than believe. Patient Square runs a 7-day free trial, so you can put it on a real Tuesday OPD and read the notes it produces against the ones you didn't have time to write. Book a demo to see a consult turn into a signed note first, or start with the [pricing page](/in/pricing/) and run your own numbers. Either way, decide on your minutes, not our adjectives.

---

## QMarkSoft Alternatives in India: The Clinic-Side Answer
https://patientsquare.com/in/blog/qmarksoft-alternatives-india/
Published 2026-08-26 · Tags: qmarksoft, alternatives, pathology-lab, clinic-software, india

QMarkSoft is a path-lab-first suite, and for lab benches it earns its place. Where the OPD note needs more, here's the ambient AI side of the comparison.

QMarkSoft is an Indian software house selling across several verticals: pathology and diagnostic labs, hospitals, clinics, schools, micro-finance, and MR reporting, with products offered in online, offline, and hybrid versions. Its pathology-lab management system is the flagship, and its clinic product is described as online and offline clinic management software with a mobile app and prescription.

QMarkSoft alternatives split cleanly by which half of the building you're buying for. For the lab downstairs, the samples, collections, reports, and billing, QMarkSoft is a path-lab-first vendor and we're not going to talk you out of it; Patient Square doesn't sell LIMS at all. For the consult room upstairs, where the OPD note either gets written or doesn't, the alternative worth testing is an ambient AI scribe that drafts the note while you talk, from ₹1,599 per clinician a month on annual billing, plus 18% GST. Book a demo if the consult room is the half you came for.

> **Key takeaways**
>
> - QMarkSoft is a multi-vertical Indian software shop covering path labs, hospitals, clinics, schools, and micro-finance; the lab ERP is the flagship.
> - Its clinic product is "online and offline clinic management software with mobile app and prescription", in their words. Pricing isn't published.
> - Offline and hybrid deployment is a real strength where internet is patchy.
> - We concede the lab bench outright: Patient Square has no LIMS and no plans to fake one.
> - The consult room is the wedge: at India's ~2-minute average consult, an ambient scribe writes the note a form can't capture. Entry ₹1,599/mo annual, ex-GST.

## Which half of the building is the problem?

A lot of QMarkSoft's Indian customers aren't running a pure clinic or a pure lab. They're running both under one roof: collection counter and analyser downstairs, two consult rooms upstairs. One vendor covering the whole building for one negotiated price is exactly how QMarkSoft positions itself, and for the lab half the pitch holds up.

The two halves have different failure modes, though. Labs fail on process: lost samples, slow reports, billing mismatches. Consult rooms fail on documentation: notes that never get written because the queue is long and the consult is short. Software that fixes the first has no mechanism for fixing the second, which is why this comparison is a split decision rather than a verdict. For what a standalone lab system does that a bundled module can't, our [LIMS explainer](../lab-management-software-india-lims/) walks that side properly.

## What QMarkSoft covers, plainly

From their own site: QMarkSoft sells software for pathology and diagnostic labs, hospitals, clinics, schools, educational institutes, micro-finance and Nidhi banking, GST billing, and MR reporting, in "online, Offline and Hybrid" versions. The clinic product is described as online and offline clinic management software with a mobile app and prescription. The lab product gets its own dedicated ERP and the bulk of the marketing attention, and third-party listings describe automated test-result management for labs from small to large.

Two things a buyer should register. First, the offline and hybrid deployment options are genuinely useful in settings where connectivity drops; their own pitch calls offline "cost effective and better for the business, having limited internet access", and that's a fair claim for a tier-3 town. Second, the breadth reads like a services-era software house: nine verticals from one vendor. That can mean attentive customisation. It can also mean the clinic module gets the leftovers of a roadmap centred on labs and schools. Ask directly how many people work on the clinic product, and ask for the full price in writing, because the site publishes none.

## We'll concede the lab outright

No hedging on this one. If your revenue runs through a path lab, buy lab software from a lab-software company. Sample tracking, collection workflows, report formatting, analyser data, lab billing: QMarkSoft built its reputation there, and Patient Square has none of it. There's no LIMS in any Patient Square plan, and no roadmap promise we'd want you to price in.

When QMarkSoft is the better choice, then: a standalone diagnostic centre, a lab-led business with a small OPD attached, a setup that needs offline billing at the collection counter, or an owner who wants one local vendor relationship across lab, clinic, and even the attached school van route. That's their home ground. Stay on it.

## Upstairs, the note still dies in a form

Now the consult room. A Patna clinic-plus-lab runs a tidy operation downstairs: barcoded samples, reports out by evening. Upstairs, the OPD sees 80 patients before 2pm, and the clinic module's prescription screen gets exactly what a two-minute consult allows: a drug list. Indian consultations average about two minutes, per a 67-country BMJ Open review. The history, the findings, the reasoning behind the drug list? Unwritten, again, because a prescription module gives you a place to type and no time to type in it.

That asymmetry is medico-legal, not cosmetic. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. Downstairs, every sample has a paper trail. Upstairs, the consult that ordered the test often doesn't. It's a strange place for a healthcare business to keep its thinnest records.

## The coverage map

| Function | QMarkSoft | Patient Square |
|---|---|---|
| Lab: samples, reports, lab billing | Flagship product | Not offered, no plans |
| Offline deployment | Online, offline, and hybrid versions | Offline encrypted capture for low-signal clinics; cloud product |
| Clinic registration and billing | Included in clinic software | Not the focus; scheduling ships from the entry plan |
| Prescription | Prescription module (you type) | Prescription draft, written by the scribe, you review and sign |
| The clinical note | A field to fill | Drafted from the conversation: SOAP note plus ICD-10 suggestions |
| Consult languages | Not stated on their pages | English, Hindi + 20 more, code-mixed in; clinical English out |
| Pricing | Not published; quote-based | Published: ₹1,599/mo entry annual, ex-GST |

Read the rows you actually need. A diagnostic centre reads the top three and should call QMarkSoft. A documentation-starved OPD reads the middle three and should book a demo instead.

## The consult room, handled as its own layer

The AI Medical Scribe by Patient Square is one module inside Practice Copilot, our AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The scribe is a documentation layer, not a lab suite: it sits in the consult room, hears the visit in English, Hindi, or 20+ Indian languages including code-mixed Hinglish, and returns the note in clean clinical English. Audio is processed in memory and discarded once the note drafts. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

It also doesn't trap the record. Every plan includes EHR-ready export (PDF · HL7 · FHIR), so notes can travel to whatever else the building runs, lab reports included. Data is handled to DPDP Act 2023 standards and a SOC 2 Type II audit is in progress; the details are on the [security page](/in/security/). We think the two-vendor answer, lab ERP downstairs, ambient scribe upstairs, beats a single vendor doing one half well and the other half nominally. The plan ladder is published: Assist ₹1,599 a month annual (about ₹1,887 with 18% GST), Copilot ₹2,399 with the bundled AI EHR, Autopilot ₹3,999, all per clinician, ex-GST, with unlimited notes and a 7-day trial. Full numbers on the [India pricing page](/in/pricing/), and the wider OPD software field is mapped in our [200-patient-day buyer guide](../opd-software-for-clinic-india/).

The one-question version of this whole page: where do your thinnest records live? If it's the lab, QMarkSoft deserves the call. If it's the consult room, run the scribe on a real OPD morning and book a demo to set that up.

---

## Scribeberry Alternatives: After the 20-Use Free Month
https://patientsquare.com/us/blog/scribeberry-alternatives/
Published 2026-08-26 · Updated 2026-08-27 · Tags: scribeberry, alternatives, ai-scribe, pricing

Scribeberry's free tier caps at 20 uses a month and Pro runs $99. The upgrade math against an unlimited ambient scribe with a bundled EHR path.

Scribeberry's published pricing shows a free tier (3 days unlimited, then 20 uses per month), a Pro plan at $99 per month with unlimited use, and an Enterprise plan at $79 per user per month for teams of five or more providers. Those figures come from their own pricing page as of this writing.

If you're looking at Scribeberry alternatives, you're usually solving one of two problems: the free tier's 20-uses-a-month cap stopped covering your volume, or you're about to pay the $99 Pro price and want to know what else that money buys. The main alternative worth pricing out is an unlimited ambient scribe with an EHR path, which is what Practice Copilot from Patient Square is.

Scribeberry is a fair product with published prices, which already puts it ahead of half this market. So this isn't a takedown. It's the upgrade math, run honestly, with the cases where staying is the right call. If you'd rather watch the alternative run on your own visit types first, book a short demo and bring a real chart day.

> **Key takeaways**
>
> - Scribeberry's published ladder: free (3 days unlimited, then 20 uses/month), Pro at $99/month unlimited, Enterprise at $79/user/month for 5+ providers.
> - 20 free uses covers about one visit per working day. A 15-patient-day clinician produces roughly 300 notes a month.
> - At the paid tier the prices nearly touch: their Pro is $99 monthly; Practice Copilot's Assist plan is $99 month-to-month or $79 on annual billing.
> - The real difference is what comes back per visit (SOAP draft plus ICD-10 suggestions plus an Rx draft) and where the note goes: EHR-ready export on every plan, bundled AI EHR at the $119 Copilot tier.

## What Scribeberry gives you, and where the caps sit

Scribeberry sells an AI medical scribe aimed at both Canada and the US. Its pricing page, which is refreshingly specific, lists three tiers as of this writing: a free plan that starts with 3 days of unlimited use and then settles at 20 uses per month, a Pro plan at $99 a month with unlimited use, custom templates, dictation and transcription, and an Enterprise plan at $79 per user per month for teams of five providers and up, with custom integrations and white labeling. The same page lists HIPAA and PIPEDA compliance, SOC 2 Type 2, end-to-end encryption, Canadian data hosting, and zero audio retention across plans.

Two things stand out. First, the free tier is a real free tier, not a 7-day teaser, and that's the honest reason Scribeberry shows up on budget shortlists. Second, the Canadian DNA runs deep: PIPEDA, Canadian hosting, and integrations its site describes with Oscar and TELUS, which are Canadian EMRs. For a US practice, that second part is mostly neutral. For a Canadian one, it's the pitch.

## 20 uses is one good Tuesday

Here's where the free tier meets a real panel. Say you run an urgent care shift on a Friday in flu season and see 22 patients. If every visit gets a note, you've burned your entire monthly allowance plus two before the weekend. The cap doesn't fail loudly; it fails by making you ration, deciding at 2pm which patients are worth an AI note and which get typed the old way.

| Your volume | Notes/month (approx.) | Free tier coverage (20 uses) | What's left to type |
| --- | --- | --- | --- |
| 1 visit/day, side panel | ~20 | Everything | Nothing |
| 8 patients/day, part-time | ~160 | About 13% | ~140 notes |
| 15 patients/day | ~300 | About 7% | ~280 notes |
| 22 patients/day | ~440 | About 5% | ~420 notes |

The first row is the interesting one. If your documentation load genuinely fits inside 20 uses, Scribeberry free is unbeatable at $0 and you should probably stop reading. Every other row is really a paid-tier decision wearing a free-tier costume. Our wider [AI scribe cost comparison](../ai-medical-scribe-cost-comparison/) maps the whole market's prices if you want the full landscape; the pattern of free tiers that cap and then upsell also shows up in our look at [Nabla past its free-tier cap](../nabla-alternatives/).

## The $99 question: what does the same money buy?

Once you're paying, the comparison gets close enough that the decision stops being about price. Scribeberry Pro is $99 a month. Practice Copilot's Assist plan is $99 month-to-month, or $79 per clinician per month on annual billing. Call it a wash monthly and a $240-a-year gap on annual.

So compare what each hands back per visit. Scribeberry Pro gives you unlimited scribing, dictation, custom templates, and (per its pricing page) AI agents for pre-intake. The AI Medical Scribe by Patient Square is one module inside Practice Copilot, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The codes are suggestions you confirm, the prescription is a draft you decide on, and nothing enters a chart without your signature.

Then compare where the note goes. Every Patient Square plan includes EHR-ready export (PDF · HL7 · FHIR) plus unlimited visits and notes with no per-note metering. And one tier up, the Copilot plan at $119 a month annual bundles an AI EHR and WhatsApp messaging, which matters if the thing you're actually shopping for is a system of record, not just a note generator. [The per-plan breakdown](/us/pricing/) lists exactly what ships where.

We think this is the fair framing: at the paid tier you're not choosing cheap versus expensive, you're choosing between a scribe with intake extras and a scribe that's the front door to a documentation platform. Which one wins depends on whether your next problem after notes is intake forms or the EHR itself.

## Where the two trust stories differ

Both vendors say the right things; the details differ in ways worth knowing. Scribeberry's pricing page lists SOC 2 Type 2 and zero audio retention, with data hosted in Canada. On our side: HIPAA-compliant safeguards, a BAA available for every customer, a SOC 2 Type II audit currently in progress (we'll say "in progress" until it isn't), and visit audio that's processed in memory and discarded once the note is drafted. Notes belong to the practice, and you can export or delete any visit anytime. The full detail is on the [security page](/us/security/).

If data residency is a board-level question for you, ask both vendors where PHI lives and get it in writing. That's a two-sentence answer from anyone who has one.

## When Scribeberry is the better fit

Three cases, and they're not edge cases.

If you practice in Canada, Scribeberry is probably the default. PIPEDA posture, Canadian data hosting, and integrations its site describes with Oscar and TELUS are exactly what a Canadian clinic needs, and none of them are things we'd claim to match today. If your volume truly fits inside 20 uses a month, the free tier is the best price in the market: $0. And if you're a 5-plus provider group that wants white labeling and custom integrations at $79 a user, their Enterprise tier is built for precisely that shape.

Outside those three, the decision comes down to the per-visit payload and the EHR path, and that's a trial question, not a blog-post question.

## Run both on the same clinic week

Pick one representative week. Run Monday and Tuesday's visits through Scribeberry, Wednesday through Friday's through Patient Square's 7-day trial, and time the loop that actually costs you evenings: draft, edit, sign, export, done. Count the edits, not the demos. Then look at [what each plan costs](/us/pricing/) with your real volume next to it, and if you want the trial set up around your specialty's note formats, book a demo and we'll do it with you.

---

## Twofold Health AI Alternatives: Notes Tool or Platform?
https://patientsquare.com/us/blog/twofold-health-ai-alternatives/
Published 2026-08-26 · Updated 2026-08-27 · Tags: twofold-health, alternatives, therapy-notes, ai-scribe

Twofold is a $49 therapy-notes AI with flexible capture modes. What an ambient scribe with ICD-10 suggestions and an EHR path changes, honestly.

Twofold's published Personal plan is $49 a month, which its own comparison content describes as the annual-billing rate, with $69 month-to-month and a discounted first month running as of this writing. Paid plans include unlimited notes, templates, and a signed BAA. Group pricing is custom. Their pricing page is the source of truth.

Twofold Health is a $49-a-month AI notes tool with a therapy tilt, and the honest alternative to it isn't "a cheaper Twofold." It's deciding whether you want a notes tool at all, or a documentation platform: an ambient scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, with an EHR bundled one tier up. That's the actual choice, and price is only half of it.

We'll lay out what Twofold publishes, where it's legitimately the better buy, and what changes when the note is the start of the pipeline instead of the whole product. If seeing beats reading, book a short demo and we'll run it on your session format.

> **Key takeaways**
>
> - Twofold publishes real prices: $49/month Personal (annual rate per their own materials; $69 month-to-month), unlimited notes, signed BAA, 7 days free without a card.
> - It captures four ways: record the session live, dictate a summary afterward, type rough notes, or upload an audio file.
> - Practice Copilot's Assist plan is $79/month annual; the gap buys ICD-10 suggestions, a prescription draft, and EHR-ready export (PDF · HL7 · FHIR) on every plan.
> - A bundled AI EHR arrives at the $119 Copilot tier, which is the fork where a notes tool and a platform stop being comparable.

## What Twofold Health actually ships

Twofold's pitch is speed and price for clinical notes, with behavioral health as its center of gravity. The published Personal plan runs $49 a month, which Twofold's own comparison content describes as the annual-billing rate with $69 month-to-month, and there's a discounted first month running as of this writing. Paid plans include unlimited note generation, a clinical template library, treatment plans and progress tracking, HIPAA posture with a signed BAA, and what their site calls EHR compatibility, meaning it works alongside whatever record system you already use. Group plans are custom-priced.

The capture flexibility is the standout feature. Twofold takes four kinds of input: a live session recording, a dictated summary after the patient leaves, typed rough notes, or an uploaded audio file. That flexibility is genuinely useful for a practice with mixed habits, say one clinician who records and another who'd rather brain-dump into a text box at day's end. Their site also lists CPT and ICD coding among plan features; read that list literally and test it on your own notes, the same advice we'd give about anyone's feature page, ours included.

So: a competent, cheap, flexible notes tool. The question a buyer should actually ask is what happens after the note exists.

## The note is where Twofold stops. It's where the pipeline starts.

Picture the Thursday of a full-caseload therapist: six 50-minute sessions, the last ending at 7pm. A notes tool solves the 9pm problem, the two hours of reconstructing sessions from memory. Good. But if you bill insurance, the note then needs a diagnosis code on the claim. If you're a prescribing clinician, an NP in psychiatric practice for instance, the visit also produced a medication decision that needs documenting. And every note needs somewhere to live that isn't a folder of PDFs.

That downstream chain is the difference in kind. The AI Medical Scribe by Patient Square is one module inside Practice Copilot, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The codes are suggestions you confirm, not a billing engine; the prescription is a draft you decide on, not a transmission. For a non-prescribing, self-pay therapist, we'll admit the Rx draft is dead weight. For everyone billing claims or writing scripts, it's the part of the evening the notes tool didn't touch.

| What you're comparing | Twofold Health (published) | Practice Copilot (Patient Square) |
| --- | --- | --- |
| Price | $49/mo annual rate per their materials; $69 monthly | $79/mo annual Assist; $99 monthly |
| Notes volume | Unlimited on paid plans | Unlimited visits and notes, no per-note metering |
| Capture | Record live, dictate summary, type notes, upload audio | Ambient capture during the visit; dictate or record on web or mobile |
| Per-visit payload | Clinical note to your template; site lists CPT/ICD coding | SOAP note + ICD-10 suggestions + Rx draft, about 2 min after the visit |
| Where the note goes | Pairs with your existing EHR | EHR-ready export (PDF · HL7 · FHIR), every plan |
| An EHR itself | Not included | Bundled AI EHR at the Copilot tier, $119/mo annual |
| BAA | Signed BAA included | BAA available for every customer |

The [full plan breakdown](/us/pricing/) has the tier-by-tier detail; if the table's bottom row is the one you paused on, that's the fork that matters.

## The $30 gap, and the $70 fork

Two money decisions hide in this comparison, and they're different sizes.

The small one: $49 versus $79 a month on annual billing, a $360-a-year gap. What it buys is the per-visit payload above plus export formats a record system can actually ingest. If none of that changes your Thursday, keep the $360, sincerely.

The bigger fork: Twofold plus the EHR you already pay for, versus the Copilot tier at $119 a month annual with an AI EHR bundled in. If your current record system is a subscription you resent, the platform math can come out ahead of the notes-tool math even though the sticker is higher. Our guide for therapists weighing exactly this, [an AI scribe for DAP and BIRP notes without night charting](../ai-scribe-for-therapists/), goes deeper on the workflow, and the [SimplePractice alternatives comparison](../simplepractice-alternatives/) covers the adjacent question of leaving a therapy platform whose built-in AI notes feel thin.

Privacy sits on top of both decisions for this specialty. Therapy audio is as sensitive as recordings get. On our side, visit audio is processed in memory and discarded once the note is drafted; there's no audio archive, safeguards are HIPAA compliant, a SOC 2 Type II audit is in progress, and the whole posture is written up on the [security page](/us/security/). We didn't find a published audio-retention figure for Twofold while researching this, which isn't an accusation, just a question you should make them answer in writing. Our piece on [privacy-first scribing for behavioral health](../ai-scribe-for-behavioral-health/) lists the rest of the questions worth asking any vendor.

## When Twofold is the better fit

Often, and here's exactly when.

You're a solo, self-pay, non-prescribing therapist. No claims, no scripts, settled diagnoses. Twofold's payload covers your real needs at $30 less a month, and the ICD-10 and Rx pieces of our pitch do nothing for you. Buy the cheaper tool.

Your practice's habits are mixed. If half your documentation happens as typed rough notes or a dictated recap in the car, Twofold's four capture modes fit that reality better than an ambient-first workflow does.

You want the smallest possible commitment. $49 with a discounted first month and 7 free days without a card is a low-friction way to find out whether AI notes help you at all. Starting there and reassessing in six months is a defensible plan, not a compromise.

## Run the two-week test and count edits

Feature tables don't finish this decision; a fortnight does. Week one, run your real sessions through Twofold's free week. Week two, run the same session types through Patient Square's 7-day trial. Track two numbers only: edits per draft before you'd sign it, and minutes from session end to note signed and filed. Then put your claim workflow next to each. The [pricing page](/us/pricing/) shows what each plan costs at your caseload, and if you want the trial preloaded with your note format, DAP, BIRP, or SOAP, book a demo and we'll set it up before your Monday intake.

---

## DocOn App Alternatives in India: Beyond the Rx Pad
https://patientsquare.com/in/blog/docon-app-alternatives-india/
Published 2026-08-25 · Tags: docon, alternatives, e-prescription, india

DocOn digitises the prescription in seconds. What the PharmEasy-family EMR app does well, what a fast Rx still leaves unwritten, and an ambient AI option.

No, and the names trip people constantly. DocOn (docon.co.in) is an EMR and digital-prescription app for doctors, described on its own LinkedIn page as acquired by PharmEasy. DocOnline is a separate telemedicine and corporate-health network that delivers consultations through its own doctor panel. This page covers DocOn, the prescription app.

Clear the name trap first: DocOn is not DocOnline. DocOn (docon.co.in) is the digital-prescription and EMR app for doctors, now in the PharmEasy family. DocOnline is a separate teleconsultation and corporate-health network, covered in our [DocOnline comparison](../doconline-alternatives-india/). If you're a DocOn user weighing alternatives, the short version: DocOn digitises the prescription in seconds, and that's genuinely useful, but a prescription is not a clinical note. An ambient AI scribe writes the whole note, from ₹1,599 per clinician a month on annual billing, plus 18% GST. Book a demo if you'd rather see that than read about it.

> **Key takeaways**
>
> - DocOn and DocOnline are different companies. This page covers DocOn, the Rx-and-EMR app; a separate post covers DocOnline.
> - DocOn's site claims 4,000+ verified doctors, 25M+ digital prescriptions, and prescriptions generated "within a few seconds", with a 15-day trial and no published pricing.
> - Its LinkedIn page describes it as acquired by PharmEasy; the product ties into e-pharmacy and e-diagnostics partners for home delivery.
> - A fast Rx still leaves the note unwritten, and the operative 2002 medical ethics code requires three-year retention for indoor records.
> - Patient Square drafts the full SOAP note, ICD-10 suggestions, and an Rx draft; entry is ₹1,599/month annual, ex-GST.

## Which DocOn did you mean?

Two Indian health-tech brands sit one syllable apart, and they do completely different jobs. DocOn is software a doctor uses inside their own practice: an EMR built around producing a digital prescription fast, with a companion patient app. DocOnline is a service patients and employers buy: teleconsultations delivered by DocOnline's own panel of doctors, sold as family plans and workplace-wellness programmes.

Search engines blur them. Your shortlist shouldn't. If your question is "what replaces the network my employer buys consults from," read the [DocOnline alternatives post](../doconline-alternatives-india/) instead. Everything below is about DocOn, the Rx app in your pocket.

## What DocOn does well

Credit where due, from their own published pages. DocOn pitches itself as a one-stop way to digitise a clinic, and the core promise is speed: "generate the prescription within a few seconds." The site claims 4,000+ verified doctors across 20+ specialties and 100+ cities, more than 25 million digital prescriptions, and about a million prescriptions generated monthly. The app listing adds patient history on one screen, investigation storage, vaccination reminders, and growth charts, which explains its following among paediatricians. There's a 15-day free trial; published pricing, as of this writing, there is none.

Then there's the ownership, which matters more than most feature rows. DocOn's LinkedIn page describes it as acquired by PharmEasy, and the product connects to e-pharmacy and e-diagnostics partners so patients can get medicines and lab tests delivered home. For patients, convenient. For the clinic, worth thinking through: the software sits upstream of a delivery business, and that's part of why it can be priced the way it is. Not a red flag, just the model. Know whose funnel your prescription pad feeds.

## A prescription is not a note

Here's the wedge, stated plainly. An Rx that prints in seconds solves the last 30 seconds of the consult. It does nothing for the record of the other 90.

An Indore paediatrician clearing 90 patients a day on a fast Rx app ends the day with 90 tidy prescriptions and, very often, 90 near-empty records: drug names without the reasoning. Indian consultations average about two minutes, per a 67-country BMJ Open review. In that window, structured history, findings, assessment, and plan don't get typed, whatever the software. The prescription is the one artefact that must exist for the patient to leave, so it's the one artefact that does.

The gap has teeth. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. When a treatment decision is questioned later, the prescription alone doesn't explain why you chose that drug. The reasoning does, and the reasoning lives in the note nobody had time to write. Our [medico-legal documentation post](../ai-scribe-medico-legal-documentation-india/) goes deeper on what a defensible record looks like.

## Rx pad vs ambient documentation

| | DocOn (published claims) | Patient Square (Practice Copilot) |
|---|---|---|
| Core promise | Prescription "within a few seconds" | Full SOAP note drafted from the conversation |
| What you enter | Diagnosis, drugs; templates speed the pad | Nothing during the consult; you review after |
| Output | Digital Rx + EMR fields you fill | Structured note, ICD-10 suggestions, Rx draft |
| Patient-facing | Companion app, reminders, med delivery via partners | No patient marketplace; clinical tool only |
| Business model | PharmEasy family; e-pharmacy/diagnostics tie-ins | Per-clinician software subscription |
| Pricing | Not published; 15-day trial | Published: ₹1,599/mo entry, annual, ex-GST; 7-day trial |

If the second column is what your evenings are missing, book a demo and test it against a live OPD block.

## When DocOn is the better choice

If your documentation need genuinely starts and ends at a fast, legible digital prescription with a patient app behind it, DocOn is the purpose-built tool, and switching would buy you nothing. High-volume OPDs that run on standard drug regimens, clinics that lean on the medicine-delivery tie-ins as a patient convenience, and paediatric practices using the growth-chart and vaccination features are all square in its lane. The 15-day trial costs nothing but time, and the app's speed claims are the kind you can verify in an afternoon.

Be honest about one more case: if your notes are thin because you choose speed over narrative, and you're comfortable with that trade, an ambient scribe solves a problem you've decided not to have.

## The full-note alternative

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription part of your workflow doesn't get slower; it gets absorbed. You still review and sign every draft, eRx included, and the drafts arrive with the clinical reasoning already written around them.

It's built for the consult as it actually sounds: English, Hindi, and 20+ Indian languages, code-mixing included, with the note always returned in clean clinical English. Audio is processed in memory and discarded once the note drafts. Records are handled to DPDP Act 2023 standards, a SOC 2 Type II audit is in progress, and every plan carries EHR-ready export (PDF · HL7 · FHIR), so notes move with you rather than locking you in. ABDM integration is on the roadmap, not live today, and we'd rather tell you that than badge it. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing is published, which we think should be table stakes in this market. Assist is ₹1,599 per clinician per month on annual billing (₹1,999 monthly), ex-GST; with 18% GST that's about ₹1,887. Copilot at ₹2,399 adds the bundled AI Copilot EHR and WhatsApp messaging. Unlimited visits and notes on every plan, no per-note metering, no setup fee. The ladder is on the [India pricing page](/in/pricing/), and the wider e-prescription legal picture, what makes a digital Rx valid in India in the first place, is covered in our [e-prescription validity checklist](../e-prescription-software-india-legal/).

Run the honest test: same patients, one week, both tools. Count what's in the record at 6pm. If the prescription pad is all you ever needed, DocOn earned its place. If the record should hold the reasoning too, book a demo and let the scribe write Tuesday's notes.

---

## Jane App Alternatives: When the Note Is the Bottleneck
https://patientsquare.com/us/blog/jane-app-alternatives/
Published 2026-08-25 · Updated 2026-08-31 · Tags: jane-app, alternatives, practice-management, ai-scribe

Jane is a loved allied-health platform, and it now has a $15 AI Scribe add-on. An honest look at who should leave, who should stay, and why.

Yes. Jane added an AI Scribe add-on priced at $15 a month per opted-in practitioner, with unlimited use. Jane's guide describes it drafting chart notes from live session recordings or post-appointment dictation, inside Jane, with templates you pick and drafts you review and sign. For clinics living in Jane, it's honest value.

Most people searching for Jane App alternatives don't have a Jane problem. They have a documentation problem that a booking-and-billing platform was never built to carry. Practice Copilot addresses that problem with an ambient scribe and either Patient Square EHR from the Copilot tier or an alongside path for an existing EHR.

Jane earned its reputation. It's the scheduling-payments-charting home of thousands of allied-health clinics, and it now ships its own AI Scribe add-on, which we'll cover fairly because it changes this comparison. If your bottleneck turns out to be the note, book a short demo and watch a visit become a signed draft.

> **Key takeaways**
>
> - Jane's published ladder: 54 / 79 / 99 a month (Balance, Practice, Thrive) in local currency, with Balance capped at 20 appointments monthly and extra practitioners priced via their calculator.
> - Jane's AI Scribe add-on is $15 a month per opted-in practitioner, unlimited, drafting chart notes from live recordings or post-appointment dictation inside Jane.
> - Practice Copilot runs per clinician from $79/month annual: ambient SOAP notes with ICD-10 suggestions and an Rx draft about 2 minutes after each visit, plus a bundled AI EHR at the $119 Copilot tier.
> - On raw dollars, a multi-practitioner allied clinic usually pays less on Jane. The switch case is documentation depth, not price.

## What Jane is, and why people rarely leave it angry

Jane is a practice management platform aimed at allied health, wellness, and mental health: online booking, scheduling, charting, payments, insurance features, telehealth, all in one subscription. The published plans read 54, 79, and 99 a month for Balance, Practice, and Thrive; their pricing page shows local currency (our fetch displayed Canadian dollars), so check what your region sees. Balance caps you at 20 appointments a month, Practice and Thrive lift that and add practitioners through a per-practitioner fee Jane prices via an on-page calculator; a third-party guide pegs that range around $17.50 to $40 depending on hours worked.

And Jane did the smart thing on documentation: it built in an AI Scribe add-on at $15 a month per opted-in practitioner, unlimited use. Jane's own guide describes it drafting chart notes from a live session recording or post-appointment dictation, with the practitioner choosing a template and reviewing and signing the draft. Jane says the feature is HIPAA, PIPEDA, and PHIPA compliant and that patient data is not used to train models. For $15 inside a platform you already run, that's honest value, and any "Jane alternatives" article that pretends otherwise is selling you something.

So why does this page exist? Because a subset of Jane clinics discover, usually somewhere around practitioner number three or prescription number forty, that their actual constraint isn't bookings. It's the chart.

## The front-desk problem and the note problem are different purchases

Jane's center of gravity is the front desk: getting patients booked, paid, reminded, and billed. Charting is present and capable, but it's one room in the house. A documentation-first platform inverts that. The visit is the input, the note is the product, and everything else grows around the record.

Concretely: a family NP running a cash-pay practice sees 19 patients on a Monday. Every visit produces a note, most produce a diagnosis code, several produce a prescription decision. On a PM-first platform, each of those is a separate manual step after the patient leaves. The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The codes are suggestions you confirm and the prescription is a draft you decide on; nothing files itself. Jane's guide describes its scribe drafting chart notes from recordings or dictation; if your visits also need code suggestions and prescription drafts every time, that's the depth gap this whole comparison turns on, and it's worth testing side by side rather than taking either vendor's word.

Where the note goes next differs too. Every Practice Copilot plan includes EHR-ready export (PDF · HL7 · FHIR) and unlimited visits and notes with no per-note metering, plus scheduling from the base plan. At the Copilot tier, $119 per clinician per month on annual billing, a bundled AI EHR comes in, so the notes have a system of record without a second vendor. Assist starts at $79. The [plan-by-plan detail](/us/pricing/) is public.

## An honest decision matrix

We'd rather you place yourself in the right row than read another feature grid.

| Your situation | Stay on Jane | Move to a documentation-first platform |
| --- | --- | --- |
| Allied-health clinic, front desk is the pain (booking, payments, no-shows) | Yes. This is Jane's home turf. | No. You'd be buying depth you don't need. |
| Happy on Jane, notes feel slow, non-prescriber | Yes. Try the $15 AI Scribe add-on first. | Only if the add-on's drafts fall short after a real month. |
| Prescriber (MD, DO, NP, PA) with coding and Rx documentation on every visit | Maybe, with workarounds. | Yes. Code suggestions plus Rx drafts per visit is the job here. |
| Notes routinely finish after 8pm despite templates | The add-on may help; measure it. | Yes, if ambient capture beats it in your own two-week test. |
| Multi-practitioner clinic optimizing raw software spend | Usually yes; Jane's base-plus-add-on model prices lower. | Only if per-clinician documentation depth pays for itself in time. |
| You also want the record system bundled with the scribe | No; Jane is the record, scribe is the add-on. | Yes; that's the Copilot tier's whole design. |

That middle-right cell deserves the emphasis. We think the fair test between Jane's scribe and ours isn't features listed, it's edits counted: run ten real visits through each and tally how many corrections a draft needs before you'd sign it.

On trust: HIPAA-compliant safeguards, a BAA available for every customer, SOC 2 Type II audit in progress, and visit audio processed in memory then discarded, never archived. Details live on the [security page](/us/security/).

## When Jane is the better choice

Say it plainly: if you're an allied-health or wellness clinic whose week runs on online booking, packages and payments, insurance workflows, and a shared front desk, Jane is the better platform and you should stay. Its per-practitioner economics favor group clinics, its ecosystem is built around your patient flow, and its $15 scribe add-on means "we have AI notes now" is a checkbox Jane already ticks. Leaving Jane to get what Jane's add-on covers would be a bad trade, and we'd tell you so on a call.

The switch case is narrower and specific: the note is your bottleneck, you're a prescriber or bill diagnosis-coded claims, and documentation depth per visit, not front-desk breadth, is what you're actually shopping for. Two adjacent reads if that's you: our [SimplePractice alternatives breakdown](../simplepractice-alternatives/) covers the same platform-versus-documentation fork for therapy practices, [the PT scribe guide](../ai-scribe-for-physical-therapy/) speaks to allied clinicians with units and the 8-minute rule in play, and our [therapist EHR roundup](../best-ehr-for-therapists/) names honest picks across the category.

## How to run the comparison without burning a month

One week each, same visit mix. Week one: Jane as you run it today, with its AI Scribe add-on turned on for at least one practitioner ($15 says test it properly). Week two: your 7-day Patient Square trial on the same visit types. Count edits per draft, minutes from visit end to signed note, and how many after-hours charting sessions each week produced. Then read the [pricing page](/us/pricing/) with your practitioner count in hand. If you want the trial configured for an allied or prescriber workflow before you start, book a demo and we'll set it up with your templates.

---

## Tebra Alternatives: A Published Price, Scribe Included
https://patientsquare.com/us/blog/tebra-alternatives/
Published 2026-08-25 · Updated 2026-08-27 · Tags: alternatives, comparison, pricing, small-practice

Tebra (Kareo + PatientPop) is quote-only and stacks modules. The alternatives practices actually shortlist, with published prices and an ambient scribe.

Tebra is the company formed when Kareo merged with PatientPop in 2022. The old Kareo EHR now sells under the Tebra name, bundled with practice management and a patient-marketing suite (Engage). If you're comparing Kareo alternatives in 2026, you're comparing Tebra alternatives.

Tebra is the Kareo-plus-PatientPop platform, and its pricing is quote-only, so you can't compare it from a webpage. If that's what brought you here, the short version: most Tebra-class all-in-one systems are also demo-gated, so the field narrows to whoever publishes a number. Patient Square is one of them. It pairs an ambient AI scribe with a bundled AI EHR at $119 per clinician per month on annual billing, price on the [pricing page](/us/pricing/). Which alternative fits depends on whether you actually want Tebra's marketing suite or just a cleaner EHR you can budget.

> **Key takeaways**
>
> - Tebra is Kareo merged with PatientPop; pricing is custom-quote, not published, per EHR Source's 2026 review.
> - Reported Tebra EHR plus practice management runs roughly $80 to $100+ per provider per month, with the Engage marketing suite a separate $200 to $400 a month.
> - The stacking modules are the real gotcha: a low base rate plus setup and per-user fees plus a marketing suite is a very different budget than the headline number.
> - Patient Square Copilot is $119 per clinician per month on annual billing and bundles the ambient scribe with an AI EHR, price on the page.
> - Growth-focused cash-pay practices that want the patient-marketing tools should probably stay on Tebra: that suite is the reason to buy it.

## Why are practices shopping for Tebra alternatives?

Tebra earned its base. Kareo was one of the most widely adopted low-cost EHR and billing platforms for small practices, and the PatientPop merger added real patient-acquisition tooling on top. Nobody leaves because it's weak.

Two things send people looking. The first is pricing you can't see. Tebra's own pricing page walks you to a demo instead of a number, and independent reviews describe a custom-quote model. You can't budget a switch, or a renewal, from the website alone.

The second is the module stack. Tebra sells three pieces: clinical (the EHR), billing, and Engage (the marketing suite inherited from PatientPop). The base EHR is genuinely among the cheaper entry points. The complication reviewers keep raising is that the "affordable" framing gets shaky once Engage is on the bill. If you don't need patient marketing, you're pricing a bundle around a part you won't use. For the full module-by-module breakdown, our [Kareo (Tebra) pricing guide](../kareo-ehr-pricing/) has the numbers those reviews report.

Picture the practice this actually bites. Two providers, a family clinic, steady patient base, no marketing budget to speak of because word of mouth already fills the schedule. They signed on for a low base EHR rate. A year in, the invoice includes the marketing suite they barely touch, a per-user fee for the front desk, and a renewal number nobody can find on the website. Nothing went wrong, exactly. They just bought a growth platform when what they needed was a chart and a scribe. That mismatch, not a bad product, is what sends most of these searches our way.

## What does Tebra cost, and where does the number grow?

Straight answer: Tebra doesn't publish a rate card, so every figure is a third-party estimate. Per EHR Source's 2026 review, Tebra "does not publish transparent pricing and requires a custom quote."

Here's what those reviews report, and it's the shape of the bill, not just the base line, that matters:

| Piece | Reported cost | Note |
|---|---|---|
| EHR + practice management | ~$80–100+/provider/mo | The affordable base most reviews cite |
| Patient marketing suite (Engage) | ~$200–400/mo, billed separately | Inherited from PatientPop; the reason cost climbs |
| One-time setup | ~$500 | Per 2026 reviews |
| Annual per-user fee | ~$50/user | Per 2026 reviews |

None of those fees is unusual for the category. The point is they're easy to miss when you compare a base monthly rate against another vendor's all-in number. A $90 base looks great until you add setup, per-user, and a $300-a-month suite. We think a per-clinician price you can read without a sales call should be table stakes, and that opinion shapes the whole comparison below.

## The shortlist, compared

Every alternative here is a real product independent practices weigh against Tebra. We've marked which publish a price, because that's the split that matters when you're trying to budget.

| Tool | Published price | Ambient scribe | Billing / RCM depth | Best for |
|---|---|---|---|---|
| Tebra (Kareo) | No; demo-led | AI note generation listed; details quote-only | Deep, plus managed billing option | Growth / cash-pay practices wanting patient marketing |
| Practice Fusion | Yes, ~$149/provider/mo (published) | No native ambient scribe | Billing via partners | Practices wanting a free-to-low-cost certified EHR |
| Charm EHR | Yes; free tier plus paid add-ons | No native ambient scribe | Add-on RCM | Small / solo practices watching every dollar |
| Patient Square Copilot | Yes, $119/mo annual | Bundled in every plan | None; no claims engine | AI clinical platform for practices wanting Patient Square EHR or an existing-EHR path at a clear price |

### Practice Fusion

The classic Tebra alternative for practices that want a certified EHR without the marketing bundle. It publishes a per-provider price and is a known quantity for small independent clinics. The trade: it's an EHR, not an ambient documentation tool, so the after-hours charting problem stays with you. Our [Practice Fusion alternatives](../practice-fusion-alternatives/) piece covers the upgrade path in detail.

### Charm EHR

Worth a look if cost is the whole story. Charm publishes a free tier and layers paid features on top, which suits a solo practice testing the water. The catch is the total once the add-ons you actually need are switched on, and there's no native ambient scribe. Our [Charm EHR pricing](../charm-ehr-pricing/) breakdown walks the real all-in math.

### Patient Square

Our lane is the documentation and the record, priced in the open. The AI Medical Scribe by Patient Square is one module inside Practice Copilot, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The Copilot plan at $119 per clinician per month on annual billing bundles that scribe with the AI Copilot EHR and scheduling; the Assist plan at $79 is the scribe essentials without the EHR. Unlimited visits and notes on every plan, no per-note metering. Visit audio is processed in memory and discarded once the note drafts. Safeguards are HIPAA compliant with BAAs available, and our SOC 2 Type II audit is in progress. Notes leave anytime via EHR-ready export (PDF · HL7 · FHIR).

What we don't have: a revenue-cycle billing engine or a patient-marketing suite. If claims processing runs your practice, keep your billing tool and use us for the clinical side, or don't use us at all.

## When Tebra is still the right call

Stay on Tebra if patient growth is the point. A cash-pay or hybrid practice that wants the online-presence, reputation, and marketing tools from Engage is buying something the documentation-first options don't replace. That suite isn't padding for a practice trying to fill its schedule; it's the reason to be there.

Stay if you want billing, EHR, and marketing under one vendor and one login, and you've priced the whole bundle honestly. And stay if you're mid-contract, since the exit math rarely favors breaking terms early. You can still fix the note burden alongside it: an ambient scribe runs next to any system, and finished notes move over with EHR-ready export. Our guide to [how to evaluate an AI medical scribe](../ai-scribe-for-medical-notes/) lists the questions that separate the field.

## How to decide inside one week

1. Get the Tebra quote anyway, with every module and fee itemized. You need the real all-in number, including Engage and setup, to compare anything.
2. Decide whether you actually want the marketing suite. If yes, Tebra's bundle has a genuine case. If no, you're paying for a part you won't use.
3. Line up the published-price options for your provider count in one spreadsheet column, all-in.
4. Run an ambient scribe on two real clinic days, including your busiest, so you're comparing the note experience, not the demo.
5. Check the export path before you sign anything, ours included. A system you can leave cleanly is one you can trust.

The plan-by-plan breakdown is on the [pricing page](/us/pricing/), and a short demo will show you a finished note from a real conversation before you commit.

## Frequently asked questions

The FAQ above covers the recurring ones: what Tebra is, why practices switch, the AI-scribe question, the cheapest real-price alternative, and how the total compares to a bundled AI EHR. For the module-level cost detail, our [Kareo (Tebra) pricing guide](../kareo-ehr-pricing/) has the third-party figures.

---

## WebPT Alternatives: Ambient Notes, Published Price
https://patientsquare.com/us/blog/webpt-alternatives/
Published 2026-08-25 · Updated 2026-08-27 · Tags: alternatives, physical-therapy, comparison, pricing

WebPT is PT-built and quote-only. The alternatives rehab clinics shortlist, with ambient documentation, the 8-minute-rule reality, and prices on the page.

WebPT's pricing page lists three plans, Starter, Enhanced, and Ultimate, with no dollar amounts; it's quote-only, priced per provider per month or per visit. Third-party listings commonly cite a starting point near $99 a month, with billing (Therabill) and patient engagement (Keet) sold as separate add-ons. Confirm your number in a demo.

WebPT is a physical-therapy-built EMR, and its pricing is quote-only, so you can't compare it from a webpage. If that's what sent you here, the short version: WebPT now ships its own AI documentation (voice-to-text, templates, compliance checks), so the real question isn't "does it have AI" but "do you want AI-assisted structured entry or an ambient scribe that writes the note from the conversation." Jane is the usual published-price PT-adjacent pick, and Patient Square pairs an ambient scribe with a bundled AI EHR at $119 per clinician per month, price on the [pricing page](/us/pricing/). Which fits depends on whether your practice runs on PT-specific billing or on getting notes done by the time you leave.

> **Key takeaways**
>
> - WebPT's pricing page lists Starter, Enhanced, and Ultimate with no dollar amounts; it's quote-only, and billing (Therabill) and engagement (Keet) are separate add-ons.
> - WebPT ships AI documentation: voice-to-text, smart note templates, and real-time compliance checking. That's AI-assisted entry inside a PT EMR, not ambient capture of the whole visit.
> - An ambient scribe drafts the note from what you narrate; under the CMS 8-minute rule, the treatment-minute math that drives your units stays yours.
> - Patient Square Copilot is $119 per clinician per month on annual billing, ambient scribe plus AI EHR, price on the page.
> - Insurance-heavy PT practices that lean on therapy-cap tracking and PT-specific claims tooling should probably stay on a PT-built system: that depth is real.

## Why are PT clinics shopping for WebPT alternatives?

WebPT is the default name in outpatient rehab for good reasons: PT-specific documentation, compliance tooling built for therapy audits, a huge install base, and integrations across the rehab stack. Clinics don't leave because it's weak.

Two frictions send people looking. The first is pricing you can't see. WebPT's pricing page routes you to a demo instead of a number, and billing and patient engagement are separate purchases. You can't budget a switch, or a renewal, from the site alone.

The second is the documentation experience. WebPT's AI documentation is real, and it's improved fast, but it's built around structured entry: you dictate or template, and the system formats and checks it. Some clinicians want the other model, where you just run the session and a scribe drafts the whole note from the conversation. That's a preference, not a defect, and it's worth being honest about which one you're actually after.

## WebPT's AI versus an ambient scribe: what's the real difference?

This is the crux, so let's be precise instead of pretending WebPT has nothing.

WebPT publishes AI documentation tools: voice-to-text that turns speech into text, smart note templates that format future notes to match a structure you set, and real-time compliance support that flags gaps as you write. All of that speeds up entering a note. You're still the one driving the note's creation, faster than before. If dictation is the model you're weighing, our piece on [AI scribe vs dictation software](../ai-scribe-vs-dictation-software/) covers where each actually cuts charting time.

An ambient scribe changes who writes the first draft. You run the session the way you already coach the patient, out loud, and the scribe listens and drafts subjective, objective, assessment, and plan from what was said in the room. Then you read it and sign. The writing moves off your plate; your job becomes review, not authoring.

| Capability | WebPT AI documentation | Ambient scribe (Patient Square) |
|---|---|---|
| How the note starts | You dictate or template; AI formats | Scribe drafts from the spoken visit |
| Your job after | Fill, correct, confirm compliance | Review and sign a full draft |
| Voice input | Voice-to-text dictation | Ambient capture, no dictation |
| PT-specific compliance flags | Yes, built in | No; you voice medical-necessity yourself |
| Published price | No; quote-only | Yes; $79–$199/clinician/mo |

Neither model does your units. That part comes next.

## The 8-minute rule stays yours

Say your Thursday board has sixteen patients: a post-op knee, a rotator cuff, two low-back cases back to back, a balance eval squeezed in. Between each one you owe a note that captures the exercises, the manual work, the cues, the progress toward goals, and the treatment minutes that decide your units.

The AI Medical Scribe by Patient Square is one module inside Practice Copilot, our AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For PT, that means the interventions and reasoning you voice land in the draft. What it does not do is your units. Under the CMS 8-minute rule, billable units come from documented one-on-one treatment minutes for each timed CPT code, and that math is yours to track and confirm. Read the draft, check the minutes against what you did, and sign. Our [AI scribe for physical therapy](../ai-scribe-for-physical-therapy/) guide covers the narration habit and the medical-necessity language in depth, and if you'd rather watch it run on a real eval, book a short demo.

## The shortlist, compared

| Tool | Published price | Documentation model | PT billing depth | Best for |
|---|---|---|---|---|
| WebPT | No; demo-led | AI-assisted entry: voice-to-text, templates, compliance | Deep, PT-specific, therapy-cap aware | Insurance-heavy rehab practices |
| Jane | Yes, tiers from ~$54/mo (shown in CAD) | Charting plus AI scribe add-on (~$15/practitioner) | General allied-health, not PT-deep | Multidisciplinary clinics: PT plus chiro, massage |
| Prompt / rehab-specific EMRs | Mostly quote-only | Structured PT documentation | Deep, rehab-built | Larger rehab groups wanting one PT platform |
| Patient Square Copilot | Yes, $119/mo annual | Ambient scribe, review and sign | None; no claims engine | Cash-pay / hybrid clinics wanting notes done fast |

### Jane

Jane is what multidisciplinary clinics keep choosing: clean scheduling and booking, plus charting a PT, chiro, and massage therapist can share. Pricing is published, which we respect, with base tiers from about $54 a month (Jane's page displays CAD) and an unlimited AI scribe add-on around $15 per practitioner. The trade: Jane is allied-health-general, so PT-specific compliance and therapy billing depth aren't the strength, and the scribe is an add-on rather than the core.

### PT-specific EMRs (Prompt and similar)

If you want a single rehab-built platform with deep PT billing, scheduling, and analytics, the rehab-specialist EMRs compete directly with WebPT on that ground. Most are quote-only, so put them in the same demo-gathering pile and compare all-in numbers for your provider count.

### Patient Square

Our lane is the note and the record, priced in the open. The Copilot plan at $119 per clinician per month on annual billing bundles the ambient scribe with the AI Copilot EHR and scheduling; the Assist plan at $79 is the scribe essentials without the EHR. Unlimited visits and notes, no per-note metering. Visit audio is processed in memory and discarded once the note drafts. Safeguards are HIPAA compliant with BAAs available, and our SOC 2 Type II audit is in progress. Notes leave anytime via EHR-ready export (PDF · HL7 · FHIR).

What we don't have: PT-specific billing, therapy-cap tracking, or a rehab flowsheet library. We think a per-clinician price you can read without a sales call should be table stakes, and if PT billing runs your practice, keep a PT-built tool and use us for the clinical documentation.

## When WebPT is still the right call

Stay on WebPT if therapy billing and compliance are the center of gravity. An insurance-heavy outpatient practice that lives on therapy-cap tracking, KX modifiers, and PT-specific audit defense gets real value from a system built for exactly that, and the documentation-first options don't replace it. Stay if your team is trained on WebPT's flowsheets and your notes already close on time. And stay if the AI-assisted entry model suits how you like to chart; some clinicians genuinely prefer dictate-and-template to ambient. Fix the after-hours charting alongside it if that's the pain: an ambient scribe runs next to WebPT, and finished notes move over with EHR-ready export.

## How to decide inside one week

1. Get the WebPT quote itemized, with Therabill and Keet if you'd use them. You need the real all-in number. For market context on what a scribe alone should run, see our [AI medical scribe pricing](../ai-medical-scribe-pricing/) guide.
2. Name your actual bottleneck. If denials and therapy-cap tracking are the problem, weight PT billing depth. If it's 6pm charting, weight the documentation model.
3. Try both note experiences on real visits: WebPT's AI entry and an ambient scribe on your busiest day.
4. Confirm the 8-minute-rule workflow. Whatever tool drafts the note, you're confirming the minutes; make sure that step is fast.
5. Check the export path before you sign anything, ours included.

The plan-by-plan breakdown is on the [pricing page](/us/pricing/), and a short demo will show you a finished PT note from a real conversation before you commit.

## Frequently asked questions

The FAQ above covers the recurring ones: what WebPT costs, its AI documentation versus an ambient scribe, the 8-minute rule, and the cheapest published-price alternative. For the PT-specific scribe habit, see [AI scribe for physical therapy](../ai-scribe-for-physical-therapy/).

---

## ChiroTouch Alternatives: Flat Price, Ambient SOAP Notes
https://patientsquare.com/us/blog/chirotouch-alternatives/
Published 2026-08-23 · Updated 2026-08-27 · Tags: alternatives, chiropractic, comparison, pricing

ChiroTouch went quote-only. Here are the alternatives chiropractors actually shortlist, with published prices and ambient SOAP notes for high-volume days.

ChiroTouch's own pricing page lists three plans, Start, Grow, and Scale, with no dollar amounts; you book a demo to get a number. Third-party guides such as Software Finder cite $159 a month for the older Core plan and $299 for Advanced. Treat those as estimates, not quotes.

ChiroTouch stopped publishing prices. Its pricing page now lists three plans, Start, Grow, and Scale, and each one ends in a demo booking instead of a number. If that's what sent you here, the short version: ChiroFusion and Jane are the usual replacements with published pricing, zHealth pitches AI-heavy chiro workflows, and Patient Square pairs an ambient AI scribe with a bundled AI EHR at $119 per clinician per month on annual billing, price on the page. Which one fits depends on whether your bottleneck is billing or the SOAP-note stack at 7pm. Every number we charge is on the [pricing page](/us/pricing/), readable before any call.

> **Key takeaways**
>
> - ChiroTouch's own pricing page lists Start, Grow, and Scale with no dollar amounts as of July 2026; third-party guides cite $159 to $299 a month for the older Core and Advanced plans.
> - ChiroFusion runs about $129 a month for a single provider per third-party comparisons. Jane publishes tiers from about $54 a month plus a $15 AI scribe add-on.
> - Patient Square Copilot is $119 per clinician per month on annual billing and bundles the ambient scribe with an AI EHR, so the note and the record live in one plan.
> - On a 45-visit adjustment day, four minutes of typing per note is three hours of charting. That arithmetic, not a feature list, is what usually forces the switch.
> - Insurance-heavy practices with a dedicated biller often should stay: ChiroTouch's chiro-specific claims tooling is the real thing.

## Why are chiropractors shopping for alternatives at all?

ChiroTouch has been the default name in chiropractic software for a long time, and it earned that. Purpose-built SOAP workflows, chiro-specific billing, an ecosystem of integrations, a huge install base. Nobody leaves because it's obscure.

Two frictions send people here. The first is pricing you can't see. The current plans are demo-gated, and review-site commentary on Capterra mentions add-on fees and contract terms as recurring complaints. Whether that matches your experience is your call; the point is you can't budget a switch, or a renewal, from the website alone.

The second friction is the one we care about: the notes. ChiroTouch's macros and templates are fast once tuned, but they're still keyboard work, per patient, every patient. A high-volume adjustment practice doesn't have a documentation problem at visit 5. It has one at visit 38.

## What does ChiroTouch cost right now?

Straight answer: the company doesn't say publicly. As of this writing, the Start, Grow, and Scale plans carry no prices. Software Finder's profile, updated June 2026, lists the older plan names at $159 a month for Core and $299 for Advanced, and those figures still circulate as the reference points. They're third-party estimates for plans ChiroTouch no longer advertises, so treat them as a floor for your quote conversation, not a fact about your invoice.

We won't pretend that's unusual. Quote-only pricing is half the medical-software market. But if you're comparing a known $119 against a "book a demo," one of those numbers you can put in a spreadsheet today. For what a scribe itself should cost, our [AI scribe pricing guide](../ai-medical-scribe-pricing/) has the market ranges.

## The 45-visit day is the real problem

Here's the scene that fills our demo calls. Tuesday, 43 patients between 8am and 6pm, mostly adjustments, a few new-patient exams. Great clinical day. Then the clock hits 7:10pm and there are 19 notes still open.

Run the arithmetic on your own numbers. These per-note times are assumptions, so replace them with yours; the multiplication is the point.

| How you chart | Per-note time (assumed) | 45-visit day total |
|---|---|---|
| Typed after hours, from memory | 4 minutes | 3 hours |
| Macros and templates in your PM | 1 to 2 minutes | 45 to 90 minutes |
| Ambient scribe, review and sign | 30 to 60 seconds of review | 25 to 45 minutes |

Templates got the industry from three hours down to ninety minutes, and that was worth it. An ambient scribe attacks the remaining half: it writes the draft from what was said in the room, and your job shrinks to reading and signing.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For chiropractic that means the segments you call out loud land in the draft, along with your ROM findings and whatever plan phase you told the patient. The habit that makes it work, plus the Medicare medical-necessity angle, is covered in our [chiropractic scribe guide](../ai-scribe-for-chiropractic/). If you'd rather just watch it run on an adjustment visit, book a short demo.

## The shortlist, compared

| Tool | Published price | Ambient scribe | Chiro billing depth | Best for |
|---|---|---|---|---|
| ChiroTouch | No; demo-led | Rheo AI charting listed on plans | Deep, chiro-specific, strongest at higher tiers | Insurance-heavy multi-provider practices |
| ChiroFusion | ~$129/mo single provider, per Software Finder | Not the pitch; template speed is | Chiro-only, built-in claims tooling | Budget-minded solo DCs staying chiro-specific |
| Jane | Yes, tiers from ~$54/mo (shown in CAD) | AI scribe add-on, $15/practitioner | General allied-health billing, not chiro-deep | Multidisciplinary clinics: chiro plus massage, PT |
| Patient Square Copilot | Yes, $119/mo annual | Bundled in every plan | None; no claims engine | AI clinical platform for cash-pay or hybrid practices; Patient Square EHR or existing-EHR path |

### ChiroFusion

The budget chiro-specific pick. Software Finder's comparison puts it around $129 a month for a single provider, and its pitch is speed inside a chiropractic-only workflow, including integrated claims handling. If you want to stay in a chiro-built system and spend less, this is the first quote to get. It competes on template efficiency rather than ambient documentation, so the keyboard time per note stays with you.

### Jane

Jane is what multidisciplinary clinics keep choosing, and the affection is earned: clean scheduling and online booking, plus charting that a DC and a massage therapist can share in one system. Pricing is published, which we respect, with base tiers from about $54 a month (Jane's pricing page displays CAD) and an unlimited AI scribe add-on at $15 per practitioner. The trade: Jane is allied-health-general, so chiro-specific billing depth isn't the strength, and the scribe is an add-on rather than the core of the product.

### zHealth

Worth a look if patient recall and growth automation are your priorities; it markets AI-assisted charting and recall workflows built for chiropractors. We couldn't reach a published price when we checked, so put it in the same quote-gathering pile as ChiroTouch.

### Patient Square

Our lane is the documentation and the record, priced in the open. The Copilot plan at $119 per clinician per month on annual billing bundles the ambient scribe with the AI Copilot EHR and scheduling; the Assist plan at $79 is the scribe essentials without the EHR. Unlimited visits and notes on every plan, no per-note metering. Visit audio is processed in memory and discarded once the note drafts, safeguards are HIPAA compliant with BAAs available, and our SOC 2 Type II audit is in progress. Notes leave whenever you want via EHR-ready export (PDF · HL7 · FHIR).

What we don't have: a chiropractic claims engine. If insurance billing runs your practice, keep your billing tool and use us for the clinical side, or don't use us at all. We think a per-clinician price you can read without a sales call should be table stakes in this market, and that opinion shapes everything above.

## When ChiroTouch is still the right call

Stay if billing is the center of gravity. A multi-provider, insurance-heavy practice with a dedicated front office gets real value from chiro-specific claims tooling, and none of the documentation-first options replace that. Stay if your macros are tuned to the second and your notes already close by 6pm; switching would be motion without progress. And stay if you're mid-contract, since the exit math rarely favors breaking terms early. Fix the note burden alongside it instead: an ambient scribe runs next to any system, and [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) lists the nine questions that separate the field.

## How to decide inside one week

1. Get the ChiroTouch quote anyway. You need the real number, including any add-ons, to compare anything.
2. Price your actual bottleneck. If claims denials are eating revenue, weight billing depth. If it's 90 minutes of nightly charting, weight the scribe.
3. Run an ambient scribe on two real clinic days, including your busiest. Our 7-day trial exists so you can test it on a genuine 45-visit Tuesday, not a demo script.
4. Check the export path before you sign anything, ours included. A system you can leave cleanly is a system you can trust.
5. Compare all-in monthly cost for your provider count, side by side, in one spreadsheet column.

The plan-by-plan breakdown is on the [pricing page](/us/pricing/), and a 15-minute demo will show you a finished chiropractic SOAP note from a real conversation before you commit to anything.

## Frequently asked questions

The FAQ above covers the recurring ones: what ChiroTouch costs, the Rheo AI question, the cheapest alternatives, and how an ambient scribe handles adjustment notes. For the wider market, our [scribe cost comparison](../ai-medical-scribe-cost-comparison/) lays out 2026 prices across vendors.

---

## InSync EHR Alternatives: Start This Week, No Project
https://patientsquare.com/us/blog/insync-ehr-alternatives/
Published 2026-08-22 · Updated 2026-08-27 · Tags: alternatives, behavioral-health, insync-ehr, comparison

Qualifacts InSync is a configurable behavioral-health EHR with a real implementation cycle. Alternatives that start this week, plus a bundled AI EHR from $119.

InSync is a behavioral-health and mental-health EHR from Qualifacts, which also runs the CareLogic and Credible platforms. InSync targets small-to-mid-size behavioral-health practices with configurable forms, encounter notes, scheduling, and revenue-cycle tooling. It's the more streamlined, faster-to-implement option in the Qualifacts lineup compared with the enterprise platforms.

If you're weighing InSync EHR alternatives, the deciding question is usually time-to-live. Qualifacts InSync is a configurable behavioral-health EHR with a real implementation cycle: configuration, training, onboarding. That depth is right for some practices and overkill for others. If you mostly want notes drafted and a record system without a large configuration project, Patient Square's Copilot plan is **$119 per provider per month** on annual billing with an ambient scribe bundled in. You can book a demo to request an assisted 7-day trial and evaluate the workflow before committing.

To be fair up front: InSync's configurability is a genuine strength, and Patient Square doesn't try to match it. This page is about which trade fits your practice.

> **Key takeaways**
>
> - InSync is Qualifacts' small-to-mid-size behavioral-health EHR, built to be configured to your workflows.
> - Third-party trackers list InSync starting around $94 per user per month; Qualifacts publishes no standard rate.
> - InSync ships with an implementation project: configuration, training, onboarding. That's a strength for complex practices, a cost for simple ones.
> - Patient Square Copilot is $119/provider monthly (annual), with an ambient scribe, a bundled AI EHR, and an assisted evaluation path.
> - Stay with InSync if you need deep behavioral-health configuration and integrated RCM.

## What is InSync EHR, and what does it cost?

InSync is the behavioral-health and mental-health EHR from Qualifacts, the company behind CareLogic and Credible. In the Qualifacts lineup, InSync is the streamlined, faster-to-implement option aimed at small-to-mid-size practices, with configurable forms, encounter notes, scheduling, and revenue-cycle tooling.

On price, Qualifacts doesn't publish a standard public number. Third-party trackers like Capterra list InSync starting around **$94 per user per month**, with the real figure tuned to your module mix and practice size. Treat that as a directional anchor, not a quote. Your number lands after a sales conversation.

| InSync (Qualifacts) | Directional figure |
|---|---|
| Published starting price | ~$94/user/mo (third-party estimate) |
| Pricing model | Customized by module mix and practice size |
| Implementation | Configuration + training + onboarding project |
| Public price | No |

If you'd rather skip the quote-and-configure cycle, [see what a flat published bundle covers](/us/) and compare it against your InSync proposal.

## The implementation project is the real trade

The setup is the part InSync buyers underweight. Qualifacts runs a proper implementation, with its team configuring the system to your workflows and delivering in-person and remote training. Reviewers describe the onboarding as thorough and well-organized. That's a real strength for a practice with specific forms, complex billing, and regulated reporting.

It's also weeks of work before you document your first note. For a solo prescriber or a small talk-therapy group, that project can outweigh the payoff. You wanted notes to stop eating your evenings, and you're four weeks into a configuration call schedule.

A lighter implementation inverts that. You confirm the workflow, get consent, and evaluate representative visits through an assisted setup. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. Book a demo and ask the team to map an evaluation to your visit type.

## InSync vs a flat AI bundle: what each is for

Compare like for like, not headline for headline.

| | InSync (Qualifacts) | Patient Square Copilot |
|---|---|---|
| Starting price | ~$94/user/mo (third-party) | $119/provider/mo (annual) |
| Ambient scribe | Not the core pitch | Bundled |
| Evaluation setup | Implementation project | Assisted 7-day trial |
| Custom forms / RCM depth | Deep, configurable | Not a billing engine |
| Published price | No | Yes |
| Free trial | Demo-led | 7-day trial |

Read that straight. InSync is a configurable behavioral-health EHR with integrated billing; Patient Square isn't. If custom forms and revenue-cycle depth are the center of your evaluation, InSync's configurability is a real reason to pick it. What Patient Square gives you instead is one predictable bill for the two things most practices touch every day: drafting the note and keeping the record. Our [best EHR for therapists](../best-ehr-for-therapists/) roundup lines up more of the behavioral-health field if you want the wider view.

## What an ambient scribe changes on a full day

The reason time-to-live matters is that documentation load is a daily tax, and every week you wait, you keep paying it. What the ambient path changes:

- **The note drafts from the visit.** Ambient capture during the session, structured note about two minutes after you finish.
- **Unlimited notes, no per-session meter.** A 14-patient Tuesday costs the same as a light Friday.
- **A prescription draft** for prescribers, reviewed and signed by you. A draft, not automated pharmacy transmission.
- **Audio is never stored.** Processed in memory and discarded once the note drafts.
- **EHR-ready export (PDF, HL7, FHIR)** on every plan, so the note leaves in a format your record system accepts. That's an export, not a certified two-way interface.

That export line matters for anyone leaving a configured EHR. You want to know the note travels before you commit. Our security posture, encryption, access, and audit status, is on the [security page](/us/security/).

## The hidden cost of a configuration project

Sticker price gets the attention. Time-to-value is the number that actually hits your practice, and it's the one buyers skip.

A configured EHR like InSync doesn't run the day you sign. Someone maps your forms, your billing rules, your reporting requirements. Your staff sits through training sessions. You test workflows before go-live. That's weeks, sometimes a couple of months, and during that stretch you're still charting the old way while paying for the new tool. For a state-funded agency with regulated reporting, that setup is worth it, because the configuration is the product. For a small prescriber group, it's weeks of overhead buying you flexibility you may never use.

There's a softer cost too: attention. The clinician driving the implementation is on config calls instead of seeing patients or, frankly, resting. We've watched practices lose their momentum in month two of a setup project, when the novelty wears off and the forms still aren't right. A short assisted trial can reduce that commitment. You evaluate representative visits for a week, and if the note holds, you keep going. If it doesn't, you stop before a quarter-long rollout. That asymmetry is the real reason time-to-live belongs in your evaluation, not just the monthly rate.

## When InSync EHR is the better choice

The honest verdict. Pick or keep InSync if you need deep behavioral-health configuration: custom forms, tailored encounter notes, integrated billing and RCM, and the compliance-heavy reporting that agency and larger group settings live on. If your workflows are specific and your reporting is regulated, that configurability earns its implementation cost, and a flat AI bundle isn't built to replace it. We'd tell a state-funded behavioral-health agency to stay on a platform like InSync, not switch to us.

Pick a flat AI bundle if your day is mostly visits and notes, you want to start this week, and you'd rather have one published price than a configured quote. That describes a lot of independent prescribers and small talk-therapy groups.

## How to test both in a week

You can settle this without a month of demos:

1. Get the InSync quote in writing, including implementation, training, and any per-module fees.
2. List the three workflows you actually can't live without. If they're custom forms and RCM, InSync's project is worth it. If they're notes and a record, it may not be.
3. Request the flat bundle's assisted 7-day trial and agree on a representative evaluation plan.
4. Check the export format and the finished note quality against what you'd have written yourself.
5. Compare total first-year cost: quote plus implementation for InSync, versus a flat annual bundle at $119 per provider.

For the migration logistics, our [AI scribe migration checklist](../switch-ai-scribe-migration-checklist/) covers the clinic-day plan, and the [pricing page](/us/pricing/) lists the full ladder. Book a short demo to see the note on your own visit type, then request a 7-day trial. If your real bottleneck is the note-writing and not the form builder, compare the tools during a real clinic week.

---

## KiviHealth Alternatives in India: An Honest 2026 Look
https://patientsquare.com/in/blog/kivihealth-alternatives-india/
Published 2026-08-22 · Tags: kivihealth, alternatives, clinic-software, india

KiviHealth lists ₹12,000 + GST a year. What the Jio-branded clinic EMR covers, where the note gap sits, and an ambient AI option from ₹1,599 a month.

KiviHealth's pricing page lists a standard package at ₹12,000 plus GST for one year, with prepay tiers of ₹17,000 for two years rising to ₹75,000 for ten. A 7-day free trial is included. The page doesn't state whether that price covers one doctor or the whole clinic, so confirm before signing.

Doctors hunting for a KiviHealth alternative usually aren't running from the bill. At ₹12,000 plus GST a year on the published standard package, the Jio-branded EMR is about as cheap as clinic software gets in India. The real complaint is the typing. KiviHealth stores the note you write; it doesn't write it. If that's your itch, the alternative to shortlist is an ambient AI platform, and that's what Patient Square is: the note drafts itself while you consult, from ₹1,599 per clinician a month on annual billing, plus 18% GST. If budget is the whole decision, KiviHealth already wins, and we'll say that plainly below. The fastest way to test the difference is to book a demo and watch one of your own consults become a note.

> **Key takeaways**
>
> - KiviHealth's published price is ₹12,000 + GST a year, with prepay tiers stretching to 10 years for ₹75,000. Cheap is its strong suit.
> - Third-party listings put 5,000+ doctors on the platform, and it sells under the Jio brand today.
> - The gap is documentation. In an OPD averaging about 2 minutes per consult, a form-filling EMR still leaves the note to you.
> - Patient Square starts at ₹1,599/month per clinician (annual, ex-GST); the ₹2,399 Copilot plan bundles an AI EHR.
> - Already decided to leave? A separate migration guide covers the mechanics. This page is for weighing the options.

## What KiviHealth is in 2026

KiviHealth started in Ahmedabad and now sells as Jio KiviHealth; company profiles list it as acquired by Reliance, and its social channels carry the Jio name. Third-party listings describe more than 5,000 doctors using it across specialties. Whatever the exact figure, the brand recognition among Indian doctors is real.

The pricing page (fetched July 2026) is refreshingly public. A standard package runs ₹12,000 plus GST for one year, and prepay tiers reward commitment: ₹17,000 for two years, ₹25,000 for three, ₹38,000 for five, ₹60,000 for seven, and ₹75,000 for ten. There's a 7-day free trial. Features named on that page include a patient CRM, EHR, medical history tracking, financial management, SMS and email tools, inventory and vendor management, camp software, mobile apps, and an offline mode.

One thing the page doesn't spell out: whether ₹12,000 covers one doctor or the whole clinic. Ask on the call, and get the answer in writing.

## Cheap isn't the question. Typed is.

Here's the honest problem with every form-filling EMR at OPD speed, KiviHealth included. Indian consultations average about two minutes, per a 67-country BMJ Open review, among the shortest in the world. Picture a Rajkot GP on a Monday: 60 patients cleared by 1pm, the EMR open in a second browser tab, each note compressed to a single line because the queue doesn't pause for paperwork. The software isn't slow. The typing is.

Thin notes cost you later, too. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A register full of one-liners is weak armour if a dispute ever lands on your desk.

No EMR fixes this, at any price, because the constraint isn't storage. It's authorship. Someone still has to write the note, and in a two-minute consult, nobody does.

## KiviHealth vs Patient Square, side by side

| | KiviHealth (Jio) | Patient Square (Practice Copilot) |
|---|---|---|
| Built as | Clinic management EMR with patient app | AI documentation platform with bundled EHR |
| The note | You type it, or you skip it | Ambient AI drafts the SOAP note, ICD-10 suggestions, and an eRx draft |
| Published price | ₹12,000 + GST/year standard package | ₹1,599/mo annual entry; ₹2,399/mo with the bundled AI EHR (ex-GST) |
| Multi-year prepay | Tiers from 2 to 10 years (₹17,000 to ₹75,000) | Annual or monthly; no decade-long lock-in |
| Consult languages | Not specified on the pricing page | English, Hindi + 20 more, code-mixed; notes in clinical English |
| Offline | Offline mode listed | Offline encrypted capture for low-signal clinics |
| Trial | 7 days | 7 days |

If the right-hand column reads like the missing half of your day, book a demo and put it against a real OPD list, not a scripted one.

## The 10-year prepay question

KiviHealth's ladder rewards long commitments. ₹75,000 for ten years works out to ₹625 a month, genuine value if the product still fits your practice in 2036. We think a 10-year prepay on clinic software in 2026 is a bet nobody needs to place. Not because KiviHealth is going anywhere; Jio's backing argues the opposite. But clinical software is changing shape quickly right now, and what "documentation" means in three years probably won't look like a form. Multi-year discounts are honest price engineering. Just price the lock-in alongside the savings.

## When KiviHealth is the better choice

Pick KiviHealth if budget is the deciding constraint. Near ₹1,000 a month for registration, records, billing, SMS reminders, and inventory undercuts most of the market, and the offline mode matters in low-connectivity towns. If you run community health camps, camp software is a genuinely uncommon inclusion. And if your notes are already fine, because you type fast or an assistant does the entry, the documentation argument simply doesn't apply to you. Don't pay for a problem you don't have.

Pick an ambient AI platform when the note is the pain: when charting bleeds into the evening, when records are thin, or when you'd rather look at the patient than the screen.

## What the extra ₹600 a month buys

Entry against entry: KiviHealth works out near ₹1,000 a month, Patient Square's Assist plan is ₹1,599 a month on annual billing (₹1,999 billed monthly), ex-GST. Add 18% GST and Assist lands at about ₹1,887. The Copilot plan at ₹2,399 ex-GST adds the bundled AI Copilot EHR and WhatsApp messaging, so the record system and the documentation engine come from one place.

What the money buys is the writing. The AI Medical Scribe by Patient Square is one module of Practice Copilot: it captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It hears the consult the way it actually happens, in Hindi, Hinglish, or 20+ Indian languages, and the note comes back in clean clinical English. Audio is processed in memory and discarded once the note drafts; no recording sits on a server. Prescriptions stay drafts you review and sign. Every plan includes unlimited visits and notes with no per-note metering, plus EHR-ready export (PDF · HL7 · FHIR). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On compliance: data is handled to DPDP Act 2023 standards, and a SOC 2 Type II audit is in progress. ABDM integration is on our roadmap, not live, and we won't pretend otherwise; ask KiviHealth the same milestone question and compare straight answers. The full ladder sits on the [India pricing page](/in/pricing/), and the 7-day trial means you can run it on a real clinic day before any money moves.

## Evaluate first, migrate second

This page is for deciding whether to move at all. If you've already decided, the practical half lives in the [switching from KiviHealth guide](../switch-from-kivihealth-india/): exporting your patient data, keeping continuity, and surviving the first OPD week on a new system. If you want a wider field than a one-on-one comparison, the [India clinic software scorecard](../best-clinic-management-software-india/) ranks the main options on documentation, pricing, and lock-in, and the [HealthPlix comparison](../healthplix-alternatives-india/) covers the other big specialty-EMR brand most KiviHealth shoppers also check.

The whole decision compresses to one question: is documentation your bottleneck or not? If not, KiviHealth's price is hard to argue with, and you should probably stay. If it is, no form-filling EMR fixes it at any price. Book a demo and decide with your own patients, not our copy.

---

## Chartnote Alternatives: When Dictation Credits Run Out
https://patientsquare.com/us/blog/chartnote-alternatives/
Published 2026-08-21 · Updated 2026-08-27 · Tags: chartnote, alternatives, ai-scribe, medical-dictation

Chartnote's free dictation and dot phrases work until volume grows. The credit math, what ambient capture changes, and when to stay put.

There is a genuinely free Basic tier, yes. Third-party writeups list it at roughly 15 minutes of dictation and a small monthly batch of AI note credits, with template caps. It's real, but it's sized for occasional use, not a full clinic day. Chartnote's own plans page is the source of truth for current limits.

The usual Chartnote alternative is an ambient AI scribe: a tool that listens to the visit itself instead of waiting for you to dictate. Chartnote is a dictation-and-dot-phrase tool with metered AI note credits layered on top. If you're bumping into its monthly minutes or credit caps, an unlimited ambient scribe such as the AI Medical Scribe by Patient Square is the standard next step.

That's the short version. The longer version is about a real distinction in how the note gets made, and it's worth getting right before you move, because Chartnote is a better deal than most people leaving it admit. If you'd rather see the ambient side running on one of your own visit types first, book a short demo and bring a messy one.

> **Key takeaways**
>
> - Chartnote is dictation plus dot phrases, with AI scribe credits metered by tier. Third-party listings put its free plan around 15 minutes of dictation a month.
> - A clinician seeing 15 patients a day generates roughly 300 notes a month. Credit-metered plans make you ration which visits get help.
> - Ambient capture removes the retelling step: the visit conversation is the input, and a structured SOAP draft lands about 2 minutes after the visit ends.
> - Practice Copilot starts at $79/clinician/month (annual Assist plan), unlimited notes, no credits. Chartnote stays the better fit for low-volume and genuinely-free use.

## Chartnote is a dictation tool with a scribe bolted on

Chartnote's own positioning is "AI Scribe, Medical Dictation, Snippets," and the order matters. The core product is medical dictation (you speak, it transcribes into the note field) plus smart snippets, its version of dot phrases that expand a short abbreviation into a formatted block. A Chrome extension lets you dictate straight into any web-based EHR, which is genuinely useful and the reason a lot of clinicians install it in the first place.

The AI scribe part is newer and metered. As of this writing, Chartnote's plans page gates AI note generation behind monthly credits on most tiers. A third-party pricing breakdown from March 2025 listed the ladder at a free Basic tier (about 15 minutes of dictation and a small stack of AI note credits), a Premium tier at $4.99 a month, Professional at $15.99, and a Max tier at $99.99 with unlimited dictation and AI notes. We've seen other listings quote slightly different credit counts, so treat those numbers as directional and read [Chartnote's plans page](https://chartnote.com/plans) before you decide anything based on them.

None of that is a criticism. It's a freemium dictation product priced like one. The question is whether metered dictation matches how your clinic actually runs.

## Where the credit math runs out

Here's the arithmetic that sends people searching for alternatives. Take a Tuesday with 18 booked patients. If you dictate even a third of those notes at 90 seconds each, that's 27 minutes of dictation, more than the free tier's listed monthly allowance, gone before lunch on day one. AI note credits burn the same way: 15 credits against 300-plus monthly visits means you're choosing which 5% of patients get an AI-drafted note.

| Your volume | Notes/month (approx.) | What a metered free tier covers | What unlimited means |
| --- | --- | --- | --- |
| 6 patients/day, part-time | ~120 | A few days, then you're typing | Every visit, no rationing |
| 15 patients/day | ~300 | Roughly 5% of visits | Every visit |
| 22 patients/day | ~440 | A rounding error | Every visit |

The counterargument is real: Chartnote's paid tiers are cheap, and the $99.99 Max tier removes the meters entirely per that same third-party listing. If dictation is the workflow you want, that tier is a fair price for it. The switch decision usually isn't about price at all. It's about the next section.

Once you've run your own numbers, the useful comparison is a week of each. [What's on each Practice Copilot plan](/us/pricing/) is public, so you can do the math before talking to anyone.

## Dictation still makes you tell the visit twice

This is the actual wedge, and it has nothing to do with credits. With dictation, the patient leaves and then you narrate what just happened: history, exam, assessment, plan, out loud, from memory, into a microphone. You've now conducted the visit twice. Dot phrases shave the typing but not the composing. Multiply by 18 patients and you've spent a real hour of your day being your own court reporter.

Ambient capture deletes that step. The visit conversation is the input. You get consent, you talk to the patient like you normally would, and the draft assembles itself from what was actually said in the room. Nobody performs a recap into a phone between patients. Our comparison of [ambient AI versus dictation](../ambient-ai-vs-dictation/) walks through where each method wins, and the wider [dictation and transcription software roundup](../medical-dictation-software-compared/) covers the rest of that market if you want to shop the category properly.

Dictation keeps one honest advantage: control. You compose every sentence, so the draft never surprises you. Some clinicians, especially those with terse, highly templated notes, prefer that. If that's you, skip ahead to the "when Chartnote is better" section, because an ambient scribe solves a problem you may not have.

## What you get from Patient Square instead

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Both of those extras are drafts for you to confirm, not a coding engine and not a script that transmits anywhere. You stay the author of the chart.

The plan mechanics are the opposite of credit metering. Every plan includes unlimited visits and notes with no per-note metering, EHR-ready export (PDF · HL7 · FHIR), a live transcript as you speak, and specialty-aware templates, ready out of the box. Practice Copilot starts at $79 per clinician per month on the annual Assist plan; the Copilot tier at $119 a month annual adds a bundled AI EHR and WhatsApp messaging if you'd rather stop pasting notes into a separate system altogether.

On the trust side: safeguards are HIPAA compliant, a BAA is available for every customer, a SOC 2 Type II audit is in progress, and visit audio is never stored (processed in memory, discarded once the note is drafted). The full posture is on our [security page](/us/security/).

We think the honest way to frame the price gap is this: Chartnote sells you documentation help by the minute, and we sell the whole documentation job at a flat rate. Cheaper per month isn't the same as cheaper per note once volume shows up.

## When Chartnote is the better fit

Plenty of cases, and we'd rather you pick correctly than pick us.

Chartnote wins when your documentation load is genuinely light: a few visits a day, a part-time telehealth panel, or a side practice where a free tier plus occasional credits covers the month. It wins if dot phrases are load-bearing in your workflow and you mostly need faster text expansion inside a web EHR. It wins on raw entry price; per third-party listings, its cheapest paid tier costs less than a sandwich. And it wins if you simply aren't ready for ambient recording in the room, since dictation never captures the patient's voice at all, which sidesteps the consent conversation entirely.

If two or more of those describe you, stay. Revisit when your volume changes.

## How to run the switch test in a week

Don't decide from pricing pages, ours included. Pick your five messiest recurring visit types. Run them through your current Chartnote workflow on Monday and Tuesday and time the full loop: dictation, dot-phrase cleanup, paste, sign. Run the same visit types ambiently on Wednesday through Friday and time the review-and-sign loop instead. The 7-day free trial exists so you can do exactly this on real patients, and the [per-plan breakdown](/us/pricing/) tells you what you'd pay if the math wins. If you want a guided version of that week, book a demo and we'll set it up around your visit mix.

---

## Clinicea Alternatives in India: Forms vs Ambient AI
https://patientsquare.com/in/blog/clinicea-alternatives-india/
Published 2026-08-21 · Tags: clinicea, alternatives, clinic-software, india

Clinicea's ladder reads ₹1,999 to ₹3,999 per practitioner, before add-ons. How the customisable-EMR suite compares with an ambient AI that writes the note.

Clinicea's pricing page lists three plans per practitioner per month: Starter at ₹1,999, Pro at ₹2,999, and Enterprise at ₹3,999. Add-ons sit on top, including a lab module at ₹499 per technician, pharmacy at ₹499 per pharmacist, and a patient portal at ₹3,999 per clinic. Confirm GST treatment and billing terms with them directly.

Clinicea and Patient Square publish price ladders that look almost like twins. Clinicea lists ₹1,999, ₹2,999, and ₹3,999 per practitioner per month; Patient Square's monthly tiers are ₹1,999, ₹2,999, and ₹4,999, dropping to ₹1,599, ₹2,399, and ₹3,999 on annual billing, ex-GST plus 18% GST. The products underneath aren't twins at all. Clinicea is a configurable clinic suite you set up and fill; Patient Square is an ambient AI that writes the note for you. So the alternative you want depends on which verb is broken in your clinic: configure, or write. If it's write, book a demo and watch a consult turn into a signed note.

> **Key takeaways**
>
> - Clinicea publishes Starter ₹1,999, Pro ₹2,999, Enterprise ₹3,999 per practitioner per month, with a 14-day trial.
> - Add-ons stack: lab ₹499/technician, pharmacy ₹499/pharmacist, patient portal ₹3,999/clinic monthly, custom EMR form packs ₹12,500 to ₹45,000 one-time.
> - Clinicea's pitch is a 100% customisable EMR. You still fill the forms, and India's ~2-minute consults are where form-filling breaks.
> - Patient Square is ₹1,599/month entry on annual billing (ex-GST); ₹2,399 bundles the AI EHR. The note drafts itself.
> - Different jobs: suite breadth and configurability vs documentation that writes itself. Price the job you actually have.

## The sticker and the loaded price

Clinicea deserves credit for publishing numbers at all; plenty of Indian clinic-software vendors hide everything behind a demo call. But the sticker is the start of the arithmetic, not the end, because the product is modular and the modules bill separately.

Here's the published structure, from their pricing page as of this writing:

| Line item | Clinicea (published) | Notes |
|---|---|---|
| Base plan, per practitioner/month | ₹1,999 Starter · ₹2,999 Pro · ₹3,999 Enterprise | Pro adds online booking, packages, feedback, virtual assistant |
| Lab module | ₹499 per technician/month | Optional |
| Pharmacy module | ₹499 per pharmacist/month | Optional |
| Patient portal | ₹3,999 per clinic/month | Covers 100 active users |
| White-labelled emails | ₹499 per clinic/month | Optional |
| Remote self-registration | ₹14,999 one-time + ₹4,999/year hosting | Their published plugin pricing |
| Custom EMR form packs | ₹12,500 to ₹45,000 one-time | 4 to 20 forms |

Run one worked example. A two-doctor clinic on Pro with a lab technician, a pharmacist, and the patient portal is ₹5,998 + ₹499 + ₹499 + ₹3,999, so roughly ₹10,995 a month before any one-time form customisation, and before you confirm GST treatment. That's not a criticism; those modules do real work, and if you need them, that's what they cost. The point is to price the configuration you'll actually run, not the Starter sticker.

Patient Square's arithmetic is shorter because the scope is narrower. Two clinicians on Copilot annual is ₹2,399 × 2 = ₹4,798 ex-GST, about ₹5,662 once 18% GST is added, and that includes the bundled AI Copilot EHR. No lab module, no pharmacy module, and we're not going to pretend otherwise. If those functions are on your must-have list, the comparison ends here honestly: Clinicea sells them, we don't. If documentation is the must-have, keep reading, or go straight to the [India pricing page](/in/pricing/) for the full ladder.

## Custom fields are still fields

Clinicea's headline claim is a 100% customisable EMR, and by the published feature set the configurability is real: forms, workflows, and packages shaped to your specialty, with paid form packs if you want them built for you. For a clinic with an operations-minded person who enjoys tuning systems, that's a genuine draw.

Now the uncomfortable part. Picture a two-chair dermatology clinic in Gurgaon that spends a weekend building the perfect acne-consult template: fourteen fields, dropdowns for severity, checkboxes for triggers. Monday morning brings 40 patients. Indian consultations average about two minutes, per a 67-country BMJ Open review. Fourteen fields in two minutes, forty times over, while the patient explains their history? The template gets abandoned by 11am, and the notes revert to two words and a drug name.

That's not a Clinicea flaw. It's the ceiling of the whole form-filling category, and every configurable EMR shares it. Customisation changes what the form asks. It doesn't change who answers it, or when. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A skipped form still leaves a gap in the record.

The ambient approach flips the order of work. Nothing to fill during the consult; the structure gets applied by the AI afterwards, and you review a finished draft instead of feeding an empty one.

## When Clinicea is the better fit

Choose Clinicea when breadth and configurability are the actual requirement. A multi-doctor or multi-specialty clinic that wants scheduling, financials, inventory, lab, pharmacy, packages, and a patient portal from one vendor gets a real suite, with published add-on pricing and a 14-day trial to verify it. Clinics selling treatment packages or memberships (dermatology, dental, wellness chains) fit the Pro plan's package management well. And if you want an EMR moulded field-by-field to your specialty and have someone to own that configuration, that's precisely the product Clinicea built.

Choose Patient Square when the note is the bottleneck and you'd rather it wrote itself. A solo GP or small clinic drowning in evening documentation doesn't need a form-builder; it needs the form filled.

## What the ambient side actually ships

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It handles consults in English, Hindi, and 20+ Indian languages, including code-mixed Hinglish, and the note lands in clean clinical English regardless. Specialty-aware templates come ready out of the box, so there's structure without a weekend of form-building. Prescriptions stay drafts you sign; ICD-10 comes as suggestions, not autopilot coding.

Data handling is deliberately boring: audio is processed in memory and discarded once the note drafts, records are handled to DPDP Act 2023 standards, a SOC 2 Type II audit is in progress, and every plan includes EHR-ready export (PDF · HL7 · FHIR) plus unlimited visits and notes. ABDM integration is on our roadmap, not live today; if production ABHA linking is a hard requirement, ask any vendor for their exact NHA milestone status and hold us to the same standard. Details live on the [security page](/in/security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

We think the fairest test is time-boxed and boring: run Clinicea's 14-day trial and our 7-day trial against the same clinic days, and measure three numbers. Minutes from patient-out to note-signed. Fields touched per patient. Charting left at 8pm. The winner for your clinic will be obvious by Thursday.

## Two trials, one decision

If your shortlist still has both names on it, that's probably correct; they solve different problems, and some clinics genuinely need both kinds of tool at once. A configurable suite can run your front office while an ambient layer writes the clinical note. For the wider field beyond these two, the [India clinic software scorecard](../best-clinic-management-software-india/) ranks the main options, and the [EMR buyer's guide](../emr-software-india-guide/) covers cloud, DPDP, and lock-in questions that apply to every vendor here. If Practo Ray is also on your list, the [Practo Ray comparison](../practo-ray-alternatives-india/) walks the same ground for that suite.

One question settles most shortlists: on your busiest OPD day, is the problem that your software can't be shaped to your workflow, or that nobody has time to feed it? Shape problems point to Clinicea. Feeding problems point to ambient AI. Book a demo and test the feeding problem against your own Monday.

---

## Patient Administration System (PAS) for Indian Hospitals: A Guide
https://patientsquare.com/in/blog/patient-administration-system-india/
Published 2026-08-21 · Updated 2026-08-27 · Tags: patient-administration-system, pas, adt, hospital-software, india

A patient administration system runs the registration, admission, transfer and discharge layer of a hospital. What a PAS covers and how to choose one.

A PAS is the core system that handles a hospital's patient administration: registration, demographics, and the admission, discharge, and transfer (ADT) workflow. It's the single source of truth for who a patient is and where they are in the hospital. The term comes from the NHS, but the administrative layer it describes exists in every hospital, including Indian ones.

A patient administration system, PAS, is the layer of a hospital that knows who a patient is and where they are. Registration, demographics, and the admission-discharge-transfer flow that moves a patient from casualty to a ward to home. The term comes from the NHS, but the job it names exists in every hospital, including yours. In India it usually lives inside a larger hospital system rather than as a standalone product, which is exactly the confusion this guide clears up: what a PAS covers, how it differs from an HMS and an EHR, and how to choose one.

> **Key takeaways**
>
> - A PAS is the administrative spine: patient registration, unique identity, and the admission-discharge-transfer (ADT) flow. It answers "who and where", not "what's the diagnosis".
> - The term is NHS-born, but the administrative layer is universal. In India it's usually bundled inside an HMS or HIS, not sold on its own.
> - A PAS and an EHR are different jobs: administration versus the clinical record. They connect through patient identity.
> - The most underrated buying criterion is duplicate-patient control: one patient, one identity, no scattered records.
> - An AI scribe sits downstream of the PAS. It drafts the note after registration; it doesn't register, admit, or discharge.

_Source: Patient administration system (definition, ADT), reference literature._

## What a patient administration system actually does

At its core a PAS records who the patient is and tracks every contact they have with the hospital, outpatient and inpatient. It starts at registration: a patient walks in, gets a record and a unique identifier, and from then on everything ties back to that identity.

The engine underneath is ADT, admission, discharge, and transfer. When a patient is admitted, moved between wards, or sent home, the PAS is what records it. It's the single source of truth for where every inpatient is at any moment. Add outpatient clinic scheduling, referral handling, waiting lists, and bed management, and you have the administrative machinery a hospital runs on before a single clinical note is written.

Think of a busy district hospital at 9pm: casualty filling up, two admissions waiting on beds, a transfer from ICU to the ward. The PAS is the board that everyone trusts to know who's where. When it's wrong, chaos; when it's right, the place runs.

## Why the PAS term confuses Indian buyers

Here's the honest snag. "PAS" is a term you'll hear far more in the UK and NHS context than in Indian hospital sales conversations. That doesn't mean the function is absent here. It means it's packaged differently.

In India, vendors overwhelmingly sell a **Hospital Management System (HMS)** or **Hospital Information System (HIS)**: a single suite that bundles the administrative layer, the clinical record, pharmacy, labs, and billing. The patient-administration functions, registration, ADT, bed management, live inside that suite as modules, not as a product called "PAS". So when an Indian buyer searches for a patient administration system, what they usually need is the administrative strength of an HMS, evaluated specifically on its administration features.

That reframing matters. If you go shopping for a "PAS" in India expecting a standalone product, you'll mostly find HMS suites. The right move is to keep the PAS lens, judge candidates on how well they handle patient identity and ADT, while accepting that the thing you buy is likely a broader system. Our [HMS explainer](/in/blog/hospital-management-system-explained/) covers what those suites bundle.

## PAS versus HMS versus EHR, sorted out

Three terms that overlap and get muddled. The cleanest way to hold them apart is by the question each answers.

| System | The question it answers | Core scope |
|---|---|---|
| PAS | Who is this patient, and where are they? | Registration, identity, ADT, beds, OPD/IPD contact |
| HMS / HIS | How does the whole hospital run? | PAS functions plus pharmacy, labs, billing, operations |
| EHR | What is this patient's clinical story? | History, diagnoses, notes, results, medications |

The PAS and the EHR are the pair people conflate most. One is administration, the other is the clinical record. They're joined at the hip through patient identity: the EHR attaches every note and result to the identity the PAS created. Get the identity wrong at registration and the clinical record inherits the error. Our [EHR vs HMS breakdown](/in/blog/ehr-vs-hms-india/) goes deeper on the clinical-versus-operational line.

## The buying criterion most hospitals underrate

If you take one thing from this guide, take this: judge a PAS on duplicate-patient control before anything else.

A duplicate record, the same patient registered twice under slightly different spellings or two phone numbers, is the quiet killer of hospital data. Suddenly a patient's history is split across two identities, their allergies live on one record and their current medication on the other, and a clinician sees half the picture. In a hospital doing hundreds of registrations a day, duplicates accumulate fast if the system doesn't actively prevent them.

A strong PAS fights this at the front door: search-before-create, fuzzy matching on name and phone, a warning when a likely duplicate appears. A weak one lets your front desk mint a fresh record every time and hands you a data-cleanup project a year later. This is unglamorous and it's the single feature that most affects data quality downstream, which is why we'd score it first, ahead of the shinier modules.

## Where ABDM and DPDP fit the administration layer

Two India-specific threads run through the PAS conversation now.

The first is ABDM. Since patient identity is exactly what a PAS manages, it's also the natural place to link a patient's [ABHA number](/in/blog/abdm-milestone-2-explained-clinics/) and participate in ABDM's consent-based record sharing. If you want records to move under the national digital-health infrastructure, the administrative layer is where that linkage starts. Ask a vendor whether its registration flow supports ABHA creation and linking.

The second is the [DPDP Act 2023](/in/blog/dpdp-act-clinics-guide/). The PAS holds the patient's core personal data, which makes it a front-line system for data governance. Registration is where consent should be captured, and the demographic record is personal data the hospital is now a Data Fiduciary for. A PAS that captures clean consent at registration makes the rest of your DPDP compliance easier; one that doesn't leaves a gap at the very start of the patient journey.

## Where a full hospital system beats a narrow PAS focus

Sometimes the narrow lens is the wrong one. If you're running or re-platforming a whole hospital, evaluating only the administration layer misses the point, you need the pharmacy, the labs, the billing, the inpatient operations all working together, and the PAS is one gear in that machine. In that case start from a full [hospital information system](/in/blog/best-his-software-india/) evaluation, with patient administration as a heavily weighted dimension inside it.

The narrow PAS focus makes sense when your gap is specifically administrative: registration is messy, duplicates are piling up, ADT is tracked on a whiteboard, and the clinical side is fine. Diagnose which you have. A hospital with good clinical software and broken registration needs administrative rigour, not a whole new suite.

## Where an AI scribe sits relative to a PAS

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

The relationship to a PAS is simple and worth stating so nobody expects the wrong thing. A scribe sits **downstream** of patient administration. By the time the scribe is working, the patient is already registered and identified, the PAS did that job. The scribe then turns the consultation into a structured note attached to that existing identity. It doesn't register patients, doesn't run ADT, doesn't manage beds or discharge.

So a scribe never replaces a PAS, and we wouldn't pitch it as one. What it changes is the clinical documentation that happens after registration. If your problem is administrative, wrong patient identities, messy admissions, this guide's PAS and HMS advice is what you need, not a scribe. If your problem is that clinicians drown in note-writing after the patient's already in the system, that's the scribe's lane. Two different fires. Our [Hospital Copilot context](/in/blog/hospital-management-system-explained/) sits the scribe inside the wider hospital picture.

## The short version

A patient administration system is the administrative spine of a hospital: registration, unique patient identity, and the admission-discharge-transfer flow. The term is NHS-born, and in India the function usually lives inside an HMS or HIS rather than a standalone product, so shop with the PAS lens but expect to buy a suite. Keep it separate from the EHR (that's the clinical record) and judge candidates hardest on duplicate-patient control, ABHA linkage, and DPDP-ready consent at registration. And remember a scribe sits downstream of all of it: it drafts the note after the patient's registered, it doesn't run the administration.

Want to see where a scribe picks up, once a patient's already in your system, and hands back a structured note? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch it run, then read how we handle patient data on the [security page](/in/security/).

---

## Patient Intake Software for Indian Clinics: Registration & Consent
https://patientsquare.com/in/blog/patient-intake-software-india/
Published 2026-08-21 · Updated 2026-08-27 · Tags: patient-intake-software, registration, digital-consent, dpdp, india

Patient intake software digitises registration and consent, the front door of the visit. What it covers, why DPDP consent matters, and how to choose one.

It's the software that handles the front door of a visit: patient registration, demographic and history capture, and consent. Instead of a paper form on a clipboard, the patient fills details digitally, often before arriving, and the data flows into the clinic's record system. For an Indian clinic, it's also where DPDP-compliant consent should be captured cleanly.

Patient intake software handles the front door of every visit: registration, the history form, and consent. It's the moment before medicine happens, and in most Indian clinics it's still a clipboard and a rushed signature. Digitising it does two things, speeds up the waiting room and, more importantly now, captures the consent the DPDP Act 2023 expects. This guide covers what intake software covers, why the consent piece is the real reason to care, and how to choose one for a clinic.

> **Key takeaways**
>
> - Patient intake software digitises the front door: registration, demographic and history capture, and consent. Patients can often complete it on their phone before arriving.
> - The consent angle is the one that changed. Under the DPDP Act 2023, consent must be free, specific, informed, and for a stated purpose. Intake is where you capture and record it.
> - It's a focused tool, distinct from a full clinic management suite. Buy it when the front desk and forms are the bottleneck.
> - The two features most buyers skip: DPDP-standard consent with an audit trail, and duplicate-patient prevention.
> - An AI scribe doesn't do intake. It picks up in the consult room, after registration.

_Sources: Digital Personal Data Protection Act 2023, Section 6; MoHFW EHR Standards for India._

## What patient intake software actually covers

Intake is everything that happens before the doctor sees the patient. Registration and demographics, the reason for the visit, medical and medication history, allergies, insurance or scheme details, and consent. Traditionally it's a paper form filled in the waiting room and then typed into the system by someone at the front desk.

Intake software moves that to a screen. The patient enters their own details, often on their phone before they arrive, and the data flows into the clinic's record system without a re-keying step. Fewer transcription errors, a shorter wait, and a front desk that isn't drowning during the morning rush.

Picture a busy Bengaluru clinic at 10am: fifteen patients in the waiting area, one receptionist, a stack of half-filled forms. Intake software is what turns that into patients arriving already registered, with the receptionist verifying rather than transcribing. That's the operational sell. But it's not the most important one anymore.

## Why DPDP made consent the real reason to care

The bigger shift is legal, and it sits right at intake. Since the [DPDP Act 2023](/in/blog/dpdp-act-clinics-guide/), a clinic handling patient data needs proper consent, and intake is where consent is asked for.

The Act sets a specific standard in Section 6. Consent to process personal data must be **free, specific, informed, unconditional, and unambiguous**, given through a clear affirmative action, for a **stated purpose**. Health data is personal data, so this isn't optional for a clinic. And here's the practical problem: capturing that reliably on paper is hard. A scrawled signature at the bottom of a form doesn't cleanly show what the patient consented to, for what purpose, or when.

Digital intake solves this better than paper can. It can present the purpose clearly, record an explicit affirmative action, timestamp it, and keep an auditable trail. If a patient later exercises a right, say, to withdraw consent or ask what you hold, you have a record instead of a shoebox. We think this is the strongest reason to digitise intake, stronger than the queue-shortening, and it's the one most vendor pitches undersell. The consent trail is the asset.

## Intake software or a full clinic management system?

A fair question, because a lot of clinic software claims to do intake too. The distinction is scope.

Patient intake software is focused on one slice: the front door. Registration, forms, consent. A full clinic management system runs the whole practice, appointments, the clinical record, billing, pharmacy, follow-ups. Intake can be a standalone tool that feeds your existing record system, or a module inside a bigger suite.

Which you need depends on your actual gap:

- If your clinical software is fine but your **front desk and forms are the mess**, a focused intake tool is the targeted fix.
- If you're **starting fresh or replacing everything**, you're shopping for a clinic management suite, and intake is one capability inside it.
- If you already run a suite that **handles intake poorly**, you might bolt a better intake layer on top rather than rip out the whole thing.

Our [clinic management software scorecard](/in/blog/best-clinic-management-software-india/) is the place to start if it's the whole suite you're weighing. If it's just the front door, keep the intake lens.

## The two features buyers skip past

Most intake demos show a clean form on a phone and call it done. Two things matter more than the form's looks.

First, **consent quality**. Does the software capture DPDP-standard consent, with the purpose stated, an explicit affirmative action, and a timestamped trail you can produce later? Or is the "consent" just a checkbox with no record of what was agreed to? A form that collects data without a proper consent record is a liability dressed up as convenience.

Second, **duplicate-patient prevention**. Intake is where duplicates are born. A patient registers as "Ramesh Kumar" today and "R. Kumar" next month, and now their history is split across two records. Good intake software searches before it creates, matches on phone and name, and warns the front desk before a duplicate is made. A weak one quietly multiplies records until your data is a mess. This one's boring and it's the difference between clean data and a cleanup project.

## Where ABDM and Indian languages fit intake

Two India-specific angles worth a vendor question each.

ABDM linkage starts at intake, because intake is where patient identity is established. If you want to link a patient's [ABHA number](/in/blog/abdm-milestone-2-explained-clinics/) or participate in ABDM's consent-based record sharing, the registration flow is the natural place to capture the ABHA and the consent. Ask whether the intake tool supports ABHA creation or linking.

Language matters too. Patient-facing forms in English alone don't serve a lot of Indian patients. Intake software that offers forms in Hindi and regional languages gets you cleaner data and genuine consent, because a patient who can read the purpose actually consents to it. Consent isn't informed if the patient couldn't read the form.

## Where an AI scribe fits, and where it plainly doesn't

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

The timing is the thing to be clear about. Intake happens **before** the consultation, at the front desk or on the patient's phone. The scribe happens **during** the consultation, in the room. So a scribe doesn't do intake, doesn't collect registration forms, and doesn't capture the administrative consent this guide is about. Different moment, different job.

Stated as plainly as we can: if your problem is the front door, messy registration, weak consent capture, duplicate records, then intake software is your answer and a scribe is not. Buy the intake tool. The scribe's value starts once the patient is registered and the consult begins, when it turns the conversation into a structured note so your evenings aren't lost to charting. The consent to process visit data still sits with your clinic and its intake process; the scribe drafts documentation, it doesn't own the consent architecture. For how the note itself comes together, our [NMC record-keeping guide](/in/blog/nmc-record-keeping-ai-scribe/) covers the documentation side.

## The short version

Patient intake software digitises the front door of the visit: registration, history, and consent, often on the patient's own phone before they arrive. The operational win is a faster, cleaner waiting room. The bigger win, since the DPDP Act 2023, is capturing consent that's free, specific, and for a stated purpose, with a trail paper can't match. Buy it when the front desk is your bottleneck, judge it hardest on consent quality and duplicate control, and ask about ABHA linkage and Indian-language forms. And keep it separate from the scribe question: intake is before the consult, the scribe is during it.

Want to see where a scribe picks up, after intake, once the consult begins, and hands back a structured note? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch it run, then read how we handle patient data on the [security page](/in/security/).

---

## E-Prescribing Software in India: What's Legal and What to Check
https://patientsquare.com/in/blog/e-prescribing-software-india/
Published 2026-08-20 · Updated 2026-08-27 · Tags: e-prescribing, e-prescription-software, nmc, telemedicine, india

E-prescriptions are legal in India, but the rules on signatures, drug lists and transmission are specific. What's legal under NMC guidance, and what to check.

Yes. Electronic prescriptions are legally valid in India, and the Information Technology Act 2000 recognises electronic records and signatures. The Telemedicine Practice Guidelines 2020 explicitly let a registered medical practitioner issue a prescription during a teleconsult. The prescription must carry the doctor's name, registration number, and the drug details, same as a paper one.

E-prescribing is legal in India, and has been for years. The Information Technology Act 2000 recognises electronic records and signatures, and the Telemedicine Practice Guidelines 2020 let a registered doctor prescribe during a teleconsult. What trips buyers up isn't legality; it's the detail. A valid e-prescription needs specific fields and a real signature, teleconsults limit which drugs you can prescribe, and India has no automatic prescription-to-pharmacy network. This is a guide to what's legal and what to check before you buy.

> **Key takeaways**
>
> - E-prescriptions are legal in India. The IT Act 2000 recognises electronic records and signatures; the Telemedicine Guidelines 2020 permit prescribing during a teleconsult.
> - A valid prescription must carry the doctor's name, address, registration number, and full drug details. A legally signed one needs an IT Act-compliant signature, not just a typed name.
> - India has no mandated e-prescription-to-pharmacy transmission network. The doctor gives the prescription to the patient, who picks the pharmacy. "Transmit" means different things to different vendors.
> - Teleconsults limit prescribing to Lists O, A, and B; Schedule X, narcotics, and benzodiazepines are off-limits.
> - An AI scribe drafts a prescription for the clinician to sign. That's a draft, not a pharmacy gateway.

_Sources: Telemedicine Practice Guidelines 2020; Information Technology Act 2000._

## Is e-prescribing actually legal in India?

Yes, and this is where a lot of the confusion starts. Some clinics still treat an electronic prescription as a legal grey area. It isn't. The [Information Technology Act 2000](https://www.indiacode.nic.in/handle/123456789/1999) gives electronic records and electronic signatures legal recognition, so a prescription created and signed electronically stands on the same footing as a paper one.

On top of that, the Telemedicine Practice Guidelines, issued on 25 March 2020, spell it out for medicine specifically. A registered medical practitioner can consult by video, audio, or text and issue a prescription at the end of it. The Guidelines even give a sample prescription format. So the base question, "am I allowed to prescribe electronically", has a clear answer. You are.

The catch is that "legal" and "done correctly" are two different things. The Act and the Guidelines both attach conditions, and software that ignores them produces a prescription that's technically deficient even if the doctor did everything right clinically.

## What makes an e-prescription valid, field by field?

A prescription, paper or digital, has to carry certain information to be a proper prescription under Indian rules. The Drugs and Cosmetics framework and the Telemedicine Guidelines line up on the essentials:

- The doctor's **name, address, and registration number** from their council.
- The **drug name, strength, dosage, and duration** for each medicine.
- The **date**, and enough patient identification to tie the prescription to the right person.

Miss the registration number and a pharmacist has grounds to refuse a Schedule H drug. Good e-prescribing software makes these fields mandatory so a prescription can't leave the system half-filled. That's the first thing to check: does the tool enforce the required fields, or does it let you type free-form and hope?

## Where the signature question gets real

Here's the part most buyers gloss over. Typing your name at the bottom of a PDF is not an electronic signature in the legal sense. The IT Act sets conditions for a valid electronic signature, and they're specific: it has to be **uniquely linked to you**, under **your sole control**, able to **detect any later tampering**, and certified by a **Certifying Authority** recognised by the Controller of Certifying Authorities.

That's a real bar. A lot of "digital prescription" apps just render a typed name in a signature font, which is fine as a convenience but doesn't meet the standard for a legally signed document. For an ordinary in-person prescription that a patient walks to the chemist with, this rarely bites. For anything that needs to hold up later, a medico-legal dispute, an insurance claim, the signature mechanism matters.

So when a vendor says "e-signature", ask what kind. Is it a proper digital signature backed by a certificate, or a picture of your name? Both have uses. Only one is what the IT Act means.

## Which drugs can you prescribe by teleconsult?

If any part of your prescribing is remote, the Telemedicine Guidelines add a layer the software should respect. The Guidelines sort medicines into lists:

| List | What it covers | Example |
|---|---|---|
| List O | Over-the-counter drugs | Paracetamol, antacids |
| List A | Safe drugs for a first teleconsult | Eye drops, skin creams |
| List B | Add-on drugs for an existing, reviewed condition | Adding enalapril to an ongoing regimen |
| Prohibited | Cannot be prescribed by teleconsult | Schedule X, narcotics, benzodiazepines |

The prohibited list is the one to watch. Habit-forming and narcotic drugs, Schedule X substances, and the like are off the table for a teleconsult, full stop. Software can flag these, but the responsibility sits with the prescriber. A tool that quietly lets you e-prescribe a prohibited drug over a video call isn't doing you a favour; it's a liability. This is worth reading alongside our post on whether [an e-prescription is legally valid in India](/in/blog/e-prescription-software-india-legal/), which walks the validity checklist in more depth.

## Why "send to pharmacy" mostly doesn't exist in India

This is the biggest gap between the marketing and the reality. In the US, e-prescribing usually means the prescription travels electronically from the doctor's software to the pharmacy's system through a network like Surescripts. India has no equivalent mandated network.

The Telemedicine Guidelines have the doctor **share the prescription with the patient**. The patient then decides where to get it filled, their local chemist, an e-pharmacy, wherever. There's no national pipe that routes a prescription from your clinic straight into a pharmacy's queue. Some large e-pharmacy platforms have built their own closed loops, but that's a private integration, not a country-wide standard.

Which means when an Indian vendor says its software "transmits prescriptions", press on what that actually is. Usually it's one of: generating a PDF the patient receives on WhatsApp or email, or a hook into one specific e-pharmacy partner. Both are legitimate. Neither is the US-style pharmacy gateway the word "e-prescribing" might make you picture. Knowing the difference stops you buying a capability that isn't real here yet.

## What should you check before you buy?

Cut through the feature list with five questions. We think most e-prescribing pitches fall apart on at least one of them.

1. **Does it enforce the mandatory fields?** Name, address, registration number, drug details. If a prescription can leave the system without these, that's a problem.
2. **How does it handle the signature?** A real IT Act-compliant digital signature, or a typed name in a fancy font? Know which you're getting.
3. **Does it respect the teleconsult drug lists?** For any remote prescribing, the O/A/B split and the prohibited list should be built in, not left to memory.
4. **Where does the prescription data live?** A prescription is health data, so it's personal data under the [DPDP Act 2023](/in/blog/dpdp-act-clinics-guide/). Ask where it's stored, how long, and who can see it.
5. **What does "transmit" mean?** Patient PDF, single e-pharmacy hook, or a claim of a pharmacy network that doesn't exist here? Make them specify.

Then trial it against a real prescribing day. A demo prescription for a fake patient tells you nothing. Your Tuesday OPD, with its Schedule H refills and its Hinglish drug names, tells you everything.

## Where an AI scribe fits, and its honest limit

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

Read that carefully, because the word to sit on is **draft**. The scribe listens during the consult and produces a prescription draft alongside the note. The clinician then reviews it, edits it, and signs it. That draft is a starting point, not a finished, transmitted prescription. It cuts the typing, not the judgement.

Now the boundary, plainly stated. The scribe is not an e-prescribing gateway. It doesn't route a prescription to a pharmacy, doesn't hold a Certifying Authority signing certificate on your behalf, and doesn't make the legal or clinical call about what to prescribe. Those stay with the doctor and the doctor's chosen signing method. What it offers is a faster path to the draft, with an ICD-10 suggestion attached, so the prescription part of documentation stops eating your evening. If your real need is a full prescribing-and-pharmacy loop, a scribe isn't that, and we'd tell you so. For the wider picture of how the note and prescription draft come together, our [NMC record-keeping guide](/in/blog/nmc-record-keeping-ai-scribe/) covers the documentation side.

## The short version

E-prescribing is legal in India under the IT Act 2000 and the Telemedicine Guidelines 2020. A valid prescription needs the right fields and, for a legally signed one, an IT Act-compliant signature, not a typed name. Teleconsults limit you to Lists O, A, and B and bar the prohibited list. And there's no US-style pharmacy transmission network, so "e-prescribing" here usually means a prescription the patient receives, not one the pharmacy auto-receives. Check the fields, the signature, the drug lists, the data storage, and what "transmit" really means. Then trial it on real patients.

Want to see how a reviewed, signed prescription draft comes together in about two minutes on a live consult? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it, then read how we protect prescription data on the [security page](/in/security/).

---

## Patient Data Management System for Indian Hospitals: A Buyer's Guide
https://patientsquare.com/in/blog/patient-data-management-system-india/
Published 2026-08-20 · Updated 2026-08-27 · Tags: patient-data-management, data-governance, dpdp, hospital-software, india

A patient data management system is where DPDP compliance lives or dies. A buyer's guide for Indian hospitals on data governance, security, and what to check.

It's the system a hospital uses to collect, store, secure, and control patient data across its departments: demographics, clinical records, prescriptions, lab and imaging results, and consent. It's less a single feature than the data spine under your EHR and HMS. For an Indian hospital, it's also where DPDP Act compliance is enforced or lost.

A patient data management system is the least glamorous thing a hospital buys and the one that will get you fined if it's weak. It's the data spine under your EHR and HMS: how patient information is collected, stored, secured, and controlled across every department. Since the DPDP Act 2023, it's also where compliance is enforced or lost. This guide is written for the person who has to choose one for an Indian hospital, and it leads with the part vendors bury: data governance.

> **Key takeaways**
>
> - A patient data management system is the governance and security spine under your EHR and HMS, not a separate clinical feature. It decides who sees what, stored where, on what consent.
> - Under the DPDP Act 2023, a hospital is a Data Fiduciary with non-delegable liability. A vendor processing data for you doesn't take the liability off your books.
> - The Act's schedule sets steep penalties, up to ₹250 crore for failing to keep reasonable security safeguards. Governance is a financial risk, not just a legal nicety.
> - Buy on governance, not just clinical features: data residency, consent handling, role-scoped logged access, erasure workflows, breach detection, and standards-based interoperability.
> - An AI scribe drafts notes; it doesn't run your data management. Keep the two questions separate.

_Sources: Digital Personal Data Protection Act 2023; MoHFW EHR Standards for India._

## What a patient data management system actually is

Strip the marketing and it's this: the layer that holds patient data and controls what happens to it. Demographics from registration, the clinical record, prescriptions, lab and imaging results, billing, and, increasingly, the consent attached to all of it. Every department writes to it and reads from it.

It's tempting to think you already have this because you have an EHR or an HMS. You have the clinical and operational software, yes. But the *data management* question is a different cut: not "can I chart a patient" but "who can see this record, on what basis, stored where, for how long, and can I prove it." That's governance, and it's the part that gets skipped in a demo where everyone's admiring the OPD screen.

For a 200-bed hospital in, say, Coimbatore, the data spine is touched by hundreds of staff a day. The system either enforces good governance at that scale or it becomes a liability that grows with every record.

## Why DPDP makes this the honest wedge

One change reset the buying calculus. The [DPDP Act 2023](/in/blog/dpdp-act-clinics-guide/) made every hospital a **Data Fiduciary** for its patients' personal data, and health data is personal data under the Act. That word carries weight the old regime didn't.

A Data Fiduciary's liability is **non-delegable**. The Act is explicit that you're responsible for compliance regardless of any contract to the contrary, and regardless of a data processor acting on your behalf. In plain terms: outsourcing the processing to a vendor does not outsource the liability. If your data management system leaks, "the software company handles that" is not a defence. The board looks at the hospital.

And the numbers are not small. The Act's schedule sets a maximum penalty of up to ₹250 crore for failing to implement reasonable security safeguards, and up to ₹200 crore for failing to notify a breach properly. That's the range that turns data governance from an IT footnote into a boardroom line item. So when we say buy on governance, it's not a compliance-officer preference. It's the risk that dwarfs the licence fee.

## The governance features that actually matter

Most patient data management pitches lead with clinical breadth. Flip it. Score the governance layer first, because that's where the DPDP exposure sits. Here's what to look for.

| Governance area | What to check |
|---|---|
| Data residency | Is patient data stored in India? For a Significant Data Fiduciary, in-country storage is expected. |
| Consent | Can you capture, record, and revoke consent per purpose, and show the trail? |
| Access control | Is access role-scoped and logged, so you know who opened which record and when? |
| Erasure and correction | Can you action a patient's request to delete or correct their data within the required window? |
| Breach detection and reporting | Can the system detect and log a breach fast enough to notify the Board and patients on time? |
| Retention | Can you set and enforce how long each data type is kept, not just keep everything forever? |

None of these show up in a glossy clinical demo. All of them show up in a DPDP audit. A hospital that gets the clinical features right and the governance features wrong has bought a beautiful liability.

## What DPDP breach handling demands of your system

Breach notification is the sharpest test, because it's time-bound and it's public. Under the DPDP framework, when a personal data breach happens, the Data Fiduciary has to notify the Data Protection Board and the affected patients. Affected individuals get a plain-language account: what happened, what data was exposed, what protective steps they can take, and who to contact.

You can't do any of that if your system can't tell you a breach occurred, or can't tell you whose records were touched. That's why detection and logging aren't optional extras. A patient data management system that stores everything but logs nothing leaves you unable to meet the notification duty even when you want to. The [DPDP Rules timeline for clinics](/in/blog/dpdp-rules-2025-clinic-timeline/) tracks how these obligations are firming up, and hospitals should read it as a system-requirements list, not just a legal update.

Ask a vendor directly: if a record is accessed improperly, will I know, and will I know whose data it was? If the answer is vague, that's your answer.

## Where it fits with your EHR, HMS, and ABDM

A patient data management system isn't a rival to your EHR or HMS; it's the layer they should both sit on. The EHR is the clinical record, the HMS runs operations, and the data management layer governs the information both of them touch. Our [EHR vs HMS explainer](/in/blog/ehr-vs-hms-india/) covers where those two lines sit; the governance layer runs under both.

Interoperability belongs here too. If you want records to move under the [MoHFW EHR Standards](https://www.nrces.in/standards/ehr-standards-for-india) or to participate in ABDM's consent-based exchange, the data has to be structured and governed for it. A system that stores records in a private format and can't share them under a recognised standard limits you later, when a patient or a regulator expects portability. For where ABDM's consent flow fits, our [Milestone 2 explainer](/in/blog/abdm-milestone-2-explained-clinics/) walks the record-sharing step.

## When a full HIS or HMS is the better buy

Be honest about scope. If your real need is to run the whole hospital, admissions, wards, theatre, pharmacy, billing, inpatient flow, then what you're buying is a full hospital system, and its data management layer is one part of a much larger tool. In that case, start from a [hospital information system](/in/blog/best-his-software-india/) evaluation and treat data governance as a scored dimension inside it, not a separate purchase.

A standalone data management focus makes more sense when you already run clinical software you're keeping and the gap is governance: you can chart fine, but you can't prove consent, control access, or handle an erasure request. Diagnose which problem you actually have before you shop. Buying a full HIS to fix a governance gap is overkill; bolting governance onto a system that fundamentally can't log access is underkill.

## Where an AI scribe sits, and where it doesn't

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

For a hospital weighing data management, the useful thing to know is what a scribe touches and what it doesn't. It doesn't run your patient data management system. It produces the note that goes into it. On the data side, the scribe's own handling is deliberately narrow: visit audio is processed in memory and discarded once the note is drafted, so there's no audio archive sitting on a server, and the signed note lands in your record system where your governance takes over. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The honest limits, stated plainly. Our platform's compliance posture is handled to DPDP Act 2023 standards, consent-first and purpose-limited, with a SOC 2 Type II audit in progress, not a certification we claim as finished. ABDM integration is on our roadmap, not shipped. So a scribe doesn't relieve you of any of the governance work in this guide; the hospital and its data management platform still own that. What the scribe changes is the quality of the record going in, and the fact that it doesn't create a second audio copy of every consult to secure. If you're evaluating the wider Hospital Copilot picture, the [hospital management system explainer](/in/blog/hospital-management-system-explained/) gives the operational frame.

## The short version

A patient data management system is the governance spine under your hospital's EHR and HMS, and under the DPDP Act 2023 it's where your compliance stands or falls. You're a Data Fiduciary with non-delegable liability and penalties reaching ₹250 crore, so buy on governance, data residency, consent, logged access, erasure, breach detection, not just clinical features. Match the scope to your real gap: a full HIS if you're running the whole hospital, a governance focus if the clinical software is fine but the controls aren't. And keep the scribe question separate; it drafts notes, it doesn't manage your data.

Want to see how a scribe hands a signed note to your record system without keeping a copy of the audio? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch it work, then read our data handling in full on the [security page](/in/security/).

---

## Types of Electronic Health Records in India: EMR vs EHR vs PHR
https://patientsquare.com/in/blog/types-of-electronic-health-records-india/
Published 2026-08-20 · Updated 2026-08-27 · Tags: electronic-health-records, emr-vs-ehr, phr, abdm, india

EMR, EHR and PHR are three different records, not synonyms. Here's what each type means in India, who owns it, and where ABDM and the ABHA-linked PHR fit in.

An EMR is a patient's digital chart inside one practice or hospital, owned by that provider. An EHR is the broader, shareable record designed to move across providers. A PHR is the record the patient owns and controls, drawing from multiple sources. Same clinical data, three different owners and three different jobs.

EMR, EHR, and PHR are not three names for the same thing. They're three different records with three different owners. An EMR is your practice's own chart of a patient. An EHR is the version built to travel across providers. A PHR is the one the patient owns and controls. Getting these straight matters before you buy anything, because vendors blur the labels and you can pay for the wrong record entirely. This walks each type, who holds it, and where ABDM's ABHA-linked PHR fits.

> **Key takeaways**
>
> - Three records, three owners: EMR sits with one provider, EHR is built to move across providers, PHR is controlled by the patient.
> - Most Indian clinic software sold as "EHR" is really an EMR with export features. Real interoperability means implementing the MoHFW EHR Standards, revised 31 December 2016.
> - The PHR is the ABDM piece patients touch: a record linked to their ABHA number, pulling data from connected providers on their consent.
> - "Types of EHR" also splits by function: inpatient, ambulatory, specialty. The owner question matters more than the feature list.
> - An AI scribe is none of the three. It drafts the note that feeds whichever record system you run.

_Sources: MoHFW EHR Standards for India (2016); National Health Authority / ABDM._

## What does EMR mean in India?

An EMR, an Electronic Medical Record, is the digital chart your practice keeps on a patient. Registration details, history, diagnoses, prescriptions, notes from each visit. It lives inside your clinic or hospital, and it belongs to you as the provider.

The defining trait is scope. An EMR is bounded to one facility. When a patient who's been coming to your Pune clinic for two years walks into a hospital in Nagpur, your EMR doesn't go with them. The Nagpur hospital starts a fresh record. That isolation is fine for a lot of practices; you mostly need a clean, retrievable chart for your own patients, and an EMR is exactly that.

Most software marketed to Indian clinics is, at heart, an EMR. It runs registration, the consultation note, billing, sometimes pharmacy and labs. Useful, and often all a solo doctor or small clinic actually requires. The label on the box may say "EHR," which brings us to the confusing part.

## The EHR is the record built to travel

An EHR, an Electronic Health Record, is the broader record designed to be shared across providers. Same clinical content as an EMR, but built to travel. The point of an EHR is that a patient's record can follow them from a clinic to a hospital to a diagnostic lab, each provider seeing a fuller picture instead of a fragment.

For that to work, the record has to speak a common language. That's what the [MoHFW EHR Standards](https://www.nrces.in/standards/ehr-standards-for-india) exist for. First published in 2013 and revised on 31 December 2016, they recommend clinical terminologies, SNOMED CT for clinical terms, ICD-10 for diagnoses, LOINC for lab results, so that "chest pain" or "HbA1c" means the same coded thing in every system. The National Resource Centre for EHR Standards at C-DAC Pune maintains them.

Here's the honest bit most vendor pages skip. Calling a system an EHR doesn't make it interoperable. If the software stores records in its own format and can't exchange them under a recognised standard, it's an EMR wearing an EHR label. The real question isn't what the marketing says. It's *which standards does this actually implement, and can it exchange a record with another system?* Our [EMR vs EHR breakdown for India](/in/blog/emr-vs-ehr-india/) goes deeper on where that line sits for a buyer.

## What is a PHR, and why is it the patient's record?

A PHR, a Personal Health Record, flips the ownership. An EMR and an EHR are held by providers. A PHR is held and controlled by the patient. It's their record, drawing from wherever their care happened, and they decide who sees it.

In India, the PHR is the part of the system patients actually hold in their hand. Under the Ayushman Bharat Digital Mission, a patient creates an ABHA number, their health account, and uses a PHR app to link records from ABDM-connected providers. The patient grants consent for each share. A hospital can push a discharge summary into the patient's PHR; the patient can then show it to a new doctor. Nobody pulls the record without the patient saying yes.

This is a genuine shift. For decades an Indian patient's records lived in a shoebox of paper and a dozen clinic systems that never talked. The PHR model puts the patient at the centre of their own record. It's early, and adoption is uneven, but it's the direction the national infrastructure is building toward. If you want to understand where a clinic's software plugs into this, our [ABDM Milestone 2 explainer](/in/blog/abdm-milestone-2-explained-clinics/) covers the consent-based record-sharing step.

## Three records, side by side

The cleanest way to hold this: same data, different owner, different reach.

| | EMR | EHR | PHR |
|---|---|---|---|
| **Owner** | The provider (one facility) | The provider(s), shareable | The patient |
| **Scope** | One clinic or hospital | Across providers | Everything the patient links |
| **Who controls sharing** | The facility | Consent-based across facilities | The patient decides |
| **India context** | Most clinic software | MoHFW EHR Standards, ABDM exchange | ABHA-linked PHR app |
| **Typical use** | Your own patients' charts | Records that follow the patient | Patient holds their full history |

Read the "Owner" row first. It's the fault line the other rows fall out of. A clinic buying "an EHR" usually wants a good EMR. A patient wanting their whole history in one place wants a PHR. Confusing the two is how clinics overbuy and patients get told the wrong thing.

## What are the "types of EHR" beyond EMR vs PHR?

The EMR/EHR/PHR split is by ownership. There's a second way records get categorised, by function, and it's worth knowing because vendors use it too.

- **Ambulatory (outpatient) records** are built for OPD and clinic workflows: the fast consult, the prescription, the follow-up. This is where most Indian clinic software sits.
- **Inpatient records** cover admissions, ward rounds, orders, and discharge, the domain of a full hospital system. Our [HMS explainer](/in/blog/hospital-management-system-explained/) covers where that fits.
- **Specialty records** are shaped for one discipline, dermatology, ophthalmology, dentistry, with templates and fields that a general system won't have.

None of these change the ownership question. An ambulatory EMR is still an EMR. A specialty system built to exchange records under a standard is still an EHR. When someone lists "types of EHR," they usually mean this functional split, so it helps to ask whether they're talking about *who owns the record* or *what the record is shaped for*. They're different axes.

## DPDP sits under every record now

Whichever record you're building, one thing now sits under all of it: the [Digital Personal Data Protection Act 2023](/in/blog/dpdp-act-clinics-guide/). Health data is personal data under the Act, and every clinical record you hold is a fiduciary responsibility, not just a file.

That raises the stakes on the ownership question. If you run an EMR, you're the data fiduciary for those records, responsible for consent, purpose limitation, and secure handling. If a patient controls their PHR, the consent architecture is baked into how ABDM sharing works. When you evaluate any record system now, "where does the data sit and how is consent handled" is no longer a nice-to-have. Our [DPDP timeline for clinics](/in/blog/dpdp-rules-2025-clinic-timeline/) tracks what's coming and when.

## Where does an AI scribe fit in all this?

It doesn't fit into any of the three boxes, and that's the point worth being clear about. An AI scribe isn't a record system. It's a documentation layer that produces the note which then goes *into* your record system.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

So the honest framing: the scribe drafts, the clinician reviews and signs, and that signed note becomes part of whatever you run, an EMR, or the bundled AI EHR at the Copilot tier. The scribe doesn't own the record, doesn't create a PHR, and isn't an ABDM record exchange, ABDM integration is on our roadmap, not shipped. What it changes is the quality of the note going in. When every consult produces a structured note instead of three rushed lines, the record underneath, whichever type it is, gets better by default. If you want to see where the bundled EHR sits, our [EMR software guide](/in/blog/emr-software-india-guide/) lays out the plan tiers.

## The short version

EMR, EHR, and PHR are three records with three owners. The EMR is your practice's chart. The EHR is the shareable, standards-based record built to follow the patient. The PHR is the patient's own record, and in India that's the ABHA-linked piece under ABDM. "Types of EHR" also splits by function, ambulatory, inpatient, specialty, but ownership is the question that decides what you actually need. Match the tool to the record you're building, not to the label on the pricing page.

Want to see how a clean, signed clinical note feeds whichever record you run? <a href="/in/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a consult land as a structured note, then read how we handle data on the [security page](/in/security/).

---

## Cloud Hospital Management Systems in India: Buyer Guide
https://patientsquare.com/in/blog/cloud-based-hospital-management-system-india/
Published 2026-08-19 · Updated 2026-08-29 · Tags: hospital-management-system, cloud, small-hospital, dpdp, india

A buyer's guide to cloud-based hospital management systems for small hospitals and clinics in India: costs, DPDP data questions, and ABDM honestly.

It's an HMS delivered over a network instead of being operated solely on hardware at the hospital. The actual modules, recovery commitments, data location, and offline behaviour vary by vendor and contract.

A cloud-based hospital management system is delivered over a network instead of being operated solely on hardware in the hospital. It can reduce local infrastructure work, but it moves important questions into the contract: responsibility for access, recovery, exports, outages, and local continuity. This guide keeps the cloud and on-premise trade-off concrete.

> **Key takeaways**
>
> - Cloud and on-premise are delivery choices, not proof of workflow fit. Test connectivity, continuity, modules, operating ownership, and policy evidence.
> - Ask for a written total that identifies the selected scope, onboarding, training, tax, support, renewal, and exit terms before you compare quotes.
> - For ABDM procurement, ask which capability the software has demonstrated, what current evidence supports it, and whether it is live in production or only in the sandbox.
> - Sections 3 through 17 of the DPDP Act are scheduled to commence on 13 May 2027. Use procurement now to prepare written evidence for those duties.

## What does "cloud-based HMS" actually mean for a small hospital?

Strip the marketing and the delivery model is simple. A cloud deployment has a provider-operated service boundary; an on-premise deployment leaves more operation with the hospital. Neither label tells you which modules, records, or downtime procedures the contract includes.

For a small hospital, cloud can reduce local server maintenance and centralise updates. It also depends on connectivity and a clear outage plan. On-premise may fit a site with unreliable connectivity or a policy that requires local operation. Run both options against the same workflow and recovery test.

The trade-off is exactly that dependency. Cloud means you need connectivity, and you're trusting the vendor with uptime and with your data. Which is why the next few questions matter more than the feature list.

## How should a small hospital evaluate the options?

Feature grids run forty rows and tell you almost nothing. Six checks decide whether a cloud HMS fits a small hospital, and they're the ones vendors are least eager to answer on a call.

1. **What does the written quote include?** Ask the vendor to identify its price unit, contract term, selected scope, onboarding, training, tax, support, renewal, and exit terms. Compare only quotes that state those items.
2. **Does it fit your workflow, or must your workflow bend to it?** A system built for a large hospital can drown a 15-bed setup in fields nobody fills. Watch a demo run your actual patient journey, not the vendor's.
3. **What happens when the internet drops?** Ask specifically. Does anything work offline? How does it reconcile when you reconnect? For clinics on patchy connectivity this can be a dealbreaker, so don't let it stay vague.
4. **ABDM, with evidence.** If ABHA linking matters, ask which capability the software has demonstrated, what current evidence supports it, and whether that capability is live in production or only in the sandbox. More on why this matters below.
5. **Preparation for DPDP duties.** Sections 3 through 17 are scheduled to commence on 13 May 2027. Before signing, obtain written answers on hosting, access, exports, deletion, incident handling, and the owner for each obligation.
6. **How do you get your data out?** If you leave in two years, can you export everything in a usable format? A vendor that makes exit hard is telling you something now.

Named options help make the choice less abstract. NIC describes e-Hospital as a cloud-based HMIS on MeghRaj for government hospitals. Bahmni documents an on-site operating path without Internet dependence. Neither fact settles the decision: use the responsibility and recovery questions above to test the option that fits your facility.

## What does "ABDM-compliant" really mean, and why be skeptical?

Treat "ABDM-compliant" or "ABDM-ready" as a prompt for evidence. Ask which capability the software has demonstrated, what current evidence supports it, and whether that capability is live in production or only in the sandbox. The label alone does not answer those questions.

ABDM is a federated, consent-based framework. Ask a vendor for its current production evidence and do not turn a badge into a claim about your facility. Patient Square's ABDM integration remains on the roadmap.

Ask the vendor to answer all three questions in writing. If ABDM matters to your hospital, the [ABDM Milestone 2 explainer](/in/blog/abdm-milestone-2-explained-clinics/) unpacks what "sharing records" involves. Do not accept a status the vendor cannot support with current evidence.

We'll be straight about our own position for the same reason we tell you to press vendors: ABDM integration is on our roadmap, not shipped, and we won't badge it until it holds the certification. Hold every vendor, us included, to the same capability, evidence, and production-status questions.

## Prepare for the scheduled DPDP duties

The Act contains the relevant definitions today. Its core processing sections, 3 through 17, are scheduled to commence on 13 May 2027 under the MeitY notification G.S.R. 843(E), published 13 November 2025. That timing matters: do not describe those future duties as already operative in August 2026.

The practical use of a 2026 procurement is preparation. Ask where data is hosted, who can access it, how access is logged, how records are exported or deleted, how incidents are handled, and who owns each response. Put the answers in the contract and recheck the legal position before go-live.

## When is on-premise or a full EMR the better buy?

Cloud isn't automatically right, and a full HMS isn't automatically what you need. Two honest counter-cases.

On-premise can beat cloud when your connectivity is genuinely unreliable and no offline mode covers the gap, or when a specific policy reason means data has to stay physically in-house. For a rural setup where the link drops for hours, a locally hosted system that keeps working may serve patients better than a cloud one that stalls. The [cloud EMR vs on-premise decision guide](/in/blog/cloud-emr-vs-on-premise-india/) weighs this trade-off properly, DPDP and all.

And you might not need a full HMS. If your operation is small and your real gap is the clinical record rather than billing, pharmacy, and beds, a lighter EMR or even a documentation layer may fit better and cost less than an enterprise suite you half-use. The [HIS software roundup](/in/blog/best-his-software-india/) and the [EMR buyer's guide](/in/blog/emr-software-india-guide/) both help you tell the categories apart before you overbuy.

## Where does Patient Square fit for a small hospital or clinic?

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot. Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. It is demo-priced. A hospital must validate its required workflows and continuity plan rather than infer them from the delivery model.

## The short version

Choose cloud only when its connectivity, continuity, module scope, operating ownership, and policy evidence meet the facility's requirements. Choose on-premise when those same tests favour local operation. Treat "ABDM-compliant" as a question, not a fact: make the vendor name its current production evidence. Use the 2026 procurement to prepare for the DPDP duties scheduled for 13 May 2027.

For a hospital discussion, bring your current deployment, department mix, outage procedure, and incumbent HIS/EHR to <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>.

---

## Cloud Practice Management Software in India: Buyer Guide
https://patientsquare.com/in/blog/cloud-based-practice-management-software-india/
Published 2026-08-19 · Updated 2026-10-04 · Tags: practice-management-software, cloud, solo-doctor, dpdp, india

A buyer's guide to cloud practice management software for Indian clinics and solo doctors: scheduling, billing, records, DPDP data questions, and cost.

It's software that runs a clinic's day-to-day operations from the vendor's servers, reached through a browser: appointments and scheduling, patient registration, billing and GST invoices, and often the clinical record. 'Cloud' means nothing is installed on a machine you maintain; you log in from anywhere with internet, and updates happen centrally.

Cloud-based practice management software runs a clinic's daily operations from the vendor's servers, reached through a browser: scheduling, registration, billing, and usually the clinical record, with no machine to maintain on-site. For an Indian clinic or a solo doctor, that's an attractive setup, no server, central updates, access from the clinic or from home. The category is crowded; some vendors publish prices, while others require a quote, and the full cost depends on included features and renewals. This guide is scoped to clinics and solo doctors, not hospitals, and it focuses on the checks that decide whether the software actually pays for itself.

> **Key takeaways**
>
> - Cloud practice management software suits clinics and solo doctors: no server, central updates, access from anywhere with internet, lower upfront cost.
> - Match the tool to your bottleneck. A solo doctor may need only scheduling and records; a busy clinic gets more from billing and follow-ups too.
> - Under the DPDP Act 2023 your practice will be the data fiduciary when the core processing duties commence on 13 May 2027. Where data sits, how it's encrypted, and how you export it are questions the vendor should answer plainly.
> - "ABDM-ready" hides three milestones and is optional to running your practice. If you want it, make the vendor name the milestone and its production status.

## What does cloud practice management software cover for a clinic or solo doctor?

Practically, it's the operational spine of a small practice. Scheduling and appointment reminders. Patient registration and the basic demographics. Billing and GST invoicing. Usually the clinical record, and sometimes messaging and follow-ups. Because it's cloud, all of it lives on the vendor's servers, and you reach it through a browser from the clinic, the ward round, or your phone at home.

For a solo doctor that flexibility is the draw. No server in a cupboard, no software to reinstall when a laptop dies, no version you've fallen behind on. You log in and it's current. And you're not tied to one machine, so the setup follows you rather than the other way round.

The dependency is the flip side. Cloud needs connectivity, and it means trusting the vendor with uptime and with your patients' data. That's why the questions below matter more than any feature checklist a sales deck hands you.

## How should a clinic or solo doctor evaluate the options?

Skip the forty-row grid. Five checks decide whether cloud practice management software fits a small practice, and they're the ones vendors would rather you didn't ask on the first call.

1. **What does it actually cost, all in?** Not the entry per-user figure. Subscription plus onboarding plus every module you'll switch on, with GST stated. Make them total it before you compare.
2. **Does it match your bottleneck?** A solo doctor drowning in charting needs a different tool than a clinic losing evenings to billing and follow-ups. Buy for the fire you're actually fighting, not the feature you might use someday.
3. **What happens offline?** For clinics on patchy connectivity, ask directly: does anything work without internet, and how does it sync when you're back? A vague answer here is a real risk, not a footnote.
4. **DPDP data discipline.** Where is the data hosted, how is it encrypted, who can access it, and how do you export or delete it? Your practice will carry the DPDP fiduciary duty from 13 May 2027; get real answers now.
5. **How do you leave?** If you switch vendors in two years, can you export everything cleanly? A tool that makes exit painful is warning you now.

## What does the DPDP Act ask of a clinic running cloud software?

More than most solo doctors expect, and moving to the cloud doesn't shift the duty off you. India's Digital Personal Data Protection Act, 2023 will make your practice the data fiduciary for patients' personal data when its core processing duties commence on 13 May 2027. Clinical data is personal data. Choose a cloud vendor with those future duties and today's applicable privacy and clinical rules in mind.

That turns into a short list you ask before you sign. Where is patient data hosted? How is it encrypted in transit and at rest? Who at the vendor can access it, and is that logged? How would you export or delete a patient's records on request? A vendor built for the DPDP era answers these plainly. If the answers are hand-wavy, treat it as a real gap, because your practice will retain the DPDP fiduciary duty when it commences. The [DPDP guide for clinics](/in/blog/dpdp-act-clinics-guide/) covers what the Act expects in daily practice, and it's worth reading before you shortlist. This is the DPDP-aware framing every clinic should buy on; it's a discipline, not a certificate you can outsource.

## Is "ABDM-ready" something a solo practice needs?

Usually optional, and worth de-mystifying before it sells you a feature you don't need. ABDM, the Ayushman Bharat Digital Mission from the National Health Authority, links patient records to an ABHA number so they can move between providers on the patient's consent. It's genuinely useful and growing, but it's not required to run your own clinic well. Plenty of solo practices don't need it on day one.

If you do want it, apply the standard skepticism. "ABDM-ready" hides three milestones: creating an ABHA (M1), sharing records on consent (M2), and fetching records (M3), and certification is per-software. So the question that cuts through the badge: which milestones have you cleared, and are they live in production or still in sandbox? The [ABDM Milestone 2 explainer](/in/blog/abdm-milestone-2-explained-clinics/) unpacks record-sharing specifically. Being ABDM-ready in the honest sense is a real, checkable status, not a sticker, and the same goes for us: our ABDM integration is on the roadmap, not shipped, and we won't badge it before it holds the certification.

## When is a lighter setup or a full suite the better call?

Match scale to need, in both directions, because overbuying and underbuying both cost you.

A **lighter setup** can be enough for a solo doctor: a solid scheduler plus a good record tool may cover you without a full suite's cost and complexity. If billing is simple and you don't run a pharmacy, paying for enterprise modules you never open is waste.

A **fuller practice suite** earns its price when appointments, billing, follow-ups, and records all need to live together and your day is lost coordinating them by hand. And if you're actually a small hospital with beds and IPD, this isn't your category at all; the [cloud HMS buyer's guide for small hospitals](/in/blog/cloud-based-hospital-management-system-india/) is scoped to that, while the [cloud EMR vs on-premise decision](/in/blog/cloud-emr-vs-on-premise-india/) weighs the hosting choice with DPDP in mind. Pick the guide that matches your actual size, not your aspiration.

## Where does Patient Square fit for a clinic or solo doctor?

In a specific, honest slot: the note and the record, with practice tooling layered on as you scale. We won't pretend to be the full billing-and-pharmacy suite if that's your real need.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

For a solo doctor or a small clinic, the shape is: the scribe and scheduling at the base, a bundled AI EHR and WhatsApp messaging as you move up the plans, more automation above that. The scribe listens during the consult, takes the code-mixed Hindi and English most Indian OPDs run in, and hands back a structured note in clean clinical English in about two minutes, so the record stays consistent instead of drifting on a busy day. On the DPDP question that this guide keeps returning to: visit audio is processed in memory and discarded once the note drafts, so nothing sits on a server; notes are encrypted in transit and at rest, belong to your practice to export or delete, and we handle data to DPDP Act 2023 standards with a SOC 2 Type II audit in progress. The full posture is on our [security page](../../security/). What we're not: a full pharmacy-and-inventory HMS, or ABDM-live today. If your bottleneck is the note, the record, and the scheduling around them, that's exactly where we help. If you want the honest rundown of the whole clinic-copilot idea, the [clinic copilot software explainer](/in/blog/clinic-copilot-software-india/) covers what ships today. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## The short version

Cloud-based practice management software is a sensible default for a clinic or solo doctor: no server, central updates, access anywhere. Buy it on the checks that matter, the all-in price with GST, workflow fit, offline behaviour, DPDP data discipline, and a clean exit, rather than on feature count. Treat ABDM as optional and as a question, not a badge. And keep the scale honest: a solo practice usually needs less than the enterprise demo suggests, and a small hospital needs something else entirely.

If the specific gap in your practice is the note, the record, and the scheduling around them, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a structured note land on a real consult, then read how the data is handled on the [security page](../../security/). India pricing starts at ₹1,599 per clinician a month ex-GST (about ₹1,887 with 18% GST) on the annual plan.

---

## Are Digital Prescriptions Legal in India? (NMC + ABDM Rules)
https://patientsquare.com/in/blog/digital-prescription-rules-india/
Published 2026-08-19 · Tags: digital-prescription, e-prescription, nmc, telemedicine, india

Digital prescriptions are legally valid in India when signed correctly. What the IT Act, the NMC Telemedicine Practice Guidelines 2020, and ABDM actually require.

Yes. A prescription created and signed electronically has the same legal standing as a paper one. The Information Technology Act, 2000 gives electronic records and digital signatures legal recognition, and the NMC Telemedicine Practice Guidelines 2020 accept a digitally signed prescription shared with the patient. The signature is what makes it valid, not the paper.

Yes, digital prescriptions are legal in India. A prescription created and signed electronically carries the same legal weight as one on paper. Two things establish that: the Information Technology Act, 2000, which gives electronic records and digital signatures legal recognition, and the NMC Telemedicine Practice Guidelines 2020, which accept a digitally signed prescription shared with the patient. The catch isn't legality. It's doing it correctly: the right signature, the right format, and knowing which drugs you can't prescribe this way at all.

> **Key takeaways**
>
> - Digital prescriptions are legal. The IT Act, 2000 (Sections 4 and 5) gives electronic records and digital signatures the same recognition as writing and a handwritten signature.
> - Over telemedicine, the NMC Telemedicine Practice Guidelines 2020 require the prescription to carry the doctor's signature and registration number, in a standard format, shared with the patient.
> - The Guidelines classify drugs into List O, List A, List B, and a prohibited list. Schedule X drugs and NDPS-controlled substances can't be prescribed over telemedicine.
> - A valid e-prescription is a signed prescription you give the patient. It's not the same as transmitting it electronically to a pharmacy, which India doesn't require and most software here doesn't do.

## What actually makes a digital prescription legal?

The signature, not the medium. That's the whole answer, and it's worth understanding why.

India's Information Technology Act, 2000 does the foundational work. Section 4 gives legal recognition to electronic records: where a law asks for information to be in writing, an electronic form that stays accessible for later reference satisfies that requirement. Section 5 does the same for signatures: where a law asks for a document to be signed, a digital signature applied in the manner the government prescribes counts as a valid signature. So an electronic prescription, signed digitally, meets the "in writing and signed" bar that a prescription needs. This is why an e-prescription with a proper digital signature has the same legal recognition as a physical one.

That's the base layer for any electronic document in India. On top of it sits the specific rulebook for prescriptions issued in a teleconsultation, which is where the NMC guidelines come in.

## What do the NMC Telemedicine Practice Guidelines 2020 require?

These are the rules most doctors are actually asking about, so let's be precise. The Telemedicine Practice Guidelines were issued in March 2020 by the Board of Governors then in supersession of the Medical Council of India, and now sit under the National Medical Commission. They gave telemedicine in India a formal legal footing for the first time.

On prescriptions, the Guidelines are specific. The registered medical practitioner issues the prescription with their signature and registration number. The online prescription is to be provided in a standard format, and the Guidelines even publish a sample format. The doctor then shares a photo, scan, or digital copy of the signed prescription, or an e-prescription, with the patient by email or a messaging platform. So a valid teleconsult prescription is a signed document, in a standard shape, delivered to the patient. A bare typed list of drugs with no signature and no registration number doesn't meet that.

One point the Guidelines make that clinics sometimes miss: the FAQs the Board of Governors issued alongside them note that a Class 2 digital signature certificate is enough for issuing an e-prescription. You don't need exotic infrastructure. You need a signature the law recognises and the discipline to apply it every time.

## Which drugs can you prescribe digitally, and which can't?

This is the part that turns a legal question into a clinical-safety one, and the Guidelines take it seriously. They sort medicines into four buckets, and the bucket decides whether, and how, you can prescribe over telemedicine.

| Category | What it covers | Telemedicine status |
|---|---|---|
| List O | Over-the-counter drugs (e.g. paracetamol, antacids) | Can be prescribed; lowest restriction |
| List A | Relatively safe drugs, low abuse potential (e.g. eye drops, skin creams, some oral hypoglycaemics) | Allowed; first-time typically needs a video consult, refills more routine |
| List B | Add-on drugs that optimise an existing regimen | Allowed as an add-on to an ongoing prescription |
| Prohibited list | Schedule X drugs; substances under the NDPS Act, 1985 (benzodiazepines, phenobarbitone, methylphenidate and similar) | Cannot be prescribed over telemedicine |

The prohibited list is the line to know cold. Schedule X medicines and controlled substances under the Narcotic Drugs and Psychotropic Substances Act, 1985 are off the table for a telemedicine prescription. That constraint has caused real friction in psychiatry, where several restricted drugs are routine, and the Guidelines have been amended over time to move some agents between lists. Because the lists get revised, the honest instruction is the same one we'd give on any regulatory point: work from the current Guidelines document, not a summary written a while ago.

## Is an e-prescription the same as sending it to the pharmacy?

No, and this confusion causes the most overselling in the whole category, so it's worth spelling out.

In India, a valid e-prescription is a signed prescription in electronic form that the doctor gives to the patient. The patient then takes it to a chemist, on their phone or printed, exactly as they would a paper slip. The legal and regulatory rules above are all about that document and that handoff.

Electronic transmission of a prescription straight to a pharmacy, through a pharmacy network, so the chemist receives it without the patient carrying anything, is a different capability. In the US it's called e-prescribing and it runs on a specific network. India's rules don't require it, and most Indian clinical software doesn't do it. So when a vendor says "e-prescription," ask which one they mean. Almost always it's the signed-document sense, not pharmacy transmission. Getting this straight saves you from expecting a feature that isn't there and isn't legally required.

## Where does ABDM fit into digital prescriptions?

ABDM changes storage and sharing, not validity. Keep those separate and the picture stays clear.

The Ayushman Bharat Digital Mission, run by the National Health Authority, is building India's interoperable record layer: ABHA-linked health records that move between providers when the patient consents. A prescription can become part of that linked record, which is genuinely useful, because the next doctor can see what was prescribed before. If you're setting up the plumbing, the [ABHA linking workflow for a clinic](/in/blog/abha-linking-clinic-workflow/) walks the practical steps.

But ABDM doesn't touch whether the prescription itself is legal. That still comes from the IT Act signature and the NMC prescribing rules. ABDM governs where the record lives and how it travels; the Guidelines and the Act govern whether it's a valid prescription in the first place. Two separate questions. A prescription can be perfectly valid and never touch ABDM, and being on ABDM doesn't fix a prescription that skipped the signature.

## Where does an AI scribe fit, and where does it stop?

At the draft, and not one step past it. This is exactly where a health vendor is tempted to overclaim, so we'll be plain about the boundary.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Read the word "draft" carefully. That draft is not a prescription. It becomes one only when the registered practitioner reviews it, edits what needs editing, and applies their signature. The legal act is the signing, and it stays entirely with the clinician.

Three things the scribe does not do, stated flatly. It doesn't transmit anything to a pharmacy: no pharmacy network, no e-prescribing in the transmission sense. It doesn't apply your signature or your registration number for you. And it doesn't decide whether a drug is on List A or the prohibited list; that judgement is the doctor's. What it offers is a faster starting point: the draft is ready, structured, and consistent, so the doctor spends their time reviewing and signing rather than typing from scratch. On data handling, which a DPDP-era clinic will ask about: visit audio is processed in memory and discarded once the note drafts, notes are encrypted and belong to your practice, and we handle data to DPDP Act 2023 standards with a SOC 2 Type II audit in progress. The full posture is on our [security page](../../security/). For the buyer's-eye view of prescription software specifically, the [e-prescription legal-validity checklist](/in/blog/e-prescription-software-india-legal/) goes feature by feature, and the [NMC record-keeping guide](/in/blog/nmc-record-keeping-ai-scribe/) covers the documentation side. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## The short version

Digital prescriptions are legal in India. The IT Act, 2000 recognises electronic records and digital signatures, and the NMC Telemedicine Practice Guidelines 2020 accept a digitally signed prescription, in a standard format, shared with the patient. Know the drug lists: List O, A, and B are prescribable with conditions, and Schedule X plus NDPS-controlled substances are off-limits over telemedicine. Don't confuse a signed e-prescription with electronic transmission to a pharmacy; India requires the first, not the second. And whatever software drafts the prescription, the signature that makes it real is still yours.

If your clinic wants the drafting sped up while keeping the signing where it belongs, <a href="/in/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a prescription draft come together on a real consult, then read how we protect the underlying data on the [security page](../../security/).

---

## Patient Record Systems for Indian Clinics: Buyer Guide
https://patientsquare.com/in/blog/patient-record-management-system-india/
Published 2026-08-19 · Updated 2026-08-30 · Tags: patient-record-management, medical-record-management, emr, dpdp, india

An honest buyer's guide to a patient record management system for Indian clinics: the features that matter, NMC record-keeping, DPDP data questions, and cost.

It's the software that stores, organises, and retrieves your patients' clinical records: history, diagnoses, prescriptions, investigations, and visit notes. Some people call it a medical record management system or an EMR. The core job is the same: keep every patient's record complete, findable, and secure, so any authorised clinician can pull it up when they need it.

A patient record management system is the software that keeps your clinic's clinical records complete, findable, and secure. Some vendors call it a medical record management system, some call it an EMR, and buyers search for all three, but the core job is one thing: the clinic should be able to retrieve the required history within its measured acceptance threshold and produce the record when it is needed. This guide is a buyer-test framework for an Indian clinic.

> **Key takeaways**
>
> - "Patient record management system," "medical record management system," and "EMR" mostly name the same thing. The record is the core job; billing and pharmacy are add-ons.
> - Four buyer tests for an Indian clinic: consistent structure, measured retrieval, a documented retention schedule, and a data-protection review.
> - ABDM linking is optional to record-keeping. If you want it, require a production identity, facility linkage, consent, sharing or receipt, failure, and audit demonstration rather than trusting an "ABDM-ready" label.
> - Price the tier you'll actually use from a written quote that covers unit, term, scope, implementation, taxes, renewal, and exit.

## What is a patient record management system, and what should it actually do?

Cut through the naming first, because it causes needless confusion. "Patient record management system," "medical record management system," and "EMR" are three labels for software whose main job is the clinical record. A full EMR bolts on billing, pharmacy, or scheduling; a record-focused tool keeps it tighter. What you're buying, at the centre, is the same: a reliable home for every patient's history.

So judge it on the record, not the brochure. Start with four buyer tests. It should store visits in a consistent structure. It should retrieve the required history within a threshold the clinic measures in a representative test. It should retain records according to a documented schedule. And it should support the data-protection controls the clinic's legal and privacy review requires. Everything else is a feature to evaluate separately.

If a demo dazzles you with dashboards but fumbles those four, keep looking. The dashboards aren't the job.

## What are the four non-negotiables for an Indian clinic?

These decide whether the software earns its fee. Everything else is negotiable; these aren't.

1. **Consistent structure.** Every record should carry the same core elements, whether it's the first patient or the fortieth on a 40-patient Tuesday. Structure is what makes records searchable, auditable, and defensible. A free-text-only system that lets each note wander is a liability dressed as flexibility.
2. **Measured retrieval.** Set a representative patient-history retrieval threshold, test it in the quoted configuration, and record the result.
3. **Documented retention.** Set a retention schedule using current legal, contractual, specialty, and operational requirements. Test storage, retrieval, export, and deletion against that schedule.
4. **Data-protection review.** Review data location, encryption, access, contract terms, and the current legal position with appropriate legal and privacy advice.

Get those four right and you have a real record system. Miss any one and you've bought a nice interface with a hole in it.

## What does Indian law expect on keeping records?

This gets muddled, so start with the current status. The NMC's Registered Medical Practitioner (Professional Conduct) Regulations, 2023 were placed in abeyance from 23 August 2023. Do not treat their three-year text as a current blanket mandate.

For a buyer, the practical instruction is to obtain current legal, contractual, specialty, and operational advice, document the resulting retention schedule, and test the vendor's retention, retrieval, export, and deletion workflow against it. The [NMC record-keeping guide](/in/blog/nmc-record-keeping-ai-scribe/) explains the abeyance point in more detail.

## Does a patient record management system need ABDM?

Only if you want it, and that's a genuine choice, not a default. ABDM is an interoperability programme run by the National Health Authority. It is optional to the core job of keeping the clinic's own records well.

If you do want ABDM linking, apply the same skepticism you would to any feature claim. NHA's process separates vendor sandbox testing, exit approval, production access and keys, facility registration and linkage, and the clinic's actual go-live. Ask the vendor to demonstrate the exact production identity and facility linkage, consent, sharing or receipt, failure, and audit path in the proposed configuration. The [ABDM Milestone 2 explainer](/in/blog/abdm-milestone-2-explained-clinics/) provides additional background. Patient Square's ABDM integration remains on the roadmap, not shipped.

## When is a lighter tool enough, and when do you need a full EMR?

Don't overbuy, and don't underbuy. Both are expensive in their own way, so match the tool to your real workload.

A **record-focused tool** is a candidate when the documented gap is the record and it passes the clinic's structure, retrieval, retention, and data-protection tests. Confirm any additional scope in the written quote.

A **full EMR or clinic suite** is a candidate when the practice needs additional workflows and the quoted system demonstrates them. The [EMR buyer's guide](/in/blog/emr-software-india-guide/) helps structure that decision, and the [electronic patient record explainer](/in/blog/electronic-patient-record-india/) explains the terminology.

## Where does Patient Square fit?

The answer depends on whether you run an independent practice or a hospital. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft when the visit ends. Scheduling is listed from Assist; Patient Square EHR and WhatsApp messaging are listed from Copilot. Hospitals get Hospital Copilot.

### Verdict for an independent practice

Practice Copilot can use Patient Square EHR as the practice system of record from the Copilot tier, or work alongside an existing EHR. The scribe accepts code-mixed Hindi and English, then returns a structured note in clean clinical English when the visit ends. Visit audio is processed in memory and discarded after the note drafts; notes are encrypted in transit and at rest, belong to your practice, and can be exported or deleted. ABDM integration remains on the roadmap, not live. If your clinic needs a consistent record and a faster note rather than a broad operational suite, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> and test it on real consults. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

### Verdict for a hospital

Hospital Copilot can use the complete Patient Square HIS/EHR as the hospital system of record or work alongside an existing HIS/EHR. It is a separate, demo-priced product. Its named hospital modules include Claims Management, AI Discharge Summary, Bed / IPD Management, and AI Copilot EHR; validate every other operational requirement before purchase. Review the [Hospital Copilot page](/in/products/hospital-copilot/) with your facility size, department mix, incumbent HIS/EHR, and a difficult record handoff in mind.

## The short version

A patient record management system, whatever the vendor calls it, should pass four buyer tests: consistent structure, measured retrieval, a documented retention schedule, and a data-protection review. ABDM is optional; if you want it, require a production workflow demonstration. Buy the tier your documented requirements need, using a written quote. Do not confuse a larger feature list with evidence that the record workflow works.

For a practice, the useful next step is to run the 7-day trial on actual visits. For a hospital, the useful next step is a scoped demo that proves the record path and required workflows. The [security page](../../security/) documents the data posture. Practice pricing starts at ₹1,599 per clinician a month, the monthly equivalent on annual billing, ex-GST, or about ₹1,887 with 18% GST.

---

## Valant Alternatives (2026): Skip the Sales Cycle
https://patientsquare.com/us/blog/valant-alternatives/
Published 2026-08-19 · Updated 2026-08-27 · Tags: alternatives, behavioral-health, psychiatry, comparison

Valant is an enterprise behavioral-health EHR with quote-only pricing. Compare published-price options, ambient notes, trial setup, and clinical scope.

Two reasons show up most. First, the buying process: Valant doesn't publish pricing, so you go through a sales cycle and quote before you know your cost, and quotes commonly land in the $100 to $300 per provider per month range with implementation fees on top. Second, fit: solo and small practices often want published pricing and ambient notes rather than enterprise group infrastructure.

Practices shopping for a Valant alternative usually hit the same wall: no published price and a sales cycle before you know what you'd pay. Valant is an enterprise behavioral-health EHR, and that model fits big multi-provider groups. For a solo psychiatrist or small practice that wants to sign up this week and see the price first, it's friction. If ambient notes matter more to you than enterprise group tooling, ours starts at $79 per clinician per month on annual billing, published, no sales call; [watch it draft a note from a real session](/us/) before you shortlist.

If you run a large prescribing group with measurement-based care, we'll say it below: Valant probably earns its sales cycle. This page is for the practices it doesn't fit.

> **Key takeaways**
>
> - Valant doesn't publish pricing; you request a custom quote, and third-party estimates put it roughly at $100 to $300 per provider per month.
> - Implementation fees are commonly cited between $500 and $2,500, per third-party reviews as of this writing.
> - Valant is built for multi-provider groups: EPCS, PDMP lookups, PHQ-9/GAD-7 outcome tracking, and group billing.
> - Valant added AI-assisted ambient documentation over 2025 to 2026, but it's part of an enterprise EHR, not a standalone scribe.
> - Patient Square publishes its price: $79/clinician/month annual on Assist, $119 on Copilot with a bundled AI EHR, and a 7-day trial.

## What you're buying with Valant, and what the sales cycle protects

Valant is real enterprise software for behavioral health, and the depth is the point. It's built for multi-provider groups that need infrastructure a solo clinician never touches: EPCS controlled-substance e-prescribing, PDMP lookups at the point of prescribing, structured medication management, built-in outcome scales like PHQ-9 and GAD-7 that score and trend automatically, group billing, and reporting across a roster of clinicians. Over 2025 and 2026 Valant also added AI-assisted documentation, including ambient note generation aimed at the charting burden that burns out psychiatric providers, per third-party reviews.

The quote-only model tracks with that. When pricing scales by practice size, specialty, and which modules you turn on, a published number would mislead as often as it helps. Third-party reviews estimate Valant lands roughly in the $100 to $300 per provider per month range, with one-time implementation fees commonly cited between $500 and $2,500, as of this writing. Those are estimates, not Valant's published figures, so treat them as directional and get a real quote.

Here's the honest read. For a five-prescriber group running measurement-based care and heavy insurance billing, that infrastructure and even the implementation project can be worth it. For a solo psychiatrist or a three-person practice whose main pain is charting time, the sales cycle is friction you're paying for before you've documented a single visit.

## Published price versus quote-only: the real comparison

The category splits cleanly into tools that show you a price and tools that make you ask. That distinction matters more than any single feature when you're trying to model your actual cost.

| Tool | Pricing model | Ambient scribe as core product | Published entry price | Free trial |
|---|---|---|---|---|
| Valant | Quote only (sales cycle) | AI documentation add-on | Not published (~$100–$300/provider est.) | Demo only |
| Patient Square Assist | Published, assisted trial | Yes, included | $79/clinician/mo annual | 7 days |
| Patient Square Copilot | Published, assisted trial | Yes, included | $119/clinician/mo annual (bundled AI EHR) | 7 days |
| SimplePractice | Published, self-serve | Add-on (~$35/mo) | $49–$99/mo | 30 days |
| ICANotes | Published, self-serve | Add-on (~$49/user) | $75/mo non-prescriber; $213 prescriber | Demo only |

Valant's price range is a third-party estimate, not its published figure; everything in the Valant row carries that caveat. Competitor prices are vendor-published or third-party as of mid-2026, so confirm before signing. The point of the table isn't the exact dollars. It's that four of these five let you model your cost in ten minutes, and one requires a sales call to start.

## Where a self-serve, ambient-first platform fits

Patient Square is an AI clinical platform, and Practice Copilot brings the whole practice under one AI copilot. The AI Medical Scribe is the module most people arrive for: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit, with a bundled AI EHR, scheduling, and messaging as you move up the plan.

For a solo or small psychiatry practice, the appeal is speed in two senses. You start this week, no sales cycle and no implementation project, and you know your price before you sign. And the documentation itself is fast: a back-to-back afternoon of medication reviews turns into notes that draft themselves about two minutes after each visit ends. You correct a line and sign. On a fourteen-patient Tuesday, that's the difference between leaving on time and charting past dinner.

Three specifics for behavioral health. Audio is never stored; it's processed in memory and discarded once the note drafts, so there's no recording archive to explain to a patient. The safeguards are HIPAA compliant with BAAs available for every customer, with the receipts on our [security page](/us/security/). And the prescription output is a draft you review and sign, not an EPCS transmission. For Schedule II through V medications that draft won't send to a pharmacy, and most states now require DEA-registered EPCS, so keep a dedicated EPCS tool. The [full plan breakdown](/us/pricing/) shows what lands at each tier.

What we won't claim: Valant's EPCS, PDMP integration, PHQ-9 and GAD-7 outcome tracking, or group billing infrastructure. We think a lot of tools oversell exactly there, so we'll be the page that doesn't. If measurement-based care across a prescribing group is the job, Valant does it better.

## When Valant is the better fit

Plainly: if you run a multi-provider behavioral-health group with several prescribers, keep Valant on your shortlist and take the sales call. The EPCS, PDMP lookups, built-in outcome scales, and group billing are the center of gravity for exactly that kind of practice, and the implementation project buys a configured system across your whole roster. For five or more prescribers running measurement-based care, that depth usually earns the friction of the sales cycle.

Valant also wins if EPCS for controlled substances needs to live inside your EHR rather than in a connected tool. Patient Square's prescription output is a draft, not a transmission, so a prescribing group that wants EPCS built into the record system is better served by Valant. That's a real gap, and pretending otherwise would be selling you one.

The choice tips toward a self-serve alternative when you're a solo clinician or a small practice, you want to see the price and start without a sales cycle, and your biggest daily cost is documentation time rather than group reporting. That's a large share of behavioral health, and it's the share for which an enterprise sales motion is overhead.

## How to shortlist without a sales cycle

You don't need three demos to make this call. Run this instead:

1. Count your prescribers and your monthly claim volume. If it's a large prescribing group running outcome scales, Valant belongs on the list. If not, weigh self-serve tools first.
2. Model your real cost on the tools that publish prices: seat count times the annual per-clinician rate, plus any add-ons. Compare that to Valant's estimated $100 to $300 range once you have a quote.
3. Write down the hours you spent charting last month. That's the number an ambient scribe attacks directly.
4. Run our 7-day trial on real med-management sessions, with patient consent, and compare the drafts to your current notes.
5. Decide with your cost model and your charting hours in front of you, not a slide deck.

If the drafts hold up on your actual session types, book a short demo and we'll run it live against a real intake or med-management visit. For the wider field and how each behavioral-health EHR prices its scribe, see our [best EHR for psychiatry comparison](../best-ehr-for-psychiatry/), and if a session-first interventional tool is your other option, [Osmind alternatives](../osmind-alternatives/) covers that branch.

---

## Ayurveda Clinic Management Software (2026)
https://patientsquare.com/in/blog/ayurveda-clinic-management-software-india/
Published 2026-08-18 · Updated 2026-08-27 · Tags: ayurveda, clinic-management-software, ayush, panchakarma, india

What Ayurveda clinic management software should do: prakriti records, panchakarma scheduling, dispensary tracking, and NCISM record-keeping for AYUSH clinics.

It's the system that runs an Ayurveda or AYUSH clinic day to day: patient registration, prakriti and dosha assessment records, panchakarma therapy scheduling across multiple days, dispensary and herbal-formulation stock, billing, and clinical notes. A general EMR built for allopathy usually can't hold prakriti records or a multi-day panchakarma plan without workarounds.

If you run an Ayurveda or AYUSH clinic, most "clinic management software" on the market was built for an allopathic OPD and bent to fit yours. That shows the moment you try to record a patient's prakriti, plan a 14-day panchakarma course, or track a dispensary full of classical formulations. Good Ayurveda clinic management software handles those three natively: constitution and dosha records, multi-day therapy scheduling, and herbal-formulation stock. Registration and billing, most tools do. These are where they fall down.

> **Key takeaways**
>
> - The three features that separate real Ayurveda software from a generic EMR: prakriti and dosha records, panchakarma course scheduling across days, and dispensary tracking for classical formulations.
> - The NCISM Board of Ethics and Registration Regulation, 2022 asks a registered ISM practitioner to keep patient records for three years, or hand them to the patient after OPD. Your software should make that painless.
> - The Health Facility Registry covers AYUSH facilities, so ABDM linking is possible in principle, but confirm milestone status per vendor rather than trusting an "ABDM-ready" label.
> - A clinic management suite and an AI scribe solve different problems. Decide whether your pain is running the clinic or writing the note before you buy either.

## What does Ayurveda clinic management software have to do that a general EMR doesn't?

Three things, and a generic system fumbles all three.

The first is the **prakriti record**. An Ayurveda consultation starts with constitution: vata, pitta, kapha, the patient's dominant dosha and the current imbalance. That's not a free-text box tacked onto an allopathic intake form. It's structured clinical data that drives the whole treatment plan, and it should be recorded as such and carried forward across visits. A general EMR has nowhere to put it, so it ends up scattered in notes.

The second is **panchakarma scheduling**. A panchakarma course isn't one appointment. It's a sequence, snehana, swedana, then the main procedure, spread across days or weeks, each step needing a therapist, a table, and often a specific time of day. A single-slot calendar can't hold that shape. You end up managing the course on paper while the software manages only the individual visits.

The third is the **dispensary**. Ayurveda clinics dispense classical and proprietary formulations, often prepared or repackaged in-house, with their own batches and expiry. Tie that to the prescription and stock drops as you dispense. Leave it disconnected and you're counting jars by hand every month.

If a tool handles registration, billing, and appointments but treats those three as afterthoughts, it's an allopathic EMR wearing an Ayurveda label.

## How should you evaluate the options for an AYUSH clinic?

Skip the forty-row feature grid. Five questions decide whether a tool actually fits an Ayurveda practice.

1. **Does it hold a structured prakriti and dosha record?** Not a notes field. A real constitution record that persists across visits and shapes the plan. This is the single clearest tell that software was built for AYUSH, not adapted to it.
2. **Can it schedule a whole panchakarma course, not one visit?** Ask to see it plan a 14-day therapy with therapist and room assignments. If the demo only books single appointments, that's your answer.
3. **Does the dispensary connect to the prescription?** Dispensing should draw down stock, track batches and expiry, and handle in-house formulations. A disconnected inventory module is barely better than a spreadsheet.
4. **Does it make NCISM record-keeping easy?** The regulation expects a three-year retrievable record. Your software should store, structure, and retrieve that without you back-filling before an inspection.
5. **Where does the data sit, and under what terms?** Since the [DPDP Act 2023](/in/blog/dpdp-act-clinics-guide/), every clinic is a data fiduciary. Patient constitution, history, and formulations are personal data. Ask where it's hosted and how it's protected before you sign.

## What does the NCISM regulation actually ask of your records?

This one gets skipped, and it shouldn't. Ayurveda practice in India is regulated by the National Commission for Indian System of Medicine (NCISM), which replaced the Central Council of Indian Medicine in June 2021. Its Board of Ethics and Registration Regulation, 2022 sets the conduct rules for registered ISM practitioners, and record-keeping is in there.

The clause is specific. A registered practitioner must maintain the medical records for indoor and outdoor patients for **three years from the date of commencement of treatment**, or hand all records to the patient immediately after the OPD consultation. The [operative code for allopathic doctors](/in/blog/nmc-record-keeping-ai-scribe/) differs: its three-year retention clause specifically names indoor records.

So the record-keeping question isn't cosmetic. Can your software store three years of structured records, retrieve a patient's history in seconds, and keep it legible and dated? A clinic that documents cleanly every day meets this by default. A clinic that scribbles three lines per consult is one inspection away from a gap it can't fill retroactively.

## Can an Ayurveda clinic connect to ABDM and ABHA?

In principle, yes, and this is where "ABDM-ready" claims need a second look.

The good news for AYUSH clinics: the Health Facility Registry, one of the ABDM building blocks run by the National Health Authority, explicitly covers traditional-medicine facilities, including Ayurveda, Unani, Siddha, Sowa-Rigpa, and Homeopathy. The Ministry of AYUSH also runs its own Ayush Grid for the sector. So an Ayurveda clinic isn't shut out of India's digital-health stack. It can register on the HFR and, with the right software, link records to ABHA.

The caution is the same one every clinic buyer needs. "ABDM-ready" on a pricing page hides three different milestones: creating an ABHA (M1), sharing records on consent (M2), and fetching records (M3). Certification is per-software. So the question to any Ayurveda-software vendor is precise: *which ABDM milestones have you cleared, and are they live in production or still in sandbox?* A tool that can mint an ABHA but can't yet share records is half-built, whatever the badge says. If ABDM linking matters to you, the [ABDM Milestone 2 explainer](/in/blog/abdm-milestone-2-explained-clinics/) unpacks what "sharing records" actually involves.

## Where does a clinic management suite fit, and where does a scribe fit instead?

Be honest about which problem you're solving. They're different problems, and the wrong buy wastes money.

You need a **full Ayurveda clinic management suite** when your day is lost to running the clinic: scheduling panchakarma courses, chasing dispensary stock, billing, managing therapists across rooms. That's an operations problem. A documentation tool won't touch it.

You need a **documentation layer** when your clinical care is fine but your evenings go to writing up consultations, and your notes drift in quality as the day gets busier. That's a note problem. An ambient scribe sits on top of whatever you already run and fixes only the note.

Plenty of Ayurveda clinics have the first problem, and for them a dedicated AYUSH management system beats anything we make. If you dispense heavily and run multi-therapist panchakarma, start your shortlist with purpose-built AYUSH software. We won't pretend to be that.

## Where does AI Medical Scribe by Patient Square fit for an Ayurveda clinic?

In the documentation slot, and only there. We're not an Ayurveda clinic management system. We don't schedule panchakarma or run your dispensary, and we won't claim to.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

For an Ayurveda consult, the useful part is consistency. The scribe listens during the consultation, takes the code-mixed Hindi and English most Indian OPDs actually run in, and hands back a structured note in clean clinical English about two minutes after the visit. Whether it's your first patient or your fortieth, the note has the same structure, which is exactly what the NCISM three-year record expects. Visit audio is processed in memory and discarded once the note drafts, so there's no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. Notes belong to your practice to export or delete, data is encrypted in transit and at rest, and a SOC 2 Type II audit is in progress. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The honest boundary: the scribe structures what was said in the room. It doesn't hold a formal prakriti assessment as its own data type, and it isn't your management system. If your pain is the note, it helps. If it's running the clinic, buy the management suite first. The [clinic management software scorecard](/in/blog/best-clinic-management-software-india/) weighs the wider field, and if you also want the scribe side for an AYUSH setting, the [scribe write-up for Ayurveda clinics](/in/blog/ai-scribe-for-ayurveda-clinics-india/) goes deeper.

## The short version

Ayurveda clinic management software earns its name on three features a generic EMR skips: structured prakriti records, panchakarma course scheduling, and a connected dispensary. On top of that, it should make the NCISM three-year record-keeping expectation easy, and if ABDM linking matters, make the vendor name its milestone. Decide first whether your real problem is running the clinic or writing the note. A management suite fixes the former; a scribe fixes the latter, and only that.

Want to see how a consistent, structured note lands on a real Ayurveda consult in about two minutes? Book a short demo and bring a recent visit, then read how we protect records on the [security page](../../security/). India pricing starts at ₹1,599 per clinician a month ex-GST (about ₹1,887 with 18% GST) on the annual plan.

---

## TheraNest Alternatives: Switching During the Ensora Rebrand
https://patientsquare.com/us/blog/theranest-alternatives/
Published 2026-08-18 · Updated 2026-08-27 · Tags: alternatives, behavioral-health, theranest, comparison

TheraNest is now Ensora Mental Health, and pricing moved per-therapist. Alternatives for practices rethinking the stack, plus a bundled AI EHR from $119.

As of this writing, TheraNest has been rebranded to Ensora Mental Health, part of Ensora Health (formerly Therapy Brands). The vendor's pages still use the TheraNest name on some pricing URLs. If you're mid-evaluation, expect to see both names, and check which product a given page is describing before you compare features or price.

TheraNest is now Ensora Mental Health, and the rebrand came with a pricing change from per-client to per-therapist. If that shift pushed your bill up, or the name confusion has you re-shopping, the honest alternative question is what you actually want the tool to do. If it's the note-writing, Patient Square's Copilot plan is **$119 per provider per month** on annual billing with an ambient scribe bundled in. You can [watch it draft a note in about two minutes](/us/) before you decide.

Straight up front: Patient Square isn't behavioral-health-specific, and TheraNest is. That trade runs through this whole page.

> **Key takeaways**
>
> - TheraNest rebranded to Ensora Mental Health, and pricing moved from per-client to per-therapist, which raised the bill for some group practices.
> - Published TheraNest pricing starts around $29 per first therapist per month; the AI Session Assistant is a ~$35/provider add-on.
> - TheraNest's edge is therapy-native admin: superbills, panels, treatment-plan templates.
> - Patient Square Copilot is $119/provider monthly (annual) with an ambient scribe and bundled AI EHR, no per-note meter.
> - Stay with TheraNest if your pain is claims and panels, not documentation.

## Why are TheraNest users shopping alternatives now?

A rebrand plus a pricing model change is the moment people re-shop. Both happened here.

In April 2025, per EHR Source, Therapy Brands rebranded to Ensora Health, and TheraNest became Ensora Mental Health. The product didn't change much, but the name, login URLs, and documentation references did, and users reported confusion about whether they were even on the same tool. That's a small thing until you're training a new front-desk hire against docs that say two different names.

The bigger nudge is money. Ensora's own pricing announcement describes a shift from per-client to per-therapist billing. If you ran a large caseload with a few clinicians, per-client math used to work in your favor. Per-therapist math doesn't. Some group practices saw their bill go up for the same work. When the pricing logic under your tool changes, it's worth checking whether the tool is still the right one.

If you're at that fork, [see what a flat per-provider bundle covers](/us/) and compare it to your new Ensora quote.

## TheraNest alternatives at a glance

The field splits by whether your daily friction is admin or documentation.

| Alternative | Best for | Ambient scribe | Published starting price |
|---|---|---|---|
| TheraNest / Ensora (staying) | Therapy-native admin, panels, superbills | Add-on (~$35/provider/mo) | ~$29/therapist/mo |
| Patient Square Copilot | Clinicians who want notes drafted from the session | Yes, bundled | $119/provider/mo (annual) |
| General EHR + separate scribe | Custom stacks | Separate subscription | Varies |

Competitor figures are Ensora's published or third-party numbers as of this writing; confirm before you sign. This table is direction, not a quote.

If the note-writing is your problem, [start with the ambient option](/us/). If it's the insurance and superbill workflow, TheraNest's therapy-native tooling is hard to beat.

## The AI Session Assistant is an add-on, not a built-in scribe

TheraNest offers an AI Session Assistant, and for some clinicians it's enough. But it prices as an add-on, roughly $35 per provider per month per Ensora's pricing, layered onto a practice-management tool. Stack that with the annual AMA CPT license fee near $19.50 per therapist and extra admin-user seats, and the "$29 to start" headline drifts a long way from your real bill.

An ambient scribe built into the core plan works differently. It listens during the session and hands back a structured note the moment you finish. You're not opening an assistant and filling a template after the fact; the draft is already there. For a therapist running seven or eight sessions a day, that's the gap between charting until 7pm and closing the laptop when the last client leaves.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. Book a demo and run it against a real talk-based visit to see if the note holds.

## What an ambient scribe changes for a talk-heavy practice

Behavioral-health visits are conversation from start to finish, which is what ambient capture is built for. Concretely:

- **The note drafts from the session.** Ambient capture during the visit, structured note ready about two minutes after you finish.
- **Unlimited notes, no per-session meter.** A packed Tuesday costs the same as a quiet Friday.
- **A prescription draft** for prescribers, reviewed and signed by you. It's a draft, not automated pharmacy transmission.
- **Audio is never stored.** It's processed in memory and discarded once the note drafts, which matters for the privacy expectations of mental-health work.
- **One bundled bill** for the scribe and the record system, instead of a base plan plus an AI add-on plus an e-prescribe add-on.

The privacy line deserves its own note. Sessions are sensitive, and a scribe that keeps no audio archive is a cleaner story to tell a client than one that retains recordings. Patient Square's safeguards are HIPAA compliant, with BAAs available for every US customer, and the full posture is on the [security page](/us/security/). For the prescriber-side specialty view, our [best EHR for psychiatry](../best-ehr-for-psychiatry/) roundup goes deeper.

## What the real TheraNest bill looks like after add-ons

The "$29 to start" headline is the base tier for the first therapist. Your actual monthly number depends on how many of the pieces you need bolted on, and behavioral-health practices usually need a few.

Walk the stack. The base plan starts around $29 per first therapist. On top of that sits the annual AMA CPT license fee, near $19.50 per therapist, which you pay whether you code heavily or not. Extra admin users carry their own monthly seats. And if the note-writing is your actual pain, the AI Session Assistant is roughly $35 per provider per month on top of everything else. For a three-clinician group that wants the AI help, you're stacking three base seats, three CPT fees, and three assistant add-ons before you count admin logins.

Compare that to a single per-provider price that already includes the ambient scribe, the AI EHR, scheduling, and messaging at the Copilot tier. We're not saying the flat bundle is cheaper in every scenario; a solo therapist on TheraNest's base tier who never touches the AI add-on pays less than $119. We think the honest comparison is like-for-like: once you add the AI note help most people actually want, the add-on math on TheraNest closes the gap fast. Run your own numbers with your seat count before you assume either way.

## When TheraNest (Ensora) is the better choice

Here's the honest concession. Stay with TheraNest if your practice runs on therapy-native admin. It ships treatment-plan templates, superbills, insurance-panel workflows, a client portal, and group-practice billing built for behavioral health. Patient Square doesn't replicate that. If your daily friction is claims, panels, and client-facing scheduling rather than note-writing, TheraNest is the tool that fits, and switching away would trade a workflow you rely on for a scribe you might not need.

TheraNest is also the safer pick if you bill insurance heavily and lean on its claims tooling. Patient Square offers ICD-10 suggestions, not a claims-management engine. We think most practices should pick the tool that solves the pain that actually costs them time, and for a claims-heavy group, that's still TheraNest.

For practices whose main complaint is documentation load, the math tilts the other way: the bundle drafts the note and holds the record, and the note-writing evening goes away.

## How to switch off TheraNest without losing a clinic day

If you decide to move, plan the cutover instead of winging it:

1. Name your worst daily friction first: notes, or admin. That picks your category before you shortlist.
2. Run a full data export from TheraNest. As the account owner you can export clinical notes, billing docs, and client records; confirm the format your new tool accepts.
3. Recreate or import clients and schedules in the new tool during a low-volume week, not month-end.
4. Request the new tool's assisted 7-day trial and run it across a real week of sessions before you move anything live.
5. Compare the finished note to what you'd have written yourself. That's the actual decision.

For the broader switch playbook, our [AI scribe migration checklist](../switch-ai-scribe-migration-checklist/) covers the clinic-day logistics, and the [pricing page](/us/pricing/) lists the full ladder with no asterisks. Book a short demo to check the note against a real visit, then request a 7-day trial before you migrate. If the rebrand and the new per-therapist bill have you rethinking the stack, that's the right time to test whether an ambient scribe fixes the part TheraNest's admin tools were never built for.

---

## TherapyNotes Pricing 2026: Base, Add-Ons, and Calculator
https://patientsquare.com/us/blog/therapynotes-pricing/
Published 2026-08-18 · Updated 2026-08-29 · Tags: pricing, behavioral-health, therapynotes, comparison

Calculate TherapyNotes cost using current solo and group rates, TherapyFuel, telehealth, ePrescribe, claims, ERA, eligibility, reminders, and payments.

TherapyNotes currently lists $69 per month for one solo user. Group pricing is $79 for the first clinician plus $50 for each additional clinician, with unlimited non-clinical users. Enterprise uses the group rates and requires at least 30 users. Recheck the official support article before buying.

TherapyNotes costs $69 a month for a solo user, but that is only the first row. A practice may also pay for TherapyFuel, premium telehealth, ePrescribe, eligibility checks, claims, ERA items, reminders, MIPS reporting, and card processing.

None of those charges is hidden. The mistake is leaving them outside the comparison.

> **Price snapshot, rechecked August 11, 2026**
>
> - Solo: $69 monthly for one user.
> - Group: $79 for the first clinician and $50 for each additional clinician.
> - TherapyFuel: $40 per enabled clinician monthly.
> - Premium Telehealth: $15 per clinician monthly; Basic Telehealth is included.
> - ePrescribe: $65 per prescriber monthly.
> - Electronic claim, ERA claim, eligibility request, and text or voice reminder: $0.14 each.

## The current TherapyNotes rate card

The first-party support article is unusually useful because it lists both subscription and usage charges. Keep the date beside your spreadsheet. Prices and agreements can change.

| Line item | Current public rate | Billable unit |
|---|---:|---|
| Solo subscription | $69/month | One solo user |
| Group subscription | $79 + $50 for each additional clinician | Clinician seats |
| Enterprise | Same group rates, 30-user minimum | Account and clinician mix |
| Non-clinical users | Included, unlimited | Practice admins, schedulers, billers |
| TherapyFuel | $40/month | Each enabled clinician |
| Basic Telehealth | Included | Up to two participants per official page |
| Premium Telehealth | $15/month | Each enabled clinician |
| ePrescribe | $65/month | Each prescriber |
| Electronic claim | $0.14 | Each claim |
| Mailed paper claim | $1.00 | Each claim |
| ERA | $0.14 | Each claim in an ERA |
| Real-time eligibility | $0.14 | Each request |
| Text or voice reminder | $0.14 | Each reminder |
| Email reminder | Included | Each reminder |
| Card processing | 3.1% + $0.30 | Each transaction, plus possible agreement fees |
| MIPS reporting | $359/year | Each clinician |
| Storage-only account | $9 + $3 for each additional user monthly | Read-only record access |

TherapyNotes says every standard plan includes a 30-day trial, client data import, unlimited clients, appointments and notes, messaging, a custom portal, Basic Telehealth, file storage, backups, and 24/7 phone and email support. Those inclusions make the base plan materially different from a scheduler or note-only tool.

## The calculator

Use a normal month, not the quietest one in the year. Let:

- **C** = number of clinicians;
- **A** = clinicians using TherapyFuel;
- **T** = clinicians using Premium Telehealth;
- **P** = ePrescribe users;
- **Q** = electronic claims;
- **E** = claims represented in ERA files;
- **R** = real-time eligibility requests;
- **M** = paid text or voice reminders;
- **V** = card volume in dollars;
- **N** = number of card transactions.

For a group with at least one clinician:

**Monthly cost = $79 + $50 × (C - 1) + $40A + $15T + $65P + $0.14(Q + E + R + M) + 3.1%V + $0.30N**

Add MIPS at $359 per participating clinician per year. Add $1 for every mailed paper claim. Do not include card processing when the practice does not use the integrated merchant service.

For a solo user, replace the group base with $69.

## Three worked examples

These are buyer-entered scenarios, not typical bills.

### Solo, cash pay, AI notes

A solo therapist uses TherapyFuel, Basic Telehealth, email reminders, and no insurance or integrated cards:

**$69 + $40 = $109 per month.**

The comparison is clean because usage charges are zero.

### Solo psychiatric prescriber

One prescriber uses TherapyFuel, Premium Telehealth, and ePrescribe:

**$69 + $40 + $15 + $65 = $189 per month before claims, ERA, eligibility, reminders, cards, or MIPS.**

That $65 ePrescribe row may be decisive. Patient Square creates a prescription draft for clinician review but does not transmit it to a pharmacy.

### Three-clinician insurance group

Three clinicians use TherapyFuel; two use Premium Telehealth; one uses ePrescribe. Before transaction fees:

**$79 + (2 × $50) + (3 × $40) + (2 × $15) + $65 = $394 per month.**

Now add the group's actual claims, ERA items, eligibility checks, reminders, and payments. If a claim later appears in an ERA, those are two separate 14-cent units in the official rate card. Count both.

## What TherapyFuel changes

TherapyFuel is the AI line item. The current support article prices it at $40 per clinician per month. It also says that enabling TherapyFuel for at least one clinician lets the whole practice use Generate Client History Summaries and Generate Contact Notes at no additional charge.

That does not make every AI function practice-wide. During a trial, name the clinician-specific functions you need and confirm which seats must be enabled. Also test the note type, group-session workflow, corrections, consent, and export. A $40 add-on is inexpensive only if it handles the sessions that create the work.

## Claims and payment costs are usage based

Fourteen cents sounds negligible until it is multiplied across several events. An insurance visit can create an eligibility request, an electronic claim, an ERA line, and a reminder. TherapyNotes may still be a strong value because those events remain inside its behavioral-health workflow. The calculator simply prevents the $69 headline from standing in for the invoice.

Card processing needs a separate read. The Help Center lists 3.1% plus 30 cents per transaction, says CardConnect manages the service, and warns that card-network and incidental fees can apply. The merchant agreement controls. For $20,000 in monthly integrated card volume across 200 transactions, the displayed formula alone is $680:

**3.1% × $20,000 + $0.30 × 200 = $680.**

That is a payment-processing cost, not an EHR subscription. Keep it in the total only when comparing payment workflows.

## TherapyNotes versus Patient Square

The products overlap on documentation and practice workflow, but they are not substitutes row for row.

| Buyer need | TherapyNotes | Patient Square |
|---|---|---|
| Behavioral-health EHR base | Included in subscription | AI Copilot EHR begins on Copilot |
| AI note workflow | TherapyFuel at $40 per clinician | Scribe included on every plan |
| Scheduling | Included | Begins on Assist |
| Client portal | Included | Not publicly listed as a module |
| Claims, ERA, eligibility | Built in with published usage fees | Not a full claims, clearinghouse, or eligibility system |
| Pharmacy transmission | ePrescribe, $65 per prescriber | Prescription draft only; no transmission |
| Premium telehealth | $15 per clinician | Not publicly listed as a module |
| Starting published price | $69 solo | Assist $99 monthly or $79 annual monthly equivalent |
| Bundled-EHR tier | Base product is an EHR | Copilot $149 monthly or $119 annual monthly equivalent |

TherapyNotes is the stronger fit when behavioral billing, portal, telehealth, or ePrescribe is central. Patient Square is worth testing when the main purchase is ambient documentation with scheduling, or when a practice wants the bundled AI Copilot EHR and WhatsApp at the Copilot tier.

The free trials answer different questions. TherapyNotes lists a 30-day trial on its standard plans. Patient Square has a 7-day free trial. Use each one to test the job you would actually replace. For TherapyNotes, that may mean claims, reminders, portal activity, and a prescribing workflow. For Patient Square, it means the review quality of the structured SOAP note and the work around it. A trial is useful only when the team records what still has to happen after the note is generated.

Patient Square's public output is a structured SOAP note, ICD-10 suggestions, and a prescription draft for review. It does not promise DAP or BIRP output on the pricing page. A therapist should test whether the output and specialty-aware templates fit, rather than infer behavioral depth from the word EHR.

## Compare the cost against the job

The relevant alternative is not always a cheaper product. TherapyNotes can be worth its full monthly cost when the practice uses its behavioral-health billing, client portal, telehealth, ePrescribe, and record workflow. Those are not incidental extras for an insurance-heavy group. A lower note-tool subscription would not replace them.

The comparison changes for a practice that already has a working billing and pharmacy path and is shopping because notes are consuming evenings. In that case, price the exact documentation seats rather than treating a complete therapy platform as the baseline. Patient Square Assist is $99 month-to-month or $79 per clinician per month as an annual monthly equivalent. Copilot is $149 month-to-month or $119 annual monthly equivalent and adds the bundled AI Copilot EHR and WhatsApp messaging. Autopilot is $249 month-to-month or $199 annual monthly equivalent. Those prices cover different scopes from TherapyNotes.

Patient Square's prescription output remains a draft for clinician review. It is not pharmacy transmission. Its EHR-ready export (PDF · HL7 · FHIR) is an export statement, not a claim that it will write back into TherapyNotes or another record. Keep the existing record path where it owns work Patient Square does not publicly list.

## Contract and PHI questions to settle

HHS explains that selling software alone does not make a vendor a business associate, while hosting or support access to PHI can. Establish the role and execute the required BAA before that access begins.

For TherapyNotes, get these answers in the order form and agreements:

1. Which users count as clinicians, non-clinical staff, interns, or prescribers?
2. Which TherapyFuel functions require a paid seat?
3. Which transaction types can trigger more than once per encounter?
4. What do the merchant and ePrescribe agreements add?
5. What happens to price and data access when users leave?
6. What is included in migration, and how is a sample export validated?

The [best EHR for therapists](../best-ehr-for-therapists/) uses those answers as disqualifiers. The [AI scribe for therapists](../ai-scribe-for-therapists/) covers consent and sessions that should not be recorded. Request your 7-day trial if the documentation workflow is the missing piece.

## Patient Square and your existing record system

Practice Copilot can use the bundled AI Copilot EHR from the Copilot tier, or work alongside an existing EHR. Neither route promises automatic filing or write-back into a third-party EHR.

---

## Integrated HMS for Multispecialty Hospitals in India
https://patientsquare.com/in/blog/integrated-hms-multispecialty-india/
Published 2026-08-17 · Updated 2026-08-30 · Tags: integrated-hms, multispecialty-hospital, abdm, dpdp, india

Why multispecialty hospitals in India need an integrated HMS, not a stack of modules: the integration points that matter, the silos that hurt, and how to test.

It's a hospital management system where the modules, registration, OPD and IPD records, pharmacy, lab, billing, and claims, share one patient index and talk to each other, rather than being separate tools bolted together. In a multispecialty hospital, where a patient moves between departments, the integration is the whole value. A stack of disconnected modules recreates the paper silos digitally.

A multispecialty hospital lives or dies on handoffs. A patient booked in cardiology, sent for a lab, admitted overnight, dispensed medication, and billed at discharge is a single journey crossing five departments. If your hospital management system treats those as five separate tools, you've digitised the paper silos without removing them. This guide is narrow on purpose: not which HMS to buy, but what "integrated" has to mean for a multispecialty hospital, which integration points actually decide whether the software works, and how to catch a fake integration in a demo before you sign.

> **Key takeaways**
>
> - In a multispecialty hospital the integration is the product. Disconnected modules just recreate department silos on screen.
> - Test handoffs, not modules: OPD-to-admission, lab-order-to-result, dispense-to-bill. Any handoff that needs re-keying is a silo the brochure hid.
> - Do not treat ABDM sandbox testing or an integration listing as proof of a hospital's live production transaction. Ask for the exact production identity, facility linkage, consent, sharing or receipt, failure, and audit demonstration.
> - The DPDP Act's core processing obligations have a phased commencement. Obtain current legal advice, then test whether access controls and records can work consistently across every module.

_Sources: MoHFW EHR Standards 2016; National Health Authority._

## What does "integrated" actually mean in a multispecialty HMS?

That the modules share one patient index and pass data between themselves without a human re-typing it. That's the whole test, and it's easy to fail. Plenty of systems marketed as an HMS are really a bundle of separately-built tools sharing a login screen. Registration knows the patient; the lab module doesn't. The pharmacy dispenses; the bill doesn't know. Each department works, but the seams between them leak.

In a single-specialty clinic you can sometimes live with that, because the patient doesn't travel far. In a multispecialty hospital you can't, because travelling between specialties is the entire point of the place. India's EHR Standards, published by the Ministry of Health and Family Welfare and revised in 2016, push toward exactly this: a shareable, standards-based record so the data means the same thing wherever it moves. An integrated HMS is that principle applied inside one building. Our [HMS modules explainer](../hospital-management-system-explained/) maps the individual modules; this post is about what has to connect them.

## Why does integration matter more in a multispecialty setup?

Because the cost of a silo scales with the number of departments a patient crosses. A GP clinic has one handoff worth worrying about. A multispecialty hospital has dozens, and each disconnected seam is a place where data gets re-entered, a result gets lost, or a bill misses a charge.

Picture a real journey. A patient sees cardiology in the OPD, gets an ECG and bloods ordered, is admitted to a ward, has medication charted and dispensed, sees a nephrology consult during the stay, and is billed at discharge with the TPA claim filed. In an integrated HMS, that's one record accreting detail as the patient moves. In a bolted-together stack, it's five or six systems, each holding a fragment, and a staff member stitching them by hand at every step. The integrated version isn't just tidier; it's fewer errors, less duplicate data entry, and a whole picture at the point of care. For the claims side specifically, our [hospital revenue cycle guide](../hospital-revenue-cycle-management-india/) covers how billing integration affects reimbursement, and the [bed management guide](../bed-management-system-hospital-india/) covers IPD flow.

## Which integration points actually decide whether it works?

The handoffs, not the modules in isolation. A vendor will happily demo each module looking polished on its own. The value, and the failure, lives in the seams between them. These are the ones to test:

| Handoff to test | What "integrated" looks like | The silo tell |
|---|---|---|
| OPD to IPD admission | The OPD record follows the patient into the ward | Ward staff re-register or re-enter history |
| Lab order to result | Result lands back in the same chart automatically | Results arrive in a separate lab system |
| Prescription to pharmacy | Dispense ties to the order and the patient | Pharmacy re-keys the drug list |
| Charge to bill | Every service billed flows to one invoice | Charges missed or reconciled manually |
| Record to ABDM / export | Consent-based sharing or clean export from one place | Each module exports its own fragment |

The single most revealing move in a demo: ask them to admit a demo patient from the OPD and show the record following the move, live, without re-keying. If that handoff is clean, most of the others usually are too. If it needs a re-type, you've found the silo the sales deck hid. We think buyers spend too long scoring individual modules and not enough time forcing these handoffs in front of the vendor.

## What should a multispecialty hospital ask about ABDM integration?

Ask for the production path, not a shorthand label. NHA's process separates vendor sandbox functional and security testing, exit approval, production access and keys, facility registration and linkage, and a hospital's actual go-live. An integration listing or sandbox result does not establish that the hospital's proposed configuration can complete a live transaction.

Ask the vendor to demonstrate, with the hospital's proposed identity and facility configuration:

1. identity and facility registration or linkage;
2. the consent path;
3. the specific sharing or receipt flow the hospital needs;
4. a failed transaction and the recovery path; and
5. the audit record available to the hospital.

Record the environment, software version, date, and responsible party for each result. Our [ABDM Milestone 2 explainer](../abdm-milestone-2-explained-clinics/) provides additional background on consent-based sharing.

## How does DPDP interact with an integrated HMS?

The DPDP Act is a phased regime, not a completed checklist. The 13 November 2025 notification sets sections 3 to 17, including processing, notice, consent, and fiduciary-obligation provisions, to commence 18 months after publication. Get current legal and privacy advice on the hospital's applicable obligations and the controls it should prepare to operate.

Here's the practical evaluation point for a multispecialty hospital: an integrated record may be easier to govern than five silos if one set of controls works across the whole patient journey. But that only holds if access control genuinely spans every module. An "integrated" HMS where each department has its own login and its own permissions has integration in the demo and silos in the audit. Ask whether role-scoped, logged access, consent records, and export or deletion on request work uniformly across all modules or per-tool. Our [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers the framework and should be read with current legal advice.

## Where does an AI scribe fit in a multispecialty hospital?

The ambient scribe fits at the documentation layer, while the record system has two deployment paths. Hospital Copilot can use the complete Patient Square HIS/EHR as the hospital's integrated record or work alongside an incumbent HIS/EHR. Practice Copilot gives clinics the same choice between Patient Square EHR and an existing EHR.

For a multispecialty setting, the relevant Hospital Copilot decision is the record-system path. It can use the complete Patient Square HIS/EHR, or it can work alongside an incumbent HIS/EHR. The ambient AI Medical Scribe can return a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review; it accepts English, Hindi, and 20+ Indian languages including Hinglish, then returns a clean clinical-English note. Visit audio is processed in memory and discarded once the note drafts. The platform supports EHR-ready export (PDF · HL7 · FHIR); it does not claim a certified HMS integration, and ABDM integration remains on the roadmap. Hospital Copilot is a separate, demo-priced product. Its named hospital-only modules include Claims Management, AI Discharge Summary, Bed / IPD Management, and AI Copilot EHR; verify any additional operational requirement with the implementation team. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The scribe module does not establish pharmacy, lab, or blood-bank workflow coverage. Verify every required module, then choose either the complete Patient Square HIS/EHR or Hospital Copilot alongside a capable incumbent. Book a demo to compare both deployment paths against your facility size, department mix, incumbent HIS/EHR, and one difficult handoff. Read the [security page](../../security/) for the documented data posture.

---

## Osmind Alternatives (2026): When You're Not a TMS Clinic
https://patientsquare.com/us/blog/osmind-alternatives/
Published 2026-08-17 · Updated 2026-08-27 · Tags: alternatives, psychiatry, behavioral-health, comparison

Osmind is built for ketamine, TMS, and Spravato practices. Run general psychiatry or want ambient notes over interventional tooling? Here are the alternatives.

Two reasons dominate. First, fit: Osmind is purpose-built for interventional psychiatry (ketamine, TMS, Spravato), so a general outpatient med-management or talk-therapy practice is paying for machinery it never uses. Second, price and priority: Osmind's plans start at $199 a month per clinician, and some practices want ambient note-taking as the core feature rather than measurement-based-care tooling.

Most practices shopping for an Osmind alternative aren't unhappy with Osmind. They just aren't the practice Osmind was built for. Osmind is purpose-built for interventional psychiatry: ketamine, TMS, and Spravato programs with measurement-based care and out-of-network billing. If you run general outpatient psychiatry or your top priority is ambient notes over rating scales, you're paying for machinery you don't use. Ours starts at $79 per clinician per month on annual billing; [watch it draft a note from a real session](/us/) before you shortlist anything.

If you do run an interventional program, we'll say so plainly below: stay put. This page is for everyone who doesn't.

> **Key takeaways**
>
> - Osmind's Starter plan is $199 per clinician per month; Plus is around $269 (some listings show $249), per its published pricing as of this writing.
> - Osmind is built for interventional psychiatry (ketamine, Spravato, TMS) with 30-plus scheduled rating scales and out-of-network reimbursement tools.
> - Osmind 360 adds full billing and revenue-cycle services, priced separately.
> - Patient Square includes ambient capture in every plan: $79/clinician/month annual on Assist, $119 on Copilot with a bundled AI EHR.
> - Osmind stays the better fit for treatment-resistant-depression and interventional programs; a general psychiatry practice usually doesn't need that depth.

## What Osmind is actually built for

Osmind is a specialist tool, and that's a compliment. It was designed around interventional psychiatry: ketamine infusion, Spravato (esketamine), and TMS programs where measurement-based care isn't optional. Its published feature set reflects that focus. Thirty-plus standard rating scales sent to patients on a schedule, compliance automations built for Spravato REMS, customizable charting, e-prescribing, multi-calendar scheduling, telehealth, superbills, and in-app out-of-network reimbursement so cash-pay patients can chase their own claims.

For a clinic whose revenue runs on those programs, that's the right software. The rating scales trend automatically. The Spravato workflow keeps you inside the REMS requirements without a spreadsheet. And Osmind 360, its billing and revenue-cycle service, exists because interventional practices deal with prior authorizations and out-of-network reimbursement that would sink a general clinic's admin.

The friction shows up when your practice isn't that. A general outpatient psychiatrist doing medication management and 45-minute therapy hybrids uses maybe a third of what Osmind ships, and pays for all of it. At $199 a month per clinician on Starter, per its published pricing, the value proposition is measurement-based care and interventional compliance. If neither is your daily work, the money is buying features you scroll past.

## The honest price picture

Here's what Osmind publishes, and where the alternatives sit, so you can compare like-for-like.

| Tool | Built for | Ambient scribe as core product | Published price (per clinician/mo) | Free trial |
|---|---|---|---|---|
| Osmind Starter | Interventional psychiatry | No (AI-assisted EHR) | $199 | Demo only |
| Osmind Plus | Interventional psychiatry + more | No (AI-assisted EHR) | ~$269 (some listings $249) | Demo only |
| Patient Square Assist | General practice, documentation-first | Yes, included | $79 annual | 7 days |
| Patient Square Copilot | Same + bundled AI EHR | Yes, included | $119 annual | 7 days |

Osmind's Starter and Plus figures are from its published pricing and third-party listings as of mid-2026; the Plus price varies by source ($249 to $269), so confirm your quote before you sign. Osmind 360 billing services are priced separately on top. The meaningful column isn't the dollar figure. It's what the tool is organized around: interventional-psychiatry compliance and measurement, or ambient documentation.

That's the real fork. If you'd trade scheduled rating scales for notes that draft themselves, you're shopping in a different category than Osmind competes in.

One thing to check before you switch: how much of your revenue actually runs through Osmind's interventional tooling. A practice that does two ketamine series a month plus a full outpatient panel is a different case than a pure infusion clinic. If the interventional programs are a small side of the practice, you may be paying interventional prices to document the ordinary med-management visits that make up most of your week. Count last month's visits by type. If fewer than one in five touched a scale, a schedule, or a Spravato protocol, the fit question answers itself.

## Where an ambient-first platform fits instead

Patient Square is an AI clinical platform, and this is the sentence we'd put on the box. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan.

For a general psychiatry or med-management practice, that flow is the whole point. You run a back-to-back afternoon of medication reviews, and each note is waiting about two minutes after the visit ends. You correct a line and sign. Nothing enters the record without you. On a Tuesday with fourteen patients, that's the difference between leaving at 5:30 and charting past dinner.

Three details matter for psychiatry specifically. Session audio is never stored; it's processed in memory and discarded once the note drafts, so there's no recording archive to explain to a patient. The safeguards are HIPAA compliant with BAAs available for every customer, with the receipts on our [security page](/us/security/). And the prescription output is a draft you review and sign, not an EPCS transmission. For Schedule II through V medications, that draft doesn't send to a pharmacy, and most states now require DEA-registered EPCS for those, so keep a dedicated EPCS tool in the stack. The [full plan breakdown](/us/pricing/) shows what lands at each tier.

What we won't claim: Osmind's 30-plus scheduled rating scales, Spravato compliance automation, out-of-network reimbursement tooling, or a billing engine. We think tools in this category oversell exactly there, so we'd rather be the one page that doesn't. If measurement-based care is the job, Osmind does it better, full stop.

## When Osmind is the better fit

Plainly: if you run an interventional-psychiatry program, keep Osmind. Ketamine, Spravato, and TMS practices need scheduled outcome scales, REMS-aware compliance, and out-of-network billing that a general documentation tool doesn't touch. For treatment-resistant depression and interventional psychiatry specifically, Osmind is probably the strongest option in the market, and switching would trade real clinical infrastructure for a faster note.

Osmind also wins if you depend on its billing and revenue-cycle service. Osmind 360 handles prior auths and out-of-network reimbursement at a depth that matters when a single Spravato course involves months of insurance back-and-forth. Patient Square doesn't run claims or RCM, and won't pretend to.

The choice tips toward an ambient-first alternative when your practice is general outpatient psychiatry or counseling, your biggest daily cost is documentation time, and you don't run infusion or TMS programs. That's a large slice of psychiatry, and it's the slice paying for interventional tooling it never opens.

## How to test the switch in one week

Don't move on a feature sheet. Run this:

1. List the Osmind features you actually used last month. If measurement-based care and interventional compliance aren't on it, that's your signal.
2. Add up your real monthly cost: plan seat, Osmind 360 billing services, any add-ons. One number.
3. Write down the hours you spent charting in the same month. That's the number an ambient tool attacks.
4. Run our 7-day trial on real med-management sessions, with patient consent, and compare the drafts to your current notes.
5. Confirm your data exports cleanly from Osmind before you commit to anything.

If the drafts hold up on your actual session types, book a short demo and we'll run it against a real intake or med-management visit. For the wider behavioral-health field and how each EHR prices its scribe, see our [best EHR for psychiatry comparison](../best-ehr-for-psychiatry/), and if enterprise sales-led tools are your other option, [Valant alternatives](../valant-alternatives/) covers that branch.

---

## TherapyNotes Alternatives (2026): An Honest Shortlist
https://patientsquare.com/us/blog/therapynotes-alternatives/
Published 2026-08-17 · Updated 2026-08-27 · Tags: alternatives, behavioral-health, therapynotes, comparison

TherapyNotes runs billing well, but the notes are still on you. The alternatives for 2026, what each costs, and when staying put is the right call.

Usually one of three reasons: the documentation still falls on the clinician (TherapyFuel AI is a $40-per-clinician add-on, not part of the base plan), the per-clinician stack adds up for groups, or the practice doesn't use the billing machinery it's paying for. Practices that live in claims and the client portal tend to stay.

Most therapists hunting for a TherapyNotes alternative aren't angry at TherapyNotes. The billing works. The portal works. What sends them shopping is the part TherapyNotes never promised to fix: the progress notes still waiting at 9pm. If that's your reason, the alternative to shortlist is one where ambient documentation is the product, not a $40 add-on. Ours starts at $79 per clinician per month on annual billing, and you can [see it draft a note on a real session](/us/) before deciding anything.

If your reason is billing friction or price, different answer. This page walks through both.

> **Key takeaways**
>
> - TherapyNotes costs $69/month solo, or $79 for the first clinician plus $50 each additional, per its December 2025 pricing update.
> - Its ambient AI, TherapyFuel Scribe, is real but costs $40 per clinician per month on top of the base plan.
> - A 3-clinician group with TherapyFuel on every seat runs about $299/month before e-prescribing and per-claim fees.
> - Patient Square's Assist plan is $79/clinician/month annual with the ambient scribe included; Copilot at $119 adds a bundled AI EHR.
> - TherapyNotes remains the better fit for insurance-heavy groups that live in its claims tooling and TherapyPortal.

## What TherapyNotes does well, and where the edges are

Credit first. TherapyNotes is practice-management software that behavioral health actually likes: scheduling, claims, ERA posting, a client portal, telehealth included in the base price, and therapy-specific note templates. Unlimited non-clinical users is a quietly generous policy; your biller, scheduler, and admin cost nothing extra. For an insurance-billing group, that package is why it's everywhere.

The edges show up in two places.

First, documentation. The base plan gives you templates, and templates still mean typing. TherapyNotes' answer is TherapyFuel, its AI suite at $40 per clinician per month, which includes TherapyFuel Scribe for ambient note generation on in-person and telehealth sessions. It works as described in their docs. But it's an add-on priced per clinician, so the moment your whole group wants it, the math changes.

Second, the stack total. $69 solo sounds modest. A prescriber adds ePrescribe, which a third-party pricing guide lists near $65 per month. Claims and text reminders bill around 14 cents each, which a busy caseload feels. None of this is hidden; it's just spread across line items that don't appear in the headline price.

## How do the alternatives actually compare?

The honest way to shop this category is by which pain you're solving. Three shapes cover most practices.

We've written up the SimplePractice branch separately in our [SimplePractice alternatives guide](../simplepractice-alternatives/), and the wider field in [the therapist EHR comparison](../best-ehr-for-therapists/). This page stays on the TherapyNotes decision.

## Run the group math before you decide

Here's where the add-on structure matters. Take a 3-clinician therapy group, everyone wanting AI notes.

On TherapyNotes: $79 for the first clinician, $50 each for two more, so $179 base. TherapyFuel on three seats adds $120. That's $299 a month, before any prescriber adds ePrescribe and before per-claim fees. You also get a full billing engine for that money, which matters if you use it.

On Patient Square: three clinicians on annual Assist run $237 a month, and ambient capture is the core product rather than a bolt-on. Want the bundled AI EHR too? Copilot is $119 per clinician annually, so $357 for three. More than TherapyNotes' $299, and we'd rather tell you that plainly than bury it. The difference is what the money buys: their $299 includes claims machinery we don't have; our $357 includes a record system built around an ambient scribe, unlimited visits and notes with no per-note metering, and no setup fees.

So the deciding question is boring but real: which system do you actually work in all day? If it's the claims screen, stay. If it's the note editor, the [full plan breakdown](/us/pricing/) is worth ten minutes.

## What changes when the scribe is the product

Patient Square is an AI clinical platform, and Practice Copilot brings the whole practice under one AI copilot. The AI Medical Scribe is the module most people arrive for: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit, with a bundled AI EHR, scheduling, and messaging as you move up the plan.

For a talk-heavy practice, that flow fits the work. Sessions are conversation start to finish. You run the session, the draft is waiting, you correct a line or two and sign. Nothing enters the record without you. On a Thursday with seven clients, that's the difference between leaving at 5:30 and charting until dinner goes cold.

Two details matter more in behavioral health than anywhere else. Session audio is never stored; it's processed in memory and discarded once the note drafts, so there's no recording archive to explain to a client. And the safeguards are HIPAA compliant with BAAs available for every customer; the specifics live on our [security page](/us/security/). Notes export in EHR-ready formats too: EHR-ready export (PDF · HL7 · FHIR) ships on every plan.

What we won't claim: therapy-native treatment plans, insurance panels, superbills, or a claims engine. We think most tools in this category oversell exactly here, so we'd rather be the one page that doesn't.

## When TherapyNotes is the better fit

Plainly: if your practice bills insurance heavily, keep TherapyNotes. Its claims workflows, ERA posting, and TherapyPortal are the center of gravity for thousands of group practices, and the unlimited non-clinical-user policy makes staffing a billing desk cheap. TherapyFuel closes a good chunk of the documentation gap for $40 a seat, and for a group already trained on the platform, that add-on is far cheaper than a migration.

TherapyNotes also wins if you prescribe and want e-prescribing inside the same system. Their ePrescribe transmits; our prescription output is a draft you review and sign, not a pharmacy transmission. That line matters, and pretending otherwise would be selling you a gap.

Switch when the notes are the pain and the billing engine is furniture. A cash-pay or light-billing practice paying for claims machinery it rarely opens is the classic case.

## How to test an alternative in one week

Don't migrate on faith. Run this instead:

1. Count last month's real costs: base plan, TherapyFuel seats, ePrescribe, per-claim and per-reminder fees. Get one number.
2. Write down the hours you spent on notes in the same month. That's the other number.
3. Run our 7-day trial on real sessions, with client consent, and compare the drafts to what you'd have written.
4. Export a sample of your TherapyNotes data to confirm the records move cleanly.
5. Decide with both numbers in front of you, not the headline prices.

If the drafts hold up, book a short demo and we'll run it against your messiest session type, group notes and all. And if you're mainly here to sanity-check the bill, the line-item breakdown lives in our [TherapyNotes pricing teardown](../therapynotes-pricing/).

---

## ICANotes Alternatives (2026): Fewer Clicks, Same Chart
https://patientsquare.com/us/blog/icanotes-alternatives/
Published 2026-08-15 · Updated 2026-08-27 · Tags: alternatives, behavioral-health, icanotes, comparison

ICANotes builds notes from menus and buttons. If the clicking wears on you, here are the 2026 alternatives, the real seat prices, and who should stay.

The most common complaint is the input method. ICANotes assembles narrative notes from menu and button selections, which was a genuine speed win before ambient AI existed but now means a lot of clicking per session. Cost structure is the other driver: prescribing seats run $213 a month plus a $99 activation fee, per its published pricing.

Clinicians shopping for an ICANotes alternative are usually tired of one specific thing: building every note from menus and buttons. The 2026 alternatives split by practice type. Prescribing psychiatric groups mostly stay, because ICANotes' $213 prescriber seat buys genuine specialty depth. Talk-therapy and general psych practices increasingly move to ambient documentation, where the note drafts itself from the session. Ours starts at $79 per clinician per month on annual billing; [watch it run on a real session](/us/) before you shortlist anything.

> **Key takeaways**
>
> - ICANotes lists $75/month for a full-time non-prescribing clinician, $55 for notes-only, and $213 for a prescribing seat plus a $99 activation fee.
> - Its AI Scribe add-on is $49 per user monthly, so a non-prescriber with AI notes pays about $124 all-in.
> - Plans carry a three-month minimum, so test alternatives before renewing, not after.
> - Patient Square includes ambient capture in every plan: $79/clinician/month annual on Assist, $119 on Copilot with a bundled AI EHR.
> - ICANotes stays the better fit for prescribers who want e-prescribing and psychiatric templates in one system.

## How ICANotes charting actually works

ICANotes earned its base honestly. Its charting assembles a narrative note from structured menu and button selections: you click through symptoms, mental-status findings, and interventions, and the system writes prose from your picks. Before ambient AI, that was the fastest honest way to produce a thorough psychiatric note, and its template library for psych evals and medication management runs deep.

The friction is the input itself. Every note is still built by you, click by click, either during the session with your eyes on a screen or after it from memory. A psychiatrist running nine med checks on a Tuesday makes those menu passes nine times. The output is thorough. The process is the tax.

ICANotes knows this, which is why its pricing page lists an AI Scribe add-on at $49 per user per month. That's the pattern across the whole category in 2026: the click-era platforms are bolting AI on top. The question for a switcher is whether you want AI added to a menu-driven system, or a system built around the capture in the first place.

## What does ICANotes cost in 2026?

Per its published pricing as of this writing, seats are priced by role, and the spread is wide.

| ICANotes seat | Published price | Notes |
|---|---|---|
| Notes-only | $55/mo | Documentation without the fuller record features |
| Non-prescribing clinician, full-time | $75/mo | The standard therapist seat |
| Prescribing clinician, part-time | $138/mo | Reduced-schedule prescriber rate |
| Prescribing clinician, full-time | $213/mo | Plus a one-time $99 activation fee |
| AI Scribe add-on | $49/user/mo | On top of any seat |

Plans carry a three-month minimum, per the pricing page, so there's no single-month test drive. Fair credit: publishing role-based prices at all beats the quote-only norm in behavioral health, and we've broken down how the whole category prices in our [behavioral health EMR cost guide](../behavioral-health-emr-cost/).

The math worth staring at is the all-in note-writing number. A full-time therapist who wants AI-drafted notes pays $75 plus $49, so $124 a month. A full-time prescriber with the same add-on is at $262 plus activation. Hold those against any alternative you're pricing.

## Which alternative fits which practice?

Sort by what you're actually solving. Three honest paths:

**You want the clicking gone.** That's ambient documentation, and it's our lane. Patient Square's Copilot plan is $119 per clinician per month on annual billing, five dollars under ICANotes' therapist-plus-AI total, and it bundles an AI EHR rather than treating intelligence as an add-on. The Assist plan at $79 covers the scribe alone.

**You want therapy practice management, billing first.** Look at the practice-management platforms instead; we compared them in our [therapist EHR roundup](../best-ehr-for-therapists/). ICANotes' clinical depth and a PM platform's billing polish are different products wearing the same category label.

**You want psychiatric depth and you prescribe.** You may be shopping the wrong page. The [psychiatry EHR comparison](../best-ehr-for-psychiatry/) covers that field properly, and ICANotes itself is a finalist there for a reason.

## What ambient capture changes, concretely

Patient Square is an AI clinical platform built around one idea: the session itself is the input. The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit.

No menus mid-session. No rebuilding the hour from memory at 6pm. You run the visit with your attention on the patient, the draft is waiting when you're done, you fix what's wrong and sign. Nothing enters the record without your signature, and the ICD-10 output is suggestions for you to confirm, not a coding engine.

For behavioral health specifically, the audio question matters as much as the note. Session audio is never stored: it's processed in memory and discarded once the note is drafted, so there is no recording archive. Safeguards are HIPAA compliant, BAAs are available for every customer, and the details sit on our [security page](/us/security/). Every plan includes EHR-ready export (PDF · HL7 · FHIR), so your notes leave in formats a record system can take.

Where we draw the honest line: our prescription output is a draft. ICANotes' prescribing seats build actual e-prescribing in. If transmitting scripts from inside the record is a hard requirement, that's a point for staying.

## When ICANotes is the better fit

Two cases, stated without hedging.

First, prescribers. The $213 seat exists because prescriber workflows cost real money to run, and it puts e-prescribing and medication management inside the same system as the chart. Our platform doesn't transmit prescriptions, full stop. A medication-management practice should weigh ICANotes (or its peers) with that fact on the table.

Second, template-heavy psychiatric documentation. Twenty-plus years of behavioral-health charting refinement live in those menus: structured psych evals, MSE checklists, forms for settings generalist tools never see. We think ambient capture beats menus for conversational sessions, and we also think a structured psych eval is exactly where a mature template library still earns its keep. Both things are true.

If neither case is yours, you're likely a talk-first practice paying a specialist's toolkit price for a documentation problem ambient AI now solves more directly. The [plan comparison](/us/pricing/) shows exactly what each of our tiers ships.

## A two-week exit test

ICANotes' three-month minimum means you want certainty before switching, not after. Run this:

1. Pull your last invoice and compute your true per-clinician monthly cost, add-ons included.
2. Time your notes for one week: menu passes, after-hours catch-up, all of it.
3. Week two, run our 7-day trial on real sessions with client consent. Compare draft quality against your clicked notes, honestly.
4. Check the export path both directions before moving anything.

If the drafts hold and the math favors switching, book a demo and bring your hardest session type. If they don't, you've spent two weeks confirming your current tool, which is cheaper than three months regretting a new one.

---

## Patient Portal Software: How to Choose One (2026)
https://patientsquare.com/us/blog/patient-portal-software-guide/
Published 2026-08-14 · Updated 2026-08-29 · Tags: guide, patient-portal, small-practice, comparison

A small-practice buyer guide to patient portal software: the five features that matter, and how athenahealth, Klara, and Phreesia compare.

Patient portal software is a secure website or app where your patients log in to do the things that used to mean a phone call: read test results, message your staff, request appointments, fill out intake forms, and pay a bill. For a practice, it's the patient-facing front of your record system.

Patient portal software is the secure site or app where your patients read results, message staff, request visits, fill out intake forms, and pay bills without calling the front desk. For a small practice, the right one comes down to five features and whether your team will use it, not the length of the feature list. This guide walks the choice honestly, and our own [pricing](/us/pricing/) sits on the documentation side of that stack, not the portal side.

> **Key takeaways**
>
> - By 2022, about 73% of individuals were offered a portal and 57% used one, per the ONC's HINTS 6 data brief, and 51% used an app to get in.
> - Five features carry most of the value: secure messaging, results release, digital intake, appointment requests, and bill pay.
> - Many EHRs bundle a portal at no separate patient charge; standalone tools like Klara are quote-priced per provider or location.
> - The ONC information-blocking rule means you can't block a patient's access to their own records, and a portal is the usual way practices meet that.

## What does patient portal software actually do?

Strip the marketing off and a patient portal is a login. On the other side of it, your patient can see the parts of their chart you release, send a message to your staff, ask for an appointment, complete forms before they arrive, and pay what they owe. That's the whole job. Everything else a vendor lists is a variation on those few verbs.

It matters more than it used to. Per the ONC's HINTS 6 data brief, about 73% of people were offered online access to their records in 2022, up sharply from 2020, and 57% actually used it. Your patients are no longer surprised by a portal. They expect one, and a growing share, 51% in that survey, reach it through a phone app rather than a browser. If your practice doesn't offer some version of this, you're the outlier now.

## Which five features actually matter for a small practice?

We've watched practices buy portals on the strength of a demo, then use one-fifth of what they paid for. So here's the short list that earns its keep in a two-provider clinic on a busy Tuesday.

- **Secure messaging.** Two-way, HIPAA-appropriate messaging between patient and staff. This is the feature that quietly kills phone tag.
- **Electronic results release.** Patients see labs and results in the portal instead of waiting for a callback. Set your release rules carefully; some results need a clinician's note first.
- **Digital intake forms.** New-patient and pre-visit forms filled out before arrival, flowing into the chart instead of onto a clipboard.
- **Appointment requests or self-scheduling.** At minimum a request; at best, patients book open slots themselves.
- **Online bill pay.** Card on file, copays, and balances collected without a paper statement.

If a portal does those five well and your front desk will actually use it, the rest is upside. A portal that does twelve things poorly is worse than one that does five things cleanly.

## How do athenahealth, Klara, and Phreesia compare?

These three show up on most small-practice shortlists, and they're not really the same kind of product. One is a portal bundled into an EHR, one is a communication layer, one is an intake specialist. Knowing which is which saves you from comparing a truck to a wrench.

**athenahealth** ships a real portal. Per its patient-engagement page, the athenahealth Patient Portal and the athenaPatient app give patients secure records and test-result access, two-way texting and secure chat, self-scheduling, online payment, and self check-in with screeners and consent forms. It's part of athenaOne, so the portal and the record are one system. That's its strength and its constraint: it's the obvious pick if you already run athenaOne, and not a standalone product you'd bolt onto a different EHR.

**Klara**, now part of ModMed, is a communication platform more than a portal. Per its product pages, it pulls texts, web chat, phone calls, and voicemails into one HIPAA-appropriate thread, and adds e-forms and intake, two-way video visits, and self-scheduling. It integrates with EHRs including athenaOne and AdvancedMD. You reach for Klara when messaging is the real pain and your record system already handles the chart.

**Phreesia** is the intake and payments specialist. Per its registration product page, patients check themselves in from their own device with no app or login, and pay copays and balances during registration through options like Apple Pay and payment plans. Phreesia says 85% of patients self-check-in across its network. It's narrower than a full portal on purpose, and very good at the narrow thing.

## A bundled EHR portal usually wins for records access; a standalone tool wins for one sharp job

Our read, from watching practices shop: if your biggest gap is patient-facing access to records and results, a portal bundled into your EHR is usually the cleaner buy. The portal and the chart already speak the same language, and you're not paying a second vendor to keep them in sync. athenahealth is the example above, and most modern EHRs ship something similar.

A standalone tool wins in two cases. First, when messaging is your actual pain and your EHR's built-in portal is clumsy, a focused layer like Klara can be worth the extra line item. Second, when intake and point-of-service payment are the bottleneck, a specialist like Phreesia often collects more, faster, than a general portal's forms. Buy the standalone when the specialist genuinely beats the bundled feature, not by default.

The trap is buying a big portal suite for one feature you needed. If all you want is result release, don't sign a platform contract for it.

## Patient Square sits on the documentation side of the stack, not the portal side

We'll be straight with you, because this is a buyer guide and not a pitch. A patient portal isn't a module we describe on our product pages, so we're not going to claim one. What we build sits on the other side of the visit: the clinical documentation and the bundled AI EHR that your clinicians work in.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On the Copilot plan, that scribe comes with a bundled AI EHR at $119 per clinician per month on the annual plan. Every plan includes **EHR-ready export (PDF · HL7 · FHIR)**. That export claim does not describe a patient portal or patient-facing access.

So think of the portal as one piece of the stack and the documentation engine as another. They solve different problems. If your top requirement today is a patient-facing portal, start with a dedicated portal or an EHR that bundles one. If finishing charts after hours is the thing eating your evenings, that's the part we're built for. [review the product scope](/us/products/practice-copilot/) if the clinician-documentation side is the gap you want to assess; the [pricing](/us/pricing/) is on the page.

## A short buying checklist

Before you sign anything, run the portal against your own week, not the demo script.

- Which of the five core features do you actually need this quarter?
- Will your front desk use the messaging, or route around it?
- Does it release results the way your clinicians want, with the right holds?
- Is it bundled into your EHR already, so you're not paying twice?
- Can patients reach it on a phone, since half of portal users do?

If a tool clears that list, it's a real contender. If it only shines in the sales deck, keep looking. For the documentation side of the same stack, our [approach to the note](../best-ehr-with-ai-scribe-built-in/) and how we handle [any-EHR export](../ai-scribe-any-ehr-export/) go deeper, and our [security page](/us/security/) covers how records are protected in transit and at rest.

## Bottom line on choosing patient portal software

Pick the portal on five features, not on the feature count: secure messaging, results release, digital intake, appointment requests, and bill pay. If patient-facing access is your gap, a bundled EHR portal like athenahealth's is usually the simplest path; if messaging or intake is the specific pain, Klara or Phreesia can beat the bundled option at that one job. A portal is one piece of a small practice's stack. The documentation piece is a different problem, and it's the one we work on.

## Frequently asked questions

The FAQ above covers the recurring questions: what portal software does, the five features that matter, whether athenahealth and Klara count as portals, the information-blocking rule, and where our documentation tools fit. For related reading, see our take on the [best EHR with an AI scribe built in](../best-ehr-with-ai-scribe-built-in/) and the [athenahealth cost math](../athenahealth-ehr-cost/).

---

## Best EHR for Small Practices: Which Include an AI Scribe
https://patientsquare.com/us/blog/best-ehr-small-practices-ai-scribe/
Published 2026-08-13 · Tags: ehr, small-practice, comparison, ai-scribe

Five small-practice EHRs, ranked by one thing: is the AI scribe bundled in a price you can read, sold as an add-on, or left to a third party? Honest 2026 picks.

As of mid-2026, several small-practice EHRs ship a native ambient scribe: Elation (Note Assist, included at no added cost), RXNT (Ambient IQ, free for EHR and Full Suite customers), and Tebra (AI Note Assist). Patient Square bundles the scribe into a published Copilot plan at $119 per clinician per month. athenahealth and Practice Fusion have no native scribe and lean on third-party tools billed separately.

Most "best EHR" roundups skip the one thing a small practice buried in charting actually cares about: does the record system come with an AI scribe, or is that a second product you pay for later? Here's the honest read on five small-practice EHRs, sorted by whether the scribe is bundled, an add-on, or missing. Our pick for a published all-in price is Patient Square at $119 per clinician per month, and we'll say plainly where a competitor wins. See [the pricing](/us/pricing/) as you read.

> **Key takeaways**
>
> - Elation (Note Assist) and RXNT (Ambient IQ) each include a native scribe at no extra cost to EHR customers; RXNT's EHR Bundle is about $126 per provider per month.
> - athenahealth and Practice Fusion have no native scribe; athenahealth wires in partners like Abridge and Suki that bill on top of its 4 to 8 percent collections fee.
> - Tebra ships a native AI Note Assist, but the EHR price is quote-only, so the all-in number arrives after a demo.
> - Patient Square publishes a flat $119 per clinician per month with the ambient scribe and AI EHR in one line, no per-note fees.

## Why "does it include a scribe" beats "is it a good EHR"

Almost every EHR on a small-practice shortlist charts, prescribes, and schedules. The features converge. What splits them in 2026 is documentation load. A solo doctor running a 22-patient Tuesday can lose an hour after the last visit typing notes into a chart that didn't help write them. So the buying question isn't "is this a capable EHR." It's "does the note get drafted for me, and is that drafting in the price I'm quoting, or a line item I discover in month three."

That reframes the whole comparison. An EHR with a bundled scribe and an EHR that makes you shop for a scribe separately are two different purchases, even if the record systems look identical on a feature grid. This roundup ranks on that split.

We build one of these tools, so we'll be direct about our bias and about where we lose. A roundup that only flatters the author isn't worth citing.

## Which small-practice EHRs include an AI scribe, and how

Four of the five competitors here have a scribe story. The stories differ enough to matter.

### Elation: native scribe, but the EHR price is hidden

Elation targets independent primary care, family medicine, and direct primary care, and it has a following in that niche. Its Note Assist scribe is native, built by Elation and embedded in the chart, and Elation says it's included at no additional cost to EHR users. If you already run Elation and like it, that's a reason to stay, not switch.

The friction is the EHR price. Elation's pricing page is quote-only now; third-party trackers estimate roughly $275 to $399 per provider per month depending on plan. So the scribe is free, but the thing it rides on is a number you get after a call.

### RXNT: native scribe, and it's free for EHR customers

RXNT is the one to watch on scribe economics. Its Ambient IQ tool is natively built, launched in late 2025, and per RXNT it's available at no cost to existing EHR and Full Suite customers, with unlimited ambient sessions. Standalone, Ambient IQ runs $75 per month after a 90-day trial with 30 free sessions. RXNT's EHR Bundle is published at about $126 per provider per month, and it's ONC-certified.

So a small practice that wants a low, published EHR price with a native scribe folded in for free lands on RXNT fast. We'll come back to when that's the better call than us.

### Tebra (Kareo): native scribe, quote-only plan

Tebra, the platform that absorbed Kareo, ships a native AI Note Assist for SOAP, therapy, and psych note types with ambient listening and diagnosis-code prompts. It's built in, not a bolt-on. The catch is the same as Elation's: Tebra doesn't publish EHR pricing, so the all-in figure with the scribe arrives after a demo. For a deeper look at what stacks onto that quote, see our breakdown of [Kareo and Tebra pricing](../kareo-ehr-pricing/).

### athenahealth: no native scribe, partners on top

athenahealth is a big ambulatory EHR with a deep revenue-cycle engine, but it has no built-in ambient scribe. It integrates partners like Abridge, Suki, iScribe, and Microsoft Dragon Copilot, and those partners bill separately. So the scribe is an added subscription layered on top of athenahealth's percentage-of-collections model, which third parties put at 4 to 8 percent of what you collect. Two vendors, two bills. Our full read on that math is in [athenahealth's cost model](../athenahealth-ehr-cost/).

### Practice Fusion: no scribe at all

Practice Fusion is a low-cost cloud EHR at roughly $199 per provider per month. It charts, prescribes, and connects labs. It has no native ambient scribe. If you want AI documentation on Practice Fusion, you bolt on a third-party tool and paste notes across. That's the gap our [Practice Fusion alternatives](../practice-fusion-alternatives/) post walks through.

## Our pick: Patient Square, because the price is on the page

Here's our case, stated as ours. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On the Copilot plan, that scribe ships with a bundled AI EHR at $119 per clinician per month on annual billing ($149 month-to-month). Unlimited visits and notes, no per-note metering, no setup fee.

The wedge isn't "we have a scribe and they don't." Elation, RXNT, and Tebra all have one. The wedge is that we publish one all-in number that covers the record and the scribe together. You can budget it on a spreadsheet before anyone from sales calls you. With Elation and Tebra, the scribe may be included, but the EHR price is quote-only, so you can't run the comparison until you're in a sales cycle. We think a published price is a feature, and small practices should weight it heavily.

If you already own an EHR you like and just want the scribe layer, our Assist tier is $79 per month annual for documentation only, and notes export as PDF, HL7, or FHIR into your existing chart. That use case is covered in [using an AI scribe with any EHR export](../ai-scribe-any-ehr-export/).

You can see the scribe and EHR running together on a real visit. Book a short demo and we'll run it on your own note types.

## What the two structures cost a solo clinician

Say you're one clinician, 20 visits a day, 20 days a month. Here's how the scribe question hits your bill on three of these options, using each vendor's own published numbers where they exist.

On RXNT, the EHR Bundle near $126 a month includes Ambient IQ at no extra cost to customers, so your documentation and record sit in one line around $126. On Patient Square's Copilot plan, the ambient scribe and AI EHR are $119 a month annual, also one line. On athenahealth, the EHR bills 4 to 8 percent of collections and the scribe is a separate partner subscription on top, so your total is a moving percentage plus a second vendor's monthly fee, and you won't know the sum until you've signed and started collecting.

The point isn't that our number is always the lowest. RXNT can undercut us on a lean setup, and we said so. The point is that with a bundled, published price you know the whole documentation bill before you commit, and with a collections percentage plus a bolt-on scribe you don't.

## When a competitor is the better fit

We lose in specific, honest situations. Pretending otherwise would make this list useless.

RXNT beats us on raw price-per-dollar of included AI. Its EHR Bundle near $126 with Ambient IQ at no extra cost to customers is a lean setup, and if you want the lowest published EHR price with a native scribe folded in, that's the one to shortlist. Elation wins on inertia. If you're an independent primary care or DPC practice already running it, Note Assist comes at no added cost, so switching to a new EHR just for a bundled scribe rarely pencils out. And athenahealth wins when revenue-cycle depth outranks the scribe. Its percentage-of-collections model even cushions a brand-new practice's early cash flow, and you can add a partner scribe later. We don't replicate an enterprise RCM engine, and we won't pretend to.

Our pick wins for a narrower buyer: a small practice that wants an AI-native workflow and a flat, published price with the scribe already in it. If that's you, [see the pricing](/us/pricing/) and compare it line for line against the quotes you'd otherwise have to chase.

## How to run the comparison in an afternoon

Skip the feature matrix. Answer four questions for each vendor on your shortlist.

1. Is the scribe native, or is it a third-party tool I manage separately?
2. Is the scribe included in the EHR price, an add-on, or a higher tier?
3. Can I read the all-in price before a sales call, or only after?
4. Does the note come back structured, with ICD-10 suggestions and a prescription draft, or just a paragraph I still have to shape?

Rank the vendors on those, not on the length of their feature list. For the broader field without the scribe lens, our [best EMR for a small practice](../best-emr-for-small-practice/) roundup covers cost and fit generally, and [best EHR with an AI scribe built in](../best-ehr-with-ai-scribe-built-in/) digs into what "built in" actually means across the market.

## The bottom line

The best EHR for your small practice depends on how much of the note you want written for you and how much of the price you want to see up front. Elation and RXNT include native scribes at no extra cost, RXNT at a published EHR price and Elation behind a quote. Tebra bundles a scribe inside a quote-only plan. athenahealth and Practice Fusion leave the scribe to third parties. Our pick, Patient Square, puts the ambient scribe and the AI EHR in one published $119 line. Rank on scribe economics, favor a price you can read, and book a demo on the two or three that make your shortlist before you sign.

---

## Medical Office Scheduling Software: 2026 Buyer's Guide
https://patientsquare.com/us/blog/medical-office-scheduling-software/
Published 2026-08-13 · Updated 2026-08-29 · Tags: scheduling, comparison, small-practice, front-desk

What small-practice scheduling software needs in 2026: online booking, reminders, waitlist, no-show reduction. Standalone vendors vs an all-in-one, compared.

It's the tool your front desk uses to book, reschedule, and cancel patient appointments against a shared calendar. Good ones add online self-booking, automated text and email reminders, a waitlist that backfills cancelled slots, and calendar sync so a booking made anywhere shows up everywhere. The goal is fewer phone hours and fewer empty rooms.

Medical office scheduling software books, reschedules, and cancels patient appointments against a shared calendar, and the good ones add online self-booking, automated reminders, a waitlist that fills cancelled slots, and two-way calendar sync. For a small practice, the decision is really one question: buy a dedicated scheduling tool, or use scheduling that's bundled into a platform you already pay for. Ours ships from the entry plan; see the [pricing page](/us/pricing/).

> **Key takeaways**
> - Five features carry a small-practice scheduler: online booking, automated reminders, waitlist backfill, calendar sync, and booking rules. The rest is enterprise weight you probably won't use.
> - The average missed appointment costs a practice about $200, and no-shows benchmark near 7%, so reminders plus waitlist backfill pay for the software fast.
> - About 65% of patients still prefer to book by phone, so online booking is an option to add, not a wall to build.
> - Standalone tools (Setmore, Phreesia, Clearwave, RXNT) are the better fit when you love your current EHR; a bundle wins when your stack is fragmented and you're re-typing patients across apps.

## What does a small practice actually need from scheduling software?

Vendor feature lists run 40 items long. A two-provider clinic uses about five of them. Here's the short list that carries the weight, and what each one is really for.

| Must-have feature | What it does | Why a small practice cares |
| --- | --- | --- |
| Online self-booking | Patients pick an open slot 24/7 from their phone | Cuts inbound phone volume; captures after-hours requests |
| Automated reminders | Text and email nudges before the visit | Fewer patients who simply forget; direct no-show cut |
| Waitlist backfill | Offers a cancelled slot to waitlisted patients | Refills gaps a busy desk would never work by hand |
| Two-way calendar sync | Booking made anywhere updates everywhere | No double-books; one source of truth for availability |
| Booking rules | Visit length, provider prefs, block types | Stops the system from booking garbage you have to fix |

Everything past this is nice-to-have. Group appointment logic, kiosk check-in, referral routing, a marketing suite: real features, but they earn their cost at scale, not at a two-room office. Buy the five that touch every single day. Ignore the rest until you feel the specific pain they solve.

One feature people over-index on is the reminder itself. Reminders help, sure. But the bigger lever is the waitlist. When a Thursday slot cancels at 11am, a slammed front desk almost never has the minutes to call down the list. Software that texts the eligible patients and books whoever confirms first fills that gap in the background. That's the behavior that moves your revenue.

## How much does medical scheduling software cost in 2026?

Pricing splits into two camps, and they don't compare cleanly.

General-purpose booking tools publish a rate. Setmore, per its pricing page, is free for up to four users, then runs roughly $5 to $12 per user per month once you want SMS reminders and two-way calendar sync. Cheap, transparent, and not built for healthcare, which matters for reasons we'll get to.

Healthcare-specific platforms mostly hide the number. Phreesia, Clearwave, and RXNT price by demo, based on your provider count and which modules you turn on. You learn your real figure after a sales call. That's normal for the category, but it makes side-by-side budgeting slow.

Then there's the third option: scheduling that's already inside a platform you pay for. If your EHR or your practice-management suite includes booking, reminders, and a waitlist, the marginal cost of "scheduling software" is zero. You're just turning on a module. That's the case for pricing the bundle before you buy a standalone tool, because you may already own most of what you're shopping for.

## Standalone scheduling vendors, compared honestly

Four tools cover most of what a small US practice will look at. None is bad. They aim at different practices.

**Setmore** is the budget pick. Free for four users, published pricing, and it just works for booking. The catch: it's a general appointment tool, not a clinical one. No EHR tie-in, and reminders sit behind a paid tier. For a cash-pay solo practice that treats scheduling as a calendar problem, it's fine.

**Phreesia** is the enterprise end. Self-scheduling, smart waitlists, and deep EHR integration with systems like athenahealth and NextGen, built to scale across many locations and providers. It's genuinely strong, and it's more platform than a two-provider clinic usually needs.

**Clearwave** aims at specialty practices and leans on a powerful rules engine, kiosk check-in, and eligibility verification at the front desk. If your bottleneck is registration and insurance verification at the window, that's its sweet spot. It's less about post-visit outreach.

**RXNT** bundles scheduling into a cloud practice-management and EHR suite, with reminders and automated eligibility checks. If you want booking, billing, and charts from one vendor and you're pricing a fuller platform anyway, it belongs on your list.

## When a dedicated scheduling tool is the better fit

We build scheduling into a platform, so treat this as us arguing against our own bias on purpose.

If you already run an EHR you like, your staff know it, your templates are built, your data lives there, then a standalone scheduling tool is the cleaner buy. Bolt Setmore or a Phreesia module onto what you have, get online booking and reminders, and don't rip out a working system to consolidate. Consolidation for its own sake is a bad reason to switch. The pain has to be real first.

That pain is usually fragmentation. You feel it when the same patient gets typed into a booking widget, then an EHR, then a separate reminder app, and the three don't agree. If that's not your life, a focused scheduling tool wins. Buy the narrow thing. We'd rather say that than sell you a migration you don't need.

## When a broader practice-system evaluation is worth the effort

Here is the honest case for evaluating a broader practice system. Scheduling gets bought as a standalone tool because it feels standalone. A booking, a reminder, an intake, and a note all touch the same patient at different moments. If your current tools create repeated manual work, evaluate the handoffs and error ownership before replacing anything.

Patient Square is an AI clinical platform. For independent practices, Practice Copilot includes an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit. Scheduling ships from Assist. Copilot adds the bundled Patient Square EHR and WhatsApp messaging, while Practice Copilot can also work alongside an existing EHR.

The scheduling module ships from the entry [Assist plan](/us/pricing/), $79 per clinician per month on the annual plan, with unlimited visits and notes and no per-note fees. Move up to the Copilot plan at $119 and you add the bundled Patient Square EHR plus WhatsApp messaging. Practice Copilot can also work alongside an existing EHR. We do not publish claims about online booking, reminders, waitlists, a patient portal, shared records, or reduced re-entry, so use the trial to test the scheduling workflow that matters to your practice.

If you want to weigh scheduling against a wider front-office change, our breakdown of [what an all-in-one patient management platform includes](../patient-management-software-guide/) and the deeper look at [what autonomous AI booking actually requires](../ai-patient-scheduling-medical-office/) cover the neighboring decisions.

## Bottom line: match the tool to your stack, not the demo

Scheduling software earns its keep through two boring behaviors: reminders that cut the forgetters, and a waitlist that refills cancellations. At about $200 a no-show, that math works quickly for almost any practice. The five features that matter are online booking, reminders, waitlist, calendar sync, and booking rules. Buy those; skip the enterprise weight.

The buy decision comes down to your current stack. Love your EHR and just want booking? A standalone tool like Setmore, Phreesia, Clearwave, or RXNT is the clean answer. If Practice Copilot's published module and pricing fit your practice, Request your 7-day trial and test your real calendar rules.

---

## What Makes a Hospital Management System 'Smart'? (AI in HMS)
https://patientsquare.com/in/blog/ai-hospital-management-software-india/
Published 2026-08-12 · Updated 2026-08-30 · Tags: ai-hms, smart-hospital, automation, dpdp, india

AI hospital management software promises a 'smart' HMS. Here's what AI actually changes inside a hospital system in India, what's just a badge, and how to tell.

Treat 'smart' as a procurement claim, not a product category. Ask the vendor to demonstrate the specific task, human review, failure handling, and measured result in your workflow. Patient Square's documented scribe output is a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review; named Hospital Copilot modules do not establish a particular workflow by themselves.

"AI-powered hospital management software" is on every vendor slide now, and most of it is a badge. A smart HMS should do one thing a plain one can't: remove work instead of just storing it. The useful question isn't whether the software "uses AI," which everything claims, but which specific task the AI actually takes off your staff's hands, and whether that task is worth paying for. This guide separates the AI in a hospital system that genuinely changes the workday from the AI that's a sticker on a spec sheet, for hospitals evaluating in India.

The search signal here is retained research, not a fresh query: the repository's Google Ads Keyword Planner export dated 2026-07-01 records `hospital management software` at 1,900 India average monthly searches. Its LOW competition label describes paid-advertiser competition, not organic ranking difficulty.

> **Key takeaways**
>
> - Treat every "smart" claim as a procurement test: name the task, required human review, failure path, and measured result.
> - Patient Square's documented AI output is a reviewable draft note and ICD-10 suggestions; do not infer a scheduling, follow-up, safety, or other hospital workflow from a module name.
> - Treat ICD-10 suggestions as a buyer test with human review and correction; a suggestion is not a coding engine.
> - DPDP's core processing provisions are scheduled for eighteen months after the 13 November 2025 Gazette notification. Use data controls as preparation and check other applicable obligations.

_Sources: National Health Authority; WHO AI-for-health guidance 2021; Irving et al., BMJ Open 2017._

## What separates a "smart" HMS from a plain one?

Whether the AI removes work or just relabels storage. A plain hospital management system records what your staff type: registration, notes, orders, bills. A smart one does something the plain one can't, drafting, flagging, or automating a part of the work so a human does less of it. That's the line. Everything else is packaging.

The trap is that "AI-powered" gets stuck on features that are ordinary automation dressed up. A reminder that fires on a schedule isn't AI; it's a cron job. A dropdown that filters isn't AI; it's a filter. The honest test for any "smart" claim: name the specific task the AI performs and the specific work it removes. If the vendor can't, the intelligence is in the marketing, not the software. Our [HMS modules explainer](../hospital-management-system-explained/) covers the standard modules; this post is about what AI genuinely adds on top of them.

## What can AI actually do inside a hospital system?

A short list of demonstrated workflows beats a long list of vague ones. Put these vendor claims through procurement tests:

- **Ambient documentation**: demonstrate a drafted note, clinician review, correction, approval, and failure recovery.
- **Front-desk automation**: demonstrate any claimed scheduling, routine-query, reminder, staff-handoff, and exception workflow.
- **Follow-up messaging**: demonstrate the trigger, recipient, consent or notice handling, clinician oversight, opt-out, and audit trail.
- **Coding suggestions**: demonstrate the source note, suggested code, human review, correction, and claim boundary.
- **Safety flags**: demonstrate the input, alert, clinical review, override, and audit behaviour; do not assume a module provides this.

Notice what's absent: autonomous diagnosis. The World Health Organization's 2021 guidance on AI for health is clear that AI should augment clinical judgement under human oversight, not replace it. A smart HMS drafts and flags; the clinician decides. Any system claiming the AI diagnoses on its own is overselling, and in a hospital setting that's a risk, not a feature.

## Is the "AI" a real capability or a sticker?

Usually you can tell in one demo question. Ask the vendor to show the exact task in your workflow, then record the baseline, observed result, required human review, correction rate, and failure path. A real capability can repeat that acceptance test; a sticker has hand-waving: "our platform uses AI throughout."

Here's a quick way to score claims:

| Claim | Real if... | Sticker if... |
|---|---|---|
| "AI documentation" | Vendor demonstrates draft, clinician review, approval, and recovery | The workflow cannot be demonstrated |
| "AI coding" | Vendor demonstrates the suggestion and human review path | The claim resolves to an ordinary code lookup |
| "AI scheduling" | Vendor demonstrates the claimed booking, reminder, handoff, and exception path | The scope is not stated or tested |
| "AI insights" | Vendor demonstrates the input, action, human reviewer, and audit trail | The claim is only a dashboard label |

We think the "AI insights dashboard" is the most oversold item in the category. A wall of charts isn't intelligence; it's reporting. The features that earn the "smart" label are the ones that quietly do a task a person used to do.

## What about AI coding, honestly?

Treat coding claims as a procurement test. Ask the vendor to show the source note, any suggested ICD-10 code, human review and correction, claim handoff, and failure path. Measure the observed result in your own workflow; do not assume a suggestion improves coding or claims throughput. Our [hospital revenue cycle guide](../hospital-revenue-cycle-management-india/) covers where coding fits in reimbursement.

But a suggestion is not a coding engine, and it's not a guarantee. A human coder or clinician still reviews and confirms the code, because responsibility for an incorrect claim doesn't transfer to the software. Be especially careful with any vendor claiming "automatic" or "guaranteed" coding across CPT, E&M, or HCC. To be straight about our own scope: Patient Square's scribe offers ICD-10 suggestions, not automated coding, and doesn't run CPT, E&M, or HCC engines. The clinician confirms every code.

## What does DPDP require from AI features?

The DPDP Act's core processing, notice, consent, and fiduciary provisions are scheduled to commence eighteen months after the 13 November 2025 Gazette notification. On this page's update date, do not describe them as current enforcement. Use consent, notice, access, retention, and security questions as prudent procurement preparation, alongside any other applicable law, contract, and professional obligation.

Three questions to put to any "smart HMS" vendor. Where does the AI process the data, and is it hosted where you expect? Are the inputs, especially any audio, stored or discarded after use? And who can access the AI's outputs? An AI feature that keeps a recording of every consult on a server is a liability sitting in your building. One that processes in memory and discards is a cleaner answer. Our [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers the fiduciary duties in full. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## Where does Patient Square fit for a hospital wanting "smart"?

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For a hospital, Hospital Copilot is a separate, demo-priced product with two record-system paths: use the complete Patient Square HIS/EHR as the system of record, or keep an existing HIS/EHR and use Hospital Copilot alongside it. The named Hospital Copilot modules that ship are AI Medical Scribe, AI Receptionist, eRx, AI Follow-ups, WhatsApp, AI Copilot EHR, Claims Management, AI Discharge Summary, and Bed / IPD Management. Those names establish the product surface; they do not establish a particular routing, integration, or automatic write-back workflow for a hospital.

The ambient scribe has the specific documentation evidence: English, Hindi, and 20+ Indian languages with code-mixing; a clean clinical-English note; ICD-10 suggestions; and a prescription draft for clinician review. Audio is processed in memory and discarded once the note is drafted. EHR-ready export (PDF · HL7 · FHIR) is an export capability, not certified interoperability. ABDM integration is on the roadmap. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to map the record-system path, named modules, and procurement acceptance tests to your hospital. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

---

## Practice Management Software for Indian Doctors (2026)
https://patientsquare.com/in/blog/practice-management-software-doctors-india/
Published 2026-08-12 · Updated 2026-08-30 · Tags: practice-management-software, solo-doctor, clinic-software, dpdp, india

What practice management software does for a solo or small-clinic doctor in India: scheduling, records, billing, messaging, rupee pricing, and where AI fits.

It's the software that runs the day-to-day of a practice, as opposed to just storing clinical notes. Scheduling and appointments, patient registration, billing and receipts, reminders and messaging, and often a linked clinical record. For a solo or small-clinic doctor, it's the tool that keeps the front desk and the back office moving, not the clinical decision-making.

If you're a solo doctor or run a small clinic in India, "practice management software" is the tool that keeps the practice moving when you're not thinking about it: the appointments, the reminders, the invoices, the records. The trouble is that every vendor stretches the phrase to cover whatever they sell. This guide is written for a doctor, not a hospital procurement committee: what the software actually does for your day, what it should cost in rupees, what DPDP now asks of it, and where AI genuinely changes the workload versus where it's just a badge.

This is not a fresh live keyword pull. The retained repository Google Ads Keyword Planner export dated 2026-07-01 records `practice management software` at 480 India average monthly searches; its LOW competition field refers to paid-advertiser competition, not organic difficulty.

> **Key takeaways**
>
> - Practice management software runs the operations of a practice, scheduling, billing, reminders, patient flow. It's a different job from the clinical record.
> - Ask each vendor for a written quote with unit, scope, cadence, tax treatment, variable charges, renewal, and exit terms; do not budget from an unsupported market range.
> - DPDP's core processing provisions are scheduled for eighteen months after the 13 November 2025 Gazette notification. Use consent, access, retention, and export questions as preparation and check other applicable obligations.
> - The biggest daily leak for most solo doctors isn't scheduling. It's the note that never gets written properly at a two-minute consult.

_Sources: DPDP Act 2023; CGST Act 2017; Irving et al., BMJ Open 2017._

## What does practice management software actually do?

It runs the machinery around the consult, not the consult itself. Think of a normal clinic day: patients booking and rebooking, a queue forming, reminders going out the evening before, receipts and GST invoices at checkout, a follow-up nudge three days later. Practice management software is the tool that handles that flow so your front desk isn't doing all of it by hand.

The core jobs are consistent across vendors:

- **Scheduling and appointments**: booking, rescheduling, and a visible queue for the day.
- **Patient registration**: a single record per patient so you're not re-entering details each visit.
- **Billing and invoicing**: receipts and GST-compliant tax invoices, which the CGST Act 2017 requires for registered practices.
- **Reminders and messaging**: appointment reminders and follow-ups, often over WhatsApp or SMS.
- **A linked clinical record**: many tools bundle the notes, which is where the line with an EMR blurs.

Notice what's not on that list: diagnosing, treating, or making clinical calls. Practice management is operational. It keeps the practice running smoothly; it doesn't practise medicine. That distinction matters when a vendor claims their software will "transform your care." It manages your logistics. Your care is still yours.

## How is it different from an EMR?

Different job, often the same product. An EMR is the clinical record, the notes, history, diagnoses, and prescriptions. Practice management software is the operational layer around it. A lot of products bundle both, which is why buyers use the terms loosely, but if you're clear on which problem you're solving, you buy better.

Ask yourself which fire you're fighting. If your evenings go to chasing no-shows, reconciling payments, and re-entering patient details, that's a practice management problem. If your evenings go to writing up thin notes from memory after the last patient leaves, that's a documentation problem, and no amount of scheduling polish fixes it. Our [EMR-vs-EHR-vs-HMS pillar](../emr-vs-ehr-explained-india/) sorts the record-system side; this post stays on the operations and where they meet the note.

## What should practice management software cost in India?

Enough to save you more than it costs, and no more. Ask every vendor for a current written quote with the product scope, clinician/user unit, billing cadence, GST treatment, variable charges, implementation, renewal, and exit terms. A demo-led price is not a market benchmark.

Two cost traps to watch. First, per-unit add-ons: a base price that looks cheap until you add per-SMS, per-appointment, or per-invoice charges that scale with your volume. Second, the year-two renewal, where a discounted first-year deal quietly resets. When you compare quotes, ask every vendor for the all-in monthly cost at your real patient volume, including messaging, and the renewal price. Our [clinic management software scorecard](../best-clinic-management-software-india/) and [EMR buyer's guide](../emr-software-india-guide/) both walk pricing in more depth.

## What does DPDP require from your practice software?

The Digital Personal Data Protection Act, 2023 contains data-fiduciary, notice, consent, and processing provisions. The 13 November 2025 Gazette notification schedules sections 3 to 17, including those core provisions, eighteen months after publication. On this page's update date, do not describe them as current enforcement.

For practice management software, use consent records, role-scoped access, export/deletion, hosting, retention, and audit questions as prudent preparation. Check other applicable law, contracts, and professional obligations, and ask the vendor for written answers. If you're using WhatsApp for reminders, our [WhatsApp for clinics guide](../whatsapp-for-clinics-india/) covers operational questions; the [DPDP guide for clinics](../dpdp-act-clinics-guide/) explains the Act's intended framework.

## Where does AI actually change the work, and where doesn't it?

AI claims need separate workflow tests. Patient Square's documented scribe can draft the clinical note for clinician review. For any claimed scheduling, receptionist, reminder, or follow-up behaviour, ask the vendor to demonstrate the trigger, human handoff, failure path, and audit trail; do not infer that behaviour from a module name. Clinical judgement stays with the doctor.

The single biggest leak for most solo doctors isn't scheduling, which manual methods handle passably. It's the note. The average primary-care consultation in India runs about two minutes, per a 2017 BMJ Open systematic review of 67 countries by Irving and colleagues, which put India near the short end of a range that ran from 48 seconds to 22.5 minutes. Two minutes to listen, examine, decide, and prescribe leaves the documentation to lose every time. That's the work AI genuinely removes.

> We think most practice management pitches over-index on scheduling, which was never the real bottleneck, and under-index on the note, which is where a solo doctor actually loses an hour a day.

## Where does Patient Square fit for a solo or small-clinic doctor?

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

For a greenfield India practice, Practice Copilot can use the bundled AI EHR from the Copilot tier as its system of record. An established practice can keep its existing EHR and use Practice Copilot alongside it. The scribe supports English, Hindi, and 20+ Indian languages with code-mixing; notes come back in clean clinical English. Audio is processed in memory and discarded after the note is drafted. ABDM integration is on the roadmap, not shipped. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Prices are per clinician and shown ex-GST: Assist is ₹1,999 month-to-month or ₹1,599 monthly-equivalent on annual billing; Copilot is ₹2,999 month-to-month or ₹2,399 monthly-equivalent on annual billing and adds AI Copilot EHR plus WhatsApp messaging; Autopilot is ₹4,999 month-to-month or ₹3,999 monthly-equivalent on annual billing and adds the named AI Receptionist and AI Follow-ups modules. GST is added at the prevailing rate, currently 18%. All plans have unlimited visits and notes, no per-note metering, no setup fees, and a 7-day free trial. If billing, pharmacy, or inventory is the main problem, validate a dedicated operational suite rather than assuming that scope here.

<a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> with a real clinic day. Let the note and the record-system choice prove their value before you add more software.

---

## EMR vs EHR vs HMS: What Indian Clinics Actually Need
https://patientsquare.com/in/blog/emr-vs-ehr-explained-india/
Published 2026-08-11 · Updated 2026-08-27 · Tags: emr-vs-ehr, hms, clinic-software, buyer-decision, india

EMR, EHR, and HMS solve three different problems. A decision guide for Indian clinics: what each is for, how to tell which you need, and the trap of buying big.

An EMR is the digital chart for one practice. An EHR is a record built to be shared across providers. An HMS, or hospital management system, is the wider operational suite, billing, pharmacy, beds, claims, with a record system inside it. In short: EMR is the chart, EHR is the shared chart, HMS is the whole hospital's software.

Three acronyms, three different problems, and a lot of software marketing that blurs them on purpose. An EMR stores your clinic's charts. An EHR shares a record across providers. An HMS runs the whole operation with a record inside it. Buying the wrong one is how clinics overspend: a solo GP pays for hospital-grade interoperability they'll never route, or a busy nursing home tries to run beds and billing on a chart tool. This pillar sorts the three by the question each one answers, so you buy for your real bottleneck.

> **Key takeaways**
>
> - EMR = the chart for one clinic. EHR = a record built to move between providers. HMS = the operational suite (billing, pharmacy, beds, claims) with a record inside.
> - Most software sold to Indian clinics as an "EHR" is really an EMR. That's usually fine; just know it.
> - Buy the EHR when you genuinely move records between sites; buy the HMS when operations, not just records, need managing.
> - The label matters less than whether the note gets written. At a two-minute Indian consult, the documentation, not the database, is the usual bottleneck.

_Sources: MoHFW EHR Standards 2016; ONC (HealthIT.gov)._

## Which problem does each acronym solve?

Forget the definitions for a second and think in jobs. Each of these three exists to do a different job, and once you see the job, the acronym stops mattering.

The **EMR** solves recording. Its job is to turn a consultation into a clean, findable digital chart for your clinic. That's it, and that's enough for a lot of practices. The US ONC describes an EMR as the digital version of the paper charts in one clinician's office, a record that doesn't travel easily out of the practice.

The **EHR** solves sharing. Its job is to make that record move: to a specialist, a hospital, a lab, the next facility. India's EHR Standards, published by the Ministry of Health and Family Welfare and revised in 2016, define the EHR as a shareable, standards-based record and recommend common vocabularies (SNOMED CT, ICD, LOINC) precisely because a record only needs shared vocabulary if it's meant to travel.

The **HMS** solves operations. Its job is to run the business of care: registration, billing and GST invoicing, pharmacy and inventory, bed and IPD flow, insurance and TPA claims, with a clinical record living inside the suite. The record is one module among many, not the whole point.

So the three aren't a ladder where bigger is better. They're three answers to three different questions. Our deeper [EMR-vs-EHR breakdown](../emr-vs-ehr-india/) covers the scope distinction on its own; here we're adding the HMS and turning it into a choice.

## How do you tell which one your clinic actually needs?

By your real bottleneck, not the vendor's demo. Run your practice through three questions and the answer usually falls out.

1. **Do I move patient records between sites, hospitals, or specialists as a routine part of care?** If yes, you want a real EHR that actually implements India's EHR Standards, not just claims the acronym. If no, an EMR is enough, and paying for interoperability you never use is money gone.
2. **Do I need to manage operations, not just records?** Billing, pharmacy, inventory, beds, claims. If two or more of those are daily fires, a bare EMR leaves you juggling systems, and an HMS that contains the record is the honest buy.
3. **Are my notes actually complete today, or thin because there's no time?** If the storage is fine but the charts are one-liners, no acronym fixes that. The gap is documentation, a different layer entirely.

Most solo doctors and small groups land on "EMR is enough, and my real problem is question three." Most hospitals and multi-site chains land on "HMS, because operations are the load." The clinics that get burned are the ones that skip these questions and buy on brochure breadth. Our [clinic management software scorecard](../best-clinic-management-software-india/) and [EMR buyer's guide](../emr-software-india-guide/) both walk the shortlist once you know your answer.

## Where do the three overlap, and why the labels blur?

Because vendors bundle. A suite sold as an "HMS" contains an EMR. An "EMR" product may market itself as an "EHR" to sound more capable. And an all-in-one platform claims all three at once. The overlap is real, but so is the trap inside it.

| | EMR | EHR | HMS |
|---|---|---|---|
| **Core job** | Record for one clinic | Record shared across providers | Run the whole operation |
| **Who it's for** | Solo / small clinic | Multi-site care, hospitals | Hospitals, busy clinics |
| **Interoperability** | Limited; export is manual | The point of it | Depends on the record inside |
| **Billing / pharmacy / beds** | No | No | Yes |
| **Honest one-liner** | Digital chart that stays put | A record that follows the patient | The clinic's back office plus a chart |

"All-in-one" is where the blur costs you. A bundle that does registration, billing, pharmacy, and a record can end up doing each part averagely. If your only real problem is charting, buying a full HMS to fix it is like buying a truck to move one box. Decide your bottleneck first, then check whether a bundle does that one part well. For hospitals, our [HMS modules explainer](../hospital-management-system-explained/) shows what a full suite actually contains.

## What does DPDP add to the decision?

A duty that applies whichever acronym you pick. The Digital Personal Data Protection Act 2023 treats patient health data as personal data and makes your clinic the data fiduciary: consent for a stated purpose, purpose-limited use, and security safeguards, whether you run an EMR, an EHR, or an HMS.

So add a fourth buying question: does the system support consent records, role-scoped logged access, and export or deletion on request? A cheaper tool that ignores this is more expensive than it looks, because the compliance gap is yours to answer, not the vendor's. Our [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers what the law asks of any clinic holding patient data.

## What matters more than any of the three labels?

Whether the note gets written at all. This is the part every acronym argument skips, and it's usually the real problem.

The average primary-care consultation in India runs about two minutes. That figure comes from a 2017 BMJ Open systematic review of 67 countries by Irving and colleagues, which clocked consultation length from 48 seconds in Bangladesh to 22.5 minutes in Sweden and put India near the short end. Two minutes to listen, examine, decide, and prescribe. The documentation loses that race. So the note gets compressed to a line, written from memory after the queue clears, or skipped.

No EMR, EHR, or HMS fixes this on its own. A better storage system doesn't make the note appear; it gives a thin note a nicer home. The constraint is upstream of the database, in the gap between a two-minute consult and a complete record. That gap is where charts go missing and, under India's medical-record-keeping expectations, where a clinic's defensibility quietly erodes.

> We think the EMR-vs-EHR-vs-HMS debate gets more clinic attention than it earns, while the thing that actually determines record quality, whether the note gets written well, gets almost none.

## Where does an AI documentation layer sit against all three?

Alongside whichever one you chose, never instead of it. This is the piece worth being precise about, because it's easy to assume an AI scribe is a fourth option competing with the record systems. It isn't.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens during the visit and drafts the note; you review and sign; the signed note lives in whatever EMR, EHR, or HMS you run.

A few things that matter for an Indian clinic. It captures English, Hindi, and 20+ Indian languages including the mid-sentence Hinglish of a real OPD, and the note comes back in clean clinical English. Visit audio is processed in memory and discarded the moment the note drafts, so there's no audio archive to defend under DPDP. Data is handled to DPDP Act 2023 standards, consent-first and purpose-limited. ABDM integration is on the roadmap, not a current claim, and a vendor telling you otherwise deserves a follow-up question. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If the missing piece is the note rather than the record system, that's the layer to fix first, whatever you settle on for storage. <a href="/in/how-it-works/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a real consult turn into a signed note, or read the [pricing in full](../../pricing/). Sort the acronym out, then fix the layer that's actually broken.

---

## Hospital EMR Software in India: What to Look For
https://patientsquare.com/in/blog/hospital-emr-software-india/
Published 2026-08-10 · Updated 2026-08-29 · Tags: hospital-emr, emr-software, abdm, dpdp, india

Specify the hospital clinical record, orders, results, imaging, medication, identity, authorship, amendments, interfaces, downtime, export, and ABDM boundaries.

Hospital EMR software holds the longitudinal clinical record: identity, encounters, notes, diagnoses, allergies, medications, orders, results, imaging references, procedures, discharge documents, authorship, amendments, access, and audit. Operational HMS modules may surround it, but the clinical record boundary should remain explicit.

A hospital EMR is not a long note form. It is the clinical source of truth that must survive departments, shifts, interfaces, corrections, downtime, and discharge.

Many buying errors come from collapsing three layers: the clinical record, the hospital's operational system, and external exchange. Separate them before scoring products.

> **Decision summary**
>
> - Define the clinical record before counting modules.
> - Treat ADT, CPOE, eMAR, LIS, RIS, PACS, pharmacy, billing, and interfaces as acceptance-tested requirements.
> - A FHIR or HL7 format claim does not prove a working interface or write-back.
> - ABDM adds consent-based exchange; it does not replace the hospital record.
> - Hospital Copilot is demo-priced and supports either a complete Patient Square HIS/EHR deployment or an alongside-existing-HIS/EHR path.

## Define the clinical record before the product

Write the minimum longitudinal record as data, not department names:

| Record element | Questions |
|---|---|
| Patient identity | How are identifiers issued, matched, merged, unmerged, and audited? |
| Encounters | How are OPD, emergency, day care, admission, transfer, and discharge linked? |
| Problems and diagnoses | Which terminology is used? Who can correct or retire an item? |
| Allergies and alerts | How are source, certainty, reaction, correction, and override recorded? |
| Medications | How are history, prescription, verification, administration, hold, stop, return, and reconciliation separated? |
| Orders and results | How are order, specimen, status, result, amendment, acknowledgment, and cancellation linked? |
| Imaging | Where are order, worklist, study, images, report, addendum, and critical-result acknowledgment stored? |
| Notes and documents | How are author, signer, time, version, amendment, and attachment represented? |
| Procedures and devices | How are consent, performer, implant, batch, observation, and follow-up captured? |
| Discharge and continuity | What is available to the patient and next care team, and in which form? |
| Consent and access | How are purpose, scope, expiry, withdrawal, role, emergency access, and audit recorded? |

If a demonstration skips identity, correction, or provenance, it has skipped the hard part.

## Keep system boundaries explicit

| Layer | Typical responsibility | Boundary question |
|---|---|---|
| EMR or EHR | Clinical record and clinical workflow | Is this the source of truth for the named data? |
| HIS or HMS | Registration, ADT, beds, billing, pharmacy, inventory, payer, finance, operations | Which operational modules are in the same product and which are connected? |
| LIS | Specimen, analyzer, result, validation | Which system owns order status and corrected results? |
| RIS and PACS | Imaging workflow, reports, images | How are identity, study, report, and image linked? |
| Pharmacy | Formulary, stock, dispensing, returns | Does a clinical prescription become a verified dispense request? |
| ABDM exchange | Consent-based health-information exchange | Which records are shared, under what consent, and what remains local? |
| Patient-facing channel | Access, appointments, messages, payments, consent | What is shown, and which system owns the source data? |

A single vendor may provide several layers. That does not remove the need to name the source of truth and failure owner for each handoff.

## Named routes worth validating

These are not a best-to-worst ranking. They show why the buyer must first decide whether it needs programme software, an open-source operating model, a certified product shortlist, or a scoped commercial deployment.

| Route | What the first-party source establishes | What the hospital still has to prove |
|---|---|---|
| NIC e-Hospital | Its official module list separates Clinic, LIS, and RIS functions inside a government-hospital system | Eligibility, rollout, exact version, module availability, migration, support, and interfaces |
| C-DAC eSushrut | C-DAC describes it as a hospital-management system used in government health settings | Access route, deployment owner, current scope, hosting, support, and exit |
| Bahmni | Its project site describes an open-source hospital and clinic system | Implementation partner, clinical configuration, infrastructure, security, recovery, interfaces, and support |
| NABH software directory | NABH operates separate HIS and EMR product-certification standards and a directory | Certification version, facility fit, excluded workflows, implementation quality, and contract |
| Patient Square Hospital Copilot | Demo-priced with complete Patient Square HIS/EHR and existing-HIS/EHR deployment paths | Required modules, interfaces, migration, acceptance tests, and the chosen source of truth |

A named product gets onto the evaluation sheet only when its access route and evidence fit the facility. A logo on a standards slide does not complete the workflow test.

## MoHFW standards turn "digital" into specific questions

India's 2016 EHR Standards cover capture, storage, retrieval, exchange, analytics, privacy, security, and semantic and technical interoperability. Use them to ask concrete questions:

- Which patient, provider, facility, encounter, diagnosis, medication, observation, and document identifiers are stored?
- Which terminology and value-set versions are used?
- Can the system preserve authorship, digital signatures, timestamps, amendments, and audit trails?
- Which exchange formats are produced, consumed, validated, and retained?
- How are access control, authentication, consent, encryption, backup, and recovery tested?
- How is a complete copy supplied to the patient or another provider?

Do not accept "standards compliant" as the answer. Ask for the conformance statement, sample data, validation result, and exception list.

## ABDM adds exchange, not a central chart

ABDM's FAQ says records remain where providers create and store them. The architecture is federated. Patients can grant granular and time-limited consent for a provider to access shared records and can revoke that consent.

That creates two separate requirements:

1. The hospital must keep a complete, safe local record and remain operational when external exchange is unavailable.
2. The hospital must perform the consent-based ABDM transactions it has actually implemented.

Test provenance, consent status, duplicates, superseded documents, expiry of access, and local availability during exchange failure. Patient Square's ABDM integration remains roadmap-only, so it should not receive points for a live workflow.

## Authorship and amendments cannot be afterthoughts

For every clinical entry, ask:

- Who authored it?
- Who reviewed and signed it?
- When did each event occur?
- Was text imported, dictated, templated, or machine drafted?
- What changed after signing?
- Can the original and amendment both be reconstructed?
- Who viewed, printed, downloaded, or exported it?

The clinician remains responsible for reviewing and signing Patient Square drafts. A structured draft is not a final record until the hospital's signing and filing workflow completes.

## Interface acceptance ladder

Score each required interface at its achieved level:

| Level | Evidence |
|---|---|
| Displayed | A user can view the other system |
| Exported | A file or message can be produced |
| Imported | The destination accepts the file or message |
| Matched | Patient, encounter, order, and author identities are reconciled |
| Workflow-complete | Acknowledgment, retry, correction, cancellation, and exception handling work |
| Operationally monitored | Queues, alerts, support ownership, downtime, recovery, and reconciliation are tested |

"FHIR" can describe a format or API. It does not, by itself, prove the higher levels.

## A ten-encounter trial

Use synthetic data and run ten varied encounters before committing:

1. new OPD patient;
2. returning patient with a possible duplicate;
3. emergency-to-admission transition;
4. inter-ward transfer;
5. lab order with a corrected result;
6. imaging order with report addendum;
7. medication allergy and documented override;
8. discharge with medication reconciliation;
9. downtime entry and recovery; and
10. patient or receiving-provider export.

For each encounter, record completion, errors, duplicate entry, elapsed staff time, source system, final source of truth, audit evidence, and recovery path.

## Patient Square's scoped hospital role

Hospital Copilot is a separate, demo-priced offering and does not inherit Practice Copilot rates. A hospital can deploy the complete Patient Square HIS/EHR or retain its existing HIS/EHR and define Hospital Copilot workflows during discovery. Neither path promises automatic filing or write-back into a named third-party system.

Patient Square's AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The product lists `EHR-ready export (PDF · HL7 · FHIR)`. That exact phrase is an export claim, not certified interoperability or native enterprise write-back.

Required ADT, CPOE, eMAR, LIS, RIS, PACS, pharmacy, billing, and interface workflows must be scoped and acceptance-tested for the selected deployment. Book a demo to map those workflows before selecting a record-system path.

---

## Electronic Prescription Software for Indian Doctors (2026)
https://patientsquare.com/in/blog/electronic-prescription-software-india/
Published 2026-08-09 · Updated 2026-08-27 · Tags: electronic-prescription, e-prescription, erx-software, clinic-software, india

What to look for in electronic prescription software in India: legality under the 2020 telemedicine guidelines, ABDM fit, and the draft-vs-transmission line.

It's software that helps a doctor create a digital prescription: the medicines, dosage, and instructions, produced as a signed electronic document instead of a handwritten slip. In India it's governed by the 2020 telemedicine practice guidelines, which set out what a valid e-prescription must contain, including the doctor's registration number and signature.

Electronic prescription software turns a handwritten slip into a signed digital document, and in India the rules for that are clearer than most vendors let on and murkier in one specific place. Issuing a digital prescription is permitted under the 2020 telemedicine practice guidelines. What isn't a settled, mandatory national rule is automated transmission to a pharmacy. That single line, draft versus transmission, is where a lot of e-prescription marketing gets loose, and it's the first thing a doctor should pin down before buying.

> **Key takeaways**
>
> - Issuing a signed digital prescription is permitted under the 2020 Telemedicine Practice Guidelines; the registration number and signature are the non-negotiable parts.
> - There's no settled, mandatory national e-prescription-to-pharmacy transmission standard in India, unlike the US Surescripts model.
> - "eRx software" spans two very different things: creating a valid prescription versus routing it to a pharmacy. Most legitimate tools do the former.
> - ABDM is a separate question: is the prescription shareable via ABHA, not is it sent to a chemist.
> - AI Medical Scribe by Patient Square produces a prescription draft only and does not transmit to any pharmacy.

_Source: MoHFW Telemedicine Practice Guidelines, 25 March 2020._

## What does electronic prescription software actually do?

Two very different jobs hide under one label, and conflating them is how doctors overpay or, worse, buy a compliance claim that isn't settled.

The first job is **creating a valid prescription**: capturing the medicines, dosage, and instructions and producing a signed digital document with the doctor's name, registration number, and signature. This is legal, well-defined, and what most e-prescription tools genuinely do.

The second job is **transmitting that prescription to a pharmacy** automatically, the way the US Surescripts network routes a prescription straight to a chemist's queue. In India there is no settled, mandatory national standard for this. A tool can produce a lovely signed prescription that the patient still carries or forwards themselves.

When a vendor says "e-prescribing," ask which job they mean. Creating a valid digital prescription is the honest, common case. Automated pharmacy transmission is the claim to scrutinise.

## Is electronic prescribing legal in India?

Issuing a digital prescription: yes. The 2020 Telemedicine Practice Guidelines, issued by the Board of Governors in supersession of the Medical Council of India and published by the health ministry, explicitly let a registered medical practitioner give a patient a prescription. The guidelines say the doctor should provide a photo, scan, or digital copy of a signed prescription, or an e-prescription, to the patient over email or a messaging platform.

The guidelines also set out what a valid prescription carries: the medicines and dosage, the practitioner's name and registration number, and their signature. They include a sample format; following that exact format is recommended rather than strictly mandatory, but the registration number and signature are the parts you don't skip.

Where it gets murkier is the newer rule-making. Specific e-prescription rules under more recent professional-conduct regulation have moved through draft and consultation stages rather than settling into a single operative national mandate. So the safe posture for 2026 is this: a signed digital prescription per the 2020 guidelines is on firm ground; automated pharmacy transmission as a legal requirement is not. Our [e-prescription legality explainer](../e-prescription-software-india-legal/) goes deeper on the regulatory specifics.

## What must a valid e-prescription contain?

Keep it concrete. Per the 2020 telemedicine guidelines, a prescription that will hold up needs:

| Element | Why it matters |
|---|---|
| Medicines, dosage, instructions | The clinical content; the reason the prescription exists |
| Practitioner's name | Identifies who prescribed |
| Registration number | Ties the prescription to a registered medical practitioner; non-negotiable |
| Signature (digital or scanned) | Makes it a valid, attributable document; non-negotiable |
| Shared with the patient | Photo, scan, digital copy, or e-prescription over email or messaging |

Software that produces this reliably, with the registration number and signature baked in, is doing the real job. The sample format in the guidelines is a good template; the two elements you never drop are the registration number and the signature.

## How does e-prescription relate to ABDM?

They're separate questions that get muddled. ABDM, run by the National Health Authority, is about linking a patient's records to their ABHA and sharing them on consent. It is not about routing a prescription to a pharmacy.

A prescription can *become part of* the ABDM record if your software is ABDM-ready at the relevant milestone (M2 shares records on consent). But that's the record-sharing question, not the "did it reach the chemist" question. So when you evaluate e-prescription software, split the two: is the prescription a valid document, and separately, is it shareable via ABDM if you want that. Our [ABDM Milestone 2 explainer](../abdm-milestone-2-explained-clinics/) covers the sharing side; don't let a vendor collapse the two into one vague "ABDM e-prescribing" claim.

## What should Indian doctors look for in 2026?

Five things, in rough priority order.

1. **A valid format, reg number and signature built in.** The non-negotiables from the 2020 guidelines. If a tool can't reliably stamp your registration number and signature, it fails at the basics.
2. **Honesty about draft versus transmission.** Ask directly: after I sign, what happens to the prescription? Does the patient carry it, or does the software claim to send it to a pharmacy, and if so, on what standard? Be sceptical of a settled-transmission claim.
3. **DPDP-aware storage.** A prescription is patient data. Under the Digital Personal Data Protection Act 2023 you're the fiduciary. Ask where it's stored and for how long. The [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers this.
4. **ABDM clarity if you want records linked.** Only relevant if you want the prescription in the shareable ABDM record. Make the vendor name the milestone.
5. **Drug-safety checks.** A prescription tool that flags interactions before you sign is worth more than one that just formats text prettily.

## When is a dedicated e-prescription tool the better fit?

When prescribing is genuinely your workflow's centre and you want a purpose-built tool for it, a dedicated e-prescription or full EMR module can be the right buy, especially if it's cleared the ABDM milestone you care about and handles interactions well. If you run a high-prescription practice and want the prescription tightly wired into your record and billing, a full EMR's e-prescription module beats a scribe's draft. Be honest about that. Our [EMR software guide for India](../emr-software-india-guide/) weighs those suites.

We'll say the boundary plainly for our own product, because this is exactly where marketing tends to blur.

## Where does AI Medical Scribe by Patient Square fit, and where does it stop?

In the drafting slot, with a hard ceiling we won't cross. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

Here's the ceiling, stated without hedging: **the scribe produces a prescription draft only. It does not transmit to any pharmacy.** There's no chemist gateway, no Surescripts-style routing, no auto-send. The doctor reviews the draft, edits it, and signs it, and that signed prescription is theirs to hand or forward to the patient. The scribe doesn't screen the draft for interactions, dosing, or contraindications. The doctor does that, exactly as they do today, so the clinical safety check stays with the person signing. It takes code-mixed Hinglish on input and returns the note in clean clinical English, the visit audio is processed in memory and discarded once the note drafts, and data is handled to DPDP Act 2023 standards. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

So if your need is automated pharmacy transmission, we're not your tool, and we'll tell you that up front rather than after the invoice. If your need is a fast, safe, valid prescription draft that comes out of the consultation itself, that's exactly what the scribe does. See which one you actually need, then <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to watch a prescription draft come together in the room, or read how we protect data on the [security page](../../security/).

---

## EMR and Practice Management Software: Buy One or Both?
https://patientsquare.com/us/blog/emr-practice-management-software/
Published 2026-08-07 · Updated 2026-08-29 · Tags: guide, comparison, ehr, small-practice, scheduling

Map charting, scheduling, claims, and patient communication before choosing an integrated EMR and practice management suite or separate systems.

An EMR (or EHR) is the clinical record: notes, problem lists, medications, results. Practice management software runs the business side: scheduling, registration, billing, claims, and reporting. They overlap at the patient's chart but solve different jobs. Many small practices run both, either as one bundle or two separate tools that pass data back and forth.

If every product on your shortlist says "all-in-one," the label has stopped helping. A clinic does not buy a label. It buys a path from appointment to signed note to claim to patient balance, and that path can still break inside a one-vendor suite.

This guide gives you a field-ownership map, a live demo script, and a cost worksheet. Use them to decide whether one suite or separate EMR and practice management systems fit the work you actually do.

> **Key takeaways**
>
> - The EMR owns clinical documentation. Practice management usually covers operational and financial work, but exact scope varies by product.
> - "All-in-one" is not a technical standard. One login does not prove one database, reliable interfaces, or complete billing functionality.
> - Keep separate systems when the specialty record or revenue-cycle workflow matters more than vendor consolidation.
> - Patient Square covers documentation, scheduling, and a bundled AI EHR by plan. Test the rest of the workflow against the ownership map below.

## What is the difference between an EMR and practice management software?

The EMR is the clinical record. It is where clinicians document the encounter, review history, record assessments and plans, and sign or amend notes. CMS tells Medicare practitioners that documentation should be complete and legible, identify the encounter reason, findings, assessment, plan, date, and author, and support the codes submitted. That is the clinical-record job.

Practice management software runs work around the encounter. Depending on the product, that can include appointment books, registration, insurance details, eligibility, charges, claims, remittance, patient balances, and operational reporting. Do not assume every product includes every row. Some "practice management" products stop at scheduling and intake; others are built around claims.

The systems touch the same people and visits, which creates the purchasing decision. A scheduled appointment may need to open an encounter in the EMR. A signed note or selected code may need to reach a billing queue. A demographic correction may need to update more than one record. The useful question is not "Do we need an EMR or PMS?" It is "Which system owns each field, and how does the next system receive it?"

## The appointment-to-payment ownership map

Copy this table into your evaluation sheet. Fill it with product names, not "integrated" or "automatic."

| Workflow object | Required owner | Data the next step needs | Failure to reproduce in the demo |
|---|---|---|---|
| Patient identity | One named master record | Name, date of birth, contact and payer identifiers | Duplicate patient or conflicting edit |
| Appointment | Scheduling system | Clinician, location, visit type, date and status | Cancelled visit still opens an encounter |
| Clinical encounter | EMR | Signed note, author, date and permitted code data | Note cannot be amended or author is lost |
| Charge or claim | PMS, billing tool, or service | Patient, payer, service, code and documentation link | Staff must retype protected or billable data |
| Remittance and balance | PMS, RCM tool, or ledger | Adjudication, adjustment and patient responsibility | Payment posts to the wrong visit |
| Archive and export | Contractually named system | Complete, usable record in an agreed format | Vendor cannot produce a test export |

This is the original artifact that catches most "all-in-one" ambiguity. The product can use a shared database, an API, an interface, or a manual handoff. Architecture matters less than a reproducible result, a monitored failure path, and one owner for support.

## What does all-in-one EMR and practice management software really mean?

There is no standard feature set behind the phrase. It can mean one contract, one login, one vendor, one database, or a collection of modules connected behind the scenes. Those are different benefits.

One contract can simplify procurement but still leave several support queues. One login can reduce password fatigue but says nothing about duplicate patient records. A shared database can reduce synchronization work but does not guarantee that a correction reaches every workflow. Separate systems can work well when their interface is tested, monitored, and owned.

Treat "all-in-one" as a claim to investigate. Ask these four questions:

1. Which module is the source of truth for patient identity, appointment, signed note, charge, claim, and balance?
2. Which fields move in real time, in a batch, through an export, or not at all?
3. Who receives the support ticket when the sending and receiving records disagree?
4. What remains available, and in what format, when the contract ends?

An "HL7" or "FHIR" bullet does not answer those questions. A file labelled for export is not the same as a live interface, certified capability, or native write-back. Ask the vendor to show the precise exchange your practice will use.

## The seven-event demo that exposes workflow gaps

A polished happy-path demo is easy. Give every finalist the same seven events and have a staff member record the clicks, delays, duplicate entry, and support answer.

1. Register a new patient whose name resembles an existing patient.
2. Reschedule the appointment, then cancel it after an encounter was prepared.
3. Change an insurance identifier and show where the correction propagates.
4. Draft, review, sign, and amend a clinical note while preserving author and date.
5. Create a charge or export the required encounter data without retyping it.
6. Correct a rejected or incomplete billing item and trace the change back to its source.
7. Export that patient's usable record and explain deletion or retention after termination.

Score the observed workflow, not the salesperson's explanation. A strong product can still be the wrong choice if your staff must bridge the one step that occurs hundreds of times a week.

## When one suite is the better choice

A combined suite deserves the lead when it passes the seven-event test, eliminates meaningful duplicate work, covers the billing depth you need, and has a clear migration and exit plan. Consolidation is especially useful when the current pain is identity mismatch, repeated registration, or support disputes between vendors.

Do not award the decision merely because the practice is small. A solo specialist may need a deep specialty chart. A larger cash-pay group may have simple billing. Practice size changes seat count and governance; workflow complexity determines the architecture.

One more practical check concerns protected health information. HHS explains that merely selling software does not make a vendor a business associate, but hosting PHI or accessing it for support can. Establish the role and execute the required business associate agreement before that access begins. A security badge cannot substitute for the contract and data-flow review.

## When separate EMR and practice management systems win

Keep or buy separate systems when one side is already doing difficult work well. Common examples include a specialty record clinicians will not replace, a billing operation that needs clearinghouse and denial workflows, a multi-entity setup with specific reporting, or an established RCM partner that depends on a known queue.

The tradeoff is interface ownership. Put the following in the contract or implementation plan:

- exact sending and receiving systems;
- fields, direction, timing, and error handling;
- patient matching and duplicate-resolution rules;
- monitoring owner and support response;
- test cases for corrections, cancellations, amendments, and downtime;
- export format and responsibilities at termination.

Separate systems are not automatically a mess. Unowned interfaces are.

## How to compare the real first-year price

Per-clinician subscription is only one row. Ask each vendor for the same cost schedule, then calculate your own total.

| Cost row | Suite | Separate systems |
|---|---:|---:|
| Clinician and staff subscriptions | $___ | $___ + $___ |
| Implementation and configuration | $___ | $___ |
| Data migration and validation | $___ | $___ |
| Interface, clearinghouse, or transaction fees | $___ | $___ |
| Training and reduced-capacity time | $___ | $___ |
| Required support or success plan | $___ | $___ |
| Year-one total | $___ | $___ |
| Written renewal total | $___ | $___ |

Do not convert an unknown line to zero. Mark it "quote required." Also record whether the rate is monthly, an annual monthly equivalent, a promotion, or a contract minimum.

## Where Patient Square fits, and where it does not

Patient Square is a narrower fit than a full EMR-plus-PMS buying category. Practice Copilot includes an ambient medical scribe, scheduling from the Assist plan, and a bundled AI Copilot EHR plus WhatsApp messaging from the Copilot plan. The public annual monthly equivalents are $79 per clinician for Assist, $119 for Copilot, and $199 for Autopilot. Month-to-month rates are $99, $149, and $249.

The scribe produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Every plan lists EHR-ready export (PDF · HL7 · FHIR). That wording describes an export option. It does not promise native write-back into every EHR or establish a particular certification.

Patient Square does not publicly offer a full US claims, clearinghouse, insurance-eligibility, patient-balance, or revenue-cycle engine. If appointment-to-payment is the main purchase, keep a dedicated PMS, billing product, or service in the architecture. If documentation, scheduling, and a bundled record are the core job, [compare the product options](/us/compare/) and test your exact handoff.

We also cannot prove from a public feature list that every Patient Square module shares one database. Ask for a live demonstration of the fields you need. That is the same standard this guide applies to every vendor.

## Make the decision from evidence

Choose one suite when it covers the complete workflow, reduces real duplicate work, and survives the correction and exit tests. Choose separate systems when a specialty or revenue-cycle capability is worth maintaining and the interface has a named owner. Keep the current setup when neither finalist beats the baseline in measured staff time, error rate, and handoff reliability.

The ownership map is the decision document. The seven-event demo supplies the evidence. The first-year worksheet prevents a low subscription from hiding a costly migration or interface. For deeper category definitions, read the [practice management software guide](../medical-practice-management-software-guide/) and [patient management software guide](../patient-management-software-guide/). For the security review, start with the [Patient Square security page](/us/security/) and verify each claim in your own agreement.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot works alongside it. A new practice can instead use the bundled Patient Square EHR, available from the Copilot tier, as its system of record. Neither path promises automatic filing or write-back into a named third-party EHR.

For the documentation, scheduling, and record test, [compare the product options](/us/compare/). Keep the separate billing or claims system in the test whenever it remains part of the workflow.

---

## Hospital Queue Management: OPD Token & Flow (2026)
https://patientsquare.com/in/blog/hospital-queue-management-system-india/
Published 2026-08-07 · Updated 2026-08-29 · Tags: queue-management, opd-token, patient-flow, hospital-software, india

How hospital queue management works for OPD and IPD in India: token systems, patient flow, and a timestamp framework for a local pilot.

It is the software and hardware used to coordinate patient movement: OPD token generation, display boards, counter and consultation-room routing, and IPD movement between departments. A procurement team should define the calling sequence, priority rules, handoffs, and downtime behaviour it needs before evaluating a system.

Hospital queue management records and displays the next step in a patient journey. At its simplest, a patient registers, receives a number, sees a call, and enters the next service. A wider hospital workflow may also record transfers between OPD services and IPD departments. This guide explains the scope to verify and a timestamp framework for a local pilot.

> **Key takeaways**
>
> - Queue management is usually evaluated as OPD token flow: registration, a numbered token, a calling state, and the next service.
> - IPD flow covers a different set of events: admission, bed allocation, ward movement, procedures, and discharge.
> - A token display does not add clinical capacity. Measure the existing handoffs before claiming an outcome.
> - Ask a vendor to demonstrate the connection between the token, registration, the clinical record, and billing if those are in scope.
> - Treat documentation as a timestamp hypothesis, not an assumed cause of queue delay.

_Source: Irving et al., BMJ Open 2017._

## How does hospital queue management actually work?

Consider a 9am OPD with one registration counter and several consulting rooms. The hospital must state its intended calling rules before it can evaluate a system. A basic workflow can record registration, issue a numbered token associated with a doctor or department, and show a call on a display or announcement.

Diagnostic return handling needs its own test. If a patient leaves the OPD flow for a blood test or X-ray, ask the vendor to show how the system records the transfer, assigns the later state, and preserves the audit trail. Do not assume every token system uses the same rule.

A display can make the calling state visible. It does not establish that patients will wait differently, that priorities are fair, or that throughput will change. Those are local hypotheses that the pilot has to measure.

## Instrument the journey before buying screens

A token display covers one visible event. The workflow behind it needs timestamps and an owner at each handoff.

| Event | Timestamp owner | Next consumer |
|---|---|---|
| Arrival | Kiosk, desk, app, or greeter | Registration |
| Registration complete | Front desk | Queue controller |
| Patient called | Queue system | Patient and room |
| Service starts | Clinical department | Next service or exit |
| Transfer or pause | Sending department | Receiving queue |
| Completion or no-show | Department | Recovery owner |

Without these events, a facility cannot separate delay at registration from delay in a room, a clinical service, a result, or a missed visit. Track a median and a long-tail measure for arrival-to-registration and ready-to-service time. The two measures answer different questions.

## What's the difference between OPD and IPD flow?

They run on different clocks.

**OPD flow** is outpatient and usually same-day: registration, token or appointment, consultation, and any follow-on service such as a test or pharmacy. The procurement scope should state the queues, routing rules, and handoffs to be tested.

**IPD flow** is inpatient and multi-day: admission, bed allocation, ward movement for procedures, and discharge. A hospital may want to track these events in the same platform, but that is a scope decision to verify, not an automatic property of a token system.

A standalone token device may address only a limited OPD workflow. NIC e-Hospital separately lists registration, appointment, and admission-discharge-transfer modules, which is a useful prompt for defining scope. Our [hospital management system explainer](../hospital-management-system-explained/) explains how IPD events can sit alongside the clinical record. If you run a clinic rather than a hospital, the [clinic queue management guide](../clinic-queue-management-india/) is scoped to a smaller, single-doctor setting.

## What should you look for in a queue system in 2026?

Use five procurement tests instead of a generic feature list.

1. **Diagnostic return handling.** Ask the vendor to demonstrate a patient sent for a scan, the transfer event, the return rule, and the audit trail.
2. **Multi-doctor and priority handling.** Define the authorised priority owner, routing rule, exception log, and display behaviour, then test each one.
3. **Connection to the record.** If registration, consultation, billing, or diagnostics must be connected, ask for one end-to-end demonstration using the hospital's expected roles.
4. **Capacity boundary.** A queue display cannot add clinical capacity. Use the timestamp baseline to show where the available capacity is consumed.
5. **Preparation for DPDP duties.** Tokens can be associated with patient identity. Ask where data sits, how long it is kept, who has access, and who will own preparation for scheduled DPDP duties when applicable sections commence.

The [ABHA linking workflow guide](../abha-linking-clinic-workflow/) covers a related front-desk identity workflow. It is not evidence that every queue system has the same identity scope.

## Test the queue effect before buying

Do not accept a waiting-time claim without a local before-and-after measure. Use the timestamp sheet above to compare arrival-to-registration, ready-to-service, service duration, transfers, and no-shows. A token display may expose a local handoff condition, but it cannot add clinical capacity. The pilot should identify the constraint before the hospital makes an outcome claim.

## Test whether documentation is a bottleneck

Documentation is a hypothesis to test. Measure service start, service end, note completion, and the next patient call for the same department. The BMJ Open review supplies consultation-duration context; it does not establish that a queue product or a documentation tool changes waiting time at a particular hospital.

## Where does a scribe fit in the flow?

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

Patient Square lists Scheduling, but its public material does not establish a hospital token display, clinical triage, multi-department routing, diagnostic return handling, or enterprise patient-flow engine. A hospital can use Hospital Copilot as the complete Patient Square HIS/EHR or alongside its existing HIS/EHR. It should not infer queue-controller capability from the Scheduling module name.

If the local pilot identifies a queue-rule or handoff condition, procure and test a system that covers the required routing, exception, and downtime behaviour. If the timestamps identify documentation as a constraint, bring those timestamps and the incumbent HIS/EHR to <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>.

---

## Medical Charting Systems: How Modern Charting Works
https://patientsquare.com/us/blog/medical-charting-systems-guide/
Published 2026-08-07 · Updated 2026-08-27 · Tags: guide, charting, documentation, scribe, small-practice

Medical charting has moved from paper to EHR templates to dictation to ambient AI. Here's how each generation works and what to look for when you pick one.

It's the method and software a clinician uses to turn a patient encounter into a permanent record entry. That covers paper charts, the templated note tools built into an EHR, dictation software, and newer ambient AI that drafts the note from the visit conversation. Each generation changed how much a clinician has to type versus review.

A medical charting system is the method you use to turn a patient visit into a record entry. In the US that's almost always electronic now: you chart inside an EHR using templates and dot phrases, or you speak the note with dictation, or you let ambient AI draft it from the conversation and review the result. Each generation cut the work in a different place. Our published [pricing](/us/pricing/) starts at $79 per clinician per month.

> **Key takeaways**
>
> - Charting has moved through four generations: paper, EHR templates, dictation, and ambient AI. Each one moved the clinician's effort somewhere different.
> - About 88% of US office-based physicians used a certified EHR by 2021, per ONC data, so the real choice today is which electronic charting method fits, not paper versus digital.
> - Physicians spend roughly 2 hours on EHR and desk work per 1 hour of direct care, per a 2016 Annals study; charting is where most of that goes.
> - When you pick a charting system, weigh five things: note structure, speed to signed note, edit burden, export/portability, and security. Rank them by your own visit mix.

## What a medical charting system actually is

A charting system is whatever gets the encounter into the record. That's it. The record has to exist for care continuity, billing, and medico-legal reasons, and the charting system is the machinery that produces it. Everything else is a detail of how.

The confusing part is that the term covers four very different generations of machinery, and vendors rarely say which one they're selling. A paper chart and an ambient AI scribe both "chart a visit," but the work they ask of you couldn't be more different. So before comparing products, it helps to see the four generations plainly, because the one you pick decides where your effort lands every clinic day.

Most notes, regardless of generation, land in a standard shape: SOAP, for Subjective, Objective, Assessment, Plan. A SOAP note charting system is just a tool that produces that structure. The question is who fills the four sections. You, by typing? You, by talking? Or the software, from listening?

## How charting got here: four generations

Charting didn't jump from paper to AI. It moved in steps, and each step solved the last one's biggest complaint while creating a new one.

**Paper.** Fast to write, terrible to find. A paper chart is quick in the moment and a nightmare at scale: illegible handwriting, one physical copy, no way to search a panel of patients or flag a drug interaction. It's nearly gone from US primary care as a main system, though some clinics keep it for downtime.

**EHR templates.** This is what "electronic charting" means to most people. Federal incentive programs pushed adoption hard, and by 2021 about 88% of US office-based physicians used a certified EHR, per ONC figures. Templates and dot phrases made structured, searchable, billable notes normal. The new complaint arrived fast: clicks. Charting became a typing-and-tabbing job, and it followed clinicians home.

**Dictation.** Speak the note, the software types it. Dictation cut the keyboard out of the loop and gave word-level control, which suits procedure notes and terse assessments. But you're still composing the whole note in your head; you've just swapped fingers for voice, and you still proofread every line.

**Ambient AI.** The newest generation listens to the visit itself and drafts the note. Your job changes from writing to reviewing. It's the only generation that removes composing from the clinician rather than speeding it up.

Read that progression and the pattern is clear: each generation attacked a different bottleneck. Paper fixed nothing but speed of a single entry. Templates fixed retrieval and billing. Dictation fixed typing. Ambient goes after composing itself.

## Why charting is worth fixing at all

Here's the pressure behind every one of these systems. A 2016 study in the Annals of Internal Medicine, from Sinsky and colleagues, found physicians spend about 2 hours on EHR and desk work for every 1 hour of direct patient care. A 2023 JAMA Network Open study measured roughly 36 minutes of ambulatory EHR time per 30-minute visit. The documentation can take as long as the medicine.

That's the after-hours charting, the notes you finish at 9pm, the reason a 22-patient Wednesday follows you home. A charting system is a bet on moving some of that off your own hands. Which generation you pick decides how much actually moves, and whether it moves to a quick review step or just to a faster kind of typing.

## What to look for in an electronic charting system

Skip the feature grids. Five things decide whether a charting system fits your practice, and you should rank them by your own visits before you look at a single demo.

**Note structure.** Does its output match how your specialty documents? A behavioral-health note, an ortho procedure note, and a well-child check don't share a shape. A charting system that fights your specialty's format taxes you on every visit. Ask whether it produces the structure you actually sign, not a generic one.

**Speed to signed note.** Not "speed to draft." The number that matters is minutes from patient-leaves to note-signed, including your edits. A fast draft that needs heavy correction can be slower than a tight template you fill in three keystrokes.

**Edit burden.** This is the one buyers underestimate. Every generation trades composing effort for editing effort at a different ratio. Templates need you to write the variable parts. Dictation needs you to proofread the whole thing. Ambient needs you to check a draft you didn't write. Know which kind of after-work you're signing up for.

**Export and portability.** Can you get a note out cleanly, and does it move into your record? If a note is trapped in one system's format, you have a lock-in problem the day you switch. Look for real export, and understand the difference between exporting a note and a certified interface into your EHR.

**Security posture.** Charting means handling PHI. The non-negotiables are a signed Business Associate Agreement and a clear, written security story. Treat any vendor that gets vague here as a no.

## How ambient charting changes the job

Ambient AI is the generation worth understanding closely, because it changes what you do rather than how fast you do it. Instead of composing at all, you have the conversation, and the software drafts the note from what was said. Your work becomes review.

The AI Medical Scribe by Patient Square, one module of the Practice Copilot platform, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. You read the draft, fix what's wrong, sign. Composing leaves your plate.

The evidence is real but read it carefully. A 2025 study in NEJM AI measured a meaningful reduction in per-note documentation time for one ambient tool. We won't inflate that into a promise, because your savings depend on your visit mix and how much you edit. The honest version: ambient moves the most burden on varied, conversational visits, and less on the short structured ones a good template already handles. We think that's exactly where it earns a subscription, and where a template can't follow you: the visit that won't fit a form.

## When a built-in EHR template is the better fit

We build ambient software, so take this as a deliberate concession. For some practices, the templated charting already in your EHR is the right answer, and an ambient tool would be wasted money.

If your visits are short, repetitive, and highly structured (a high-volume urgent-care line, a vaccine clinic, a screening-heavy panel), a sharp template with good dot phrases can beat reviewing an AI draft. There's little to edit that you didn't already know how to type in a few keystrokes. Templates keep required fields consistent, which billing and audits like, and they add no recurring cost when they already live in your EHR. A lean practice on a tight per-provider budget with a predictable panel should build its templates first and only look at ambient if variance and after-hours charting are the real pain.

Ambient earns its keep when the visit won't fit a form, when eye contact with the patient matters, and when the note-writing is what's eating your evenings. Match the generation to the visit, not the marketing.

## How to pick the right charting system for your practice

Answer three questions about your own days, then the choice mostly makes itself.

How much do your visits vary? Low variance favors EHR templates. High variance favors ambient. How much do you value control over exact wording? High value nudges toward dictation. And where does your time leak: during the visit, or after it? If it's after, on charting that follows you home, that's the ambient case.

Whichever generation you lean toward, it has to land in your record system. Native templates already do. For dictation and ambient, ask how the note reaches your chart. Patient Square gives you EHR-ready export (PDF, HL7, FHIR), which moves a finished note into your workflow; treat that as an export path, not a certified two-way interface, and confirm the mechanics for your specific EHR before you buy. For the method-by-method trade-offs, [medical documentation software: ambient vs the old way](../medical-documentation-software/) goes deeper on each approach, and if after-hours notes are your real problem, [cutting charting time for clinicians](../reduce-charting-time-clinicians/) is the sharper read.

## The honest way to decide

You can argue the trade-offs on paper forever. The only test that settles it is a week of real visits. Pick your busiest, most representative days, run the candidate on them, and count two numbers: minutes to a signed note, and how many notes you finished before you left the building.

For templates, that's a build exercise inside your EHR. For an ambient tool, it's a short trial on live patients. Patient Square offers a 7-day trial, so you can run the scribe on an actual clinic day instead of a demo script. If you want to hold an ambient draft up against your current template workflow, book a short demo and we'll run it on your own visit types. You can also see how the plans line up on the [pricing page](/us/pricing/).

A charting system isn't one product with a winner. It's four generations of solving the same problem, and the right one is whichever moves the most work off your specific Wednesday.

## Frequently asked questions

The FAQ above covers the recurring questions: what a charting system is, how modern charting works, what to look for, the SOAP format, whether paper survives, and how compliance works. For the full plan breakdown, see the [pricing page](/us/pricing/).

---

## Clinical Notes Software 2026: AI Notes vs Manual
https://patientsquare.com/us/blog/clinical-notes-software-guide/
Published 2026-08-06 · Updated 2026-08-27 · Tags: clinical-notes, soap-note, scribe, documentation, comparison

Clinical notes software in 2026 splits two ways: AI drafts the SOAP note from the visit, or you chart it by hand. How each handles structure, time, and fit.

It's any tool that produces a clinical note from a patient encounter. Two shapes exist in 2026: manual charting, where you type or click the note into a template, and AI-drafted charting, where an ambient tool listens to the visit and writes a SOAP note you review and sign. They differ mostly in whether you compose the note or edit one.

Clinical notes software in 2026 comes in two shapes. Either you chart the note by hand in a template, or an AI drafts a SOAP note from the visit and you review and sign it. Manual charting gives you control and costs nothing extra inside most EHRs. AI-drafted charting shifts your work from composing the note to editing one, with the draft ready about two minutes after the visit. Our published [pricing](/us/pricing/) starts at $79 per clinician per month.

> **Key takeaways**
>
> - Clinical notes software splits two ways in 2026: manual charting inside your EHR, or an AI that drafts a SOAP note you review and sign.
> - AI-drafted notes land about 2 minutes after the visit, structured into all four SOAP sections; you edit rather than compose.
> - Ambulatory physicians log a median of 36.2 minutes of EHR time per 30-minute visit, per a 2023 JAMA Network Open study. That's the burden AI drafting targets.
> - Manual charting still wins on very short, structured visits, for fast typists, and anywhere recording isn't allowed.

## What clinical notes software actually is

A clinical note is the record of what happened in a visit: what the patient reported, what you found, what you concluded, and what you're doing about it. Clinical notes software is anything that turns the encounter into that written record. In practice it's one of two things.

The first is manual charting. You open a note template in your EHR and fill it in, typing free text or triggering reusable phrases (dot phrases, macros, whatever your EHR calls them). You compose the note. It's the default because it's already in the system you bought.

The second is AI-drafted charting. An ambient tool listens to the visit, transcribes it, and writes the note for you. You don't compose. You review a draft and correct it. That's the real difference between the two, and it changes how a clinic day feels more than any feature list does. If you're weighing the older approaches too, we compare templates, dictation, and ambient AI in our [guide to medical documentation software](../medical-documentation-software/).

Most of the confusion in this category comes from the word "note" doing too much work. A template that gives you a blank SOAP skeleton is clinical notes software. So is a tool that writes the whole note from a recording. They sound similar and behave nothing alike.

## How AI clinical notes software drafts a SOAP note

The SOAP note has four sections, and a good AI tool fills all four from the same visit conversation. Here's what lands in each:

- **Subjective:** the patient's story in their words. Chief complaint, history of present illness, relevant review of systems. This is the part the AI pulls almost entirely from what the patient said out loud.
- **Objective:** exam findings, vitals, anything measured or observed. The AI drafts what you spoke aloud during the exam; the numbers you didn't say still need to be added.
- **Assessment:** your clinical impression. The AI drafts this from your spoken reasoning, and it's the section you'll edit most, because judgment is yours, not the model's.
- **Plan:** what happens next. Medications, orders, follow-up, patient instructions. This is where a prescription draft and ICD-10 suggestions attach.

The pipeline behind it is short. Ambient capture during the visit, speech-to-text, then a language model that sorts the transcript into those four buckets. The draft is ready about two minutes after the visit ends. Then the step that matters: you read it, fix what's wrong, and sign. Nothing enters the chart on its own. If you want the full mechanism, we walk through it in [how an AI scribe works](../ai-scribe-for-medical-notes/).

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The ICD-10 pieces are suggestions and the prescription is a draft; both wait for your sign-off, same as the note itself.

## AI-drafted notes vs manual charting, side by side

The honest way to compare these isn't feature counts. It's the work each one creates on a real Tuesday with 18 patients on the schedule. Here's how they line up.

The pattern most clinics see: manual charting feels free because it's already in the EHR, but the cost shows up after hours. A 2023 JAMA Network Open study found ambulatory physicians averaged about 36 minutes of EHR time for every 30-minute visit, and a 2016 study in the Annals of Internal Medicine from Sinsky and colleagues put it at roughly two hours of EHR and desk work per hour of direct patient care. That time doesn't disappear when charting is manual. It moves to the evening.

AI drafting targets that specific leak. It doesn't make you faster at composing; it removes the composing step for most of the note. If your after-hours time is going to charts, that's the trade that pays back. If it isn't, keep reading, because manual charting is genuinely the better call for some practices.

## When manual charting is the better fit

We build an AI scribe, and we'll still tell you plainly: for some visits, manual charting wins. Three cases where an AI tool is the wrong buy.

Very short, structured visits. A busy urgent-care line or a run of near-identical follow-ups is faster with a tight template and dot phrases than with reviewing a draft. The visit is over before an ambient tool saves you anything, and a well-built template keeps required fields consistent for billing. If your day is 25 quick, repetitive encounters, a template beats a draft.

Clinicians who already type fast and think in structured notes. If you compose a clean assessment in the room without breaking stride, editing an AI's version can feel like extra work, not less. Some people are just faster at charting than others, and the honest answer is that an ambient draft doesn't help them much.

Anywhere recording isn't an option. Ambient tools need to capture the room. If your setting doesn't permit in-room recording, or your patients won't consent to it, AI drafting is off the table and manual charting is what you've got. That's not a knock on the tool; it's a hard constraint, and it's worth checking before you buy anything.

For those practices, buying an ambient tool would be money spent on a problem you don't have. We'd rather you skip it than regret it.

## What to check before you switch

If your visits are varied and talk-heavy and your after-hours time is leaking into charts, AI-drafted notes are usually the better trade. A few things worth confirming on any tool before you commit:

- **Does the draft come out as a real SOAP note, or a transcript with headers?** Ask to see a draft from a visit like yours. Structure quality is the whole point.
- **How much do you edit?** The draft that needs a total rewrite saves nothing. Test edit burden on your own patients during a trial.
- **Where does the note go?** Some tools write into named EHRs; others export. Patient Square offers EHR-ready export (PDF, HL7, FHIR) on every plan, which is an export path, not a certified two-way interface.
- **What happens to the audio?** Ask every vendor. Patient Square processes visit audio in memory and discards it once the note is drafted, so there's no audio archive.
- **Is the price on the page?** Several large vendors publish no number and route you to sales. Ours is on the [pricing page](/us/pricing/): from $79 per clinician per month on the annual Assist plan, unlimited visits and notes.

On compliance, ask for it in writing. Patient Square's safeguards are HIPAA compliant, BAAs are available for every customer, and a SOC 2 Type II audit is in progress. Verify that with any vendor before you send real patient data.

The cleanest way to decide is to run the draft on your own note types for a week. Start by <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">comparing the options</a>, then test a SOAP draft on visits that look like yours.

## Bottom line on clinical notes software

Clinical notes software in 2026 is really a choice between composing the note and editing one. Manual charting keeps you in control, costs nothing extra in most EHRs, and stays the right pick for short, structured visits, fast typists, and settings where recording isn't allowed. AI-drafted charting writes a structured SOAP note about two minutes after the visit and shifts your work to review and sign, which is the better trade when varied visits are leaking charting into your evenings.

For the AI side, the number worth comparing is the all-in one. Ours is published on the [pricing page](/us/pricing/), starting at $79 per clinician per month. You can <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> before testing SOAP drafts on your own visits.

## Frequently asked questions

The FAQ above covers the recurring ones: what clinical notes software is, how AI drafts a SOAP note, when manual charting still wins, EHR export, and cost. For the full breakdown of what's in each plan, see the [pricing page](/us/pricing/), and a demo runs the scribe on your real note types.

---

## Free & Open-Source Hospital Software India: Where It Breaks
https://patientsquare.com/in/blog/free-hospital-management-software-india/
Published 2026-08-06 · Updated 2026-08-29 · Tags: hospital-management-software, open-source, free-software, hms, india

Compare e-Hospital, eSushrut, Bahmni, and open-source hospital software by eligibility, deployment, support, security, interfaces, staffing, and total cost.

There is no universal best option. NIC e-Hospital is an as-is government-hospital SaaS programme. C-DAC eSushrut is a public-sector hospital system whose access and support route must be confirmed. Bahmni is open source and can be operated locally. Eligibility and operating ownership decide the shortlist before features do.

A zero licence fee does not keep a hospital running at 2 a.m. Someone still owns registration, wards, lab and radiology handoffs, pharmacy stock, bills, claims, backups, upgrades, and incident response.

India has credible public and open-source hospital systems. They are not interchangeable free downloads. The first filter is eligibility; the second is operating ownership.

> **Decision summary**
>
> - NIC e-Hospital is described for government hospitals; do not infer private eligibility.
> - eSushrut's programme, version, deployment, and support route require facility-level confirmation.
> - Bahmni removes a proprietary licence but leaves implementation and continuity work to the hospital or a partner.
> - Hospital Copilot is a separate, demo-priced product rather than a free HMS.

## The three routes buyers often mix together

| Route | What it is | First question |
|---|---|---|
| NIC e-Hospital | An as-is SaaS product described by NIC for government hospitals | Is this facility eligible, and what rollout and support are provided? |
| C-DAC eSushrut | A government-developed hospital-management system used in public health settings | What programme, deployment, support, and version is available to this facility? |
| Bahmni | An open-source hospital system combining clinical and operational components | Who will implement, host, secure, support, upgrade, and recover it? |

These routes can reduce proprietary licence cost. Only an answered operating model makes one usable.

## What the official pages establish

NIC calls e-Hospital a cloud-based, as-is SaaS product for government hospitals. Its current module list includes registration, admission-discharge-transfer, billing, clinic, laboratory, radiology, store and pharmacy, operation theatre, dietary, laundry, and queue management. That is meaningful scope. It is not a promise that any private facility can sign up, receive every module, or avoid local rollout work.

C-DAC's official health-informatics page describes eSushrut as a hospital-management system deployed across government health settings. A buyer should confirm the exact access path, current version, modules, implementation partner, hosting, and support for its institution. Public-sector use is not a private-hospital commercial contract.

Bahmni's official site describes an open-source system built from multiple components for hospitals and clinics. It can be hosted on site without dependence on the Internet. That feature is useful in a low-connectivity setting, but the hospital owns local infrastructure and continuity unless a partner contract says otherwise.

## Eligibility and ownership matrix

Fill this before a feature comparison.

| Decision | e-Hospital | eSushrut | Bahmni or other open source |
|---|---|---|---|
| Facility eligible |  |  | Licence permits intended use |
| Contract or programme owner |  |  |  |
| Implementation owner |  |  |  |
| Hosting and infrastructure owner |  |  |  |
| Security and patch owner |  |  |  |
| Interface owner |  |  |  |
| Migration owner |  |  |  |
| Training and go-live owner |  |  |  |
| Day and night support owner |  |  |  |
| Backup and restore owner |  |  |  |
| Upgrade and regression-test owner |  |  |  |
| Data-export and exit owner |  |  |  |

An empty cell is a deployment risk. It is not a saving.

## Price the work that the licence omits

Build two totals: year one and a normal operating year. Keep unknown costs blank until the programme, implementation partner, or hospital supplies a figure.

| Cost row | Quantity and unit | Year one | Later annual | Owner | Evidence |
|---|---|---:|---:|---|---|
| Discovery, workflow mapping, governance |  |  |  |  |  |
| Infrastructure, network, devices, power, hosting |  |  |  |  |  |
| Configuration, approved customisation, master data |  |  |  |  |  |
| Patient, clinical, billing, stock, document migration |  |  |  |  |  |
| Lab, PACS, payment, accounting, payer interfaces |  |  |  |  |  |
| Security testing, logging, incident handling |  |  |  |  |  |
| Backup, restore tests, redundancy, recovery |  |  |  |  |  |
| Training, super-users, floor support, downtime drills |  |  |  |  |  |
| Upgrades, regression tests, release support |  |  |  |  |  |
| Internal clinical, finance, quality, IT labour |  |  |  |  |  |
| Complete export, archive, termination, transition |  |  |  |  |  |
| GST and other applicable tax |  |  |  |  |  |

The [HMS cost breakdown](../hms-software-cost-breakdown-india/) has a more detailed workbook. Put zero in a row only when someone has accepted the work and its cost.

## Test a hospital journey, not a module menu

NABH's hospital digital toolkit separates readiness, RFP, vendor evaluation, migration, UAT, SLA, infrastructure, backup, and go-live. That structure is more useful than asking whether a product "has pharmacy."

Use one synthetic journey:

1. Register a patient and resolve a possible duplicate.
2. Move the patient from OPD to admission and then another bed.
3. Place a lab and imaging order; process a corrected result.
4. Prescribe, dispense, return, and trace a batch.
5. Add services, cancel one charge, and reconcile the bill.
6. Prepare discharge and the applicable payer or claim packet.
7. Correct a signed record without erasing the original.
8. Interrupt an interface or the network and show recovery.
9. Export the complete encounter and audit evidence.

The test should identify the owner at each handoff. If two systems participate, the interface and its failure queue are part of the product decision.

### Run a recovery drill

The normal demo proves the happy path. A hospital also needs evidence for the bad hour.

1. Stop the application or network during registration.
2. Record the local downtime workflow and temporary identifier rule.
3. Restore service and reconcile duplicate or delayed entries.
4. Restore a backup into an isolated environment.
5. Compare patient counts, recent encounters, stock, bills, and audit events.
6. Record the recovery time, data-loss window, decision owner, and unresolved differences.

Do not accept "backups are included" as the result. A restore log and reconciliation record are the evidence.

### Turn modules into contractual questions

| Module or handoff | Contract question |
|---|---|
| Registration and ADT | Who resolves duplicates, merges, transfers, and downtime identities? |
| Laboratory | Who owns analyzer interfaces, corrected results, acknowledgment, and queues? |
| Radiology and PACS | Who owns worklists, report addenda, image links, and failed messages? |
| Pharmacy and stores | Who validates formulary, batches, expiry, returns, and stock reconciliation? |
| Billing and payer | Who configures packages, refunds, deposits, claims, and financial reconciliation? |
| Backup and recovery | What recovery time and data-loss window are contractual? |
| Support | Which hours, channels, severity rules, and escalation contacts are contracted? |
| Exit | Which complete exports, formats, delivery times, and transition services are included? |

Each answer should name the programme, hospital team, implementation partner, or vendor. Shared responsibility without named handoffs is an empty cell in a different form.

## Open source is strongest with a real operating team

Bahmni can be a sound choice for a hospital that wants deployment control, can fund implementation, and has an accountable technical team or partner. It is risky when "community supported" substitutes for a named service owner.

The same principle applies to customisation. Every local change creates something the hospital must retest when upstream software or a connected system changes. Tie each change to a documented clinical or operational need.

## ABDM does not fill the missing HMS modules

ABDM's official FAQ says it does not recommend a particular HIS, HIMS, or HMIS. Its model is federated and consent based; providers retain their own records. ABDM can be an exchange requirement for a local hospital system. It is not the local registration, ward, lab, radiology, pharmacy, billing, or finance system.

Ask any programme or implementation partner to demonstrate the exact ABDM transaction needed, including consent, refusal, failure, and audit. Do not assume open-source code is production-integrated because a connector exists somewhere.

## Patient Square's hospital boundary

Patient Square is not a free HMS. Hospital Copilot is separately demo-priced. A hospital can deploy the complete Patient Square HIS/EHR or retain its existing HIS/EHR and define Hospital Copilot workflows during discovery. Neither path promises automatic filing or write-back into a named third-party system.

Registration, ADT, CPOE, eMAR, LIS, RIS, PACS, pharmacy, billing, interfaces, and other specialist workflows are requirements to scope and acceptance-test, not universal shipped claims. Book a demo once the hospital has written that validation plan.

---

## Choosing ABDM-Ready EMR Software for a Small Clinic
https://patientsquare.com/in/blog/abdm-ready-emr-software-india/
Published 2026-08-05 · Updated 2026-08-27 · Tags: abdm, emr-software, abha, clinic-software, india

What ABDM-ready EMR software actually means, the three NHA milestones behind the label, and the exact questions to ask a vendor before you sign.

It means the EMR can work with the Ayushman Bharat Digital Mission: create ABHA numbers, share records on patient consent, or fetch records from other providers. The catch is that it maps to three separate National Health Authority milestones, M1, M2, and M3. A vendor claiming ABDM-ready may have cleared only one of them, so always ask which.

ABDM-ready EMR software means the record system can plug into India's national digital-health rails: create an ABHA number, share records when the patient consents, or pull records from another provider. That's the promise. The problem is the label, because "ABDM-ready" hides three separate National Health Authority milestones, and a vendor can wave the ABDM logo while having cleared just one. This guide breaks the label into its parts and hands you the exact questions to ask before you sign.

> **Key takeaways**
>
> - ABDM-ready is not one capability. It maps to three NHA milestones: M1 (create ABHA), M2 (share records on consent), M3 (fetch records).
> - Certification is per-software, not per-clinic. The vendor clears the sandbox once; your facility still registers itself.
> - ABDM participation is voluntary. You need it only if you want ABHA-linked, shareable records.
> - The one question that matters: which milestones are cleared, and are they live in production or still in the sandbox?
> - AI Medical Scribe by Patient Square has ABDM on its roadmap, not shipped. We won't badge a status we don't hold.

_Source: National Health Authority / ABDM portal; DD News, May 2026._

## What "ABDM-ready" is supposed to mean

The Ayushman Bharat Digital Mission, run by the National Health Authority, is India's programme for an interoperable patient record. As of May 2026 it had crossed 100 crore ABHA-linked health records, per DD News reporting the NHA figures. The direction is set: ABHA is becoming the patient's portable health identity, and records are meant to move between providers on the patient's consent.

For a clinic, "ABDM-ready" software is what lets you take part. It should be able to create an ABHA for a walk-in, register your clinic on the official registries, and, when the patient agrees, share a discharge note or a lab report so the next doctor can see it. Done well, that's genuinely useful. A referral stops meaning a lost paper file.

But the label does a lot of quiet work, and most buyers never ask what's actually behind it.

## What are the three ABDM milestones?

Under the NHA's sandbox-to-production process, software certifies against milestones. Each does a different job, and clearing one does not mean clearing the others.

- **M1 (identity and registries).** The software can create and verify an ABHA number and register your clinic on the Health Facility Registry (HFR) and its clinicians on the Healthcare Professional Registry (HPR). This is the entry rung.
- **M2 (Health Information Provider).** The software can share a patient's records, formatted as FHIR, when the patient consents. This is the one that makes your records actually flow outward.
- **M3 (Health Information User).** The software can request and pull records from other providers into your view, again on consent. This is what lets you see the patient's history from elsewhere.

A tool that has cleared M1 can mint an ABHA but can't yet share records. On a pricing page, both read as "ABDM-ready." In your clinic, they're very different products. Our [ABDM Milestone 2 explainer](../abdm-milestone-2-explained-clinics/) walks through what M2 specifically demands, and the [ABHA linking workflow guide](../abha-linking-clinic-workflow/) shows how ABHA creation lands at the front desk.

## Is ABDM certification per-clinic or per-software?

Per-software. The vendor takes its product through the NHA sandbox, clears the milestone, and moves to production. That certification belongs to the product. Your clinic then registers itself on the HFR and, for clinicians, the HPR. So two things have to be true for records to move: the software is certified, and your specific facility is onboarded.

This matters for the buyer because a vendor can honestly say "our software is ABDM-certified" while your onboarding is still weeks of paperwork away. Ask the vendor to walk you through what onboarding *your* clinic involves, start to finish, and who does the work.

## Which questions should you ask a vendor?

Here's the checklist. Get the answers in writing, not on a sales call where they evaporate.

| Question | Why it separates real from marketing |
|---|---|
| Which milestones (M1, M2, M3) have you cleared? | A single "ABDM-ready" can mean just M1. The milestone names force specificity. |
| Are they live in production or still in the NHA sandbox? | Sandbox means it passed a test, not that a real patient's record has moved. |
| Do you appear in the ABDM integrator ecosystem? | A cross-check against the NHA side, not just the vendor's word. |
| What does onboarding my clinic on the HFR and HPR involve? | Separates product certification from your facility's actual readiness. |
| How is consent captured and logged for M2 and M3 flows? | Consent is the legal spine of ABDM sharing; a vague answer is a red flag. |
| Where does the data sit, and how does this square with the DPDP Act? | ABDM sharing and DPDP obligations run together; the vendor should have an answer. |

If a vendor can name the milestone, show production usage, and explain onboarding, that's a real capability. A bare ABDM logo with none of the above is a claim, not a feature.

## How does ABDM sit alongside the DPDP Act?

They pull in the same direction but from different angles. ABDM is about records moving *between* providers on consent. The Digital Personal Data Protection Act 2023 is about how any patient data is handled at all: consent-first, purpose-limited, with the clinic as a data fiduciary. When you turn on M2 sharing, you're both enabling ABDM flows and taking on DPDP obligations for the data you hold and share.

So the ABDM question and the DPDP question aren't separate purchases. The [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers the data-handling side; the milestone questions above cover the interoperability side. A good vendor answers both without flinching.

## When is a non-ABDM tool the better fit?

More often than the marketing suggests. ABDM is voluntary, and plenty of clinics don't need shareable records today. If your patients are local and repeat, your referrals go to two clinicians you already know, and your real pain is the hour of charting after the last patient, then ABDM certification solves a problem you don't have. A documentation tool would help you more than a milestone would.

Be honest about the fire you're fighting. If cross-provider records genuinely matter for your patients, an ABDM-ready EMR with M2 and M3 cleared is worth the diligence. If they don't, don't pay for a badge you'll never use. Our [EMR software guide for India](../emr-software-india-guide/) and the [best EMR roundup](../best-emr-software-india-roundup/) weigh both kinds of buyer.

## Where does AI Medical Scribe by Patient Square stand?

Plainly stated: **ABDM integration is on our roadmap and not shipped.** We don't claim ABDM-ready, ABDM-certified, or ABDM-compliant, because none of those are true yet, and we won't put a badge on a status we don't hold. This guide exists to make you a sharper buyer of ABDM-ready EMRs, not to sneak our name into that category.

What the scribe does is upstream of ABDM. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. It takes code-mixed Hinglish on input and returns the note in clean clinical English, the audio is processed in memory and discarded once the note drafts, and data is handled to DPDP Act 2023 standards. When ABDM support ships, we'll name the milestone we've cleared, same as we're telling you to demand from everyone else. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

So use this guide the way we'd use it ourselves. Make the vendor name the milestone, show it in production, and put it in writing. Then, if documentation is your other bottleneck, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to see a two-minute consult come back as a signed note, or read how we protect records on the [security page](../../security/).

---

## Best EMR for Pain Management Clinics (2026)
https://patientsquare.com/us/blog/best-emr-for-pain-management/
Published 2026-08-05 · Tags: comparison, pain-management, ehr, buying

ModMed, DrChrono, AdvancedMD, and Tebra compared for pain management on EPCS, PDMP, and procedure notes. Plus where an ambient AI scribe actually fits.

There's no single winner. ModMed is the specialty-built pick with EPCS, interfaced PDMP access, and MME calculators. DrChrono suits iPad-first prescribers who want native EPCS. AdvancedMD fits groups that lean on deep revenue-cycle tooling. Tebra is a lower-cost general option. The deciding factor is usually how heavily your practice prescribes controlled substances.

The best EMR for pain management depends on how much you prescribe controlled substances. ModMed is the specialty-built pick, with EPCS, interfaced PDMP access, and MME calculators inside the workflow. DrChrono fits iPad-first prescribers who want native EPCS. AdvancedMD suits groups built around revenue-cycle depth, and Tebra is a lower-cost general option. Below we compare them honestly on the things a pain clinic actually cares about. We also build [Practice Copilot](/us/products/practice-copilot/), an ambient scribe with a bundled EHR, and we'll be straight about where it fits and where it doesn't. If you just want our price without a call, it's on the [pricing page](/us/pricing/).

> **Key takeaways**
>
> - Controlled-substance prescribing drives the decision. If you write Schedule II opioids daily, EPCS plus interfaced PDMP is the feature that matters most, and it's what separates a pain-built EMR from a general one.
> - ModMed names EPCS, interfaced PDMP access, and MME calculators for pain management; quote-based pricing runs roughly $200 to $700-plus per provider per month, per 2026 reviews.
> - DrChrono was the first EHR certified for controlled-substance e-prescribing on iPad, iPhone, and web; it publishes no price, with outside estimates of $199 to $599.
> - Tebra is the cheaper entry at about $80 to $100-plus per provider, but controlled-substance e-prescribing carries a separate application fee, per EHR Source's 2026 review.
> - An ambient scribe drafts the procedure note fast. It does not e-prescribe or query a PDMP, so it sits alongside your prescribing EMR, not in place of it.

## The feature that decides a pain management EMR: controlled-substance prescribing

Start with what makes pain management different from a general clinic. You prescribe controlled substances, often Schedule II opioids, and you do it under real regulatory pressure. Two capabilities carry the whole evaluation.

The first is EPCS, electronic prescribing of controlled substances. Without it, controlled-substance prescriptions can't go out electronically, so you're stuck on paper for the exact drugs you write most. The second is PDMP access, the prescription drug monitoring program your state runs. Many states require a PDMP check before each controlled-substance prescription, and a system with interfaced PDMP access pulls that report without a separate portal login in the middle of a visit.

Everything else, templates, billing depth, scheduling, is a tiebreaker. If the EMR you're eyeing doesn't handle EPCS and PDMP cleanly, nothing else on the brochure saves it for a pain practice. Score that first.

## ModMed: the specialty-built option for pain management

ModMed is the closest thing to a purpose-built pain management EMR on this list. Its EMA platform is specialty-specific, and the pain management version names the features that matter here: EPCS embedded in the prescribing workflow, interfaced PDMP access, and built-in MME calculators for tracking morphine milligram equivalents across a patient's regimen. Its documentation tool, ModMed Scribe, was trained on de-identified data sampled from over 750 million patient encounters, so it's tuned to how pain physicians actually chart.

The trade-off is price and commitment. ModMed uses quote-based pricing with no published rate, and 2026 third-party reviews estimate roughly $200 to $700-plus per provider per month, with implementation adding several thousand dollars. That's real money, and you don't learn your number until you're on a sales call. For a practice that lives inside pain management and wants the MME and PDMP tooling native, that depth tends to earn its cost.

**Pick ModMed if:** pain management is your whole practice, you prescribe controlled substances heavily, and you want EPCS, PDMP, and MME handling built for exactly this specialty.

## DrChrono: native EPCS for iPad-first prescribers

DrChrono took a different route and won a first with it. It was the first EHR certified for electronic prescribing of controlled substances on iPad, iPhone, and web, and it runs a dedicated pain management workflow. If your providers chart from an iPad in the exam room and want to send a controlled-substance script from the same device, that native experience is genuinely differentiated.

DrChrono publishes no per-provider price. Third-party estimates put entry plans around $199 to $299 per provider per month, with billing-inclusive tiers reaching $499 to $599, all quote-driven. There's also an ambient documentation tool, EverHealth Scribe, that launched in March 2026, though it's included only in the Premium plan and sold as an add-on below that. For an iPad-first pain practice that wants EPCS in a native app, DrChrono is a strong fit; for a desktop-first one, the iPad advantage matters less.

**Pick DrChrono if:** your providers are iPad-first, native EPCS on a tablet is a hard requirement, and you're comfortable getting your price by demo.

## AdvancedMD and Tebra: the revenue-cycle and budget routes

These two solve different problems than the specialty-built pair.

AdvancedMD prices by module, which suits a group that wants deep revenue-cycle tooling and will assemble the pieces it needs. Third-party trackers put a single module near $229 per provider per month, the EHR-plus-practice-management bundle around $429, and full suites at $729 to $999, with managed billing running 3 to 7 percent of collections on top. For a pain group where billing complexity and denials are the real headache, that depth can pay off. For a small clinic, the module stack can mean paying for capacity you barely touch.

Tebra, the platform formed when Kareo merged with PatientPop, is the budget entry. Per EHR Source's 2026 review, the EHR plus practice management runs about $80 to $100-plus per provider per month, well below the specialty options. The catch for a pain practice: controlled-substance e-prescribing carries a separate one-time application fee, per that same review, so the "cheap EMR" line isn't the whole controlled-substance cost. It's ONC-certified and fine as a general record system; it just wasn't built around pain management the way ModMed was.

**Pick AdvancedMD if** revenue-cycle depth is central. **Pick Tebra if** controlled-substance volume is lighter and base cost is your main constraint, and you've priced the EPCS fee in.

## Where an ambient scribe with a bundled EHR fits, and where it doesn't

Here's the honest part, and we'll draw the line clearly because it matters for a pain practice.

Every EMR above stores your chart and, in the pain-built cases, prescribes your controlled substances. What none of them does especially well is write the note for you. That's the gap we work on. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On the Copilot plan, that scribe comes with a bundled EHR at $119 per clinician per month on the annual plan, published on the page, no quote to chase.

Now the limit, stated plainly. Our prescription output is a draft you review, not e-prescribing that transmits to a pharmacy, and we do not query a PDMP. For a pain practice that writes Schedule II scripts daily, that's not optional tooling. So we're not the system that handles your controlled-substance prescribing. What the scribe does is take the documentation load off a procedure-heavy day: it drafts the injection or nerve-block note and the visit note as you describe them, and suggests [ICD-10 codes](../ai-scribe-icd-10-suggestions-explained/) for you to confirm. The prescribing and PDMP piece stays in a purpose-built EMR next to it.

That's the honest verdict. When a pain-specific EMR with EPCS and PDMP is the better fit, which for most controlled-substance-heavy practices it is, get that from ModMed or DrChrono. Where a scribe earns its place is the note, and we think that's the part most pain clinics underestimate until they're editing procedure documentation at 7pm. If you want to see it on your own visit types, book a short demo; if you just want the price, it's [already public](/us/pricing/).

## How to choose in one pass

Answer three questions in order and the shortlist writes itself.

How heavily do you prescribe controlled substances? Daily Schedule II volume makes EPCS and interfaced PDMP non-negotiable, which points at ModMed or DrChrono. How do your providers chart, desk or tablet? iPad-first leans DrChrono; desktop-first opens the field. And how late are your providers finishing procedure notes? If that's the pain, a scribe alongside the EMR is where the time comes back.

One thing to do before you sign anything: make each vendor show you a real controlled-substance prescription end to end, EPCS signing and the PDMP check included, on a timed visit, not a canned demo. The number that decides your day isn't the base rate. It's how many clicks and seconds a controlled-substance script actually takes when the schedule is full. For a broader view across specialties, our [small-practice EMR roundup](../best-emr-for-small-practice/) and the [urgent care comparison](../best-emr-for-urgent-care/) run the same honest scoring on different clinic shapes.

## Frequently asked questions

The FAQ above covers the recurring ones: which EMR wins for which pain practice, real cost ranges, why EPCS and PDMP decide it, and exactly what an ambient scribe does and doesn't do. If you're weighing note-drafting specifically, the [pricing page](/us/pricing/) has the full Practice Copilot breakdown, and a demo shows the scribe on your own procedure notes.

---

## Best Teleconsultation Software for Doctors in India (2026)
https://patientsquare.com/in/blog/best-teleconsultation-software-doctors-india/
Published 2026-08-05 · Updated 2026-10-04 · Tags: best, teleconsultation, roundup, comparison, telemedicine

A practical roundup of teleconsultation platforms for Indian doctors in 2026, scored on video quality, prescriptions, telemedicine rules, notes, and rupee pricing.

If you want patients from a large marketplace, an aggregator like Practo or Apollo 24|7 brings demand plus a video tool. If you want video tied to your own clinical record, an EMR with teleconsult (HealthPlix) keeps the call and the note together. If your pain is documenting the tele-visit itself, Patient Square's ambient AI drafts the note, ICD-10 codes, and a prescription during the call. Pick by whether you need patients, integration, or documentation relief.

Fast verdict: the best teleconsultation software for Indian doctors depends on whether you need patients, integration, or documentation relief. Aggregators like Practo and Apollo 24|7 bring demand and a built-in video tool. An EMR with teleconsult (HealthPlix) keeps the call tied to your record. But if the hard part is writing the note during a tele-visit, our pick is **Patient Square**, because its ambient AI drafts the note, ICD-10 suggestions, and a prescription while you talk to the patient, on top of whichever video tool you use. The Copilot tier with the AI EHR is ₹2,399 a month per clinician on annual billing, ex-GST. [See the India pricing](/in/pricing/).

Here's the honest read, scored on what an Indian doctor actually needs from a tele-visit, from video to a compliant prescription to the note.

| | Practo / Apollo 24\|7 (marketplace) | HealthPlix (EMR + teleconsult) | Video-only tool | Patient Square (AI Copilot + EHR) |
|---|---|---|---|---|
| **Best for** | Patient demand + video | Video tied to your record | A simple video call | Documenting the tele-visit |
| **Brings you patients** | Yes | No | No | No |
| **Tied to clinical note** | Platform record | Yes, EMR | No | Yes, AI EHR |
| **Prescription output** | Platform Rx | EMR Rx | None | AI-drafted Rx to review + sign |
| **Note drafted for you** | No | EMR notes | No | Yes, ambient AI note + ICD-10 |
| **Published price** | Request platform-specific fee schedule | ₹11,999–17,999/yr per doctor | Check current plan and limits | ₹2,399/mo per clinician (Copilot, annual) ex-GST |
| **Indian-language input** | Varies | EMR UI | Video only | Hindi + Indian languages on input |

_Figures from vendor pages or market ranges as of 2026, hedged where sales-gated or commission-based. Confirm before buying._

## What "teleconsultation software" actually covers

The label runs across three different products, and Indian doctors usually want just one. Pin yours down first.

The first is the **marketplace with video**: an aggregator that lists you, sends patients, and handles the call and payment. Practo and Apollo 24|7 sit here. It brings demand, but it takes a cut and puts you inside its brand. If you need patient volume, this is the layer.

The second is **teleconsult tied to your record**: video wired to your own EMR, so the call, the note, the history, and the prescription live in one place. HealthPlix does this. You keep the patient relationship and the record.

The third is **documentation during the call**: the note, the codes, and the Rx you have to produce while looking at a patient on a screen. This is the part that's often worse on tele-visits than in person, because you're typing and talking at once. Software that drafts the note as you go attacks this, and it rides on top of whatever video you use.

Buy a marketplace to fix a documentation problem, or a video tool to fix a demand problem, and you've solved the wrong thing.

## What the telemedicine rules require

Before comparing tools, know the frame you're practising in. India's **Telemedicine Practice Guidelines**, issued in 2020 by the Board of Governors in supersession of the Medical Council of India, set out how a registered medical practitioner may consult and prescribe remotely. They cover patient consent, the doctor's judgement on when a tele-visit is appropriate, and restrictions on prescribing certain drug categories remotely.

The practical point for a buyer: whatever software you pick should let you practise inside those guidelines, produce a clear and retrievable prescription, and keep proper records. Ask any vendor how its tool supports compliant prescribing and record-keeping, and don't assume a slick video call covers the paperwork the rules expect.

## How we scored the options

Five things decide whether teleconsult software earns its fee for a real Indian doctor.

- **What it's for: demand, integration, or documentation.** Settle this first. A marketplace won't lighten your notes, and an AI note tool won't send you patients.
- **Video that holds up on Indian bandwidth.** A call that drops mid-consult wastes everyone's time. Test it on the connections your patients actually use.
- **Compliant, clear prescriptions.** Can it produce a retrievable Rx within the Telemedicine Practice Guidelines? This is not optional.
- **Documentation during the call.** Does anything draft the note and codes while you consult, or do you type after? On tele-visits, this is where the time goes.
- **Honest economics.** Ask for a written fee schedule, including any per-consult charge, subscription, taxes, and renewal terms, so you can calculate the real per-visit cost.

## How the main options compare

**Practo and Apollo 24|7** are marketplaces with video built in. They list doctors and offer patient-facing booking or consultation flows. Confirm the actual referral model, platform fees, ownership of patient relationships, and video capabilities in the current provider contract before choosing one for patient acquisition.

**HealthPlix** is a specialty OPD EMR with teleconsult, so the video call sits next to your note, history, and prescription. It publishes real prices, ₹11,999 a year for Pro and ₹17,999 for Elite per doctor. For a doctor who wants tele-visits inside their own record, this keeps everything together.

**Video-only tools** give you a cheap or free call but no clinical record and no Rx handling. Fine as a stopgap, weak as a system.

**Patient Square** targets the documentation during the visit, on top of any video. More on the fit below.

_Sources: Telemedicine Practice Guidelines 2020; vendor pages, 2026._

If your real problem is documenting the tele-visit, not finding patients, skip ahead and [see the India pricing](/in/pricing/). Otherwise, keep reading.

## Where a marketplace or EMR teleconsult wins

Plenty of the time. If your gap is demand or record integration, one of those is the right buy, and an AI note layer alone won't fill it. Pick a marketplace or EMR teleconsult when you:

- Need patient volume that a large platform's audience can supply.
- Want the video call wired into your own EMR and billing.
- Are building a tele-practice from scratch and need the whole stack in one place.
- Aren't yet feeling the note-writing burden that tele-visits pile on.

If that's you, choose on demand and integration, and add a documentation layer later if the notes start to hurt.

## Where Patient Square fits

At the note, during the call, and that's why it's our pick when documentation is the burden. Patient Square doesn't send you patients and isn't your video tool. It makes each tele-visit produce a clean record without you typing through the consult.

The product is a Copilot: the ambient AI listens during the tele-visit and drafts a structured note, ICD-10 suggestions, and a prescription for you to review and sign, within the Telemedicine Practice Guidelines' expectation of a clear, retrievable record. It rides on top of whichever video call you're using, marketplace or your own. For Indian tele-OPDs, it takes Hindi and Indian-language input and returns a clean clinical note, so the call in Hinglish still ends in a proper English record.

On price, the numbers are published, per clinician. Assist is ₹1,999 a month, ₹1,599 on annual, with no EHR. Copilot with the bundled AI EHR is ₹2,999, or ₹2,399 annual. Autopilot is ₹4,999, or ₹3,999 annual. Add 18% GST to any of them. The point for a tele-practice: it's a flat, computable cost per doctor, not a slice of every consult the way a marketplace bills.

Honest read: if you need demand or a full tele-stack, buy a marketplace or an EMR teleconsult first. But if you've got the video sorted and the note is what's killing your tele-visits, fixing the documentation is the move that pays off fastest. [See the India pricing](/in/pricing/) or [start from the India home page](/in/), and run a real tele-clinic session to see where your notes land.

---

## Patient Management System for Indian Clinics: 2026 Guide
https://patientsquare.com/in/blog/patient-management-system-india/
Published 2026-08-05 · Updated 2026-08-27 · Tags: patient-management-system, clinic-software, abdm, dpdp, india

What a patient management system covers, how to shortlist one for an Indian clinic in 2026, and where a scribe fits versus a full EMR. Honest and priced.

It's the software a clinic uses to run patient-facing operations: registration, appointments, the clinical record, prescriptions, billing, and follow-ups. In India the term overlaps with EMR, HMS, and practice management, so buyers often mean slightly different things. Decide whether your real gap is the record, the front desk, or the note before you shortlist.

A patient management system is whatever software runs the patient side of your clinic: registration, appointments, the record, prescriptions, billing, and the follow-up nudge. That's the honest one-line answer. The hard part isn't the definition. It's that "patient management system," "EMR," "HMS," and "practice management" get used interchangeably in India, and a clinic that buys the wrong shape ends up paying monthly for features it never opens. This guide sorts the categories, prices them, and says plainly where each one wins.

> **Key takeaways**
>
> - "Patient management system" is a category, not a product. Decide first whether your gap is the record, the front desk, or the clinical note.
> - India-native tools sit around ₹1,000 to ₹1,500 per doctor a month plus 18% GST; hospital suites are usually demo-priced.
> - ABDM-ready hides three National Health Authority milestones (M1, M2, M3). Make the vendor name the one it has cleared.
> - Under the DPDP Act 2023, every purchase is a data-fiduciary call: ask where data sits, how long it's kept, and whether audio is stored.
> - If your only real problem is charting time, a scribe on top of your existing system beats ripping the system out.

_Sources: Irving et al., BMJ Open 2017; National Health Authority / DD News, May 2026; vendor pages, July 2026._

## What does a patient management system actually cover?

Strip the marketing off and there are three jobs hiding under one label.

The first is the **front desk**: registration, appointment booking, queue and token flow, reminders. Fix this and your waiting room stops feeling like a bus stand.

The second is the **clinical record**: the patient's history, past visits, the note from today, the prescription, lab results. This is the EMR layer, the system of record. It's the part a medico-legal complaint will one day be read against.

The third is the **documentation act itself**: turning the conversation in the room into a written note. For a two-minute Indian OPD consult, which is roughly the primary-care average per the 67-country BMJ Open review, that note is where the time goes and where the record quality quietly slips as the day gets longer.

Most vendors sell you a bundle across all three and call it a patient management system. That's fine when you need all three. It's overbuying when your only real problem lives in one of them.

## How should you shortlist one for an Indian clinic?

Feature lists forty rows deep are noise. Six questions decide whether a tool earns its fee.

1. **Which job is broken, front desk, record, or note?** Answer this before anything else. Buying a full suite to fix charting is like buying a car because your phone needs charging.
2. **Is the price on the page, in rupees, ex-GST with the 18% shown?** A published number is a trust signal. Sales-gated pricing usually flexes with how hard you push back.
3. **Which ABDM milestone has it cleared, live in production?** Only relevant if you want ABHA linking now. More on the three milestones below.
4. **Does it shorten the note or just store it?** A form-heavy EMR can add documentation work. An ambient scribe removes it. Big difference for an evening you'd rather spend at home.
5. **How does it behave under DPDP?** Where does the data live, how long is it retained, and for anything that listens, is the audio kept? We think this one is underweighted today and about to get heavier.
6. **Can you trial it on a real clinic day?** A demo shows the happy path. A trial shows what happens on a 40-patient Tuesday with three walk-ins and a flaky internet line.

## How do the main categories compare?

Here's the shape of the market, scored by which clinic problem each category is built for. Read the "Best for" row first.

| | Full clinic suite / HMS | Specialty EMR | Ambient scribe (documentation layer) |
|---|---|---|---|
| **Best for** | Billing, pharmacy, IPD, multi-site under one roof | A clinic that wants records plus ABDM in one place | A clinic whose real pain is charting time |
| **Example** | Hospital-grade suites (demo-priced) | HealthPlix (₹11,999–17,999/yr) | AI Medical Scribe by Patient Square |
| **Front desk** | Yes, deep | Yes | No (sits on top of yours) |
| **Clinical record** | Yes | Yes | Drafts the note; you keep the record |
| **ABDM** | Often listed; verify the milestone | Listed as a feature | On the roadmap (not shipped) |
| **Cuts the note** | Not really | Somewhat | Yes, that's the whole point |
| **Price signal** | Usually sales-gated | First-party published | First-party published |

Figures come from each vendor's own pages in July 2026; confirm before buying. HealthPlix's ₹11,999 (Pro) and ₹17,999 (Elite) per year compute to roughly ₹1,000 and ₹1,500 a month, per the [HealthPlix pricing page](https://blogs.healthplix.com/pricing/). For a deeper product-by-product read, our [clinic management software scorecard](../best-clinic-management-software-india/) ranks the named tools.

## What does "ABDM-ready" really mean here?

This is the row that trips buyers up most, so slow down. ABDM, the Ayushman Bharat Digital Mission run by the National Health Authority, crossed 100 crore ABHA-linked health records in May 2026, per DD News reporting on the NHA figures. It's real and it's large. But "ABDM-ready" on a pricing page can mean almost anything.

Under the NHA's sandbox-to-production process, software certifies against milestones, and each does a different job:

- **M1** lets the software create and verify an ABHA number and register on the facility and professional registries (HFR and HPR).
- **M2** lets it share a patient's records, as FHIR, when the patient consents.
- **M3** lets it pull records from other providers into your view.

Certification is per-software, not per-clinic, so the vendor clears the sandbox once and each facility then registers. The buyer's whole job is one question: *which milestones have you cleared, and are they live in production or still in sandbox?* A tool that can mint an ABHA (M1) but can't yet share records (M2) is "ABDM-ready" in marketing and half-built in practice. Our [ABDM Milestone 2 explainer](../abdm-milestone-2-explained-clinics/) and the [ABHA linking workflow guide](../abha-linking-clinic-workflow/) go deeper if this is your priority.

Straight talk on our own position: **AI Medical Scribe by Patient Square has ABDM integration on its roadmap, not shipped.** We won't badge a scribe with a certification it doesn't hold, and neither should any vendor you're evaluating.

## When is a full suite the better fit?

Often, honestly. If your evenings aren't lost to charting but to chasing payments, stock, and appointments, a scribe won't touch your actual problem and a full suite will. Reach for a full clinic suite or HMS when you:

- Bill in-house and want GST invoicing in the same system as the note.
- Run a pharmacy or hold inventory and want dispensing tied to the prescription.
- Manage inpatients, labs, or several satellite clinics under one roof.
- Want ABDM linking today and your vendor has actually cleared the milestones.

If two or more of those are true, start your shortlist with a full suite, not a documentation tool. For hospital-scale buyers, the [hospital management system explainer](../hospital-management-system-explained/) covers the IPD and multi-department side.

## Where does a scribe fit in the stack?

In the documentation slot, and only there. AI Medical Scribe by Patient Square doesn't pretend to be your clinic's system of record. It's the layer that fixes the note and sits on top of whatever you already run.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

For an Indian OPD the design choices are specific. Consults arrive in braided Hindi and English, so the scribe takes code-mixed Hinglish on input and returns the note in clean clinical English. The prescription is a draft the doctor reviews and signs, not a transmission to a pharmacy. Visit audio is processed in memory and discarded once the note drafts, so there's no recording sitting on a server, which is the cleaner answer under the [DPDP Act](../dpdp-act-clinics-guide/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On price, every number is on the page. In India, plans start at ₹1,599 per clinician a month on annual billing, ex-GST; the bundled AI EHR starts one tier up at ₹2,399 a month annual. Add 18% GST and the entry invoice is about ₹1,887. Unlimited visits and notes, no per-note metering, no setup fees, and a 7-day trial you can run on a real clinic day. That sits inside the same ₹1,000 to ₹1,500-ish band as the rest of the Indian clinic-software wallet.

The deciding move is the one we'd give a friend: don't buy on a guide, including this one. Name the job that's broken, shortlist two tools for it, and run them on your own Tuesday OPD. Book a short demo to watch where a two-minute consult lands as a note, or read how we protect records on the [security page](../../security/).

---

## Best Doctor Appointment Software in India (2026): Honest Picks
https://patientsquare.com/in/blog/best-doctor-appointment-software-india/
Published 2026-08-04 · Updated 2026-09-29 · Tags: best, appointment-software, roundup, comparison, scheduling

A practical roundup of doctor appointment and booking software for Indian practices in 2026, with buyer tests for discovery, scheduling, record-system paths, and pricing.

If you want patients to find and book you online, assess Practo's public discovery and booking surfaces separately from its Ray clinic-management product. If you want an EMR with scheduling, HealthPlix is a candidate to assess. Patient Square lists Scheduling from the Assist tier and a bundled AI EHR from Copilot, but it is not a discovery marketplace. Pick by the bottleneck you can verify in a trial or demo.

Quick verdict: the best doctor appointment software in India depends on whether you need patient discovery, an EMR with scheduling, or a practice platform whose scheduling and record-system paths you can test. Assess Practo's public discovery and booking surfaces separately from Ray clinic management. HealthPlix is a named EMR-and-scheduling candidate. Patient Square lists Scheduling from Assist, and the bundled AI EHR starts at Copilot. It is not a public discovery marketplace. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> to test the practice fit with your own staff.

Below is a buyer-test framework for the appointment workflow your practice actually needs.

| | Practo discovery / Ray clinic management | HealthPlix (EMR + scheduling) | Generic booking app | Patient Square (Practice Copilot) |
|---|---|---|---|---|
| **Buyer question** | Which Practo surface is being quoted and what patient-discovery workflow is included? | Does the quoted EMR plan fit the practice? | Does the quoted calendar fit the practice? | Does Scheduling from Assist fit the practice? |
| **Record-system path** | Confirm with Practo | EMR | Confirm with vendor | Bundled AI EHR from Copilot, or use alongside an existing EHR |
| **Published price** | Request current quote | ₹11,999-17,999/yr per doctor | Request current quote | ₹2,399/mo per clinician ex-GST (Copilot monthly equivalent on annual billing) |
| **Documentation scope** | Confirm with vendor | Confirm with vendor | Confirm with vendor | AI Medical Scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review |

_Use the exact product, plan, and written terms being quoted. Do not compare unrelated product surfaces or third-party price estimates._

## What "appointment software" actually covers

The label spans three different products, and buyers usually want just one of them. Name yours first.

The first is **discovery plus booking**: a public profile where patients find you and book a slot. If your practice depends on new patients finding you online, evaluate the relevant public discovery and booking surface, rather than treating a clinic-management product as the same thing.

The second is the **calendar tied to your record**: test the appointment workflow, the record path, and staff handoffs in the exact quoted EMR plan. HealthPlix is one candidate to assess. You're not chasing discovery; you're testing clinic operations.

The third is the **practice-platform decision**: whether scheduling should sit beside an existing EHR or a bundled AI EHR, and whether an ambient documentation tool earns its place during the visit. A product listing is not proof of every front-desk workflow. Ask staff to run the appointment flow they need.

Buy a booking calendar to fix a discovery problem, or a marketplace to fix a documentation problem, and you've solved the wrong thing.

## How we scored the options

Five things decide whether appointment software earns its fee at a real Indian practice.

- **What it's for: discovery, calendar, or the whole visit.** Decide this first. A public listing won't lighten your doctor's notes, and an EMR calendar won't bring new patients from search.
- **Reminder workflow.** Ask the vendor to demonstrate the exact channel, configuration, charge, and reporting path.
- **Staff handoffs.** Have staff run the phone, booking, check-in, reschedule, and record-placement workflow they use.
- **Record path.** Check where the appointment information appears and what staff must re-enter.
- **Written commercial terms.** Record the unit, term, included scope, implementation, taxes, renewal, and exit costs.

## How the main options compare

**Practo** has public discovery and booking surfaces as well as Ray clinic-management software. Confirm which product is being quoted and demonstrated. Practo's public price is sales-gated in this comparison, so request a written quote rather than relying on a third-party estimate.

**HealthPlix** publishes ₹11,999 a year for Pro and ₹17,999 for Elite per doctor. Confirm the appointment workflow and included scope in the quoted plan.

**Generic booking apps** need the same buyer test: confirm the exact calendar, staff, record, messaging, and price workflow before purchase.

**Patient Square** lists Scheduling from Assist and adds a bundled AI EHR at Copilot. More on the fit below.

_Sources: NHA / ABDM portal; vendor pages, 2026._

If you are comparing a practice platform rather than a listing site, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> and run the scheduling path with your own staff. Otherwise, keep reading.

## Where a booking-first tool wins

Often, and we'll say so. If you mainly need to be found and to fill slots, a marketplace or a calendar is the right buy, and an AI platform is overkill for that alone. Pick a booking-first tool when you:

- Depend on online discovery to bring new patients through the door.
- Need a demonstrated calendar workflow.
- Run a solo or small practice with a light clinical record.
- Have a written quote whose scope matches the gap.

If that's you, buy the calendar, keep it simple, and don't overspend on a platform you won't use.

## Where Patient Square fits

Patient Square fits a practice that wants to evaluate scheduling alongside documentation and a record-system choice. It is not a marketplace and will not bring patients from search.

Practice Copilot lists Scheduling from Assist. Its AI Medical Scribe can produce a structured SOAP note, ICD-10 suggestions, and a prescription draft for the clinician to review and sign. Practice Copilot can use Patient Square EHR from Copilot, or work alongside an existing EHR. For Indian OPDs, the scribe accepts English, Hindi, and 20+ Indian languages, including code-mixed input, and returns a clean clinical-English note.

Every price is on the page, per clinician. Assist is ₹1,999 monthly or ₹1,599 monthly equivalent on annual billing. Copilot is ₹2,999 monthly or ₹2,399 monthly equivalent on annual billing and includes the bundled AI EHR. Autopilot is ₹4,999 monthly or ₹3,999 monthly equivalent on annual billing. Prices are ex-GST; add 18% GST.

Honest read: if you only need a calendar or a listing, buy one of those. If you need Scheduling from Assist, Patient Square EHR from Copilot or an alongside path for an existing EHR, and an ambient scribe to test during real visits, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>. Use the first week to check the staff handoffs you actually rely on.

---

## Best EHR for Cardiology Practices (2026)
https://patientsquare.com/us/blog/best-ehr-for-cardiology/
Published 2026-08-04 · Updated 2026-08-27 · Tags: best, cardiology, ehr-comparison, scribe

The best EHR for cardiology in 2026: Epic Cupid, athenahealth, AdvancedMD, NextGen, and a bundled AI EHR from $119/mo. Six options, one honest verdict.

It depends on whether your bottleneck is device and imaging data or documentation time. If you need cath, echo, and pacemaker data flowing into structured reports, a cardiology-aware platform like Epic Cupid or a dedicated cardiology EHR fits best. If your real pain is finishing notes after a full clinic day, Patient Square's Copilot tier bundles an AI EHR and ambient scribe at $119 per clinician per month on annual billing. Try both categories before you commit.

If your cardiology practice needs cath, echo, and pacemaker data flowing into structured reports, the honest answer is a cardiology-aware EHR like Epic Cupid or a dedicated cardiology platform. Those handle the device and imaging side that general-purpose EHRs struggle with. But if your real pain is finishing notes after a full clinic day, a bundled AI EHR and ambient scribe is worth a look. Patient Square's Copilot tier does that at $119 per clinician per month on the annual plan. [See the pricing](/us/pricing/) or book a demo.

> **Key takeaways**
>
> - A 2020 ACC survey (mini-Z) put cardiologist burnout at 35.4%, with insufficient documentation time and EHR use at home among the named drivers.
> - Cardiology has device- and imaging-heavy needs: pacemaker and ICD interrogation, echo and EKG data, structured cardiovascular reporting. Epic Cupid and dedicated platforms cover this; most general EHRs need heavy customization.
> - Cardiology EHR pricing runs roughly $140 to $729 per provider per month per 2026 third-party reviews, and most vendors quote-only.
> - Patient Square bundles an ambient scribe and AI Copilot EHR from $119/mo annual. It does not claim device or imaging integration. The price is on a public page.
> - If your day is 22 visits plus echo and nuclear reads to sign, documentation speed is not a small line item.

## Cardiology EHR buyers are choosing between two different problems

Most comparison posts flatten this into one question. It's really two.

The first problem is clinical data depth for cardiology specifically. Pacemaker and ICD interrogation data. Holter and event-monitor results. Echo and EKG readings that live in a structured report, not just free text. Cardiovascular risk calculators tied to the visit. Imaging viewers inside the chart. A cardiology practice runs on device output, and an EHR that can't ingest and structure that output makes you a manual transcriptionist for your own equipment. If this is your bottleneck, you need a platform built for cardiovascular workflows.

The second problem is visit volume and documentation time. A general cardiology day can be 20-plus office visits, plus echo, nuclear, and stress reads waiting to be signed. Heart-failure follow-ups, AFib rate-versus-rhythm checks, post-cath visits, device clinics. The clinical tools might be excellent, but if there's no ambient capture, the note-writing follows you home. That second problem is where documentation-first tools compete, and it's a different axis entirely.

Know which one is actually costing you. We think most independent cardiologists have more of a problem with the second than they admit, because the first is the one vendors sell hardest.

## The comparison table

| EHR | Device data (pacer/ICD/Holter) | Echo & EKG structured reporting | Built-in ambient scribe | EHR included | Pricing |
|---|---|---|---|---|---|
| Epic (Cupid) | Yes | Yes | Optional add-on | Yes | Quote only |
| athenahealth | Varies / customization | Partial | No | Yes | Quote / collections-based |
| AdvancedMD | Varies | Templates | No | Yes | Quote (up to ~$729/prov/mo) |
| NextGen | Cardiology templates | Templates | No | Yes | Quote only |
| eClinicalWorks | Device integration | Templates | No native | Yes | ~$449/prov/mo (EHR-only) |
| **Patient Square** | **No** | **No (captures your dictation)** | **Yes, native** | **Yes (Copilot+)** | **$119/mo annual** |

No asterisks on the Patient Square row. Those "No" entries in the device and imaging columns are real. If automatic device and echo data flow is non-negotiable for you, this table just did its job and pointed you up the list.

## What each cardiology EHR option actually does

### Epic (Cupid)

Cupid is Epic's cardiovascular module, and it's the deep end of the pool. Per Healthcare IT Leaders, it covers cath, echo, EP, stress testing, and vascular ultrasound, with order entry, scheduling, procedure documentation, and structured reporting. A cardiology program on Cupid maps interfaces between the module, its cardiology PACS, its hemodynamic monitoring, and its ECG systems so the structured report actually carries the images, measurements, and signals. That's powerful, and it's built for hospitals and large cardiovascular programs with an implementation team. Pricing is quote-based. For a solo or two-provider clinic, Cupid is usually more system than the practice needs or wants to pay for.

### athenahealth

athenaOne leans on revenue cycle and real-time eligibility, which cardiology practices with heavy claim volume value. The cardiology fit comes through template customization rather than out-of-the-box cardiovascular depth, per 2026 reviews. Pricing is often collections-based rather than a flat per-provider figure, so your effective cost scales with what you bill. If your practice already runs on athena and you want billing and EHR tightly tied, it's workable. If you want cardiology-specific structure on day one, expect setup work.

### AdvancedMD

AdvancedMD is a multi-specialty cloud platform with EHR, practice management, billing, patient engagement, and telehealth. Cardiology is served through templates, not a dedicated cardiovascular product. Third-party 2026 pricing puts EHR-only near $229 per provider per month, with the full suite reaching $629 to $729. It's a broad platform. Whether the cardiology tooling runs deep enough depends on how device- and imaging-heavy your workflow is.

### NextGen

NextGen Healthcare offers pre-configured cardiology templates inside a general ambulatory EHR, plus telehealth and MIPS reporting. It's a reasonable pick for a mid-size cardiology group that wants a full ambulatory platform and can invest in configuration. Pricing is quote-only. Like most on this list, it stores and structures your chart but doesn't write the note for you.

### eClinicalWorks

eCW ships arrhythmia, heart-failure, and hypertension templates, device integration, and a voice assistant, and it publishes an EHR-only figure around $449 per provider per month, per 2026 reviews. It's common in higher-volume and community settings. There's no native ambient scribe, so practices that want one usually layer on a third-party tool, which is another subscription and another integration to manage.

### A note on ModMed

If you searched for ModMed here, worth knowing: ModMed's specialty-specific EHR does not currently support cardiology. It covers dermatology, ophthalmology, orthopedics, gastroenterology, and several others, but cardiology is not on the list. So it's off this table, not because it's a weak product, but because it doesn't serve the specialty.

## A Thursday in a two-provider cardiology clinic

It's 8am. Twenty-two patients on the schedule. Two new-patient consults, a stack of heart-failure follow-ups, three AFib rechecks, a couple of post-cath visits, an afternoon device clinic. On top of the office visits, there are six echo reads and four nuclear studies to sign before end of day.

By 6pm, the clinical work is done. The documentation isn't. If every follow-up note is still open, that's two more hours before anyone leaves. The device and imaging data mostly flowed where it needed to, assuming the interfaces were built right. The narrative note, the interval history, the assessment and plan, that's still a typing job.

This is the part an ambient scribe changes. It listens during the visit, structures the SOAP note, surfaces ICD-10 suggestions and a prescription draft, and has it ready in about two minutes. You say "EF 40 percent, moderate MR, dry weight down two pounds, NYHA class two," and the note reflects exactly that. You read it, confirm the findings match what you dictated, and sign. Next room.

AI Medical Scribe by Patient Square is one module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Move up to the Copilot plan and it comes bundled with an AI EHR, so the note lands in a chart you own.

For the documentation workflow specifically, the [AI scribe for cardiology](../ai-scribe-for-cardiology/) post goes deeper on echo reads, longitudinal heart-failure notes, and procedure documentation. The [best EHR with AI scribe built in](../best-ehr-with-ai-scribe-built-in/) roundup covers the bundled-EHR angle across specialties.

## Our honest take on Patient Square for cardiology

We build this, so we'll be straight about the limits. Patient Square's Copilot tier bundles an ambient AI scribe and an AI Copilot EHR in one subscription at $119 per clinician per month on annual billing. Specialty-aware templates ship ready out of the box, so the cardiac visit types are there without a build project. A BAA is available for every customer, and audio is processed in memory and discarded once the note drafts.

What we don't do, and won't pretend to: we don't integrate with echo systems, EKG carts, or pacemaker programmers. We don't read images or pull hemodynamic data. The scribe captures the reading you dictate; it doesn't measure anything. If automatic device and imaging data flow into structured cardiovascular reports is core to your practice, a cardiology-specific EHR is the right call, and we'll say so plainly.

The honest split is this. If the device and imaging integration is your bottleneck, Epic Cupid or a dedicated cardiology platform wins, full stop. If documentation time after a 22-visit day is what's costing you evenings, that's the problem we're built for. The [best EMR for small practice](../best-emr-for-small-practice/) guide covers the broader selection criteria if you're not sure which camp you're in.

## When a cardiology-specific EHR is the better fit

Choose Epic Cupid, PrognoCIS, or a comparable cardiovascular platform when any of these are true:

- Pacemaker, ICD, and Holter data need to flow into your chart automatically, not get retyped
- Echo and EKG readings must live in structured, reportable fields tied to imaging
- You run a cath lab, EP program, or nuclear service that needs procedure documentation with hemodynamics
- You're a large cardiology group or health system with an implementation team to support the build
- Cardiovascular structured reporting is a compliance or registry requirement for your program

If none of those are hard requirements, or you have the device layer covered elsewhere, the field opens up, and a documentation-first tool becomes the better spend.

## How to evaluate in a week

Skip the polished demos first. Do this.

List your hard requirements. Device data, echo and EKG structured reporting, cath and EP procedure docs: yes or no on each? One yes short-lists you to Cupid or a dedicated cardiology platform. If those are covered elsewhere, or they're nice-to-haves, the lighter options come into play.

Run each finalist on a real clinic day. Not a scripted walkthrough. A Thursday of heart-failure follow-ups, AFib rechecks, and a device clinic will surface things no demo will.

Ask the audio question of any ambient scribe on your list. What happens to the recording once the note is done? Is it stored, and for how long? That answer matters clinically and under HIPAA.

Get total cost in writing. Monthly per-provider fee, setup, per-module add-ons, interface fees for your device and imaging systems. Base pricing is the cheapest number a vendor will show you. The full invoice, with the cardiology interfaces, is the real one.

Patient Square publishes its plans on the [pricing page](/us/pricing/). You can request an assisted 7-day trial after workspace setup. Book a short demo if you want to see the note output on a real heart-failure or post-cath follow-up before trying it.

## Bottom line on the best EHR for cardiology

There isn't one best cardiology EHR, and any post that names a single winner is selling you something. If device and imaging integration is your bottleneck, Epic Cupid or a dedicated cardiology platform earns the higher cost and the build effort. Those handle cath, echo, EP, and device data the way general EHRs can't.

If your bottleneck is documentation time after a 22-visit day plus a stack of reads, a bundled AI EHR with an ambient scribe is the cleaner spend, and it's published, not quote-only. Ours sits at $119 per clinician per month on the annual Copilot plan, on the [pricing page](/us/pricing/), no sales call required to read the number.

## Frequently asked questions

The FAQ above answers the recurring ones: the features cardiology actually needs, whether we integrate with device and imaging systems (we don't), the cost range across vendors, and whether an AI scribe fits cardiology documentation. For the full breakdown, see the [pricing page](/us/pricing/); a demo shows the scribe on your own cardiac note types.

---

## Best HIS Software in India (2026): Honest Roundup
https://patientsquare.com/in/blog/best-his-software-india/
Published 2026-08-04 · Updated 2026-08-29 · Tags: best, his-software, roundup, comparison, abdm

A working roundup of Hospital Information System (HIS) software in India for 2026, scored on modules, ABDM-readiness, AI charting, interoperability, and rupee pricing.

A Hospital Information System (HIS) is the integrated software that runs a hospital's clinical and administrative operations: registration, wards, OT, lab, pharmacy, radiology, and billing, often with the EMR inside it. HMS is used almost interchangeably. An EMR is narrower, the clinical record. In practice, an enterprise HIS is the operational backbone, while an AI documentation layer can produce a reviewable note draft alongside it.

Verdict up top: the best HIS software in India depends on your scale and where the pain is. Government hospitals can assess NIC e-Hospital and C-DAC e-Sushrut. Hospitals that can support an implementation programme can assess Bahmni or an enterprise HIS. Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot. Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Validate every required specialist workflow during discovery.

Here is a practical read: separate hospital operations from the clinical-note workflow, then ask each candidate to demonstrate the work your teams must complete.

| | e-Hospital (NIC) | e-Sushrut (C-DAC) | Bahmni | Hospital Copilot |
|---|---|---|---|---|
| **Best starting context** | Government hospitals | Public-sector programmes | Open-source implementation path | Hospital discovery |
| **Published module breadth** | HMIS modules | HMIS programme | Clinical, lab, imaging, inventory, billing, accounting | Validate required specialist workflows |
| **Deployment decision** | Government service path | Programme fit | Implementation ownership | Complete Patient Square HIS/EHR or alongside incumbent HIS/EHR |
| **Price question** | Ask the programme | Ask the programme | Price implementation, support, and exit | Demo-priced |
| **Proof to request** | Current service scope | Current programme scope | Rollout and continuity evidence | Workflow and rollout evidence |

_Published vendor and programme descriptions are a starting point, not a substitute for a workflow demonstration and written scope._

## What "HIS software" actually means

The terms blur, and that's the first thing to sort. A **Hospital Information System (HIS)** is the integrated software that runs a hospital: patient registration, ward and bed management, OT scheduling, lab, radiology, pharmacy, and billing, usually with the clinical record (EMR) inside it. Vendors and buyers use "HIS" and "HMS" almost interchangeably. An **EMR** is the narrower piece, the clinical record itself.

For a buyer, the useful split is between two layers. One is the **operational backbone**: everything that keeps the hospital floor running, which is what an enterprise HIS delivers. The other is the **clinical note**: the record a doctor produces per visit, where time and medico-legal risk pile up in a busy OPD. An AI documentation layer can produce a note draft for clinician review alongside the HIS.

Confusing the two is how hospitals overbuy. Slow notes are a reason to test a documentation layer. They are not, by themselves, proof that a hospital needs to replace its HIS.

## How we scored the options

Five things decide whether HIS software earns its cost at a real hospital.

- **What it's for: operations or documentation.** Decide first. A full HIS is evaluated for operational workflows; an AI layer is evaluated for the note workflow. They are not substitutes.
- **Module depth for your scale.** A 40-bed hospital and a 400-bed one need different module sets. Pay for what you'll switch on, not the full brochure.
- **Interoperability and ABDM.** Can it share records under ABDM, and which NHA milestone has it cleared? "ABDM-ready" is loose, so make the vendor name it.
- **Documentation workflow.** Does the candidate produce the note format, review step, and retrieval path clinicians require? Test this with a real specialty scenario.
- **Quote comparison.** Ask every candidate to state the price unit, contract term, included modules, implementation, support, tax, renewal, and exit terms before comparing totals.

## How the main options compare

**e-Hospital**, from the National Informatics Centre, is a government-hospital SaaS path with published HMIS modules. **e-Sushrut**, from C-DAC, is a public-sector HMIS programme. **Bahmni** is an open-source hospital system whose published scope includes clinical, laboratory, imaging, inventory, billing, and accounting components. Each option still needs an implementation, support, continuity, and exit review.

**Hospital Copilot** can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. More on the fit below.

If your operations are fine and the note is the problem, skip ahead and [see the India pricing](/in/pricing/). Otherwise, keep reading.

## What "ABDM-ready" really means for an HIS

This is the row that trips up HIS buyers most, so slow down here. ABDM, the Ayushman Bharat Digital Mission run by the National Health Authority, is where India's interoperable patient record is heading. But "ABDM-ready" on an HIS brochure can mean almost anything, because certification runs against milestones, each doing a different job:

- **M1** covers creation and verification of the ABHA number.
- **M2** is the Health Information Provider milestone for sharing records under patient consent.
- **M3** lets it pull records from other providers into your view.

Certification applies to software through NHA's sandbox path. A hospital still needs to establish its own registry and onboarding path with NHA. Ask the vendor which milestones have current production evidence, and ask the hospital team which facility and professional registrations apply. Software that can create and verify an ABHA number but cannot share records under patient consent has a narrower scope than a buyer who needs record sharing.

Our own position, stated plainly: Patient Square has ABDM integration on the roadmap, not shipped. We won't badge a status we don't hold, and neither should any HIS vendor you're evaluating.

## When a full HIS is the right category

If bed management, claims, lab turnaround, and stock are the active concerns rather than charting, begin by evaluating a full HIS against those workflows. A full HIS is the relevant category when you:

- Run wards, an OT, a lab, or radiology and need those modules integrated with the record.
- File TPA and cashless claims alongside GST billing in one system.
- Manage pharmacy and inventory tied to prescriptions and dispensing.
- Need cross-department, NABH-friendly reporting.

If two or more of those are true, start with an HIS shortlist such as e-Hospital, e-Sushrut, Bahmni, or another platform whose required modules and implementation evidence you can verify.

## Where Patient Square fits

Hospital Copilot can use the complete Patient Square HIS/EHR as the hospital's record system or work alongside an existing HIS/EHR. Discovery should validate every required cross-department workflow, specialist module, rollout plan, continuity practice, and exit requirement.

During the visit, the ambient AI can produce a structured note, ICD-10 suggestions, and a prescription draft for clinician review. It accepts code-mixed Hindi-and-English input and returns notes in clinical English. The published Hospital Copilot scope does not state every administrative or specialty workflow, so validate the required administrative, clinical, rollout, continuity, and exit workflows during discovery.

Hospital Copilot is demo-priced. Practice Copilot's ₹1,599, ₹2,399, and ₹3,999 annual monthly-equivalent India rates apply to practices, not hospital deployments.

Bring your facility size, department mix, incumbent HIS/EHR, and one difficult workflow to a Book a demo conversation. That is the right test for Hospital Copilot.

---

## Best Pharmacy Software in India (2026): Honest Picks
https://patientsquare.com/in/blog/best-pharmacy-software-india/
Published 2026-08-04 · Tags: best, pharmacy-software, roundup, comparison, inventory

A practical roundup of pharmacy software for Indian clinics and chemists in 2026, scored on billing, inventory, GST, drug-safety checks, and real rupee pricing.

For a standalone chemist shop, a dedicated pharmacy billing and inventory tool like Marg ERP or a POS-focused system fits best. For a clinic pharmacy tied to the doctor's prescription, an EMR with a built-in pharmacy module (HealthPlix) keeps dispensing and Rx in one place. If the real gap is upstream, doctors writing prescriptions by hand, an AI platform like Patient Square that drafts a clean, checkable Rx during the visit removes the errors before they reach your counter. Match the tool to where your pain actually is.

Straight answer first: the best pharmacy software in India depends on your setup. A retail chemist and a clinic that dispenses against its own prescriptions need different tools. For a standalone shop, a dedicated billing-and-inventory tool wins. For a clinic pharmacy, an EMR with a pharmacy module keeps Rx and dispensing together. But if the actual mess is upstream, handwritten prescriptions your counter has to decode, our pick is **Patient Square**, because it drafts a clean, structured prescription during the visit that you review and sign, so a legible order reaches your dispensing screen. The bundled AI EHR starts at ₹2,399 a month per clinician on annual billing, ex-GST. [See the India pricing](/in/pricing/).

Here's the honest read, scored on what a real Indian pharmacy counter needs, plus where the prescription itself gets fixed.

| | Standalone pharmacy tool (e.g. Marg / POS) | Clinic EMR + pharmacy module (HealthPlix) | Patient Square (AI Copilot + EHR) |
|---|---|---|---|
| **Best for** | Retail chemist: stock + billing | Clinic that dispenses its own Rx | Fixing the prescription before it hits the counter |
| **GST billing** | Yes, core | Yes | Not a billing tool |
| **Inventory / expiry** | Yes, core | Yes | No |
| **Rx drafted for the doctor** | No | EMR notes | Yes, an AI-drafted Rx the doctor reviews and signs |
| **Drug-interaction check** | Usually no | Listed (DDI alerts) | No; the prescriber reviews the draft |
| **Published price** | Low thousands ₹, annual/one-time (varies) | ₹11,999-17,999/yr per doctor | ₹2,399/mo per clinician (Copilot, annual) ex-GST |
| **Indian-language input** | Billing UI | EMR UI | Hindi + Indian languages on input |

_Figures from vendor pages or general market ranges as of 2026, hedged where prices vary by seat and state. Confirm before buying._

## What "pharmacy software" actually covers

The label hides two jobs, and mixing them up is how clinics overspend. Decide which one you're actually buying.

One is the **counter system**: GST billing, batch and expiry tracking, stock reorder, supplier purchase, returns, and daily sales reports. A retail chemist runs the whole shop on this. Marg ERP and cloud POS tools live here, and a clinic pharmacy that mostly sells over the counter needs this too.

The other is the **prescription itself**: the thing the doctor writes that your counter then has to read, verify, and dispense. In a busy Indian OPD, a handwritten Rx in a two-minute consult is where dosing errors and callbacks are born. Software that fixes the prescription sits upstream of your billing screen, and it solves a different problem than any inventory tool.

You don't need a better billing system because your doctors' handwriting is a hazard. You need the prescription drafted cleanly in the first place.

## How we scored the options

Five things decide whether pharmacy software earns its keep at a real Indian counter or clinic.

- **What it's for: the counter or the prescription.** Settle this before you compare features. A billing tool won't clean up a doctor's Rx, and a prescribing tool won't run your stock.
- **GST and compliance, done right.** Compliant invoices, HSN codes, batch and expiry, returns. This is table stakes for a chemist, so treat it as pass or fail, not a differentiator.
- **Inventory discipline.** Reorder points, near-expiry alerts, supplier reconciliation. This is where a good tool pays for itself and a weak one leaks money.
- **Safety at the point of prescribing.** Does anything catch a bad interaction or a wrong dose before it's dispensed? Most counter tools don't. The prescribing layer can.
- **Honest rupee pricing.** Is the number published, ex-GST, and does it scale with seats sensibly? Watch for per-terminal charges that balloon.

## How the main options compare

**Standalone pharmacy tools** like Marg ERP and various cloud POS systems are built for the counter. They handle GST billing, batch and expiry, purchase and returns, and daily reconciliation, usually at a low annual or one-time licence in the thousands of rupees (exact pricing varies by vendor, seats, and state, as of 2026). For a retail chemist, this is the right buy, and no clinical tool replaces it.

**HealthPlix**, a specialty OPD EMR, includes a pharmacy module so a clinic can tie dispensing to its own prescriptions. It publishes real prices, ₹11,999 a year for Pro and ₹17,999 for Elite per doctor, with billing, pharmacy, and drug-interaction alerts. For a clinic that both prescribes and dispenses, keeping it in one record cuts re-entry and reconciliation errors.

**Patient Square** sits upstream of both: it fixes the prescription at the moment it's written. More on that fit below.

_Sources: GST portal; vendor pages, 2026._

If your real gap is the prescription, not the stock ledger, you can skip ahead and [see the India pricing](/in/pricing/). Otherwise, keep reading.

## Where a standalone or EMR pharmacy tool wins

Most of the time, honestly. If your pain is stock, expiry, and GST, a counter system or an EMR pharmacy module is the right answer, and a prescribing tool won't help. Pick a dedicated pharmacy tool when you:

- Run a retail chemist where billing and inventory are the whole business.
- Need tight batch, expiry, and supplier reconciliation to stop stock leakage.
- Want GST-compliant invoices and returns handled without workarounds.
- Dispense mostly over the counter, not against your own prescriptions.

If two or more of those describe you, start with a pharmacy-first tool, and add a clinical layer only if prescribing is also a problem.

## Where Patient Square fits

Upstream, at the prescription, and that's why it's our pick for the software that stops errors before they reach the counter. Patient Square isn't your billing system and won't pretend to be. It fixes the Rx at the source.

The product is a Copilot: the ambient AI listens during the visit and drafts a structured note, ICD-10 suggestions, and a prescription for the doctor to review and sign. The Rx isn't auto-sent; it's a draft the clinician reads, corrects, and signs in the room, so any problem gets caught by the prescriber at the source, not decoded (or missed) later at your counter. For Indian OPDs, it takes Hindi and Indian-language input and returns a clean, legible prescription instead of the handwriting your dispenser has been squinting at for years.

The prices are on the page, per clinician. Assist runs ₹1,999 a month (₹1,599 annual, no EHR). Copilot, the tier with the bundled AI EHR that drafts the Rx, is ₹2,999 (₹2,399 annual). Autopilot is ₹4,999 (₹3,999 annual). All ex-GST, so add 18% and the Copilot invoice lands near ₹2,831 a month. Transparent per-clinician pricing you can check on the page, not a quote you chase.

Our honest position: if your problem is truly stock and billing, buy a pharmacy tool, not us. But if the root cause of your counter's callbacks and dosing queries is the prescription itself, fixing it at the point of writing does more than any inventory feature. [See the India pricing](/in/pricing/) or [start from the India home page](/in/), and let a real clinic day show you where your prescriptions land.

---

## Best EMR for Solo Practice: Scribe + EHR at One Price
https://patientsquare.com/us/blog/best-emr-for-solo-practice/
Published 2026-08-03 · Updated 2026-08-29 · Tags: ehr, solo-practice, comparison, pricing

The best EMR for a solo doctor in 2026, ranked on what matters for a practice of one: price, contract, and daily workflow.

There's no single winner, only the best fit for a practice of one. Patient Square fits a solo doctor who wants an ambient scribe and AI EHR bundled at a published $119 per clinician per month, with a 7-day trial. Practice Fusion suits a bare-bones cash-pay solo; DrChrono fits an iPad-first clinic. Match the tool to how you actually run your day.

The best EMR for a solo practice in 2026 is the one whose price, contract, and daily workflow fit a practice of one. Our pick is Patient Square at $119 per clinician per month with the AI EHR and an ambient scribe bundled, and we'll name exactly when Practice Fusion, DrChrono, or CareCloud beats us. Check [our pricing](/us/pricing/) as you read.

> **Key takeaways**
>
> - A solo doctor is the practice's only IT, admin, and buyer, so a clear price, contract, and daily workflow matter more than a long feature list.
> - The free EMR era is over. Practice Fusion pioneered the free, ad-supported model in 2005 and went paid in 2018; it now runs about $149 to $199 per provider per month.
> - Solo-friendly EMRs span $149 to $650 per provider per month; CareCloud and DrChrono often require annual or three-year contracts plus a setup fee.
> - Patient Square publishes $79 for documentation and $119 with the full AI EHR and scribe bundled, with a 7-day trial and no setup fee.

## A solo practice buys software differently, so rank on that

A two-provider clinic has someone who handles the front desk and maybe a part-time biller. A solo doctor is the front desk, the biller, the IT department, and the person who signs the check. That changes what "best" means. You're not evaluating an enterprise rollout. You're deciding whether one more login is worth it on a Tuesday when you've got 18 patients and no one to delegate setup to.

So the questions that decide it are different. Is there a contract that locks me in before I know it works? Does the available trial provide enough evidence for a decision? And when the last patient leaves at 5:40, does the software help me finish the note, or just store it after I type it? Feature grids don't answer those. This roundup does, and yes, we build one of the tools on it, so we'll say where we lose.

## Is there still a free EMR for a solo practice?

Short answer: no, not in any real sense. This trips up a lot of solo doctors who remember the old pitch.

Practice Fusion built its whole brand on a free, ad-supported EMR starting in 2005. It was genuinely free for years, funded by ads shown to clinicians. That model ended. Per Wikipedia's record and Practice Fusion's own transition notices, the company moved to paid subscriptions on June 1, 2018, after Allscripts (now Veradigm) acquired it. Accounts that didn't buy a plan dropped to view-only.

As of 2026, there's no mainstream free ambulatory EMR worth building a practice on. What took its place is transparent low pricing and free trials. That's the honest reframe for a solo doctor chasing "free": you can't get free anymore, but you can get a published price and test the thing on real visits before you pay. We think that's a better deal than free-with-ads ever was, and we'll defend that opinion below.

## Which EMR fits which kind of solo doctor?

Here's the field, sorted by the solo situation each one actually suits. Prices are 2026 figures where the vendor publishes them; the rest are quote-only.

### Practice Fusion: best for a bare-bones, cash-pay solo

If you want a clean, cheap, ONC-certified cloud chart and you're fine typing your own notes, Practice Fusion is a fair pick. It runs roughly $149 to $199 per provider per month, does charting, e-prescribing, scheduling, and lab connectivity, and it's simple. That simplicity is the appeal for a solo cash-pay or concierge doctor who doesn't want moving parts. Where it stops helping: it has no native ambient scribe, so if your evenings vanish into charting, Practice Fusion stores the note but doesn't write it. You'd bolt on a separate scribe and paste across.

### DrChrono: best for an iPad-first solo clinic

DrChrono was built with solo and small practices in mind, and its iPad-native charting is the reason people who love it love it. If you chart at the point of care on a tablet and want an all-in-one that includes practice management, DrChrono belongs on your shortlist. The trade-offs for a practice of one are the commitment and the ramp: plans commonly start near $199 per provider per month and climb to the $399 to $599 range for fuller suites, annual contracts are typical, and setup fees have been reported from $500 to $2,000. That's real money and a real lock before you've charted a single visit.

### CareCloud: best for a solo planning to grow into a group

CareCloud is capable, but it prices and contracts like a system built for bigger practices. Third-party trackers put it around $349 to $649 per provider per month, pricing is quote-only, and the vendor commonly signs three-year contracts. For a solo doctor, that's a lot of commitment for a system whose value shows up most when you scale. If you're solo today but genuinely plan to add providers soon, it can pencil out. If you're staying solo, the contract length alone is a reason to look elsewhere.

### Tebra (Kareo): best for a solo who wants marketing tools too

Tebra, which absorbed Kareo, pairs a low-ish base EHR with patient-acquisition and marketing tooling, and it ships a native AI Note Assist for note drafting. The catch is transparency: Tebra doesn't publish EHR pricing, so your all-in number arrives after a demo, and the fees can stack. If growing your patient panel is the priority and you want marketing built in, it's a reasonable choice. We broke down the full cost picture in [what Kareo and Tebra actually cost](../kareo-ehr-pricing/).

## Our pick: Patient Square, for published pricing and a bundled scribe/EHR path

Here's our case, stated as ours. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On the Copilot plan, that scribe comes with the bundled Patient Square EHR at $119 per clinician per month on annual billing ($149 month-to-month). If you already have a chart you like and just want the documentation help, Assist is $79 per month annual and Practice Copilot can work alongside your existing EHR. Every plan includes **EHR-ready export (PDF · HL7 · FHIR)**.

The wedge for a solo practice isn't the scribe alone. It is the published price and the chance to test a 7-day trial on your own visits before you pay. There are no setup fees. Plans include unlimited visits and notes with no per-note metering. When you're the only person in the building, a trial on a real clinic day is worth more than a feature nobody had time to configure.

That's also our answer to the free-EMR question. You can't get free, but you can get a published $79 or $119 number and a trial that runs on your real Tuesday. We'd rather be judged on that than on ad revenue.

Want to see the scribe on your own note types? Request your 7-day trial, or read [the pricing](/us/pricing/) first.

## What the two setups actually cost a solo doctor in year one

Say you're one clinician, 18 visits a day. Compare the shape of the bill, not just the headline rate.

A quote-only vendor with an annual or three-year contract and a $500 to $2,000 setup fee costs you a sales cycle before you learn the number, then locks the number in for a year or more, then adds documentation help as a separate tier or partner tool. Your first-year total is the monthly rate times twelve, plus setup, plus whatever the scribe layer costs, and you commit to most of it sight unseen.

A published bundle at $119 per clinician per month with the scribe already inside is one line you can read on a spreadsheet today. Twelve months, no setup fee, and if the 7-day trial doesn't convince you, you don't proceed. For a practice of one with no procurement team, that difference isn't a rounding error. It's whether you can decide this yourself in an afternoon.

## When a competitor is the better fit for you

We lose in specific, honest cases, and pretending otherwise would make this list useless.

Practice Fusion wins when your only need is a cheap, certified chart and you genuinely don't want a scribe. At roughly $149 to $199 with no documentation AI, it's simpler and does the record-keeping job. If you're a cash-pay solo who types fast and hates extra tools, that's a fair call, and we won't talk you out of it. DrChrono wins if you chart on an iPad and want that native tablet workflow above all else; nobody matches its iPad heritage for a solo point-of-care clinic. And CareCloud wins for the solo doctor who is about to become a three-provider group and wants a platform built to scale into that. We're built for the practice of one that wants an AI-native workflow at a price it can read, not the practice racing to enterprise.

If that practice of one is you, [see the pricing](/us/pricing/) and put it next to the quotes you'd otherwise have to chase.

## How to decide in one afternoon

Skip the feature matrix. For each vendor on your shortlist, answer four questions.

1. Does the available trial give me useful evidence on real visits before I choose a term?
2. Is there an annual or multi-year contract, and a setup fee, before I know it works?
3. Is documentation help (an ambient scribe) in the price I'm quoting, or a separate tier or partner tool?
4. Does the note come back structured with ICD-10 suggestions and a prescription draft, or just stored after I type it?

Rank on those, not on the length of the feature list. For the broader small-practice field beyond solo, our [best EMR for a small practice](../best-emr-for-small-practice/) roundup covers cost and fit generally, and [which small-practice EHRs include an AI scribe](../best-ehr-small-practices-ai-scribe/) sorts the market by scribe economics.

## Choose for the work a solo practice actually does

There's no universal winner, only the fit for a practice of one. The free EMR is gone; what replaced it is transparent pricing and trials. Practice Fusion is the cheap, simple, no-scribe pick. DrChrono suits an iPad-first solo who'll accept a contract. CareCloud fits a solo about to grow into a group. Our pick, Patient Square, puts the AI EHR and an ambient scribe in one published $119 line. Rank on price, lock-in, and whether the note gets written for you, then Request your 7-day trial on the one that makes your list.

---

## Best Hospital Management Software in India (2026): Honest Roundup
https://patientsquare.com/in/blog/best-hospital-management-software-india-2026/
Published 2026-08-03 · Updated 2026-08-29 · Tags: best, hospital-management-software, roundup, comparison, abdm

A working shortlist of hospital management software for Indian hospitals and clinics in 2026, scored on modules, ABDM-readiness, AI charting, and real rupee pricing.

It depends on your workflow. Attune and Medixcel are enterprise options worth putting through a hospital-specific demo, while government hospitals can consider eHospital from the NIC. If doctors spend their evenings charting, an AI-native platform that drafts the note during the visit, like Patient Square, addresses a different problem than another billing module. Score each on modules, ABDM, and documentation workflow.

There is no single best hospital management software in India, because a nursing home and a multispecialty hospital buy differently. For running operations, an enterprise HMS such as Attune or Medixcel may fit. Hospital Copilot gives hospitals two deployment modes: use the complete Patient Square HIS/EHR as the record system, or keep an incumbent HIS/EHR and use Hospital Copilot alongside it. It is demo-priced, so the useful next step is a facility-specific discussion, not a practice pricing page.

Below is the honest read, scored through one lens most HMS reviews skip: how much clinical documentation the software takes off your doctors' plates.

| | Attune / Medixcel (enterprise HMS) | eHospital (NIC) | HealthPlix (specialty EMR) | Patient Square (AI Copilot + EHR) |
|---|---|---|---|---|
| **Best for** | Attune: large-chain / multi-branch positioning. Medixcel: end-to-end HMS with billing emphasis | Government hospitals | Specialty OPD clinics | Hospitals choosing a complete HIS/EHR path or selected Hospital Copilot workflows alongside an incumbent |
| **AI ambient notes** | Verify in vendor demo | Verify in vendor demo | Assisted charting | Yes, ambient AI note during the visit |
| **Record-system path** | Validate scope in vendor demo | Full record | EMR | Complete Patient Square HIS/EHR, or Hospital Copilot alongside an existing HIS/EHR |
| **Published price** | No price used in this comparison: request a vendor scope | Free for govt | ₹11,999-17,999/yr per doctor | Demo-priced hospital deployment |
| **Indian-language input** | Verify in vendor demo | Verify in vendor demo | Verify in vendor demo | Hindi + Indian languages on input |
| **ABDM** | Per vendor, verify milestone | Government stack | Listed | On roadmap, not claimed live |

_Figures from each vendor's pages or third-party directories as of 2026, hedged where sales-gated. Confirm before buying._

## What "hospital management software" actually means

It's a loose label, and that's the first trap. Vendors stretch "HMS," "HIS," "EMR," and "practice management" to mean almost the same thing on a landing page. Buyers, though, are usually chasing one of two very different outcomes.

One is the **operational spine**: registration, bed management, OT scheduling, pharmacy and inventory, lab orders, TPA and cashless claims, GST billing. That's a full HMS.

The other is the **clinical note**: the thing that turns a consultation into a signed, retrievable record. In a busy Indian OPD where a consult can run two or three minutes, that note is where doctor time and medico-legal risk both stack up. An AI documentation layer handles this slice and sits on top of whatever operational system you already run.

Buy the wrong one and you overspend. You don't need a new HMS because your notes are thin. You need something that fixes the notes.

## How we scored the options

We skipped the bloated feature grid. Five things decide whether an HMS earns its monthly fee at a real hospital.

- **What it's actually for: operations or documentation.** Decide this before anything else. A billing suite won't fix charting, and an AI scribe won't run your OT.
- **Module depth that matches your facility.** A nursing home does not need a blood bank module. Pay for the modules you'll switch on this year, not the brochure.
- **ABDM-readiness, milestone named.** If you want ABHA-linked records, the software must be ABDM-certified, and "ABDM-ready" hides three different NHA milestones. Make the vendor name the one it has cleared.
- **Documentation burden lifted.** Does it shorten the doctor's note, or just store it? An ambient AI note removes work. A form-heavy screen adds it.
- **Honest rupee pricing.** Is the number on the page, ex-GST, or does it flex with how hard you negotiate? Quote-based isn't a dealbreaker for big deployments, but it's friction.

## How the main options compare

Adrine's 2026 comparison positions **Attune** for large chains and multi-branch hospitals. It describes **Medixcel** as an end-to-end hospital-management option with a billing emphasis. That is enough to put both on an enterprise shortlist, not enough to infer modules, facility size, or price. Ask each vendor to run the workflows that matter at your hospital.

**eHospital**, built by the National Informatics Centre, is the default for government facilities. It's free for government hospitals and tied into the national digital-health stack. For a private hospital it's usually not the fit, but it's worth knowing it exists before you assume everything is paid.

**HealthPlix** is a specialty OPD EMR, not a full hospital system. It publishes real prices, ₹11,999 a year for Pro and ₹17,999 for Elite per doctor, with billing, pharmacy, and drug-interaction alerts, and it lists ABDM. For a busy specialty clinic that wants an EMR with assisted charting, it's a strong candidate. For a hospital floor with wards and an OT, it's under-scoped.

**Patient Square** offers two hospital deployment paths: the complete Patient Square HIS/EHR as the system of record, or Hospital Copilot alongside an existing HIS/EHR. More on the fit below.

_Sources: NHA / ABDM portal; vendor pages, 2026._

Still narrowing? If the issue is a hospital-wide record-system decision or a difficult workflow around an incumbent, book a Hospital Copilot demo and bring your facility size, department mix, existing HIS/EHR, and one workflow that currently breaks. Otherwise, keep reading for where each category wins.

## What "ABDM-ready" really means

This row trips up more hospital buyers than any other. ABDM, the Ayushman Bharat Digital Mission run by the National Health Authority, is where India's interoperable patient record is heading, and it's already large. But "ABDM-ready" on a pricing page can mean almost anything, because certification runs against milestones and each one does a different job:

- **M1** lets the software create and verify an ABHA number and register on the facility and professional registries (HFR and HPR).
- **M2** lets it share a patient's records, as FHIR, when the patient consents.
- **M3** lets it pull records from other providers into your view.

Certification is per-software, so a vendor clears the sandbox once and each hospital then registers itself. The buyer's question is one line: *which milestones have you cleared, and are they live in production or still in sandbox?* A system that can mint an ABHA (M1) but can't yet share records (M2) is "ABDM-ready" in marketing and half-built in practice.

To be straight about our own position: Patient Square has ABDM integration on the roadmap, not shipped. We won't badge a status we don't hold, and you shouldn't accept one from any vendor who can't name the milestone.

## Where a full HMS wins

Plenty of hospitals. If your nights aren't lost to charting but to bed management, claims, and stock, an AI note won't fix the real fire, and a full HMS will. A full HMS is the better buy when you:

- Run wards, an OT, or a blood bank and need those modules tied to the clinical record.
- File TPA and cashless claims and want them in the same system as billing.
- Manage pharmacy and inventory with dispensing tied to prescriptions.
- Need NABH-friendly reporting across departments.

If two or more of those are true, start your shortlist with an enterprise HMS, not with a documentation tool. Attune and Medixcel belong on that list only if their demo covers the workflows you need.

## Where Patient Square fits

Hospital Copilot can use the complete Patient Square HIS/EHR as the hospital's record system or work alongside an existing HIS/EHR. Its named hospital modules include AI Copilot EHR, Claims Management, AI Discharge Summary, and Bed / IPD Management, alongside the core Copilot set. The module names are the current scope ceiling. Validate every required OT, pharmacy, LIMS, RIS/PACS, billing, and specialist workflow in the demo.

The product is a Copilot: the ambient AI Medical Scribe hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft for a clinician to review and sign. For an Indian OPD, it accepts Indian-language input and returns the note in clean clinical English. The prescription remains a draft. It is not transmitted to a pharmacy.

Hospital Copilot is demo-priced. It is not a Practice Copilot tier, and the practice per-clinician prices do not apply to a hospital deployment.

The fit is straightforward. Choose the complete Patient Square HIS/EHR path when you are selecting a hospital record system. Choose the alongside path when the incumbent stays and you need the Hospital Copilot modules around it. In either case, start with the department and workflow that make the decision urgent.

Run the shortlist on a live hospital day. Book a Hospital Copilot demo and bring your facility size, department mix, incumbent HIS/EHR, and one difficult workflow. That conversation will tell you whether the complete HIS/EHR path or the alongside deployment is the better fit.

---

## WhatsApp Appointment Reminders for Indian Clinics: What Works
https://patientsquare.com/in/blog/clinic-appointment-reminders-whatsapp-india/
Published 2026-08-03 · Tags: whatsapp, appointment-reminders, no-shows, dpdp-consent, clinic-operations

How Indian clinics cut no-shows with WhatsApp appointment reminders, DPDP-aligned patient consent, and template-message rules that keep it compliant.

They can help by putting a timely, hard-to-miss reminder in front of the patient on a channel they already check. Results vary by clinic and patient mix, so treat it as a tool to test and measure rather than a guaranteed fix.

No-shows quietly cost Indian clinics a lot: an empty slot that a waiting patient could have used, and staff time already spent on scheduling. WhatsApp reminders are one of the most practical fixes, because almost every patient already lives on WhatsApp. Done right, a timely reminder with clean consent cuts missed appointments. Done wrong, it annoys patients and skirts the rules. This post keeps to appointment reminders specifically: reducing no-shows, getting consent under DPDP, and following WhatsApp's template rules.

> **Key takeaways**
> - WhatsApp reminders work because they reach patients on a channel they already check, at a time that matters.
> - Capture consent to message at registration. Under the DPDP Act 2023, a phone number is personal data used for a consented purpose.
> - Business-initiated WhatsApp messages generally use pre-approved templates, and patients can opt out. Follow current WhatsApp Business policy.
> - Reminders are a scheduling and messaging job, separate from clinical documentation.
> - AI Medical Scribe by Patient Square drafts the visit note; it does not send reminders.

## Why no-shows hurt more than they look

A missed appointment is not one cost. It is several stacked together. The slot goes empty when someone on the waitlist could have taken it. The staff time spent booking and confirming is gone. And in a busy clinic, a few no-shows a day add up to real lost capacity over a month.

Patients do not skip out of malice. They forget. The appointment was booked two weeks ago, life happened, and the reminder never landed. Which is the whole opportunity: most no-shows are a memory problem, not a commitment problem. A good reminder solves a memory problem.

## Why WhatsApp is the right channel in India

SMS gets ignored. Calls take staff time and often go unanswered. Email is not where most Indian patients live. WhatsApp is. It is the messaging app people actually open, and a message there is far more likely to be seen than a text buried under bank alerts.

That is the practical case. A reminder is only useful if the patient reads it, and WhatsApp is where reading happens. It also allows a short, clear message with the appointment details, which is exactly what a reminder needs to be.

None of this means blasting patients. It means using the channel they already check, with their consent, for a message they will find useful.

## Consent, done right under DPDP

This is the part clinics skip and shouldn't. A phone number is personal data. Sending marketing or reminders to it needs a lawful basis, and consent is the clean one. Under the DPDP Act 2023, personal data should be collected for a clear purpose, with the patient's consent, and used only for that purpose.

So build consent into registration. When a patient shares their number, ask plainly whether you may send appointment reminders to it on WhatsApp, and record the answer. Keep it specific: reminders are one purpose, general marketing is another. Do not treat "gave us a number" as blanket permission for anything.

A few consent habits that hold up:

- Ask at registration, in clear language, and log the consent.
- Separate reminder consent from any marketing consent.
- Give patients an easy way to opt out later, and honour it.
- Use the number only for what the patient agreed to.

The [DPDP guide for clinics](../dpdp-act-clinics-guide/) and the [DPDP explainer for doctors](../dpdp-act-explained-doctors/) cover the wider obligations. Reminders sit inside those rules, not outside them.

## WhatsApp template rules, in plain terms

You cannot just message patients however you like on the WhatsApp Business Platform. Business-initiated messages generally have to use templates that Meta approves in advance, and patients can opt out. This is deliberate: it keeps businesses from spamming people.

For appointment reminders, that means a pre-approved template with the details slotted in. Keep it relevant to the appointment. Do not smuggle promotions into a reminder template. Follow WhatsApp's current business policy and approval process, since the specifics get updated over time; the official WhatsApp Business site is where to check.

A workable reminder template covers the essentials and nothing more:

| Element | Include | Avoid |
|---|---|---|
| Greeting | Patient name | Overly casual tone |
| Appointment | Date, time, doctor or department | Vague "your appointment" |
| Location | Clinic name | Long address blocks |
| Action | How to confirm or reschedule | Pressure tactics |
| Opt-out | A way to stop reminders | Hiding the opt-out |

Short, clear, useful. That is what gets read and does not get reported.

## When to send, and how often

Timing does most of the work. Too early and it is forgotten again. Too late and the patient has already made other plans. A common, sensible pattern is a reminder a day or two before, with an option to confirm or reschedule.

Frequency is a balance. One well-timed reminder respects the patient. A stream of them trains people to mute you. The goal is to be helpful, not present. Send what a patient would thank you for, and stop there.

Measure it. Track no-show rates before and after you start, and adjust timing based on what your patients actually respond to. Reminders are a tool to tune, not a switch to flip and forget.

## How reminders and documentation fit together

Worth being clear, because these get muddled. Reminders live on the operations side: scheduling, messaging, front-desk work. Documentation is the clinical record created during the visit. They are two different workflows serving two different needs.

Reminders get the patient through the door. Documentation captures what happened once they are in the room. A clinic wants both working well, but they are handled by different tools. Your scheduling or messaging system runs reminders. Your clinical documentation is the note from the consult. There is more on the broader messaging picture in the [WhatsApp for clinics guide](../whatsapp-for-clinics-india/); this post stays on the reminder-and-no-show slice of it.

## Where the scribe sits, and where it does not

Straight answer: AI Medical Scribe by Patient Square does not send WhatsApp reminders. It is not a messaging tool. What it does is handle the documentation half of the day. It listens during the consult and drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft in about two minutes. The clinician reviews and signs. The record stays yours.

So the two pieces complement each other without overlapping. Reminders reduce empty slots; the scribe keeps the notes for the patients who do show up clean and consistent, without adding evening paperwork. If you want the documentation picture on its own, see the [scribe overview for Indian doctors](../scribe-for-doctors-india/).

## The short version

No-shows are mostly a memory problem, and WhatsApp reminders solve memory problems because that is where Indian patients already read. Capture consent at registration under the DPDP Act 2023, use pre-approved templates that patients can opt out of, time reminders a day or two ahead, and measure the effect. Keep reminders separate from documentation: different workflows, different tools. The scribe handles the note, not the message.

Want to keep the clinical side just as tidy as your scheduling? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> of the scribe on a real consult, read how we handle data on the [security page](../../security/), or see India plans on the [pricing page](../../pricing/).

---

## Clinic Software Costs in India: Pricing and Hidden Fees
https://patientsquare.com/in/blog/clinic-software-cost-guide-india/
Published 2026-08-03 · Updated 2026-09-29 · Tags: india, pricing, clinic-software, cost, buyers-guide

A buyer's cost guide to clinic software in India 2026: per-doctor vs per-clinic pricing, one-time vs subscription, hidden costs, and Patient Square's transparent ₹ tiers.

Vendors use different units and bundles, so compare a written quote rather than a market average. Patient Square Assist starts from ₹1,599 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST. The bundled Patient Square EHR starts from Copilot at ₹2,399 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST.

Clinic software quotes vary by licensing model and included modules. Compare a written quote by unit, inclusions, tax treatment, first-year total, and recurring total. [Practice Copilot pricing](../../pricing/) starts from ₹1,599 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST. The AI Copilot EHR is bundled from Copilot at ₹2,399 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> on a real clinic day.

> **Decision summary**
>
> - Compare vendor quotes by unit, inclusions, tax treatment, first-year total, and recurring total; do not rely on a market-average headline.
> - A perpetual licence does not make infrastructure, upgrades, support, or migration free.
> - Patient Square bundles the AI Copilot EHR from ₹2,399 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST.
> - Hidden costs can include migration fees, per-message charges, add-on modules, onboarding fees, and applicable GST; preserve the tax treatment stated in each quote.
> - Compare on all-in first-year cost and 3-to-5-year TCO, not the sticker rate.

## Published price sheet, checked 11 August 2026

| Vendor and plan | Public price | Published unit or condition |
|---|---:|---|
| Practo Ray CM Atom | ₹999 per month | One-year plan |
| Practo Ray Clinic Management | ₹1,499 per month | One-year plan |
| HealthPlix Pro | ₹11,999 per year | Annual plan |
| HealthPlix Elite | ₹17,999 per year | Annual plan |
| Eka Doc Plus | ₹16,999 per year | Exclusive of 18% GST |
| Eka Doc Pro | ₹18,749 per year | Exclusive of 18% GST |
| Eka Clinic Pro | ₹1,00,000 per year | Five doctors and fifteen staff; exclusive of 18% GST |
| KiViHealth | ₹12,000 plus GST | One year; longer terms are also listed |
| Patient Square Assist | ₹1,999 month to month or ₹1,599 monthly equivalent on annual billing | Per clinician; plus 18% GST |
| Patient Square Copilot | ₹2,999 month to month or ₹2,399 monthly equivalent on annual billing | Per clinician; plus 18% GST |
| Patient Square Autopilot | ₹4,999 month to month or ₹3,999 monthly equivalent on annual billing | Per clinician; plus 18% GST |

These products do not contain the same jobs. Keep each published unit and condition intact, and recheck the linked first-party page when requesting a quote.

## Per-doctor and per-clinic billing units

Quotes can use per-doctor or per-clinic billing units. Model both against the practice's actual doctor, staff, and location counts.

**Per-doctor subscription** charges for each doctor using the system. A solo doctor pays one seat; a five-doctor clinic pays five. Patient Square uses this model for Practice Copilot.

**Per-clinic or per-location flat pricing** charges a fixed amount per site regardless of doctor count.

Do not assume either model is cheaper. Run your actual doctor count, staff count, locations, and expected growth through both structures.

## Subscription vs one-time licence: the TCO question

The second fork is subscription versus perpetual licence. The invoices arrive differently, so compare the same time horizon.

| Model | Upfront cost | Ongoing cost | Buyer check |
|---|---|---|---|
| Cloud subscription | First month or year of seats | Subscription, usage, storage, interfaces, support, renewal | Ask for invoice schedule and limits |
| On-premise licence | Licence, infrastructure, implementation | Support, upgrades, database, security, major releases | Ask who owns every operating task |

Ask each vendor to provide the licence or subscription, infrastructure, migration, implementation, support, tax, and renewal terms in writing. Then compare the first-year total and the recurring total across the period you expect to use the system.

## The EHR question: bundled or a second invoice

Some quotes separate modules; others bundle them. Record exactly which capabilities, support, and renewal terms are included before comparing the headline.

Patient Square bundles its EHR into the Copilot tier. These are the current per-clinician rates; each is ex-GST plus 18% GST:

| Tier | Month to month (ex-GST) | Monthly equivalent on annual billing (ex-GST) | What you get |
|---|---|---|---|
| Assist | ₹1,999 | ₹1,599 | AI Medical Scribe, ICD-10 suggestions, prescription drafts, scheduling |
| **Copilot** | ₹2,999 | **₹2,399** | Assist plus WhatsApp messaging and the **AI Copilot EHR bundled** |
| Autopilot | ₹4,999 | ₹3,999 | Copilot plus AI Receptionist, follow-ups, priority support, ROI analytics |

On Copilot at ₹2,399 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST, the AI Copilot EHR is bundled. The scribe drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Pick Assist at ₹1,599 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST, if you keep an existing record system and want Practice Copilot alongside it. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> to test the workflow.

## Hidden costs that don't show on the headline

Build a quote sheet instead of guessing which charges are hidden. Give every vendor the same rows: subscription or licence; doctor, staff, and location quantities; migration; messages; storage; modules; onboarding; training; support; renewal; export; and tax. Mark each row included, capped, separately priced, or unknown.

The Patient Square GST math, once: ₹2,399 × 1.18 = ₹2,830.82, about **₹2,831 per clinician as the monthly equivalent including GST on annual billing**. Preserve the applicable tax treatment stated in every other vendor quote.

### Complete cost worksheet

Do not stop at the five headline rows. Use the same sheet for every supplier:

| Cost row | Quantity and rate | Year one | Later annual | Evidence |
|---|---|---:|---:|---|
| Base subscription or licence |  |  |  |  |
| Doctor and staff seats |  |  |  |  |
| Extra clinic or location |  |  |  |  |
| Scheduling and clinical record |  |  |  |  |
| Documentation or scribe |  |  |  |  |
| Billing, reports, pharmacy, inventory, lab |  |  |  |  |
| SMS, WhatsApp, voice, or email usage |  |  |  |  |
| Storage, attachments, and archive |  |  |  |  |
| Setup, templates, and configuration |  |  |  |  |
| Data cleaning and migration |  |  |  |  |
| Interfaces and third-party fees |  |  |  |  |
| Training, support, and go-live |  |  |  |  |
| Devices, connectivity, and printing |  |  |  |  |
| Internal doctor and staff time |  |  |  |  |
| Export, termination, and transition |  |  |  |  |
| GST and other applicable tax |  |  |  |  |

Ask the vendor to mark included items, caps, overage rates, and exclusions. "Included" without a limit is incomplete evidence.

**Year-one total = subscription or licence + setup + migration + interfaces + training + devices + internal implementation time + applicable tax.**

**Later annual total = recurring plan + seats + usage + storage + interfaces + support + internal operating time + applicable tax.**

Use the contract's real invoice schedule. If an annual rate is paid upfront, cash leaves upfront even when the pricing page displays a monthly equivalent.

## Five steps before signing

1. Model per-doctor and per-location quotes against your actual doctor, staff, location, and growth counts.
2. Choose subscription versus on-premise on a three-to-five-year TCO using written infrastructure, support, and upgrade quotes.
3. Confirm whether the EHR is bundled or separately priced.
4. Surface every hidden cost: migration, messages, modules, onboarding, and applicable GST. Get an all-in first-year number.
5. Run a trial on a real clinic day and record task completion, errors, and staff time.

For an OPD clinic, compare your written requirements with Copilot at ₹2,399 per clinician as the monthly equivalent on annual billing, ex-GST plus 18% GST, then use <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> before committing.

---

## Best EHR for Small & Community Hospitals (2026)
https://patientsquare.com/us/blog/best-ehr-for-small-hospitals-us/
Published 2026-07-31 · Updated 2026-08-27 · Tags: ehr, comparison, hospital, small-practice

Epic and Oracle own big hospitals. For a 25-to-100-bed community or critical-access hospital, the shortlist is different. Here's the honest 2026 pick, by fit.

There's no single winner. Meditech Expanse is the most common pick for rural and critical-access hospitals. TruBridge (formerly CPSI/Evident) is built specifically for rural and community facilities. athenahealth fits hospital-owned ambulatory clinics but isn't a primary inpatient system. Epic is possible via Community Connect but usually oversized. Match the vendor to your bed count and clinic footprint, not to brand names.

If you run a small or community hospital, the "best EHR" lists written for big health systems don't fit you. For a 25-to-100-bed community or critical-access hospital in 2026, the real shortlist is Meditech Expanse, TruBridge (formerly CPSI/Evident), and athenahealth for the clinic side, with Epic possible but usually oversized. We build an AI-native option too. See how the fits differ on our [hospital product page](/us/products/hospital-copilot/).

> **Key takeaways**
>
> - Epic holds 43.7% of acute-care hospitals but 56.9% of beds, per KLAS 2026, so it concentrates in large systems and is usually oversized for a standalone small hospital.
> - Meditech is the most common EHR among rural and critical-access hospitals; TruBridge (CPSI/Evident) has 1,200-plus deployments aimed at that same segment.
> - athenahealth fits hospital-owned physician clinics but isn't a primary inpatient system; small hospitals often pair it with a separate inpatient EHR.
> - Hospital Copilot is our AI-native hospital product, demo-priced, with an ambient scribe, AI EHR, claims management, discharge summaries, and bed/IPD management.

## Why the big-hospital EHR lists don't apply to you

Most "best hospital EHR" content ranks Epic and Oracle Health at the top and calls it a day. That ranking is real, but it's answering a different question. Per KLAS 2026, Epic holds 43.7% of acute-care hospitals and 56.9% of beds. Read those two numbers together. Epic wins the big systems, so it holds a lot more beds than hospitals. Oracle Health sits second at 21.9% of hospitals.

For a 30-bed hospital, that concentration is the whole story. The platforms that dominate by bed count were designed for hundreds of beds, dozens of service lines, and an IT staff to match. Drop one into a critical-access hospital and you're paying for scale you don't have and staffing you can't hire. That's why the small-hospital slice looks nothing like the headline chart.

KLAS also noted that in 2025 the new EHR decisions came mostly from smaller health systems with two to ten hospitals, and buying overall hit a five-year low. Translation: the small end is where the actual shopping is happening, and the vendors courting it aren't only the two on the front page.

## Meditech Expanse: the default for community and critical-access hospitals

Meditech is the most commonly used EHR among rural and critical-access hospitals, and that's not an accident of history. Expanse, its cloud-native platform, is aimed straight at community facilities that want one web-based system across inpatient and their owned clinics.

Meditech holds 14.7% of the acute-care market per KLAS 2026, well behind Epic and Oracle by bed count. But retention tells the more useful story for a buyer at your size: 84% of Meditech customers chose to migrate to Expanse in 2025, up from 63% the year before. Hospitals that already run Meditech are staying and upgrading rather than jumping ship.

Recent signings show the pattern. Hendry Regional Medical Center, a critical-access hospital in rural Florida, picked Expanse to replace four separate legacy systems and pull everything into one patient record. That "collapse several old systems into one" job is the classic small-hospital use case, and it's what Meditech is set up to do.

When Meditech is the better fit: you want a mature, ONC-certified inpatient EHR from a vendor with deep rural experience, and you're fine with a quote-based sales process. If your pain is fragmentation across old systems, this is a safe, proven answer.

## TruBridge (CPSI/Evident): built for the rural and RCM-heavy hospital

TruBridge is the name to know if the phrase "rural hospital EHR" describes you exactly. The company consolidated the CPSI, Evident, and Healthland brands under the TruBridge name, so if you've shopped for any of those, you've shopped for this. It reports 1,200-plus US deployments concentrated in rural and community facilities, plus roughly 45 years of domain history from its CPSI roots.

Certification is solid. TruBridge EHR v22 holds ONC 2015 Edition Cures Update certification through Drummond Group, which matters for interoperability programs and federal requirements. The typical customer, by TruBridge's own framing, is a critical-access hospital where Epic and Oracle are cost-prohibitive for the bed count, or a 25-to-150-bed community hospital wanting one vendor for both inpatient and ambulatory visits.

Revenue cycle is where TruBridge leans hardest. A 2026 Black Book survey of 162 rural hospital RCM leaders named TruBridge the benchmark leader for end-to-end and complete/extended RCM. For a small hospital where claims and collections are a constant fight, that focus is a real differentiator, not marketing.

When TruBridge is the better fit: you're rural, budget is tight, revenue-cycle performance keeps you up at night, and you want a single vendor sized for your facility rather than trimmed down from an enterprise product. We think it's the strongest pure-play rural pick on this list.

## athenahealth: a clinic-side answer, not a whole-hospital one

Here's where buyers get tripped up. athenahealth shows up on hospital searches, but it isn't a primary inpatient EHR. It's optimized for ambulatory practices, with particular strength in the 1-to-75-provider range. Inpatient workflows, OR management, and enterprise-scale operations are handled by Epic, Oracle, Meditech, or TruBridge, not athenaOne.

That doesn't make it irrelevant to a small hospital. It makes it a clinic tool. Ashe Memorial Hospital, a small facility, runs its physician practices on athenaOne while keeping inpatient departments on Meditech, then connects the two through CommonWell and coordinates with Epic-based neighbors through Carequality. That's a realistic hybrid: athenahealth for your owned clinics, a separate inpatient EHR for the hospital floor.

If you're weighing athenahealth for the ambulatory side, our breakdown of [what athenahealth actually costs](../athenahealth-ehr-cost/) walks through the per-provider math.

When athenahealth is the better fit: your immediate need is your owned outpatient clinics, not the inpatient floor, and you're comfortable running two systems joined by an interoperability network. For that job it's a strong ambulatory platform. For running the hospital itself, look at Meditech or TruBridge.

## What about Epic and Oracle Health at small scale?

Epic isn't off the table for a small hospital, but the path is usually indirect. Epic added standalone hospitals in 2025 through Community Connect, which lets a smaller facility tether to a larger neighbor's Epic instance instead of buying its own. If a nearby health system already runs Epic and will host you, that can be a real option. Direct, independent Epic ownership at 30 beds is rare because the cost and staffing rarely work out. Our [Epic cost breakdown](../epic-emr-cost/) covers why the number climbs so fast.

Oracle Health, meanwhile, has been losing ground exactly where you sit. KLAS reported Oracle down 56 hospitals in 2025, with losses heaviest among small health systems, and its Millennium platform ranked lowest-scoring across large, midsize, and small organizations in the 2026 Best in KLAS report. That's a hard recommendation to make for a small hospital in 2026.

So the honest read: Epic via Community Connect if a partner will host you, and a careful look at Oracle only if you already run it and have a reason to stay.

## Where Hospital Copilot fits, and where it doesn't

We'll be direct about our own product. Hospital Copilot is Patient Square's hospital line, and it's a different animal from the vendors above. It's AI-native from the start: an ambient AI scribe, an AI Copilot EHR, claims management, AI discharge summaries, and bed/IPD management. The AI Medical Scribe module listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

Now the honest part. Meditech and TruBridge are mature, ONC-certified inpatient platforms with decades of hospital deployments behind them. Hospital Copilot is newer and demo-priced, with no public tier, because a hospital rollout depends on your bed count, modules, and clinical setup. If your requirement is a proven legacy acute-care system with a long deployment track record, one of those two is the safer buy today, and we'd tell you so.

Hospital Copilot is the pick when the AI-first documentation workflow is the reason you're shopping. If your clinicians are drowning in charting and after-hours notes, and you'd rather build on a system where the scribe and the record are one thing instead of bolting a scribe onto a legacy EHR, that's the case for us. To see whether the modules line up with your workflow, book a demo and we'll walk your team through it.

## How to actually choose

Match the vendor to your shape, not to a leaderboard. A few questions cut through most of the noise:

- Do you run inpatient beds, owned clinics, or both? Both usually points to a single-vendor setup like Meditech or TruBridge.
- Is revenue cycle your biggest pain? TruBridge's RCM focus is built for that.
- Are you truly rural or critical-access? Meditech and TruBridge both target that segment directly; Epic and Oracle rarely fit it well.
- Is a nearby Epic system willing to host you? Community Connect becomes worth pricing out.
- Is your real problem documentation burden more than the record system itself? That's where an AI-native option like Hospital Copilot earns a look.

Most small hospitals land on Meditech or TruBridge for the core system, add athenahealth or a specialty tool for specific clinics, and evaluate AI documentation separately. There's no shame in a two-system setup joined by an interoperability network; plenty of small hospitals run exactly that.

## Bottom line

For a small or community hospital in 2026, skip the big-system rankings. Meditech Expanse is the broad default, especially if you're collapsing several old systems into one. TruBridge is the rural and RCM-focused pick. athenahealth handles owned clinics but not the inpatient floor. Epic is worth pricing only through Community Connect, and Oracle Health is a tough call at small scale given its 2025 losses.

Hospital Copilot is the AI-native option when documentation burden is the thing you're actually trying to fix. It's demo-priced because a hospital rollout is never one-size-fits-all. If that's the problem you're solving, start with a demo, and if you want to see how the AI copilot idea plays out for practices too, our overview of [what a Practice Copilot is](../what-is-a-practice-copilot/) covers the smaller end.

---

## EMR for Behavioral Health: Features Generic Ones Miss
https://patientsquare.com/us/blog/emr-for-behavioral-health-features/
Published 2026-07-31 · Updated 2026-08-27 · Tags: behavioral-health, ehr, therapy, documentation, scribe

A generic EMR stores a chart. Behavioral-health documentation needs therapy-note structures, treatment plans, group notes, and confidentiality handling.

Four things a medical EMR usually gets wrong for therapy: progress-note structures built for sessions (DAP, BIRP, or a narrative SOAP rather than a 15-minute template), a real treatment plan with goals you can update over time, group and family session notes, and confidentiality handling for sensitive records. A general EMR stores your chart; it wasn't shaped around the 50-minute hour.

A behavioral-health EMR needs four things a generic one usually gets wrong: therapy-note structures built for sessions (DAP, BIRP, or a narrative SOAP, not a 15-minute template), a real treatment plan with goals you update over time, group and family session notes, and confidentiality handling for sensitive records. A general medical EMR stores your chart. It just wasn't shaped around the 50-minute hour. If you're weighing systems, our [pricing page](/us/pricing/) shows where a bundled AI EHR lands.

> **Key takeaways**
>
> - Therapy documentation runs on DAP, BIRP, or narrative SOAP, not the short medical-visit templates a generic EMR ships with.
> - CMS requires an individualized written plan of care with goals, service type, frequency, and duration for Medicare behavioral health, reviewed periodically. A note field isn't a treatment plan.
> - Group notes are one session across many records; a per-patient medical EMR handles that shape badly.
> - 93% of behavioral health workers reported burnout in a 2023 survey of 750, and 68% of direct-care staff said admin time takes from client time.
> - An ambient scribe drafts the narrative note. It doesn't replace the plan, the group structure, or your clinical judgment.

## Why generic EMR note templates fight the therapy hour

Open a general medical EMR and the progress note is built for a focused visit. Chief complaint, a short HPI, an exam, an assessment, a plan. That layout works for a 15-minute follow-up. It fights a therapy session.

Therapists don't document that way. Most write in DAP (data, assessment, plan) or BIRP (behavior, intervention, response, plan), and even a SOAP note in behavioral health runs narrative, because you're reconstructing a 50-minute conversation rather than a physical exam. The content is longer. It's more contextual. A client's affect, what came up about a relationship, how they responded to a reframe, none of that drops cleanly into a medical template's boxes.

So clinicians do what people always do with software that doesn't fit: they route around it. They paste a wall of text into a "notes" free-text field, or they keep the real note somewhere else and copy a summary in. Both are a tax you pay every session. A behavioral-health EMR starts from the session-note formats therapists actually use, so the structure holds the work instead of resisting it. That gap is real. It's the difference between a note that takes four minutes and one that takes twelve.

## A treatment plan is not a note field

Most generic EMRs treat the treatment plan as an afterthought. For behavioral health, it's a compliance requirement.

For behavioral health billed to Medicare, CMS requires care under an individualized, written plan of care that states the type, amount, frequency, and duration of services, the diagnosis, and expected goals, reviewed and updated periodically (Medicare & Mental Health Coverage, MLN1986542, March 2026). For an intensive outpatient program the booklet is even more specific: the plan states the physician's diagnosis; the type, amount, frequency, and duration of services; and the treatment goals, established and periodically reviewed.

Read that as a software spec. You need a document that lives across visits, carries measurable goals, and gets updated as the client progresses, and your progress notes should tie back to it. A single free-text field labeled "plan" inside one encounter isn't that. It doesn't persist, it doesn't track goal progress, and it makes an audit painful, because the reviewer wants to see the plan, the goals, and the notes that show movement against them.

A behavioral-health EMR holds the treatment plan as a living object. A generic EMR usually makes you rebuild it by hand or bolt on a template that nobody keeps current. If you take insurance, this gap isn't cosmetic; it's the thing a payer audit looks for first.

## Group and family notes break a one-patient EMR

Group therapy exposes a design assumption baked into most medical EMRs: one patient, one encounter, one note.

A group session is the opposite shape. One meeting, many clients, and the documentation has to do two jobs at once. It records the group as a whole, the topic, the interventions, the arc of the hour, and it records each individual client's participation and response, filed in that client's own record. And it has to do the second job without spilling one member's protected information into another member's chart. A per-encounter medical EMR built for a solo visit makes this clumsy. You end up duplicating the group summary into every chart by hand, then editing each one for the individual piece, which is exactly the kind of repeat typing documentation software is supposed to kill.

Family sessions carry the same twist. Who is the identified client? Where does the note live? What about the other people in the room who aren't your patients? Behavioral-health documentation tools are built around these questions. General medical software mostly wasn't, because a cardiology clinic never has to answer them.

## What behavioral-health documentation needs vs. what a generic EMR ships

The table below lays it out: the documentation need on the left, and how a general medical EMR typically handles it. This is the original artifact for this post.

The point of the table isn't that a generic EMR is useless. It's that the fields it optimizes for are the wrong ones for session-based care. You feel the mismatch every time you force a narrative into a template or copy a group summary five times.

## Confidentiality is a feature, not a footnote

Behavioral-health records are more sensitive than most, and the software has to respect that at the record level, not just with a login screen.

Two cases show up constantly. First, the HIPAA psychotherapy-notes category: a therapist's separate session-analysis notes get heightened protection and are supposed to be kept apart from the regular chart. An EMR that has no concept of that separation makes it easy to blur the line. Second, substance use disorder records. Under 42 CFR Part 2, records held by a federally-assisted SUD program, including "private practitioners who hold themselves out as providing... substance use disorder diagnosis, treatment, or referral for treatment," carry consent and disclosure rules stricter than plain HIPAA. If you run that kind of program, your documentation system needs to track consent and log disclosures, not hope you remember.

A generic EMR treats all charts the same. That's fine for a general clinic. It's a real gap for a practice whose records are, by their nature, the kind people most want kept private.

## Where the scribe fits, and where it doesn't

Now the honest part, because we build a scribe and we're not going to pretend it does everything.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, ready to review and sign. For behavioral health, the value is narrow and real: it drafts the narrative progress note, the single heaviest chore, so you review and sign in the gap instead of writing at 10pm. It'll return the note in the structure you work in, and the session audio is processed in memory and discarded once the note is drafted, so there's no recording to retain. On our security posture, safeguards are HIPAA compliant, BAAs are available for every customer, and our SOC 2 Type II audit is underway; the full detail is on our [security page](../../security/).

But a scribe drafts a note. It is not the whole documentation system. Your treatment plan, your outcome measures, your group-note structure, and record-level confidentiality still live in your EMR. A scribe removes the after-hours writing. It doesn't turn a general medical EMR into a behavioral-health one. If someone sells you a scribe as the fix for every gap in this post, they're overselling.

Our read, stated as opinion: for a lot of therapy practices the biggest single win is getting the narrative note off your evening, and a scribe does that regardless of which EMR holds the chart. The rest of the behavioral-health feature set matters too; it just isn't what a scribe is for.

## When a dedicated behavioral-health EMR is the better fit

We'll draw the line plainly, because that's the useful thing to do.

If your compliance workflow needs to live in one system, a purpose-built behavioral-health EMR beats a general EMR plus a scribe. That's the case when you want a running treatment plan tied to your notes, built-in DAP or BIRP structures, group-note handling that doesn't require copy-paste, outcome-measure tracking like a PHQ-9 or GAD-7 trended over time, and, if you're a 42 CFR Part 2 program, consent tracking wired in. A dedicated system was designed around those exact jobs. Fighting a generic EMR to fake them is a slow tax.

Where we fit is different. If your chart is workable and your real pain is the documentation load, an ambient scribe that drafts the note is the cleaner, cheaper move, and it works alongside whatever EMR you already run. On the Copilot plan we also bundle an AI EHR, but we won't pretend it's a specialized behavioral-health record system with group-note workflows and outcome-measure trending built in. If that specialization is what you need, buy the specialized tool. We'd rather tell you that than lose your trust.

For the EMR side of this decision, our [honest EHR comparison for therapists](../best-ehr-for-therapists/) walks the trade-offs, and if the narrative note is your bottleneck, [how therapists use a scribe for DAP and BIRP notes](../ai-scribe-for-therapists/) covers the workflow. For the privacy questions specifically, the [behavioral-health scribe privacy guide](../ai-scribe-for-behavioral-health/) puts the audio question first.

## Bottom line on behavioral-health EMR features

A generic EMR stores your chart competently. It just wasn't built around therapy documentation: the DAP and BIRP note structures, a treatment plan CMS expects you to keep and update, group notes that span many records, and confidentiality for records people most want protected. Those are the features that separate a behavioral-health EMR from a medical one, and they're the ones worth checking before you commit.

If the narrative note is your heaviest chore, a scribe drafts it no matter whose EMR you use, and you can <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to run it on your own sessions. If your whole compliance workflow needs to sit in one purpose-built system, a dedicated behavioral-health EMR is the better fit, and we'd tell you so. Match the tool to the work, and don't buy note structures you'll never use.

## Frequently asked questions

The FAQ above covers the recurring ones: which features a behavioral-health EMR needs, whether a therapy note is a medical SOAP note, the treatment-plan requirement, group-note handling, and where a scribe fits. For the EMR comparison itself, see the [therapist EHR guide](../best-ehr-for-therapists/); for the scribe workflow, the [DAP and BIRP note walkthrough](../ai-scribe-for-therapists/).

---

## HIPAA-Compliant Practice Management Software
https://patientsquare.com/us/blog/hipaa-compliant-practice-management-software/
Published 2026-07-31 · Updated 2026-08-29 · Tags: hipaa, practice-management, compliance, security, pms

No one certifies practice management software as HIPAA compliant. What compliance actually requires: a signed BAA, access controls, audit logs, and encryption.

No. HHS states there is no standard that requires certifying compliance with the Security Rule, and the Office for Civil Rights does not certify software or vendors. A product can be built and operated to meet HIPAA safeguards, and prove it with a signed BAA and documented controls, but a HIPAA certificate does not exist. Treat any vendor selling one as a red flag.

"HIPAA-compliant practice management software" is a real requirement described by a phrase that means less than it sounds. No agency certifies software as HIPAA compliant. What HIPAA actually requires is a set of safeguards: a signed business associate agreement, access controls with audit logging, encryption in transit and at rest, and a breach process. The software can be built to meet them, but compliance is how you run it, not a stamp on the box. We publish our own posture on the [security page](/us/security/).

> **Key takeaways**
>
> - HHS does not certify any product or vendor as HIPAA compliant. A "HIPAA-certified" claim is a marketing red flag, not proof.
> - Real compliance means 5 things: a signed BAA, the 3 Security Rule safeguard categories, access controls plus audit logs, encryption in transit and at rest, and a breach-notification process.
> - You need a written BAA before patient data flows. OCR once settled with a single practice for $31,000 over a missing BAA alone.
> - Ask the vendor 5 direct questions in writing. If any answer is a slogan instead of a specific, keep shopping.

## "HIPAA certified" is not a thing anyone can sell you

Start here because it clears up half the confusion. There is no HIPAA certification. HHS says plainly, in its own Security Rule FAQ, that "there is no standard or implementation specification that requires a covered entity to certify compliance." The Office for Civil Rights, which enforces HIPAA, does not certify people, products, or organizations as compliant.

So when a vendor puts a "HIPAA Certified" badge on its site, one of two things is true. Either they mean their software includes the safeguards HIPAA calls for, phrased sloppily, or they're hoping you won't check. A third-party firm might run an attestation or assessment against HIPAA criteria, and that's useful, but it still isn't a government certificate. The honest version of the claim sounds like "we're built to meet the HIPAA Security Rule and we'll sign a BAA," not "we're HIPAA certified." Watch the verb.

This matters because the badge does a lot of unearned work in a buying decision. A busy solo doctor sees "HIPAA compliant," checks the box, and moves on. The safeguards behind the phrase are what actually protect the practice, and those you have to ask about one by one.

## What HIPAA actually requires of your software

HIPAA has two rules that touch your practice management system directly. The Privacy Rule governs when and how patient information can be used and disclosed. The Security Rule governs how electronic patient information is protected. Compliant software is really software that supports both.

The Security Rule organizes its requirements into three safeguard categories, and a serious vendor can speak to all three:

- **Administrative safeguards.** The policies and process side. Risk analysis, workforce training, assigned security responsibility, and access-management procedures. This is the part people forget is software-adjacent, but your PMS vendor's own program lives here.
- **Physical safeguards.** Facility access, workstation use, and device and media controls. For a cloud PMS, this is largely about where the data physically sits and who can reach the servers.
- **Technical safeguards.** The parts that live in the code: access control, audit controls, integrity controls, and transmission security. Encryption and access logging both sit in this bucket.

Notice what's missing from that list: a feature you switch on. HIPAA describes outcomes and controls, not a settings toggle. Two practices can run the same software and one is compliant while the other isn't, because compliance depends on configuration, BAAs, and habits as much as on the product.

## The five things a compliant PMS has to get right

Strip away the jargon and the requirement comes down to five concrete things. Run every practice management vendor against these.

**A signed BAA.** HHS draws the line at access: a software seller isn't automatically a business associate, but a vendor that hosts patient information or reaches it to provide support is. In that case, the practice needs a business associate agreement before the access begins ([HHS software-vendor FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/256/is-software-vendor-business-associate/index.html)). This isn't waived by small practice size. In 2017, OCR settled with a small Illinois practice, the Center for Children's Digestive Health, for $31,000 over a missing BAA with a vendor. One document, a five-figure lesson. Ask for the actual BAA and read it.

**Access controls and audit logging.** Not everyone in the practice should see everything, and the system should record who did. The Security Rule names access control and audit controls as technical safeguards, which in plain terms means role-scoped access plus a log of who viewed, changed, or exported a record and when. If a vendor can't show you what the audit trail captures, that's a gap.

**Encryption in transit and at rest.** In transit means TLS on every connection, 1.2 or newer. At rest means strong encryption on stored records and account data, with AES-256 as the common standard. A vendor that answers "bank-grade security" instead of naming the actual standard is dodging. Get the specifics in writing.

**Breach procedures.** When data is exposed, HIPAA's Breach Notification Rule sets what happens next: notify affected individuals, notify HHS, and in larger breaches notify the media, within defined timelines. Your vendor should have a documented process, not an improvised scramble. Ask what their breach playbook is and how fast they'd tell you.

**Honest certification status.** Since no HIPAA certificate exists, the tell of a trustworthy vendor is how they talk about it. "HIPAA compliant, BAA available" is honest. "HIPAA certified" is not. If they lean on a certificate that can't exist, ask what else they're rounding up.

## The five questions to ask before you sign

You don't need to be a compliance officer to vet a PMS. You need five questions and the patience to make the vendor answer in specifics, in writing.

1. Will you sign a BAA, and can I see it now?
2. What encryption do you use, in transit and at rest, by name?
3. Who on your side can access our patient data, and is that access logged?
4. What is your breach-notification process and timeline?
5. What is your honest certification status?

Picture a two-provider clinic on a Thursday, comparing three quote-only PMS vendors. The one worth trusting answers all five plainly and hands over the BAA. The one to walk away from sends back a brochure with a "HIPAA compliant" badge and no BAA in sight. The questions do the filtering for you.

Patient Square should pass the same test. Patient Square is HIPAA compliant, and BAAs are available to every customer. It uses encryption in transit and at rest with role-scoped, logged access. Request your 7-day trial after you have read the BAA and checked the controls against your own workflow.

## Where we land, honestly

Here's our own posture, because you should hold us to the same standard. Patient Square is an AI clinical platform, and Practice Copilot bundles an AI EHR at the [Copilot plan](/us/pricing/) alongside the scribe. On the compliance front we'll say exactly what's true and nothing more. Our safeguards are HIPAA compliant. We make BAAs available to every customer. We use encryption in transit and at rest, with role-scoped, logged access. Our SOC 2 Type II audit is in progress. We are not "SOC 2 certified" and we are not "HIPAA certified," because neither claim would be honest, and one of them can't exist for anyone.

The scribe module at the center of it captures the visit ambiently and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The compliance posture around all of it is the plain version above, not a badge.

We think honesty on this topic is the whole game. YMYL health content and health software both get judged on whether they overclaim, and a vendor that fudges its compliance status is telling you how it'll handle your data. So we'd rather under-promise the certificate and show you the BAA.

## When a compliance-first enterprise PMS is the better fit

To be fair about it: we aren't the right answer for every practice. If you're a large group or a hospital with a formal vendor-risk program, a procurement team, and a checklist that demands a completed SOC 2 Type II report, HITRUST certification, or a signed security questionnaire before anything moves, an established enterprise practice-management vendor that already holds those artifacts is a cleaner fit than a platform with SOC 2 in progress. That's a real gap and we won't paper over it.

Where a published, honest posture wins is the independent practice that wants to actually understand what it's buying, sign a real BAA, and not get sold a certificate that doesn't exist. If that's you, request your 7-day trial after you have confirmed the safeguards on your own workflow.

## What "compliant" should mean when you shop

Strip the phrase down and "HIPAA-compliant practice management software" means a vendor who'll sign a BAA, applies the Security Rule's administrative, physical, and technical safeguards, controls and logs access, encrypts your data both ways, and has a breach plan. It does not mean a certificate, because none exists. If you take one thing from this: ask the five questions, get the answers in writing, and trust the vendor who names specifics over the one who shows you a badge.

For related reading, our [AI scribe security checklist](../ai-scribe-security-checklist/) runs the same discipline for the documentation layer, and the [BAA and consent guide](../ai-scribe-hipaa-baa-consent/) goes deeper on what a business associate agreement has to contain. If you want the honest number for our own platform, it's on the [pricing page](/us/pricing/).

## Frequently asked questions

The FAQ above covers the recurring ones: whether any PMS is truly HIPAA certified, what compliance actually requires, whether you need a BAA, the three safeguard categories, cloud safety, the questions to ask, and whether audit logs are required. For the fuller vendor-vetting drill, see the [security checklist](../ai-scribe-security-checklist/), then request your 7-day trial when you are ready to test the workflow.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot supports documentation and shipped practice workflows. A new practice can instead use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## Clinical Documentation Software: Note Tool or CDI Platform?
https://patientsquare.com/us/blog/medical-documentation-software/
Published 2026-07-31 · Updated 2026-08-29 · Tags: comparison, scribe, documentation, small-practice

Map templates, dictation, ambient notes, EHR workflows, and enterprise CDI before buying clinical documentation software for a clinic or hospital.

It is a broad buying category. It can mean EHR templates, dictation, ambient note drafting, or an enterprise clinical-documentation-improvement workflow. Those products solve different jobs. Define whether the buyer is a clinician finishing a note or an organization managing documentation quality before comparing vendors.

"Clinical documentation software" can describe a dot-phrase editor bought by one clinician or a hospital program coordinating reviewers, queries, coding, and utilization. Search results put them beside each other. Procurement should not.

First decide who has the problem. Is a clinician trying to finish today's note, or is an organization trying to improve documentation across an enterprise? The answer determines the category.

> **Key takeaways**
>
> - Templates, dictation, and ambient notes help create the encounter record.
> - Enterprise CDI coordinates a larger review and query process. It is not a synonym for an AI scribe.
> - CMS focuses on the completed record: reason, findings, assessment, plan, date, author, and support for submitted codes.
> - Patient Square is a clinician note tool with adjacent practice modules. It is not inpatient CDI, coding, utilization, or RCM software.

## The documentation category map

| Category | Primary user | Input | Output | What it does not prove |
|---|---|---|---|---|
| EHR template or dot phrase | Clinician | Clicks, typed fields, shortcuts | Structured encounter note | Faster work on varied visits |
| Dictation | Clinician | Deliberate spoken narrative | Transcript or dictated note | Visit-level summarization |
| Ambient AI scribe | Clinician | Patient-clinician conversation | Draft structured note | Accuracy, native write-back, or autonomous coding |
| EHR documentation workflow | Clinician and staff | Notes, orders, results, tasks | Signed record and downstream handoffs | Enterprise CDI depth |
| Enterprise CDI | CDI, coding, clinical, quality, utilization teams | Record review and organizational rules | Queries, review worklists, documented clarifications | A faster individual note |

This table is the original buying artifact. It prevents a clinic from paying for an enterprise program it does not need and prevents a hospital from mistaking a note generator for documentation governance.

## Templates are still the right answer sometimes

A good template is fast when visits repeat. Vaccine encounters, routine procedures, and tightly scoped follow-ups can have stable required fields and short clinical variance. The clinician knows the exact language and can reach it with a few shortcuts.

The failure mode is copy-forward clutter and fields that look complete without reflecting the visit. A template trial should include an exception: the patient who does not fit the usual pathway. Record how much old text must be removed and whether required distinctions remain visible.

Templates are often already included in the EHR. If they finish the note cleanly, another subscription has to beat a near-zero incremental price.

## Dictation trades typing for composition

Dictation captures the clinician's words. It is useful when exact wording matters and the clinician can compose a coherent note aloud. Procedure findings, specialist assessments, letters, and short plans can fit well.

The clinician still decides what to say, in what order, and with which detail. A transcript may also need formatting or cleanup. That is not a flaw. It is the trade: high control, less keyboard work, but the cognitive work of composition remains.

Medical transcription adds a human processing layer and different turnaround and billing units. The [AI scribe versus transcription guide](../ai-scribe-vs-medical-transcription-service/) has a buyer-entered crossover model rather than a universal cost claim.

## Ambient software changes the work to review

An ambient scribe listens to the encounter and creates a draft. The clinician reviews, corrects, and signs. It can be a strong fit for narrative visits because the software begins with the conversation rather than a blank note.

That review step is not ceremonial. A draft can omit a negative, combine the wrong history with the plan, mishear a medication or dose, or produce polished language that was never established. CMS tells practitioners that documentation should be complete, legible, attributable, and support the submitted service. The signed record is the evidence, not the model output.

Measure ambient software against the current workflow:

| Trial measure | Baseline | Candidate | Pass rule |
|---|---:|---:|---|
| Minutes from visit end to signed note |  |  | Lower without unsafe corrections |
| Material omissions |  |  | No worse than baseline |
| Unsupported additions |  |  | Zero tolerated |
| Medication or dose corrections |  |  | Investigate every event |
| Formatting repairs after handoff |  |  | Within agreed threshold |
| Unsigned notes at day end |  |  | Lower than baseline |
| Sessions intentionally not recorded |  |  | Workflow still completes |

Averages can hide a dangerous failure. Keep the event log.

There is one more practical check: measure the work that happens after a clinician spots an error. Correct one medication, remove an unsupported sentence, change a heading, and record the amended note. Then make the handoff. The evaluator should be able to answer who changed it, where the old text remains, and how the final version reaches the legal record. A draft that is easy to admire but hard to repair is not saving the clinic time.

## Enterprise CDI is a different purchase

An enterprise CDI program can involve concurrent or retrospective chart review, clinician queries, coding collaboration, quality reporting, utilization work, work queues, escalation, analytics, and audit trails. Exact scope varies by organization and vendor.

That work has several actors and governance questions:

- Who may open, answer, revise, and close a query?
- How is a clarification linked to the record without leading the clinician?
- Which coding, quality, utilization, and denial workflows receive the result?
- How are policy changes versioned and audited?
- Which facilities, specialties, and encounters enter each queue?
- What happens when reviewer and clinician disagree?

A clinic buying a faster note may not need any of this. A hospital running a CDI program cannot replace it with a scribe.

## The handoff ladder

"Works with your EHR" can mean five different things:

1. **Copy and paste:** portable, visible, manual.
2. **Downloaded file:** useful for archive or import if the receiving system accepts it.
3. **Structured export:** fields or resources in a documented format.
4. **Browser or desktop automation:** fewer clicks, but dependent on the target interface.
5. **Native integration:** a supported connection with patient and section mapping.

Ask the vendor to demonstrate corrections as well as the first transfer. A beautiful note sent to the wrong patient is not an integration success.

Patient Square lists EHR-ready export (PDF · HL7 · FHIR). It does not establish a live bidirectional interface, native write-back into every EHR, or certification.

## Where Patient Square fits

Patient Square's AI Medical Scribe returns a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Audio is processed in memory and discarded when the note is drafted. Scheduling begins on Assist. Copilot adds the bundled AI Copilot EHR and WhatsApp.

Public US annual monthly equivalents are $79 for Assist, $119 for Copilot, and $199 for Autopilot. Month-to-month prices are $99, $149, and $249. All plans list unlimited visits and notes.

The product boundary is just as important:

- ICD-10 suggestions are not a coding engine;
- the prescription draft is not pharmacy transmission;
- export is not universal native write-back;
- the public pages do not name inpatient CDI, clinical queries, utilization management, DRG, denials, or full RCM.

Patient Square can be tested as a clinician documentation workflow. It should not be shortlisted as an enterprise CDI platform.

For a smaller practice, the deployment question is usually simpler. Keep the incumbent EHR when it already owns the clinical record and the clinic wants a documentation workflow beside it. Use the bundled AI Copilot EHR from the Copilot tier only after the practice has evaluated the record path it needs. The public product surface supports both paths. It does not fill in the EHR modules a buyer has not seen.

## What a clean decision record looks like

After the trial, write a one-page decision record instead of relying on collective memory. Name the current workflow, the candidate category, the visits tested, the correction events, the handoff target, and the signed-record result. Include the subscription and any required implementation work. If the tool is rejected, state why. That makes the next evaluation faster and gives the clinic a baseline when the workflow changes.

The final question is plain: did the candidate remove enough composition work to justify the new review and handoff work it introduced? A template, dictation tool, ambient scribe, EHR workflow, or CDI platform can each be the right answer. They are not interchangeable just because they all touch a clinical note.

## A practical trial has two clocks

One clock starts when the visit ends. Track the minutes until the clinician can sign a complete record. The other starts when that record moves to its next system. Track the time and repair work until the right chart contains the right version. A tool can win the first clock and fail the second. That is why a short, clean ambient draft is not enough evidence by itself.

Run at least one routine visit and one awkward visit. The awkward one might include a medication change, an uncertain history, a late clarification, a refusal to record, or a correction after handoff. Record the original draft, the final signed note, and every human intervention. Do not score a tool solely on the polished note it produced during a sales presentation.

The result separates category fit from vendor preference. Templates usually win the first clock for a stable, repetitive service. Dictation can win when the clinician needs deliberate wording. Ambient drafting earns its place when it reduces composition work without adding dangerous corrections. A CDI platform is justified only when the organization has the separate review and query operation to run.

## Choose the category before the vendor

Use templates when repeatability and exact fields already solve the job. Use dictation when clinician-authored wording is the priority. Trial ambient software when conversational visits create composition work. Procure enterprise CDI only when the organization needs the multi-role review and query system.

The [medical scribe software guide](../medical-scribe-software-for-clinics/) compares output, review, retention, and handoff across note tools. The [any-EHR export guide](../ai-scribe-any-ehr-export/) goes deeper on portability. Request your 7-day trial when you have a defined signed-record test.

## Patient Square and your existing record system

Practice Copilot can use the bundled AI Copilot EHR from the Copilot tier, or work alongside an existing EHR. Neither path promises automatic filing or write-back into a third-party EHR.

---

## AI Scribe for Medical Notes: How It Works
https://patientsquare.com/us/blog/ai-scribe-for-medical-notes/
Published 2026-07-30 · Updated 2026-08-27 · Tags: ai-scribe, ambient-documentation, buyers-guide, scribe

How an AI scribe turns a visit into a SOAP note, ICD-10 suggestions, and an Rx draft, plus the six criteria that separate the real tools from demo-ware.

It captures the visit conversation ambiently, transcribes the speech to text, then a language model organizes that transcript into a structured SOAP note. Good tools also draft downstream pieces like ICD-10 suggestions and a prescription draft. You review and sign; nothing enters the chart on its own.

An AI scribe for medical notes listens to the visit, transcribes it, and drafts a structured note you review and sign. Under the hood it runs a short pipeline: ambient capture, then speech-to-text, then a language model that shapes the transcript into a SOAP note. The better tools add ICD-10 suggestions and a prescription draft. What each tool lists on its [pricing page](/us/pricing/) is the ceiling, so read it literally.

That's the mechanism. The part that actually decides whether a tool earns a place in your clinic is what happens after the draft appears, so most of this page is about the six things worth checking before you sign.

> **Key takeaways**
>
> - An AI scribe runs four steps: capture, transcribe, structure into a SOAP note, then you review and sign. The draft lands about 2 minutes after the visit.
> - Beyond the note, good tools return ICD-10 suggestions and a prescription draft, all draft-only until a clinician signs.
> - Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit, which is the burden these tools target.
> - Six criteria separate the field: note quality, edit burden, EHR export, language coverage, security and BAA, and price.

## How does an AI scribe turn a visit into a note?

Four steps, and all of them happen during or right after the appointment.

It listens first. You open a session on your phone or laptop, get the patient's consent, and run the visit like you always do. The scribe captures the conversation ambiently. Nobody dictates.

Then it transcribes. Speech becomes text in near real time. The solid systems handle two speakers, interruptions, and the way a real consult loops back on itself. The hard case is a full room with a relative answering half the questions in an accent the model hasn't heard much of.

Next it structures the transcript. A language model reads the text and sorts it into subjective, objective, assessment, and plan. This is where products split. Some stop at the note. Others draft the pieces around it too.

Then you read it and sign. The draft shows up about two minutes after the visit ends. You fix what's wrong, add what the room didn't say out loud, and sign. Nothing reaches the chart without you.

Here's the canonical version of that flow, the way our tool does it. AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. If you want to watch it run on a real visit type, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring your own note format.

## What does the AI actually hand back?

Baseline for any credible product is one thing: a structured note. Past that, read the feature list closely, because "scribe" gets stretched to cover a lot.

Some tools give you the SOAP note and stop there. Others draft the downstream artifacts. AI Medical Scribe by Patient Square returns ICD-10 code suggestions and a prescription draft with the note. Two things to be clear about, because vendors blur them. Those ICD-10 codes are suggestions for you to confirm, not a coding engine that finalizes billing. The prescription is a draft for you to review, not an order that transmits to a pharmacy. The clinician stays the author of every one.

That draft-only line is the honest one. A tool that claims to code the chart or send the script by itself is either overselling or building something you shouldn't want. The point of the review step is that a draft a model wrote is still a draft a model wrote.

## The six criteria that actually separate AI scribes

Every vendor demo looks good on a quiet, scripted visit. The differences show up on a 14-patient Tuesday. These are the six things worth pressure-testing before you commit, and the honest questions to ask about each.

**Note quality** is first because it's the whole job. A clean draft on a single-speaker consult is table stakes. Ask to see the tool run on your messiest visit type, not the vendor's tidy demo script. Read a real note it produced end to end.

**Edit burden** is the criterion buyers skip and regret. A tool that drafts a note you then rewrite from scratch hasn't saved you anything. The goal is review-and-sign, where you correct a line or two and move on. Time yourself editing three real drafts during a trial.

**EHR export** decides whether the note gets where it needs to go. Some vendors write into named EHRs; others hand you a file. We offer EHR-ready export in PDF, HL7, and FHIR on every plan, so the note leaves in a format your record system accepts. Note that's an export, not a certified two-way interface. Ask each vendor exactly what "integrates with your EHR" means, in one sentence.

**Language coverage** is where "multilingual" marketing goes to die. Read the language list literally, then test it on your own patients. We capture English and more languages and always return the note in clean clinical English.

**Security and BAA** is non-negotiable for PHI. The floor is a signed BAA plus encryption in transit and at rest. We maintain HIPAA compliant safeguards, offer a BAA to every US customer, and don't store the audio: it's processed in memory and discarded once the note is drafted. Our full posture is on the [security page](/us/security/). No vendor is "HIPAA certified," because no such certificate exists; treat that phrase as a red flag.

**Price** should be on a page, not behind a sales call. Published US scribe pricing runs roughly $39 to $199 per clinician per month, and several big names publish nothing. We think a per-clinician software subscription that hides its price tells you how the renewal will go. Ours starts at $79 per clinician per month on the annual Assist plan, with unlimited visits and notes.

For a deeper version of this checklist, our guide on [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) walks through the trial itself. And [SOAP note quality](../ai-scribe-soap-note-quality/) covers what a good draft should and shouldn't get right.

## When is a human scribe or a template the better fit?

We'll be straight about this, because a scribe isn't the answer for every visit.

A human scribe still wins in a few cases. If the visit is chaotic enough that a person needs to interpret it live, a trauma bay or a packed OPD with three people talking, a trained human in the room reads the situation in a way software doesn't yet. If your patients won't consent to any recording, a human writing from observation may be the only path. The trade is cost: a human scribe is a salary plus hiring and turnover, and it scales one clinician at a time.

A template-only tool can be the better fit too. If your notes are short and repetitive, say a dermatology follow-up you already document in 40 seconds with a macro, an ambient scribe is solving a problem you don't have. Smart templates and quick-text are cheaper and faster for that pattern. The math flips the moment your notes are long, variable, and piling up after clinic. Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit, per a 2023 JAMA Network Open study; that's the exact burden an ambient scribe targets, and a template doesn't.

So the honest verdict: pick the human scribe for the hardest, non-recordable rooms, pick the template for short repetitive notes you already write fast, and pick an AI scribe when the after-hours charting is the real problem. If that last one is you, [see what's on each plan](/us/pricing/) before you shortlist anything.

## What the AI scribe still can't do for you

Worth saying plainly, since honest limits are how you judge a vendor.

Drafts contain errors. Models mishear medication names, occasionally merge two complaints, sometimes write something plausible that didn't happen. The review step is load-bearing for exactly that reason. Distrust any pitch that implies you can skip reading the note.

Noisy rooms are still the hard case. A quiet consult is easy; a crowded clinic with a caregiver answering half the questions is where transcription quality varies most across products. Test your real patient mix, not the demo's.

And the chart stays yours. No scribe, software or human, moves the documentation responsibility off the signing clinician. The ICD-10 codes are suggestions you confirm. The prescription is a draft you decide on. A good tool makes those decisions faster and better documented. It doesn't make them for you, and you wouldn't want a tool that did. If you want to see where those lines sit in practice, our [audio-retention explainer](../ai-scribe-audio-retention/) covers what happens to the recording, and the [pricing page](/us/pricing/) lists exactly what ships on each plan today.

## Frequently asked questions

The FAQ above covers the recurring questions: how the note gets written, whether the draft is accurate enough to trust, whether it reaches your EHR, what else it hands back, what happens to the audio, when a human or template fits better, and what it costs. For the full plan breakdown, see the [pricing page](/us/pricing/), then <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> for your visit types.

---

## Best EMR for Mental Health Practices (2026 Roundup)
https://patientsquare.com/us/blog/best-emr-for-mental-health/
Published 2026-07-30 · Tags: comparison, behavioral-health, ehr, pricing, scribe

An honest roundup of mental health EMR software: ICANotes, TherapyNotes, and SimplePractice compared on price, templates, billing, and where an AI scribe fits.

There's no single winner; it depends on whether you prescribe and how much you bill insurance. ICANotes tends to win for prescribers who want deep psychiatric templates and EPCS. TherapyNotes tends to win for insurance-heavy therapy practices. SimplePractice tends to win for private-pay solo clinicians who run everything from their phone.

There's no single best EMR for mental health, and any roundup that names one is selling you something. The real answer forks on two questions: do you prescribe, and how much of your money comes from insurance. Prescribers who want deep psychiatric templates lean ICANotes. Insurance-heavy therapy practices lean TherapyNotes. Private-pay solo clinicians lean SimplePractice. Below we compare the field honestly, then draw the line we're straight about: we make a scribe, not an EMR, and we'll tell you exactly where that fits. Start with the [pricing page](/us/pricing/) if you just want a number.

> **Key takeaways**
>
> - The choice forks on prescribing and payer mix. Prescribers lean ICANotes; insurance-heavy therapy leans TherapyNotes; private-pay leans SimplePractice.
> - Non-prescribing therapy plans run $49 to $99 a month; ICANotes' full-time prescribing plan is listed at $213 a month plus a $99 activation fee.
> - ICANotes and TherapyNotes are ONC-certified; SimplePractice is not on the ONC list, which matters for interoperability incentive programs.
> - An EMR stores your note. A scribe writes the first draft. Many practices run both, and that's a feature, not a failure.

## How should a mental health practice actually pick an EMR?

Start with two facts about your own practice before you read a single feature list. First: do you or your clinicians prescribe? A psychiatrist writing controlled substances needs EPCS and drug-interaction checking; a talk-therapy practice never touches that workflow. Second: what share of your revenue runs through insurance? A claims-heavy group has different needs than a cash-pay counselor who never files.

Those two answers sort the field fast. If you prescribe, ICANotes is built for you: integrated controlled-substance e-prescribing, psychiatric templates, and screeners like the PHQ-9 and GAD-7 wired in, per EHR Source's 2026 review. If you're insurance-heavy but non-prescribing, TherapyNotes carries ONC certification and a claims-first design. If you're private-pay and solo, SimplePractice's app and workflow tend to win the day.

We think most buyers skip these two questions and go straight to a demo, then wonder why the "affordable" EMR feels wrong three months in. Answer them first. It saves a migration.

## What do the leading mental health EMRs actually cost?

Here's the honest table. Figures come from each vendor's pricing page or a 2026 EHR Source review, fetched in July 2026. Rates change and quotes vary by practice size, so confirm before you commit.

A few things the table can't say out loud. SimplePractice's $49 Starter is the lowest headline number, but it omits insurance billing and the telehealth most practices need, so your real entry tier is Essential at $79 or Plus at $99, per its pricing page. TherapyNotes folds more of the clinical and billing core into its $69 base plan, but bills claims at $0.14 each or $65 a month for unlimited, per EHR Source. ICANotes prices by role: a part-time notes-only plan starts at $35, non-prescribing full-time runs $75, and full-time prescribing is $213 with a one-time $99 activation fee, per its pricing page.

## Which mental health EMR wins for prescribers versus therapists?

This is where an honest roundup earns its keep, so here are the concessions plainly.

**When ICANotes is the better fit:** you prescribe. If you're a psychiatrist or a psychiatric NP writing controlled substances, ICANotes' integrated EPCS, medication management, and psychiatric-specific templates are a real advantage that a talk-therapy EMR can't match. Its 2-to-5-minute menu-driven note assembly and built-in screeners were designed for exactly this work. The full-time prescribing price is steep at $213 a month, but for a prescriber it's buying a workflow, not just a chart.

**When TherapyNotes is the better fit:** you bill insurance heavily and don't prescribe. It's ONC-certified, its documentation and claims are built for behavioral-health billing, and the $69 solo base plus $0.14-a-claim model is predictable for a practice that files a lot. If more than 60 percent of your revenue is insurance, the billing edge usually points here.

**When SimplePractice is the better fit:** you're private-pay and you run your practice from your phone. It has one of the strongest mobile apps in the category and a clean solo workflow. The catch worth knowing: SimplePractice isn't on the ONC Certified Health IT Product List, which the EHR Source review notes "disqualifies practices from Promoting Interoperability incentive payments." For a cash-pay practice that never touches those programs, that's a non-issue.

Notice what none of these three do well: they store your note, they don't write it. That's the gap the next section is about.

## What about the documentation burden itself?

This is the part every EMR roundup skips, and it's the part that eats your evenings. A behavioral-health note isn't a checkbox. DAP notes, BIRP notes, treatment plans, progress notes tied to goals and interventions: that's still you, typing, often after the last client leaves at 6pm on a full Tuesday.

The EMR is where the note lives. It is not, by itself, what writes the note. Two of the three vendors here now sell an AI note-taker as an add-on, SimplePractice's Note Taker at $35 a clinician and ICANotes' AI Scribe at $49 a user, because they know the documentation load is the actual pain. That's a fair path if you want one vendor and one bill.

The other path is a standalone scribe that drafts the note and works alongside whichever EMR you keep, so you're not locked into one vendor's note quality. Neither path is wrong. One bill, or the better draft. That's the real trade.

## Where does an AI scribe fit for a mental health practice?

Right at that documentation layer, and we'll be precise about the boundary. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For a mental health clinician that means a drafted DAP or BIRP note waiting two minutes after the session ends, not a blank template staring at you at 9pm.

Here's the line. If you already run ICANotes, TherapyNotes, or SimplePractice, the scribe doesn't rip it out; it drafts the note and you keep your existing chart, scheduling, and billing where they are. The ICD-10 output is suggestions, and the prescription output is a draft you review, not e-prescribing that transmits to a pharmacy. Audio is processed in memory and discarded once the note drafts, so there's no recording archive, and the notes belong to your practice to export or delete anytime. We don't quote an accuracy percentage, because no honest vendor can. What we do is write the first draft well enough that the note stops outlasting the session.

There's a second option worth naming if you're a two-provider clinic tired of stitching tools together. On our Copilot plan, the scribe comes with a bundled AI EHR at $119 per clinician per month on the annual plan, price published, no quote. That's one number for the note-drafting and the record system, and it's on the [pricing page](/us/pricing/) to read without a sales call.

## So what should you actually do?

Pick the EMR by your two answers. If you prescribe, price ICANotes and expect to pay for the prescriber workflow. If you're insurance-heavy therapy, price TherapyNotes and confirm the per-claim math. If you're private-pay solo, try SimplePractice and check whether ONC certification matters for your programs. Then decide the note separately: an add-on inside your EMR, a standalone scribe alongside it, or a bundle that carries both.

If you want to see the split in your own day, the [best EHR for therapists](../best-ehr-for-therapists/) comparison goes deeper on the SimplePractice-versus-TherapyNotes billing decision, and the [AI scribe for behavioral health](../ai-scribe-for-behavioral-health/) page walks the DAP and BIRP workflow session by session. When you're weighing privacy specifically, the [AI scribe for psychiatry](../ai-scribe-for-psychiatry-privacy/) page covers what gets stored and what doesn't. Or book a short demo and bring your current EMR; the question is never which tool replaces it, but which one finally writes the note. The [security page](/us/security/) has the compliance detail if that's your first question.

---

## Medical Scribe Software for Clinics: 2026 Buyer's Guide
https://patientsquare.com/us/blog/medical-scribe-software-for-clinics/
Published 2026-07-30 · Updated 2026-08-29 · Tags: scribe, buyers-guide, small-practice, comparison

How to pick medical scribe software for a multi-provider clinic: what to require, how to price seats, how to roll it out, and when a solo tool fits better.

It captures or accepts the encounter, produces a draft clinical note, gives the clinician a review step, and moves the signed result into the record. A clinic buyer must also verify retention, account ownership, offboarding, pricing by active clinician, and the exact handoff into its EHR. Those operating details vary by vendor.

Medical scribe software turns an encounter into a draft note for clinician review, then hands the reviewed result to the record. A clinic has four separate decisions: what comes out, who reviews it, how long the vendor keeps data, and how the note reaches the chart. Account ownership, offboarding, and seat pricing come next. Don't assume the word clinic guarantees any of them.

> **Key takeaways**
>
> - Separate output quality from the operating workflow around it. A polished draft can still fail on review, retention, or chart handoff.
> - Make the vendor demonstrate account ownership, offboarding, export, and price for every clinician type you plan to activate.
> - Price the exact tier and active seats you will use. Public rates and quote-only contracts aren't comparable until limits and renewal terms are written down.
> - Start with a one-week failure log on real visits. Expand only after clinicians can repeat the review and handoff without guesswork.
> - A solo-only tool or a human scribe service is the better fit in specific cases. We name them below.

## What does "clinic-scale" actually change about scribe software?

Not the medical-content standard. CMS still expects a complete, legible record with the reason for the encounter, relevant findings, assessment, plan, date, and identifiable author ([CMS E/M guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)). What changes at clinic scale is the number of people who must repeat the capture, review, handoff, and offboarding process without inventing private workarounds.

Picture a five-provider family clinic on a 14-patient Tuesday. Each provider walks out of every visit with a chart to finish. The documentation problem is the same one a solo doctor has, times five, and it shows up in the same place: the AMA, reporting a 2022 JAMA Network Open study, found primary-care physicians spent about 36 minutes on the EHR per 30-minute visit, roughly 6 of those minutes as after-hours "pajama time" ([Rotenstein et al., JAMA Network Open, 2022, via AMA](https://www.ama-assn.org/practice-management/digital-health/primary-care-visits-run-half-hour-time-ehr-36-minutes)). Five providers, five evenings.

So the draft is only one part of the buy. Who owns the account? What happens when a provider joins in March and leaves in September? Where do encounter artifacts live, and what gets deleted? How does a reviewed note reach the chart? A vendor may handle these well, poorly, or not at all. The clinic has to collect the answer instead of filling the blank with hope.

## What should a clinic require from scribe software?

Start with four evidence packets. A clinic shouldn't sign without them.

- **Output and review evidence.** Mark up ten difficult notes. Record omissions, invented details, and minutes to sign. A clean demo note proves almost nothing.
- **Retention and deletion terms.** Ask separately about audio, transcript, draft, signed note, support logs, and backups. Get the cancellation behavior in writing.
- **Handoff proof.** Move one reviewed note into the real chart. Patient Square describes its output as “EHR-ready export (PDF · HL7 · FHIR).” That is an export claim, not certified interoperability or native write-back.
- **Clinic controls and cost.** Ask the vendor to show account ownership, roles, offboarding, active seats, one sample invoice, and renewal terms. If a capability isn't shown, treat it as absent from the decision.

Our opinion: the failure log and handoff test expose more than any feature grid. If the vendor can't answer these four packets, the clinic isn't ready to buy it.

## How much does clinic scribe software cost across N providers?

Many ambient AI scribes price per clinician per month; others offer a free eligible tier or a sales quote. For a clinic, the unit, usage limit, add-ons, renewal term, and meaning of an active seat all matter.

Patient Square publishes $79 per clinician per month on the annual Assist plan; the Copilot plan adds a bundled AI EHR and WhatsApp messaging at $119, and Autopilot is $199 with an AI receptionist and follow-ups ([Patient Square US pricing](/us/pricing/)). Freed publishes its own tiers ([Freed pricing](https://www.getfreed.ai/pricing)). Don't turn those two examples into a market average. Put every finalist's live rate and contract terms into the same worksheet.

Two things move the clinic number:

1. **Active seats, not headcount.** A part-time provider who documents 20 notes a month may still cost a full seat. The contract controls. Model your bill on seats you will actually turn on, and ask whether a low-volume clinician can sit on a cheaper tier.
2. **What's bundled changes the comparison.** A $79 scribe-only seat and a $119 seat that includes an EHR aren't the same purchase. When you compare vendors, line up what each seat contains, not just the number.

For the per-clinician version of this math and a longer pricing walk-through, the [scribe pricing breakdown](../ai-medical-scribe-pricing/) covers the solo case in detail, and the [group-practice per-seat guide](../ai-scribe-for-group-practice/) works the multi-provider contract questions.

## How do you roll scribe software out across a whole clinic?

Stage it. Run a one-week pilot first, study the failures, then decide whether another specialty or clinician should join. Buying seats for everyone on day one is how a rollout stalls quietly.

Here's the order we'd run it in a five-to-fifteen-provider clinic. The full rollout may be quick or may take months; integration, contracting, and the failure rate decide.

- **Week one: pilot 3 to 5 providers on real visits.** Not a demo, real Tuesdays. The pilot finds the note-quality quirks and the specialties where the draft needs more editing. A sales demo won't.
- **Standardize one note structure.** Pick a shared SOAP order so a covering provider can open a colleague's chart at 7pm and find the plan where they expect it. Let clinicians edit within it; don't let every provider invent a private format.
- **Set ownership and billing before you scale.** Decide who owns the vendor account, how active seats are counted, who approves access, and how a departing clinician is removed. Make the vendor demonstrate each control it actually provides.
- **Add the rest in a staged wave.** Bring on another specialty or small group only after the first group can capture, review, and hand off a note without private instructions.

The [small-clinic rollout plan](../ai-scribe-implementation-small-clinic/) walks a two-week version of this step by step if you want the day-by-day version.

## When is a solo-only tool or a human scribe the better fit?

Two honest cases where clinic-scale AI software is the wrong buy.

**A genuinely solo practice.** If you're one clinician with no plans to add providers, the clinic admin layer is overhead you'll never use. A solo-tier scribe with a single account is cleaner and often cheaper. The [solo pricing breakdown](../ai-medical-scribe-pricing/) is the right starting point; skip the multi-provider machinery entirely.

**A clinic with unusually complex visits, or a provider who wants a person.** A human scribe service puts a trained person on the documentation, live, and some clinicians strongly prefer that for high-complexity encounters. The tradeoff is cost and turnover: a human scribe is a recurring salary or contract, and scribes leave, so you re-hire and re-train. The [AI-versus-human cost and turnover math](../ai-scribe-vs-human-scribe-cost/) lays out both sides. For most multi-provider clinics chasing steady per-seat cost with no staffing churn, AI software wins. For a few, the human fit is real, and we'd rather you buy the right thing.

## Where Patient Square fits for a clinic

The AI Medical Scribe by Patient Square is one module of Practice Copilot. It captures the visit and returns a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Scheduling starts on Assist; the Copilot tier adds the bundled AI Copilot EHR and WhatsApp messaging. These are plan claims, not proof of a particular clinic's admin or EHR write-back needs.

The public rate is per clinician: $79 per month on the annual Assist plan, or $119 on Copilot. Every plan includes unlimited visits and notes, no per-note metering, and EHR-ready export (PDF · HL7 · FHIR). The site doesn't claim native write-back to every third-party EHR. A clinic should still ask us to demonstrate account ownership, offboarding, and the exact handoff it intends to use.

If you're evaluating for a multi-provider clinic, request your 7-day trial and do the seat math yourself. Run the same visit types through the failure log, then decide whether the demonstrated controls and handoff fit your clinic.

## Bottom line on clinic scribe software

The clinic decision has four parts: output, review, retention, and handoff. Prove those first. Then verify account ownership, offboarding, price, and renewal terms. A one-week failure log gives you more useful evidence than a big launch and a stack of seats.

If you're truly solo, buy the solo tool. If your visits are unusually complex and you want a person, price a human scribe honestly. For clinics that want to test steady per-provider cost and less time spent writing notes, request your 7-day trial and compare finished notes on a real clinic week.

## Frequently asked questions

The FAQ above covers the recurring ones: what clinic scribe software is, what it costs across providers, the four things to require, the AI-versus-human call, EHR export, rollout time, and non-physician use. For the full plan detail, the [pricing page](/us/pricing/) has every tier. Request your 7-day trial when you are ready to test the scribe on your clinic's real note types.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot supports documentation and shipped practice workflows. A new practice can instead use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## Types of EMR Systems, Explained for Practice Buyers
https://patientsquare.com/us/blog/types-of-emr-systems/
Published 2026-07-30 · Updated 2026-08-27 · Tags: emr, ehr, guide, small-practice

The main types of EMR systems: cloud vs server-based, specialty vs general, standalone vs all-in-one, certified vs not, and AI-native, for practice buyers.

EMR systems sort along a few axes: deployment (cloud-based versus on-premise server), scope (specialty-specific versus general-purpose), packaging (standalone EMR versus all-in-one with practice management), and certification (ONC-certified versus non-certified). A newer category is the AI-native EMR that builds ambient documentation into the record itself. Most real products are a mix, like a cloud, ONC-certified, all-in-one built for primary care.

If you're shopping for an EMR, the types sort along four practical axes: how it's hosted (cloud versus on-premise server), who it's built for (specialty-specific versus general), how it's packaged (standalone record versus all-in-one with scheduling and billing), and whether it's ONC-certified. A newer fifth type, the AI-native EMR, writes the note as you talk. Most real products mix these. Our [pricing page](/us/pricing/) shows one example: a cloud, all-in-one, AI-native record.

> **Key takeaways**
>
> - There are 5 useful ways to sort EMR systems: deployment, specialty scope, packaging, certification, and AI-native.
> - Cloud versus on-premise is the first fork; most new small practices pick cloud to skip the server, the upfront hardware cost, and the in-house IT load.
> - ONC certification is voluntary but required if you bill Medicare or Medicaid Promoting Interoperability programs.
> - AI-native is the newest category: it drafts a structured note during the visit instead of after hours.

Most "types of EMR" articles get one thing backwards. These aren't five separate product shelves you pick one from. They're five questions you answer about the same product. A single EMR is a point on all five axes at once: a cloud-hosted, general-purpose, all-in-one, ONC-certified, AI-native system is one product that happens to answer every question. So read this as a checklist for a demo, not a menu.

## Cloud-based vs on-premise: the deployment fork

This is the first decision and it shapes most of the others. A cloud-based EMR runs on the vendor's servers. You open a browser, log in, and the vendor handles hosting, backups, security patches, and updates. You pay a monthly or annual subscription per clinician. Nothing lives on a box in your closet.

An on-premise (server-based) EMR runs on hardware you buy and keep in your office. You own the server, the database, the updates, and the backups, usually with an IT person or a contract to keep it healthy. The upfront cost is larger, but some practices like owning the infrastructure outright and keeping data physically in-house.

For a two-provider clinic opening this year, cloud almost always wins on setup burden. There's no server to size, no on-site IT, and updates arrive without a maintenance window. On-premise still makes sense for a small set of practices, mostly larger groups with existing IT staff, unusual data-residency rules, or a deep distrust of anyone else touching the servers.

One myth to kill: cloud does not mean less secure. A well-run cloud EMR encrypts data in transit and at rest, logs every access, and signs a Business Associate Agreement with you. Ask for those specifics either way. The word "cloud" tells you where the servers are, not how safe they are.

## Specialty-specific vs general-purpose EMR

The second axis is who the EMR was built for. A specialty-specific EMR ships with the templates, note structures, and order sets that one field actually uses. A dermatology EMR expects lesion diagrams and procedure notes. A behavioral-health one expects therapy notes and treatment plans. Because the charting already matches the specialty, you spend less time configuring and more time seeing patients.

A general-purpose EMR aims to fit many specialties. It's more flexible and usually cheaper per seat, but you often build out your own templates before it feels native to your work. That's fine if your documentation is straightforward or if you have someone willing to configure it.

There's a middle path worth knowing about. Some general systems ship specialty-aware templates ready out of the box, so you get a head start without buying a niche product locked to one field. If you run a multi-specialty group, that middle path often beats stitching together several single-specialty systems. We wrote a longer take on picking one in our [honest roundup for small practices](../best-emr-for-small-practice/).

## Standalone EMR vs all-in-one: how it's packaged

The third axis is scope of the software itself. A standalone EMR is the clinical record and little else. It stores charts, notes, problem lists, and results. You then pair it with separate scheduling software, a separate billing or clearinghouse tool, and maybe a separate patient-messaging product. More vendors, more logins, more bills, but you get to pick a best-in-class tool for each job.

An all-in-one platform bundles the record with practice management, scheduling, and often patient communication under one login and one invoice. For a lean practice, that's usually the easier life: one vendor, one support line, one thing to learn. The trade-off is you take the bundle's version of each piece rather than shopping each one separately.

Which is right depends on what you already own. If you have a billing service you trust and a scheduler your front desk loves, a standalone record that plays nicely with them can be cleaner. If you're starting fresh or tired of juggling four tabs, all-in-one usually wins. Either way, watch for the fees that stack: setup charges, per-user fees, and separately-billed add-ons. Our [EMR cost breakdown](../emr-system-cost-guide/) walks through where the money actually goes.

## Certified vs non-certified EMR systems

The fourth axis is certification, and it's the one buyers most often misread. ONC certification means the EMR met criteria under the federal Health IT Certification Program. Per ASTP/ONC, that program is voluntary: it's a formal, third-party conformity check, not a legal requirement to sell or use an EMR.

So why does it matter? Because certain federal programs require it. The Medicare and Medicaid Promoting Interoperability programs (the successors to Meaningful Use) require the use of certified health IT to participate and avoid payment adjustments. If you bill Medicare and take part in those programs, you need a certified system. Full stop.

If you don't, the calculus changes. A cash-pay concierge practice, a direct-primary-care clinic, or a cosmetic derm office that isn't in those programs can run a non-certified system without penalty, and often does. We think buyers over-weight the certification badge when it doesn't apply to their billing mix. Certification is a real signal of interoperability rigor, but it answers a specific regulatory question. Ask yourself whether that question is yours before you pay a premium for it.

## AI-native EMR: the newest category

The fifth type is recent enough that most roundups don't list it yet. An AI-native EMR builds ambient documentation into the record instead of bolting a separate scribe on top. Rather than you dictating into a scribe app and then copying the note into a different EMR, the system listens during the visit, drafts the structured note, and it lands in the same chart you already work in.

The distinction is where the AI sits. A bolt-on scribe produces text you paste somewhere else. An AI-native EMR treats the drafted note as a first-class part of the record. For a clinician finishing charts at 8pm, that's the difference between "the note is written and in the chart" and "I still have to move it."

Because this category is new, look closely at what the AI actually does and where it stops. A good ambient tool drafts the SOAP note and suggests codes; it should not claim to make final coding or billing decisions for you. If you want the full picture on that boundary, we broke it down in [how ICD-10 suggestions work](../ai-scribe-icd-10-suggestions-explained/).

This is the category we build in. Patient Square is an AI clinical platform: Practice Copilot brings the whole practice under one AI copilot, and the AI Medical Scribe is one module of it, listening during the visit and handing back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On our Copilot plan it comes with a bundled AI EHR, so the note is drafted and filed in one place. That's what "AI-native" looks like in practice.

## The types of EMR systems, side by side

Here's the whole picture in one table. Read each row as a question to answer for your own practice, not as five boxes to pick between.

## When another type is the better fit for you

We'll be straight about this. An AI-native, cloud, all-in-one EMR is not the right answer for every practice, and pretending otherwise would be useless.

If you're a hospital-owned group running Epic or Cerner, your record is chosen for you, and the real question is which ambient tool exports or works alongside it, not whether to replace the EMR. If your practice is deep into a Medicare Promoting Interoperability program and needs specific certified capabilities, start with the certification list and work backward. And if you already run billing and scheduling software your team likes, a standalone certified record that connects to them cleanly may beat swapping everything for a bundle.

Our bias is toward cloud, all-in-one, and AI-native because that's the shortest path to less after-hours charting for a small independent practice. But the right type is the one that matches your billing mix, your specialty, and the tools you already can't live without. Pick the axes first, then pick the product.

## Where to go from here

You now have the five questions: cloud or on-premise, specialty or general, standalone or all-in-one, certified or not, and AI-native or not. Take them into any demo and you'll cut through a lot of sales language fast.

If you want to see what a cloud, all-in-one, AI-native record feels like on your own visits, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and we'll run the scribe on real note types. The [pricing page](/us/pricing/) has the numbers up front, no sales call needed to read them.

## Frequently asked questions

The FAQ above covers the recurring ones: the main types, the cloud-versus-on-premise difference, what specialty-specific and AI-native mean, what ONC certification is for, and how to choose between standalone and all-in-one. For a deeper look at cost across types, see the [EMR cost guide](../emr-system-cost-guide/).

---

## AI Scribe vs Note Templates: When Structure Helps or Hurts
https://patientsquare.com/us/blog/ai-scribe-note-templates-vs-freetext/
Published 2026-07-29 · Tags: ai-scribe, note-templates, dot-phrases, clinical-documentation, physician-workflow

Dot phrases and SmartPhrases speed some visits and flatten others. Here is when templates fit, when ambient free-narrative capture wins, and how they coexist.

No. Templates are excellent for repetitive, structured visits where the same fields recur. An ambient scribe is stronger for narrative, variable visits. The honest answer is that each fits a different kind of encounter, and many clinicians use both.

Dot phrases, SmartPhrases, and note templates are fast when the visit is repetitive and slow, or worse, distorting, when it is not. An ambient AI scribe drafts the note from the actual conversation, which fits narrative and variable visits better than a rigid template does. This is not a fight where one tool wins. Templates and ambient capture solve different problems, and most clinicians end up using both. Patient Square returns a structured SOAP note about two minutes after the visit, which you then review, edit, drop your usual phrases into, and sign.

> **Key takeaways**
> - Templates fit repetitive, structured visits; ambient capture fits narrative, variable ones.
> - An ambient scribe drafts from the conversation, so it reduces template fatigue on complex visits.
> - Patient Square returns a structured SOAP note, not raw free text.
> - You can still use dot phrases and SmartPhrases inside the drafted note; the tools coexist.
> - You review, edit, and sign every note, and legal responsibility for the record stays with you.

_Source: audio handling described on the [security page](../../security/)._

## What templates are good at

Templates earn their reputation on the right visits. A well-controlled diabetes follow-up, a routine post-op check, a sports physical: the same fields recur, the structure is stable, and a dot phrase fills most of the note in a keystroke. For those encounters, a template is fast and consistent, and consistency has real value for quality reporting and for the next clinician reading the chart.

The strength is repetition. When the shape of the visit is known in advance, a template encodes that shape once and reuses it forever. You are not composing a note; you are confirming a form. That is efficient, and dismissing it would be wrong.

Templates also enforce completeness on visits that need it. If a protocol requires five specific fields, a template makes you fill five specific fields. That is a feature, not a bug, when the protocol is the point.

## Where templates start to hurt

The trouble starts when the visit does not match the form. A patient comes in for a knee, then mentions their spouse died last month and they have not been sleeping. A template built for the knee has nowhere to put the part of the visit that mattered most. So you either force it into an ill-fitting field or drop it, and neither serves the record.

This is template fatigue: tabbing through blanks that do not fit, deleting boilerplate that does not apply, wrestling a rich conversation into a rigid frame. It slows you down and it flattens the note. The chart ends up looking like every other chart, which is the opposite of what a complex, human visit deserves.

There is a subtler cost too. Templates can pull you toward documenting what the template expects rather than what happened. The form quietly shapes the visit. On a routine encounter that is fine. On a complicated one it is a problem.

## How an ambient scribe fits a variable visit

An ambient scribe starts from the other direction. Instead of a form you fill, it drafts a note from the conversation that actually occurred. The grieving patient with the knee gets a note that reflects both, because the scribe wrote down what was said rather than what a template predicted.

Patient Square returns a structured SOAP note about two minutes after the visit. Structured is the key word: you get organized sections, not a wall of free text. So you keep the readability and organization that make templates useful, without forcing the visit into predefined blanks. For narrative, unpredictable, or emotionally complex encounters, that is the better fit.

And it coexists with your templates. The drafted note is yours to edit before signing, so nothing stops you from dropping a familiar dot phrase into a boilerplate section, or pasting a standard plan block you always use. Ambient capture for the parts that vary, templates for the parts that do not.

## Templates vs ambient capture, side by side

Neither column is the winner. Match the tool to the visit.

| Dimension | Note templates | Ambient scribe |
| --- | --- | --- |
| Best visit type | Repetitive, protocol-driven | Narrative, variable, complex |
| Speed on routine visits | Very fast | Fast |
| Fidelity to the actual visit | Lower when the visit is atypical | Higher, drafts from the conversation |
| Structural consistency | Very high | High, returns structured SOAP |
| Risk of note bloat | Boilerplate can pad the note | Reflects what was said |
| Screen time during the visit | You are filling fields | You are with the patient |
| Coexist with each other | Yes, drop phrases into the draft | Yes, edit the draft freely |

The pattern: templates optimize for consistency on known visits, ambient capture optimizes for fidelity on unknown ones. Most real practices have both kinds of visit, so most real workflows want both tools.

## When to reach for each

Rule of thumb. If you can predict the note before the visit starts, a template is probably faster. If you cannot, ambient capture will serve the encounter better and spare you the fatigue of forcing it into fields.

High-volume, protocol-heavy clinics lean template. Practices with long, variable, or emotionally involved visits, primary care, behavioral health, geriatrics, lean ambient. But almost nobody is purely one or the other, which is why the coexistence point is not a hedge. It is the actual answer.

Because Patient Square is EHR-agnostic, this holds regardless of your system. You copy or paste the structured note into Epic, athenahealth, eClinicalWorks, Elation, or NextGen, and your existing dot phrases live right where they always did. For the note itself, [SOAP note quality](../ai-scribe-soap-note-quality/) goes deeper, and [primary care documentation](../ai-scribe-for-primary-care/) covers a common use case.

## Where your judgment stays

Whatever the mix, you own the note. The scribe drafts, you review and sign, and legal responsibility for the record stays with the signing clinician. That is true whether the draft came from ambient capture, a template, or both stitched together.

The same holds for the extras. ICD-10 codes come back as suggestions you confirm or change. The prescription draft reflects the plan you discussed in the visit; it is a draft only and never sends to a pharmacy, and screening it for interactions, dosing, and contraindications is your review to run, exactly as you run it today. The reading stays yours.

If you are still comparing approaches, [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) and the [best AI medical scribes](../best-ai-medical-scribes/) overview are good next reads. Or skip ahead: <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it on two visits, one you would normally template and one you would not. You will see fast where each tool earns its place.

---

## AI Scribe vs Dictation Software: What Cuts Charting Time
https://patientsquare.com/us/blog/ai-scribe-vs-dictation-software/
Published 2026-07-29 · Tags: comparison, dictation, scribe, ambient-ai, documentation-methods

Dictation makes you narrate the note. An ambient AI scribe drafts it from the visit. Here is how the two differ on time-to-note, mental load, and edit burden.

Dictation software turns your speech into text: you narrate the finished note yourself and it types what you say. An ambient AI scribe listens to the natural visit conversation and drafts a structured SOAP note for you. Dictation moves typing to talking. Ambient AI moves the writing itself off your plate, leaving review.

Dictation software and an AI scribe both use your voice, but they cut charting time in different amounts. Dictation makes you narrate the finished note yourself, so you still rebuild every visit from memory. An ambient AI scribe drafts the note from the actual conversation, leaving a short review. That's the gap, and it decides which one saves you real time. See how our bundle prices it on the [pricing page](/us/pricing/).

> **Key takeaways**
>
> - Dictation transcribes your narration; you still build the note after the visit. Ambient AI drafts it during the visit, so you review instead of write.
> - Dictation typically costs several minutes of speaking plus cleanup per note. An ambient scribe leaves about 2 minutes of review.
> - A 2023 JAMA Network Open study found primary-care physicians log a median 36.2 minutes of EHR time per 30-minute visit; dictation trims the typing inside that, not the after-visit reconstruction.
> - The edit load differs: dictation edits are misheard words, ambient edits are clinical review. Test both on your own note types.
> - Dictation still wins when you want to control every word or keep any capture out of the room.

## Dictation and an AI scribe do different jobs with your voice

Both tools listen to you. That's where the similarity ends, and the difference is the whole story.

Dictation software is speech recognition. You speak the note, it types the words. Dragon Medical One, the category incumbent, describes itself plainly on Microsoft's product page as "speech-driven clinical documentation" that lets you "dictate notes immediately with best-in-class speech recognition." You are the author. The software is a very fast keyboard you talk to instead of type on.

An ambient AI scribe does something structurally different. It listens to the natural back-and-forth of the visit, the questions you ask, what the patient says, your spoken exam findings, and it drafts a structured SOAP note from that conversation. You don't narrate a note. You have the visit, and the note gets written from it. So the leftover task changes from "produce the note" to "review a draft."

Read that difference again, because it's the one that shows up in your evening. With dictation you moved from typing to talking, which is genuinely lighter. But you're still the one composing every sentence, usually after the patient has left. With an ambient scribe the composing step is gone.

## Which cuts charting time: the anatomy of one note

The fairest way to compare is to walk a single visit through each tool and time the steps. Here's what one routine note looks like end to end.

Two rows carry most of the weight. "When the note gets built" and "your time on the note." Dictation keeps the note as after-visit work, so it competes with your next patient or your drive home. The 2016 Annals of Internal Medicine time-motion study found nearly two hours of EHR and desk work for every hour of direct care. Dictation trims that. It doesn't erase it, because the narration still lands on you.

An ambient scribe moves the writing into the visit. A 2025 NEJM AI study of ambient scribes measured a reduction in per-note documentation time when the tool drafts the note from the conversation. What's left is review, and review of a draft is faster than construction from memory on a routine visit.

## Dictation software carries a hidden cognitive tax

There's a cost dictation never shows on the invoice: what your brain is doing during the visit.

If you dictate after the encounter, you spend the whole visit quietly holding a running list of what you'll need to say later. Which findings to include, what the plan was, the exact phrasing you meant to use. That background bookkeeping is real work, and it splits your attention while the patient is still in the room. Dictate findings aloud during the visit and you fix the attention problem but add a stilted, narrate-as-you-go rhythm that some patients find odd.

Ambient capture removes that tax. You don't rehearse a note in your head, because you're not going to narrate one. You just run the visit. For a clinician on a 22-patient Tuesday, dropping that running memory load across every encounter is a change you feel by 3pm, not just at the end of the week.

We think this is the part buyers underweight when they compare on price alone. The monthly numbers can look close. The cognitive difference over a full clinic day doesn't show up in a spreadsheet, and it's the thing clinicians mention first after switching.

## The edit burden is different, not automatically smaller

Here's where a fair comparison has to slow down, because "less editing" isn't guaranteed.

Dictation edits are predictable. They're transcription errors: a misheard drug name, a wrong number, a run-on where you paused. You know what you said, so you know what to look for, and modern medical speech recognition is accurate on clinical vocabulary. The edit is mechanical and fast.

Ambient AI edits are a different animal. You're not hunting typos. You're confirming clinical substance: does the assessment match your reasoning, did the draft attribute a finding correctly, did anything get into the note that shouldn't be there. That's a heavier kind of attention per edit, even if there are fewer of them. On routine visits a good ambient scribe usually leaves a lighter total edit load than dictation. A weak one can leave more. The quality of the draft is the whole variable, which is exactly why you test before you commit rather than trust a demo reel.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Those ICD-10 lines are suggestions you confirm, and the prescription is a draft you sign off, not a note transmitted anywhere on its own. The point of naming them is that dictation software, as a speech-to-text tool, doesn't produce codes or a prescription draft at all. It types what you say and stops there.

## Why the note comes out structured, not just transcribed

There's a mechanical reason the two tools end at different places, and it's worth a minute because it explains the edit difference above.

Dictation gives you text in the order you spoke it. If you narrate out of sequence, jumping to the plan, back to the history, then remembering an exam finding, that's roughly how the transcript lands, and part of your after-visit cleanup is dragging it into SOAP order. The software heard words. It didn't understand that "blood pressure was fine" belongs under objective and "we'll recheck in two weeks" belongs under plan.

An ambient scribe works on the conversation, not just the audio. It's built to sort what was said into the note's sections, so the subjective, objective, assessment, and plan land where they go without you rearranging anything. That's why the leftover task is review rather than restructuring. You're checking that the sorting was right and the clinical content is accurate, not moving paragraphs around. For a clinic already tired of copy-paste note bloat, structure you don't have to assemble is a real part of the time saving, separate from the narration step.

The flip side is honest to name: because the tool interprets to build that structure, it can misplace or misstate something, which is exactly the clinical review the last section described. Dictation never misinterprets your meaning, because it isn't trying to. It just types. Different tool, different failure mode.

## When is dictation software the better fit?

To be straight about it: dictation isn't beaten in every case, and some clinicians should stick with it.

Dictation wins when you want to control every word. If you have a precise documentation style and you'd rather compose a finished narrative in your own phrasing than review a model's draft, dictation gives you that authorship with no interpretation layer in between. Radiology and other structured, template-driven reporting are a natural fit too, where the workflow is already "dictate into a known structure" and there's no free-flowing patient conversation for an ambient tool to capture. And if your policy or your comfort level rules out any third-party ambient capture in the room, dictation keeps the recording question off the table entirely, because you're speaking a note, not capturing a visit.

For those clinicians, dictation is the honest pick, and an ambient scribe would be solving a problem they don't have. If you already dictate fast and the after-hours load is something you can live with, the gain from switching is smaller. Name that honestly before you spend on either.

For most charting-heavy practices, though, the bottleneck is the after-visit reconstruction, and that's the exact step dictation can't remove. If your notes follow you home, the method that writes the note during the visit is the one that helps.

## How the pricing shapes the decision

The workflow difference is the main event, but the money follows a pattern worth naming.

Dragon Medical One, the dictation standard, is sold through Microsoft and resellers rather than a checkout page, so pricing comes as a quote and often sits on a multi-year contract. That's a fair model for an established tool, but it means you commit before you know the workflow fits. We publish our number instead. On the Copilot plan, the ambient scribe comes bundled with an AI EHR at $119 per clinician per month on the annual plan, and documentation starts from $79 per clinician per month on the Assist plan. Unlimited visits and notes, no per-note metering, no setup fee, and a 7-day trial so you can run it on a real clinic day before you decide.

That last part matters more than a price gap. When you can trial an ambient scribe next to your current dictation tool for a week, you settle the comparison with your own edit counts instead of a sales pitch. Keep dictating some visits, let the scribe draft others, and time both.

You can [see the full pricing](/us/pricing/) with no sales call, or <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we'll run the scribe on your own visit types so you can watch the note land about two minutes after a sample encounter.

## The bottom line on dictation software versus an AI scribe

Dictation software and an ambient AI scribe both use your voice, but they cut charting time by different amounts because they do different jobs. Dictation types what you narrate, so you still build the note after the visit. An ambient scribe drafts the note from the conversation, so you review instead of write. For clinicians whose evenings disappear into after-visit charting, that structural difference is the one that pays off, and it's bigger than any gap in the monthly price.

Dictation still earns its place for clinicians who want to control every word, work in structured-reporting specialties, or keep capture out of the room. If that's you, stay with it. If your real problem is the note that follows you home, run both for a week and let your own numbers settle it.

## Frequently asked questions

The FAQ above covers the recurring ones: how the two methods differ, which cuts charting time, when dictation is still the better call, and how the edit burden compares. For the method-by-method view including manual typing, see [ambient AI versus dictation](../ambient-ai-vs-dictation/); for the dictation-cost breakdown, see [Dragon Medical One cost in 2026](../dragon-medical-one-cost/); and for how ambient differs from a transcription service, see [AI scribe versus medical transcription](../ai-scribe-vs-medical-transcription-service/).

---

## Behavioral Health EMR Cost: Real Per-Provider Pricing (2026)
https://patientsquare.com/us/blog/behavioral-health-emr-cost/
Published 2026-07-29 · Tags: pricing, comparison, behavioral-health, ehr, small-practice

Real behavioral health EMR cost per provider in 2026: SimplePractice, TherapyNotes, and ICANotes pricing, the add-on fees that stack, and a bundled alternative.

Most behavioral health EMRs land between about $49 and $99 per month for a solo clinician on published plans like SimplePractice and TherapyNotes. Prescriber-focused systems run higher: ICANotes lists prescribing seats at $213 per month plus a $99 activation fee. Then add-ons stack. E-prescribing, AI notes, and premium telehealth are often billed on top, so your real per-provider number is usually higher than the headline plan.

A behavioral health EMR costs roughly $49 to $99 per provider per month on published solo plans like SimplePractice and TherapyNotes, and more if you prescribe. ICANotes lists prescribing seats at $213 a month plus a $99 activation fee. Add-ons for AI notes, e-prescribing, and reminders stack on top, so your real per-provider number usually runs higher than the headline plan. Our published price sits on the [pricing page](/us/pricing/): $79 per clinician per month on the annual Assist plan.

> **Key takeaways**
>
> - Non-prescribing solo plans start around $49 to $75 a month; SimplePractice Starter is $49, TherapyNotes Solo is $69, ICANotes non-prescribing is $75.
> - Prescribing changes the math: ICANotes lists $213 per prescriber per month plus a $99 activation fee, per its pricing page.
> - Add-ons stack. SimplePractice ePrescribe is $24.50 a month plus $89 setup; its AI Note Taker is $35 a month; a third-party guide cites TherapyNotes e-prescribing near $65 per prescriber.
> - Practice Copilot publishes a flat $79 per clinician per month on annual Assist, no setup fee and no per-note metering, with an ambient scribe on the Copilot plan.

## What does a behavioral health EMR actually cost per provider?

Start with the published base plans, because they set the floor. For a non-prescribing solo clinician in 2026, the entry points cluster in a narrow band.

- **SimplePractice Starter:** $49 per month, per its pricing page. Essential is $79, Plus is $99.
- **TherapyNotes Solo:** $69 per month, with additional clinicians around $39 each, per EHR Source's 2026 review.
- **ICANotes non-prescribing:** $75 per month, per its pricing page. A notes-only tier runs $55.

So far, so affordable. A one-person counseling practice can be up and documenting for under $80 a month. That's real, and it's why these systems dominate the category.

The number moves the moment you prescribe. ICANotes lists a prescribing seat at $213 per month plus a $99 activation fee. That's not a markup for its own sake. Prescriber workflows, medication logic, and the long narrative templates that psychiatrists lean on cost more to build and run. If your practice is all talk therapy, you're paying for capability you won't touch. If you run medication management, that tier is where the value lives.

The base plan is the easy part of the budget, though. The add-ons are where behavioral health practices get surprised.

## Which add-on fees stack on a behavioral health EMR?

The plan grid is the sticker. The fee schedule is the invoice. Three add-ons show up on almost every behavioral health quote, and each one can move your monthly total more than switching tiers would.

**E-prescribing.** SimplePractice lists ePrescribe at $24.50 per month plus an $89 one-time setup fee. A third-party pricing guide cites TherapyNotes e-prescribing around $65 per prescriber per month. ICANotes folds prescribing into its higher $213 seat instead of charging it separately. Three vendors, three completely different structures for the same feature.

**AI notes and ambient documentation.** SimplePractice sells a Note Taker add-on at $35 per month, and a broader Care Aide bundle at $59 for the account owner. ICANotes lists an AI Scribe add-on at $49 per month per user. In both cases, the AI that drafts your note is a line item on top of the EMR, not part of it.

**Reminders, claims, and per-transaction fees.** Text reminders and claims often bill per message or per claim rather than as a flat rate. A busy practice sending hundreds of reminders a month feels those. ICANotes also requires a three-month minimum commitment, so you can't test-drive it on a single billing cycle.

Run the arithmetic on a real scenario. Take a solo therapist on SimplePractice Starter who wants AI notes and e-prescribing. That's $49 base, plus $35 for Note Taker, plus $24.50 for ePrescribe, plus the $89 e-prescribe setup in month one. The $49 headline is now $108.50 a month once you're set up. Still reasonable, but nowhere near the number on the pricing page.

If a clear all-in figure matters to you, [our pricing](/us/pricing/) is published flat: $79 per clinician per month on annual Assist, with unlimited notes and no setup fee.

## Behavioral health EMR pricing compared: the structures side by side

The vendors don't just differ on price. They differ on how the price is built, which is what makes clean comparison shopping hard. Here's the structure laid out.

Two things jump out. First, every one of these vendors publishes a price, which is genuinely helpful; behavioral health has more pricing transparency than the broader EMR market. Second, the transparency stops at the base plan. The e-prescribe, AI, and reminder lines are where two similar-looking quotes end up hundreds of dollars apart.

## When is ICANotes, TherapyNotes, or SimplePractice the better fit?

We build a competing product, so take this in the spirit it's meant: for a lot of behavioral health practices, one of these three is the right call, and we'll say when.

**ICANotes is the better fit when you prescribe and live in structured narrative notes.** Its button-driven charting and psychiatric templates are built for medication management and complex behavioral documentation. If you're a prescribing psychiatrist or a group with prescribers, the $213 seat buys depth that a general EMR doesn't have. We don't try to match that prescriber-first template library, and our [rundown of psychiatry EHR options](../best-ehr-for-psychiatry/) says as much.

**TherapyNotes is the better fit for an insurance-billing group that wants proven behavioral workflows.** Its integrated billing, claims, and therapy-specific note templates are established and well-reviewed, and the $69 solo price with $39 additional clinicians scales predictably for a group practice. If billing and multi-clinician management are your center of gravity, it's a strong, boring-in-the-good-way choice.

**SimplePractice is the better fit for a solo cash-pay or concierge therapist who wants a polished client experience.** The client portal, scheduling, and telehealth are clean, and the $49 Starter is a low entry point if you skip the add-ons. For a private-pay practice that values patient-facing polish over deep clinical tooling, it fits.

Where all three share a limitation: they store your note, but the clinician still writes it. Add-on AI helps, at an add-on price. If your practice's actual pain is finishing progress notes after the last session of the day, the base EMR doesn't solve that on its own. That's the case we make in more detail for [an ambient scribe in a behavioral health practice](../ai-scribe-for-behavioral-health/).

## The transparent-price alternative for behavioral health practices

Here's where we come in, and we'll be direct. We build [Practice Copilot](/us/products/practice-copilot/), and we publish the price. AI Medical Scribe by Patient Square is one module inside it: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On the annual Copilot plan at $119 per clinician per month, that scribe comes with a bundled AI EHR. The entry Assist plan is $79 per clinician per month. No per-note metering, no setup fee, a 7-day trial.

For a behavioral health practice, the contrast is the all-in number. With the others, the ambient AI that drafts your note is a separate add-on stacked on the base plan. With Practice Copilot, the scribe is the plan, and the price on the page is the price you pay. A two-clinician counseling practice can read the total in one line instead of adding up four.

We're not the deepest behavioral-specific record system on this page, and we've said which competitor wins for prescribers and for insurance-heavy groups. What we do is put a flat number in front of you with the ambient documentation already included. If that's the comparison you want to run, [see the pricing](/us/pricing/) or book a short demo and we'll run the scribe on your own session notes. Our [security page](/us/security/) covers how BAAs and data handling work for behavioral health PHI.

## Bottom line on behavioral health EMR cost

A behavioral health EMR runs about $49 to $99 per provider per month on published non-prescribing solo plans, with ICANotes' prescribing seat at $213 plus a $99 activation fee. The base price is only the start; e-prescribing, AI notes, and reminders can add $35 to $65 a month each, and a $49 plan can quietly become a $108 bill. Price the add-ons you'll actually use, not the entry tier.

ICANotes wins for prescribers. TherapyNotes suits insurance-billing groups, and SimplePractice fits cash-pay solo therapists. If you want a flat published per-clinician price with an ambient scribe already in the plan, that's our pitch. It's on the [pricing page](/us/pricing/), no sales call required to read it.

## Frequently asked questions

The FAQ above covers the recurring ones: real per-provider cost, why prescribing tiers jump, which add-ons stack, and how the totals compare. For the full Practice Copilot breakdown, see the [pricing page](/us/pricing/); a demo shows the scribe on your own behavioral note types.

---

## Patient Management Software: Which Category Do You Need?
https://patientsquare.com/us/blog/patient-management-software-guide/
Published 2026-07-29 · Updated 2026-08-29 · Tags: guide, small-practice, ehr, scheduling

Separate records, portals, CRM, scheduling, billing, and care management before buying patient management software for a medical practice.

It is an ambiguous buying term, not one product category. A vendor may mean an EHR, patient portal, scheduling system, healthcare CRM, billing platform, or care-management tool. Define the record, operational, financial, or longitudinal-care job before comparing software.

A practice searching for patient management software may be shopping for six different products without realizing it. The phrase can describe a clinical record, portal, CRM, scheduler, billing system, or longitudinal care platform.

Do not compare vendors yet. Locate the job.

> **Key takeaways**
>
> - The category name does not establish scope. Identify the system of record and the event that needs fixing.
> - Portal, CRM, scheduling, billing, and care management can sit around an EHR without replacing it.
> - Patient Square covers documentation, scheduling, a bundled EHR by tier, and named communication modules. It is not full RCM, payer care management, or population health.
> - Price the complete data path, not the cheapest seat.

## The six-category patient-management grid

| Category | Job it owns | Core evidence in a demo | Disqualifier |
|---|---|---|---|
| Clinical record / EHR | Signed chart, history, medications, documents | Create, sign, amend, retrieve, export | Cannot produce a usable complete record |
| Patient portal | Patient access, forms, results, messages, payments | Patient completes the intended task on a phone | Portal is only a staff-facing screen |
| Healthcare CRM / engagement | Outreach, lead or referral follow-up, communication | Consent, routing, opt-out, attribution | Communication cannot be tied to an authorized workflow |
| Scheduling and intake | Appointment inventory, booking, reminders, registration | New, rescheduled, cancelled, walk-in, duplicate | Appointment and chart identities diverge |
| Billing / RCM | Eligibility, charges, claims, ERA, balances, denials | Claim from encounter through correction and payment | Requires retyping or lacks payer workflow |
| Care management / population health | Cohorts, care plans, gaps, tasks, longitudinal work | Attribution, risk or gap logic, task closure, audit | It is merely a patient list or reminder tool |

This grid stops a familiar mistake: buying a portal to solve a claims problem, or buying a CRM and assuming it became the chart.

## Start with the event that fails

Write one sentence before opening a demo. Examples:

- "Patients wait on hold because staff cannot expose safe appointment inventory online."
- "Signed notes remain open until the next morning."
- "The billing team retypes demographics and codes from the chart."
- "Patients cannot retrieve results or complete intake on a phone."
- "Referrals arrive, but nobody owns the next contact."
- "Care managers cannot see which attributed patients have an unresolved task."

Each sentence routes to a different row in the grid. A broad suite can cover several rows, but it still has to prove the failing event.

## Name the source of truth

Patient data is not one blob. Assign an owner to each object:

| Data object | Source-of-truth system | Who may change it | Where it must go next | Failure owner |
|---|---|---|---|---|
| Patient identity |  |  |  |  |
| Appointment and status |  |  |  |  |
| Signed clinical note |  |  |  |  |
| Consent and communication preference |  |  |  |  |
| Charge and claim |  |  |  |  |
| Payment and patient balance |  |  |  |  |
| Care plan, gap, and task |  |  |  |  |

One vendor may own several rows. That is fine. One login does not fill the blanks automatically.

That worksheet becomes especially useful when a practice is changing only one system. A scheduler can remain the source of truth for appointments while the EHR holds signed notes. A billing service can own claims while a different system creates the charge data. The important part is not forcing every task into one platform. It is making the handoff and exception owner explicit before a patient is affected.

## Records and portals solve different access problems

The EHR is the professional record. It should preserve authorship, dates, amendments, and a usable history. CMS documentation guidance focuses on the completed encounter record and whether it supports the service billed.

A portal exposes selected patient-facing tasks. It may show results, messages, forms, appointments, balances, or records, depending on the product. A portal does not become the EHR because it displays chart data. An EHR does not automatically have a usable portal because a feature list says "patient engagement."

If patient access is the purchase, test the [bundled-versus-standalone portal matrix](../patient-portal-software-guide/). Use a real phone and a test patient, not an administrator's desktop.

## CRM and scheduling are not care management

A healthcare CRM often manages outreach, referrals, leads, campaigns, and communication. Scheduling owns appointment inventory and status. Both can improve access.

Care management is a different job. It can involve attributed populations, care plans, assessments, gaps, risk logic, cross-encounter tasks, escalation, and outcome tracking. A reminder to return in six months is useful. It does not prove a population-health platform.

Ask the vendor to show why a patient entered a worklist, who is responsible, what evidence closes the item, and how the action is audited. If the answer is "we can tag patients," the scope is narrower.

## Billing must reach the financial endpoint

A product has not demonstrated billing because it can display ICD-10 suggestions or print a superbill. Follow one encounter through charge, claim, payer response, correction, patient responsibility, and payment.

Record which product handles:

- eligibility and payer enrollment;
- charge and code ownership;
- claim creation and clearinghouse submission;
- rejection, denial, and corrected claim;
- ERA and payment posting;
- statement, payment plan, and patient balance;
- reporting and reconciliation.

If these are the main problems, buy billing or RCM depth. Documentation software should not be stretched into that category.

## Where Patient Square maps to the grid

Patient Square's public Practice Copilot scope maps to several, but not all, rows:

| Grid row | Public Patient Square scope | Boundary |
|---|---|---|
| Clinical documentation | Structured SOAP, ICD-10 suggestions, prescription draft for review | Suggestions and draft are not autonomous coding or prescribing |
| Scheduling | Listed from Assist | Depth, self-booking, intake, and edge cases need an evaluation |
| Clinical record | AI Copilot EHR begins on Copilot | Public pages do not enumerate deep EHR submodules |
| Messaging | WhatsApp begins on Copilot | Exact workflow and consent behavior need proof |
| Front office | AI Receptionist and AI Follow-ups named on Autopilot | Module names do not establish every behavior |
| Portal | Not publicly listed | Do not assume one |
| Billing and RCM | Not a full US claims, clearinghouse, eligibility, or RCM system | Keep a dedicated workflow |
| Care management / population health | Not publicly listed | Do not infer from follow-up naming |

Current US annual monthly equivalents are $79 for Assist, $119 for Copilot, and $199 for Autopilot. Month-to-month rates are $99, $149, and $249. All plans list unlimited visits and notes.

Practice Copilot supports two record paths: use the Patient Square EHR from the Copilot tier or keep an existing EHR while Patient Square handles documentation and front-office workflows. Discovery should confirm the handoff for either path.

That scope is intentionally narrower than the phrase "patient management software" makes it sound. It can be a sensible purchase for a practice that needs ambient documentation, scheduling, or the bundled record. It should not be chosen on the assumption that it includes patient access, billing, or population management that the public pages do not list.

EHR-ready export (PDF · HL7 · FHIR) is a portability claim. It is not proof that another product will ingest every field or that Patient Square writes natively into every EHR.

## Security follows the data flow

HHS explains that software sale alone does not create a business-associate relationship, but storing or accessing PHI for hosting or support can. Map every vendor and subprocess that receives PHI. Put required BAAs in place before access.

Patient Square is HIPAA compliant, and Business Associate Agreements are available. The practice still owns consent, access rules, device controls, retention, and its complete workflow.

The contract should identify:

1. data types and permitted uses;
2. roles, support access, and logs;
3. retention and deletion for each data type;
4. interface monitoring and incident ownership;
5. export format, timing, cost, and termination behavior.

The more categories a suite covers, the more important that map becomes.

## The one-week selection exercise

Assign one owner for the decision and one owner for each failing event. A clinician should validate the record and documentation path. Front desk staff should test scheduling and duplicate identities. The person who works claims should test the financial path. A patient or trained staff member should test any patient-facing workflow from a phone. Do not let the buyer who never uses a function certify it for everyone else.

Give the finalists the same short script. Create a patient, make and change an appointment, complete the clinical encounter, move the required information to the next system, then trace any financial or follow-up event to closure. Capture the screens, exception steps, ownership, and time required. The test is not a demand for a giant proof of concept. It is a way to surface the quiet manual work that an attractive feature grid does not show.

Then price only the systems that passed the required events. Include the modules, staff seats, transactions, training, data migration, interfaces, support, and exit terms. A lower subscription with a permanent retyping step can cost more than a higher tier. A broad platform with an unused billing or portal module can cost more too.

## Buy the narrowest system that closes the gap

A clinic with a working EHR and a broken appointment line may need scheduling, not replacement. A practice with persistent payer rework needs billing depth, not a prettier patient list. A group building longitudinal programs needs care management, not a reminder module.

Use the six-category grid to route the problem. Use the source-of-truth worksheet to expose integration work. Then price seats, transactions, migration, interfaces, training, support, and exit for only the finalists in the right category.

The [medical practice management guide](../medical-practice-management-software-guide/) maps operational modules. The [patient portal guide](../patient-portal-software-guide/) handles the patient-facing layer. Request your 7-day trial if Practice Copilot passes the specific jobs in its published scope.

## Patient Square and your existing record system

Practice Copilot can use the bundled AI Copilot EHR from the Copilot tier, or work alongside an existing EHR. Neither path promises automatic filing or write-back into a third-party EHR.

---

## AI Medical Scribe for Diagnostic Centres in India
https://patientsquare.com/in/blog/ai-scribe-for-diagnostic-centres-india/
Published 2026-07-28 · Tags: diagnostic-centre, ai-medical-scribe, nabh, clinical-documentation, india

How an ambient AI scribe drafts consult and report-desk notes for Indian diagnostic centres while capturing referring-doctor context.

No. It does not generate lab reports and does not read or interpret scans. It drafts consult and report-desk notes from what is said during the interaction. The clinical reading stays with your radiologist, pathologist, or physician.

Most people picture a diagnostic centre as machines and reports, not conversations. The reality has more talking in it than that. A patient arrives with a referral and explains why. A physician at the centre runs a consult before or after a test. Someone at the report desk explains a result and what to do next. Each of those interactions should leave a record, and usually does not, because nobody has time to write it. An ambient AI scribe drafts a structured note from those spoken interactions and hands it back about two minutes later. What it does not do is generate the lab report or read the scan. Those stay with your pathologist, radiologist, or consulting physician.

> **Key takeaways**
> - The scribe drafts consult and report-desk notes from spoken interactions; it does not generate lab reports or read scans.
> - It captures referring-doctor context when stated, helping close the loop back to the referrer.
> - It supports the documentation habit NABH accreditation expects; the centre holds accreditation, not the software.
> - Notes are encrypted, belong to the centre, and audio is discarded once the note drafts. An India data-residency posture is available. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - ABDM integration is on the roadmap for AI Medical Scribe by Patient Square, not shipped.

_Source: Product behaviour of AI Medical Scribe by Patient Square._

## Where documentation actually happens in a diagnostic centre

The tests themselves are already documented by the instruments and the LIS. The gaps are in the human touchpoints around them, and those touchpoints are where a scribe fits.

Three moments stand out. First, referral intake, where a patient explains what they were sent for and by whom. Second, the physician consult that many centres run alongside imaging or pathology, a proper clinical encounter that deserves a proper note. Third, the report desk, where a result gets explained and advice gets given, often verbally and then lost.

An ambient scribe drafts a note from each of these spoken interactions. The person doing the consult or the explaining talks as they normally would, and the structured draft comes back for review and sign-off. The instruments still produce the report. The scribe produces the record of the conversation around it.

## What the scribe does, and does not, do

Clarity here is the whole point, because a diagnostic centre is exactly the setting where an overclaiming vendor could cause real harm.

The scribe does not generate lab reports. It does not read or interpret scans. It does not produce a radiology finding or a pathology result. Those are clinical readings, and they belong to your qualified staff: the radiologist reading the film, the pathologist reporting the slide, the physician interpreting the panel.

What the scribe does is transcribe and structure the spoken interaction into a consult or report-desk note. So a note might read "referred by Dr Sharma for evaluation of persistent cough, chest X-ray advised, findings discussed with patient," because that is what was said during the encounter. The reading in the report stays with whoever read it. The scribe records the conversation, not the diagnosis.

| Interaction | What the scribe drafts | What stays with clinical staff |
|---|---|---|
| Referral intake | Reason for referral, referring doctor, tests advised | The decision on what to test |
| Physician consult | History, examination narrated, plan | The clinical assessment |
| Report-desk explanation | What was explained, advice given, follow-up | The report and its interpretation |
| Prescription (if a physician consults) | A draft the physician reviews | The signed prescription |

## Referring-doctor context and closing the loop

Diagnostic centres live on referrals, and the referral relationship runs on communication. A referring doctor wants their patient seen, tested, and reported back cleanly. When the reason for referral and the referring doctor's name are captured in the note, the loop is easier to close.

If, during the interaction, the referral context is stated out loud, the scribe captures it: who referred, what for, what was advised. That gives the centre a consistent record tying each encounter back to its source. It does not auto-fax the referrer or integrate with their system; it produces the note, and your team handles the communication. Still, a clean, consistent record of referral context is worth having when a referring doctor calls to ask what happened with their patient.

## NABH documentation touchpoints

NABH accreditation, including the entry-level programme relevant to many diagnostic centres and labs, expects documented processes and consistent records. The consult and report-desk notes are part of that documentation picture.

Two honest clarifications. First, NABH accreditation is held by the centre after it meets the standards and passes assessment. It is not something a piece of software holds or confers. AI Medical Scribe by Patient Square does not hold NABH accreditation and cannot make your centre accredited. Second, what the scribe genuinely helps with is the underlying habit: producing legible, dated, structured notes for the human touchpoints, consistently, rather than relying on memory or skipping the note entirely. Consistent documentation is one input into the record-keeping that accreditation assessors look for.

Our [NABH documentation overview](../nabh-documentation-requirements/) goes through what the documentation expectations involve, and the [EMR software for India guide](../emr-software-india-guide/) covers how a scribe sits alongside the systems your centre already runs, since the scribe is EHR-agnostic and does not require an integration project.

## Data handling for a diagnostic centre

A diagnostic centre holds a lot of patient data, and the consult and report-desk notes add to it. How that is handled should be plain.

Consultation audio is processed in memory and discarded the moment the note drafts. No recording of the interaction is kept. Notes are encrypted in transit with TLS and at rest with AES-256, they belong to the centre, and you can export or delete them at any time. An India data-residency posture is available, so the data stays handled within the country. This aligns with a DPDP-conscious way of handling personal data; our [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) covers the obligations, and our [data-residency note](../ai-scribe-data-residency-india/) covers where the notes live. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

ABDM integration is on the roadmap for AI Medical Scribe by Patient Square, not shipped. The product does not currently link diagnostic-centre records to ABHA.

## When a scribe is the right call for a centre

Not every diagnostic centre needs this. If your only output is machine-generated reports with no human consult, a scribe adds little. The centres that gain most are the ones running real clinical encounters: an in-house physician OPD, a specialist consult tied to imaging, a busy report desk giving verbal advice all day.

For those, the scribe turns conversations that were going undocumented into a consistent record, without an IT project and without touching the LIS or the reporting software. It works alongside what you have. For a broader view of how a scribe fits Indian practice generally, our [scribe-for-doctors overview](../scribe-for-doctors-india/) is the starting point, and if you are comparing tools, the [best AI scribe for India roundup](../best-ai-scribe-for-india-2026/) lays out the options.

## See it at your report desk

The test is your own touchpoints: a referral intake, a physician consult, a report-desk explanation. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, run a few real interactions, and see how the drafts read against what your team actually says. The [pricing page](../../pricing/) has India plans, and the [security page](../../security/) details encryption, residency, and deletion. See where it fits before it touches a single record.

---

## Pharmacy Software Prices in India: 2026 Cost Guide
https://patientsquare.com/in/blog/pharmacy-software-price-india/
Published 2026-07-28 · Updated 2026-08-27 · Tags: india, pricing, pharmacy-software, clinic-software, cost

What pharmacy software costs in India in 2026: retail chemist billing tools vs clinic-pharmacy modules, typical price ranges, GST notes, and where Patient Square fits.

It depends on the type. Standalone retail chemist billing software often starts around ₹5,000 to ₹15,000 a year for a single counter, with mid-range cloud tools running ₹15,000 to ₹40,000 a year and multi-store or enterprise systems higher. Pharmacy modules inside a hospital HMS are usually bundled into the HMS price rather than sold separately. Always confirm whether GST is included, because most vendors quote ex-GST.

Pharmacy software price in India splits by what you're actually running. A standalone retail chemist billing tool often starts around ₹5,000 to ₹15,000 a year for one counter, mid-range cloud tools run ₹15,000 to ₹40,000, and multi-store systems climb from there. A pharmacy module inside a hospital HMS is usually folded into the HMS price, not sold on its own. If your need is the clinic side rather than a standalone chemist counter, Patient Square's Copilot tier bundles front-office automation and the AI Copilot EHR at ₹2,399 per clinician per month on annual billing, ex-GST, so the prescription and record are handled in one place. [See the India pricing](../../pricing/) or book a demo.

> **Key takeaways**
>
> - Retail chemist software: roughly ₹5,000 to ₹40,000 a year depending on single vs multi-store, ex-GST.
> - Clinic-pharmacy value is the prescription-to-dispense link, not thousands of SKUs. Different problem, different tool.
> - Patient Square is a clinic AI platform, not a standalone retail-pharmacy inventory system. It bundles the EHR and front-office at ₹2,399/clinician/month (annual, ex-GST).
> - Software is quoted ex-GST; add 18% GST on the invoice. A ₹20,000 tool becomes ₹23,600.
> - For a busy chemist counter with big SKU counts, buy a dedicated pharmacy inventory tool. For the clinic side, Patient Square fits.

## Retail chemist software vs clinic-pharmacy needs

First split, because it decides your whole budget. There are two different products people call "pharmacy software," and they solve different problems.

**Retail chemist software** runs a standalone medical store. Its job is fast billing across thousands of SKUs, inventory with batch and expiry tracking, reorder alerts, supplier and purchase management, GST invoicing, and drug-licence compliance including the Schedule H1 register the Drugs and Cosmetics Rules require. This is heavy inventory software. Marg, Vyapar, and similar tools live here, and prices range from a few thousand rupees a year for a single counter to lakhs for a chain.

**Clinic-pharmacy needs** are narrower. A clinic that dispenses from a small in-house counter doesn't need enterprise SKU management. What it needs is the doctor's prescription flowing to dispensing without someone re-typing it, plus clean records. The value is the link between the consult and the counter, not a warehouse system.

Getting this split right saves money. A three-doctor clinic buying enterprise multi-store chemist software is overbuying; a busy retail chemist trying to run inventory inside a clinic tool is underbuying. Name your building first.

## Typical India pharmacy software prices in 2026

Here's the ballpark for standalone retail pharmacy software, from published vendor pricing and common market quotes. Ranges, not a rate card, and all ex-GST.

| Setup | Typical annual cost (ex-GST) | What it usually covers |
|---|---|---|
| Single-counter chemist (basic) | ₹5,000 to ₹15,000 | GST billing, batch/expiry, stock alerts, H1 register |
| Single-counter cloud (mid) | ₹15,000 to ₹40,000 | Above plus reporting, purchase management, multi-user |
| Multi-store / chain | ₹40,000 to ₹2,00,000+ | Centralised inventory, branch reporting, integrations |

Two things to check on any pharmacy quote. First, batch and expiry tracking is non-negotiable; a tool that only prints bills isn't pharmacy software. Second, confirm the Schedule H1 register is handled, because dispensing H1 drugs without maintaining that register is a compliance problem, not a convenience one. The [pharmacy management software buyer's guide](../pharmacy-management-software-india/) walks through the full feature checklist if you're buying a standalone system.

## Where Patient Square fits, and where it doesn't

Straight answer, because a cost guide that oversells is useless. Patient Square is not a standalone retail-pharmacy inventory system. If you run a chemist counter with thousands of SKUs, batch-level stock, and supplier ledgers, buy a dedicated pharmacy tool. That's the right call and we'll say so.

Where Patient Square fits is the clinic side of the same building. Its Copilot tier bundles front-office automation and the AI Copilot EHR, so the doctor's ambient note, ICD-10 suggestions, and prescription draft, plus the patient record, live in one place, in Hindi and other Indian languages. For a clinic that dispenses a small in-house set of medicines, the win is that the prescription is already drafted and reviewed in the system rather than hand-written and re-keyed at the counter.

Here are the per-clinician tiers, ex-GST, with 18% GST added:

| Tier | Monthly (ex-GST) | Annual rate (ex-GST) | What you get |
|---|---|---|---|
| Assist | ₹1,999 | ₹1,599 | AI Medical Scribe, ICD-10 suggestions, Rx drafts, scheduling |
| **Copilot** | ₹2,999 | **₹2,399** | Assist plus front-office automation and the **AI Copilot EHR bundled** |
| Autopilot | ₹4,999 | ₹3,999 | Copilot plus AI Receptionist, follow-ups, priority support, ROI analytics |

So the honest positioning: a busy standalone chemist should price dedicated pharmacy inventory software from the table above. A clinic that wants the consult, the record, and the prescription handled in one AI platform should look at Copilot at ₹2,399 per clinician per month (annual, about ₹2,831 with GST). Different jobs. Book a demo if the clinic side is your problem.

## The GST math, shown once

Pharmacy software, like all Indian B2B software, is quoted ex-GST. Here's the arithmetic once so you can run it on any quote:

₹20,000 ex-GST × 1.18 (18% GST) = **₹23,600 on the invoice** a year.

Do the same on Patient Square's ₹2,399 monthly Copilot rate: ₹2,399 × 1.18 is about ₹2,831 per clinician per month. The rule for the whole shortlist: get the ex-GST figure and confirm GST treatment in writing before you compare, so you're not lining up a with-GST number against an ex-GST one.

## How to buy the right pharmacy software for your setup

1. Name the building. Standalone chemist counter or clinic-with-dispensing? The answer picks your category.
2. For a chemist, demand batch/expiry tracking, stock alerts, GST billing, and the H1 register. Price from the retail table.
3. For a clinic, the value is the prescription-to-record link, not SKU management. Price a clinic AI platform like Patient Square's Copilot instead.
4. Confirm ex-GST pricing and GST treatment for every vendor.
5. Get the all-in first-year number: licence plus onboarding plus any per-user or per-store add-ons plus GST.

Buy the tool that matches the job. A clinic paying for enterprise chemist inventory it never uses, or a chemist trying to run stock inside a clinic tool, both overspend in opposite directions. If your problem is the clinic, [see the Copilot pricing](../../pricing/) and book a demo.

---

## AI Medical Scribe for Multi-Specialty Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-multi-specialty-clinics-india/
Published 2026-07-27 · Tags: ai-scribe, multi-specialty, opd, clinic-operations, documentation

How an ambient AI scribe fits a busy multi-specialty OPD in India: consistent notes across departments, per-doctor workflow, and high patient volume.

Yes. AI Medical Scribe by Patient Square structures whatever is said in the consult into a SOAP note, so it adapts to a physician, a gynaecologist, an orthopaedic surgeon, or a paediatrician in the same clinic. Each doctor reviews and signs their own note.

A multi-specialty OPD is a documentation stress test. Ten departments, dozens of doctors, hundreds of patients, and every one of them expecting a note that holds up. The physician writes differently from the gynaecologist, who writes differently from the orthopaedic surgeon, and by evening half the notes are a scramble. An ambient AI scribe helps by drafting a structured note for each consult, per doctor, in about two minutes. This post covers how that fits a high-volume, many-specialty clinic in India.

> **Key takeaways**
> - One ambient scribe adapts across specialties because it structures whatever is said into a SOAP note.
> - Each clinician uses it on their own consults and signs their own note. No shared queue.
> - Notes draft in about two minutes, so documentation keeps pace with a busy OPD instead of piling up.
> - No integration project. It is EHR-agnostic; the clinician copies, pastes, or exports into your records.
> - Built with DPDP-aligned handling: audio processed in memory and discarded, notes encrypted in transit and at rest. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## Why documentation breaks down in a multi-specialty OPD

The failure mode is predictable. Volume is high, time per patient is low, and consistency is the first casualty. A note that should capture history, examination, assessment, and plan gets compressed into a few rushed lines by patient number thirty.

Now multiply that across departments. Each specialty has its own rhythm and its own note habits. Some doctors are meticulous. Some are terse. An administrator trying to keep records to a common standard is fighting ten different styles at once. When accreditation prep or an insurance audit arrives, those gaps show.

The problem is not that doctors are careless. It is that thorough documentation and high throughput pull against each other. Something has to give, and it is usually the note.

## How an ambient scribe fits a multi-specialty visit

The scribe listens during the consult and, about two minutes after, hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft. It works the same way regardless of specialty because it structures what was actually said rather than applying a specialty-specific template.

So the paediatrician's consult becomes a paediatric note. The orthopaedic consult becomes an orthopaedic note. The underlying structure is consistent, but the content follows the conversation in the room. The clinician then reviews, edits anything that needs it, and signs.

That consistency is the point for a multi-specialty setup. Every department produces notes with the same backbone, which is exactly what an administrator wants when records are pooled and assessed together.

## Per-doctor workflow, not a shared queue

Each clinician uses the scribe on their own consults. There is no central transcription desk, no shared backlog, no waiting on someone else to type up your morning. The note for your patient drafts for you, and you sign it.

This matters at scale. A shared documentation queue becomes a bottleneck the moment volume climbs. A per-doctor flow does not. Twenty doctors running the scribe in parallel is twenty independent streams, each finishing its own note in about two minutes.

For the clinic, that means documentation capacity scales with the number of doctors rather than the size of a back-office team. Add a specialist, and their notes get handled the same way from day one.

## Note consistency across specialties

Consistency does not mean identical. A cardiology note and a dermatology note should read differently. What a multi-specialty clinic wants is a shared structure underneath: the same sections, the same discipline about capturing history and plan, so records are comparable and complete.

| Specialty | Same backbone | Content follows the consult |
|---|---|---|
| General medicine | SOAP structure | Symptoms, exam, plan as discussed |
| Gynaecology | SOAP structure | Specialty history and findings |
| Orthopaedics | SOAP structure | Injury, exam, management |
| Paediatrics | SOAP structure | Growth, symptoms, guidance |
| ENT | SOAP structure | Focused exam and plan |

The clinician stays in charge of the content. The scribe just makes sure the structure is there and the note is legible and complete, every time, across every department.

## Volume without the evening backlog

The number that matters in a busy OPD is not per-note time in isolation. It is whether documentation keeps up with patient flow. When notes draft in about two minutes after each visit, the doctor finishes documenting roughly when the patient leaves, not at 9 pm after the last consult.

That changes the shape of the day. No stack of pending notes. No trade-off between seeing the next patient and finishing the last one's record. For a clinic pushing high daily volume, that is the difference between records that stay current and records that fall behind.

## No integration project, which matters for a multi-site group

Multi-specialty clinics often run mixed systems, a HMS here, a legacy tool there, spreadsheets somewhere. An ambient scribe that demands deep integration would be a project in itself.

This one does not. It is EHR-agnostic and works alongside whatever you already run, whether that is a standard HMS or something older. The clinician copies, pastes, or exports the finished note into your records. Nothing to rip out, no IT programme to schedule. If you are still choosing core systems, our [clinic management software rundown](../best-clinic-management-software-india/) and [EMR software guide](../emr-software-india-guide/) are worth a look, but the scribe does not depend on either.

## Data handling for Indian clinics

For a clinic handling this much patient data, the handling posture matters. Audio is processed in memory and discarded the moment the note drafts, so no recording is retained. Notes are encrypted in transit and at rest, belong to the practice, and can be exported or deleted at any time. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

This is built with DPDP-aligned data handling, and Indian clinic data can be handled with India data-residency as a posture. Record-keeping also needs to meet NMC expectations and, where relevant, MoHFW EHR Standards; the scribe supports that by producing consistent, structured records for the clinician to sign. For the data-protection detail, see the [DPDP guide for clinics](../dpdp-act-clinics-guide/).

## What the scribe does not do

Worth stating clearly. The scribe does not diagnose. It does not read scans or interpret lab studies. It structures what is said in the consult and drafts a note, ICD-10 suggestions, and a prescription. The prescription is a draft the clinician reviews and signs; it never sends to a pharmacy. The reading, the judgement, and the signature stay with the clinician. If you want the single-doctor view of how the drafting works, the [scribe overview for Indian doctors](../scribe-for-doctors-india/) covers it.

## The short version

A multi-specialty OPD lives or dies on consistent records at high volume. An ambient scribe drafts a structured note per consult, per doctor, in about two minutes, with the same backbone across every specialty and no shared queue to bottleneck. No integration project, DPDP-aligned handling, and the clinician always reviews and signs. It solves the consistency-versus-throughput problem without asking doctors to slow down.

Want to see it run across a few different specialties in your clinic? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and try it on real consults, check the [security page](../../security/) for how we handle data, or see India plans on the [pricing page](../../pricing/).

---

## AI Scribe and Medicare Documentation: E/M, MDM, and 2021 Rules
https://patientsquare.com/us/blog/ai-scribe-medicare-documentation-requirements/
Published 2026-07-27 · Tags: ai-scribe, medicare-documentation, e-m-coding, mdm, clinical-documentation

The 2021 E/M office-visit guidelines let you code by MDM or time. Here is how an ambient scribe helps you capture both, as a draft you verify and sign.

No. It drafts a note and suggests ICD-10 codes based on what was said. It does not guarantee correct E/M level selection or coding compliance, and it does not bill anything. You and your coding process own the final code and the signed record.

The 2021 revisions to the E/M office-visit guidelines changed how you pick a level for CPT codes 99202 through 99215: you now choose by medical decision making or by total time on the date of the encounter, not by counting history and exam bullets. An ambient AI scribe helps by drafting the note so the problems, data, and risk you actually discussed are written down, and by reflecting the time-relevant work of the visit, for you to verify. Patient Square hands that back about two minutes after the visit as a draft with ICD-10 suggestions. It does not guarantee coding compliance and it does not bill. You review, confirm the code, and sign.

> **Key takeaways**
> - The 2021 E/M guidelines let you code office visits (99202 to 99215) by MDM or by time.
> - An ambient scribe drafts the note so MDM elements discussed in the room are documented.
> - It reflects time-relevant activity, but you attest to the total time you actually spent.
> - ICD-10 codes come back as clinician-verified suggestions, not final billing decisions.
> - It never guarantees coding compliance and never bills; the signed record and code are yours.

_Source: CMS and AMA guidance on the 2021 E/M office-visit changes; see the sources below._

## What the 2021 E/M guidelines actually require

For office and outpatient visits, CMS and the AMA revised the coding framework effective January 1, 2021. The core change: level selection is based on either medical decision making or total time on the date of the encounter. History and exam still belong in a competent note, but they no longer set the level. This applies to CPT 99202 through 99215.

Medical decision making, under the revised guidelines, rests on three elements: the number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications from the visit and its management. Two of those three, at a given level, support that level.

Time, the alternative path, means total time spent on the date of the encounter, including non-face-to-face work like reviewing records and documenting the note, not just the minutes in the room. If you select by time, your documentation has to support the total time you are attesting to.

Both paths share a requirement that is easy to lose in the abstraction: the note has to actually reflect what happened. That is where documentation load and coding accuracy meet.

## How an ambient scribe helps you capture MDM

MDM is a documentation problem before it is a coding problem. If the problems you addressed, the data you reviewed, and the risk you weighed never make it into the note, the visit looks simpler on paper than it was in the room, and it may be under-documented for the level of work you did.

An ambient scribe drafts the note from the conversation, so the problems discussed, the labs or records you talked through, and the risk you raised with the patient get written down instead of forgotten. Patient Square returns that draft about two minutes after the visit. You read it against the MDM framework, confirm the elements are captured accurately, and sign.

The scribe is not deciding your MDM level. It is making sure the raw material for that decision is documented in the note. Whether the documentation supports a given level is your call, checked against CMS and AMA guidance. That distinction is the whole point of the next section.

## The line the scribe does not cross

Say this part clearly, because coding is where overpromising gets clinicians in trouble.

The scribe drafts a note and suggests ICD-10 codes. It does not guarantee coding compliance. It does not choose your E/M level for you. It does not bill anything and it has no connection to any claims system. The ICD-10 suggestions are clinician-verified: you confirm or change every one, and the diagnosis is yours.

The prescription draft follows the same rule. It reflects the plan you discussed in the visit; it does not screen for interactions, dosing, or contraindications, and it will not block or override anything. That review is yours to run, exactly as you run it today. It is a draft only. It never sends to a pharmacy. There is no e-prescribing. You prescribe through your own system.

None of this is a coding engine. It is documentation support that gives your coding process better raw material. The signed record, the E/M level, and the billing code stay with you and your compliance workflow.

## MDM elements and where the note comes from

Here is how the pieces line up, so you know what to verify.

| E/M path | Element | Where the draft note reflects it | What you verify |
| --- | --- | --- | --- |
| MDM | Problems addressed | Problems discussed in the visit | Count and complexity match the encounter |
| MDM | Data reviewed | Labs, records, studies you talked through | Documentation supports what you reviewed |
| MDM | Risk | Risk and management options discussed | Risk level reflects your clinical judgment |
| Time | Total time | Time-relevant activities of the encounter | Your attestation of total time on the date |
| Diagnosis | ICD-10 | Suggested from what was said | Confirm or change every code |

The pattern holds across every row: the scribe drafts, you verify. It never converts documentation into a guaranteed code.

## Time-based selection, and honest limits

If you code by time, the scribe can reflect the time-relevant work discussed in the visit, but it cannot know the total time you spent unless you tell it. Reviewing records before the patient arrived, documenting after they left, coordinating care later that day, those count toward total time on the date of service and they live partly outside the recorded encounter. Your time attestation is yours to make and document.

So treat any time figure in a draft as a starting point, not a total. The same caution applies to MDM: the scribe captures what was said, but it does not read your intent or your outside review unless it was part of the conversation. Verify against the actual visit.

## When this matters for your practice

If Medicare and commercial payers make up a real share of your panel, under-documented visits are lost work and over-documented ones are a compliance risk. Better documentation of MDM and time protects you in both directions, and an ambient scribe raises the floor on documentation without touching the coding decision.

For adjacent workflows, [how ICD-10 suggestions work](../ai-scribe-icd-10-suggestions-explained/) explains the code-suggestion side, [reducing claim denials through documentation](../ai-scribe-claim-denials-documentation/) covers the downstream billing angle, and [SOAP note quality](../ai-scribe-soap-note-quality/) goes into the note itself. On the trust and compliance side, the [HIPAA, BAA, and consent](../ai-scribe-hipaa-baa-consent/) page has the specifics.

Nothing here should be read as coding advice for your specific situation. The 2021 guidelines are published by CMS and the AMA, linked below, and your coder or compliance lead is the authority on how they apply to your visits. Want to see the documentation half in practice? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we will walk a real office visit through to a draft note with ICD-10 suggestions, in about two minutes, that you would then verify and sign.

---

## Best EHR for Family Practice: A 2026 Buyer Guide
https://patientsquare.com/us/blog/best-ehr-for-family-practice/
Published 2026-07-27 · Updated 2026-08-29 · Tags: comparison, primary-care, buying, ehr

Compare family-practice EHR options with a requirements matrix, live workflow test, complete quote, certification check, and migration plan.

There is no defensible universal winner. The right EHR is the one that passes the practice's tests for longitudinal charting, medication and order workflows, results, referrals, patient communication, billing, reporting, security, certification needs, implementation, support, and data exit. Compare current vendor demonstrations and contracts against those requirements.

The best EHR for a family practice is not the product with the loudest ranking badge. It is the product that holds up through a normal clinic day, supports the practice's reporting and payment obligations, protects its records, and leaves a workable exit if the relationship ends.

Elation, athenahealth, and eClinicalWorks are reasonable names to put on an initial shortlist because each publishes an ambulatory or primary-care offering. Patient Square belongs in a different comparison when a practice wants an EHR bundled with ambient documentation. Inclusion here is not a ranking, and this guide does not use third-party price ranges.

> **Key takeaways**
>
> - Write requirements before booking demonstrations.
> - Use the same patient scenarios and scoring sheet with every vendor.
> - Compare complete written quotes, not headline prices or market ranges.
> - Verify the exact product and version in the official Certified Health IT Product List when certification matters.
> - Put migration, support, renewal, and data exit into the decision.

## Build the family-practice requirements list

Family medicine needs a longitudinal view. A useful test follows the patient across preventive care, acute problems, chronic conditions, medicines, outside results, referrals, and follow-up. The practice also has to run appointments, messages, claims or invoices, reporting, and record requests around that clinical work.

Separate must-haves from preferences. A sample first pass:

| Area | Questions for the practice |
|---|---|
| Chart | Can clinicians understand the patient's story without hunting across screens? |
| Medicines | How are reconciliation, refills, allergies, and prescription review handled? |
| Orders and results | Who sees an incoming result, acknowledges it, and closes the follow-up loop? |
| Referrals | Can staff track an outgoing referral and the returned consult? |
| Messaging | Can the practice route patient questions to the right person and document the response? |
| Billing | Does the workflow fit the practice's payers, contracts, and staff model? |
| Reporting | Which quality, operational, and financial reports are required? |
| Security | Do access controls, logs, backups, BAA terms, and incident duties meet policy? |
| Exit | Can the practice retrieve usable clinical and administrative records on a defined timeline? |

Do not let a demo add requirements just because a feature looks polished. Start with the work your team already has to complete.

## Put shortlisted vendors through the same visit

Ask Elation, athenahealth, eClinicalWorks, Patient Square, and any other candidate to show the same cases in the product being quoted. A vendor-guided tour is useful, but it should not replace your script.

Use a preventive visit with several care gaps, a chronic-disease follow-up with a medication change, an acute visit that needs a test and follow-up, and an outside result that arrives after the encounter. Include a patient message and a corrected note.

Watch who clicks, who waits, and who owns the next task. Record:

1. Time to find the relevant history.
2. Number of screens and handoffs needed to finish the visit.
3. How the clinician reviews and signs documentation.
4. How staff know a result, referral, or message is still open.
5. What happens after an error or duplicate record.
6. Which steps depend on an add-on, interface, or separate service.

Have clinicians, front-desk staff, billing staff, and the privacy or security lead score their own work. One role cannot judge the whole system.

## Compare complete quotes

Ask for a current written quote from every vendor. The quote should state:

- the unit being charged, such as clinician, user, location, encounter, claim, or percentage;
- the initial and renewal term;
- included EHR, practice-management, billing, patient-engagement, and documentation modules;
- implementation, data conversion, interfaces, training, and project management;
- support hours, response targets, and paid support tiers;
- transaction, clearinghouse, messaging, storage, tax, and other variable charges;
- renewal increases, termination notice, and data-export costs.

If a vendor cannot state an item, mark it unresolved. Do not fill the gap with an industry average.

Patient Square publishes Copilot at a $119 per-clinician monthly equivalent on annual billing or $149 month to month. Patient Square EHR is included from that tier. The [pricing page](/us/pricing/) is the source of truth, and the same quote checklist still applies.

## Verify certification and program fit

The ASTP/ONC Certified Health IT Product List is the authoritative public listing for certified health IT. Search the exact developer, product, and version. Review the certification status, criteria, disclosures, and compliance activity shown for that listing.

Certification is not a general quality score, and one vendor name may have several listings. It also does not prove that a product supports every operational feature your practice needs. Confirm the federal and payer program requirements that apply to your clinicians, then verify the specific configuration being purchased.

Do this check near contract signature as well as during the shortlist. Product versions and requirements can change.

## Evaluate ambient documentation as its own workflow

An ambient scribe can reduce typing, but it does not remove the clinician's responsibility for the record. Test note completeness, material corrections, review time, coding suggestions, medicine details, consent, audio handling, and final approval.

AI Medical Scribe by Patient Square produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The prescription draft is not sent to a pharmacy. Patient Square says the draft is normally ready about two minutes after the visit.

Patient Square EHR is bundled from the Copilot tier in Practice Copilot. A practice can use that route or keep an existing EHR alongside Patient Square. No named-EHR integration, write-back, or automatic filing is promised. If the existing EHR remains the system of record, test the exact record-transfer process and destination.

## Plan migration and exit before signing

Ask what the vendor will import, what it will not import, how long conversion takes, how the practice validates the result, and who fixes errors. Include scanned records, discrete data, attachments, task history, audit information, billing records, and patient access needs.

Then ask the same questions in reverse. What files and structured data can the practice receive at termination? What will they cost? How long will access remain? Who certifies deletion after the practice has a usable copy?

A difficult exit can erase years of apparent savings. Put the answers in the contract.

## Choose the product that passes

The final comparison should be unglamorous: requirements met, test results, unresolved risks, complete cost, contract terms, and references from practices that resemble yours. That record will survive a leadership change better than a ranking.

If you want to include Patient Square in the clinical-documentation and bundled-EHR test, Request your 7-day trial. Keep the same bar for every candidate.

---

## Kareo (Tebra) EHR Pricing 2026: What It Actually Costs
https://patientsquare.com/us/blog/kareo-ehr-pricing/
Published 2026-07-27 · Tags: pricing, comparison, ehr, small-practice

Kareo is now Tebra, and pricing is quote-only. Here's what the EHR really costs by module, the fees that stack, and how it compares to a transparent bundled EHR.

Kareo is now part of Tebra, and pricing is quote-only, not published. Per 2026 third-party reviews, the EHR plus practice management runs roughly $80 to $100+ per provider per month, billing-only is lower at about $10 to $50, and the patient marketing suite is a separate charge near $200 to $400 a month. There's also a one-time setup fee around $500 and a $50 annual per-user fee, per those reviews. You'll need a demo to get your actual number.

Kareo is now Tebra, and its pricing is quote-only, so there's no single published number. Per 2026 third-party reviews, the EHR plus practice management runs roughly $80 to $100+ per provider per month, with billing-only lower and a separate patient marketing suite that adds $200 to $400 a month. On top of that sit a one-time setup fee near $500 and a $50 annual per-user fee. If you want a transparent all-in figure to compare against, our bundled EHR is published on the [pricing page](/us/pricing/): $119 per clinician per month on the annual Copilot plan.

> **Key takeaways**
>
> - Kareo merged into Tebra; pricing is custom-quote, not published, per EHR Source's 2026 review.
> - Reported EHR plus PM cost is roughly $80 to $100+ per provider per month; the marketing suite is a separate $200 to $400 a month.
> - Watch the stacking fees: about $500 setup, $50 annual per user, and a $75 application fee for controlled-substance e-prescribing, per 2026 reviews.
> - Practice Copilot publishes its price and bundles an ambient scribe with the EHR at $119 per clinician per month on the annual Copilot plan.

## First, the name: Kareo is Tebra now

If you're searching for Kareo pricing in 2026, you're searching for Tebra. Kareo merged with PatientPop to form Tebra, and the EHR sells under that name today. Everything below reflects the combined platform. The old Kareo brand still shows up in reviews and search, which is why the numbers can feel scattered; they're describing one product under two names.

That matters for budgeting because Tebra bundles more than the old Kareo EHR did. The practice-management and patient-marketing pieces are where the cost quietly grows.

## What Tebra (Kareo) actually costs by module

Tebra doesn't publish a price. Per EHR Source's 2026 review, "Tebra does not publish transparent pricing and requires a custom quote." So the figures below come from third-party reviews, not a rate card, and your quote will depend on provider count, modules, and claim volume.

Here's the module breakdown those reviews report:

- **Billing only:** roughly $10 to $50 per month.
- **EHR plus practice management:** about $80 to $100+ per provider per month.
- **Patient marketing suite:** a separate charge near $200 to $400 a month.
- **Managed billing service:** a percentage of collected revenue, commonly cited around 4 to 8 percent, rather than a flat fee.

The base EHR is genuinely among the lower-cost entry points in the market. That's the honest strength. The complication is that the "affordable EHR" framing gets shaky once you add the marketing suite, which reviewers note can push total cost toward pricier competitors. When you price Tebra, price the modules you'll actually use, not the base line item.

## The fees that stack on top

Monthly module cost isn't the whole bill. Per 2026 reviews, Tebra layers on:

- A one-time implementation and setup fee around $500.
- A $50 annual fee per authorized user.
- A one-time $75 application fee if you e-prescribe controlled substances.

None of these is unusual for the category. The point is that they're easy to miss when you compare a base monthly rate against another vendor's all-in number. A $90 base rate with $500 setup, $50 per user a year, and a $300-a-month marketing suite is a very different budget than $90 flat. Add the pieces before you compare.

## Is Tebra (Kareo) right for your practice?

To be fair to Tebra: it's a reasonable pick for a specific kind of practice. Reviews recommend it for solo practitioners, startups, and cash-pay or concierge practices, and it's ONC-certified, which matters for interoperability programs. If you want a low base-cost EHR and you actually want the patient-acquisition and marketing tooling, Tebra's bundle can make sense. The marketing suite isn't padding for a practice trying to grow its patient base; it's the reason to buy.

Where it gets harder is transparency and documentation load. Quote-only pricing makes clean comparison shopping slower, and like most EHRs on this list, Tebra stores your chart but doesn't write your note for you. If your practice's real pain is finishing charts after hours, the marketing suite doesn't touch that.

## The transparent-price alternative for small practices

Here's where we come in, and we'll be direct about it. We build [Practice Copilot](/us/products/practice-copilot/), and we publish the price. The AI Medical Scribe by Patient Square, the ambient scribe module inside it, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. On the Copilot plan, that scribe comes with a bundled EHR, at $119 per clinician per month on the annual plan. No quote, no setup fee to negotiate, no marketing suite billed on the side.

For a small independent practice, the contrast is the point. Tebra's base EHR may land in a similar range, but you learn the real number after a demo, and the scribe, if you want one, is a separate line. Practice Copilot puts the number on the page and the scribe in the plan. That's a cleaner comparison to run when you're a two-provider clinic watching every recurring cost.

We're not saying Tebra is a bad product. For a growth-focused cash-pay practice that wants the marketing tools, it's a fair choice. We're saying that if you want a published all-in price with an ambient scribe already included, ours is easier to budget against. [See the pricing](/us/pricing/), or book a short demo and we'll run the scribe on your own visits.

## Bottom line on Kareo (Tebra) pricing

Kareo-now-Tebra costs roughly $80 to $100+ per provider per month for the EHR plus practice management, per 2026 reviews, with billing-only cheaper and the marketing suite a separate $200 to $400 a month. Setup, per-user, and e-prescribing fees stack on top, and the whole thing is quote-only, so your real number comes after a demo. It's a fair pick for a growth-minded cash-pay practice that wants the marketing tools.

If you want a published all-in price and an ambient scribe already in the plan, that's the case for a transparent bundled EHR. Ours is on the [pricing page](/us/pricing/), no sales call required to read it.

## Frequently asked questions

The FAQ above answers the recurring ones: the real cost by module, whether Tebra publishes pricing, the extra fees, and how the total compares to a transparent bundled EHR. For the full Practice Copilot breakdown, see the [pricing page](/us/pricing/); a demo shows the scribe on your own note types.

---

## OPD Management Software Price in India: A 2026 Cost Breakdown
https://patientsquare.com/in/blog/opd-management-software-price-india/
Published 2026-07-27 · Tags: india, pricing, opd-software, clinic-software, cost

OPD management software pricing for Indian outpatient clinics in 2026: per-doctor vs per-clinic models, typical ranges, hidden costs, and where Patient Square's EHR fits.

Most cloud OPD software for Indian clinics is priced per doctor per month and lands between ₹800 and ₹2,500 per doctor. Basic scheduling-and-records tools sit at the lower end; AI-assisted plans that add ambient notes and an EHR sit higher. Patient Square's Copilot tier, which bundles the AI Copilot EHR, is ₹2,399 per clinician per month on annual billing, ex-GST (about ₹2,831 with 18% GST).

OPD management software in India is almost always priced per doctor per month, and for a cloud tool that number runs roughly ₹800 to ₹2,500 per doctor depending on what's inside. Bare scheduling and records sit at the bottom. Plans that add ambient AI notes, ICD-10 suggestions, and a full EHR sit at the top, and that's where the real value is for a busy OPD. Patient Square's Copilot tier bundles the AI Copilot EHR at ₹2,399 per clinician per month on annual billing, ex-GST, so you're not paying separately for the records system. [See the India pricing](../../pricing/) or book a demo if you'd rather watch it run on a real OPD day.

> **Key takeaways**
>
> - OPD software in India is priced per doctor per month, roughly ₹800 to ₹2,500 depending on features.
> - The gap between cheap and mid-priced tools is the EHR and AI notes. Scheduling-only tools are cheap because they do less.
> - Patient Square Copilot bundles the AI Copilot EHR at ₹2,399/clinician/month (annual, ex-GST), about ₹2,831 with 18% GST.
> - Hidden costs to check: migration fees, per-message charges, separately-billed modules, onboarding fees, and GST on top.
> - Per-doctor pricing scales cleanly: a 3-doctor clinic pays three seats, no surprise per-location licence.

## How OPD software is priced in India: per doctor, per month

The default model for cloud OPD software here is per doctor per month. You pay a seat for each doctor who uses the system. A three-doctor clinic pays three seats; add a doctor, add a seat. It's clean to budget and it scales with the practice, which is why almost every Indian clinic tool uses it, Patient Square included.

The other model you'll meet is per-clinic or per-location flat pricing, usually in on-premise or enterprise deals, sometimes with a bed or user cap baked in. Flat pricing can look cheaper for a big practice and more expensive for a solo doctor. For most OPD practices, per-doctor is the fairer and more predictable structure.

What moves the per-doctor number up or down is the feature set. That's the real story of OPD pricing, so let's put it in a table.

## What you get at each OPD price band

Here's the honest breakdown of what a per-doctor monthly rate buys in 2026. Ranges are ballpark from published clinic-software pricing, not a fixed rate card.

| Per-doctor / month (ex-GST) | Typical feature set | Best for |
|---|---|---|
| ₹800 to ₹1,200 | Scheduling, queue, basic records, OPD billing, Rx printing | Solo doctor who mostly needs a diary and bills |
| ₹1,200 to ₹2,000 | Above plus a proper EMR/EHR, reminders, reporting | Multi-doctor clinic that wants records done properly |
| ₹2,000 to ₹2,500+ | Above plus ambient AI notes, ICD-10 suggestions, front-office automation | Busy OPD where documentation is eating the day |

The pattern is simple. The cheap band is cheap because it does less: it schedules and bills, and you still type your own notes. The mid band adds a real records system. The top band adds the AI that writes the note for you, which is the part that actually gives you time back on a 40-patient morning.

Patient Square sits in that top band with a difference worth naming: the EHR is bundled, not a separate line. More on that below. If time-per-patient is your bottleneck, book a demo and see a Hindi consult turn into a review-ready note.

## Where the Patient Square EHR fits, at ₹2,399

The thing to understand about OPD pricing is that many vendors quote you a scheduling-and-billing price, then charge separately for the EMR or EHR. Two invoices, two renewals. Patient Square doesn't split them.

Here are the three Practice Copilot tiers, per clinician per month, ex-GST, with 18% GST added on the invoice:

| Tier | Monthly (ex-GST) | Annual rate (ex-GST) | What you get |
|---|---|---|---|
| Assist | ₹1,999 | ₹1,599 | AI Medical Scribe, ICD-10 suggestions, Rx drafts, scheduling |
| **Copilot** | ₹2,999 | **₹2,399** | Assist plus front-office automation and the **AI Copilot EHR bundled** |
| Autopilot | ₹4,999 | ₹3,999 | Copilot plus AI Receptionist, follow-ups, priority support, ROI analytics |

On Copilot at ₹2,399 per clinician per month (annual), the EHR is included. That means ambient AI notes, ICD-10 suggestions, prescription drafts, front-office automation, and the records system are one price, in Hindi and other Indian languages. Compared with buying a scheduling tool plus a separate EMR licence (often ₹12,000 to ₹18,000 per doctor a year on top), the bundled maths usually comes out ahead for an OPD practice that wants both.

With 18% GST, Copilot is about ₹2,831 per clinician per month on the invoice. Assist, the documentation-first tier without the EHR, is ₹1,599 annual (about ₹1,887 with GST). Pick Assist if you already run records elsewhere and only want the scribe; pick Copilot if you want the EHR folded in.

## Hidden costs that inflate the real OPD bill

The monthly rate is rarely the whole bill. A few line items hide off the headline, so dig them out before you compare vendors. Data migration off your old system can carry a one-time fee, so ask whether it's included. SMS and WhatsApp reminders are sometimes billed per message on top of the seat price, which adds up fast on a high-volume OPD. Lab, pharmacy, teleconsultation, and analytics are often add-ons rather than part of the base seat. Some vendors charge for setup and staff training. And the headline is ex-GST, so 18% lands on the invoice.

Ask every vendor for an all-in first-year number: seats plus migration plus messages plus modules plus onboarding plus GST. That's the figure to compare, not the sticker. For the wider view on what an OPD practice actually needs beyond price, the [OPD software buyer guide](../opd-software-for-clinic-india/) and the [best clinic management software roundup](../best-clinic-management-software-india/) go deeper on features.

## Match the OPD price band to your real bottleneck

Match the band to your real bottleneck, not the longest feature list.

1. If your only need is a diary and OPD bills, the ₹800 to ₹1,200 band is honest value. Don't overbuy.
2. If your records are a mess and you want them done properly, the mid band with a real EHR is the fix.
3. If documentation is eating your OPD day, the top band with ambient AI notes is where the time comes back, and a bundled EHR keeps it to one price.
4. Whichever band, get the all-in first-year number and confirm GST treatment before you sign.

For most multi-doctor OPD clinics that want the note written for them and the records handled in one place, Copilot at ₹2,399 per clinician per month (annual, ex-GST) is the fit. Book a demo and run it on a real clinic day before you decide.

---

## AI Medical Scribe for Gynaecology & Obstetrics Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-gynaecology-clinics-india/
Published 2026-07-26 · Tags: gynaecology, obstetrics, ai-medical-scribe, antenatal-care, india

How an ambient AI scribe drafts Indian gynaecology OPD and ANC notes, including LMP, EDD, obstetric history, and sensitive-data handling.

Yes. If you dictate gravida, para, LMP, and EDD during the consultation, the scribe transcribes and structures them into the note. You review the values and sign; the calculation and the record stay yours.

Gynaecology and obstetrics run on histories that are both detailed and private. A single ANC visit touches gestational age, blood pressure, weight, fundal height, foetal movements, and a plan, while a routine gynaec consultation covers menstrual history, contraception, and often something the patient would rather not repeat to a receptionist. An ambient AI scribe drafts a structured note from the spoken consultation and returns it about two minutes after the visit, so the record gets written without you turning to a keyboard mid-conversation. You review the draft and sign. Because this data is sensitive, how it is handled matters as much as how it is captured, and that is treated as a first-order concern here.

> **Key takeaways**
> - The scribe transcribes and structures obstetric and gynaec histories you dictate, including LMP, EDD, gravida, and para.
> - It drafts ANC visit notes from your narration; it does not interpret ultrasound scans or lab reports.
> - Sensitive data is handled with encryption, in-memory audio that is discarded after drafting, and an available India data-residency posture. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - Prescription output is a draft reflecting what you said. It never reaches a pharmacy, and the pregnancy-safety call before you sign stays with you.
> - ABDM integration is on the roadmap for AI Medical Scribe by Patient Square, not shipped.

_Source: Product behaviour of AI Medical Scribe by Patient Square._

## How an ambient scribe fits a gynaecology visit

Start with a routine gynaec OPD. A patient describes irregular cycles for four months, some spotting, and asks about contraception. You take a menstrual history, ask about the last cycle, examine as needed, and advise. Much of this is talking, and the note that comes out of it needs to hold the specifics: cycle length, LMP, contraceptive history, the plan.

An ambient scribe captures that conversation and structures it into a draft. When you say "LMP fifteen days ago, cycles previously regular now irregular for four months, no contraception currently," those details land in the history section. You are consulting as usual, and the note assembles from your words for you to review. Nothing enters the permanent record until you read the draft and sign.

For a clinic that also runs obstetrics, the same flow applies to ANC, where the data is more structured and repeats visit to visit.

## What a gynaecology and obstetrics scribe must capture

Obstetric notes carry shorthand that is second nature to you and opaque to a generic template. The scribe should hold it as you dictate it:

| Element | What you narrate | What lands in the draft |
|---|---|---|
| Obstetric score | "G2 P1 L1 A0" | Gravida, para, living, abortions as spoken |
| Dates | LMP, EDD, gestational age | The dates you dictated, structured |
| Menstrual history | Cycle length, regularity, flow | Menstrual history section |
| ANC vitals | BP, weight, fundal height, foetal movements | Values you narrated, recorded |
| Examination | Per-abdomen, per-speculum, per-vaginal as done | Findings as you spoke them |
| Plan | Investigations, medication, next visit | Plan section, prescription drafted separately |

The obstetric score and the dates are where errors creep into hand-written notes under time pressure. Dictating them into a scribe is faster and gives you a clear line to check. The scribe records what you say. It does not calculate the EDD for you or decide the gestational age; you state it, and the draft holds it for your review.

## The scribe captures, it does not interpret

This is the honest boundary in a specialty full of imaging and reports. A gynaec and OB practice lives on ultrasound, on blood work, on Pap and biopsy results. The temptation for any AI vendor is to claim the software can read a scan and tell you the findings. AI Medical Scribe by Patient Square does not read scans or reports, and does not claim to.

The reading stays yours. You look at the ultrasound, you read the report, and you decide. The scribe captures what you say about it. So a note might record "USG shows single live intrauterine gestation corresponding to twelve weeks, as reported," because that is what you dictated from the report in front of you, not because the tool interpreted an image.

Keeping that line clear protects both the patient and you. The clinical judgement, and the legal responsibility for it, belong to the signing clinician.

## Privacy and DPDP-aligned handling of sensitive data

Gynaecological and obstetric information is among the most sensitive a clinic holds. It deserves handling that reflects that, not an afterthought.

Here is how the data is treated. Consultation audio is processed in memory and discarded the moment the note drafts, so no recording of a private consultation is retained. Notes are encrypted in transit with TLS and at rest with AES-256. They belong to your practice, and you can export or delete them at any time. An Indian clinic can be set up with an India data-residency posture, so the data stays handled within the country. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

India's Digital Personal Data Protection Act 2023 is the governing statute for personal data, and health data falls squarely within its scope. AI Medical Scribe by Patient Square is built with DPDP-aligned data handling: encryption, consent-conscious processing, and a data-residency posture. To be precise, there is no such thing as being "DPDP certified," and no vendor should claim it. What exists is a way of handling data that aligns with the Act, and that is what is described here. Our [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) goes through the obligations in plain terms, and our note on [data residency in India](../ai-scribe-data-residency-india/) covers where notes live.

## Prescription drafts in obstetric care

Prescribing in pregnancy carries obvious weight. A drug that is fine in a non-pregnant patient may be contraindicated in the first trimester. This is exactly where your clinical judgement earns its keep, and it is exactly the judgement the scribe does not try to make for you.

The scribe produces a prescription draft from your consultation, and only a draft. It writes out the drug, the dose, and the instructions you dictated so you are not retyping them. It never sends to a pharmacy and never dispenses. What it does not do is screen for drug-interaction, renal, or pregnancy concerns; there is no automated check, no flag, no block. In an ANC context, the pregnancy-safety call is one you would never want to hand to software, and you don't have to: you read the draft, weigh the trimester and the clinical picture, correct anything that needs correcting, and sign.

The decision is always yours. The draft saves the typing; the safety check is you.

## Record-keeping and continuity in ANC

Antenatal care is continuity by definition. Each visit builds on the last, and the record has to show the trajectory: BP over time, weight gain, fundal height progression, investigations done. A missing or illegible ANC note is a real gap, both clinically and medico-legally.

A structured, dated note per visit is what an ambient scribe helps you produce consistently, which matters across a full ANC course. NMC's record-keeping expectations point to this same need for legible, contemporaneous notes. For how AI-drafted notes sit within your record-keeping duties, see our [NMC record-keeping note](../nmc-record-keeping-ai-scribe/), and for medico-legal considerations specifically, our piece on [medico-legal documentation in India](../ai-scribe-medico-legal-documentation-india/). What goes in the record, and how long you keep it, stay your clinic's responsibility.

## See it on a real ANC and OPD mix

The way to judge a scribe for this work is to run it across your own visit types, private histories and all. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, dictate a routine gynaec consult and an ANC visit, and see how the drafts read. The [security page](../../security/) details encryption, residency, and deletion, which matter more here than in most specialties. The [pricing page](../../pricing/) has India plans. See how it handles your most sensitive records before it touches one.

---

## AI Medical Scribe for Bilingual & Spanish-Language Visits
https://patientsquare.com/us/blog/ai-scribe-multilingual-visits-us/
Published 2026-07-25 · Tags: ai-scribe, bilingual-visits, spanish-language, interpreter, clinical-documentation

Many US clinics see Spanish-speaking patients and interpreter-mediated visits. Here is how an ambient scribe handles bilingual encounters, and its honest limits.

No. A qualified medical interpreter is for the clinical conversation with the patient and is a patient-safety and compliance requirement in many settings. The scribe documents the encounter; it does not interpret between you and the patient during the visit.

Plenty of US clinics see Spanish-speaking patients every day, and many of those visits run through a qualified interpreter. So a fair question about any ambient scribe is: what does it do when the encounter is not all in English? Short version: Patient Square listens to the visit and drafts a structured English note about two minutes after you finish, including encounters that crossed languages or used an interpreter. It does not interpret between you and the patient, and it does not replace a medical interpreter. The note is a draft you review and sign, with names and medications worth an extra look.

> **Key takeaways**
> - Many US visits involve Spanish-speaking patients or a qualified interpreter; the scribe documents them.
> - The scribe does not interpret the clinical conversation and does not replace a medical interpreter.
> - The note comes back in English for you to review and sign.
> - Verify patient names, medication names, and dosages carefully, especially in bilingual encounters.
> - We do not publish an accuracy percentage; treat every draft as a draft.

_Source: audio handling described on the [security page](../../security/)._

## What a bilingual US visit actually looks like

There is no single shape. Sometimes you speak Spanish yourself and the whole visit runs in Spanish. Sometimes a family member is present and switching between languages. Often a qualified interpreter joins in person, by phone, or by video, and the conversation moves patient, interpreter, clinician, and back again. Language access is a legal and safety obligation in many US settings, not a nicety, so these visits are common and they are not going away.

That mix is the hard part for documentation. The clinical facts live across two languages and sometimes three voices. A note has to pull the medically relevant content out of all that and land it in English, accurately, for the record.

An ambient scribe helps with the documentation half of that problem. It does not help, and should not try to help, with the interpretation half. Those are different jobs.

## How an ambient scribe handles interpreter-mediated encounters

Patient Square listens to the encounter and drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after you finish. That includes visits where an interpreter is present. The scribe is documenting what happened; it is not the channel through which you and the patient understand each other.

Keep the roles clean. The interpreter carries the clinical conversation in real time. You practice medicine. The scribe drafts the note afterward. If you drop the interpreter and lean on the scribe to bridge the language gap during the visit, you have misused the tool and created a safety problem. The scribe is downstream of the conversation, not part of it.

The finished note comes back in English, which is what your chart and your colleagues need. A human scribe documenting an interpreted visit would do the same: the conversation crosses languages, the record is in English.

## The honest limits

This is the part vendors skip, so here it is plainly.

The note is in English. If the visit happened partly in Spanish, the scribe is producing an English clinical note from a multilingual conversation, and that is a harder task than a single-language visit. Read the draft against what you remember of the encounter.

Names and medications need verification. In any note, patient names and drug names are the most error-prone fields, because they are proper nouns and they sound alike. Across languages, that risk goes up. Confirm the patient's name, every medication name, and every dose before you sign. Do not skim those fields.

We do not publish an accuracy number. Be wary of any scribe that quotes one language-accuracy figure as if it settles the question, because accuracy depends on audio quality, accents, crosstalk, and the specific vocabulary of the visit. The safer posture is the correct one anyway: it is a draft, you review it, you own the signed record.

## What to check in a bilingual-visit note

A quick review discipline catches most of what matters.

| Field to check | Why it is higher-risk in a bilingual visit | What to do |
| --- | --- | --- |
| Patient name | Proper nouns transcribe poorly, more so across languages | Confirm spelling against the chart |
| Medication names | Drug names sound alike and cross languages badly | Verify each against your own order |
| Dosages and units | Numbers and units are easy to mishear | Read every dose before signing |
| History details | Content moved through an interpreter | Check the draft against your recollection |
| Plan and follow-up | Instructions may have been relayed, not stated directly | Confirm the plan reflects what you decided |

This is not busywork specific to Patient Square. It is the review any signing clinician owes any draft, tightened a notch for encounters that crossed languages. The reading stays yours.

## Where the scribe fits, and where it does not

It fits the documentation load. A clinic that sees Spanish-speaking patients all day still has to chart every one of those visits in English, and doing that from memory after a long interpreted encounter is slow and lossy. The scribe drafts it in about two minutes so you review instead of reconstruct.

It does not fit the interpretation need. If your clinic's language access plan requires a qualified interpreter, that requirement stands. The scribe changes nothing about it. Anyone selling an ambient scribe as an interpreter replacement is selling you a compliance and safety risk.

Because Patient Square is EHR-agnostic, none of this depends on your system. You copy or paste the English note into Epic, athenahealth, eClinicalWorks, or whatever your clinic runs. Related reading: [primary care documentation with an ambient scribe](../ai-scribe-for-primary-care/), [SOAP note quality](../ai-scribe-soap-note-quality/), and the [HIPAA, BAA, and consent](../ai-scribe-hipaa-baa-consent/) page for how consent works when you are recording a visit.

## Try it on a real bilingual encounter

The best test is your own hardest visit. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it against an interpreter-mediated encounter or a Spanish-language annual exam. You will see the English note come back in about two minutes, and you will see exactly which fields you would double-check before signing. If you want to compare tools first, [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) covers the questions worth asking.

---

## Hospital Management Software Prices in India (2026)
https://patientsquare.com/in/blog/hospital-management-software-price-india/
Published 2026-07-25 · Updated 2026-08-27 · Tags: india, pricing, hospital-software, cost, hms

See 2026 hospital management software costs in India, including price drivers by module, bed count, deployment, and implementation scope.

Hospital management software in India has no single sticker price. The total changes with bed count, locations, modules, users, hosting, interfaces, migration, devices, implementation, support, and tax. Ask each vendor for a written, line-item year-one total and steady-state annual cost before comparing quotes.

Hospital management software in India doesn't have one price, and any vendor who gives you a single number without asking about your beds and modules is guessing. Small clinics on a cloud HMS with core modules often pay ₹15,000 to ₹1,00,000 a year. Mid-size hospitals run ₹1,00,000 to ₹8,00,000. Large multi-speciality setups with IPD, pharmacy, lab, and on-premise licences can cross ₹10,00,000 once you add implementation. If you run a clinic or OPD practice rather than a full hospital, the cheaper and better-fit path is per-clinician software: Patient Square's [Practice Copilot pricing](../../pricing/) starts from ₹1,599 per clinician per month on annual billing, ex-GST, with the AI Copilot EHR bundled from the ₹2,399 tier. Hospital Copilot, for larger facilities, is priced on a demo.

> **Key takeaways**
>
> - HMS price scales with four levers: modules switched on, beds or users licensed, cloud vs on-premise, and one-time implementation. There is no flat rate.
> - Ballpark bands (annual): small clinic ₹15,000 to ₹1,00,000; mid-size hospital ₹1,00,000 to ₹8,00,000; large multi-speciality ₹10,00,000-plus with on-premise licences.
> - Cloud is cheaper to start and easier to budget; on-premise costs more upfront and carries 15 to 20% AMC a year. Compare on 3-to-5-year TCO.
> - Software is quoted ex-GST; add 18% GST on the invoice. Make every vendor show the ex-GST figure.
> - Running a clinic, not a hospital? Per-clinician software fits better. Patient Square Copilot bundles the EHR from ₹2,399/mo (annual) + GST.

## What actually drives the price of an HMS in India

The quote you get is built from four levers, and vendors turn them quietly. Know them and you can read any proposal.

**Modules.** A basic OPD and billing setup is one price. Switch on IPD (admissions, wards, bed management), a pharmacy store with batch and expiry tracking, a lab with LIMS, radiology with PACS hooks, a blood bank, an operation-theatre module, and each one adds licence cost. Most Indian hospitals buy far more module than they run. If your lab sends out most tests, a full in-house LIMS module is dead weight.

**Beds or users.** Clinic and OPD tools price per doctor or per user per month. Hospital HMS often prices per bed, or in tiers keyed to bed count. A 30-bed nursing home and a 300-bed multi-speciality are different line items entirely, and the per-bed rate usually drops as bed count climbs.

**Deployment.** Cloud is a subscription: monthly or annual, updates included, no server to buy. On-premise is a perpetual licence plus a server plus an annual maintenance contract. The upfront gap is large; the multi-year gap is smaller.

**One-time costs.** Implementation, data migration from your old system, on-site training, and any customisation. These land once but they're real, and they're the numbers most likely to be missing from a headline price. Ask for them in writing.

That's the shape of every HMS quote in the country. If you'd rather skip the module-stacking exercise for a clinic-sized practice, book a demo and we'll show you what a per-clinician plan covers instead.

## Typical India HMS price ranges in 2026

Here's the honest lay of the land. These are ballpark bands from published clinic-software pricing and common market quotes, not a rate card, and your number depends on the four levers above.

| Facility type | Typical annual cost (ex-GST) | What it usually covers | Deployment |
|---|---|---|---|
| Solo clinic / small OPD | ₹15,000 to ₹60,000 | Records, scheduling, OPD billing, prescriptions | Cloud subscription |
| Nursing home (10 to 30 beds) | ₹60,000 to ₹2,00,000 | Above plus basic IPD, pharmacy, lab | Cloud or light on-premise |
| Mid-size hospital (30 to 100 beds) | ₹2,00,000 to ₹8,00,000 | Full IPD, pharmacy, lab, radiology, billing, TPA/claims | Cloud or on-premise |
| Large multi-speciality (100+ beds) | ₹8,00,000 to ₹25,00,000+ | Everything above plus OT, blood bank, HR, deep customisation | Usually on-premise + AMC |

Two cautions on that table. First, on-premise headline licences don't include the server, the AMC (15 to 20% a year), or the implementation, so the real first-year outlay is higher than the licence line. Second, per-doctor clinic tools sit well below even the small-clinic band: published clinic software like Practo Ray and HealthPlix runs roughly ₹12,000 to ₹18,000 per doctor per year, and a per-clinician AI plan like Patient Square's lands in the same wallet while adding the scribe and EHR.

## Where Patient Square fits, and where it doesn't

Straight answer: Patient Square is built for clinics and OPD practices, not for running a 200-bed hospital's IPD and blood bank. If that's your building, a full HMS is the right buy and we'll say so.

For a clinic, solo doctor, or multi-doctor OPD practice, the maths is different. Patient Square's Practice Copilot is priced per clinician per month, ex-GST, with 18% GST added:

| Tier | Monthly (ex-GST) | Annual rate (ex-GST) | What you get |
|---|---|---|---|
| Assist | ₹1,999 | ₹1,599 | AI Medical Scribe, ICD-10 suggestions, Rx drafts, scheduling |
| **Copilot** | ₹2,999 | **₹2,399** | Assist plus front-office automation and the **AI Copilot EHR bundled** |
| Autopilot | ₹4,999 | ₹3,999 | Copilot plus AI Receptionist, follow-ups, priority support, ROI analytics |

The line that matters for a cost comparison: the EHR isn't a separate ₹15,000-a-year licence here. It's inside the Copilot tier. So a clinic on Copilot at ₹2,399 per clinician per month (annual) gets ambient AI notes, ICD-10 suggestions, prescription drafts, front-office automation, and the EHR in one price, in Hindi and other Indian languages. Add 18% GST and that's about ₹2,831 on the invoice.

For a hospital, Hospital Copilot is the separate product, and it's quoted on a demo rather than a public tier because bed count and module mix set the number. Book a demo and we'll scope it against your actual facility instead of a guessed range.

## The GST math, shown once

Indian B2B software is quoted ex-GST, so a headline rate is never your invoice. Here's the arithmetic, once, so you can run it on any vendor:

₹2,399 ex-GST × 1.18 (18% GST) = **₹2,831 on the invoice** per clinician per month.

Run the same on a hospital quote: a ₹5,00,000 annual HMS licence becomes ₹5,90,000 with GST. The rule for the whole shortlist is simple. Make every vendor quote ex-GST, confirm the GST treatment in writing, and only then line the numbers up. A vendor comparing its with-GST number against a rival's ex-GST number is stacking the deck.

## How to budget an HMS purchase without overpaying

The most common India overspend is buying hospital-grade modules for a clinic-grade problem. Before you sign anything, work these steps.

1. List the modules you'll actually use in the first year. Not the ones that sound useful. If your lab is outsourced, skip the LIMS module.
2. Decide cloud vs on-premise on TCO across three to five years, not the first invoice. Include AMC and the server for on-premise.
3. Get every one-time cost in writing: implementation, migration, training, customisation.
4. Ask for the ex-GST figure and confirm GST treatment for every quote.
5. If you run a clinic or OPD practice, price per-clinician software beside the HMS. The [best clinic management software options](../best-clinic-management-software-india/) and a straight [EHR vs HMS breakdown](../ehr-vs-hms-india/) will tell you which category you're actually shopping in.

Match the software to the building. A clinic paying hospital HMS prices for IPD modules it never opens is the pattern we see most, and it's avoidable. If your practice is clinic-sized, [see the Practice Copilot pricing](../../pricing/) and book a demo before you commit to a full HMS you'll half-use.

---

## NABH Entry-Level Accreditation for Clinics: A Documentation Primer
https://patientsquare.com/in/blog/nabh-entry-level-accreditation-clinics/
Published 2026-07-25 · Tags: nabh, accreditation, clinic-documentation, shco, quality

What NABH entry-level accreditation asks of clinics and SHCOs, the documentation you need, and how clean clinical records support your prep.

It is an entry-level quality standard from NABH, the National Accreditation Board for Hospitals and Healthcare Providers, aimed at smaller healthcare organisations (SHCOs) and clinics. It sets a starting set of standards on patient care, records, and safety, with documentation as a core requirement.

NABH entry-level accreditation is where a lot of Indian clinics start their quality journey, and where a lot of them get stuck on paperwork. The standard itself is manageable. The documentation load is what trips people up. This primer explains what entry-level NABH is, who runs it, and how the everyday habit of keeping clean clinical records makes the whole preparation lighter. NABH is the accrediting body; no software hands you the certificate.

> **Key takeaways**
> - NABH is the National Accreditation Board for Hospitals and Healthcare Providers, the accrediting body. Standards live on nabh.co.
> - Entry-level accreditation is aimed at smaller healthcare organisations (SHCOs) and clinics as a starting quality standard.
> - Documentation is a core requirement. Policies, records, and evidence of practice all get assessed.
> - Consistent clinical records make prep far easier because the evidence already exists.
> - AI Medical Scribe by Patient Square does not confer accreditation. It drafts notes that the clinician reviews and signs.

_Source: NABH, nabh.co._

## What entry-level NABH is

NABH sits under the Quality Council of India and accredits healthcare organisations against published standards. The entry-level programme is the starting rung, built for smaller healthcare organisations, often abbreviated SHCO, and for clinics that are not full-scale hospitals.

The idea is progression. Entry-level sets a reachable baseline on patient care, safety, and record-keeping. A clinic meets it, then can work toward higher levels later. It is a real programme with a real assessment, not a self-declared badge.

Work from the current standards on nabh.co. They get revised, and a summary written last year can steer you wrong. The official documents are the source of truth.

## Why documentation carries so much weight

Accreditation assessors do not just watch you work for a day. They read your files. Much of the standard is about whether you have written policies, whether staff follow them, and whether your records show it. Documentation is the evidence that your clinic does what it claims.

This is where clinics feel the pain. The clinical care might already be solid. The problem is proving it, retroactively, across months of inconsistent notes. If half your consult records are three illegible lines and the other half are thorough, an assessor sees a gap.

So the smart move is to fix the record habit early, well before you apply. Good notes are not a last-minute scramble. They are a byproduct of documenting properly every day.

## The documentation themes to expect

Broad areas that recurring NABH prep touches. Confirm specifics against the current published standards.

| Area | What documentation tends to cover |
|---|---|
| Patient records | Complete, legible, dated clinical notes with a consistent structure |
| Consent | Records of informed consent where procedures require it |
| Policies and procedures | Written SOPs that staff actually follow |
| Medication safety | How prescriptions and drug handling are documented |
| Patient rights and info | Evidence patients are informed and their data handled properly |
| Staff and training | Records of qualifications and relevant training |

The thread running through all of it: write it down, keep it consistent, make it findable. An assessor should be able to pull a random file and see the standard reflected in it.

## How clean clinical records support prep

Take patient records specifically. The standard wants clinical notes that are complete, legible, and consistent. That is exactly the part of daily work that slips when a clinic is busy: fifty patients before lunch, and the notes get shorter and rougher as the day wears on.

If every consult already produces a structured note with the right elements, your record-keeping evidence is built as you go. No back-filling. No panic before the assessment. The documentation standard becomes something you meet by default rather than something you cram for.

This is also where a scribe earns its place, honestly and within limits.

## Where a scribe helps, and the honest boundary

AI Medical Scribe by Patient Square listens during the consult and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft in about two minutes. The clinician reviews and signs. That signed note is the record, and the clinician stays responsible for it.

For NABH prep, the value is consistency. When each visit yields a structured draft, your notes stop drifting in quality across a long day. The structure is there whether it is the first patient or the fortieth. That supports the record-keeping standards directly.

Now the boundary, stated plainly. The scribe does not give you accreditation. NABH awards accreditation after assessment; no product does. It also does not read images, interpret studies, or diagnose. It structures what was said in the room. The reading stays yours, and the signature stays yours. What it offers is a cleaner, more consistent record as a starting point. Our [NABH documentation requirements](../nabh-documentation-requirements/) post goes deeper on the record side, and the [scribe overview for Indian doctors](../scribe-for-doctors-india/) shows how the drafting works.

## How documentation fits a real clinic

The clinics that sail through prep tend to share a habit: they treat documentation as part of care, not a chore bolted on after. A few practical moves:

- Standardise the note structure so every clinician records the same core elements.
- Keep records legible and dated. An assessor cannot credit what they cannot read.
- Store records securely and handle patient data under DPDP-aligned practices. The [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers this.
- Keep your written SOPs current, and make sure staff actually follow them.
- Run a mock review before the real one, pulling random files to see what an assessor would see.

Software choice plays into this too. A system that makes good record-keeping easy is worth more at accreditation time than one that fights you. If you are evaluating options, our [clinic management software rundown](../best-clinic-management-software-india/) and [EMR software guide](../emr-software-india-guide/) both weigh record-keeping features.

## The short version

Entry-level NABH is a reachable quality standard for clinics and SHCOs, run by NABH and documented on nabh.co. Documentation is the heart of the assessment. Consistent, legible clinical records make prep far lighter, because the evidence is already sitting in your files. A scribe can help keep those records consistent by drafting structured notes for the clinician to review and sign. It cannot hand you the accreditation. That comes from NABH.

Want to see how a consistent, signed clinical note comes together in about two minutes on a real consult? <a href="/in/products/hospital-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch it run, then read how we protect records on the [security page](../../security/).

---

## AI Medical Scribe for Concierge & DPC Practices
https://patientsquare.com/us/blog/ai-scribe-for-concierge-medicine/
Published 2026-07-24 · Tags: ai-scribe, concierge-medicine, direct-primary-care, patient-experience, clinical-documentation

Concierge and direct primary care sell time and attention. An ambient scribe keeps your eyes on the patient during long visits and drafts the narrative note for you.

Yes. It listens across the whole encounter and drafts a structured note about two minutes after you finish, whether the visit ran ten minutes or fifty. Longer, more narrative visits give it more to work with, not less.

Concierge and direct primary care practices sell something specific: time, attention, and a doctor who actually looks at you. A keyboard between you and the patient undercuts the whole model. An ambient AI scribe fixes that by listening during the visit and drafting the note itself, so you keep eye contact through a forty-minute annual exam and still walk out with the documentation mostly written. Patient Square hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after you finish. You review, edit, and sign.

> **Key takeaways**
> - Concierge and DPC visits run long and narrative, which plays to an ambient scribe's strength.
> - The scribe drafts the note from the conversation, so you stay present instead of typing.
> - A structured SOAP note plus ICD-10 suggestions come back about two minutes after the visit.
> - From $79 per clinician per month on the annual Assist plan, which suits a smaller panel; higher tiers add an EHR, messaging, and a receptionist.
> - You review and sign every note; legal responsibility for the record stays with you.

_Source: pricing described on the [pricing page](../../pricing/); audio handling on the [security page](../../security/)._

## Why documentation hurts the concierge model most

The concierge and DPC pitch is presence. A member pays a retainer for a physician who is not rushing, not double-booked, and not half-watching a screen. So the documentation burden lands harder here than in a high-volume clinic, because the very thing that erodes it, a doctor typing through the visit, is the thing your patients are paying to avoid.

The usual workaround is charting after hours. You stay present in the room, then reconstruct six long visits from scratch at nine at night. That trades one problem for another. The note gets thinner, the details fade, and your evening disappears.

An ambient scribe removes the choice. You are present during the visit and the note is drafted from what was said, not from a tired memory hours later. The relationship stays intact and the charting does too.

## How an ambient scribe fits a concierge visit

A concierge annual exam might run forty-five minutes and wander through family history, sleep, stress, three medications, and a plan you talk through together. That is a lot of narrative. It is also exactly what an ambient scribe is built to catch.

Patient Square listens across the whole encounter. When you finish, it returns a structured SOAP note about two minutes later, with the history and plan drafted from the actual conversation. You read it, fill in the nuance only you would know, and sign. The longer, richer visit gives the scribe more signal, not less.

Audio is processed in memory and discarded the moment the note drafts. Nothing is recorded or stored. For a practice built on trust, that is worth saying to members plainly: the conversation is not kept.

## What a concierge or DPC note needs to capture

Membership medicine leans on the longitudinal story. Here is what that demands from a scribe.

| Concierge / DPC need | Why it matters | How Patient Square handles it |
| --- | --- | --- |
| Long narrative visits | Annual exams and complex reviews run long | Listens across the full encounter, any length |
| Presence over typing | Members pay for attention | Scribe drafts the note; no keyboard mid-visit |
| Detailed history and plan | The relationship is longitudinal | Structured SOAP note drafted from the conversation |
| Small-panel economics | Fewer visits per day | Flat per-clinician fee, no per-visit charge |
| Patient trust on privacy | Retainer relationship, high expectations | Audio discarded once the note drafts |
| Clinician ownership | Your name, your record | You review, edit, and sign every note |

None of this asks you to change how you practice. It asks the documentation to keep up with a slower, deeper visit instead of forcing the visit to speed up.

## The membership math

Concierge and DPC practices run smaller panels at a flat membership fee, which changes how you weigh a per-clinician tool. There are no per-visit or per-encounter charges to model. It starts at $79 per clinician per month on the annual Assist plan. If you want the bundled AI EHR and messaging, the Copilot tier is $119 per clinician per month; a receptionist and follow-ups come with Autopilot at $199. Pick the tier that matches how much of the practice you want under one roof.

Set that against the alternative. After-hours charting is unpaid time, and in a practice where your differentiator is unhurried attention, burnout is a direct threat to the business. Time returned to the top of your day, or the bottom of your evening, is the actual return. We keep the pricing simple on purpose; the [pricing page](../../pricing/) has the full detail.

## Where the scribe stops, and your judgment starts

The scribe drafts. You decide. That line matters more in a relationship-first practice, where the member is trusting your read specifically.

Along with the note, Patient Square produces a prescription draft. It reflects what the visit called for, and it is a draft only: the scribe does not screen it for interactions or dosing, and you stay the safety check the way you are today. It never sends to a pharmacy, and there is no e-prescribing built in. You read the draft, adjust it, and prescribe through your own system.

The ICD-10 suggestions and the note itself come from what was said, not from any interpretation of images or studies. The scribe does not diagnose. It structures the encounter and leaves the clinical reading to you. If note quality is your main question, [how ambient scribes affect SOAP note quality](../ai-scribe-soap-note-quality/) goes deeper, and [primary care documentation with an ambient scribe](../ai-scribe-for-primary-care/) covers the adjacent workflow.

## When a concierge practice should adopt one

The fit is strong when your visits are long, your panel is small, and your brand is attention. If those describe you, an ambient scribe protects the exact thing your members pay for.

It is less compelling if you already have a human scribe you love and the cost works, though even then many physicians prefer not to have a third person in an intimate annual exam. And if you are shopping the category broadly, [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) lays out the questions to ask any vendor before you commit.

Because Patient Square is EHR-agnostic, it does not matter whether your practice runs Elation, athenahealth, or something lighter. There is no integration to schedule. You copy or paste the finished note into your chart and keep going.

Want to see it on a real long-form visit? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it against your next annual exam. You will get the note back in about two minutes, and you will have watched the patient the whole time.

---

## AI Medical Scribe for Paediatric Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-pediatric-clinics-india/
Published 2026-07-24 · Updated 2026-09-24 · Tags: paediatrics, ai-medical-scribe, immunization, clinical-documentation, india

How an ambient AI scribe drafts Indian paediatric OPD notes, including growth, immunisation, and weight-based prescription details for doctor review.

It drafts a prescription from what you say. It does not check dosing or interactions; it is a draft you review and correct. The weight-based dose you sign is your responsibility, not the software's, exactly as it is today.

A paediatric consultation has two people talking who are not the patient. The parent describes the fever, the poor feeding, the three nights of broken sleep, while the child squirms on the examination table. You weigh the child, check growth, decide on a vaccine or a weight-based dose, and reassure an anxious parent, all in a few minutes. Writing the note in that setting is a genuine problem. An ambient AI scribe drafts a structured note from the spoken consultation and returns it about two minutes after the visit, so the parent's account and your findings become the record without you typing through the chaos. You review the draft and sign it.

> Key takeaways
> - The scribe transcribes the visit, parent history included, and drafts a structured paediatric note for your review.
> - It captures narrated growth and immunization details; it does not plot charts or run the vaccine schedule.
> - Weight-based prescriptions come out as a draft. Check the child's recorded weight, calculate the dose yourself, and review the medication and interactions before you sign.
> - Consultation audio is processed in memory and discarded once the note drafts. No recording of a child's visit is kept. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - ABDM integration is on the roadmap for AI Medical Scribe by Patient Square, not shipped.

_Source: Product behaviour of AI Medical Scribe by Patient Square._

## How an ambient scribe fits a paediatric visit

Consider a sick-child visit. A mother brings in a two-year-old with fever for two days, reduced feeds, and one episode of loose motion. She does most of the talking. You examine the child, note the weight, check hydration, and decide on management. The history that matters here came from the parent, and it came fast.

An ambient scribe captures that spoken exchange and structures it into a draft. The parent's account becomes the history section. Your examination findings, dictated as you go, become the examination section. When you say "weight eleven kilos, well hydrated, throat congested, chest clear," that lands in the note. You are not stepping away to type while a toddler cries; you are consulting, and the note builds from the conversation for you to check afterward.

The value shows up most on the busiest days, when the queue is long and the notes would otherwise be written from fading memory hours later, if at all.

## What a paediatric scribe must capture

Paediatric OPD notes carry a few things adult notes do not. The scribe should structure your narration into them cleanly:

| Section | What gets narrated | What lands in the draft |
|---|---|---|
| Parent-reported history | Symptoms, feeding, sleep, duration | Structured history from the parent's account |
| Anthropometry | Weight, length or height, head circumference | The values you dictated, recorded |
| Development | Milestones observed or asked | Development notes for your review |
| Examination | Hydration, ENT, chest, abdomen | Findings as you spoke them |
| Immunization | Vaccine given, site, batch as read out | Immunization line in the note |
| Plan and dose | Weight-based medication, review date | Plan section, prescription drafted separately |

The anthropometry and immunization lines matter for continuity. A clean record of weight-over-time and vaccines-given is exactly what the next visit, or a referral, needs. The scribe records what you dictate. It does not plot the WHO growth chart or tell you the child has crossed a centile; that reading stays with you.

## Weight-based dosing and the prescription draft

Paediatric prescribing is where the stakes rise. Dosing is by weight, the margin for error is smaller in small children, and a decimal in the wrong place has consequences.

The scribe produces a prescription draft from your consultation. It is a draft, always. It writes out the drug, the dose, and the instructions you dictated so you are not retyping them. It never sends to a pharmacy and never dispenses.

Be clear on the boundary here. The scribe does not check the dose or screen for interactions. There is no automated safety layer, no flag, no block. Confirm the child's current recorded weight, calculate and check the dose against the chart and your clinical references, review the medication and potential interactions, then sign only after you are satisfied. The prescribing decision remains yours.

## High-volume vaccination days

Immunization clinics have their own rhythm. On a heavy vaccination day, a paediatric practice might run through dozens of well-child and vaccine visits, each needing a short but real record: which vaccine, which site, the next due date, and any advice given.

An ambient scribe keeps that documentation moving. You narrate the vaccine given and the counselling done, and the note drafts from it, so you are not left with a stack of half-written cards at the end of the session. It structures the visit; it does not run the national immunization schedule or decide what is due. For the schedule itself, you and your team stay in charge, referencing the programme you follow.

For a solo paediatrician without a full front desk, this kind of support is often the difference between notes that get written and notes that get skipped. Our note for [solo doctors in India](../ai-scribe-for-solo-doctors-india/) covers that single-handed setup in more detail.

## Parent history, consent, and children's data

Two sensitivities sit close together in paediatrics: the child's data and the fact that a parent is speaking on the child's behalf.

On data handling, consultation audio is processed in memory and discarded the moment the note drafts. No recording of the visit is kept. Notes are encrypted in transit with TLS and at rest with AES-256, they belong to your practice, and you can export or delete them at any time. An Indian paediatric clinic can be set up with an India data-residency posture. Children's health data is sensitive personal data, and handling it this way aligns with a DPDP-conscious approach; our [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) walks through what that involves, including consent for minors. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Because the parent does much of the talking, the history in the draft reflects the parent's words. You review it the same way you review any history: does it match what you heard, and is anything missing. Then you sign.

## Record-keeping that holds up

A paediatric record has to serve continuity above all. The next fever visit, the next growth check, and any referral all depend on a legible, dated, per-visit note. NMC's record-keeping expectations point at exactly this. A consistent structured note per child per visit is what an ambient scribe helps you produce, even at the end of a long clinic.

If your clinic is working toward NABH entry-level standards, consistent documentation is part of the picture; see our [NABH documentation overview](../nabh-documentation-requirements/). And for how AI-drafted notes intersect with your record-keeping duties, our [NMC record-keeping note](../nmc-record-keeping-ai-scribe/) is the relevant read. The signed content, and how long you retain it, stay your clinic's call.

## Run it on a real clinic day

The honest test is a busy morning with real parents and real kids. Book a demo, dictate a handful of visits, and see whether the drafts match how your OPD actually sounds. The [pricing page](../../pricing/) has India plans, and the [security page](../../security/) lays out encryption, residency, and deletion. See how it holds up when the queue is long and the day is loud.

---

## Bajaj Finserv Health CRM Alternatives: The AI Copilot Route
https://patientsquare.com/in/blog/bajaj-health-crm-alternatives-india/
Published 2026-07-24 · Updated 2026-08-27 · Tags: ehr, bajaj-finserv-health, hospital-software, alternatives, hospital-copilot

Comparing Bajaj Finserv Health's clinic software for your practice or hospital? See how Patient Square's ambient-AI EHR and Copilot compare on documentation and price.

For clinics and hospitals whose main gap is ambient documentation, yes. Bajaj Finserv Health offers clinic and practice management with ABHA integration and ties into a large hospital and consumer network. Patient Square leads with an ambient scribe and a bundled EHR in the Copilot plan from Rs 2,399 per month on an annual plan, plus GST, with a separate Hospital Copilot for hospitals. Match the tool to your biggest pain.

If you are weighing Bajaj Finserv Health's clinic software, you are probably drawn to the ecosystem: a big hospital network, a consumer app, ABHA integration, all under one recognised brand. Patient Square comes at the problem from a different angle. It leads with an ambient scribe that drafts the note, ICD-10 codes, and prescription during the consult, with the EHR bundled in the Copilot plan from Rs 2,399 per clinician per month on an annual plan, ex-GST, and a separate Hospital Copilot for hospitals. Check the [India pricing](/in/pricing/) first, then decide whether you are buying reach or documentation.

Both are legitimate priorities. This page is about which one is yours, not about which company is bigger.

> **Key takeaways**
>
> - Bajaj Finserv Health offers clinic and practice management with ABHA integration, ISO 27001 certification, and NHA empanelment for ABDM, per its site as of 2026.
> - Its strength is ecosystem reach: a large hospital network and a consumer app for patient demand.
> - Patient Square leads with an ambient scribe and a bundled EHR in the Copilot plan.
> - Ambient AI documentation is the layer Patient Square adds on top of practice management.
> - For hospitals, Patient Square offers a separate Hospital Copilot, priced via demo rather than a public tier.

## Bajaj Finserv Health vs Patient Square at a glance

The quick map. Verify current details with both before you commit.

| | Bajaj Finserv Health | Patient Square |
|---|---|---|
| Primary role | Practice management + ecosystem | Ambient scribe + bundled EHR / Copilot |
| Documentation | Records, prescribing recommendations | AI drafts note, ICD-10, Rx from the consult |
| ABDM/ABHA | Integrated, NHA-empanelled | Roadmap, not live |
| Compliance | ISO 27001 certified (2026) | DPDP-aligned |
| Network reach | Large hospital + consumer app | Clinical tool, no marketplace |
| Hospital product | Practice/clinic focus | Separate Hospital Copilot (demo-priced) |

If the "documentation" row is why you are here, note that Bajaj Finserv Health is built around records and network, not ambient scribing.

## What Bajaj Finserv Health does well

Bajaj Finserv Health brings scale that a standalone tool cannot. Its provider software covers patient records, scheduling, prescriptions, billing, and online consultation, with ABHA integration and prescribing recommendations, per its site as of 2026. Around that sits the ecosystem: partnerships with a large number of hospitals, a consumer app that can send patient demand, and NHA empanelment as one of the platforms chosen for ABDM. It is also ISO 27001-certified, which is a concrete, present-day compliance credential.

For a clinic or hospital that values reach, a recognised brand, and an established compliance posture in one package, that is a strong offer. If patient acquisition through a consumer app and ABHA-linked records matter to you, Bajaj Finserv Health is built for exactly that, and its certification and network are real advantages Patient Square does not match today.

What it is not centred on is ambient documentation. That layer is where Patient Square comes in.

## What the AI Copilot route changes

Patient Square starts at the consult. You open the app before the visit, tap once, and set it down. The scribe listens and drafts the note in the background, in English, Hindi, Hinglish, or a code-mixed regional language.

AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The practical details:

- The note comes out in clinical English regardless of the spoken language.
- Audio is discarded after the note drafts; only structured output persists. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
- The prescription is a draft that mirrors the plan discussed in the visit; you review and sign it, and it never sends to a pharmacy. Screening for interactions and dosing stays with the clinician.

The record layer, the AI Copilot EHR, is bundled in the Copilot plan. For solo and clinic use, that is the Practice Copilot. For hospitals, Patient Square offers a separate Hospital Copilot, which is priced through a demo rather than a public tier. So the product you evaluate depends on your setting. If you run a clinic, book a demo of Practice Copilot. If you run a hospital, ask for the Hospital Copilot walkthrough specifically.

## What Patient Square costs, and how to compare fairly

For clinics, Patient Square publishes per-clinician tiers. The Copilot plan bundles the EHR at Rs 2,399 per clinician per month on an annual plan, ex-GST, about Rs 2,831 with 18% GST. The Assist tier handles documentation only at Rs 1,599 per month annual, and Autopilot sits above. The full ladder is on the [India pricing page](/in/pricing/). Hospital Copilot does not have a public tier; that is a demo conversation.

Bajaj Finserv Health's provider pricing is best confirmed with their team, and we are not going to quote a figure we cannot verify. When you compare, be clear about what you are buying: a records-plus-network package and an ambient-documentation tool are not the same unit. Price the problem you actually have.

## When Bajaj Finserv Health is the better choice

Choose Bajaj Finserv Health if ecosystem reach is the point: access to a large hospital network, a consumer app for patient demand, ABHA integration, and ISO 27001 certification within one recognised brand. If patient acquisition, network scale, and an established compliance credential outrank ambient documentation, Bajaj Finserv Health's advantages are concrete and Patient Square does not match them today. That is an honest call, not a hedge.

Choose Patient Square if documentation is your biggest daily drain and you want the note drafted for you, with the EHR bundled, whether you run a clinic on Practice Copilot or a hospital on Hospital Copilot. For a practice where the real problem is charting, not reach, the ambient approach is the more direct fix.

## How to decide in a week

1. Name what you are buying. Reach and network point to Bajaj Finserv Health. Charting time points to Patient Square.
2. If you run a hospital, evaluate Hospital Copilot, not the clinic plan.
3. Trial Patient Square's note quality on real consults, not a demo script.
4. Get each vendor's price on a clear per-seat, ex-GST basis, then add GST once.

Patient Square's data-handling posture under the DPDP Act 2023 and the full price ladder are on the [pricing page](/in/pricing/). If the note is what steals your evenings, book a demo and see Patient Square draft one against a real clinic day.

_Reviewed by the Patient Square clinical team._

---

## Best EMR for Small Practice 2026: An Honest Roundup
https://patientsquare.com/us/blog/best-emr-for-small-practice/
Published 2026-07-24 · Updated 2026-08-29 · Tags: ehr, best, small-practice, comparison

Compare 2026 EMR and EHR options for small US practices using current vendor pricing, workflow fit, and evidence without claiming one universal winner.

There isn't one winner. This comparison names Patient Square, athenaOne, Tebra, DrChrono, and eClinicalWorks because their own current pages disclose a meaningful price model or product boundary. A one-to-five-provider practice should still score documentation, migration, scheduling, billing boundaries, export, security, and monthly cost, then reject any option missing a must-have.

There's no single best EMR for a small practice. For a one-to-five-provider clinic, the right choice is the one that passes your record, workflow, cost, and exit tests without failing a must-have. Practice Copilot can use the Patient Square EHR from the Copilot tier, priced at $119 per clinician per month on annual billing, or work alongside an existing EHR. A full ambulatory or specialty suite is the better fit when claims, labs, imaging, prescribing connectivity, or deep specialty workflows decide the purchase.

Request your 7-day trial only after you have written down the workflows that would disqualify the product.

> **Key takeaways**
>
> - Score one-to-five-provider fit, not feature count. A missing claims, lab, imaging, prescribing, or specialty requirement is a disqualifier.
> - Subscription price is only one row. Migration, training, interfaces, add-ons, staff time, and exit work belong in the same first-year model.
> - Patient Square publishes the Copilot subscription and shipped module names. It doesn't publish enough detail to assume every specialty or integration fit.
> - The winner is the product that survives your real clinic day and still lets you leave with usable data.

## How to use this named shortlist, including our gaps

We're the vendor behind one option, so the scorecard has to expose our gaps. We weight the daily clinical workflow and total cost, but a missing must-have beats the arithmetic. CMS's current E/M guidance says the record should be complete and legible, identify the reason, relevant findings, assessment, plan, date, and author, and support the codes reported. That is the documentation floor, not a nice extra ([CMS E/M guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)).

Patient Square can draft that record for review and bundle an AI Copilot EHR at the Copilot tier. It does not claim a full claims engine, clearinghouse, lab or imaging suite, or prescribing transmission. Those gaps are disqualifiers for some practices. Good. A useful roundup should tell those practices to buy something else.

## Named vendors: price model and fit

Start with the vendor's published contract shape, then use the weighted scorecard below. Each price is a current vendor-published rate or model checked on August 29, 2026. It is not a complete first-year quote.

| EMR | Current vendor-published price evidence | Fit to test | What the price does not settle |
|---|---|---|---|
| Patient Square | Copilot: $119 per clinician monthly on annual billing, or $149 month to month | Documentation, Scheduling, and a bundled AI EHR when a separate billing stack remains | Migration, claims, labs, imaging, specialty depth, and third-party-EHR write-back |
| athenaOne | Pricing is a percentage of collections; the vendor provides a customized quote | A practice that wants EHR, billing, practice management, and patient engagement from one vendor | The actual percentage, implementation terms, and specialty workflow |
| Tebra | For physicians, EHR Starter and Billing Starter each begin at $199 monthly for low-volume practices; Practice Essentials starts at $349 low-volume and $599 standard volume | Independent practices evaluating EHR, billing, telehealth, and patient-engagement bundles | Your final price, which depends on provider type, claim volume, and configuration |
| DrChrono | Its pricing page names Foundation, Growth, and Premium tiers but asks buyers to request a quote | A practice comparing EHR, patient engagement, practice management, billing, and revenue-cycle scope by tier | The contract price, setup work, and which add-ons are included |
| eClinicalWorks | EHR Only: $449 per provider monthly, with no start-up cost stated on the pricing page | A practice that wants an EHR with mobile, portal, messaging, document-management, and referral-management tools | Implementation, migration scope, and whether the listed EHR-only package meets its billing needs |

The comparison does not crown one of these products. It gives you five concrete buying paths to test.

## Match the shortlist to your practice shape

| Practice shape | Shortlist first | Why | Hard disqualifier to test |
|---|---|---|---|
| One clinician, documentation-heavy, separate billing | A self-serve record and scribe bundle | Low setup burden and one visible per-clinician rate matter | No usable legacy-record import or exit export |
| Two to five providers with a billing service | A small-practice EHR plus scheduling | The clinical record can change without replacing the claims operation | Weak permissions, offboarding, or shared-calendar rules |
| Insurance-heavy in-house billing | A full ambulatory EHR/PMS suite | Eligibility, clearinghouse, ERA, denials, and statements are core jobs | A product that calls export or code suggestions a claims engine |
| Imaging, lab, medication, or specialty-intensive clinic | A specialty or deeply integrated suite | Interfaces and specialty workflows outweigh a cheap subscription | Missing required order, result, registry, or prescribing connection |
| Hospital-owned or multi-site group | An enterprise platform with formal implementation | Governance, interfaces, support, and procurement evidence dominate | Self-serve software with no enterprise operating proof |

### The one-to-five-provider scorecard

| Criterion | Weight | What earns full credit | Disqualifier |
|---|---:|---|---|
| Real clinic workflow | 25 | Staff complete one visit from booking through signed note without a workaround | A must-have step lives in a spreadsheet or private note |
| Record and migration | 20 | Vendor maps each source field, exceptions, validation, and fallback | No written plan for legacy charts or open work |
| Billing boundary | 15 | Claims owner, interfaces, and handoffs are explicit | Sales material implies RCM the product does not ship |
| Security and access | 15 | BAA, role model, audit evidence, retention, and incident roles are written | Vendor needs PHI access but won't execute a BAA |
| First-year total cost | 15 | Subscription, setup, migration, training, interfaces, add-ons, and staff time are priced | Quote omits a mandatory line |
| Exit and growth | 10 | Practice runs an export and knows when a larger suite becomes necessary | Data leaves only as an unreadable archive |

Score out of 100 after enforcing the disqualifiers. A three-provider clinic might give Patient Square 23 on documentation and still reject it because a required lab or claims workflow is absent. That isn't a scoring failure. It's the scorecard doing its job.

## Why AI-native pricing matters for a small practice

The phrase “AI-native” doesn't prove a handoff. A scribe may give you copy-paste text, a file, structured export, a browser-assisted transfer, or native write-back. Those are different workflows. Patient Square claims EHR-ready export (PDF · HL7 · FHIR) and bundles the AI Copilot EHR at the Copilot tier. It does not claim native write-back into every third-party EHR. Run the exact path you'll use before awarding points.

Price transparency still matters. Patient Square publishes $119 per clinician per month on annual Copilot billing and $149 month to month. That lets a clinic model the subscription. It does not erase migration, training, interface, or staff-time cost. Our opinion: a visible rate is a useful feature, but a visible rate with an untested workflow is still an incomplete quote.

Run the [small-practice cost model](/us/blog/emr-system-cost-guide/) before a trial, then bring the worksheet and one difficult visit. The [pricing page](/us/pricing/) supplies the published Patient Square rows.

## How to make the final call

Rank your priorities first, enforce the disqualifiers, then pick. Patient Square belongs on the shortlist when documentation, scheduling, and a bundled EHR are the core job and the practice can retain a separate billing stack. A full ambulatory suite belongs first when eligibility, claims, denial work, lab or imaging interfaces, or deep specialty modules drive the purchase.

Whatever you choose, compare first-year cost per provider, run one legacy-record migration sample, and run one exit export. The [full EMR cost breakdown](../emr-system-cost-guide/) gives you the worksheet; the [integrated EMR and practice-management guide](/us/blog/emr-practice-management-software/) separates the clinical record from the claims stack.

## The bottom line on the best EMR for a small practice

There's no universal winner. For a one-to-five-provider clinic, the best EMR is the one that passes the workflow, migration, billing-boundary, security, cost, and exit tests without failing a must-have. Patient Square publishes a $119 annual Copilot rate. athenaOne uses a collections-based model, Tebra and eClinicalWorks publish current rates, and DrChrono asks buyers to request a quote. Each price still needs a written first-year scope. Practice Copilot can use the Patient Square EHR from the Copilot tier or work alongside an existing EHR. It is not the right choice when claims, lab, imaging, prescribing connectivity, or specialty depth require a fuller suite. Request your 7-day trial only after you have written those disqualifiers down.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot supports documentation and shipped practice workflows. A new practice can instead use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## EMR System Cost Guide 2026: The Full US Price Breakdown
https://patientsquare.com/us/blog/emr-system-cost-guide/
Published 2026-07-24 · Updated 2026-08-29 · Tags: ehr, pricing, cost, buying

Model US EMR cost across subscriptions, migration, training, interfaces, and staff time, then compare it with a published $119 bundled-EHR tier.

There is no trustworthy universal per-provider average. Scope, implementation, migration, interfaces, specialty modules, billing model, and support change the quote. Calculate first-year cost as subscription plus setup, migration, training, interfaces, add-ons, hardware, and internal staff time. Patient Square's published bundled-EHR rate is $119 per clinician per month on annual Copilot billing.

An EMR system costs its subscription plus implementation, migration, training, interfaces, add-ons, hardware, support, and staff time. There is no defensible universal US average: vendors and consultants publish different ranges because they are pricing different scopes. Patient Square publishes one exact comparison point, $119 per clinician per month on annual Copilot billing for the bundled AI Copilot EHR. The worksheet below makes you price the rest.

> **Key takeaways**
>
> - Compare the same scope. A cheap subscription with mandatory interfaces and migration can cost more than a higher visible rate.
> - Mark every line as included, fixed, usage-based, quote-only, buyer-owned, or unavailable. A blank quote row isn't free.
> - Compare cloud and on-premise over the same years, downtime, security, support, and exit assumptions.
> - Patient Square publishes the subscription: $79 annual Assist for documentation, $119 annual Copilot with the bundled AI Copilot EHR. Other costs still need proof.

## What does an EMR system cost in 2026?

Split cost into one-time, recurring, usage-based, and internal rows. Then force both cloud and on-premise candidates into the same columns.

| Cost row | Cloud question | On-premise question | Evidence to keep |
|---|---|---|---|
| Subscription or licence | What is billed per clinician, user, visit, location, or module? | Is the licence perpetual, version-bound, or recurring? | Current rate card and renewal clause |
| Implementation | Which configuration and validation work is included? | Who installs and qualifies the environment? | Fixed scope, owner, date, and acceptance test |
| Migration | Which fields, documents, images, balances, and histories move? | Same question, plus local extraction tooling | Mapping, exception log, sample import, fallback |
| Training | How many roles, sessions, and refresher hours are included? | Who trains local administrators and IT? | Role-based training plan and attendance |
| Interfaces | Which lab, imaging, billing, identity, or exchange links are mandatory? | Who maintains each interface after upgrades? | Per-interface setup and recurring charge |
| Infrastructure | Which devices, bandwidth, and peripherals are needed? | Servers, storage, backups, monitoring, disaster recovery, and facilities | Buyer and vendor responsibility list |
| Exit | How do you receive records and how long does extraction take? | How do you move data and retire hardware safely? | Tested export, format, fee, and deletion terms |

Patient Square supplies a visible subscription row on the [US pricing page](/us/pricing/). The published Copilot annual rate is $119 per clinician per month. The public page doesn't turn every migration or interface row above into zero, so get those answers separately.

## What are the hidden costs most buyers miss?

The subscription is the easiest part to compare, which is why sales conversations orbit it. The harder rows are scope and labour. A vendor can quote migration while leaving data cleanup to your staff. An interface can have a setup fee, a recurring fee, and upgrade work. Training can mean one recorded webinar when your practice needs live sessions for clinicians, front desk, billers, and administrators.

Internal time belongs in the model even when no invoice arrives. Count hours for data cleanup, configuration decisions, test patients, training, parallel operation, issue triage, and reconciliation. Multiply by the loaded hourly cost for each role. Don't invent a generic “productivity dip”; put the actual people and planned hours into the sheet.

The lesson isn't to fear these costs. It's to label them. Ask the vendor to mark each line included, fixed-price, usage-based, quote-only, buyer-owned, or not available.

## Cloud versus on-premise: which is cheaper?

Cloud usually moves infrastructure work to the vendor and puts more cost into recurring subscription. On-premise gives the buyer more infrastructure responsibility: servers, storage, backups, monitoring, upgrades, physical security, disaster recovery, and qualified staff. Neither description proves a lower five-year total.

Build both models over the same contract term. Use the same clinician count, migration scope, interfaces, training, support hours, downtime assumption, upgrade cadence, backup standard, and exit work. If one quote includes a row and the other leaves it blank, investigate the blank.

The deployment decision can also be about control or continuity rather than price. A practice with established IT and a hard local requirement may reasonably accept more infrastructure work. A small office without that team may prefer a managed cloud service. Write down the reason instead of borrowing a market average.

## What does a transparent EMR tier actually include?

Here's the current Patient Square subscription ladder, checked against the live local pricing configuration and [US pricing page](/us/pricing/). Rates are per clinician per month.

| Tier | Annual billing | Month to month | Scope that matters to an EMR buyer |
|---|---:|---:|---|
| Assist | $79 | $99 | Documentation plus scheduling; no bundled EHR |
| Copilot | $119 | $149 | Adds the bundled AI Copilot EHR and WhatsApp messaging |
| Autopilot | $199 | $249 | Adds the named AI Receptionist, AI Follow-ups, priority support, and adoption/ROI analytics modules |

All plans include unlimited visits and notes and no per-note metering. The scribe produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for review. The prescription is not transmitted to a pharmacy. The public product surface does not enumerate deep billing, lab, imaging, patient-portal, or specialty modules inside the EHR.

The point isn't that Patient Square is cheapest. The exact subscription is visible, while total cost still depends on your migration, training, interfaces, and staff work. That distinction keeps a public rate from turning into an unsupported TCO promise.

If the published Copilot scope is a match, Request your 7-day trial before committing to the annual rate. Use the worksheet to document the rest of the first-year cost.

## How to compare EMR costs the right way

Use this worksheet. Enter zero only when the vendor explicitly includes the line.

| First-year row | Formula | Vendor A | Vendor B | Patient Square example |
|---|---|---:|---:|---:|
| Subscription | monthly rate × clinicians × 12 |  |  | $119 × clinicians × 12 on annual Copilot |
| Implementation | fixed fee + required services |  |  | verify in writing |
| Migration | extraction + cleanup + import + validation |  |  | verify in writing |
| Training | role hours × loaded hourly cost + vendor fee |  |  | verify in writing |
| Interfaces and add-ons | setup + 12 months recurring |  |  | include only required connections |
| Internal project work | staff hours × loaded hourly cost |  |  | enter your planned hours |
| Hardware and connectivity | devices + network + peripherals |  |  | enter clinic-specific need |
| Exit reserve | export, contract exit, and overlap |  |  | verify format, timing, and fee |
| **First-year total** | sum all rows |  |  | don't calculate until blanks are resolved |

For a three-clinician practice, the published Copilot subscription row is $4,284 for twelve months: $119 × 3 × 12. That is not the first-year total. Migration, training, interfaces, internal work, and exit reserve remain blanks until evidence fills them.

The [best EMR for a small practice](/us/blog/best-emr-for-small-practice/) turns these costs into a disqualification scorecard. The [pricing page](/us/pricing/) supplies the live Patient Square rates.

## The bottom line on EMR system cost

Budget for the whole thing, not the sticker. Subscription, implementation, migration, training, interfaces, add-ons, hardware, staff time, and exit all belong in the same model. The Patient Square Copilot subscription is $119 per clinician per month on annual billing with the bundled AI Copilot EHR. Everything else is a question until a written answer fills the row. Request your 7-day trial with the worksheet open, not after you've forgotten the blanks.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot works alongside it. A new practice can instead use the bundled Patient Square EHR, available from the Copilot tier, as its system of record. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## AI Medical Scribe for Dermatology Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-dermatology-clinics-india/
Published 2026-07-23 · Tags: dermatology, ai-medical-scribe, clinical-documentation, cosmetology, india

How an ambient AI scribe drafts Indian dermatology OPD notes, including described lesion findings, acne, eczema, and cosmetic visits.

No. It does not read images, dermoscopy captures, or clinical photos. It transcribes and structures the lesion description you speak during the consultation. The visual reading stays yours.

Dermatology is a volume specialty in India. A busy skin clinic in a metro can see sixty to a hundred patients a day, many of them quick acne, fungal infection, or hair-fall visits, punctuated by longer cosmetic consultations. Documentation is the first thing that suffers when the queue is long. An ambient AI scribe drafts a structured note from your spoken consultation and hands it back about two minutes after the visit, so the note gets written while the patient is still fresh in your mind. You review it, fix anything off, and sign. One thing it does not do, and this is deliberate: it does not read or interpret your skin photographs. It captures the lesion description you speak.

> **Key takeaways**
> - The scribe transcribes and structures the lesion findings you describe out loud; it never reads or interprets images.
> - Built for high patient volume, it drafts a note about two minutes after each visit so documentation keeps pace with the queue.
> - It handles both medical and cosmetic dermatology from what you narrate; you decide the record and sign it.
> - Prescription output is a draft only that you review and sign; the scribe does not screen it, so the safety check stays with you. It never reaches a pharmacy.
> - Notes are encrypted, yours to export or delete, and audio is discarded once the note drafts. ABDM linking is roadmap, not shipped. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

_Source: Product behaviour of AI Medical Scribe by Patient Square._

## How an ambient scribe fits a dermatology visit

Take a standard acne consultation. You examine the face, note grade, describe comedones, papules, pustules across the T-zone, ask about duration and prior treatment, and set a plan. In a fast OPD, the temptation is to write two words in the file and move on. Six months later that note tells you nothing.

An ambient scribe running in the background turns the words you already say into a structured note. When you describe "grade three acne, closed comedones over both cheeks, few pustules on the chin, no scarring yet," that description becomes the examination section of the draft. You are not typing. You are consulting the way you always do, and the note assembles itself from your speech for you to check.

For quick repeat visits, this is where the time goes back. A fungal infection follow-up or a hair-fall review takes a sentence or two to document if you dictate it, versus a full stop-and-type interruption for every patient.

## Why the scribe does not read images

This is the most important honesty in derm. Diagnosis in dermatology is heavily visual: morphology, distribution, colour, dermoscopy. It is tempting for a vendor to claim their AI can look at a lesion photo and tell you what it is. AI Medical Scribe by Patient Square does not do that, and does not pretend to.

The reading stays yours. You look at the lesion, the dermoscopy, or the biopsy report, and you make the call. The scribe captures the words you use to describe what you saw. So a note might read "well-defined erythematous scaly plaque over extensor surface of elbow, suggestive of psoriasis, biopsy advised," because that is what you said, not because the software interpreted a picture.

Keeping that line bright protects you. The clinical judgement, and the legal responsibility for it, sits with the signing clinician. A tool that transcribes your described findings supports the record. A tool that claims to diagnose from an image would be making a claim no honest scribe should make.

## What a dermatology scribe must capture

A useful derm note has a recognisable shape. The scribe should structure your narration into it without forcing you off your natural flow:

| Section | What you narrate | What lands in the draft |
|---|---|---|
| Complaint and duration | "Acne for six months, worse before periods" | Structured complaint with timeline |
| Lesion description | Type, site, distribution, colour, size | Morphology exactly as you described it |
| Relevant history | Prior treatments, allergies, family history | History section for review |
| Provisional impression | Your stated clinical impression | Recorded as your words, not a diagnosis by the tool |
| Procedures | Peel, cautery, biopsy, extraction done | Procedure note you sign |
| Plan | Topicals, systemics, review date | Plan section, prescription drafted separately |

The morphology line is where derm notes live or die, and it is the one clinicians most often shorten under time pressure. Dictating it into a scribe is faster than typing it, so it actually gets recorded in full.

## Medical versus cosmetic dermatology

Many Indian skin clinics run both sides of the house. Medical derm on one hand, aesthetic and cosmetic work on the other. The documentation needs differ.

For medical visits, the note supports continuity of care and, where relevant, insurance or cashless claims. For cosmetic work, the note is often about consent, procedure detail, and expectation-setting: which peel, what concentration, what was discussed about downtime and results. A chemical-peel consult where you narrate the agent, the strength, the areas treated, and the aftercare advice produces a clean procedure record you can rely on later.

The scribe drafts from whichever kind of visit you are in. It does not upsell, does not decide the procedure, and does not generate marketing claims. It writes down what you said and hands it back for your sign-off.

## Prescription drafts, safely

Derm prescribing has real traps. Isotretinoin in a patient who might be pregnant. Systemic steroids stacked on comorbidities. A topical-plus-oral combination in someone already on other medication.

The scribe produces a prescription draft from your consultation, and only a draft. It never sends to a pharmacy and never dispenses. What it does not do is check the medicines for you: there is no interaction screen and no pregnancy flag. It writes down what you said, and the safety review is yours. On a retinoid in a woman of childbearing age, that pregnancy risk is exactly what you weigh when you read the draft, adjust it, and sign, the same judgement you apply to a handwritten script.

You remain in charge, because that is where the safety belongs. The scribe drafts; you decide.

## Volume, data residency, and where notes live

High volume is the whole reason a scribe earns its place in a skin clinic. The maths is simple: if documentation eats even five minutes a patient across seventy patients, that is nearly six hours of writing a day spread across the team. Trimming that materially changes the clinic's day.

On data, an Indian derm clinic can be set up with an India data-residency posture. Notes are encrypted in transit with TLS and at rest with AES-256, they belong to your practice, and you can export or delete them at any time. The consultation audio is processed in memory and discarded the moment the note drafts, so nothing is retained as a recording. This aligns with a DPDP-conscious way of handling sensitive personal data, and you can read more in our [DPDP Act guide for clinics](../dpdp-act-clinics-guide/). If NABH documentation is on your roadmap, our [NABH documentation overview](../nabh-documentation-requirements/) covers what a consistent note habit supports. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

ABDM integration is on the roadmap for AI Medical Scribe by Patient Square, not shipped, so the product does not currently link derm records to ABHA.

## See it against your own clinic

Volume specialties reward tools that keep pace without getting in the way. The way to judge that is to run it in your OPD for a session. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, dictate a few real consultations, and see how the drafts read. The [pricing page](../../pricing/) has India plans, and the [security page](../../security/) details encryption, residency, and deletion. If you want to compare options first, our [best AI scribe for India roundup](../best-ai-scribe-for-india-2026/) is a fair place to start.

---

## AI Medical Scribe for Nephrology: CKD & Dialysis Notes
https://patientsquare.com/us/blog/ai-scribe-for-nephrology/
Published 2026-07-23 · Tags: nephrology, ai-medical-scribe, ckd-notes, dialysis-documentation, clinical-documentation

An ambient AI scribe drafts nephrology notes for CKD staging, dialysis adequacy, and transplant follow-up from what you say. You review and sign.

No. The scribe has no memory of prior visits. If you want the eGFR trend in the note, for example a drop from 42 to 35, you say it during the visit. Then the scribe captures the trend you narrated.

Nephrology lives on trends and numbers: eGFR falling stage by stage, dialysis adequacy measured cycle to cycle, electrolytes and fluid status that shift week to week. An ambient AI medical scribe drafts your CKD, dialysis, and transplant follow-up notes from what you say during the visit, then hands the draft back about two minutes after the patient leaves. Like every scribe, it has no memory of prior visits, so any trend you want in the note gets spoken out loud. You review the draft, confirm the coding, and sign.

> **Key takeaways**
> - The scribe drafts nephrology notes plus ICD-10 suggestions about two minutes after the visit; you review and sign.
> - It has no memory of prior visits, so eGFR trends, Kt/V history, and dose changes over time must be spoken.
> - The prescription draft reflects the dose you dictated; renal dose adjustment stays your call, since the scribe does not screen kidney function.
> - It runs alongside any nephrology EHR. Copy or export. No integration.
> - Audio is discarded the moment the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## How an ambient scribe fits a nephrology visit

A CKD clinic visit is a review of trajectory. You talk through the eGFR, the proteinuria, blood pressure, fluid status, electrolytes, and the medications that need renal adjustment. You decide whether the patient is progressing, whether to change a dose, whether to start planning for renal replacement. A dialysis visit reviews adequacy, access, fluid removal, and labs. A transplant follow-up watches graft function and immunosuppression.

The scribe listens through all of it. When you say the eGFR dropped from 42 to 35 and you are moving the patient from stage 3b thinking to stage 4 planning, that goes in the note. When you say the Kt/V is 1.4 and adequate, that lands in the note. Two minutes after the patient leaves, you have a draft.

Because the clinical story is longitudinal, your narration during the visit builds the note. The scribe carries nothing forward and infers nothing.

## The no-memory design and the eGFR trend

Nephrology, like endocrinology, is a specialty where the trend is the story. A single eGFR of 35 means one thing if it was 42 three months ago and another if it was 28. The scribe does not know which, because it has no memory of the prior visit and no view into your labs.

So the discipline is to speak the trend. When you say the eGFR fell from 42 to 35 over three months and the decline is faster than you would like, the trend, the rate, and your concern are all in the note because you said them. Skip it and the note holds only the single value you mentioned.

Most nephrologists already say this to the patient. "Your kidney function has slipped a bit since last time, from 42 to 35, so we need to talk about what comes next." Say that and the note reflects it. The scribe turns the conversation you are already having into the record.

## What a nephrology scribe must capture

The vocabulary here is numeric and specific, and the scribe has to land it when you speak it.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| CKD staging and eGFR | "eGFR down from 42 to 35, moving to stage 4" | Stage and trend as narrated |
| Proteinuria | "Urine protein-to-creatinine ratio 1.2, up from 0.8" | Proteinuria value and change |
| Dialysis adequacy | "Kt/V 1.4, adequate this month" | Adequacy as stated |
| Fluid status | "Euvolemic, no edema, dry weight unchanged at 72 kg" | Volume assessment |
| Electrolytes | "Potassium 5.2, bicarbonate 20, phosphorus mildly high" | Labs as you stated them |
| Vascular access | "AV fistula, good thrill and bruit, no signs of stenosis" | Access exam |
| Transplant follow-up | "Graft function stable, tacrolimus level therapeutic" | Graft and immunosuppression status |
| Medication renal dosing | "Reducing gabapentin dose for renal function" | Dose adjustment in the plan |

The electrolytes and fluid status carry weight for both management and coding. If you assess volume and state the potassium and bicarbonate, the note supports the complexity of the visit. If you leave them out, the scribe cannot supply them.

## Dialysis adequacy and access, captured not calculated

Worth stating clearly. The scribe does not calculate the Kt/V and it does not measure the fistula. It records what you say. If you state the Kt/V is 1.4 and adequate, that goes in the note because you spoke it. If you examine the access and describe a good thrill and bruit with no stenosis, the scribe writes down your exam.

The judgment about whether dialysis is adequate, whether the access is failing, whether fluid removal needs adjusting, that is yours. The scribe documents your assessment. It does not produce it.

## The prescription draft, and where renal dosing stays

This is where nephrology needs a clear boundary. When your plan includes a medication change, the scribe drafts a prescription from what you said. If you reduce a gabapentin dose for a patient with an eGFR of 35, the draft reflects that reduced dose because you dictated it. The scribe writes it out so you are not retyping the order.

What the scribe does not do is screen kidney function or check the dose. There is no renal logic, no flag, no block. In nephrology, where a huge share of medications need dose adjustment or avoidance based on kidney function, that adjustment is exactly the judgement you make on every prescription, and it stays entirely with you. You read the draft, confirm the renal dose against the patient's function, and sign.

The draft never goes to a pharmacy. There is no e-prescribing connection and nothing transmits. You act on the draft in your own workflow. Our post on [prescription draft safety](../ai-scribe-prescription-draft-safety/) covers how the draft works and why the clinician is the safety check.

## ICD-10 suggestions for the renal visit

After the visit the scribe offers ICD-10 suggestions from what you said. Common ones in nephrology:

| Condition | ICD-10 suggestion |
|---|---|
| Chronic kidney disease, stage 3 | N18.3 (with 3a/3b specificity) |
| End-stage renal disease | N18.6 |
| Hypertensive chronic kidney disease | I12.- family |
| Hyperkalemia | E87.5 |

These are suggestions to speed coding, not final answers. CKD staging in ICD-10 wants the right stage and, for stage 3, the a-or-b subdivision, so you confirm the specificity. When the CKD is hypertensive or diabetic, the combination coding matters, and you resolve that. Our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) has the detail.

## Security and ownership

Renal and dialysis records are protected health information and are handled accordingly. Audio is processed in memory and discarded the moment the note drafts, so no recording persists. Notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256, they belong to your practice, and you can export or delete them any time.

We maintain HIPAA compliant safeguards, offer a signed BAA to every customer, and have a SOC 2 Type II audit underway. If compliance is a gate for you, start with the [security page](../../security/) and our detail on [BAAs and consent](../ai-scribe-hipaa-baa-consent/).

## Where nephrology fit stands or falls your practice

If you run busy CKD and dialysis clinics and charting is eating your time, the trade is clear: speak the trends and the numbers you already discuss with the patient, and the note drafts for your review, with any prescription draft reflecting the renal dose you set. If your visits are lighter, the gain is smaller.

Pricing starts from $79 per clinician per month on the annual Assist plan, stepping up to Copilot and Autopilot as you add a bundled AI EHR, messaging, and receptionist and follow-up automation. On Assist the scribe works alongside your existing nephrology EHR with no integration and no IT project. See our [comparison of AI medical scribes](../best-ai-medical-scribes/), the [cardiology scribe overview](../ai-scribe-for-cardiology/) for cardiorenal patients, and [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before committing to any vendor.

Want to see it on a real CKD follow-up? Book a demo. Pricing is on the [pricing page](../../pricing/).

---

## Best EHR for Internal Medicine (2026): An Honest Roundup
https://patientsquare.com/us/blog/best-ehr-for-internal-medicine/
Published 2026-07-23 · Updated 2026-08-27 · Tags: comparison, internal-medicine, primary-care, buying, ehr

Epic, athenahealth, Elation, Tebra, and Practice Fusion compared for adult primary care on panel management, Medicare AWV, and cost. Plus where a scribe layer fits.

It depends on your size and model. Large internal medicine groups and health-system practices usually land on Epic or athenahealth for scale and revenue-cycle depth. Small independent practices lean Elation, Tebra, or Practice Fusion for a cleaner primary-care fit and lower cost. The pick turns on your panel size, how you handle billing, and how much of the day documentation eats.

The best EHR for internal medicine depends on how big you are and how you bill. Large adult primary care groups and health-system practices usually land on Epic or athenahealth for scale and revenue-cycle depth. Small independent practices lean Elation, Tebra, or Practice Fusion for a cleaner fit and lower cost. [Practice Copilot](/us/products/practice-copilot/) gives an independent practice two paths: use Patient Square EHR from the Copilot tier, or keep an existing EHR and run the ambient scribe alongside it. The right path depends on the billing, lab, and panel-management depth you need.

> **Key takeaways**
>
> - Size decides the shortlist: Epic and athenahealth for large groups and systems, Elation, Tebra, and Practice Fusion for small independent practices.
> - A 2016 Annals of Internal Medicine time-motion study found physicians spend close to two hours on EHR and desk work for every hour of direct patient care.
> - Internal medicine leans on chronic-disease panels, Medicare Annual Wellness Visits, and HCC documentation, so the note is longer and the after-hours load is heavier.
> - The EHR stores your note; it usually doesn't write it. Patient Square runs an ambient scribe alongside any EHR, or bundled with an AI EHR at a published $119 per clinician a month on annual billing.

## What internal medicine actually asks of an EHR

Adult primary care has a shape that urgent care and single-specialty clinics don't. You carry a panel you've known for years. A single Tuesday might run 22 patients: three diabetics due for A1c review, a heart-failure follow-up, two Medicare Annual Wellness Visits, a polypharmacy reconciliation on an 80-year-old taking nine medications, and a stack of referrals to route. Continuity is the whole job, and the chart is where continuity lives or dies.

That drives four things the EHR has to handle well. Chronic-disease panel management, so you can see who's overdue at a glance. Medicare Annual Wellness Visits, which CMS covers with a defined set of required elements you have to document each year (CMS Medicare Learning Network). HCC risk-adjustment documentation, where the diagnoses you capture and code drive Medicare Advantage payment (CMS risk-adjustment program). And polypharmacy, because your patients are older and their medication lists are long.

One number decides more than any feature grid. A 2016 time-motion study in Annals of Internal Medicine watched physicians across four specialties, internal medicine among them, and found they spent close to two hours on EHR and desk work for every hour of direct patient care (Sinsky et al., 2016). The chart is thorough in adult primary care, which is exactly why the note is long and the after-hours typing is real. So the EHR question isn't only "does it manage a panel." It's "how late does it keep me charting."

## Epic: built for systems, not solo practices

Epic is the enterprise EHR. If you're part of a hospital network, a large multi-site internal medicine group, or an academic practice, you're probably already on it or heading there, and the integration depth is the reason. Panel management, population health tooling, and revenue-cycle scale are all there at a level a small practice will never touch.

The catch is that scale. Epic is quote-only, enterprise-priced, and a heavy lift to implement. For a solo or small independent adult primary care practice, it's usually overkill, both in cost and in the operational weight of running it. We cover the numbers in more detail in our read on [Epic EMR cost](../epic-emr-cost/).

**Pick Epic if:** you're inside a health system or a large group that needs deep integration and can staff the implementation.

## athenahealth: percentage billing at ambulatory scale

athenahealth is the large ambulatory option that isn't Epic. Instead of a flat per-provider fee, it charges a percentage of what you collect, commonly cited at 4 to 8 percent, and in exchange runs your billing on a deep claims engine that scrubs before submission. For an internal medicine group fighting denials or short on billing staff, that trade can pay off.

The math is the thing to watch. As your collections grow, so does the bill, and a rate that reads small on a demo can quietly become your largest software cost. Model it against your real revenue, not a sample number. We break down that model in our post on [athenahealth's cost](../athenahealth-ehr-cost/), and cover leaving in [switching from athenahealth](../switch-from-athenahealth/). If billing is a genuine headache, the percentage may still win. If it isn't, a flat fee is usually cheaper once you scale.

**Pick athenahealth if:** you want billing handled at scale, denials are a real problem, and you accept paying a slice of collections for it.

## Elation: clean primary-care fit for independent practices

Elation is built around independent primary care, and internal medicine is squarely in its target, alongside family medicine, pediatrics, and direct primary care. The interface is one of the tidiest around for a physician who wants the chart to get out of the way, and it ships a native ambient scribe, Note Assist, at no added cost to EHR users (Elation Health). If you already run Elation and like it, that native scribe is a real reason to stay put.

The friction is price. Elation's pricing page is quote-only now, and third-party trackers estimate roughly $275 to $399 per provider a month depending on plan. So the scribe is free, but the EHR is a number you get after a call. More detail in our [Elation EHR pricing](../elation-ehr-pricing/) breakdown.

**Pick Elation if:** you're a small independent adult primary care practice that wants a clean chart and a native scribe, and you don't mind a quoted price.

## Tebra and Practice Fusion: the smaller-practice options

Two more belong on a small-practice shortlist, and they sit at different ends of it.

Tebra, the platform that absorbed Kareo, puts the record, billing, and a native AI Note Assist in one system, which suits a practice that wants everything under one login. Like Elation, its EHR pricing is quote-only, so the all-in figure arrives after a demo. Our [Kareo and Tebra pricing](../kareo-ehr-pricing/) post covers what stacks onto that quote.

Practice Fusion is the low-cost cloud option, near $199 per provider a month on its published pricing, and it charts, prescribes, and connects labs cleanly (Practice Fusion). What it doesn't do is write the note. There's no native ambient scribe, so you type or dictate yourself, or bolt on a third-party tool and paste across. That gap is the subject of our [Practice Fusion alternatives](../practice-fusion-alternatives/) post.

## Where each Practice Copilot path fits

Now the honest part. Every system above stores the chart. Most of them don't write the note as the main event, and where an AI note exists, it's usually a feature bolted onto a record system that was designed before ambient scribing existed.

We build [Practice Copilot](/us/products/practice-copilot/), and writing the note is the point. AI Medical Scribe by Patient Square is one module inside it: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For an internal medicine day, that lands on the exact pain a 2016 time-motion study measured. The continuity work still needs you. The typing after clinic doesn't.

The part worth stating plainly: you don't have to switch EHRs to get it. Patient Square runs alongside whatever you already own. On the Assist tier, $79 a month on annual billing, it's documentation only, and the note exports as PDF, HL7, or FHIR into your existing chart. There's no integration project to schedule, no interface to certify. You copy or export the note into Epic, athenahealth, Elation, or Practice Fusion and move on. If you'd rather have the record and the scribe in one place, the Copilot plan bundles an AI EHR with the scribe at a published $119 per clinician a month on annual billing.

We think a published price is a feature, especially when three of the EHRs above are quote-only. You can budget ours on a spreadsheet before anyone from sales calls you.

## When a full EHR beats adding a copilot

Keeping an incumbent EHR isn't always the right path, and pretending it is would make this list useless.

If your current EHR is genuinely holding the practice back, if panel management is clunky, if billing is broken, if you're on a system you're leaving anyway, then the fix is a better EHR, not a scribe stapled to a bad one. Adding a copilot to a record system you already resent just buys you a faster note inside a chart you still hate. In that case, pick the EHR that fits your size first, Elation or Tebra for a small practice, Epic or athenahealth for a group, and worry about the documentation layer second.

And if you're a large group where revenue-cycle depth outranks charting speed, athenahealth's claims engine or Epic's integration will matter more than shaving minutes off a note. We don't replicate an enterprise RCM engine, and we won't pretend to. Keep that EHR and use Practice Copilot alongside it. An independent practice whose requirements fit the documented Patient Square scope can instead use Patient Square EHR as its system of record.

## How to choose in one pass

Answer three questions honestly. How big are you, one clinician or twenty? Do you want to run billing or hand it off? And how late are you finishing charts?

Small independent adult primary care that wants a clean chart and a native scribe leans Elation. Want everything in one platform leans Tebra. Lowest published cost and you'll bring your own scribe leans Practice Fusion. Large group or health system leans athenahealth or Epic. Practice Copilot can stay alongside any of those from $79 a month on annual billing, or Patient Square EHR can become the record system from the $119 annual Copilot tier.

One rule before you sign anything: make each vendor time a real charted internal medicine visit on your own note types, an AWV, a diabetic follow-up, a polypharmacy reconciliation, not a scripted demo. The pricing page won't tell you how many minutes a note takes. That number decides more than the sticker does. When you've got a shortlist of two or three, book a short demo and run the scribe on your own visits, and if you just want our number, it's on the [pricing page](/us/pricing/).

---

## DocEngage Alternatives: AI-Native EHR and Front Office
https://patientsquare.com/in/blog/docengage-alternatives-india/
Published 2026-07-23 · Tags: ehr, docengage, clinic-crm, alternatives, practice-copilot

Looking past DocEngage's healthcare CRM? See how Patient Square's ambient-AI EHR and Practice Copilot compare on documentation and front-office automation.

If you want an AI-native clinical tool rather than a CRM-first suite, yes. DocEngage is a healthcare CRM focused on patient engagement, call-centre workflows, and referral management. Patient Square leads with an ambient scribe and a bundled EHR in the Copilot plan from Rs 2,399 per month on an annual plan, plus GST. They solve different primary problems, so match the tool to your biggest pain.

If DocEngage is on your shortlist but you keep coming back to documentation, the two products are aimed at different problems. DocEngage is a healthcare CRM: patient engagement, call-centre workflows, referral management. Patient Square is an AI-native clinical tool: an ambient scribe drafts the note, ICD-10 codes, and prescription during the consult, and the EHR is bundled in the Copilot plan from Rs 2,399 per clinician per month on an annual plan, ex-GST. See the [India pricing](/in/pricing/) first, then decide which problem is actually yours.

This is a fit question, not a quality one. DocEngage does its job well. So the honest work here is figuring out whether your biggest drain is patient communication or clinical documentation.

> **Key takeaways**
>
> - DocEngage is a healthcare CRM: engagement, call-centre and IVR, referral management, patient feedback.
> - Patient Square leads with an ambient scribe and a bundled EHR in the Copilot plan.
> - DocEngage reports outcomes like fewer no-shows and more follow-ups; it is HL7 FHIR compliant with HIS and EHR connectors, per its site as of 2026.
> - Patient Square's Copilot plan bundles the EHR at Rs 2,399/clinician/month annual, ex-GST.
> - Different primary problems: pick engagement (DocEngage) or documentation (Patient Square) based on your bottleneck.

## DocEngage vs Patient Square at a glance

The quick map. These are different categories, so read it as a fit guide.

| | DocEngage | Patient Square (Copilot plan) |
|---|---|---|
| Primary role | Healthcare CRM, engagement | AI-native EHR + Practice Copilot |
| Documentation | Not the core focus | Ambient AI drafts note, ICD-10, Rx |
| Front office | Call centre, IVR, referrals, feedback | Copilot automation (some live, some roadmap) |
| Integration | HL7 FHIR, HIS/EHR connectors | Bundled scribe + EHR |
| Pricing | Confirm with vendor | Per-clinician, Rs 2,399/mo annual + GST |
| Best for | Hospitals, homecare, diagnostics, marketing | Solo and small clinics buried in charting |

If the "documentation" row is what pulled you here, DocEngage was not built to be that tool, and that is fine.

## What DocEngage does well

DocEngage has been at healthcare CRM since 2013, and it shows. The platform is built around patient engagement: call-centre and IVR workflows, click-to-call, referral-network lifecycle management, auto-generated feedback forms, and reminder flows. It reports real operational gains, including fewer no-shows and more follow-ups, and it is HL7 FHIR compliant with connectors into HIS and other EHRs, per its site as of 2026.

For a hospital, homecare provider, or diagnostics chain where the pain is patient communication, referral tracking, and experience, DocEngage is purpose-built. It is not trying to be an ambient scribe, and it does not need to be. If your front desk is drowning in recall calls and no-shows, that is exactly the layer DocEngage targets.

Where it is not aimed is the consult itself. Drafting the note during the visit is not DocEngage's job. That is where Patient Square comes in.

## What an AI-native clinical tool changes

Patient Square starts at the consultation, not the CRM. You open the app before the visit, tap once, and set it down. The scribe listens through the visit and drafts the note in the background, in English, Hindi, Hinglish, or a code-mixed regional language.

The AI Medical Scribe is the core module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. What that means in practice:

- Notes come out in clinical English whatever the spoken language, which suits referrals and claims.
- Audio is used to draft the note, then discarded. Only structured output persists. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
- The prescription is a draft the clinician reviews and signs. The scribe doesn't screen for interactions or dosing; that check stays with the prescriber.

The record layer, the AI Copilot EHR, is bundled in the Copilot plan, and Patient Square frames the wider product as a Practice Copilot because front-office automation is part of the plan too. Some of that is live and some is roadmap, so it is not a full CRM the way DocEngage is. If your core need is documentation with some front-office help around it, book a demo and see the note against your own visits.

## What Patient Square costs, and how to compare fairly

Patient Square publishes per-clinician tiers. The Copilot plan, which bundles the EHR, is Rs 2,399 per clinician per month on an annual plan, ex-GST, about Rs 2,831 with 18% GST. The Assist tier handles documentation only at Rs 1,599 per month annual, and Autopilot sits above. The full ladder is on the [India pricing page](/in/pricing/).

DocEngage pricing depends on the modules and the clinic type, hospital, homecare, or diagnostics, and the fair thing is to confirm it with their team rather than quote a figure we cannot verify. When you compare, remember you may be comparing across categories: a CRM seat and a clinical seat are not the same unit. Decide what problem you are buying for first, then price that.

## When DocEngage is the better choice

Choose DocEngage if your primary need is patient engagement, call-centre or referral-network management, feedback, and marketing-driven experience, especially at hospital, homecare, or diagnostics scale. That CRM layer is what DocEngage is built for, and it does it with years of refinement behind it. If cutting no-shows and running structured patient communication is your top priority, DocEngage is the right category and Patient Square is not competing with it there.

Choose Patient Square if documentation is your biggest daily drain and you want the note drafted for you, with the EHR bundled and some front-office help around it. For a solo GP or small clinic where the real problem is charting, not marketing, the ambient approach is the more direct fix.

## How to decide in a week

1. Name your bottleneck. Engagement and no-shows point to DocEngage. Charting time points to Patient Square.
2. If you need both layers, you may run both, so scope which one you buy first.
3. Trial Patient Square's note quality on real consults, not a demo script.
4. Get pricing on a clear per-seat, ex-GST basis from each, then add GST once.

Patient Square's data-handling posture under the DPDP Act 2023 and the full price ladder sit on the [pricing page](/in/pricing/). If the note is what steals your evenings, book a demo and watch Patient Square draft one against a real clinic day.

_Reviewed by the Patient Square clinical team._

---

## eka.care Alternatives in India: An Honest Comparison
https://patientsquare.com/in/blog/eka-care-alternatives-india/
Published 2026-07-23 · Tags: ehr, eka-care, ai-scribe, alternatives, abdm

Evaluating eka.care for your clinic? A fair look at how Patient Square's ambient-AI EHR and Copilot compare, and where eka.care's ABDM edge still wins.

It depends on what you value most. eka.care is an ABDM-native health platform with its own AI scribe, EkaScribe, and strong ABHA and record-linking features. Patient Square is also ambient-AI-first, with the EHR bundled in the Copilot plan from Rs 2,399 per month on an annual plan, plus GST. If ABDM linking is your priority, eka.care has the edge today. If you want a Copilot-style workflow with transparent per-clinician pricing, Patient Square is worth a look.

Comparing eka.care against Patient Square is not the usual scribe-versus-EMR match-up. Both are ambient-AI-first. eka.care ships EkaScribe, and Patient Square ships its own scribe with the EHR bundled in the Copilot plan from Rs 2,399 per clinician per month on an annual plan, ex-GST. So the honest framing is narrower: this comes down to ABDM depth, product shape, and how each one prices. On ABDM, we will say it plainly up front. eka.care is ahead. You can check Patient Square's [India pricing](/in/pricing/) while you weigh the rest.

This page is a fair comparison, not a takedown. eka.care is a strong India-native platform. The goal is to help you pick the one that fits your clinic, not to pretend one is universally better.

> **Key takeaways**
>
> - Both tools are ambient-AI-first. eka.care ships EkaScribe; Patient Square ships its own scribe with a bundled EHR.
> - eka.care is ABDM-native with live ABHA verification and record linking. Patient Square's ABDM integration is roadmap, not live.
> - Patient Square publishes per-clinician tiers: EHR bundled in Copilot at Rs 2,399/month annual, ex-GST.
> - The real differences are ABDM depth, product breadth, and pricing structure, not whether ambient documentation exists.
> - If ABHA linking is a hard requirement now, eka.care is the safer choice on that axis.

## eka.care vs Patient Square at a glance

The quick map. Confirm current details with both vendors before you commit.

| | eka.care | Patient Square (Copilot plan) |
|---|---|---|
| Ambient scribe | EkaScribe, own LLM (2025) | AI Scribe, ambient, bundled |
| ABDM/ABHA | Native, live | Roadmap, not live |
| EHR | Structured EHR, ABDM-linked | AI Copilot EHR, bundled in Copilot |
| Product breadth | Broad health OS | Practice Copilot, AI-first |
| Pricing | Confirm with vendor | Per-clinician, Rs 2,399/mo annual + GST |
| Languages | Tuned for Indian accents | English, Hindi, Hinglish, 20+ languages |

If the ABDM row is the deciding one for you, this comparison is basically already answered. Read on only if it is not.

## Where eka.care is genuinely strong

eka.care describes itself as an AI-native health OS, and it earns the label. It is ABDM-native: ABHA verification, consent-based record fetch and share, and participation in India's interoperable digital-health network are built in, not bolted on. For a clinic that wants patient records to travel across the ABDM ecosystem, that is a real, present-day capability.

It also ships EkaScribe, which eka.care calls India's first AI medical scribe, built on its own purpose-built LLM and tuned for Indian accents and dialects, as of late 2025. So eka.care is not just a records platform with ABDM plumbing. It is doing ambient documentation too. If you want one India-native vendor covering both the scribe and the interoperability layer, eka.care is a serious, well-built option.

We will not pretend Patient Square matches eka.care on ABDM. It does not, today. That concession is the honest centre of this page.

## Where Patient Square is different

The difference is in shape and pricing, not in whether ambient AI exists. Patient Square is built as a Practice Copilot, with the scribe and the EHR as one product and front-office automation as part of the same vision.

The AI Medical Scribe is the core module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It works in English, Hindi, Hinglish, and 20-plus Indian languages, with notes always in clinical English. A few specifics:

- Audio is discarded after the note drafts. Only structured output persists. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
- The prescription is a draft the clinician reviews and signs. The scribe doesn't screen for interactions or dosing; that check stays with the prescriber.
- The record layer, the AI Copilot EHR, is bundled in the Copilot plan rather than sold separately.

The other practical difference is pricing transparency. Patient Square publishes per-clinician tiers you can read without a call. If you want to know exactly what a seat costs before you talk to anyone, that clarity is worth something. Book a demo if you want to see the note and the workflow against your own visits.

## Pricing, side by side

Patient Square's Copilot plan bundles the EHR at Rs 2,399 per clinician per month on an annual plan, ex-GST, which is about Rs 2,831 with 18% GST. Below it, the Assist tier handles documentation only at Rs 1,599 per month annual, and Autopilot sits above with the full stack. The whole ladder is public on the [India pricing page](/in/pricing/).

eka.care's pricing varies by product and configuration, and the fairest thing we can say is to confirm it directly with their team, since we are not going to quote a number we cannot verify. When you compare, put both on the same basis: per clinician, per month, ex-GST, then add GST once. That is the only apples-to-apples way to read them.

## When eka.care is the better choice

Choose eka.care if ABDM and ABHA record linking sit at the centre of your requirements, or if you want an established India-native health OS with a live scribe and broad platform coverage. Its ABDM-native design and its own LLM are genuine strengths, and on interoperability it is ahead of Patient Square today. If record continuity across the ABDM network is your top concern, eka.care is built for exactly that, and switching away to save on a per-seat price would cost you the thing you most wanted.

Choose Patient Square if you want a Copilot-style workflow with the scribe and EHR as one bundled product, transparent per-clinician pricing you can read up front, and you are comfortable that ABDM linking is on the roadmap rather than live. For a clinic whose priority is documentation and a clean, predictable price, that fit is strong.

## How to decide in a week

1. Rank ABDM. If ABHA linking is required now, eka.care is the safer pick and this decision is mostly made.
2. If ABDM can wait, compare the two scribes on your own consults, side by side.
3. Get both prices on the same basis, per clinician per month ex-GST, then add GST.
4. Ask each vendor the audio-retention question and get the answer in writing.

Patient Square's data-handling posture under the DPDP Act 2023 and the full price ladder are on the [pricing page](/in/pricing/). If your priority is a bundled, transparently priced ambient tool and ABDM can follow later, book a demo and test the note against a real clinic day before you decide.

_Reviewed by the Patient Square clinical team._

---

## ABDM Milestone 2 (M2) Explained for Clinics
https://patientsquare.com/in/blog/abdm-milestone-2-explained-clinics/
Published 2026-07-22 · Tags: abdm, milestone-2, vendor-certification, clinic-software, nha

What ABDM milestones M1, M2, and M3 mean in plain language, and the questions a clinic should ask its software vendor about ABDM certification.

It is a stage in the NHA's vendor-certification path where a software product demonstrates it can exchange health records, typically the ability to link and share records, building on the create-and-link ABHA capability of the earlier milestone. Exact scope is defined by the NHA, so confirm current details on the official ABDM sandbox.

"ABDM ready" is one of the most oversold phrases in Indian health software. It hides a real question: ready for what, exactly? The NHA certifies software vendors against a set of milestones, usually described as M1, M2, and M3. Each covers different capabilities. This post explains what those milestones mean at a plain-language level, what Milestone 2 is about, and the exact questions to put to your vendor before you believe the label.

> **Key takeaways**
> - ABDM milestones (M1, M2, M3) are a vendor-certification path run by the NHA, not something a clinic passes.
> - M1 broadly covers creating and linking ABHA. M2 broadly covers exchanging or linking health records. M3 covers deeper Health Information Provider capabilities.
> - There is a real gap between passing in the sandbox and running in production. Ask which one your vendor means.
> - Do not accept "ABDM ready" without a milestone name and a production-versus-sandbox answer.
> - AI Medical Scribe by Patient Square is not ABDM-certified today; ABDM integration is on the roadmap.

_Source: ABDM and NHA portals; confirm current milestone definitions there._

## Why the milestone question matters

A vendor can say "ABDM ready" the moment they touch the sandbox. That does not mean patients at your clinic can actually link records under ABDM. Certification runs in stages, and each stage enables different functionality. If you buy on the label alone, you can end up with software that demoed well and does very little of what you assumed.

The fix is to make the vendor name the milestone and say whether it is live in production. That single question filters out most of the fog.

## What the milestones broadly cover

The NHA defines the exact scope, and it can change, so treat the descriptions below as the well-known structure rather than a legal spec. Confirm current details on the ABDM portal.

- **M1** broadly covers the ABHA basics: creating an ABHA and linking it. This is the entry point. A product at M1 can help a patient get onto ABDM, but that is roughly where it stops.
- **M2** broadly covers exchanging or linking health records. This is where a product moves from "can create an ID" to "can participate in record sharing." For a clinic, M2-class capability is what starts to make ABDM useful in day-to-day care.
- **M3** broadly covers deeper Health Information Provider (HIP) capabilities, the fuller set of functions a system needs to serve records into the ecosystem reliably.

If those descriptions feel qualitative, that is on purpose. The precise checklists live with the NHA and get revised. What stays true is the shape: create and link first, exchange records next, deeper provider capability after.

## What Milestone 2 means for a clinic

M2 is the one most clinics actually care about. M1 gets a patient an ABHA, which is useful but limited. M2 is where record exchange enters the picture: linking a patient's records so they can flow, with consent, into the wider system.

Put plainly: a product certified at M2 in production can do more of the interoperability work you probably imagined when you first heard "ABDM." A product stuck at M1, or only at M2 in the sandbox, cannot yet.

This is why the milestone label is worth chasing. "We support ABDM" could mean M1 in a test environment. It could mean M2 in production. Those are very different products for your front desk and your patients.

## Sandbox versus production, the gap nobody mentions

There are two worlds in ABDM certification. The sandbox is a test environment. Production is the live system real patients use. A vendor can pass a milestone in the sandbox long before anything works for your actual clinic.

So there are really two questions, not one:

1. Which milestone has the vendor completed?
2. Is that milestone live in production, or only in the sandbox?

A confident "M2, in production" is a real answer. A vague "we're ABDM ready" that dodges both parts is a signal to keep asking.

## Questions to put to your software vendor

Bring these to any vendor pitching ABDM support. Ask for evidence, not adjectives.

| Question | Why it matters | Weak answer |
|---|---|---|
| Which ABDM milestone have you completed? | Forces a specific claim | "We're ABDM ready" |
| Is it live in production or only in the sandbox? | Separates demo from reality | "It works in our environment" |
| Can you show current certified status? | Verifiable, not marketing | "Trust us" |
| Does it create ABHA, link records, or both? | Maps to M1 vs M2 capability | "It does ABDM" |
| How is patient consent captured for record sharing? | Ties to DPDP obligations | Silence |

That last row connects to your own obligations. Record sharing under ABDM has to sit inside lawful, consent-based handling. Our [DPDP guide for clinics](../dpdp-act-clinics-guide/) covers the consent and data-protection side in more detail.

## How ABHA linking fits at the desk

Whatever milestone your vendor claims, the front-desk reality is an ABHA-linking step during registration. If you are setting that up, the [ABHA linking clinic workflow](../abha-linking-clinic-workflow/) post walks through it, and the [ABHA number vs address explainer](../abha-number-vs-abha-address-explained/) clears up the two things patients confuse. Doctors registering themselves on the provider side will want the [HPR registration guide](../hpr-registration-guide-doctors/).

There is also a financial angle worth knowing. The NHA's Digital Health Incentive Scheme can pay facilities for eligible KYC-verified ABHA-linked transactions, but an M2 label alone does not establish eligibility. Record category, volume, patient limits, the participant's role, production milestone, API version, security evidence, and claim timing all matter under the effective corrigendum. The [ABDM incentives for doctors](../abdm-incentives-for-doctors/) guide owns the current rates and shows its source-check and next-review dates, so volatile numbers do not drift across several posts.

## Where AI Medical Scribe by Patient Square sits in all this

Straight answer: AI Medical Scribe by Patient Square is not ABDM-certified today, and we will not imply otherwise. ABDM integration is on the roadmap, not shipped. We do not assert any milestone status for the product.

What the scribe does is separate from certification. It listens during the consult and drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft in about two minutes. You review and sign. The record stays yours. So the milestone conversation is one you have with your clinic-software or HMS vendor about record exchange; the scribe is about producing the clinical note quickly and accurately. If you want the note-drafting picture on its own, see the [scribe overview for Indian doctors](../scribe-for-doctors-india/).

## The short version

Milestones belong to vendors, not clinics. M1 is create-and-link ABHA. M2 is record exchange, and it is the one that makes ABDM feel useful. M3 is deeper provider capability. Sandbox is not production. Before you believe "ABDM ready," get the milestone name and the production answer in writing.

Curious how a signed clinical note comes together in about two minutes, with no integration project on your side? <a href="/in/how-it-works/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and see it on a real visit, then check the [security page](../../security/) for how we handle data.

---

## AI Medical Scribe for Locum Tenens: One Tool, Any EHR
https://patientsquare.com/us/blog/ai-scribe-for-locum-tenens/
Published 2026-07-22 · Tags: ai-scribe, locum-tenens, ehr-agnostic, clinical-documentation, physician-workflow

Locum physicians face a new EHR every assignment. An EHR-agnostic ambient scribe needs no site IT project, so your notes travel with you between facilities.

No. It listens during the visit and hands back a structured note you copy or paste into whatever system that site runs. There is no integration project and no site IT ticket, so it works the same on your first day at a new assignment as your last.

Locum physicians live with a problem staff docs rarely think about: a different EHR at almost every assignment. An ambient AI scribe that works the same way regardless of the system underneath solves the part of the job that actually eats your evenings, the documentation. Patient Square listens during the visit, then hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes later. You review it, sign it, and paste it into whatever chart the facility uses. No integration, no IT ticket, no waiting for the site to set anything up.

> **Key takeaways**
> - A locum scribe should be EHR-agnostic, since you cannot count on the same system twice.
> - Patient Square never connects to the EHR, so there is no per-site integration project to schedule.
> - You copy or paste the finished note into Epic, athenahealth, eClinicalWorks, Elation, NextGen, or a legacy system.
> - Notes belong to the practice you document for and can be exported or deleted anytime.
> - The signing clinician stays legally responsible for the record, the same as with a human scribe.

_Source: pricing and product behavior described on the [pricing page](../../pricing/)._

## Why locum work breaks EHR-tied documentation tools

A scribe built to plug into one EHR assumes stability you do not have. Staff physicians keep the same system for years, so a deep integration pays off. Locums churn. New facility, new login, new documentation rules, sometimes every few weeks. A tool that needs a site integration is a tool you cannot use on day one, which is exactly when you need it most.

Credentialing already burns your time. Every assignment means fresh privileging paperwork, a new badge, a new orientation. Adding "wait for IT to wire up my scribe" to that list is a non-starter. The whole appeal of locum work is mobility. Your documentation tool has to match it.

Then there is note portability. If your notes live inside one facility's EHR-linked tool, they are stranded there when the contract ends. You want the opposite: a note you generate, review, and place into the chart yourself, so the record lands where it belongs and nothing follows you to the next site that should not.

## How an ambient scribe fits a locum assignment

The flow is the same everywhere, which is the point. You start the visit, the scribe listens, and roughly two minutes after you finish it returns a draft. You read the note against what actually happened, fix anything that needs fixing, sign, and move the text into the chart.

Because Patient Square does not talk to the EHR, an unfamiliar system only slows the clicking, not the writing. You might spend your first morning at a new site hunting for where the note field lives in their build of eClinicalWorks. The note itself is already done. Paste, sign, next patient.

Audio is processed in memory and discarded the moment the note drafts. Nothing is recorded or kept. For a clinician rotating through facilities with different privacy cultures, that matters: there is no growing archive of visit recordings trailing you from contract to contract.

## What a locum scribe must actually do

Not every ambient tool is built for someone who changes sites constantly. Here is what the job demands and how Patient Square lines up.

| Locum need | Why it matters | How Patient Square handles it |
| --- | --- | --- |
| No per-site integration | You cannot wait on IT at each assignment | Scribe never connects to the EHR; copy or paste the note |
| Works on any system | Epic here, a legacy tool next month | System-agnostic by design |
| Portable, review-first notes | Records must land in the right practice | You review, sign, then place the note yourself |
| No retained audio | Different sites, different privacy expectations | Audio discarded once the note drafts |
| Fast turnaround | Short assignments, high volume | Draft back in about two minutes |
| Clear ownership | Notes are the practice's, not yours to carry | Notes belong to the practice, exportable or deletable |

The pattern underneath all of it: the scribe stays out of the EHR and out of the site's plumbing. That is what lets it behave identically whether you are covering an ED in one state or a rural clinic in another.

## The prescription draft, and where your judgment stays

Alongside the note, the scribe produces a prescription draft. It writes out the drug, the dose, and the instructions you dictated, so the order you already decided on is typed for you rather than by you.

Read that carefully, because the boundary matters for locums especially. It is a draft. It never sends to a pharmacy. There is no e-prescribing, no pharmacy gateway, no SureScripts connection. The scribe does not screen for interactions, dosing, or contraindications; there is no automated check and no block. You are the one who reviews and prescribes through whatever ordering system the facility uses, and at a new site where you may not know a patient's history cold, that read is entirely yours to make. The draft saves the typing; the safety check is you.

Same logic on the ICD-10 side. The scribe suggests codes based on what was said in the room. You confirm or change them. It structures the encounter; it does not diagnose, and it does not interpret images or studies. Related reading on that: [how ICD-10 suggestions work](../ai-scribe-icd-10-suggestions-explained/).

## When an EHR-agnostic scribe is the right call

If you were a staff physician on one system for a decade, a deeply integrated scribe might be worth the setup cost. For locum work, the calculus flips. You want zero setup and total portability, even at the price of copy-paste instead of auto-filing.

Some clinicians ask whether they should just learn each site's built-in AI charting instead. Two problems with that. First, you would relearn a different tool at every assignment. Second, availability varies wildly, and plenty of the systems you will meet have no ambient scribe at all. We wrote more on that tradeoff in [ambient scribe versus a new EHR](../ai-scribe-vs-new-ehr/) and in [why an ambient layer beats Epic's built-in charting for many clinicians](../ai-scribe-vs-epic-ai-charting/).

The copy-paste step is real, and worth naming plainly. You do move text by hand into the chart. In exchange you get a documentation tool that is the same on assignment one as assignment fifty, with no dependency on any facility's IT calendar. For most locums, that trade is easy.

## Setup between assignments

Setup is a login, not a project. There is nothing to install at the facility and nothing for their IT team to approve on the scribe side. Confirm the BAA with whoever the covered entity is for your engagement, set which practice your notes file under, and you are documenting on your first patient.

If you are weighing options, our guide on [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) walks through the questions that matter, and the [best AI medical scribes](../best-ai-medical-scribes/) overview puts the category in context. On compliance specifics, the [HIPAA, BAA, and consent](../ai-scribe-hipaa-baa-consent/) page covers what to check before your first documented visit.

Ready to see it against your own workflow? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring the messiest assignment you can think of. We will show you the note coming back in about two minutes, on whatever screen happens to be in front of you.

---

## Epic EMR Cost in 2026: What You'll Actually Pay
https://patientsquare.com/us/blog/epic-emr-cost/
Published 2026-07-22 · Tags: ehr, pricing, epic, cost

What Epic EMR really costs a practice, from licensing to implementation, why it's quoted per deal, and a transparent EHR alternative at $119/mo for small clinics.

Epic does not publish prices, but 2026 industry estimates put a small-clinic Epic build at roughly $100,000 to $300,000 upfront, plus $50,000 to $150,000 a year to run. Per-physician clinical licenses are commonly estimated at $5,000 to $7,000. Every Epic contract is custom-quoted, so these are benchmarks, not a rate card.

Epic EMR costs a small practice roughly $100,000 to $300,000 to stand up and another $50,000 to $150,000 a year to run, based on 2026 industry estimates, and Epic publishes none of those numbers. Every contract is custom-quoted. If you run an independent clinic, that opacity is the real problem, not the sticker. Patient Square puts its EHR at a flat $119 per clinician per month on annual billing, and you can see [our full pricing](../../pricing/) before you talk to anyone.

> **Key takeaways**
>
> - Independent estimates put a small-clinic Epic build at about $100,000 to $300,000 upfront, plus $50,000 to $150,000 per year to operate.
> - Per-physician clinical licenses are commonly estimated at $5,000 to $7,000, and Epic publishes no public price at all.
> - Implementation, hosting, training, and data migration stack on top of the license, often tens of thousands more.
> - Patient Square bundles a full AI EHR into the Copilot plan at $119 per clinician per month, annual, with no per-seat surprises.

## What does Epic EMR actually cost in 2026?

Here's the honest version. Epic doesn't publish a price, so the figures below are aggregated from independent 2026 estimates, and they carry wide ranges because Epic quotes every deal separately. Read them as benchmarks.

| Cost component | Typical 2026 estimate | Notes |
|---|---|---|
| Small-clinic upfront build | $100,000–$300,000 | Software, hardware or hosting, implementation, training |
| Per-physician clinical license | $5,000–$7,000 | Full clinical access, one physician |
| Annual operating cost | $50,000–$150,000 | Roughly $4,000–$12,000 a month all-in |
| Annual maintenance | 15–20% of initial spend | On top of operating cost |
| Data migration | Tens of thousands | Scales with record volume and complexity |

Those numbers come from independent guides (TactionSoft and EMR Guides, 2026) that reverse-engineer Epic pricing from real deals, since Epic itself confirms nothing publicly. A cloud-hosted Epic seat is sometimes cited at $200 to $500 per user per month, which lowers the upfront bill but keeps the operating cost high.

None of this makes Epic a bad product. It's built for scale, and at scale the math works. The issue for a small clinic is that you inherit enterprise-grade pricing and the IT staffing that goes with it. If you'd rather see a number today than earn a quote, [our pricing page](../../pricing/) lists every tier.

## Why is Epic's pricing so opaque?

Epic sells to organizations, not to individual clinicians, and it configures each install around that organization's size, specialties, modules, and hosting choice. So the price genuinely does vary. It also means there's no list price to compare against, and the number you eventually get is negotiated in a process the vendor designed.

For a hospital with a procurement team and consultants, that's normal enterprise software buying. For a solo doctor or a three-provider clinic, it's a wall. You can't budget without a sales cycle, you can't compare Epic to two alternatives on a spreadsheet, and you're negotiating against a party that has done this thousands of times and knows exactly where the give is. Opaque pricing isn't a scandal. It's just a structure that favors the seller, and small buyers feel that most.

## Where Epic is genuinely the right choice

We'll say it plainly: if you run a large integrated health system, Epic is often the correct pick, and no honest cost post pretends otherwise. Deep interoperability across dozens of departments, a mature app ecosystem, and a single record spanning inpatient and outpatient care are real advantages, and Epic does them at a scale few vendors match. If that's your world, the six-figure build is buying something.

The trouble is that most US clinics aren't that world. A small primary care practice doesn't need cross-department inpatient workflows. It needs charting that doesn't eat the evening, clean codes, and a bill it can predict. Paying enterprise money for enterprise capability you'll never touch is the classic small-practice EHR mistake.

## What does a transparent EHR cost instead?

This is the contrast we care about. Patient Square publishes its price, and the EHR is bundled into the Copilot plan at $119 per clinician per month on annual billing, or $149 month-to-month. There's no separate implementation invoice, no per-seat gotcha at renewal, and no sales process required to learn the number.

Patient Square EHR is a real EHR, not a bolt-on scribe. The Copilot plan's AI Copilot EHR includes ambient AI notes that draft during the visit, ICD-10 suggestions you confirm, prescription drafts, and front-office automation. The pricing runs three tiers: Assist at $79 per clinician per month annual (no EHR, scribe-style documentation only), Copilot at $119 with the EHR bundled, and Autopilot at $199 for the full self-running practice. Entry pricing starts from $79 a month; the EHR starts from $119.

Here's the same decision Epic forces, laid out side by side.

| | Epic (small clinic) | Patient Square Copilot |
|---|---|---|
| Published price | No | Yes, $119/clinician/mo annual |
| Upfront implementation | $100k–$300k (est.) | None |
| EHR included | Yes, enterprise-scale | Yes, AI-native |
| Ambient AI notes | Add-on / module | Included |
| Dedicated IT team needed | Typically yes | No |
| Best fit | Large health systems | Small and independent practices |

If you're an independent clinic, the choice isn't really Epic versus a lesser product. It's enterprise pricing you can't see against a flat rate you can. Compare it yourself on [our pricing page](../../pricing/), or book a demo and run it on a real clinic day.

## How to budget for an EHR without getting surprised

A few things save small practices from cost shock, whichever vendor they pick.

Ask for the all-in number, not the license. The software subscription is often only 40 to 60 percent of the real cost once implementation, training, and data migration land, per RXNT's 2026 budgeting guide. Ask what the price does at renewal, since a low first-year rate that jumps later is common. Ask who does data migration and what it costs, because moving records between systems can run into the tens of thousands. And ask whether you need on-site IT, since cloud systems that run without a server room are why over 70 percent of new EMR implementations in 2026 went cloud.

The cleanest defense is a vendor whose price you can read before the sales call. That's the whole point of a published rate: it puts you and the seller on the same side of the table. See where Patient Square lands on [our pricing page](../../pricing/), compare it against the [full EMR cost picture](../emr-system-cost-guide/), or look at the [best EMR options for small practices](../best-emr-for-small-practice/).

## The bottom line on Epic EMR cost

Epic is enterprise software priced like enterprise software. For a hospital, that's fair. For a small or independent practice, the six-figure build and the missing price tag are the reasons to look elsewhere. A transparent EHR at $119 per clinician per month, bundled with ambient AI notes and coding, does what a small clinic actually needs without the quote-to-quote guessing game. You can see the number today.

---

## Best EMR for Urgent Care (2026): An Honest Roundup
https://patientsquare.com/us/blog/best-emr-for-urgent-care/
Published 2026-07-21 · Updated 2026-07-22 · Tags: comparison, urgent-care, buying, ehr

Experity, athenahealth, and eClinicalWorks compared on throughput, billing, and cost per provider. Plus where an ambient AI scribe with a bundled EHR fits.

There isn't one winner for every clinic. Experity is the purpose-built option and tends to win on throughput and occupational-medicine billing. athenahealth suits clinics that want billing handled on a percentage-of-collections model. eClinicalWorks fits groups that prefer a conventional per-provider SaaS bill. The deciding factor is usually your visit volume and whether you want to run billing in-house.

The best EMR for urgent care depends on your volume and how you want billing handled. Experity wins for high-throughput, multi-site groups that need queue control and occupational-medicine billing. athenahealth suits clinics that want claims run for them on a percentage of collections. eClinicalWorks fits groups that prefer a plain per-provider SaaS bill. Below we compare them honestly, and we'll tell you where our own tool fits: we build [Practice Copilot](/us/products/practice-copilot/), an ambient scribe with a bundled EHR, and it isn't the right pick for every urgent care. If you just want a price without a sales call, ours is on the [pricing page](/us/pricing/).

> **Key takeaways**
>
> - Experity is purpose-built for urgent care and leads on throughput; published reviews cite roughly 35-minute patient throughput and charting 80 percent of common visits in under a minute.
> - Pricing splits by model: about $400 per provider per month for Experity, near $449 for eClinicalWorks EHR-only, and 4 to 7 percent of collections for athenahealth, per 2026 comparisons.
> - The EMR stores your chart; it doesn't write your note. At 40-plus visits a day, an ambient scribe is where the time actually comes back.
> - Practice Copilot bundles a real EHR at a published $119 per clinician per month on the annual Copilot plan, no quote required.

## What actually matters when you pick an urgent care EMR

Start with the shape of your day. An urgent care provider doesn't work like a primary-care physician with a known panel. You see a wider mix of acute complaints, at higher volume, with patients you've usually never met. There's little prior context in the chart, and the pressure to document between rooms is relentless. So the features that decide it aren't the ones vendors put on the front of the brochure.

Three things carry the decision: throughput, billing model, and how the note gets written. Everything else is a tiebreaker.

Throughput is queue control, room turnover, and how fast a provider can chart a common visit. Billing model is whether you run claims in-house or hand them off. And note-writing is the quiet one clinics forget to score, right up until they're finishing charts at 9pm.

## Experity: built for urgent care, priced like it

Experity is the only major platform built exclusively for urgent care, with the largest purpose-built installed base in the category. That focus shows up in the workflow. Published reviews report that providers chart roughly 80 percent of common urgent care visits in under 60 seconds, with patient throughput around 35 minutes and about a 50 percent cut in charting time.

The trade-off is price and scope. Experity starts near $400 per provider per month, per 2026 comparisons, and it's tuned for high-volume groups that care most about patient flow, queue management, and occupational-medicine billing. For a busy multi-site operator, the throughput gains tend to pay back that premium inside a year. For a single clinic doing lower volume, you're paying for capacity you may not use.

**Pick Experity if:** you run high-volume or multi-site urgent care, do meaningful occ-med billing, and want a system that was designed for exactly this.

## athenahealth: hand off the billing, pay a percentage

athenahealth takes a different bet. Instead of a flat per-provider fee, it charges a percentage of what you collect, commonly cited at 4 to 7 percent with a per-provider minimum. The pitch is alignment: the vendor only makes more when you do. Behind that sits a large claims operation, tens of thousands of billing rules, and a rules engine that scrubs claims before they go out. It won multiple Best in KLAS awards for 2026.

Percentage pricing is a real fork in the road. For a clinic with thin margins and messy denials, offloading the billing headache can be worth every point. For a high-collections group, that same percentage can quietly become the most expensive line item you have. Run your own numbers before you sign; a percentage that looks small on a demo slide scales with your revenue.

**Pick athenahealth if:** you'd rather not staff billing, your denial rate is a problem, and you're comfortable trading a slice of collections for that.

## eClinicalWorks: the conventional SaaS route

eClinicalWorks is the familiar model: a per-provider subscription, billing you manage in-house, and one of the largest general ambulatory footprints in the market. Published 2026 comparisons put the EHR-only plan near $449 per provider per month, with EHR plus practice management higher. It carries AI documentation features and broad configuration options.

The upside is control and predictability; you own the billing and the bill is a known number. The downside is that it's a general ambulatory system, not an urgent-care-native one, so you'll do more configuring to get urgent-care flow out of it. That's fine for a group that wants one platform across several service lines. It's more setup than a single urgent care clinic usually wants.

**Pick eClinicalWorks if:** you want a predictable per-provider bill, you keep billing in-house, and you're running more than just urgent care.

## Where an ambient scribe with a bundled EHR fits

Here's the honest part. Every system above stores the chart. None of them writes the note for you unless you add an AI layer, and even then the note is usually a side feature, not the point of the product.

We build [Practice Copilot](/us/products/practice-copilot/), and the point of the product is the note. AI Medical Scribe by Patient Square is one module inside it: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On the Copilot plan, that scribe comes with a bundled EHR, so the note lands in a chart you own without a second login or an export step.

For urgent care, the math is simple. On a 40-patient Saturday, the minutes you lose aren't in the exam, they're in the charting between rooms. An ambient scribe takes that back. And the price is on the page: EHR bundled from $119 per clinician per month on the annual Copilot plan, no demo required to learn the number. If you want to talk through it, book a short demo; if you just want the price, it's already public.

We won't pretend this replaces Experity's occ-med billing depth or athenahealth's claims machine. It doesn't. What it does is fix the part that keeps urgent care providers late: writing the note.

## How to choose in one pass

Score your clinic on three questions. What's your daily volume? Do you want to run billing or hand it off? And how late are your providers finishing charts?

High volume, occ-med heavy, billing in-house leans Experity. Want billing off your plate leans athenahealth. Predictable per-provider bill across multiple service lines leans eClinicalWorks. And if the real pain is documentation time and you want a transparent price, that's where a bundled scribe like Practice Copilot earns its place.

Whatever you shortlist, do one thing before you sign: make each vendor show you a real charted visit, timed, not a canned demo. The number that matters isn't on the pricing page. It's how many minutes a provider spends per note when the waiting room is full.

## Frequently asked questions

The FAQ above answers the common ones: which EMR wins for which clinic, real cost ranges, whether you need a scribe on top, and why some prices are quote-only while ours is published. If you're comparing on price specifically, the [pricing page](/us/pricing/) has the full Practice Copilot breakdown, and a demo walks through the scribe on your own visit types.

---

## AI Medical Scribe for Podiatry: Wound & Procedure Notes
https://patientsquare.com/us/blog/ai-scribe-for-podiatry/
Published 2026-07-20 · Updated 2026-07-22 · Tags: podiatry, ai-medical-scribe, wound-care-notes, procedure-documentation, clinical-documentation

An ambient AI scribe drafts podiatry notes for wound care, debridement, and nail procedures from what you dictate. You review, code, and sign.

No. It captures your description. If you say the ulcer is a Wagner grade 2, plantar, 2 by 3 centimeters with granulation tissue, that is what the note reflects. The scribe does not look at the wound or grade it. Your exam and staging stay yours.

Podiatry notes carry a lot of detail: wound dimensions, staging, the exact tissue you debrided, the vascular check, the offloading plan. An ambient AI medical scribe drafts all of it from what you dictate during the visit, then hands the note back about two minutes after the patient leaves. It captures your wound description and your procedure narration; it never looks at the foot or grades the ulcer itself. You review the draft, confirm the codes, and sign. The exam stays yours.

> **Key takeaways**
> - The scribe drafts podiatry wound and procedure notes plus ICD-10 suggestions about two minutes after the visit; you review and sign.
> - It captures your wound staging (for example Wagner grade 2) and procedure detail from dictation. It does not view or grade the wound.
> - Debridement and nail-procedure documentation reflect what you say you did. You confirm the CPT.
> - It runs alongside any podiatry EHR. Copy or export. No integration.
> - Audio is discarded the moment the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## How an ambient scribe fits a podiatry visit

A wound-care visit has a rhythm. You unwrap the dressing, look at the ulcer, measure it, decide whether to debride, do the procedure, redress it, and set the offloading and follow-up. A routine nail visit is quicker but still needs the procedure documented and the risk status recorded. Both generate notes with a lot of moving parts.

The scribe listens while you work and narrate. When you say the plantar ulcer is Wagner grade 2, roughly 2 by 3 centimeters, with granulation tissue at the base and no exposed bone, that description goes in the note. When you describe sharp debridement down to healthy bleeding margins, that becomes the procedure note. Two minutes after the patient leaves, you have a draft.

The habit that makes this work is describing what you see and do out loud. Podiatrists already tend to narrate wound findings, partly for the patient and partly out of documentation discipline. The scribe turns that narration into the note.

## What a podiatry scribe must capture

The vocabulary here is dense and specific. The scribe has to land these terms accurately when you speak them.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| Ulcer staging | "Plantar ulcer, Wagner grade 2, 2 by 3 cm, granulation base" | Wound description with stage and size |
| Debridement | "Sharp debridement of devitalized subcutaneous tissue to healthy margins" | Procedure note with tissue level |
| Nail procedure | "Debrided six dystrophic nails, no bleeding" | Nail care procedure |
| Gait / biomechanical exam | "Pronated foot type, hallux limitus, antalgic gait" | Biomechanical findings |
| Offloading | "Total contact cast applied" or "offloading with a surgical shoe" | Offloading plan |
| Vascular check | "Pedal pulses palpable bilaterally, ABI 0.9, cap refill under 2 seconds" | Vascular exam findings |
| Neuro / protective sensation | "Monofilament absent at three sites, loss of protective sensation" | Neuro exam line |
| Follow-up | "Recheck in one week for redebridement" | Plan with interval |

The vascular and neuro findings carry weight for medical necessity in diabetic foot care. If you check the pulses and the monofilament and say so, the note supports the level of care. If you skip narrating them, they will not appear, because the scribe records only what it hears.

## When wound and procedure documentation is the bottleneck

Debridement coding is unforgiving. The CPT depends on the depth of tissue removed and the surface area, and the note has to match exactly. A note that says "debrided the wound" without the tissue level and area invites a downcode or a denial.

The scribe helps by getting your procedure narration into the note reliably. When you say you did sharp debridement of subcutaneous tissue over a specific area, that language lands in the procedure section. You then confirm the code:

| CPT | Procedure |
|---|---|
| 11042 | Debridement, subcutaneous tissue, first 20 sq cm or less |
| 11043 | Debridement, muscle and/or fascia |
| 11720 | Debridement of nails, 1 to 5 |
| 11721 | Debridement of nails, 6 or more |

The scribe does not pick the CPT. Whether you debrided subcutaneous tissue or muscle, and how many square centimeters, are your calls. What the scribe does is make sure the note reflects the depth and extent you described, so your code matches your documentation. That alignment is the difference between a clean claim and a fight with the payer.

## The diabetic foot, coded with care

A lot of podiatry volume is diabetic foot care, and the coding has to capture both the ulcer and the underlying diabetes for medical necessity. After the visit the scribe suggests ICD-10 codes from what you said:

| Condition | ICD-10 suggestion |
|---|---|
| Non-pressure chronic ulcer, other part of foot | L97.5- (site and severity specific) |
| Onychomycosis (fungal nail) | B35.1 |
| Type 2 diabetes with foot ulcer | E11.621 |
| Peripheral vascular disease | I73.9 |

These are suggestions, not final coding. The ulcer codes get specific about laterality, site, and severity, and you confirm those. When the ulcer is diabetic, pairing the diabetes code with the ulcer code is what supports the visit. Our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) covers the logic.

## Vascular findings are captured, not measured

Being clear about the boundary again. The scribe does not perform your vascular check and it does not read an ABI study. It records what you say. If you state the pedal pulses are palpable and the ABI was 0.9, that goes in the note because you spoke it. If you say the dorsalis pedis is non-palpable and you are referring to vascular, the referral is drafted.

The reasoning about whether the wound has the perfusion to heal, whether the patient needs a vascular workup, whether offloading is enough, that is yours. The scribe writes it down. It does not decide it.

## The prescription draft for wound infections

Foot infections often need antibiotics, and the scribe drafts a prescription when your plan calls for one. If you decide to start an oral antibiotic for a mild infection, that draft reflects what you said, writing out the drug and dose so you don't retype the order.

The scribe does not screen the draft or check the dose. For podiatry patients, where so many have diabetic kidney disease and antibiotic dosing shifts with renal function, that renal-dose read is exactly the check you already run, and it stays yours. The draft never goes to a pharmacy and there is no e-prescribing connection. You review it against the patient's kidney function, adjust the dose, and act on it in your own workflow. More detail in our post on [prescription draft safety](../ai-scribe-prescription-draft-safety/).

## When it is worth trying

If your wound-care and procedure charting is fast and complete, you may not need help. If you are spending your lunch break catching up on procedure notes, or your debridement documentation does not always match your coding, the scribe is worth a trial.

Pricing starts from $79 per clinician per month on the annual Assist plan, then steps up to Copilot and Autopilot, which add a bundled AI EHR, messaging, and receptionist and follow-up automation. On the scribe-only plan it works alongside your existing podiatry EHR with no integration and no IT setup, exporting the finished note rather than writing into your system. See our [roundup of AI medical scribes](../best-ai-medical-scribes/), our [primary care scribe overview](../ai-scribe-for-primary-care/) for shared-care patients, and [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before you decide.

Want to see it on a real wound-care visit? Book a demo. Pricing is on the [pricing page](../../pricing/), and compliance details are on the [security page](../../security/).

---

## HealthPlix Alternatives in India: The Ambient-AI EHR Option
https://patientsquare.com/in/blog/healthplix-alternatives-india/
Published 2026-07-20 · Updated 2026-07-22 · Tags: ehr, healthplix, clinic-software, alternatives, ai-scribe

Comparing HealthPlix EMR for your clinic? Here is how Patient Square's ambient-AI EHR stacks up on documentation, pricing, and Indian-language support.

If your main pain is note-taking, yes. HealthPlix is a template-driven EMR built for fast prescription writing across many specialties. Patient Square takes a different route: an ambient AI listens to the consult and drafts the note, ICD-10 codes, and prescription for you, so you are not typing or picking templates during the visit. The EHR is bundled in the Copilot plan from Rs 2,399 per month on an annual plan, plus GST.

Shopping for a HealthPlix alternative usually means one thing: you like the idea of a digital EMR, but the typing and template-picking during a busy OPD still eats your day. The short answer is that Patient Square goes at the same problem from the other side. Instead of helping you write a prescription in 30 seconds, an ambient AI listens to the consult and drafts the note, ICD-10 codes, and prescription for you. The EHR comes bundled in the Copilot plan from Rs 2,399 per clinician per month on an annual plan, ex-GST. You can see the [India pricing](/in/pricing/) before you read another word.

Both tools are trying to give you back your evenings. They just make different bets about how.

> **Key takeaways**
>
> - HealthPlix is a mature, template-driven EMR with 14,000-plus doctors across 16 specialties and 30-second prescription writing, as of 2025.
> - Patient Square's bet is ambient AI: the scribe listens and drafts the note, codes, and Rx, so you type less during the visit.
> - HealthPlix published Pro at roughly Rs 11,999/year and Elite at Rs 17,999/year in 2025. Patient Square's Copilot plan bundles the EHR at Rs 2,399/clinician/month annual, ex-GST.
> - Both support Indian languages. HealthPlix helps you write faster in 14 languages; Patient Square listens across 20-plus and drafts for you.
> - HealthPlix already ships ABDM features. Patient Square's ABDM integration is roadmap, not live.

## HealthPlix vs Patient Square at a glance

Here is the honest side-by-side. Prices are indicative and change, so treat this as a starting map, not a quote.

| | HealthPlix EMR | Patient Square (Copilot plan) |
|---|---|---|
| Core approach | Template-driven EMR, fast Rx writing | Ambient AI scribe + bundled EHR |
| Documentation | You write, assisted by templates | AI drafts note, ICD-10, Rx from the conversation |
| Indian languages | Rx in 14 languages (2025) | Listens in English, Hindi, Hinglish, 20+ languages |
| Pricing | Pro ~Rs 11,999/yr, Elite ~Rs 17,999/yr (2025) | EHR bundled in Copilot, Rs 2,399/mo annual + GST |
| ABDM/ABHA | Available | Roadmap, not live |
| Installed base | 14,000+ doctors, 16 specialties (2025) | Newer entrant, GA now |

If the "documentation" row is the one you keep re-reading, that is the signal you are shopping for an ambient tool, not a faster template.

## Where HealthPlix earns its reputation

Give HealthPlix its due. It calls itself India's largest EMR, and the numbers behind that are real: 14,000-plus doctors across 16 specialties, with around 650 clinical templates and prescription writing in 14 languages, per its site as of 2025. The core promise is speed. Open the patient, pick the template, write a legible digital prescription in about 30 seconds, and move on. For a specialist who sees the same conditions all day, a tuned template library is genuinely fast.

That maturity matters. An EMR that thousands of doctors have hammered on for years has fewer rough edges than a new one. If you want a well-worn tool and you are happy driving the prescription yourself, HealthPlix is a strong pick. Nothing here argues it is a bad product.

The question is whether "faster typing" is the ceiling of what you want, or whether you would rather not type at all.

## Where the ambient-AI approach is different

Patient Square does not hand you a better template. It removes the step. You open the app before the consult, tap once, and set the phone or tablet aside. The scribe listens through the visit, in English, Hindi, Hinglish, or a code-mixed regional language, and drafts the note in the background.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. A few things worth knowing for Indian clinic conditions:

- Notes come out in clean clinical English, which is what a referral, an insurance claim, or a medico-legal record needs, even when the consult happened in Marathi or Hinglish.
- Audio is used to generate the note and then discarded. Only the structured output persists. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
- The prescription is a draft. The scribe doesn't screen it for interactions or dosing; you review it, adjust it, and approve it before anything reaches the patient, exactly as you check every script today.

The EHR that stores all of this is part of the Copilot plan, labelled AI Copilot EHR. So you are not bolting a scribe onto a separate record system. It is one product. If that shape fits how you work, book a demo and run it against your own visit type.

## The price question, honestly

HealthPlix published two paid tiers in 2025: Pro at roughly Rs 11,999 a year and Elite at roughly Rs 17,999 a year, plus a free path when patients book through its app. That works out to about Rs 1,000 to Rs 1,500 a month, which is competitive for a specialty EMR.

Patient Square prices the EHR inside the Copilot plan at Rs 2,399 per clinician per month on an annual plan, ex-GST. Add 18% GST and that is about Rs 2,831 a month all-in. What the extra buys you is the ambient scribe: the note, codes, and Rx draft written for you rather than by you. Whether that trade is worth it depends on how many hours you currently lose to charting. If you finish notes at 9pm, the math usually favours the tool that writes them during the visit. The full ladder, including the documentation-only Assist tier at Rs 1,599 per month annual and the Autopilot tier, sits on the [India pricing page](/in/pricing/).

## When HealthPlix is the better choice

Stay with HealthPlix, or choose it, if you want a proven, specialty-tuned EMR with a deep template library, a large installed base, and live ABDM features, and you are comfortable writing the prescription yourself. That describes a lot of high-volume specialists, and for them the ambient layer is a nice-to-have, not the point. HealthPlix has years of refinement behind it and ABDM linking today, which Patient Square does not yet have.

Choose Patient Square if your single biggest drain is documentation and you would rather have the note drafted for you than type it faster. If you are a solo GP or specialist doing 40-plus patients a day and your notes are either half-done or finished after dark, the ambient approach is the more direct fix.

The split is not about which is a better company. It is about whether you want a faster pen or no pen at all.

## How to decide in a week

Skip the feature grid and run the real test:

1. Time your charting for two clinic days. If most of your evening is notes, an ambient scribe targets that directly.
2. Check your ABDM need. If ABHA linking is required now, HealthPlix has it and Patient Square's is roadmap.
3. Trial the note quality on your own visits, not a scripted demo. A demo flatters everything.
4. Confirm both current prices with the vendors, ex-GST, and do the with-GST math once.

The receipts on data handling under the DPDP Act 2023 and the price ladder with no asterisks are on the [pricing page](/in/pricing/). If documentation is the thing that is stealing your time, book a demo and see the note against a real Tuesday clinic before you assume the cheaper tool does the job you actually have.

_Reviewed by the Patient Square clinical team._

---

## Practo Ray Alternatives: An AI-Native EHR for Clinics
https://patientsquare.com/in/blog/practo-ray-alternatives-india/
Published 2026-07-20 · Updated 2026-07-22 · Tags: ehr, practo-ray, clinic-software, alternatives, practice-copilot

Weighing Practo Ray for clinic management? See how Patient Square's ambient-AI EHR and front-office Copilot compare on documentation, lock-in, and price.

For clinics whose biggest drain is documentation, yes. Practo Ray is a broad clinic-management suite: appointments, records, billing, and Practo-network integration. Patient Square is narrower and deeper on the AI side. An ambient scribe drafts the note, ICD-10 codes, and prescription during the visit, and the EHR is bundled in the Copilot plan from Rs 2,399 per month on an annual plan, plus GST.

If you are looking past Practo Ray, it is usually for one of two reasons. Either the clinic suite feels heavier than you need, or you want the documentation done for you, not just stored. Patient Square answers the second one directly: an ambient AI listens to the consult and drafts the note, ICD-10 codes, and prescription, and the EHR that holds it all is bundled in the Copilot plan from Rs 2,399 per clinician per month on an annual plan, ex-GST. Start with the [India pricing](/in/pricing/) and the rest of this page fills in the trade-offs.

Practo Ray and Patient Square are not the same category. One is a broad clinic suite tied to a marketplace. The other is an AI-native clinical tool. Which fits depends on what actually slows your clinic down.

> **Key takeaways**
>
> - Practo Ray is a broad clinic suite: appointments, records, billing, and Practo-network integration.
> - Third-party listings put Practo Ray around Rs 1,000 to Rs 6,000 per doctor per month, as of 2025.
> - Patient Square bundles the EHR in the Copilot plan at Rs 2,399/clinician/month annual, ex-GST, with an ambient scribe that drafts notes during the visit.
> - Reviews as of 2025 note Practo Ray does not include ambient AI documentation. That gap is where Patient Square fits.
> - Practo Ray ties into the Practo marketplace for patient demand. Patient Square is a clinical tool, not a marketplace.

## Practo Ray vs Patient Square at a glance

The quick map. Prices move, so verify before you buy.

| | Practo Ray | Patient Square (Copilot plan) |
|---|---|---|
| Category | All-in-one clinic suite | AI-native EHR + Practice Copilot |
| Documentation | EMR you type into | Ambient AI drafts note, ICD-10, Rx |
| Front office | Appointments, records, billing | Copilot automation (some live, some roadmap) |
| Marketplace | Tied to Practo patient app | None; independent clinical tool |
| Pricing | ~Rs 1,000 to Rs 6,000/doctor/mo (2025) | EHR bundled in Copilot, Rs 2,399/mo annual + GST |
| Ambient AI | Not included (per 2025 reviews) | Core of the product |

If the "documentation" and "ambient AI" rows are why you clicked, you are shopping for a tool Practo Ray was not built to be.

## What Practo Ray does well

Practo Ray is a competent, well-known clinic-management suite. It handles appointments, patient records, prescriptions, and billing in one place, and it plugs into the Practo network and consumer app, which is the real draw. For a clinic that wants both software and a pipeline of patients booking through Practo, that combination is hard to match with a standalone tool.

The suite breadth is a genuine plus if you want one vendor for scheduling, records, and billing. And the marketplace tie-in means Practo Ray is not just software you pay for; it can also send you demand. If new-patient acquisition is high on your list, that changes the calculation in Practo's favour.

What Practo Ray is not, per independent reviews as of 2025, is an ambient documentation tool. The EMR is something you type into. That is fine if charting is not your bottleneck. If it is, keep reading.

## What an AI-native EHR changes

Patient Square starts from documentation and builds outward. You open the app before the consult, tap once, and set it down. The scribe listens through the visit and drafts the note in the background, in English, Hindi, Hinglish, or a code-mixed regional language.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Details that matter for an Indian OPD:

- The note comes out in clinical English regardless of the spoken language, which is what referrals and claims need.
- Audio is discarded after the note drafts. Only structured output persists. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
- The prescription is a draft you review, edit, and sign; it doesn't run an automated interaction check, and it never goes to a pharmacy on its own. The clinical call stays yours.

The record that stores all of this is the AI Copilot EHR, bundled in the Copilot plan. Patient Square calls the wider product a Practice Copilot because the aim is to offload front-office work too, not just documentation. Some of that is live and some is on the roadmap, so ask the team which pieces are ready for your clinic. If the AI-first shape appeals, book a demo and test it on real visits.

## Price and lock-in, weighed together

On price alone, the two overlap. Practo Ray sits around Rs 1,000 to Rs 6,000 per doctor per month depending on size and add-ons, per third-party listings as of 2025. Patient Square's Copilot plan is Rs 2,399 per clinician per month annual, ex-GST, or about Rs 2,831 with 18% GST. So this is not a cheap-versus-expensive decision.

The sharper question is lock-in. Practo Ray ties you into the Practo ecosystem, which is a feature if you want its patient demand and a constraint if you would rather stay independent of any marketplace. Patient Square has no marketplace; it is a clinical tool you run on top of whatever else your clinic uses. Neither is right for everyone. The point is to choose the lock-in you actually want. The full price ladder, including the Assist tier at Rs 1,599 per month annual and the Autopilot tier, is on the [India pricing page](/in/pricing/).

## When Practo Ray is the better choice

Choose Practo Ray if you want an all-in-one suite plus access to the Practo marketplace for new-patient demand, and ambient documentation is not your top priority. If patient acquisition and a single vendor for scheduling, records, and billing matter more than charting time, Practo Ray's breadth and reach win. That is a legitimate priority and Practo is built for it.

Choose Patient Square if documentation is your biggest daily drain and you would rather have the note drafted for you than type it into a suite. For a solo GP or small clinic buried in evening charting, the ambient approach is the more direct fix, and the bundled EHR means you are not stitching a scribe onto a separate record system.

## How to decide in a week

Run the real test rather than the spec sheet:

1. Name your bottleneck. If it is new patients, Practo's marketplace matters. If it is charting, an ambient scribe matters.
2. Decide how you feel about ecosystem lock-in before you sign anything.
3. Trial the note quality on your own consults, not a scripted demo.
4. Confirm current prices with both vendors, ex-GST, and run the with-GST math once.

The data-handling posture under the DPDP Act 2023 and the full price ladder are on the [pricing page](/in/pricing/). If the note is what is stealing your evenings, book a demo and see Patient Square draft one against a real clinic day.

_Reviewed by the Patient Square clinical team._

---

## AI Scribe and HCC Documentation: Getting Risk Adjustment Into the Note
https://patientsquare.com/us/blog/ai-scribe-hcc-risk-adjustment-documentation/
Published 2026-07-19 · Updated 2026-07-22 · Tags: hcc-coding, risk-adjustment, medicare-advantage, clinical-documentation, ai-medical-scribe

For Medicare Advantage practices, HCC capture starts with the note. An ambient AI scribe drafts stated chronic conditions but does not code or submit.

No. It drafts the clinical note from what you say and offers ICD-10 suggestions you confirm. It does not map codes to HCC categories, compute a risk-adjustment factor, or submit anything to a plan or CMS. Risk-adjustment coding stays with your coder and your billing system.

For a practice with a large Medicare Advantage panel, the annual note is where risk adjustment lives or dies. A chronic condition that gets assessed and treated but never makes it into a coded, documented problem for that calendar year does not count toward the patient's risk profile, and the gap shows up later as an unsupported code or a missed one. An ambient AI medical scribe touches exactly one part of this: it drafts the clinical note from what you say during the visit, so the conditions you actually address have a written record. It does not code the HCC, it does not compute a risk score, and it does not send anything anywhere. Understanding where that line sits is the whole point of this piece.

> **Key takeaways**
> - The scribe drafts your spoken assessment into a note; risk-adjustment coding and submission stay with your coder and your billing system.
> - HCC capture depends on you documenting the condition and its detail. A condition you never dictate does not document itself.
> - ICD-10 suggestions are starting points that turn on specificity, so confirm every one against what the note supports.

_Source: Patient Square product specifications, 2026._

## What risk adjustment actually rewards

Medicare Advantage pays plans a monthly amount per member that is adjusted for how sick that member is. The mechanism is the CMS Hierarchical Condition Category model, which groups thousands of ICD-10-CM diagnosis codes into condition categories that carry weight, and rolls those weights into a risk-adjustment factor for the patient (CMS, Risk Adjustment in Medicare Advantage). A patient with well-documented diabetes with complications, heart failure, and chronic kidney disease has a very different risk profile from a patient whose chart shows only "diabetes" with no further detail, even when the underlying medicine is the same.

Two features of the model drive everything downstream. First, it resets every calendar year: a chronic condition documented last year does not carry forward, so it has to be captured again this year to count. Second, CMS has been phasing in an updated version of the model, V28, which changes which conditions map to a category and how they are weighted (CMS, 2024 Rate Announcement). The details of the model are a coding and finance problem, not a bedside one. What reaches the exam room is simpler and more stubborn: the code is only as good as the note behind it.

## The note is the raw material, and it is often thin

Coders cannot code what clinicians do not write. A condition has to be documented as assessed or addressed during a face-to-face encounter, with enough clinical detail to support the specific diagnosis, before it can support a code that feeds an HCC. The industry shorthand for that standard is that a condition should be monitored, evaluated, assessed, or treated in the note, and the diagnosis should be stated clearly enough that a coder does not have to guess.

This is where documentation habits quietly cost a practice. You manage the patient's CKD and their diabetes competently, you adjust a medication, you plan a follow-up, and then the note that comes out says "diabetes, stable" and never mentions the kidney disease you spent five minutes on. The care happened. The record of it did not. When that pattern repeats across a panel, the practice's coded risk drifts below the panel's real clinical burden, and the shortfall is invisible until an audit or a year-end reconciliation surfaces it.

## Where an ambient scribe fits

The scribe listens through the visit and drafts the note from what you say. If you state that the patient's type 2 diabetes now shows diabetic chronic kidney disease and you describe the stage, that linkage and that detail land in the draft because you said them. If you assess the heart failure and note it is compensated on the current regimen, that goes in too. Two minutes after the patient leaves, you have a draft that reflects the assessment you actually delivered rather than the compressed version you would have typed at 9 p.m.

The mechanism matters here because it also bounds the benefit. The scribe records what you say and nothing you do not. It has no prior chart, no problem list it reasons over, and no ability to infer a condition you managed silently. If a chronic condition never enters your spoken assessment, it never enters the draft, and no amount of ambient capture fixes a diagnosis that was addressed but never articulated. The habit the scribe rewards is the same one good risk-adjustment documentation has always rewarded: say the condition, say its detail, say what you did about it.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| Linked conditions | "Type 2 diabetes with diabetic CKD, stage 3b" | The diagnosis and linkage as stated |
| Status of a chronic problem | "Heart failure, compensated on current dose" | The condition with your status assessment |
| What you did about it | "Continued the ACE inhibitor, recheck labs in six weeks" | The management and plan |
| Specificity that drives coding | "COPD with an acute exacerbation today" | The stated manifestation, for you to confirm |

## The boundary, stated plainly

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Read what is not in that sentence for risk adjustment. It does not group codes into HCCs. It does not calculate a RAF score. It does not know which version of the CMS model your plan is under, and it does not submit a diagnosis to any health plan or to CMS. Those are coding, compliance, and billing functions that sit in your coder's hands and your revenue systems, and they stay there.

The ICD-10 outputs are the clearest place to keep this straight. The scribe offers a suggested code from what you said, and for risk adjustment that suggestion is a first draft, not a decision. Risk-adjustment coding turns on specificity that a single spoken sentence rarely resolves on its own, so the CKD stage, the diabetes manifestation, or the exacerbation status all need you or your coder to confirm the exact code the documentation supports. Our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) walks through why the suggestion is deliberately a starting point, and [how notes affect claim denials](../ai-scribe-claim-denials-documentation/) covers the same discipline on the billing side.

## Annual recapture without the year-end scramble

Because the model resets each January, the practical work of risk adjustment is recapturing every active chronic condition during that year's visits. Many practices do this in a compressed annual-wellness sweep, which is exactly when documentation quality tends to suffer under time pressure. If the note drafts itself from your spoken assessment of each active problem, the recapture record accumulates as you work through the patient rather than as a separate typing task afterward. The scribe does not tell you which conditions still need recapture, and it does not track a patient's coded status across the year. It gives you a cleaner draft of the visit you just did, which is a better input to whatever recapture workflow your practice and coder already run.

## Security and ownership

Risk-adjustment work concentrates a lot of diagnostic detail in one place, so how the record is handled matters. Visit audio is processed in memory and discarded the moment the note drafts, so no recording of the encounter exists afterward. Notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256, they belong to your practice, and you can export or delete them at any time. We maintain HIPAA compliant safeguards, offer a signed BAA to every customer, and have a SOC 2 Type II audit underway. If compliance gates the decision, start with the [security page](../../security/) and the detail on [BAAs and consent](../ai-scribe-hipaa-baa-consent/).

## Whether it earns a place

If your practice carries meaningful Medicare Advantage risk and your documentation gaps show up as chronic conditions that get treated but not captured, the trade is worth weighing. The scribe does not close that gap for you. It makes the note reflect what you said, which only helps if you are saying the conditions and their detail out loud in the first place. For a practice already disciplined about spoken assessment, that is a faster path from visit to a coder-ready draft. For a practice whose real problem is silent management, the fix is upstream of any tool.

Pricing starts from $79 per clinician per month on the annual Assist plan, then steps up to Copilot and Autopilot, which add a bundled AI EHR, messaging, and receptionist and follow-up automation. On the scribe-only plan it runs alongside your existing EHR and hands you an export rather than writing back into it, which is the posture that matters for risk-adjustment: nothing the scribe drafts reaches a plan or CMS on its own. Compare options in our [roundup of AI medical scribes](../best-ai-medical-scribes/), see the [primary care scribe overview](../ai-scribe-for-primary-care/) since that is where most risk adjustment happens, and read [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before committing to any vendor. Want to see it on a real annual visit? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Pricing is on the [pricing page](../../pricing/).

---

## PM-JAY Claim Documentation: What a Hospital's Notes Have to Carry
https://patientsquare.com/in/blog/pmjay-claim-documentation-hospitals-india/
Published 2026-07-17 · Tags: pmjay, ayushman-bharat, cashless, claims, hospital, india

See what PM-JAY cashless pre-authorisation and claim notes must contain, common documentation deductions, and where AI drafting may fit.

A PM-JAY cashless case runs on a pre-authorisation and then a claim, and both are assembled from the treating team's clinical record. The diagnosis, the indication for the chosen procedure package, the treatment provided, and the discharge summary all have to be present and consistent. A package selected without a clinical record that clearly supports it is the most common reason a pre-auth is queried or a claim is deducted at audit.

Ayushman Bharat Pradhan Mantri Jan Arogya Yojana pays an empanelled hospital nothing at the counter and everything on the claim. The patient is treated cashless, the hospital raises a pre-authorisation and later a claim, and a State Health Agency and its auditors decide, from the record you submitted, what gets paid and what gets deducted. That makes PM-JAY unusually document-driven for the hospital: the clinical work earns the payment, but the written record is what proves it. This piece is about what that record has to carry, where money leaks out of it, and the narrow place where an AI scribe helps.

> **Key takeaways**
> - A PM-JAY payment is assembled from the clinical record: diagnosis, package indication, treatment, and discharge summary must be present and consistent.
> - Most avoidable deductions at medical audit are documentation gaps, not clinical ones.
> - An AI scribe writes the note; it does not select packages, file pre-auths, or connect to the scheme's systems.

_Source: Patient Square product specifications, 2026._

## How PM-JAY actually pays a hospital

The scheme covers eligible families for up to ₹5 lakh per family per year for secondary and tertiary hospitalisation, delivered cashless at empanelled public and private hospitals (National Health Authority, PM-JAY portal). Treatment is billed against a defined package rather than as loose line items. The Health Benefit Package master, HBP 2022, lists the procedures, their specialties, and their rates, and the hospital selects the package that matches what the patient needs (National Health Authority, HBP 2022).

The flow that follows is where documentation starts to matter. For most packages the hospital raises a pre-authorisation before or shortly after admission, stating the diagnosis and the clinical indication for the package it wants approved. Treatment proceeds, and at discharge the hospital files a claim with the supporting record. A State Health Agency processes and audits that claim. At each of those steps someone who was not in the room reads your record and decides whether it supports what you billed. The clinical decision was yours; the payment turns on whether the paper behind it holds up.

## Where the money actually leaks

Ask any PM-JAY billing desk where claims get reduced and the answer is rarely "the treatment was wrong." It is almost always the record. A pre-authorisation that names a package but does not spell out the clinical indication invites a query. A claim whose diagnosis does not line up with the procedure billed gets flagged. A discharge summary that omits a procedure that was actually done, or that contradicts the pre-auth, gives an auditor a clean reason to deduct. These are documentation failures wearing the costume of clinical ones.

The reason this happens is structural, not careless. A busy IPD generates the clinical facts in real time and the paperwork after the fact, often reconstructed from memory at discharge under time pressure. The gap between what the team did and what the record says is where deductions live. Closing that gap does not require doing anything different clinically. It requires the note to carry, at the moment of care, the same detail the auditor will later look for: the diagnosis, the indication for the package, what was actually done, and a discharge summary that agrees with all of it. Our reads on [how notes affect cashless approvals](/in/blog/ai-scribe-cashless-claim-documentation/) and [whether better notes cut claim denials](/us/blog/ai-scribe-claim-denials-documentation/) draw the same line for private cashless, and it holds just as firmly for a government scheme.

## PM-JAY is not the private cashless you already run

It is worth separating PM-JAY from the private insurance and TPA cashless most hospitals also handle, because the documentation discipline overlaps but the machinery does not. Private cashless runs through insurers and third-party administrators, increasingly over the National Health Claims Exchange, against IRDAI timelines. PM-JAY runs on its own rail: State Health Agencies, the scheme's own transaction systems, its own package master, and its own medical-audit and de-empanelment consequences for records that do not hold up. If you want the private-side picture, our [plain-English TPA and cashless glossary](/in/blog/tpa-full-form-cashless-explained/) and the [NHCX explainer](/in/blog/nhcx-claims-explained-clinics/) cover it. The common thread across both worlds is the one this post keeps returning to: the claim is only as strong as the note it is built from.

## What a claim-ready PM-JAY note has to contain

The specifics vary by package and specialty, but the spine is consistent. A record that survives audit tends to carry all of the following, stated plainly and consistently across the pre-auth and the discharge summary.

| Record element | Why the auditor looks for it |
|---|---|
| Working and final diagnosis | Must support the package billed; a mismatch is a standard deduction |
| Clinical indication for the package | The reason this procedure, for this patient, now |
| Procedure and treatment actually done | Must match what was pre-authorised and claimed |
| Investigations and findings that justify it | The evidence trail behind the indication |
| Discharge summary consistent with the above | The single document auditors read most closely |

None of this is new to a clinician. What is new is how expensive an omission has become under a scheme that pays entirely on the strength of the written record. A finding you noted mentally but never wrote, or a summary assembled at speed that drops a detail, is not a clinical lapse. It is a payment risk.

## Where an AI scribe fits, and where it stops

At the note, and nowhere near the scheme. We will be exact about the boundary, because a government-scheme claim is precisely the kind of thing a health vendor is tempted to overstate.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Read what is absent from that sentence for PM-JAY. It does not select an HBP package. It does not raise a pre-authorisation. It does not connect to the Transaction Management System, to a State Health Agency, or to any TPA. The ICD-10 outputs are suggestions for your coder or billing team to confirm, not a coding engine and not a claim submission. Package selection, pre-auth, and claim filing are your billing team's work on the scheme's own portal, and they stay there.

The benefit is upstream and deliberately modest. A complete, consistent note is better raw material for whoever prepares the pre-auth and the claim, so the diagnosis, the indication, and the discharge summary that reach the auditor are already coherent. For an Indian ward that carries a practical detail: the scribe captures the code-mixed Hindi and English of a real ward round and returns the note in clean clinical English, which is the language the record has to be in. Visit audio is processed in memory and discarded once the note drafts, so no recording sits on a server, which is the cleaner position under the DPDP Act 2023. Data is encrypted in transit and at rest, notes belong to your hospital to export or delete, and a SOC 2 Type II audit is underway. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## The short version

PM-JAY pays on the record, not at the counter, so a hospital's exposure under the scheme is largely a documentation exposure. The claim is built from the diagnosis, the package indication, the treatment done, and a discharge summary that agrees with all three, and the deductions that hurt most are the ones an auditor can trace to a gap in that chain rather than to the medicine. Nothing about that requires new clinical work; it requires the note to carry, at the point of care, what the audit will later ask for.

If PM-JAY deductions cluster on missing indications or inconsistent summaries, compare the queried claim with its clinical record and the applicable package requirements. Check that findings, treatment, and discharge information agree. Documentation tools should be evaluated against those gaps without assuming that a generated note guarantees payment.

---

## AI Medical Scribe for Oncology: Treatment & Follow-up Notes
https://patientsquare.com/us/blog/ai-scribe-for-oncology/
Published 2026-07-16 · Updated 2026-07-22 · Tags: oncology, ai-medical-scribe, treatment-notes, restaging-documentation, clinical-documentation

An ambient AI scribe drafts oncology notes for chemo cycles, staging, and restaging visits from what you say. It never reads scans. You review and sign.

No. It captures what you say about the scan read. If you say the CT shows a partial response with the liver lesion down from 4 to 2 centimeters, that is what the note reflects. The scribe does not read images or interpret studies. The reading stays yours.

Oncology notes are among the densest in medicine: staging, regimen and cycle, performance status, toxicity grading, restaging scan summaries, and the plan that follows from all of it. An ambient AI medical scribe drafts these notes from what you say during the visit, then hands the draft back about two minutes after the patient leaves. One boundary matters more here than anywhere: the scribe captures what you say about a scan read, but it never reads the image or interprets the study. The reading stays yours. You review the draft, confirm the codes as suggestions, and sign.

> **Key takeaways**
> - The scribe drafts oncology treatment and follow-up notes about two minutes after the visit; you review and sign.
> - It captures what you say about a scan; it does not read images or interpret studies. The reading stays yours.
> - Chemo cycle, ECOG status, and toxicity grading come from your dictation, not from any inference.
> - ICD-10 suggestions are starting points only, given how site- and behavior-specific oncology coding is.
> - Audio is discarded the moment the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## How an ambient scribe fits an oncology visit

An oncology visit moves through a lot of ground. You review how the patient tolerated the last cycle, check toxicities, look at the latest labs and any restaging imaging, decide whether to continue, adjust, or hold treatment, and set the next cycle or scan. A follow-up in surveillance is lighter but still records the interval, the exam, and any new symptoms.

The scribe listens through the visit. When you say the patient is on cycle 3 of the regimen and tolerated it with grade 1 nausea and grade 2 fatigue, that goes in the note. When you summarize the restaging CT as a partial response with the liver lesion down from 4 to 2 centimeters, that summary lands in the note as your reading. Two minutes after the patient leaves, you have a draft to review.

Because so much of the oncology story is longitudinal and image-dependent, your narration carries the note. The scribe holds nothing between visits and sees nothing you do not say.

## The scan boundary, stated plainly

This is the line that matters most in oncology. The scribe does not open the CT. It does not read the PET. It does not interpret the MRI. It has no imaging capability at all.

What it does is capture your words about the scan. When you dictate that the restaging scan shows a partial response, or stable disease, or progression with a new lesion, the scribe writes down that you said it. The interpretation is yours, spoken by you, recorded as your reading. If you say the liver lesion measured 4 centimeters on the prior scan and 2 now, both numbers are in the note because you stated them.

Why labor this point? Because a scribe that appeared to interpret imaging would be making a clinical claim it has no business making, and in oncology that claim drives treatment. The design keeps the reading firmly with the physician. The scribe is a stenographer for your assessment, not a radiologist.

The same holds for pathology and molecular results. You state the finding, the scribe records it. It does not read a path report or a genomic panel and tell you what it means.

## What an oncology scribe must capture

The vocabulary is specific and the stakes are high, so accurate capture of your spoken terms matters.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| Staging | "Clinical stage T2 N1 M0, stage IIB" | Stage as you dictated it |
| Regimen and cycle | "Cycle 3 of the current regimen, day 1" | Treatment and cycle |
| Performance status | "ECOG 1, ambulatory, restricted in strenuous activity" | Performance status |
| Toxicity grading | "Grade 2 fatigue, grade 1 neuropathy, no neutropenic fever" | Toxicities with grades |
| Restaging summary | "CT shows partial response, liver lesion 4 to 2 cm" | Your scan read, as stated |
| Tumor board narration | "Discussed at tumor board, consensus to continue current line" | Multidisciplinary discussion |
| Plan | "Continue for two more cycles, restage after cycle 5" | Plan with restaging point |

Toxicity grading matters for both safety and coding, and it is easy to leave vague. If you grade the neuropathy and the fatigue and say so, the note carries the grades. If you say "some fatigue," that is what the note says, which is why stating the grade out loud is worth the two seconds.

## Tumor board and restaging, in the record

Multidisciplinary discussion is part of oncology care and part of the note. When you say the case was reviewed at tumor board and the consensus was to continue the current line, that discussion goes in the note as you described it. The scribe does not attend the board or summarize other clinicians' views. It records your account of the outcome.

Restaging visits are where the scan boundary and the longitudinal problem meet. The scribe has no prior scan on file, so the comparison you want in the note is the comparison you speak. State the prior measurement and the current one and your assessment of the response, and the note reflects all three as your reading.

## ICD-10 for oncology: suggestions to start from

Oncology coding is among the most specific in ICD-10, with site, laterality, and behavior all encoded. The scribe offers suggestions from what you said, but here more than anywhere they are a starting point.

A lung primary might surface a C34 family suggestion; a secondary in the liver, a C78.7 suggestion; a personal history of cancer, a Z85 suggestion. Every one of these needs you to confirm the exact site, side, and whether the code reflects primary, secondary, or history. The scribe cannot resolve those distinctions from a spoken sentence, so it hands you a candidate and you finalize it. Our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) walks through why oncology suggestions in particular need review.

## Supportive medications and the prescription draft

Oncology visits generate supportive prescriptions constantly: antiemetics, growth factors, pain management, prophylaxis. When your plan includes one, the scribe drafts it from what you said, writing out the drug and dose so you don't retype the order.

The scribe does not screen the draft for interactions or dosing. In oncology, where patients are on complex regimens and polypharmacy is the norm, that interaction read is exactly the check you already run on every order, and it stays yours. The draft never goes to a pharmacy and there is no e-prescribing link. You review it against the regimen, adjust what needs adjusting, and act on it in your own prescribing workflow. See our post on [prescription draft safety](../ai-scribe-prescription-draft-safety/) for how the draft works and why the clinician is the safety check.

## Security and ownership in a high-sensitivity specialty

Oncology records are as sensitive as health data gets. Audio is processed in memory and discarded the moment the note drafts, so no recording of the visit exists afterward. Notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256, they belong to your practice, and you can export or delete them at any time.

We maintain HIPAA compliant safeguards, offer a signed BAA to every customer, and have a SOC 2 Type II audit underway. If compliance gates your decision, start with the [security page](../../security/) and our detail on [BAAs and consent](../ai-scribe-hipaa-baa-consent/).

## When it earns a place in oncology

Oncology notes are long and the visits are cognitively heavy. If charting is stealing time you would rather spend with patients or on treatment planning, the trade is worth weighing: narrate your assessment as you already do, and the note drafts for your review, with the scan reading always kept as yours.

Pricing starts from $79 per clinician per month on the annual Assist plan, then steps up to the Copilot and Autopilot tiers, which add a bundled AI EHR, messaging, and receptionist and follow-up automation. On the scribe-only plan it runs alongside your oncology EHR and hands you an export; it does not write back into your system. See our [comparison of AI medical scribes](../best-ai-medical-scribes/), the [cardiology scribe overview](../ai-scribe-for-cardiology/) if you co-manage cardiac toxicities, and [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before committing to any vendor.

Want to see it on a real treatment visit? Book a demo. Pricing is on the [pricing page](../../pricing/).

---

## ABHA Number vs ABHA Address: What's the Difference?
https://patientsquare.com/in/blog/abha-number-vs-abha-address-explained/
Published 2026-07-15 · Tags: abdm, abha, clinic-workflow, health-id, patient-records

An ABHA number is a 14-digit health ID. An ABHA address is a username@abdm login. Here is what each does and how an Indian clinic uses both.

No. The ABHA number is a 14-digit unique health ID for the patient. The ABHA address is a login-style handle that looks like username@abdm and is used to sign in to a Personal Health Record app. One person can have one ABHA number but more than one ABHA address.

Two things called "ABHA" trip up almost every front desk in India. The ABHA number is a 14-digit health ID for the patient. The ABHA address is a login handle that reads like `name@abdm`. They are not the same, and they do different jobs. This post walks through both, in plain language, and shows where each one shows up in an ordinary clinic day.

> **Key takeaways**
> - The ABHA number is a 14-digit unique health ID. Think of it as the patient's permanent identifier under ABDM.
> - The ABHA address is a login-style username (`something@abdm`) used to access a Personal Health Record app.
> - A patient has one ABHA number but can hold more than one ABHA address.
> - At the desk, you usually collect the ABHA number or a scanned QR. The address matters when the patient wants records pushed to a PHR app.
> - AI Medical Scribe by Patient Square has ABDM integration on the roadmap, not shipped yet.

_Source: ABDM portal, abdm.gov.in._

## What an ABHA number actually is

The ABHA number is a 14-digit code. It is issued under the Ayushman Bharat Digital Mission and, once KYC-verified, it belongs to one person for good. You will sometimes see it written in a spaced format like `12-3456-7890-1234`. That spacing is just for readability. The digits are what count.

The point of the number is identity. When a patient walks into a lab, a pharmacy, a district hospital, and your clinic, the ABHA number is the thread that can tie those visits to the same person. A phone number changes. A name gets spelled three ways. The ABHA number is meant to sit under all of that as a stable reference.

For a clinic, the practical use is simple. You capture the number against the patient's file in your software, the same slot where you already keep a phone number or a medical record number. It is identifying data, so treat it that way under DPDP-aligned handling: collect it for a clear purpose, store it with care, and do not pass it around loosely.

## What an ABHA address actually is

The ABHA address looks like an email or a UPI handle. Something like `priya.sharma@abdm` or `9876xxxx@sbx`. It is not a number. It is a self-chosen username tied to a Personal Health Record (PHR) app.

The part people miss is this. The address is a login, not an ID. A patient uses it to sign in to a PHR app, view their linked records, and grant or revoke consent for who can see what. The same patient can create several addresses if they want, and pick which one to use with which app.

So the number answers "who is this person?" The address answers "where does this person want their records to land, and under whose login?" One is fixed and about identity. The other is chosen and about access.

## How the two fit together

Think of the ABHA number as your passport number and the ABHA address as your email login. The passport number identifies you no matter which airline you fly. The email login is how you actually read your messages, and you might have more than one inbox.

A patient can:

- Hold exactly one ABHA number after verification.
- Create one or more ABHA addresses linked to that number.
- Use an address to log in to a PHR app and manage consent.
- Share the number at a clinic desk for identification, with consent.

The linkage runs one way in spirit: addresses hang off the number. If a patient loses track of an address, the underlying number is still theirs.

## Where each one shows up in a clinic day

Most front desks never touch the ABHA address at all. What they handle is the number or a QR scan. Here is the rough split.

| Situation | You need the ABHA number | You need the ABHA address |
|---|---|---|
| Registering a walk-in patient | Yes, or a QR scan | No |
| Matching a returning patient to the right file | Yes | No |
| Patient wants records sent to their own PHR app | Number identifies them | Yes, for their app login |
| Patient managing consent themselves | Not directly | Yes |
| Clinic-side record-keeping in your software | Yes | Rarely |

The pattern: your side of the counter mostly cares about the number for identity. The address lives on the patient's side, inside their PHR app, where they log in and decide who gets to see their history.

## What this means for record-keeping

If you run clinic or hospital software, the ABHA number is the field to get right. Capture it accurately, tie it to the patient record, and protect it. Under the DPDP Act 2023, this kind of personal data needs a lawful purpose, patient consent, and sensible security around storage and sharing. Our fuller notes on that live in the [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) and the [DPDP explainer for doctors](../dpdp-act-explained-doctors/).

Getting the number in cleanly also helps later, if and when you link records under ABDM. Clinics that already run an ABHA-linking step at reception have a smoother path here; there is a walkthrough in the [ABHA linking clinic workflow](../abha-linking-clinic-workflow/) post.

## Where a scribe fits, and where it does not

A quick, honest boundary. AI Medical Scribe by Patient Square listens during the consult and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the visit. You review and sign. The legal record stays yours.

What it does not do: it does not create ABHA numbers, it does not manage ABHA addresses, and it does not link your notes to ABDM. That integration is on the roadmap, not shipped yet. So the scribe helps you produce a cleaner clinical note faster; the ABHA identity work still happens through your clinic software and the ABDM flow. If you want to see how the note drafting works on its own, there is a [scribe overview for Indian doctors](../scribe-for-doctors-india/).

## Common mix-ups to avoid

A few that come up again and again:

- Treating the address as an ID. It is a login, not an identifier. Do not use it to match patient files.
- Assuming one address per patient. A patient can hold several. Do not panic if the one they gave last time differs.
- Forgetting the number is sensitive data. It identifies a person's health footprint. Store and share it under consent.
- Expecting your software to "be ABHA" automatically. ABHA creation and linking is a specific ABDM flow your software has to support. Ask your vendor plainly whether they do it.

That last point deserves its own conversation with whoever supplies your software. If you are weighing options, our rundown of [clinic management software in India](../best-clinic-management-software-india/) and the [EMR software guide](../emr-software-india-guide/) both touch on what ABDM support looks like in practice.

## A simple way to remember it

Number identifies. Address logs in. The 14-digit number is the patient's health ID under ABDM. The `name@abdm` address is how they sign in to a PHR app and control consent. Keep those two straight and most of the confusion at the desk goes away.

Want to see how a clean, signed clinical note comes together in about two minutes, with no IT project on your side? <a href="/in/how-it-works/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch it run on a real consult. You can also read how we handle data on the [security page](../../security/) or check the [pricing page](../../pricing/) for India plans.

---

## AI Medical Scribe for Ayurveda & AYUSH Clinics in India
https://patientsquare.com/in/blog/ai-scribe-for-ayurveda-clinics-india/
Published 2026-07-15 · Updated 2026-07-22 · Tags: ayurveda, ayush, ai-medical-scribe, clinical-documentation, india

How an ambient AI scribe drafts structured OPD notes for Ayurveda and AYUSH clinics in India, captures prakriti assessment, and supports NMC and NCISM record-keeping.

It transcribes what the vaidya says. If you dictate terms like vata, pitta, kapha, ama, or agni during the consultation, those words land in the draft note. The scribe does not translate or reinterpret classical concepts; it captures your own phrasing so you can review and correct it.

An Ayurveda OPD runs on the consultation, not the keyboard. A vaidya spends twenty minutes reading prakriti, checking nadi, asking about digestion and sleep, and by the time the patient leaves there is a page of notes to write from memory. An ambient AI scribe changes that order. It listens while you consult, then hands back a structured draft note about two minutes after the visit, so the writing happens while the details are fresh instead of at the end of a long clinic day. You read the draft, correct it, and sign. That is the whole idea.

> **Key takeaways**
> - The scribe captures what the vaidya says during the consultation and returns a structured OPD draft; it does not diagnose or reinterpret classical concepts.
> - Dictated Ayurvedic terms (vata, pitta, kapha, ama, agni, prakriti, vikriti) land in the note as spoken, ready for your review.
> - Prescription output is a draft only. It never reaches a pharmacy, and the vaidya stays the safety check, reviewing and signing every draft.
> - A signed, timestamped note per visit supports NMC and NCISM record-keeping expectations.
> - ABDM integration is on the roadmap for AI Medical Scribe by Patient Square, not shipped. Your notes stay yours.

_Source: Product behaviour of AI Medical Scribe by Patient Square._

## How an ambient scribe fits an Ayurveda consultation

Picture a typical morning OPD. The patient describes acidity, irregular bowel movements, and disturbed sleep for three weeks. You ask about diet, work stress, and water intake. You note the prakriti as vata-pitta, mark aggravated pitta, and settle on a plan involving diet correction and a couple of classical formulations. Under the old flow, you would remember all of that and type it up between patients or after the last one leaves.

With an ambient scribe running, the spoken consultation becomes the source of the note. When you say "prakriti is vata-pitta, current vikriti shows raised pitta, agni is manda," those words go into the draft in a structured format. The scribe is transcribing and organising, not judging. If you misspeak or change your mind mid-consultation, you fix it in the draft. Nothing is signed until you sign it.

This matters for a clinic with high patient throughput. When you see thirty or forty patients in a session, the ten minutes saved per note adds up to real time back in your day, or to notes that actually get written instead of half-remembered later.

## What an Ayurveda scribe must capture

A good OPD note for an AYUSH clinic is not a generic SOAP template. It has its own anatomy. The scribe should be able to hold the following without forcing you into a rigid mould:

| Element | What the vaidya narrates | What lands in the draft |
|---|---|---|
| Prakriti and vikriti | "Prakriti vata-pitta, vikriti raised pitta" | Constitution and current imbalance, as spoken |
| Presenting complaint | Duration, severity, aggravating factors | Structured complaint with timeline |
| Ashtavidha and dashavidha pareeksha | Nadi, mala, mutra, jihva, and the rest | Examination findings you dictated |
| Agni and koshtha | "Agni manda, koshtha krura" | Digestive and bowel assessment |
| Chikitsa plan | Diet, lifestyle, formulations, procedures | A plan section you review |
| Follow-up | Review date, red flags to watch | Clear next-step line |

The point is that the scribe records your words. It does not know the shastras better than you, and it does not pretend to. Classical terminology handling means it keeps the term you said intact rather than "correcting" pitta to something else. When it mishears a Sanskrit term, you catch it on review, the same way you would catch a typo.

## Classical terminology, handled honestly

Here is the honest limit. Speech recognition on dense classical vocabulary is not flawless, and any vendor claiming otherwise is overselling. A scribe trained mostly on English clinical speech will stumble on rapid Sanskrit compound terms. So the workflow assumes review, not blind trust.

What helps: speaking the term clearly, keeping a consistent vocabulary in your dictation, and reviewing the draft before signing. Over time, as you correct the same terms, the note quality you accept improves because you have learned how to dictate for the tool. If your clinic runs consultations in Hindi or a mix of Hindi and English, an ambient scribe that supports Indian languages is worth checking against your actual speech pattern. You can read more on that in our note on [Hindi and Indian-language scribing](../ai-scribe-hindi-indian-languages/).

The record you sign is the record that counts. The draft is a starting point that saves typing, not a source of clinical truth you are meant to accept unread.

## Panchakarma and procedure records

Panchakarma visits have a documentation rhythm of their own: purvakarma, the main procedure, and paschatkarma, spread across several days. Each day has an observation and a plan.

An ambient scribe drafts the note portion of each visit from what you say. On a vamana or virechana day, you narrate the procedure done, the patient's response, any adverse reaction, and the plan for the next day. The scribe structures that into a note. It does not decide the protocol, calculate the ghee dose, or run the schedule. Those are yours. What it removes is the after-the-fact writing, which is exactly where panchakarma notes tend to get thin because staff are busy and the day is long.

For a clinic that runs panchakarma alongside OPD, consistent day-wise notes also help if a patient's course is ever reviewed, whether internally or by an insurer for a cashless claim.

## Prescription drafts and who checks them

Ayurvedic prescribing carries its own considerations. Some classical formulations contain heavy metals in bhasma form, some patients are pregnant, and many walk in already on allopathic medicines for diabetes or blood pressure.

The scribe produces a prescription draft from your consultation. It is a draft. It never sends to a pharmacy, and it never dispenses. What it does not do is check the medicines for you: there is no interaction screen, no dosing check, no pregnancy flag. It writes down what you said, and the review is yours. You read the draft, weigh those exact considerations, adjust the formulation, and sign.

That is by design, not a gap. You know the patient, the formulation, and the context; a rule engine does not. The safety on an Ayurvedic script belongs with the vaidya, the same as it does with a handwritten one.

## Where NMC and NCISM record-keeping fit

Record-keeping in Indian medicine is not optional. NMC's professional-conduct expectations and NCISM's role in the Indian systems of medicine both point to the same practical need: a legible, dated, per-visit record that shows what happened and what was advised. If a complaint or a medico-legal question ever arises, the record is your first line of defence.

A structured, timestamped note per patient per visit is precisely what an ambient scribe helps you produce consistently, even at the end of a forty-patient day. For a fuller treatment of record-keeping duties, see our guide on [NMC record-keeping and AI scribes](../nmc-record-keeping-ai-scribe/) and the piece on [medico-legal documentation in India](../ai-scribe-medico-legal-documentation-india/).

Two things stay firmly with you. The clinical content of the record is yours to verify. And retention, storage, and consent are your clinic's responsibility. AI Medical Scribe by Patient Square encrypts notes in transit and at rest, keeps them exportable and deletable at your instruction, and processes the consultation audio in memory only, discarding it the moment the note drafts. No recording is kept. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## What the scribe does not do

Worth stating plainly, because clarity here builds trust. The scribe does not read tongue photographs, pulse-diagnosis devices, or lab reports. It does not diagnose. It does not decide your chikitsa. It does not link records to ABHA today, because ABDM integration is on the roadmap for AI Medical Scribe by Patient Square and not shipped. And it does not claim to know classical medicine; it captures the classical medicine you speak.

For a solo vaidya running a clinic without support staff, that limited, honest scope is often the appeal. You get the note-writing off your plate without handing over the part that matters. Our note for [solo doctors in India](../ai-scribe-for-solo-doctors-india/) goes deeper on that setup, and the broader [scribe-for-doctors overview](../scribe-for-doctors-india/) covers the general workflow.

## Try it in your own OPD

The real test is your own clinic voice, your own terminology, your own patient mix. You can <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run a few live consultations to see how the draft reads against how you actually speak. Check the [pricing page](../../pricing/) for India plans, and the [security page](../../security/) for how notes are encrypted, stored, and deleted. See it work on your terms before it touches a single patient record.

---

## AI Medical Scribe for Chiropractic: SOAP & Adjustment Notes
https://patientsquare.com/us/blog/ai-scribe-for-chiropractic/
Published 2026-07-15 · Updated 2026-07-22 · Tags: chiropractic, ai-medical-scribe, soap-notes, medicare-documentation, clinical-documentation

An ambient AI scribe drafts chiropractic SOAP notes, adjustment levels, and Medicare medical-necessity language while you treat. You review and sign.

It captures what you say. If you speak the segments out loud, for example an adjustment at L4-L5 and T7, the note reflects those levels. The scribe does not watch your hands or infer levels you never verbalized, so segment call-outs during the visit matter.

Chiropractic documentation eats time you would rather spend adjusting. An ambient AI medical scribe listens during the visit and hands back a structured SOAP note about two minutes after the patient leaves, including the segments you called out, your orthopedic and neuro findings, and a draft of the medical-necessity language Medicare asks for. You read it, correct anything that is off, and sign. The scribe writes down what you say; the clinical judgment and the signature stay with you.

> **Key takeaways**
> - The scribe drafts a chiropractic SOAP note plus ICD-10 suggestions roughly two minutes after the visit; you review and sign.
> - It records the adjustment levels and manipulation you speak out loud (for example L4-L5, T7), not what it guesses.
> - Medicare active-treatment and AT-modifier decisions stay with you. The scribe drafts language, you own the call.
> - It runs alongside ChiroTouch, Jane, or any EHR. Copy, paste, or export. No integration.
> - Visit audio is discarded the instant the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## How an ambient scribe fits a chiropractic visit

A typical adjustment visit is fast. The patient describes where it hurts, you run a quick exam, you adjust, you set the plan for the next few weeks. The note is supposed to capture all of that, but by the third patient of the morning the details blur, and the after-hours catch-up on charting is where a lot of chiropractors lose their evenings.

The scribe sits in the background while you work. It hears the patient say the low back pain is worse after sitting. It hears you note the restricted segment, the muscle guarding, the tenderness on palpation. When you say you are adjusting L4-L5 and doing a thoracic manipulation at T7, that goes in the objective section. Two minutes after the patient leaves, you have a draft.

What it does not do is watch your hands or read the patient's spine. If you adjust a level silently, the scribe has no way to know. So the habit that makes this work is simple: say the levels out loud as you treat. You probably already narrate to the patient. Now that narration builds the note.

The AMA's research on documentation burden has been blunt about how much time clinicians spend charting outside the visit itself. Chiropractic is not immune. Cutting that after-hours drag is the whole point.

## What a chiropractic scribe must capture

Generic scribing tools miss the vocabulary that makes a chiropractic note defensible. A good chiropractic note lives on specific terms, and the scribe has to get them down accurately when you speak them.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| Subluxation / segmental dysfunction | "Restriction and segmental dysfunction at L4-L5" | Objective finding tied to the level |
| Adjustment / manipulation levels | "Diversified adjustment L4-L5, thoracic at T7" | Treatment rendered, per region |
| Range of motion | "Lumbar flexion limited to 40 degrees, painful" | ROM findings with the limitation |
| Orthopedic tests | "Straight leg raise positive on the right at 45 degrees" | SLR result and side |
| Provocative tests | "Kemp's positive on the left, reproduces low back pain" | Kemp's finding |
| Neuro screen | "Deep tendon reflexes 2+ and symmetric, no sensory deficit" | Neuro exam line |
| Treatment plan phase | "Acute phase, three times a week for two weeks, then reassess" | Plan with frequency and reassessment point |

The plan section is where a lot of Medicare denials start. If the note does not show a functional deficit, a treatment goal, and a measurable expected outcome, the active-treatment argument falls apart. The scribe drafts that structure from what you dictate. You still decide what the goal is and whether the patient is in active care or maintenance.

## When the Medicare note burden is the real problem

Cash-pay chiropractic and insurance-billed chiropractic are two different documentation worlds. A wellness patient paying out of pocket needs a clean record. A Medicare patient needs a record that survives an audit.

Medicare only covers manual manipulation of the spine to correct a subluxation, and only when it is active treatment expected to improve function, not maintenance. That means every covered visit needs the subluxation documented, the functional deficit named, and the treatment plan showing progress toward a goal. The AT modifier signals active treatment. Get the note wrong and the whole claim is exposed.

The scribe helps by getting your spoken medical-necessity reasoning into the note reliably. When you say the patient's low back pain limits their ability to sit for more than 20 minutes, and that you expect a 50 percent improvement over the next three weeks, that language lands in the plan. You review whether it is accurate and whether the AT modifier belongs. It never applies the modifier for you, and it never decides that a visit is medically necessary. Those are your calls, and the signature confirms them.

If your practice mixes cash and insurance, the scribe drafts both kinds of note the same way. The difference is what you choose to include and how you bill it.

## ICD-10 and CPT: suggestions, not decisions

After the visit, the scribe offers ICD-10 suggestions pulled from what you said. For a low back subluxation you might see M99.01 for segmental and somatic dysfunction of the lumbar region, or M54.5 for low back pain. These are suggestions to speed up your coding, not a final answer. You confirm or change them.

CPT is a separate matter. The chiropractic manipulative treatment codes run by the number of spinal regions treated:

| CPT | Regions treated |
|---|---|
| 98940 | 1 to 2 regions |
| 98941 | 3 to 4 regions |
| 98942 | 5 regions |
| 98943 | Extraspinal, one or more regions |

The scribe does not pick the CMT code. It cannot count regions for billing purposes on your behalf, because whether the cervical and thoracic spine both got treated is a decision you own. What it can do is make sure the note reflects the regions you actually said you adjusted, so your CPT choice matches your documentation. That alignment is what keeps a claim clean.

For more on how the ICD-10 suggestions work across specialties, see our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/).

## The prescription draft, for the chiropractors who need it

Most chiropractic care is hands-on, but some practices co-manage with medications or recommend over-the-counter regimens, and some DCs work in integrated clinics alongside prescribers. When a prescription is part of the visit, the scribe drafts one. That draft reflects what was discussed; the scribe does not screen it for interactions or dosing. The prescriber reads the draft, adjusts it, and signs, and that review is the safety check.

The draft is a draft. It never goes to a pharmacy. The scribe has no e-prescribing connection and does not transmit anything. If you or a co-managing prescriber decide to act on it, that happens in your own prescribing workflow, where the safety review belongs. We wrote more about reviewing an AI-drafted prescription in our piece on [prescription draft safety](../ai-scribe-prescription-draft-safety/).

## How it compares to typing your own note

The realistic comparison is not scribe versus perfect note. It is scribe versus the note you actually write at 7pm when you are tired and the details have gone fuzzy.

| Approach | Segment accuracy | Time after visit | Medicare language |
|---|---|---|---|
| Typing from memory later | Fades with each patient | 10 to 20 min per note | Easy to leave thin |
| Dictating to a transcription service | Depends on turnaround | Hours to next day | You still assemble it |
| Ambient AI scribe | Captures what you spoke in real time | About 2 min, drafted | Drafted from your dictation |

The scribe is not a replacement for your judgment. It is a way to keep the note honest to what happened in the room, while you were still in the room.

## Security and who owns the note

Chiropractic records are protected health information, and the handling has to match. Audio is processed in memory and discarded the moment the note drafts, so there is no recording sitting on a server. The finished notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256. They belong to your practice, and you can export or delete them whenever you want.

We maintain HIPAA compliant safeguards and offer a signed BAA to every customer. Our SOC 2 Type II audit is underway. If compliance is a gating question for you, start with our [security page](../../security/) and the details on [BAAs and consent](../ai-scribe-hipaa-baa-consent/).

## When it is worth trying

If your charting is quick and your evenings are free, you may not need this. If you are losing time to after-hours notes, or your Medicare documentation feels thin, or you just want the adjustment levels you call out to land in the record without you retyping them, it is worth a look.

The price is from $79 per clinician per month on the annual Assist plan. Same scribe, same review-and-sign workflow, whether you run one office or several. Move up to Copilot ($119/mo annual) for a bundled AI EHR and messaging, or Autopilot ($199/mo annual) for an AI receptionist and follow-ups. You can see how it stacks up against other tools in our [roundup of AI medical scribes](../best-ai-medical-scribes/), and our guide on [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) walks through the questions worth asking any vendor.

Ready to see it on a real adjustment visit? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we will run it against your workflow. Pricing details live on the [pricing page](../../pricing/).

---

## AI Medical Scribe for Endocrinology: Diabetes & Thyroid Notes
https://patientsquare.com/us/blog/ai-scribe-for-endocrinology/
Published 2026-07-15 · Updated 2026-07-22 · Tags: endocrinology, ai-medical-scribe, diabetes-notes, thyroid-documentation, clinical-documentation

An ambient AI scribe drafts endocrinology notes for diabetes and thyroid follow-ups from what you say about A1c trends, titration, and labs. You sign.

No. The scribe has no memory of prior visits and no view into your EHR history. If you want the A1c trend in the note, you say it out loud, for example that the A1c dropped from 8.4 to 7.6. Then the scribe captures the trend you narrated.

Endocrinology runs on trends. An A1c means little as a single number and everything as a trajectory, and the same goes for a thyroid panel followed across months of titration. An ambient AI medical scribe drafts your diabetes and thyroid follow-up notes from what you say during the visit, then hands them back about two minutes after the patient leaves. One thing to know up front: the scribe has no memory of the last visit, so any trend you want in the note is a trend you speak out loud. You review the draft, fix anything off, and sign.

> **Key takeaways**
> - The scribe drafts endocrine follow-up notes plus ICD-10 suggestions about two minutes after the visit; you review and sign.
> - It has no memory of prior visits, so A1c trends, TSH history, and dose changes over time must be spoken during the visit.
> - It captures insulin titration and levothyroxine adjustments from your dictation. It does not interpret lab values.
> - It runs alongside Epic, athenahealth, and any EHR. Copy or export. No integration.
> - Audio is discarded the moment the note drafts. Nothing is recorded.

_Source: Patient Square product specifications, 2026._

## How an ambient scribe fits an endocrine follow-up

A diabetes follow-up is mostly conversation and adjustment. You talk through the last few months of glucose logs, the fasting numbers, the hypoglycemic episodes if any. You look at the A1c. You change a dose. You order labs and set the next visit. Thyroid follow-ups run the same shape: symptoms, the panel, a titration, a recheck interval.

The scribe listens through all of it. When you say the A1c came down from 8.4 to 7.6 and the fasting sugars are running in the 130s, that goes in the note. When you say you are bumping the basal insulin from 20 to 24 units, that lands in the plan. Two minutes after the patient walks out, you have a draft that reflects the visit.

Because the scribe carries nothing between visits, the note is only as complete as your dictation. That is a feature more than a limitation. It means nothing gets pulled in from an old visit and asserted as current. If the A1c trend matters, you say it, and it is right because you said it.

## The no-memory design, and why it changes how you narrate

This is the single most important thing to understand about scribing an endocrinology visit. The scribe does not know your patient. It did not see last quarter's labs. It has no line into your EHR's flowsheets.

For most specialties that barely matters. In endocrinology it changes your habits, because so much of the clinical story is longitudinal. The A1c at 7.6 is only meaningful next to the 8.4 three months ago. The suppressed TSH matters because the last one was normal and you just raised the dose. If you want that arc in the note, narrate it.

In practice this looks like a slightly fuller spoken summary during the visit. You are probably already saying most of it to the patient anyway. "Your A1c is down from 8.4 to 7.6, good progress, but we are not at goal yet, so I want to add a bit more basal insulin." Say that and the trend, the interpretation, and the plan are all in the draft. Skip it and the scribe writes only the single number you mentioned.

Some clinicians find this discipline actually improves their notes, because it forces the reasoning into the record instead of leaving it in their head.

## What an endocrinology scribe must capture

The vocabulary of an endocrine note is specific, and the scribe has to land it when you speak it.

| Note element | What you say out loud | What the scribe drafts |
|---|---|---|
| A1c trend | "A1c down from 8.4 to 7.6 over three months" | The trend as narrated |
| Glucose pattern | "Fasting sugars in the 130s, occasional lows overnight" | Home monitoring summary |
| Insulin titration | "Raising basal glargine from 20 to 24 units" | Dose change in the plan |
| Thyroid panel | "TSH suppressed at 0.1, free T4 upper normal" | Lab values as stated |
| Levothyroxine adjustment | "Dropping levothyroxine from 125 to 100 micrograms" | Med change in the plan |
| Diabetic foot exam | "Monofilament intact bilaterally, no ulcers, pulses present" | Foot exam findings |
| Retinopathy screening | "Referring to ophthalmology for dilated eye exam, overdue" | Referral in the plan |
| Follow-up interval | "Recheck A1c and TSH in three months" | Labs ordered and interval |

The foot exam and the retinopathy referral matter because they are easy to skip and easy for an auditor to notice missing. If you do the monofilament check and say so, it is in the note. If you decide the patient is due for a dilated eye exam and say you are referring, the referral is drafted.

## Labs are captured, not interpreted

Worth being precise here. The scribe does not read the thyroid panel and tell you what it means. It writes down what you say about it. If you say the TSH is suppressed and that means the patient is slightly over-replaced, that reasoning is in the note because you spoke it. The scribe never decides on its own that a value is high, low, or clinically significant.

The same holds for the A1c. The scribe does not fetch the number or grade it. You state it, you interpret it, the scribe records both. The interpretation stays yours, which is exactly where clinical responsibility belongs.

This matters most when a lab result would change management. The decision to raise or lower a dose based on a value is a medical judgment. The scribe documents that you made it. It does not make it for you.

## ICD-10 suggestions for the endocrine visit

After the visit the scribe offers ICD-10 suggestions from what you said. Common ones in this specialty:

| Condition | ICD-10 suggestion |
|---|---|
| Type 2 diabetes without complications | E11.9 |
| Hypothyroidism, unspecified | E03.9 |
| Type 2 diabetes with diabetic polyneuropathy | E11.42 |
| Hyperthyroidism, unspecified | E05.90 |

These are suggestions to speed your coding, not a final answer. You confirm the specificity, because a diabetes code with the right complication captured is what supports the visit level. Our explainer on [how ICD-10 suggestions are generated](../ai-scribe-icd-10-suggestions-explained/) goes into the mechanics.

## Titration and the prescription draft

When your plan includes a medication change, the scribe drafts a prescription to match. If you raise the basal insulin or drop the levothyroxine, that draft reflects what you said. It is a draft only: the scribe does not screen it for interactions or dosing, so the safety review stays with you.

The draft never leaves the app. It is not e-prescribing, and it does not transmit to a pharmacy. You act on it in your own prescribing workflow. For endocrine patients with renal impairment, where metformin dosing and insulin sensitivity both shift, the renal call is exactly the kind of judgement you make when you read the draft and sign, not something to hand to a rule engine. We describe reviewing an AI-drafted prescription in our post on [prescription draft safety](../ai-scribe-prescription-draft-safety/).

## When it fits your practice

If you run high-volume diabetes and thyroid clinics and your evenings disappear into charting, the trade is straightforward: narrate the trends you already discuss with the patient, and the note drafts itself for your review. If your visits are lighter or your notes are already fast, the gain is smaller.

Pricing starts from $79 per clinician per month on the annual Assist plan, and steps up to the Copilot and Autopilot tiers as you add a bundled AI EHR, messaging, and receptionist and follow-up automation. On Assist the scribe works alongside whatever EHR you already run, so there is no IT project and no go-live. See our [comparison of AI medical scribes](../best-ai-medical-scribes/) and our [primary care scribe overview](../ai-scribe-for-primary-care/) if you co-manage with primary care, and read [how to evaluate an AI scribe](../how-to-evaluate-ai-medical-scribe/) before you commit to anyone.

Want to watch it draft a real diabetes follow-up? <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>. Pricing is on the [pricing page](../../pricing/), and the compliance details are on the [security page](../../security/).

---

## Abridge vs Nuance DAX: Two Enterprise Scribes Compared
https://patientsquare.com/us/blog/abridge-vs-nuance-dax/
Published 2026-07-14 · Tags: ai-scribe, comparison, abridge, nuance-dax

Abridge and Nuance DAX (now Dragon Copilot) serve health systems through enterprise sales. Compare their fit with a published-price option for independent practices.

Both are enterprise ambient scribes built for health systems, deployed through sales and integration projects, priced by contract. Abridge is the fast-growing independent platform, named #1 Best in KLAS 2026 for Ambient AI in the revenue-cycle category. Nuance DAX, now Microsoft Dragon Copilot, has the deepest Microsoft and EHR integration and the longest track record. Both require a sales conversation; neither is self-serve.

Abridge and Nuance DAX are the two heavyweights of enterprise ambient scribing. Both are excellent, both are built for health systems, both are demo-priced, and both make an independent practice do a sales dance to learn a number. If you run a large system, this is a real evaluation and you should run it. If you're a solo doctor or a small group, the honest truth is that neither is built for you, and a self-serve scribe with published pricing fits far better. Patient Square publishes $119 a month for a plan that bundles the scribe and an AI EHR, and you can review the [pricing page](/us/pricing/) and try a finished note without entering anyone's procurement cycle.

Here's how the two enterprise tools compare, then where the self-serve option fits the buyer they both ignore.

> **Key takeaways**
>
> - Abridge and Nuance DAX (now Microsoft Dragon Copilot) are both enterprise, demo-priced, health-system-first. Neither is self-serve.
> - Abridge was named #1 Best in KLAS 2026 for Ambient AI in the revenue-cycle category. DAX has the deepest Microsoft and EHR integration.
> - Pricing is quote-based. Estimates: Abridge ~$200–$800/provider/mo; Dragon Copilot list ~$1,512/user/mo unlimited or ~$604.80 Flex base, plus setup.
> - Neither ships an EHR; both integrate into your existing one.
> - Independents usually can't buy either directly. A self-serve scribe with a bundled EHR at $119/mo annual fits that buyer instead.

| | Abridge | Nuance DAX / Dragon Copilot | Patient Square |
|---|---|---|---|
| Buyer | Health systems | Health systems | Independents, small groups |
| Published price | No (quote) | List on MS marketplace | Yes ($79/$119/$199) |
| Est. / list monthly | ~$200–$800 (estimate) | ~$604–$1,512 (list) | $79–$199 |
| Self-serve signup | No | No | Yes |
| Bundled EHR | No (integrates) | No (integrates) | Yes (Copilot, $119/mo annual) |
| Free trial | Demo required | Demo required | 7-day |

Abridge figures are third-party estimates (Abridge publishes no price). DAX figures are Microsoft marketplace list prices, July 2026. Patient Square figures are published list pricing.

## What separates Abridge from Nuance DAX

Both are enterprise-grade, so the differences are in emphasis, not category. Abridge is the fast-growing independent platform: deployed across hundreds of health systems, with features that reach into revenue-cycle and coding work, and named #1 Best in KLAS 2026 for Ambient AI in the revenue-cycle category. It's the momentum player, backed by large funding rounds and a clear enterprise focus.

Nuance DAX, now folded into Microsoft as Dragon Copilot, brings the longest track record and the deepest integration into the Microsoft and EHR stack. If your system already runs on Microsoft and a major EHR, DAX's plumbing is hard to match, and Microsoft's scale sits behind it.

The honest read: both are strong, and at the health-system tier the choice comes down to your existing stack, your EHR, and which vendor's integration and support model fits your organization. This isn't a case where one is clearly better; it's two serious platforms for the same enterprise buyer. If that's not you, review the [pricing page](/us/pricing/) to see what the self-serve route costs.

## Abridge vs Nuance DAX on price

Neither publishes a clean number, which is normal for enterprise software and also tells you what buying will feel like. Abridge publishes no per-provider price at all; third-party comparison sites estimate roughly $200 to $800 per provider a month depending on deal size and features. Treat that as a wide, directional range, not an Abridge quote.

Dragon Copilot is slightly more visible because Microsoft lists it on its marketplace. As of mid-2026 that listing shows roughly $1,512 per user a month for unlimited ambient use, or about $604.80 for a Flex base license with pay-as-you-go ambient on top, per Microsoft's marketplace page. Real deals vary widely by size, and setup fees and multi-month deployment sit on top of either.

The pattern is the same for both: you don't learn your real price without a conversation, and there's a rollout project attached. Patient Square works the other way, published on the [pricing page](/us/pricing/) in US dollars: $79 Assist, $119 Copilot with the bundled AI EHR, $199 Autopilot, per clinician on annual billing, no setup fees, no sales cycle to learn the number. Our [Nuance DAX / Dragon Copilot alternatives](/us/blog/nuance-dax-dragon-copilot-alternatives/) page goes deeper on that specific comparison. For a broader look at what every scribe category actually costs side by side, [AI medical scribe cost comparison](/us/blog/ai-medical-scribe-cost-comparison/) puts both enterprise and self-serve tiers in one table.

## Do Abridge or Nuance DAX include an EHR? No, they integrate into yours

This is where the buyer split gets concrete. Neither Abridge nor DAX sells a record system. Both integrate deeply into the EHR you already run, and that integration is a genuine part of their enterprise value. Deployed across a system, the scribe writing straight into Epic or your chart of record is exactly the point.

But that model assumes you have the EHR, the integration team, and the deployment budget. An independent practice usually has none of those, and doesn't need the depth. For that buyer, a scribe that assumes an integration project is solving a problem they don't have while charging for one.

Patient Square takes the independent's route. It's an AI clinical platform: Practice Copilot brings the whole practice under one AI copilot, starting with an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit. At the Copilot tier ($119/mo annual) that scribe ships with a bundled AI Copilot EHR, so a small practice gets the note and the chart in one subscription, no integration project required. If that's your shape, check the [pricing page](/us/pricing/) and test it in a trial.

One scope note: our ICD-10 is suggestions, not a certified coding engine, and our eRx is a draft you review and sign, not pharmacy transmission. The enterprise revenue-cycle depth Abridge is known for is a different tier of feature; if that's central to your buy, you're likely an enterprise buyer, and both of these belong on your list.

## When Abridge or Nuance DAX is the better choice

Choose Abridge or DAX if you're a large health system that needs the scribe embedded across hundreds of clinicians, wired into your EHR and revenue-cycle workflows, with enterprise support and a procurement process that expects all of it. At that scale a self-serve tool isn't competing; it's the wrong category. Both platforms are built for this, recognized for it, and switching to shave a per-seat price would cost you more in lost integration than you'd save.

Choose a self-serve scribe if you're an independent practice or a small group that wants a clean note in two minutes, published pricing, a BAA without an enterprise contract, and a trial you can start this afternoon. And if you want the chart bundled with the scribe rather than a separate EHR to integrate, that's the case for a tool like ours specifically.

The split is size and EHR depth, not quality. All three draft good notes. Abridge and DAX assume you have an integration team; we assume you'd rather not. For the standalone view of the fast-growing enterprise player, [Abridge alternatives](/us/blog/abridge-alternatives/) covers when that health-system tool is overkill.

## How to decide in a week

1. Count your EHR-integration need honestly. If "the scribe writes into my system's EHR automatically, across many clinicians" is a hard requirement, you're in enterprise territory, and both Abridge and DAX belong on your list.
2. If it isn't, shortlist self-serve tools with published prices and a same-day, no-card trial.
3. Match the clinical output: a note plus ICD-10 suggestions plus a checked prescription draft, so you compare like for like instead of enterprise plumbing against a notepad.
4. Settle the audio question with every vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits. A scripted demo flatters every scribe equally.

The receipts behind our claims are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Use the [comparison page](/us/compare/) to see how each option fits your own visit types over a real clinic week. If you're an independent practice, the odds are good that both enterprise tools are more than you need, and a self-serve scribe with a bundled EHR at less than a fraction of the cost does the job you actually have.

---

## AdvancedMD Alternatives: A Flat Bundle vs Module Pricing
https://patientsquare.com/us/blog/advancedmd-alternatives/
Published 2026-07-14 · Updated 2026-08-27 · Tags: alternatives, ehr, advancedmd, pricing

AdvancedMD prices by module and climbs fast for small groups. Alternatives that fold scribe, EHR, and scheduling into one flat price from $119 per provider.

AdvancedMD prices by module. Third-party trackers put a single module near $229 per provider per month, the EHR-plus-practice-management bundle around $429, and full suites with patient engagement and telehealth at $729 to $999. Managed billing runs 3 to 7 percent of collections on top. AdvancedMD publishes no simple flat rate, so these are outside estimates.

Most practices looking for an AdvancedMD alternative aren't unhappy with the software; they're unhappy with the invoice. AdvancedMD prices by module, so a small group ends up stacking EHR, practice management, patient engagement, and telehealth into a bill that climbs past **$429 per provider** before billing fees. If you'd rather one flat price for the pieces you use every day, Patient Square's Copilot plan is **$119 per provider per month** annually and folds the ambient scribe, AI Copilot EHR, scheduling, and messaging into a single line. You can see the note quality on a real visit first.

This isn't a claim that Patient Square does everything AdvancedMD does. It doesn't. It's a claim about which cost model fits a small group better.

> **Key takeaways**
>
> - AdvancedMD prices by module: ~$229 single module, ~$429 EHR+PM bundle, up to $729–$999 for full suites (third-party estimates).
> - Managed billing adds 3–7% of collections on top of the per-provider fee.
> - For a small group, the module stack can mean paying enterprise overhead for lightly-used pieces.
> - Patient Square Copilot is $119/provider monthly (annual), scribe plus EHR plus scheduling in one flat price.
> - AdvancedMD still wins when a deep revenue-cycle engine is the center of your evaluation.

## AdvancedMD alternatives at a glance

The choice is really flat-bundle versus module-stack.

| Alternative | Pricing model | Ambient scribe | Estimated starting cost |
|---|---|---|---|
| AdvancedMD (staying) | Per module, stacks | Not the headline feature | ~$229–$999/provider/mo |
| Patient Square Copilot | Flat bundle | Yes, bundled | $119/provider/mo (annual) |
| Full EHR + separate scribe | Base + add-on | Separate subscription | Varies |
| Behavioral-health suite | Tiered + add-ons | Add-on note-taker | $49–$99/mo |

AdvancedMD numbers are third-party estimates as of this writing; get a written quote for your module mix. The table shows direction.

If per-module billing is your headache, start with the flat option. If you run heavy claims volume, keep reading; the billing engine is a real consideration.

## Why AdvancedMD's module pricing adds up for small groups

AdvancedMD's model is flexible by design. You buy the EHR module, or the practice-management module, or both, and layer patient engagement, telehealth, and reporting on top. For a large organization that wants granular control, that's a feature.

For a three-provider group, it's a math problem. Third-party trackers put a single module near $229 per provider, the EHR-plus-PM bundle around $429, and a full suite with engagement and telehealth at $729 to $999. Then managed billing takes 3 to 7 percent of collections. Add implementation of $2,000 to $5,000, and the per-provider number you started with is not the number you pay.

None of that is hidden maliciously. It's just enterprise pricing applied to a small practice, and small practices rarely use enough of the suite to justify it. A flat bundle inverts the model: one price, the common pieces included, no per-module climb.

## What a flat bundle includes

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** annually. Here's what that flat price covers:

- **Ambient scribe**, drafting a structured note about two minutes after the visit ends.
- **AI Copilot EHR**, the bundled record system, no separate EHR-module fee.
- **Scheduling**, included from the entry tier.
- **WhatsApp messaging**, added at the Copilot tier.
- **Unlimited notes**, no per-note metering, no setup fee.

What it isn't: a revenue-cycle engine. Patient Square offers ICD-10 *suggestions* to speed coding, not managed billing or claims scrubbing. If billing runs your practice, that gap is the whole story, and AdvancedMD's RCM depth is worth its price. Book a demo and judge the note before you weigh the rest.

## AdvancedMD vs Patient Square: the small-group view

Run it for a two-provider group.

| | AdvancedMD EHR+PM (estimated) | Patient Square Copilot |
|---|---|---|
| Per-provider base (mo) | ~$429 | $119 (annual) |
| Ambient scribe | Not the headline | Bundled |
| Pricing model | Per module | Flat bundle |
| Managed billing | 3–7% of collections | Not offered |
| Implementation | $2,000–$5,000 | None |
| Published price | No | Yes |
| Free trial | Demo-led | 7-day trial |

The takeaway isn't "cheaper is better." It's that you're buying two different things. AdvancedMD sells a full practice-operations platform with real billing muscle. Practice Copilot is an AI clinical platform for practices: ambient scribe plus Patient Square EHR from the Copilot tier, or an alongside path for an existing EHR. For a small group whose day is visits and notes rather than claims workflows, the flat bundle is less to manage and less to pay. For our roundup of bundled tools, see [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/), and for a related cost breakdown, the [eClinicalWorks cost](/us/blog/eclinicalworks-cost/) page.

## When AdvancedMD is the better choice

Keep AdvancedMD, or choose it, if revenue cycle is the center of your world. If you need managed billing, deep claims workflows, patient-engagement tooling, and the ability to compose exactly the module mix a growing multi-site group requires, AdvancedMD earns its cost and its complexity. A flat scribe-plus-EHR bundle isn't built for that, and switching to save on the per-provider line would cost you far more in lost billing capability.

AdvancedMD is also the better fit if you're scaling past a handful of providers and want one vendor to own operations end to end. The module model that feels heavy at three providers starts to make sense at thirty. Pick based on where you're headed, not just where you are.

## How to compare your real AdvancedMD cost in an afternoon

Build your own number, then decide:

1. Get the AdvancedMD quote in writing, itemized by module, including the billing-fee percentage.
2. Add managed billing as a percentage of your real monthly collections.
3. Add implementation as a one-time cost amortized over year one.
4. Compare that total against a flat bundle at $119 per provider annually with the scribe included.
5. Trial the alternative on a real clinic week before deciding. A demo hides the daily reality.

The receipts, encryption, access, and audit status, are on the [security page](/us/security/), and the full price ladder is on the [pricing page](/us/pricing/). Book a short demo to check the note against your own visits, then run the 7-day trial on a real week. For a small group tired of watching the module count climb, one flat price for the scribe and the record is usually the simpler, cheaper answer to the job you actually have.

---

## AI Scribe vs Transcription Cost in India: The Crossover Math
https://patientsquare.com/in/blog/ai-medical-scribe-vs-transcription-cost-india/
Published 2026-07-14 · Tags: pricing, comparison, ai-scribe, transcription

Medical transcription bills per line, forever. An AI scribe is flat per doctor from ₹1,599/mo. Here is the crossover math and when each one wins.

Almost always per line, where a line is the industry-standard 65 characters. Offshore Indian transcription runs roughly $0.04 to $0.08 a line, and some India sellers quote ₹5 to ₹99 a minute of audio instead. Either way, the meter never stops: every note you dictate this year, next year, and the year after adds to the bill. Volume is the enemy of a per-line contract.

If you are pricing medical transcription against an AI scribe, the answer turns on one thing: how a per-line bill behaves as your OPD grows. Transcription charges you for every line you produce, forever. An AI scribe charges a flat ₹1,599 per doctor per month on Patient Square's Assist plan (annual, ex-GST), with unlimited notes. Past a couple of dozen notes a month, flat wins, and it keeps winning harder the busier you get. You can check the [India pricing](/in/pricing/) before you read the math below.

The catch is that they don't produce the same thing. One hands you a typed transcript hours later. The other hands you a reviewed clinical note two minutes after the patient leaves. Price them side by side, then decide which output you actually want.

> **Key takeaways**
>
> - Indian medical transcription bills per line (65 characters is the standard line) at roughly $0.04 to $0.08 a line offshore, or ₹5 to ₹99 a minute of audio.
> - Patient Square's Assist plan is flat: ₹1,599 per doctor per month, annual, ex-GST, unlimited visits and notes, no metering.
> - The crossover comes fast. At about ₹100 a transcribed note, 16 notes a month already beats the flat plan. Most OPD doctors pass that in a day.
> - Transcription gives you a typed transcript, often hours later. The AI scribe gives you a structured SOAP note, ICD-10 suggestions, and a prescription draft in about two minutes.
> - Transcription still wins for verbatim medico-legal records with no time pressure, or genuinely tiny volume.

## How does medical transcription actually get priced in India?

Per line. That is the industry convention, and a line means the standard 65 characters, per ScribeMed's 2026 rate breakdown, not one sentence or one thought. Offshore Indian transcription runs roughly $0.04 to $0.08 a line by that same source, the lowest tier in the global market. Some India sellers skip lines and quote per minute of audio instead: IndiaMART listings show starting rates from about ₹5 to ₹99 a minute as of mid-2026.

Whichever meter your vendor uses, the shape is the same. You pay for output. A long, detailed note costs more than a terse one. A hundred-patient Tuesday costs more than a quiet Monday. And the bill never ends, because next month's notes are next month's charge. That is fine when volume is low. It gets expensive fast when it isn't.

If you want the workflow comparison rather than just the price, our [transcription vs AI scribe walkthrough](/in/blog/medical-transcription-vs-ai-scribe-india/) covers what changes day to day. Or book a demo and watch a finished note appear instead of a transcript.

## How does an AI scribe get priced instead?

Flat, per doctor, per month, with nothing metered underneath. Patient Square's Assist plan is ₹1,599 per doctor per month on an annual plan, ex-GST. Add 18% GST and it's ₹1,887. That single number covers unlimited visits and notes. There is no per-line charge, no per-minute charge, and no setup fee. A 4-note day and a 40-note day cost exactly the same.

That is the structural difference. Transcription prices your volume. A subscription prices your seat. The moment your volume is anything but tiny, pricing the seat is cheaper, and it gets more lopsided the busier your OPD runs. A doctor doing 200-patient days is the worst possible customer for a per-line vendor and the best possible fit for a flat plan.

Here is Patient Square's India ladder so the anchor is clear:

| Plan | Price (annual, per doctor, ex-GST) | With 18% GST | What you get |
|---|---|---|---|
| Assist | ₹1,599/mo | ₹1,887/mo | AI Medical Scribe, ICD-10 suggestions, eRx drafts, scheduling |
| Copilot | ₹2,399/mo | ₹2,831/mo | Everything in Assist, plus bundled AI Copilot EHR and WhatsApp messaging |
| Autopilot | ₹3,999/mo | ₹4,719/mo | Everything in Copilot, plus AI Receptionist, AI Follow-ups, priority support, analytics |

Prices are in Indian rupees, shown ex-GST; GST is added at the prevailing rate, currently 18%. Confirm the current numbers on the [pricing page](/in/pricing/).

## Where does the crossover happen?

Let's do the arithmetic a per-line contract hides from you. Take a middling note: about 20 lines at 65 characters each. At roughly ₹5 a line (the low end of Indian per-line-equivalent rates), that's about ₹100 a note. Now compare monthly totals against the flat ₹1,599 Assist plan.

| Notes per month | Transcription (~₹100/note) | Patient Square Assist (flat) | Cheaper option |
|---|---|---|---|
| 10 | ₹1,000 | ₹1,599 | Transcription |
| 16 | ₹1,600 | ₹1,599 | About even |
| 40 | ₹4,000 | ₹1,599 | AI scribe |
| 120 | ₹12,000 | ₹1,599 | AI scribe |
| 400 | ₹40,000 | ₹1,599 | AI scribe |

The crossover sits near 16 notes a month. Most OPD doctors clear that in a day or two. So for anyone with a real patient load, the flat plan isn't a little cheaper, it's the obvious answer. The per-line model only stays competitive at very low volume, and it punishes exactly the busy clinics that most need documentation help. If your Tuesday looks like 40 patients, book a demo and price your own volume against the table above.

## Are you even buying the same thing?

No, and pretending you are is how the price comparison misleads people. Transcription gives you a typed record of what was said. It's verbatim, it's usually human-typed, and it usually lands hours later, sometimes the next day. You still have to turn that transcript into a structured note, pull out the diagnosis, and write the prescription yourself.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It's not a transcript. It's a note. The clinical reasoning is done, the codes are suggested, the Rx is drafted. You review, edit, and sign.

That gap matters for more than convenience. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A same-day structured note is a defensible record. A transcript sitting in a vendor's queue is not, at least not yet. The AI scribe closes that loop before the next patient walks in.

One honest limit: the note always comes out in clean clinical English, even when the consult ran in Hindi or a mix. The scribe captures the regional language; it does not write the note in it. If you specifically need Hindi-language note output, that's not what this is.

## When is transcription still the better call?

Two cases, and they're real.

First, when you need a verbatim, human-typed record and time genuinely doesn't matter. Some medico-legal and research workflows want the exact words, human-verified, and are happy to wait. A structured AI note is a different artifact. If word-for-word is the requirement, transcription is the tool.

Second, when your volume is tiny. A doctor seeing three or four patients a week may never cross the 16-note line where a subscription pays off. Pay-per-line with no monthly commitment can genuinely be cheaper and simpler for that pattern. Don't buy a flat plan to sit idle.

For everyone in between, which is most practicing doctors, the math and the output both point the same way. If you're weighing the broader software spend, our [clinic software cost guide](/in/blog/clinic-software-cost-guide-india/) puts documentation in context, and the [solo-doctor cost breakdown](/in/blog/ai-scribe-for-solo-doctors-india/) runs the single-doctor case in detail. If you're also comparing Augnito on price specifically, [Augnito price vs AI scribe in India](/in/blog/augnito-price-vs-ai-scribe-india/) puts the two side by side. And if you want to understand all the hidden EHR costs beyond transcription, [EHR software cost guide](/in/blog/ehr-software-cost-india-buyers-guide/) names every line item vendors leave out of the headline number.

## How to decide in a week

Skip the spec sheet. Run your own numbers:

1. Count a normal week of notes. Multiply by four for a monthly figure. If it's above about 16, flat pricing already wins on cost alone.
2. Ask your transcription vendor for their exact per-line or per-minute rate and their turnaround time in hours. Get it in writing.
3. Decide whether you need a transcript or a note. If you want the diagnosis, codes, and Rx handed to you, that's a scribe, not transcription.
4. Trial the scribe on real visits, not a scripted demo. Watch how long the note takes to appear and whether it needs heavy editing.
5. Confirm the current price and GST on the [pricing page](/in/pricing/), then book a short demo to see the note quality against your own OPD.

The receipts on encryption, access, and data ownership are on the [security page](/in/security/). For most Indian doctors, a flat plan that covers unlimited notes beats a meter that never stops, and the output is a finished note instead of a transcript you still have to write up.

---

## AI Scribe Cost for a Solo Doctor in India (2026)
https://patientsquare.com/in/blog/ai-scribe-cost-for-solo-doctor-india/
Published 2026-07-14 · Tags: india, pricing, ai-scribe, cost

AI scribe cost for a solo doctor in India: ₹1,599/mo (annual, ex-GST), unlimited visits, no per-note metering, no setup fee, plus the per-visit math.

Patient Square's Assist tier is ₹1,999 per month, or ₹1,599 per month on annual billing, ex-GST (add 18% GST). That covers unlimited visits and notes with no per-note charge and no setup fee. Add the bundled AI Copilot EHR by moving up to the Copilot tier at ₹2,399 per month annual, ex-GST. For a solo doctor, the scribe alone at ₹1,599 is the entry point, and the price is on the pricing page, not behind a demo call.

For a solo doctor in India, an AI scribe starts at ₹1,599 per clinician per month (annual billing, ex-GST, so about ₹1,887 with 18% GST). That's Patient Square's Assist tier: unlimited visits and notes, no per-note charge, no setup fee. It handles the writing so you don't carry the day home. Want records born digital in one place too? The Copilot tier at ₹2,399/mo (annual, ex-GST) bundles the AI Copilot EHR. The price is on the [pricing page](/in/pricing/), not behind a sales call, and you can book a demo to see a finished note in about two minutes before you spend a rupee.

> **Key takeaways**
>
> - Entry price for a solo doctor: ₹1,599/mo per clinician (annual, ex-GST), about ₹1,887 with 18% GST.
> - Unlimited visits and notes, no per-note metering, no setup fee, so your bill is the same on a 15-patient day or a 60-patient day.
> - Bundled AI Copilot EHR starts one tier up, at ₹2,399/mo (annual, ex-GST).
> - At 20 patients a day, ₹1,599/mo works out to roughly ₹4 per visit, less than the chai between consults.
> - "AI is expensive" is a metering fear. A flat per-doctor rate removes it: the cost doesn't move with volume.

## What does an AI scribe actually cost a solo doctor?

Here's the number without the runaround. Patient Square's cheapest tier, Assist, is ₹1,999 per month month-to-month, or ₹1,599 per month if you commit annually, both ex-GST. Add 18% GST and the annual rate is about ₹1,887 a month. That's it for the scribe. No setup fee, no per-note charge, no minimum patient count.

| Plan | Monthly (ex-GST) | Annual, per mo (ex-GST) | With 18% GST (annual) | What you get |
|---|---|---|---|---|
| Assist | ₹1,999 | ₹1,599 | ~₹1,887 | AI Medical Scribe, ICD-10 suggestions, eRx drafts, scheduling |
| Copilot | ₹2,999 | ₹2,399 | ~₹2,831 | Everything in Assist, plus AI Copilot EHR and WhatsApp messaging |
| Autopilot | ₹4,999 | ₹3,999 | ~₹4,719 | Everything in Copilot, plus AI Receptionist, AI Follow-ups, priority support |

A solo doctor who just wants the charting burden gone starts at Assist. A solo doctor who wants records in one place moves to Copilot for the bundled EHR. Both are per clinician, so the price is exactly what one doctor pays.

## The per-visit math that ends the "AI is expensive" worry

The price objection usually isn't about the monthly figure. It's a fear of a meter running: charged per note, per minute, or per transcription line, so a busy day becomes an unpredictable bill. Patient Square doesn't work that way. Every plan is unlimited, flat per doctor. So the real cost is the monthly rate divided by however many patients you actually see.

| Patients per day (22 days/mo) | Visits per month | Cost per visit at ₹1,599/mo | Cost per visit at ₹2,399/mo (with EHR) |
|---|---|---|---|
| 15 | 330 | ~₹4.8 | ~₹7.3 |
| 20 | 440 | ~₹3.6 | ~₹5.5 |
| 30 | 660 | ~₹2.4 | ~₹3.6 |
| 50 | 1,100 | ~₹1.5 | ~₹2.2 |

The busier you are, the cheaper each note gets, which is the exact opposite of per-note pricing, where a hundred-patient day costs you a hundred times. A per-line transcription vendor bills forever and scales up with your volume. A flat scribe bills once and gets cheaper per visit as your queue grows. For the head-to-head, our [medical transcription vs AI scribe cost post](/in/blog/medical-transcription-vs-ai-scribe-india/) shows the crossover.

If those numbers describe your day, book a demo and check the note quality on your own visit type before you assume cheaper means worse.

## Why unlimited beats a low per-note price

A low headline per-note rate looks cheap until you do the arithmetic on an Indian OPD. The average consult in a 67-country study ran about two minutes; the queue sets the pace, and a solo doctor can push past 50 patients on a heavy day. Any pricing that charges by the note or the minute punishes exactly the doctor who needs the tool most.

Flat per-doctor pricing removes the calculation entirely. You never sit at your desk deciding whether this patient is "worth" a note. You never ration the scribe to keep the bill down. Every visit gets a complete, defensible record, which is also the record that wins a negligence complaint, and India sees an estimated 65,000 of those reach courts and consumer forums a year. The note you didn't skip to save ₹3 is the note that protects you.

That's the honest case for a flat plan: predictability. Your software cost is a line you set once at the start of the year, not a variable that spikes on your busiest, most valuable days.

## What the ₹1,599 tier actually does at the desk

Concretely, on a Tuesday OPD. You start the visit; a live transcript runs as you talk. The patient speaks Hindi, you answer in English, they slip back to Marathi, and it keeps up, because the scribe handles code-mixed Indian-language conversation. The moment the patient leaves, a structured SOAP note is ready in clean clinical English, with ICD-10 suggestions attached and a prescription draft you review and sign. Audio isn't stored; it's processed in memory and discarded once the note drafts. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Two honest limits, because a cost post shouldn't oversell. The languages are input only: the scribe understands Hindi and 20-plus Indian languages, but the note comes out in English. And the prescription is a draft, not e-prescribing; there's no transmission to a pharmacy. If either is a dealbreaker, better to know now than after you've paid.

Move up to Copilot at ₹2,399 and you add the bundled AI Copilot EHR, so records live in one place instead of being copied out. That's the whole ladder a solo doctor needs. For the segment view, our [best clinic software for a single doctor roundup](/in/blog/best-clinic-software-for-single-doctor-india/) and [AI scribe for solo doctors post](/in/blog/ai-scribe-for-solo-doctors-india/) go wider.

## When an AI scribe isn't worth it yet

Fair fork. The scribe earns its keep when documentation is your bottleneck. If it isn't, hold off.

Skip it if you see a handful of patients a day and charting genuinely isn't a burden, or if your notes are so short that typing them takes seconds. At very low volume the per-visit cost climbs and the time saved is small. Skip it too if you specifically need Indian-language note output or live e-prescribing today; those aren't what this tool does.

Buy it if you're a solo doctor losing evenings to charting, running a queue where two-minute consults leave no time to write, and you want a complete record on every visit without hiring a scribe or a junior. That's the case the ₹1,599 tier is built for, and it's most solo doctors reading a cost page.

The test isn't the price. It's whether you'd trade ₹1,887 a month, with GST, for the hour you currently spend writing up the day. For most busy solo practices, that's an easy yes.

## Decide it in a week

1. Count your real daily patient volume and divide ₹1,887 (with GST) by your monthly visits. That's your true per-note cost.
2. Decide scribe-only or scribe-plus-EHR: if your records already live somewhere workable, start at Assist; if you want them in one place, take Copilot.
3. Get any competing quote as an all-in monthly cost at your real volume, not a per-note headline, so you're comparing the same thing.
4. Match the output: note plus ICD-10 suggestions plus a prescription draft, and confirm the note comes out in English if that matters to you.
5. Trial on a real clinic day. A scripted demo flatters every scribe.

The receipts on encryption, access, and audit status are on the [security page](/in/security/), and the full price ladder is on the [pricing page](/in/pricing/). Book a short demo to see the note against your own visits, then run the 7-day trial on a real week. At ₹1,887 a month with GST for unlimited notes, the price worry is smaller than one evening of charting.

---

## AI Medical Scribe Cost Comparison: Real 2026 Prices
https://patientsquare.com/us/blog/ai-medical-scribe-cost-comparison/
Published 2026-07-13 · Updated 2026-07-18 · Tags: ai-scribe, pricing, comparison, cost

Compare 2026 AI medical scribe prices, from $39 capped plans to $1,500+ enterprise tools, with published $79, $119, and $199 Patient Square tiers.

It splits into two camps. Self-serve scribes publish prices from about $39 to $120 a month per clinician: Freed $39–$119, Nabla $119, Tali around CA$100–$150. Enterprise scribes are quote-only and land far higher: Abridge is estimated near $200–$800, and Dragon Copilot (Nuance DAX) lists around $604–$1,512 on Microsoft's marketplace. Patient Square publishes $79, $119, or $199.

AI medical scribes cost anywhere from $39 to over $1,500 a month per clinician in 2026, and half of them won't tell you their price without a sales call. That's the whole problem with shopping this category. So here's the real table, published numbers where they exist and honest estimates where they don't, sorted so you can see published-price tools beside enterprise tools that make you ask. Patient Square publishes $79, $119, or $199 a month, and the $119 Copilot plan bundles an AI EHR so you're not also paying for a separate chart. You can book a demo and see a finished note against your own visit before you spend anything.

Let's get the numbers on the table first, then break down what actually drives the cost.

> **Key takeaways**
>
> - Published scribe prices include Freed $39–$119, Nabla $119, Tali ~CA$100–$150, and Patient Square $79/$119/$199.
> - Enterprise scribes are quote-only and far higher: Abridge est. ~$200–$800, Dragon Copilot (DAX) list ~$604–$1,512, DeepScribe est. ~$400–$500, Suki est. ~$299–$399.
> - The cheapest sticker (Freed Starter, $39) caps at 40 notes; unlimited plans start around $79.
> - Most scribes don't include an EHR. Patient Square's $119 Copilot bundles one, which changes the total-cost math.
> - Compare cost per note in your own currency and volume, and add a separate EHR cost when the scribe doesn't ship one.

## The 2026 AI medical scribe price table

Here's the field, cheapest published sticker first, then the quote-only enterprise tier. Read the caps and the currency, not just the number.

| Scribe | Published monthly price | Unlimited notes? | Bundled EHR | Pricing model |
|---|---|---|---|---|
| Freed Starter | $39 | No (40 notes/mo) | No | Self-serve |
| Freed Core | $79 | Yes (monthly billing) | No | Self-serve |
| Patient Square Assist | $79 (annual) | Yes | No | Assisted setup |
| Tali Pro | ~CA$100–$150 | Yes | No | Self-serve (CAD) |
| Freed Premier | $104 annual / $119 monthly | Yes | No (EHR push) | Self-serve |
| Nabla Pro | $119 | Yes | No | Self-serve |
| Patient Square Copilot | $119 (annual) | Yes | Yes | Assisted setup |
| Patient Square Autopilot | $199 (annual) | Yes | Yes | Assisted setup |
| Suki | ~$299–$399 (estimate) | Quote | No | Sales-led |
| DeepScribe | ~$400–$500 (estimate) | Quote | No | Sales-led |
| Abridge | ~$200–$800 (estimate) | Quote | No | Sales-led |
| Dragon Copilot (Nuance DAX) | ~$604–$1,512 (list) | Quote/Flex | No | Sales-led |

Published figures, including Patient Square's, are from each vendor's pricing page (July 2026). Enterprise figures marked "estimate" are third-party; those vendors publish no per-provider price. Dragon Copilot figures are Microsoft marketplace list prices. Tali is in Canadian dollars; convert before comparing.

That's the honest map. Now the part that decides your real cost.

## Why half these prices are hidden

Notice the split in that table. Freed, Nabla, Tali, and Patient Square post a number. Abridge, DeepScribe, Suki, and Dragon Copilot make you request a quote. That's not an accident, and it's not really about the software; it's about who they sell to.

The quote-only tools sell to health systems, where price tracks the number of providers, the depth of EHR integration, and how hard the customer negotiates. A hundred-provider system pays a very different per-seat rate than a ten-provider group, so a single public number wouldn't mean much to them. Fair enough at that scale.

The scale involved is the tell. When Microsoft launched Dragon Copilot in March 2025, it said its DAX ambient technology had already handled more than 3 million patient conversations across 600 healthcare organizations in a single month. A vendor operating at that volume is negotiating enterprise contracts by the health system, not selling a $79 seat to a solo doctor, so a public sticker price genuinely wouldn't fit the model. The number is real, and so is the reason it stays off the page. That's the honest version of "contact sales."

But it lands differently on an independent practice. If you're a solo doctor, having to book a sales call to learn what a subscription costs is friction before you've seen a single note. And a vendor that hides the subscription price is usually telling you something about the renewal conversation later. A published price, $79, $119, whatever it is, means you can do the math today and you'll do the same math at renewal. That transparency is worth more than a small sticker difference. If you want the enterprise-heavy end explained, our [Abridge alternatives](/us/blog/abridge-alternatives/) page walks through when that tier is overkill. For the specific quote-only tools in the table, [DeepScribe pricing](/us/blog/deepscribe-pricing/) and [Ambience Healthcare pricing](/us/blog/ambience-healthcare-pricing/) each pull together what third-party sites estimate for those vendors.

## The cheapest scribe isn't always the cheapest scribe

The lowest sticker in the table is Freed Starter at $39. But it caps at 40 notes a month, so for a full-time clinic it's a light-use plan, not a real scribe. The moment you need unlimited notes, the floor rises to about $79 (Freed Core, Patient Square Assist), and that's the number most working practices should actually compare.

So "cheapest" depends entirely on your volume. Run the per-note math. Say you document 400 visits a month:

| Plan | Monthly price | Cost per note (400 visits) | Bundled EHR |
|---|---|---|---|
| Freed Core | $79 | $0.20 | No |
| Patient Square Assist | $79 | $0.20 | No |
| Nabla Pro | $119 | $0.30 | No |
| Patient Square Copilot | $119 | $0.30 | Yes |
| DeepScribe (est.) | ~$450 | ~$1.13 | No |
| Dragon Copilot (list) | ~$604+ | ~$1.51+ | No |

Enterprise per-note figures use midpoint estimates or list prices; those vendors publish no per-provider price. Self-serve figures are published.

Every self-serve plan is cheap per note against an evening lost to charting, so at the low end price shouldn't be your tiebreaker; note quality and workflow should be. The enterprise tools cost multiples more per note, which is fine if you're buying their integration depth and a bad deal if you're not. To see the whole self-serve field ranked, our [best AI medical scribes](/us/blog/best-ai-medical-scribes/) roundup is the honest version, and you can book a demo to test note quality directly.

## The cost most comparisons forget: the EHR

Here's the line item that skews every scribe comparison, and almost nobody puts it in the table. Most scribes don't ship a record system. Freed, Nabla, Tali, DeepScribe, Abridge, DAX, none of them sell you the chart. So if you're shopping a scribe because your documentation is broken AND your EHR is clunky, the scribe price is only half your bill. You'll pay it plus whatever your separate EHR costs.

That's where the bundle changes the math. Patient Square's Copilot plan is $119 a month, and that includes an AI Copilot EHR alongside the scribe. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus the bundled AI EHR, scheduling, and messaging as you move up the plan; at the Copilot tier the note lands in a chart that's part of the same subscription. Against a $79 scribe plus a separate EHR, $119 for both is often the cheaper total, not the more expensive one.

Keep the scope honest when you compare: our eRx is a draft you review and sign, not pharmacy transmission, and ICD-10 is suggestions, not a certified coding engine. If you're specifically buying coding or e-prescribing depth, weigh that against every vendor. But if your real need is a note plus a chart, book a demo and price the bundle against your current two-tool stack. If you're deciding between adding a scribe or replacing the whole EHR, our [free EHR AI scribe vs standalone](/us/blog/free-ehr-ai-scribe-vs-standalone/) breakdown helps.

## How to compare AI scribe prices without getting fooled

Five steps that turn the messy table above into a real decision:

1. Convert everything to your currency and billing period. Tali is in CAD; enterprise tools quote annually with setup fees. Get every number to "US dollars per clinician per month" before you compare.
2. Divide by your real monthly visit count. Cost per note is the number that matters, and it depends on your volume, not the sticker.
3. Add the EHR cost when the scribe doesn't include one. A $79 scribe plus a $100 EHR is a $179 stack; compare that to a $119 bundle honestly.
4. Confirm "unlimited" is unlimited. Check for per-note caps (Freed Starter's 40, Nabla free's 30) and setup fees, which enterprise tools often add on top of the subscription.
5. Trial on real visits. The cheapest tool that writes a note you have to rewrite isn't cheap. A 7-day trial on your own encounters settles quality faster than any price table.

The receipts behind our claims are on the [security page](/us/security/), and the price ladder with no asterisks, $79, $119, $199, is on the [pricing page](/us/pricing/). Book a short demo to see the note against your own visit type, then run the 7-day trial on a real clinic week. The scribe market hides its prices because the sales cycle is where enterprise vendors win. Shopping it well means doing the per-note math yourself, in your own currency, with the EHR cost included, and rewarding the vendors honest enough to post their number.

---

## AI Receptionist for Clinics in India: A Front-Desk Guide
https://patientsquare.com/in/blog/ai-receptionist-clinic-india/
Published 2026-07-13 · Updated 2026-08-30 · Tags: ai-receptionist, front-desk, india, clinic-automation

How to evaluate an AI receptionist for an Indian clinic front desk: workflow acceptance tests, plus the TRAI and DPDP questions to check.

Ask the vendor to demonstrate its actual front-desk workflow, including identity, consent, calendar rules, staff takeover, and failure handling. Do not infer calling, booking, reminders, triage, or patient-facing behaviour from the label "AI Receptionist." Medical advice remains with a Registered Medical Practitioner.

An AI receptionist is a product category, not a reliable description of shipped behaviour. Before you buy, ask the vendor to demonstrate the exact call, booking, calendar, reminder, escalation, and failure workflows your clinic needs. This post gives that acceptance pack, the price questions, and the TRAI and DPDP timing to check.

> **Key takeaways**
>
> - Treat each claimed front-desk job as a vendor-specific workflow to test. A product label alone does not prove calling, booking, reminder, triage, or patient-facing behaviour.
> - Check TRAI's TCCCPR 2018 requirements for the actual messaging workflow. DPDP's core processing provisions are scheduled to commence eighteen months after the 13 November 2025 Gazette notification; use consent, notice, retention, and opt-out controls as preparation and check other applicable obligations.
> - Require a human escalation path for clinical questions under the Telemedicine Practice Guidelines 2020.
> - Patient Square lists AI Receptionist as an Autopilot module. Autopilot is ₹4,999 per clinician month-to-month or ₹3,999 per clinician monthly-equivalent on annual billing, ex-GST; add 18% GST.

_Sources: TRAI TCCCPR 2018; MeitY, DPDP Act 2023; MeitY Gazette G.S.R. 843(E), 13 November 2025._

## What does an AI receptionist actually do at the front desk?

Picture a two-doctor OPD in Indore at 11am. Twelve people in the waiting area, the desk phone ringing, and a WhatsApp inbox with nine unread "doctor available today?" messages. The receptionist can do one thing at a time. Everything else waits or drops.

Use the scene to test five vendor claims, not to assume any of them: answering routine calls, booking and rescheduling against the live calendar, missed-call recovery, reminder delivery, and FAQ routing with human escalation. For each, run a consented test with a staff takeover and a deliberately failed handoff. Record the calendar result, duplicate-booking prevention, message template, opt-out, audit trail, and recovery owner. If your bottleneck is the queue inside the room rather than the phone, our [OPD queue management guide](../clinic-queue-management-india/) is the better starting point.

## Can it replace your receptionist? No, and be suspicious of anyone who says yes

Do not make a staffing decision from a demo. Test the vendor's claimed volume workflows with the current team, then require human escalation for clinical, distressed, and exception cases. The acceptance record should show what happens when the calendar is unavailable, the caller is unmatched, a message fails, or a clinical question arrives.

## What compliance questions should you ask about clinic messages?

Before enabling a vendor's messaging or calling workflow, ask which channel and registered entity will send it, and which TCCCPR classification, DLT setup, headers, templates, customer preferences, opt-out, escalation, retention, and failure process apply to the proposed use.

The Telecom Commercial Communications Customer Preference Regulations, 2018 is the framework to check for the actual SMS or calling workflow (TRAI, TCCCPR 2018). Obtain the vendor's written answers for the channel and use case you propose, then have the clinic's appropriate adviser and messaging provider confirm them.

Do not assume a booked reminder has a particular classification, or that a vendor provides a calling, booking, reminder, or WhatsApp workflow. Require a demonstration and written compliance answer for every claimed flow, including its human handoff and failure path. If WhatsApp is your main channel, our [WhatsApp for clinics guide](../whatsapp-for-clinics-india/) can help frame the questions to take to the vendor and provider.

## Who's responsible for the patient's data? You are

The Digital Personal Data Protection Act, 2023 defines data-fiduciary, notice, consent, and processing obligations, but the 13 November 2025 commencement notification schedules sections 3 to 17, including those core processing provisions, eighteen months after publication. On this page's update date, do not present them as current enforcement. Use the controls below as prudent preparation and check other applicable law, contracts, and professional obligations.

For any AI-receptionist vendor, obtain written answers about patient phone numbers, call logs, recordings, retention, location, access, and opt-out before processing. Those are useful procurement and preparation questions regardless of the staged DPDP date.

Three questions to put to any AI-receptionist vendor before you sign:

| Question | What a good answer sounds like | Red flag |
|---|---|---|
| Where does patient data (numbers, call logs, recordings) sit? | A named region and a straight answer, in writing | "On the cloud, it's secure" with no specifics |
| Are calls recorded, and can we turn that off? | Yes/no, with a toggle you control | Vague reassurance, no control |
| How does a patient opt out of messages? | A documented opt-out you can point patients to | "That never comes up" |

"The vendor handles compliance" is not a complete procurement answer. Record the vendor's commitments and have the clinic's appropriate adviser assess its obligations.

## Where's the line on medical advice? At the doctor, always

Require the vendor to demonstrate a booking/routing workflow that escalates clinical questions rather than answering them. That is a procurement requirement, not a claimed Patient Square behaviour.

Under India's Telemedicine Practice Guidelines 2020, giving medical advice is the professional responsibility of a **Registered Medical Practitioner**, who has to identify themselves by name, qualification, and registration number and verify the patient or caregiver before advising (MoHFW/Board of Governors, Telemedicine Practice Guidelines 2020). A front-desk assistant, human or software, is none of those things. So the design rule is a hard handoff: the instant a caller asks "should I take this medicine" or "my child has a fever, what do I do," the assistant's only correct move is to route to the doctor or the clinic's clinical staff, not to answer.

For any claimed booking, reminder, timing, direction, fee, or routing flow, require a vendor demonstration and an immediate human escalation path for clinical questions. Ask what happens when a caller describes a symptom, when the workflow fails, and when staff must take over; record the answer in the acceptance test.

## Does the front desk talk to the rest of your clinic?

A standalone answering bot is a start. But the front desk isn't an island, and its real value shows up when the calls and messages connect to the calendar and the visit itself.

Ask the vendor to run one connected test: create a booking, inspect calendar availability, change it, send a permitted reminder, hand off a clinical question, record the visit, trigger any claimed follow-up, and then recover from a failed message or duplicate attempt. Confirm which steps are automated, which require staff, and whether the audit trail reaches the systems you use. If you're evaluating just the booking layer right now, our [appointment scheduling software buyer's guide](../doctor-appointment-scheduling-software-india/) breaks down what online booking has to get right. And for the after-visit side, [patient follow-up automation](/us/blog/ai-patient-follow-up-automation/) covers which nudges need a clinician's eyes.

## Where does Patient Square fit, and what won't we claim?

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

AI Receptionist is a named Practice Copilot module at Autopilot. The current product material does not describe its calling, booking, reminder, triage, or patient-facing behaviour, so this page does not assign those behaviours to Patient Square. Use the acceptance pack above to make a vendor demonstrate the operational details that matter to your clinic.

Practice Copilot can use Patient Square EHR from the Copilot tier as its system of record or work alongside an existing EHR. The practice pricing is per clinician: Assist is ₹1,999 month-to-month or ₹1,599 monthly-equivalent on annual billing; Copilot is ₹2,999 month-to-month or ₹2,399 monthly-equivalent on annual billing; Autopilot is ₹4,999 month-to-month or ₹3,999 monthly-equivalent on annual billing. Prices are ex-GST and GST is added at the prevailing rate, currently 18%. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> to test the documented scribe workflow and inspect the Autopilot module in the product context.

---

## AI Scribe for ENT Clinics in India: OPD-Speed Notes
https://patientsquare.com/in/blog/ai-scribe-for-ent-clinics-india/
Published 2026-07-13 · Tags: specialty, ai-scribe, ent

An ambient AI scribe built for busy ENT OPDs, multilingual capture, clean English notes, ICD-10 suggestions. Per-doctor pricing from ₹1,599/mo + GST.

Yes. That's the case it's built for. The scribe listens during the visit and hands back a structured SOAP note about two minutes after the patient leaves, so it keeps pace with a queue that turns over every few minutes. There's no per-note charge and no visit limit, so a hundred-patient ENT day costs the same as a quiet one: a flat per-doctor price from ₹1,599/mo annual plus GST.

If you run an ENT OPD in India, the scribe you want is the one that keeps up with the queue. AI Medical Scribe by Patient Square listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the patient leaves. It captures the consult in Hindi, Tamil, or a Hinglish mix and writes the note in clean English. Flat per-doctor price from [₹1,599/mo on annual billing](../../pricing/) plus 18% GST, unlimited visits, no per-note charge. A hundred-patient day costs the same as a quiet one.

This is the ENT-specific case: why high-volume ear-nose-throat OPDs are a hard documentation problem, how ambient capture fits between patients, what the scribe drafts, and where an EHR comes in later.

> **Key takeaways**
>
> - Built for volume: structured SOAP note about two minutes after each patient, so it fits an ENT queue that turns over fast.
> - Multilingual on the input side, English on the output. Hindi, Tamil, Telugu, Hinglish in; clean clinical English notes out.
> - Specialty-aware templates ship out of the box, so the note reflects an ENT consult, not a generic visit.
> - Flat per-doctor pricing from ₹1,599/mo annual (ex-GST). Unlimited visits, no per-note metering, no setup fee.
> - Scribe runs standalone; the bundled AI Copilot EHR is one tier up (₹2,399/mo annual) when you want connected records.

## Why is an ENT OPD hard to document?

Volume plus variety. An ENT clinic sees a blocked ear, then allergic rhinitis, then a tonsillitis follow-up, then a vertigo work-up, in the time it takes most specialties to see one patient. In a 67-country study in BMJ Open, the average Indian consult ran about two minutes, among the shortest anywhere. In a packed ENT OPD it's often less. Two minutes doesn't leave room to also write a defensible note, so the note is what gives.

The result you already know: notes written from memory at the end of the session, or not written at all. Both are a problem. Thin records don't hold up if a case goes to a consumer forum, and they don't help the next doctor who sees that patient. The scribe closes the gap by writing while you work, not after.

If that's your Tuesday, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch it draft an ENT note from a real consult.

## How ambient capture fits an ENT visit

The scribe listens during the consult and drafts the note the moment the patient leaves. You don't dictate a separate summary; it works off the actual conversation.

For ENT that matters because the consult is fast and physical. You're looking in an ear, checking a throat, talking through symptoms in whatever language the patient speaks. The scribe captures the history and the plan from the conversation, structures it into a SOAP note, and suggests ICD-10 codes so your coding isn't a separate chore.

Specialty-aware templates ship out of the box, so the note comes back shaped like an ENT visit rather than a blank generic form. You review, edit if needed, and sign. About two minutes, and the patient's already left the room.

The scribe also drafts a prescription from what was discussed, nasal spray, antibiotic, ear drops, for you to check and sign. That's a draft, a keystroke-saver, not an e-prescribing button. The clinical decision stays yours.

## Does it handle the languages an ENT OPD actually runs in?

Yes, and this is the part that decides it for a lot of Indian clinics. A patient describes ear pain in Hindi, switches to English for the medicine name, throws in a Marathi phrase. That's a normal OPD sentence, and it breaks tools built for one language.

The scribe listens in English, Hindi, and 20-plus Indian languages, including code-mixed Hinglish, and keeps up when the patient and doctor switch mid-sentence. What comes out is always a clean clinical English note. The flexibility is on the input side; the record stays consistent and readable. You never get a half-Hindi, half-English note you have to clean up later.

## What does it cost for an ENT clinic in India?

Flat per-doctor, ex-GST, with 18% shown once.

| Plan | What an ENT clinic gets | Monthly (annual billing) | With 18% GST |
|---|---|---|---|
| Assist | AI scribe, ICD-10 suggestions, eRx draft, scheduling | ₹1,599 | ₹1,887 |
| Copilot | Everything in Assist, plus bundled AI Copilot EHR + WhatsApp | ₹2,399 | ₹2,831 |
| Autopilot | Everything in Copilot, plus AI Receptionist, follow-ups, priority support | ₹3,999 | ₹4,719 |

The pricing logic for a high-volume specialty: it's flat. You're not billed per note, so the busiest ENT day doesn't cost more than the quietest. No setup fee, unlimited visits at every tier. [See the full ladder](../../pricing/). If you're a single-doctor ENT practice, [AI scribe for solo doctors in India](../ai-scribe-for-solo-doctors-india/) breaks down the numbers for your size, and [scribe for doctors in India](../scribe-for-doctors-india/) covers the general case.

## When an AI scribe isn't the right fit for your ENT clinic

Honest limits. A scribe drafts notes; it isn't a full practice-management or record system on its own, and it isn't magic.

If your real bottleneck is records, not writing, a searchable history across years of patients, shared charts for multiple ENT doctors, then start with the record layer. Patient Square's bundled AI Copilot EHR at the Copilot tier handles that, but if you only ever wanted the scribe, be clear that Assist is documentation, not a full EMR.

If you need live ABDM or ABHA linkage today, know that ABDM integration is on our roadmap, not live. We won't claim a certification we don't have. What you get now is records born digital and export-ready for the ABHA-linked era on your timeline. If ABDM is a hard requirement this quarter, verify each vendor's actual status.

If you don't do much documentation, a very light-footfall clinic, the payback is smaller. The scribe earns its price fastest in a busy OPD, which most ENT clinics are.

## How to decide in a week

1. Pick your busiest ENT session and <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, then test it live with real patients, real languages.
2. Check the note against how you'd chart that visit yourself. History, exam, plan, ICD-10 suggestions.
3. Test the language mix on purpose. Take a Hindi or Hinglish consult and confirm the note comes out in clean English.
4. Time it. From patient-leaves to signed note. See whether it keeps pace with your queue.
5. Read the receipts on the [security page](../../security/), audio handling, encryption, DPDP alignment, and the ABDM roadmap.

<a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">Compare the options</a> to see an ENT note drafted against your own visit type first. For a busy ear-nose-throat OPD, the scribe's whole value is that it writes at the speed you work: a clean, coded, defensible note about two minutes after each patient, in English, no matter what language the room was speaking.

---

## OT SOAP Notes: Format, Examples, and Functional Status
https://patientsquare.com/us/blog/ot-soap-notes/
Published 2026-07-13 · Tags: soap-note, occupational-therapy, clinical-documentation

Two full worked OT SOAP notes (outpatient and school-based), each section annotated, plus a blank template and the functional-status language AI scribes miss.

An OT SOAP note documents an occupational therapy visit in four parts: Subjective (what the client and caregiver report), Objective (what you measured, including assist levels and ADL performance), Assessment (your clinical reasoning about function and progress toward goals), and Plan (what you will do next). The difference from a generic SOAP note is that OT documentation lives or dies on functional status: how much help the person needed to do a real task, not just range of motion or a raw score.

An OT SOAP note records an occupational therapy visit in four parts: Subjective (what the client and caregiver report), Objective (what you measured, including assist levels and ADL performance), Assessment (your reasoning about function and progress toward goals), and Plan (what happens next). What sets it apart from a generic medical SOAP note is functional status. An OT note has to show how much help a person needed to do a real task, not just a range-of-motion number.

That one difference is where most OT notes get thin, and it's also the part an AI scribe can't infer for you. So this page is mostly worked examples: a full outpatient note and a full school-based note, each section annotated, then a blank template you can paste, then the functional-status and goal language you have to own yourself.

> **Key takeaways**
>
> 1. OT SOAP = Subjective, Objective, Assessment, Plan. Same four sections as any SOAP note, but the currency is functional status, not raw measurements.
> 2. The Objective must carry assist levels and ADL/IADL performance. "Patient did transfers" is not an assist level. "Sit-to-stand transfer with min assist x1" is.
> 3. The Assessment states progress toward a specific goal and justifies continued skilled care. Per the 2018 AOTA documentation guidelines, the note has to demonstrate measurable functional progress.
> 4. OT evaluations code as 97165, 97166, or 97167 by complexity (AMA CPT / AOTA); timed treatment codes like 97110, 97530, and 97535 bill in 15-minute units under the CMS 8-minute rule.
> 5. Two full worked notes below (outpatient stroke rehab, school-based handwriting), plus a blank template. Steal the template.

## What makes an OT SOAP note different from a generic one?

If you've read a physician's SOAP note, the skeleton looks familiar. The content underneath is not. A medical note reasons toward a diagnosis. An OT note reasons toward occupational performance: can this person get dressed, hold a pencil, cook a meal, return to work, participate in class. Per the 2018 AOTA Guidelines for Documentation of Occupational Therapy (American Journal of Occupational Therapy), an intervention note should record the client's present level of performance and flag any significant or unexpected change in functional status. That's the spine.

Here's what each section carries in an OT note specifically.

**Subjective** is the client's and caregiver's account. How the home program went, what's hard right now, pain, fatigue, what the client wants to get back to. In pediatrics it's often the parent or teacher talking. Their words, framed clinically, not your interpretation yet.

**Objective** is the measured, observable stuff. This is where OT notes earn their keep. Assist levels for each task, ADL and IADL performance, cueing frequency, range of motion or grip strength if you tested it, standardized scores. Write only what you actually saw or measured. An assist level you didn't observe is a note that won't survive an audit.

**Assessment** is your clinical reasoning. Not a task recap. Where is the client relative to their goals, why did the assist level change, what is limiting performance, and why is continued skilled OT justified. Per the AOTA guidelines, this is where measurable functional progress has to show up.

**Plan** is the next steps. Interventions to continue or progress, home program updates, frequency and duration, goals to add or discharge, and what you'll reassess. A plan that just says "continue POC" wastes the section.

## Worked example 1: an outpatient OT note (stroke rehab)

A 67-year-old is three weeks into outpatient OT after a left-hemisphere stroke, working on right upper-extremity use and self-care. This is the bread-and-butter outpatient visit. The illustrative note:

---

**Subjective:** Client reports the home exercise program is "getting easier" and that he managed to butter toast one-handed at breakfast twice this week using the built-up handle. Reports mild fatigue in the right arm by late afternoon. Wife present, notes he is trying to use the right hand more at meals but "gives up when it's slow." Denies new shoulder pain. Goal restated by client: "I want to dress myself without her helping."

**Objective:** Upper-body dressing assessed: donned button shirt with mod assist x1 for buttoning, down from mod-max last week; managed the sleeve independently. Grooming at sink: brushed teeth with supervision and 2 verbal cues for right-hand use. Right shoulder flexion AROM 0-118 degrees (up from 0-105). Right grip 12 lb (left 46 lb). Therapeutic activities: reaching and grasping tasks graded to countertop height, 15 minutes. Self-care retraining with adaptive buttoning device, 15 minutes. No adverse response; BP stable, no dizziness on standing.

**Assessment:** Client demonstrating measurable progress toward the upper-body dressing goal: buttoning assist dropped from mod-max to mod over two weeks, and AROM gains support the functional change. Right-hand neglect during untimed tasks is the main limiter now, not strength alone, which is why cueing frequency matters more than reps at this stage. Skilled OT remains necessary to grade tasks and train compensatory strategies the client cannot yet self-initiate. On track for the modified-independent dressing goal within the current plan-of-care window.

**Plan:** Continue upper-body dressing and grooming retraining, progressing to full button shirt with reduced cueing. Advance home program: add right-hand use log at meals to address neglect during untimed tasks (wife to prompt, not assist). Continue therapeutic activities (97530) and self-care training (97535) at 2x/week for 4 weeks. Re-measure grip and dressing assist level in 2 weeks. Add IADL meal-prep task next session to probe the client's stated breakfast goal.

---

What to notice. The Subjective quotes the client's actual goal in his words, which is worth more than "patient motivated." The Objective gives assist levels with a direction of travel (mod-max to mod), not just "did dressing." The Assessment names the real limiter, right-hand neglect during untimed tasks, and uses that to justify skilled care, which is exactly what a payer reviewing medical necessity needs. And the Plan ties a home-program change to the client's stated breakfast goal instead of floating a generic "continue POC." The treatment codes (97530, 97535) are timed, so the 15-minute blocks in the Objective are doing double duty: clinical record and billing support under the CMS 8-minute rule.

If you also want the generic four-section breakdown with non-OT examples, the [SOAP note examples and template](/us/blog/soap-note-examples/) post covers a cold, a blood-pressure check, and an anxiety visit.

## Worked example 2: a school-based OT note (handwriting / IEP)

School OT documentation reasons toward educational participation and IEP goals, not medical necessity. The Subjective often comes from a teacher, and the Assessment ties progress to the student's access to the curriculum. Same SOAP skeleton, different "why it matters." A 7-year-old with an IEP handwriting goal:

---

**Subjective:** Classroom teacher reports the student is "less frustrated" during morning journal time this week and completed the writing warm-up without asking to skip it. Student says printing is "still hard but the fat pencil helps." Teacher notes letter reversals still appear in independent work.

**Objective:** Handwriting sample from morning journal reviewed: 8 of 10 lowercase letters formed with correct sequence, up from 5 of 10 two weeks ago; 'b' and 'd' reversals persist. Copied a 3-word sentence from the board with 2 verbal cues for letter start-point, down from 4 cues last session. Grasp: modified tripod, stable for the 10-minute task. Used a slant board and pencil grip provided last month. Self-regulated through the full 20-minute session with one movement break.

**Assessment:** Student is progressing toward the IEP handwriting goal: correct letter formation improved from 5 to 8 of 10 and required cueing is dropping, both of which support increased independent participation in written classroom work. Persistent b/d reversals are the current barrier to independent journaling and are directional-processing, not grasp or endurance, so the next block of intervention should target letter discrimination rather than motor control. Adaptive supports (slant board, grip) are being used and appear effective; recommend continuing them across settings.

**Plan:** Continue push-in handwriting support 2x/week within the classroom writing block. Target b/d discrimination with multisensory letter-formation cues and a desk reference card. Coordinate with teacher to embed the movement break before journal time. Re-assess letter formation and cueing level in 3 weeks toward the IEP goal. Share the reference-card strategy with the classroom aide so it carries over on non-OT days.

---

Two things this teaches. First, the Objective is classroom performance (a real journal sample, cueing counts, session self-regulation), not a clinic measure lifted out of context. Second, the Assessment connects the numbers to the IEP goal and to curriculum access, which is the school equivalent of medical necessity. It also isolates the actual barrier (directional processing, not motor) and lets the Plan follow from it. If your caseload is mostly pediatric school work, the [SOAPIE note format for nursing](/us/blog/soapie-note-nursing/) post is worth a look for how the added Intervention and Evaluation steps map onto the SOAP frame, since school teams sometimes borrow that structure.

## A blank OT SOAP note template you can copy

Paste this into your chart and fill each line. The brackets are prompts, not text to keep.

---

**Subjective:**
[Client and/or caregiver report: how the home program went, current difficulties, pain/fatigue]
[Client's stated goal or priority occupation, in their words]
[Relevant change since last visit: new symptoms, life events, equipment issues]

**Objective:**
[Assist level per functional task: independent / mod independent / supervision / contact guard / min / mod / max / dependent]
[ADL and IADL performance observed this session]
[Cueing frequency and type: verbal, tactile, visual]
[Measurements you actually took: AROM, strength, standardized scores]
[Interventions and timed minutes per code: e.g. therapeutic activities 97530 x 15 min]
[Adaptive/assistive devices used or fabricated; adverse responses]

**Assessment:**
[Progress relative to each goal: direction of change in assist level or score]
[What is limiting occupational performance right now, stated as clinical reasoning]
[Why continued skilled OT is justified]
[Any significant or unexpected change in functional status]

**Plan:**
[Interventions to continue, progress, or add]
[Home program update]
[Frequency and duration]
[Goals to add, revise, or discharge]
[What you will re-assess and when]

---

Keep the order fixed and label every section. The point of SOAP is that a covering therapist, a teacher, or an auditor can jump straight to the Assessment without hunting. Per the StatPearls reference, the format was devised by Dr. Lawrence Weed about half a century ago precisely so any reader could follow the reasoning, not just the result.

## Which section does functional status actually live in?

This is the part worth slowing down on, because it's where OT notes fail quietly and where automation trips.

Functional status shows up twice, and they're not the same. In the **Objective**, functional status is the observed data: the assist level, the ADL performance, the cueing count. Facts. In the **Assessment**, functional status is the interpretation: is this person more independent than last week, and does that progress justify the next block of care. A note that records assist levels but never interprets them in the Assessment has data without judgment, which is exactly the note that gets a payer denial or a stalled IEP.

The standard assist-level vocabulary is what makes the Objective auditable: independent, modified independent, supervision, contact guard assist, minimal, moderate, maximal, dependent. Use those words, not "did okay" or "needed some help." Per the 2018 AOTA documentation guidelines, objective measures should be repeated per payer and facility requirements and documented to show measurable functional progress toward goals. If you can't compare today's assist level to a prior one, the Assessment can't demonstrate progress, and progress is the whole justification for skilled OT.

Goal language is the other half. A goal has to be measurable and functional: "Client will don a button shirt with modified independence within 4 weeks" beats "improve UE function." Every worked note above ties its Assessment back to a goal like that. This matters for AI drafting because a goal statement is a decision you own, not a phrase a transcript contains.

## How an AI scribe drafts an OT note, and the part you keep

Filling that template by hand, on every client, on a full caseload, is the documentation load that follows OTs home. That's the gap an ambient scribe is built to close.

The AI Medical Scribe by Patient Square, one module of the Practice Copilot platform, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

In an OT session, that flips your job from writing to editing. The scribe maps the session conversation onto the four sections: the Subjective from what the client and caregiver reported, the Objective from the findings and measures you said out loud, the Assessment and Plan from your stated reasoning. You read the draft, correct it, and sign. The ICD-10 entries are suggestions you confirm, not codes filed for you.

Now the honest limit, and it's the whole reason this post exists. The two sections you have to own are the functional-status data in the Objective and the goal language in the Assessment. A transcript can capture that you did a dressing task. It can't decide the assist level was "mod assist x1, down from mod-max," and it can't write "on track for the modified-independent dressing goal" unless you said the goal out loud and meant it. Say your assist levels and your goal progress aloud during the session, then check exactly those lines in the draft before you sign. Everything else the scribe can rough in; those two you decide.

The note comes out in clean clinical English. The visit audio is processed in memory and discarded the moment the draft is ready, so there's no recording sitting in an archive. If you're weighing a scribe for a rehab-heavy caseload, the [AI scribe for physical therapy](/us/blog/ai-scribe-for-physical-therapy/) post covers the PT-side version of this same functional-status problem, and [what to expect from AI scribe accuracy](/us/blog/ai-scribe-accuracy-what-to-expect/) sets realistic expectations before you trust a draft on a busy day.

The worked notes above are the bar. A drafted OT note should read like one of them after a quick edit, with your assist levels and goal statement corrected, not like a transcript you have to rebuild. The way to know is to run it on real sessions, not a demo. Read the [pricing page](/us/pricing/), then try structured notes for a week on your own caseload and read the Objective and Assessment on every draft.

---

## AI Scribe for Homeopathy Clinics in India: Capture the Case
https://patientsquare.com/in/blog/ai-scribe-for-homeopathy-clinics-india/
Published 2026-07-10 · Tags: specialty, ai-scribe, homeopathy

An ambient AI scribe for homeopathy clinics, capture long case-taking in Hindi or regional languages, get a clean English note. From ₹1,599/mo + GST.

Yes, and the long consult is exactly where it helps. Homeopathic case-taking runs far longer than a typical OPD visit, and writing all of it by hand is the drain. The scribe listens through the full case, the symptoms, the modalities, the patient's own words, and drafts a structured note for you to review. It captures detail you'd otherwise lose while trying to write and listen at once.

Homeopathy has the opposite documentation problem from a fast OPD: the consult is long, and writing all of it by hand while you listen is what wears you out. AI Medical Scribe by Patient Square listens through the full case-taking, in Hindi, Tamil, or whatever language your patient is comfortable in, and hands back a structured note in clean English for you to review and sign. The remedy stays your call; the scribe just makes sure nothing the patient said gets lost. Flat per-doctor price from [₹1,599/mo on annual billing](../../pricing/) plus 18% GST, no per-consult charge, unlimited visits.

This is the homeopathy-specific case: why long case-taking is a real documentation burden, how ambient capture lets you actually listen, what the scribe does and pointedly does not do, and where a record system fits for constitutional follow-ups.

> **Key takeaways**
>
> - Homeopathy's problem is the long case, not queue speed. The scribe captures full case-taking so you don't write and listen at once.
> - Multilingual input, English output. The patient speaks Hindi or a regional language; your written case comes out in clean English.
> - It's a case recorder, not a repertory. The scribe won't select a remedy; remedy choice stays entirely your clinical work.
> - Flat per-doctor pricing from ₹1,599/mo annual (ex-GST). No per-consult charge, unlimited visits, no setup fee.
> - Scribe runs standalone; the bundled AI Copilot EHR (₹2,399/mo annual) is one tier up for records that follow a patient's history.

## Why is homeopathic case-taking hard to document?

Because it's long, and the detail is the medicine. A first homeopathic consultation can run thirty minutes or more: the presenting complaint, the modalities, the mental and emotional picture, the patient's history in their own words. Homeopaths are trained to capture the *whole* person, which means far more narrative than a two-minute allopathic OPD note.

That creates a specific bind. To take a good case you have to listen closely, watch the patient, follow where they go. But you also have to write it all down, and you can't fully do both. So either the consult stops while you catch up on notes, breaking the rapport that makes case-taking work, or you write from memory afterward and lose the exact words that would have pointed to a remedy.

India has a huge homeopathy sector, much of it still on paper. The record burden is real and mostly unautomated. The scribe is built precisely for the "listen and capture at the same time" problem. Book a demo and watch it draft a case note from a real consult.

## How ambient capture lets you actually take the case

The scribe listens through the whole consultation and drafts a structured note when it ends. You don't stop to type. You give the patient your attention, and the record is built from what was actually said.

For homeopathy that's the difference between a rich case and a thin one. When a patient describes exactly how their symptoms behave, worse in the evening, better with warmth, tied to a particular worry, those are the words that matter, and they're the words you lose when you're scribbling. The scribe keeps them, structures the case into a readable note, and hands it to you to review, refine, and sign.

Specialty-aware templates ship out of the box, so the note comes back organised rather than as one undifferentiated block of text. You confirm the detail and add your assessment. The typing is done for you; the clinical thinking is entirely yours.

## What the scribe does not do for a homeopath

Say this plainly, because it's where honesty matters most. The scribe is a case *recorder*. It is not a repertory, not a materia medica lookup, and not a remedy-selection engine. It will not tell you which remedy to give, and it doesn't try to.

It captures the consult, the symptoms, the modalities, the plan you state, into a structured note. Remedy selection, potency, repetition, all of that stays your clinical work, informed by your training and your repertory of choice. If a tool promises to *pick the remedy* for you, that's a different and much bigger claim; the scribe doesn't make it.

One more limit: the platform's ICD-10 suggestions are conventional-medicine codes. They exist for clinics that use them; they're not central to a homeopathic case, and you can ignore them. What matters here is the clean, complete narrative record, which is what the scribe delivers.

## Does it work in the languages your patients speak?

Yes, and for homeopathy this is close to essential. Case-taking often happens entirely in the patient's mother tongue, because the whole method depends on the patient describing their experience precisely, in their own words. That only works if they can speak comfortably.

The scribe listens in English, Hindi, and 20-plus Indian languages, including code-mixed speech, and keeps up when the patient switches naturally. The note it drafts always comes out in clean clinical English. So the patient talks freely in Hindi, Bengali, or Tamil, and your written case stays consistent and readable. The language flexibility is on input; the record is always English.

## What does it cost for a homeopathy clinic in India?

Flat per-doctor, ex-GST, 18% shown once.

| Plan | What a homeopathy clinic gets | Monthly (annual billing) | With 18% GST |
|---|---|---|---|
| Assist | AI scribe (full case capture), eRx draft, scheduling | ₹1,599 | ₹1,887 |
| Copilot | Everything in Assist, plus bundled AI Copilot EHR + WhatsApp | ₹2,399 | ₹2,831 |
| Autopilot | Everything in Copilot, plus AI Receptionist, follow-ups, priority support | ₹3,999 | ₹4,719 |

The flat price fits homeopathy well: you're not billed per consult, so a day of long first cases costs the same as a day of short follow-ups. No setup fee, unlimited visits at every tier. [See the full ladder](../../pricing/). For a single-practitioner clinic, [AI scribe for solo doctors in India](../ai-scribe-for-solo-doctors-india/) has the numbers, and [scribe for doctors in India](../scribe-for-doctors-india/) covers the general case.

## When an AI scribe isn't the right fit for your homeopathy clinic

Honest limits, so nobody's disappointed.

If you want software to *choose the remedy*, this isn't that. The scribe records the case; it doesn't repertorise. If remedy-selection help is what you're shopping for, you're looking for a different category of tool.

If your real need is a connected record of a patient's constitutional history across years of follow-ups, the standalone scribe (Assist) gives you great individual notes, but the searchable record layer is the bundled AI Copilot EHR at the Copilot tier. Be clear which you're buying.

If you need live ABDM or ABHA linkage today, ABDM integration is on our roadmap, not live, and we won't claim otherwise. You get records born digital and export-ready for the ABHA-linked era on your timeline. Verify every vendor's actual status if ABDM is a hard requirement now.

## How to decide in a week

1. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, then test a real first case in the language your patient actually speaks.
2. Read the drafted note against your own case-taking. Did it keep the modalities, the mentals, the exact words?
3. Confirm it captured a Hindi or regional-language consult and returned a clean English note.
4. Check that it stayed in its lane, recording the case, not trying to pick the remedy.
5. Read the [security page](../../security/), audio handling, encryption, DPDP alignment, and the ABDM roadmap.

Book a short demo to see a homeopathic case note drafted against your own style. For a homeopathy clinic, the scribe's value is that it lets you do the thing your method actually needs, listen completely, while the record writes itself in the background and comes back in clean English, ready to sign.

---

## Ambience Healthcare Alternatives: No Procurement Cycle
https://patientsquare.com/us/blog/ambience-healthcare-alternatives/
Published 2026-07-10 · Updated 2026-07-22 · Tags: ai-scribe, comparison, ambience-healthcare, pricing

Compare the health-system rollout of Ambience with published-price options for independent practices, including an AI scribe from $79 and bundled EHR from $119.

Ambience publishes no public price and sells to health systems through enterprise negotiation. Third-party review sites estimate roughly $250 to $500-plus per provider per month for documentation, with the full AI suite reaching $4,000 to $5,000 per provider per year. Those are outside estimates, not Ambience figures. Patient Square publishes $79/mo for the scribe and $119/mo for the plan with a bundled AI EHR.

Ambience Healthcare is a strong enterprise platform. It's also built for health systems, which means opaque pricing, a sales cycle, and a rollout measured in months. If you're an independent practice, that's a lot of machinery for a note. The alternative worth naming is a published-price scribe with a practice-sized setup. Patient Square's scribe starts at $79 per clinician per month on annual billing, the Copilot plan bundles an AI EHR from $119/mo, and the assisted 7-day trial begins after the workspace is ready. See the ladder on our [pricing page](../../pricing/), or book a demo to watch a note draft in about two minutes.

This isn't an Ambience takedown. It's a fit question. Below: what Ambience costs (nobody publishes it), how the timelines differ, and when the enterprise platform is the right call.

> **Key takeaways**
>
> - Ambience publishes no public price. Third-party sites estimate $250 to $500-plus per provider per month, with the full suite near $4,000 to $5,000 per provider per year. Outside estimates, not Ambience numbers.
> - Third-party reviews describe implementations running six to eighteen months. Patient Square uses a short assisted setup before its 7-day trial begins.
> - Patient Square publishes all three US tiers: $79 / $119 / $199 per clinician per month on annual billing, unlimited notes.
> - Ambience's edge is a broad enterprise AI suite tuned to health-system scale. An independent practice rarely uses most of it.
> - When you're a health system wanting that depth, Ambience is the better tool. That's the design.

## How does Ambience compare to Patient Square?

Here's the side-by-side. Ambience's price and timeline are third-party estimates, because Ambience doesn't publish either.

| | Ambience Healthcare | Patient Square |
|---|---|---|
| Published price | No; enterprise negotiation | Yes. $79 / $119 / $199 per clinician/mo, annual |
| Entry price | ~$250–$500+/provider/mo (third-party estimate) | $79/mo (Assist) |
| Time to start | ~6–18 months (third-party estimate) | Assisted workspace setup, then a 7-day trial |
| Bundled EHR | Integrates with health-system EHR | Yes, AI Copilot EHR from $119/mo |
| Clinical output | SOAP note, coding-support suite | SOAP note, ICD-10 suggestions, Rx draft |
| Best fit | Health systems and large groups | Solo and small practices |

If your practice is independent, book a demo and see whether a self-serve tool covers the job you actually have before you enter anyone's sales cycle.

## What does Ambience cost, and how long is the rollout?

Two frictions here, not one. First the price. Ambience sells to health systems through enterprise negotiation, so there's no public number. Third-party review sites estimate $250 to $500-plus per provider per month for documentation alone, and the full suite, with coding-support and other modules, closer to $4,000 to $5,000 per provider per year. Be precise: those are outside estimates on comparison pages, not prices Ambience publishes. Directional, not a quote.

Second, the timeline. The same reviews describe Ambience implementations running six to eighteen months, because a health-system deployment means EHR integration, IT resourcing, and enterprise onboarding. That's appropriate for a 2,000-clinician system. For a three-doctor practice, it's a year of waiting to document a visit.

Patient Square runs the opposite way. You can read all three prices on the [pricing page](../../pricing/) right now, and the assisted 7-day trial begins after the workspace is ready rather than after a multi-month enterprise rollout. The bundled AI Copilot EHR arrives at the Copilot tier, in the same $119-a-month line, no integration project attached.

## What do you trade leaving Ambience for a self-serve scribe?

There's a genuine trade, and it's about depth.

You give up the broad enterprise AI suite. Ambience layers modules for clinical documentation and coding support tuned to health-system workflows. Patient Square stays scoped: an ambient scribe that gives ICD-10 suggestions, not a coding platform, and a bundled AI EHR at the Copilot tier. If a wide enterprise suite is the center of your evaluation, weigh that honestly.

What you keep is the part a small practice uses. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The note exports EHR-ready (PDF, HL7, FHIR), or lives in the bundled AI EHR at the Copilot tier. Audio is processed in memory and discarded once the note drafts. A BAA is available for every customer, solo practices included.

If your shortlist is wider, [DeepScribe alternatives](../deepscribe-alternatives/) covers another sales-led enterprise scribe, and [Augmedix alternatives](../augmedix-alternatives/) looks at the human-assisted-scribing lineage. For a deeper look at what Ambience charges, [Ambience Healthcare pricing](../ambience-healthcare-pricing/) pulls together the third-party estimates and what the numbers cover.

## When is Ambience the better choice?

It's about scale and how much of the suite you'll use.

Choose Ambience if you're a health system or large group that wants an ambient platform tuned to your specialties, wired into a major EHR, with the broader AI suite and enterprise support behind it. At that scale, a self-serve tool isn't a competitor. It's the wrong category, and the six-to-eighteen-month rollout buys real integration you'd otherwise be building yourself.

Choose a practice-sized scribe if you're an independent practice or small group that wants a clean note in about two minutes, a price you can read now, an assisted trial on real visits after workspace setup, and a BAA without an enterprise contract. That's most of the practices reading this. And if you want the chart and front desk in the same subscription, that's the Copilot bundle.

## How to decide in a week

Skip the RFP for a minute and run the real test.

1. Count how much of an enterprise AI suite you'd actually use. If coding-support modules and health-system integration are hard requirements, Ambience belongs on your list.
2. If they aren't, shortlist practice-sized tools with published prices and documented trial setup and start terms.
3. Match the clinical output: note plus ICD-10 suggestions plus a prescription draft, like for like.
4. Ask about time-to-first-note. A tool with a short, explicit setup path beats a tool you'll deploy next year, for most independent practices.
5. Settle the audio question: stored or not, and for how long. Ours is never stored.

The receipts behind our claims are on the [security page](../../security/), and the price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visit type, then request the 7-day trial for a real clinic week. If you run a health system, Ambience is your tool. If you'd rather read the price first and use a smaller-practice rollout, that is the route you are shopping for.

---

## Telemedicine Software for Doctors in India: Checklist
https://patientsquare.com/in/blog/telemedicine-software-for-doctors-india/
Published 2026-07-10 · Updated 2026-10-04 · Tags: telemedicine, teleconsultation, telemedicine-software, india, buyers-guide

A doctor-side checklist for teleconsult software in India: NMC 2020 rules, prescriptions, low-bandwidth video, DPDP data, and where an AI scribe fits.

Indian telemedicine software should support the clinic's identity, consent, record-keeping, prescription, and data-handling duties under current rules. It also has to work on the connection your patients actually use and place the note in the clinic record without retyping. Booking, reminders, and payments matter, but compliance and documentation are the load-bearing tests.

You are adding teleconsultation to a clinic that already works, and the market is loud with apps that promise a booking page and a video button. Most of that is the easy 20%. The parts that decide whether telemedicine helps you or hurts you are the NMC rules, the video holding up on a weak signal, the prescription following the medicine lists, and where your patients' data ends up.

This is a doctor-side checklist, not a patient-booking pitch. It walks what actually matters when you pick teleconsult software in India, in the order it matters, and it is general information, not legal advice. Confirm the specifics against the current guidelines and your medical council.

> **Key takeaways**
>
> - The NMC Telemedicine Practice Guidelines 2020 put the duties on you, not the software: confirm identity, record consent, document the consult, prescribe within the medicine lists ([MoHFW](https://www.mohfw.gov.in/pdf/Telemedicine.pdf)). A good tool makes compliance the default; it cannot take the responsibility off you.
> - Test video on the worst connection your patients use. A platform that drops to clean audio-only beats one that freezes on HD.
> - Under the DPDP Act 2023 you are the data fiduciary. Ask where records sit, whether calls are recorded, and how you get your data back ([MeitY](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf)).
> - WhatsApp reminders and UPI payments are convenience features. Judge the tool on compliance and the consultation record first.
> - An AI scribe fits in the note, not the call: it drafts, you sign.

_Sources: MoHFW, Telemedicine Practice Guidelines 2020; MeitY, DPDP Act 2023; CBIC / GST._

If you already run appointments and payments fine and the drain is the note you type after each video call, jump to the AI scribe section. Otherwise, start where the risk is.

## Start with NMC compliance, because that is where the risk lives

Every telemedicine vendor will show you a clean video screen. Far fewer will talk you through the four things the [NMC Telemedicine Practice Guidelines 2020](../teleconsultation-guidelines-india-nmc/) actually require of you on a remote consult. Those guidelines, issued on 25 March 2020 by the Board of Governors in supersession of the Medical Council of India with NITI Aayog, sit in Appendix V of the 2002 Professional Conduct Regulations and are binding ([MoHFW](https://www.mohfw.gov.in/pdf/Telemedicine.pdf)).

Four duties matter for software selection:

1. **Confirm who the patient is.** You have to verify identity before you consult. A tool that captures name, age, and a contact number, and lets you note how you confirmed identity, supports that. A raw video link with no patient record does not.
2. **Take and record consent.** Consent can be implied when the patient initiates the consult, but it should be documented. The platform should give you a clean place to record that the patient consented, especially if you are the one who reached out.
3. **Document the consult like an in-person visit.** The conversation trail, your provisional diagnosis, the advice, the prescription. This is a record you must keep, so the tool has to produce and store one, or hand it to a system that does.
4. **Prescribe within the medicine lists.** The guidelines sort medicines into List O, List A, List B, and a prohibited set, and they set conditions such as a video consult for certain first-time prescriptions. The software cannot make that call for you. It can help you keep the prescription and the basis for it on record.

Here is the line to hold in your head while you demo anything: the software supports compliance, it does not confer it. The provisional diagnosis, the decision to prescribe, and the documented reasoning stay with you as the registered medical practitioner. A vendor that says "our platform makes you NMC-compliant" is overselling. The honest version is "our platform helps you meet your NMC duties," and that is what you want.

## Video that survives Indian bandwidth

A teleconsult is only as good as the call. And the call rarely happens on clinic wifi. It happens on a patient's 4G in a town with two bars, at 8pm, sharing the tower with everyone else who just got home.

So the question is not "is the video HD." It is "what does the tool do when the connection is bad." The platforms that work in India degrade gracefully. They drop resolution before they freeze, they fall back to audio-only cleanly when video will not hold, and they do not stack a two-second lag that turns a consult into a walkie-talkie. Ask the vendor two plain things: do you use adaptive bitrate, and is there a plain audio-call fallback. Then ignore the answers and test it yourself, on the worst connection your patients actually use, with a colleague on the other end pretending to be a patient with a poor signal.

One more practical note. A lot of Indian teleconsults still run over a WhatsApp video call or a plain phone call, and the NMC guidelines do allow telemedicine over telephone, video, or text within their conditions. That is fine. But an unstructured WhatsApp call leaves you with no consultation record and no clean consent trail, which is exactly the documentation gap dedicated software closes. If you are going to run teleconsults regularly, a tool that keeps the record is worth more than the familiarity of a chat app.

## The prescription problem, and how to keep it clean

Prescribing is where teleconsultation gets legally sharp, and where a lazy tool can quietly get you in trouble.

The guidelines let you prescribe over telemedicine after you reach a provisional diagnosis and are reasonably satisfied with the information you gathered, and they hold you to the medicine lists, with a prohibited category for Schedule X drugs, narcotics, and psychotropics ([analysis of the 2020 guidelines](https://pmc.ncbi.nlm.nih.gov/articles/PMC8106416/)). First-time prescriptions from List A generally require a video consult. All of that is your judgment to exercise, documented.

What you want from software is a way to produce and store the prescription against the consult record, so the basis for it is there if anyone asks. What you do not want is a tool that auto-fires a prescription, or one that treats a suggested medicine as an order. For the deeper walk-through of what a legally clean e-prescription looks like in India, the [e-prescription rules guide](../e-prescription-software-india-legal/) covers the signature, the record, and the medicine-list conditions.

This is also the honest boundary of what our own tool does. Where an AI scribe touches the prescription, it produces a **draft** for you to review, edit, and sign. It is not e-prescribing, it does not send anything to a pharmacy, and it never signs for you. It doesn't run an automated interaction or dosing check either; the draft reflects what you said in the consult, and the safety review is yours to do, the same as it is on any script. The signature and the responsibility are yours.

## Make the record land in your clinic, not a second silo

A teleconsult produces a note. If that note lives only inside the telemedicine app, you now have two records for the same patient: the one in your clinic system and the one in the video tool. That split is a real cost. It shows up when a teleconsult patient walks in next month and their remote history is stranded in another app.

So ask how the consultation record leaves the platform. Can you export it, copy it into your clinic record, attach it to the patient's file in whatever [OPD software](../opd-software-for-clinic-india/) you run? A tool that exports cleanly keeps one patient history intact. A tool that traps the note inside its own walls quietly fragments your records.

Two touchpoints your patients will expect, and both are fine to want. **WhatsApp** for appointment confirmations and reminders is how Indian patients actually communicate, so a platform that sends reminders over WhatsApp saves no-shows. **UPI** for the consult fee is the payment rail patients reach for first, so collecting the fee over UPI at booking cuts the awkward money conversation. Treat both as convenience wins, not as the reason to buy. They do not touch your compliance or your record; they just reduce friction around it.

## DPDP Act 2023: you are the data fiduciary

The moment a patient consults you remotely, their data lands on someone else's servers, and under the [DPDP Act 2023](../e-prescription-software-india-legal/) you are the data fiduciary for it ([MeitY](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf)). That is a legal role, and teleconsultation raises the stakes because you are now holding consultation records, chat logs, and possibly a video recording.

Three questions cut to the heart of it:

- **Where does the data physically sit?** Consultation records, patient contact details, any uploaded reports. Ask where the servers are and how the data is protected.
- **Is the call recorded or stored?** Some platforms record video by default. A stored recording of a medical consultation is sensitive data you now have to guard, retain, and eventually delete. A platform that records nothing by default gives you a cleaner posture. If it does record, that has to be consented and justified.
- **How do you get your data back if you leave?** Purpose limitation and storage limitation are legal duties now. If you stop using the tool, you need your patients' records back, and you need to know the vendor is not keeping them "just in case."

None of this is a reason to fear cloud telemedicine. It is a reason to buy it with your eyes open and pick a vendor that answers these three crisply. A tool that shrugs at "where does our data live" is telling you something.

## Where an AI scribe fits in a video consult

In the note, and only there. This is the piece that quietly eats your evenings, and the one an ambient layer is actually built for.

Picture a Pune clinic on a Wednesday afternoon: eleven teleconsults back to back, each one a video call, then the note. By the fourth patient you are typing from memory while the fifth is already calling. An ambient scribe listens during the video consult and drafts that clinical note for you to review, edit, and sign. It does not run the video, take the payment, or send the prescription. It sits alongside whatever telemedicine tool you use and hands back a draft, faster than typing after the patient has dropped off.

A few design points matter for Indian teleconsults specifically. Consults happen in braided Hindi and English, so the scribe takes code-mixed speech on input and returns the note in clean clinical English. The call audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner posture under the DPDP Act. Any prescription it drafts is yours to check and sign, and any diagnosis code it offers is a suggestion, not a final code. When your patients are in a low-signal area and the consult drops to audio, the same [offline-tolerant capture](../ai-scribe-offline-low-connectivity/) approach applies: it works from what it heard, not from a perfect stream. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That scribe is one module of [Practice Copilot](/in/products/practice-copilot/), our AI bundle for Indian clinics. We publish our prices rather than gating them: the Copilot tier is ₹2,999 per clinician a month, or ₹2,399 per month on annual billing (a 20% saving), all ex-GST, with 18% GST added on top ([Patient Square published pricing, checked October 2026](/in/pricing/)). ABDM integration is on our roadmap, not shipped, and we will not badge a status we do not hold. If the documentation drain is what you feel most on teleconsult days, the [scribe guide for Indian doctors](../scribe-for-doctors-india/) covers where it sits alongside your telemedicine setup.

## When a bundled telemedicine platform beats a standalone approach

Being honest about our own scope: we do not sell you a telemedicine platform. We draft the note. So here is the straight verdict on when a bundled telemedicine tool is the better buy, and when it is not.

| | Standalone telemedicine platform | Clinic system with teleconsult built in | AI scribe (documentation only) |
|---|---|---|---|
| **Runs the video call** | Yes | Yes | No |
| **Booking, WhatsApp, UPI** | Usually yes | Usually yes | No |
| **Keeps the consult record** | In its own app | In your clinic record | Drafts the note, you file it |
| **Prescription** | Templated, you sign | Ties to clinic record | Draft only, you review and sign |
| **NMC 2020 support** | Prompts, you comply | Prompts, you comply | Helps document; you comply |
| **Best when** | You need teleconsult only | You want one record end to end | Typing the note is the drain |

A **bundled clinic system with teleconsult built in** wins when you want one patient record and are tired of stitching apps together. If your booking, in-clinic notes, billing, and teleconsults all live in one system, you avoid the two-record split entirely, and that is worth a lot. Buy the bundle when telemedicine is a feature of your clinic, not a separate business.

A **standalone telemedicine platform** wins when teleconsultation is most of what you do, or you are running a pure remote-consult service and want the best possible video and booking flow without dragging a full clinic system along.

An **AI scribe is not an either-or with those.** It sits on top of whichever you pick, because your problem after a busy teleconsult afternoon is usually the note, not the video. We think most solo and small-clinic doctors already have a workable way to run the call, whether that is a dedicated tool or a structured WhatsApp workflow, and the real gap is the documentation. If that is you, add the scribe on top rather than ripping out a setup that already works.

## The one-page checklist

Before you sign anything, run the vendor through this:

- Does it help me confirm identity, record consent, and keep a consultation record per the [NMC 2020 guidelines](../teleconsultation-guidelines-india-nmc/)?
- Does the video degrade gracefully and fall back to audio on a weak signal? Did I test it on a real bad connection?
- Can I produce and store a prescription that follows the medicine lists, with me signing it?
- Does the consult note export into my clinic record, or does it get trapped in a second app?
- Where does the data sit, is the call recorded, and how do I get my records back if I leave?
- Is the price clear, ex-GST, with the 18% GST spelled out, and do I know whether a seat is a doctor or a location?

Get those six answered in writing and you have done more due diligence than most clinics do before they buy.

If the note is your real drain on teleconsult days, book a short demo and watch where a real consult lands as a draft, or <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> and evaluate it on your own Wednesday afternoon.

_Sources: MoHFW, Telemedicine Practice Guidelines 2020; MeitY, DPDP Act 2023; CBIC / GST; analysis of the 2020 guidelines (PMC)._

---

## Virtual Medical Scribe vs Ambient AI: What Really Changes
https://patientsquare.com/us/blog/virtual-scribe-vs-ambient-ai/
Published 2026-07-10 · Updated 2026-07-22 · Tags: remote-medical-scribe, virtual-scribe, ambient-ai, ai-scribe

Compare remote human scribes with ambient AI on latency, cost, review, privacy, what people catch, and when a human remains the better fit.

A virtual medical scribe is a real person, usually offshore or remote, listening live on a headset during the visit and typing the note in real time. An ambient AI scribe is software that captures the visit and drafts the note itself, usually about two minutes after you finish. The human works during the visit; the AI works right after it. The human can also do chart lookups and side tasks; the AI only writes the note.

A virtual medical scribe is a person. A remote one on a headset, listening to your visit live and typing the note as you talk. An ambient AI scribe is software that captures the same visit and drafts the note itself, about two minutes after you finish. Same job on paper. Very different in the room.

If you already run a remote human-scribe service and you're weighing the switch, the honest question isn't "which is better." It's "what actually changes on a Tuesday." This page walks the real differences: when the note shows up, what the bill looks like, what a person catches that software doesn't, who's listening, and the cases where the human is still the right call.

> **Key takeaways**
>
> - A virtual human scribe works *during* the visit, live on a headset. An ambient AI scribe works *right after*, drafting the note in about two minutes. That timing gap is the first thing you'll feel.
> - The cost shape flips. A remote human is per-hour or per-visit staffing that scales with your clinic day. An AI scribe is flat per-clinician software, so a packed day costs the same as a light one.
> - A person catches things software won't: ambiguity in the room, a chart lookup while you talk, a wrong dose that sounds off. An ambient AI drafts a clean note but doesn't run errands or push back.
> - Privacy changes who's on the line. A remote scribe is a third human listening to every visit. Our AI has no human on the call, and the audio is processed in memory and discarded at note draft.
> - The human still wins when you need more than the note: in-basket, orders, chart navigation, tasks beyond documentation. If that's your setup, don't switch for the sake of switching.

## What is a virtual medical scribe, exactly?

Start with the thing you already have, because "remote medical scribe" gets used loosely.

A virtual medical scribe, sometimes called a telescribe or remote scribe, is a trained person working off-site, often in a different time zone, who joins your visit by audio or video. They listen live and type the note into the chart in real time, the way an in-room scribe would, except they're not in the room. Some services also have that person manage parts of the chart while you work: pulling a prior note, dropping in an order, flagging a result. You're paying for a human's attention during your clinic hours.

That's the key word. Attention. A remote scribe is billed by the hour or by the visit because that's the unit you're buying, a person's time on your schedule. The upside is obvious: a human understands context, handles the messy parts, and can do more than write. The cost, and a few other things, follow directly from the fact that it's a person.

## What is an ambient AI scribe, and how is it different?

An ambient AI scribe is software. It listens to the visit through your phone or laptop, and after you finish, it drafts the note on its own. No person on the line. AI Medical Scribe by Patient Square is one of these: it captures the encounter, then hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready for you to review about two minutes after the visit ends.

The difference that matters most on day one is timing. A virtual human scribe produces the note *during* the visit; by the time the patient leaves, the note is mostly written. An ambient AI produces it *right after*, so there's a short wait, and you review the draft rather than watch it appear live. For most primary-care and specialty visits that two-minute gap is a non-issue, since you'd be reviewing the human's note anyway. But it's a real change in rhythm, and you should know it's there before you switch.

The second difference is scope. The AI writes the note. That's the job. It doesn't leave the note to go chase a lab or manage your in-basket, because it isn't a person with hands in your EHR. We'll come back to that, because it's the whole reason the human sometimes still wins.

## Latency: live during the visit vs a two-minute draft

Here's the trade in plain terms. A live human scribe means the note is being built while you're still talking to the patient. Walk out, and it's largely done. An ambient AI means you finish the visit, and about two minutes later the draft is sitting there for you to check.

Neither is strictly better. Live has a nice feel: nothing to wait for. But "live" also means a person is typing in real time and can fall behind on a fast visit, and you're still reviewing that note before you sign it. The AI's short delay buys you a note you read once, clean, at a moment you choose, between patients or at the end of a block. On a 14-patient Tuesday, the two minutes per visit disappear into the gaps you already have.

The honest catch: with the AI, the note doesn't exist the instant the visit ends. If your workflow depends on a fully-typed note the second the patient stands up, that's a change. Most clinicians find the review step is where their attention was going anyway, so a draft that's ready when they get to it fits fine. Test it on your own visit length rather than trust a table.

## Cost: staffing a person vs licensing software

This is the difference most practice managers feel first, because it shows up on the invoice.

A remote human scribe is staffing. You pay for a person's time, priced per hour or per visit, and that bill scales with your clinic day. More hours, more visits, more cost. Two providers running full days cost roughly twice one provider running a full day. That's not a flaw; it's what paying for human attention looks like. It just means your documentation cost tracks your volume, which is exactly when you can least afford it.

An ambient AI scribe is software, priced per clinician per month. A packed day and a light day cost the same. AI Medical Scribe by Patient Square is $149 per clinician a month, or $119 a month on annual billing ([Patient Square pricing](https://patientsquare.com)). That number doesn't move whether you see 8 patients or 28. The full ladder, no asterisks, is on the [pricing page](../ai-medical-scribe-pricing/).

We think the flat shape is the quiet advantage here, more than the headline price. A human-scribe service that looks affordable at 12 visits a day gets expensive at 30, and your busiest clinicians are usually your highest-volume ones. Software that charges the same at any volume takes documentation cost off the table as a reason not to add a patient. For the full head-to-head on dollars, we did the math in [AI scribe vs human scribe cost](../ai-scribe-vs-human-scribe-cost/).

## What a human scribe catches that AI doesn't

This is where you have to be honest, and where a lot of AI-scribe marketing goes quiet. A person in the loop catches things software doesn't.

Three of them stand out:

**Ambiguity in the room.** You mumble a med name, or the patient talks over you, or you say "the usual" about a plan you both understand. A good human scribe fills that gap from context, or asks. An ambient AI drafts what it heard; if the audio was unclear, the draft is unclear, and you catch it on review instead of the scribe catching it live.

**Chart work while you talk.** A human scribe can pull up last visit's labs, find the imaging report, or start an order while you're still with the patient. That's real hands in the chart. An ambient AI writes the note and stops there. It doesn't navigate your EHR, because it isn't logged into it.

**Pushback.** An experienced scribe who hears a dose that sounds high, or a laterality that doesn't match the exam, sometimes flags it. That's a second brain in the room. An AI won't argue with your plan; it records it.

Being fair to the AI side, though: it's honest about what it isn't. Our scribe doesn't push back on your plan, and it doesn't run an automated interaction or dosing check on the prescription. The Rx it produces is a draft off what you said; you review the drugs, doses, and instructions and sign, exactly as you would with a paper script. The safety check is you, and we won't dress that up as something the software does for you. The ICD-10 codes are suggestions, not a coding engine, and they don't set your E/M level. On what to expect from the note's accuracy in plain terms, we wrote [AI scribe accuracy: what to expect](../ai-scribe-accuracy-what-to-expect/) without any percentages we can't back.

## Privacy: a third human on the line vs in-memory audio

Every visit with a remote human scribe has a third person listening. That's the model. For a lot of practices that's fine, and the scribe is under a BAA like any other business associate ([HHS, HIPAA](https://www.hhs.gov/hipaa/for-professionals/covered-entities/sample-business-associate-agreement-provisions/index.html)). But some patients get quieter when they know a stranger is on the call, and some visit types, behavioral health, sensitive histories, make a live listener a harder sell.

An ambient AI scribe removes the human from the line. No person hears the encounter. With AI Medical Scribe by Patient Square, the visit audio is processed in memory and discarded the moment the note drafts. Nothing is stored, not by us, not by your practice. What survives is the note you reviewed. The full posture is on our [security page](../../security/).

Both models still need the paperwork: a signed BAA, patient notice, the usual HIPAA hygiene. Software doesn't skip consent. The real difference is simpler than the legal language, whether there's a person in the room by headset. For some of your visits, removing that person is the point. For others it won't matter. You know your patient mix better than we do.

## Virtual human scribe vs ambient AI scribe, side by side

Here's the whole comparison in one place. Read the last two rows carefully, because that's where the human earns its cost.

| | Virtual (remote) human scribe | Ambient AI scribe (ours) |
|---|---|---|
| **When the note is written** | Live, during the visit | Drafted ~2 min after the visit |
| **Who's listening** | A remote person, every visit | No human; audio in memory, discarded at draft |
| **Cost shape** | Per-hour or per-visit staffing, scales with volume | Flat per-clinician software ($149/mo, $119 annual) |
| **Handles ambiguity in the room** | Yes, a person fills gaps or asks | Drafts what it heard; you fix on review |
| **Chart lookups while you talk** | Often, if the service includes it | No, writes the note only |
| **Pushback on a wrong dose or side** | Sometimes, a second brain | No; you review and sign the Rx draft yourself |
| **In-basket, orders, results chasing** | Yes, with many services | No, not its job |
| **Gets into the chart** | Via the person, in real time | You paste or export the note |

The pattern is clear once it's laid out. The AI wins on cost, privacy, and consistency; it never has a bad day, never calls in sick, never leaves for a new job. The human wins on everything that happens *around* the note, the ambiguity, the chart work, the tasks beyond documentation. Which column matters more depends entirely on what your scribe actually does all day.

## When a virtual human scribe is still the better fit

Here's the verdict without the hedging, because the honest one is the useful one.

Keep the virtual human scribe if the scribe does more than the note. If your remote scribe manages the in-basket, queues orders, chases labs and imaging, and navigates a genuinely complex chart while you work, that's delegation an ambient AI does not do. You're not really paying for documentation there. You're paying for a person to take work off your plate, and swapping in software that only writes notes would dump all of that back on you or your staff. Very high-complexity specialties with heavy chart-navigation demands are the clearest case: the note is the small part of what the scribe handles.

The mistake runs both ways. Buying an AI scribe to replace a human who was mostly writing notes is an easy win, cheaper, more private, flat cost. Buying an AI scribe to replace a human who was quietly running half your chart is how you end up doing that work yourself at 7pm. Before you switch, write down everything your current scribe touches. If it's the note and not much else, the AI covers it and you'll feel the cost drop fast. If it's the note plus a pile of chart work, price out who picks up the pile first.

If you do decide to move, the transition is smaller than a new EHR but not nothing. We put the steps in a [switch and migration checklist](../switch-ai-scribe-migration-checklist/), and for a small practice standing this up for the first time, [AI scribe implementation for a small clinic](../ai-scribe-implementation-small-clinic/) walks the setup. One product note so there's no confusion: AI Medical Scribe by Patient Square is standalone. It hands back the note, and you move it into your chart by copy-paste or export. There's no EHR write-back, no auto-filing, no e-prescribing, and the note comes back in English whatever language the visit happened in.

The cheapest way to settle this is on your own visits, not a table. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to see a note draft against your real visit type, then run the 7-day trial on a live clinic week. Compare it to what your human scribe actually delivers, note plus everything else, and let that decide it. If the scribe's job was the note, the AI does it for a flat fee and never quits in August. If it was more, you'll know that too.

---

## AI Medical Scribe for NextGen: A Buyer Test Plan
https://patientsquare.com/us/blog/ai-scribe-for-nextgen/
Published 2026-07-09 · Updated 2026-08-29 · Tags: ai-scribe, nextgen, ehr, workflow

Compare NextGen's ambient documentation options with a separate scribe using verified workflow, contract, security, and acceptance questions.

Yes. NextGen's June 2024 announcement describes NextGen Ambient Assist for NextGen Enterprise clients and NextGen Office Ambient Assist for small practices. It says generated documentation is delivered for clinician review, editing, and approval. Confirm current availability, plan scope, and terms with NextGen.

A NextGen practice already has a sensible first question: what ambient documentation option is available for the NextGen product we license? NextGen's June 2024 announcement describes NextGen Ambient Assist for NextGen Enterprise clients and NextGen Office Ambient Assist for small practices. It says generated documentation is delivered for clinician review, editing, and approval.

That first-party description gives you a baseline. A separate scribe should be compared against the actual NextGen option in your agreement, not against a generic description or a feature someone remembers from a demo.

Patient Square does not claim a NextGen integration. It does not promise to file a note into NextGen, write back to the chart, or sync in both directions. If a practice keeps NextGen or another existing EHR as its system of record, Patient Square remains alongside it and the practice must validate the record-transfer process.

> **Key takeaways**
>
> - Ask NextGen which ambient product is available for your licensed product and configuration.
> - Confirm current scope, price, implementation, support, and record placement in writing.
> - Patient Square makes no NextGen connector or automatic-filing claim.
> - EHR-ready export (PDF · HL7 · FHIR) does not guarantee import into a receiving EHR.
> - Test both routes with the same visits and require clinician approval of every draft.

## Establish the NextGen baseline

Use your account documentation and a current vendor demonstration. Product names alone are not enough because availability, packaging, configuration, and contract terms can change.

Ask NextGen to show the complete workflow for your environment:

1. Which NextGen product and version is required?
2. Where does the clinician start and stop capture?
3. Where does the generated draft appear?
4. What must the clinician review, edit, and approve?
5. Which note sections and visit types are supported?
6. What happens when the draft is incomplete or assigned to the wrong encounter?
7. Which implementation, training, and support work is included?
8. What is the total price, contract term, renewal rule, and exit process?

NextGen's public announcement supports the existence of the Enterprise and Office offerings and the clinician review step. It does not answer every practice-specific question above. Get those answers in the proposal or order form.

## Define the separate-scribe route accurately

AI Medical Scribe by Patient Square produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The draft is normally ready about two minutes after the visit. The clinician remains responsible for correcting and approving the clinical record, suggested codes, and prescription details. The prescription draft is not sent to a pharmacy.

A practice can use Patient Square EHR from the Copilot tier in Practice Copilot or keep its existing EHR alongside Patient Square. "Alongside" is the important word here. It does not mean Patient Square is installed in NextGen or that it can place a note in a NextGen chart.

Patient Square's public portability claim is **EHR-ready export (PDF · HL7 · FHIR)**. Confirm whether your receiving system accepts the format, version, resource or message, identifiers, and clinical fields you intend to use. An export option is not proof of a successful import.

## Compare the two workflows on the same cases

Use representative, consented visits. A useful set includes a routine follow-up, a medication change, a complex assessment and plan, and the note template your clinicians find hardest.

Score what happens after the conversation:

| Measure | What to record |
|---|---|
| Completeness | Material facts omitted from the history, assessment, or plan |
| Accuracy | Statements that require correction before approval |
| Review time | Minutes from draft availability to clinician approval |
| Record path | Exact steps required to place the final note in the correct chart |
| Medication safety | Errors in drug, dose, route, frequency, or instructions |
| Coding review | Suggested codes accepted, changed, or rejected by the clinician |
| Recovery | Steps required when capture, matching, export, or placement fails |

Do not award points for a claim the practice has not observed. Record the specific test, product version, date, and result so the team can repeat it.

## Compare commercial terms without guessing

NextGen can provide the current price and scope for the option tied to your account. Ask for the charge unit, commitment, included implementation, training, support, taxes, renewal terms, and cancellation or data-export rights.

Patient Square publishes its current US plans. Assist is a $79 per-clinician monthly equivalent on annual billing or $99 month to month. Copilot is $119 on the same annual-billing basis or $149 month to month. Autopilot is $199 on the annual-billing basis or $249 month to month. Each price is per clinician. The [pricing page](/us/pricing/) is the current source.

These figures are not comparable until you align scope. A native EHR feature and a separate clinical platform may include different products, services, and operational work. Put each quote into the same worksheet.

## Review privacy and failure handling

Ask both vendors where audio and notes are processed, what is retained, who can access records, which logs exist, and how deletion works. Have the practice's security or privacy lead review the actual contracts.

Patient Square says visit audio is processed in memory and discarded when the note is drafted. It says notes are encrypted in transit and at rest, a BAA is available to US customers, and visits can be exported or deleted. Confirm the current details on the [security page](/us/security/).

Also test a failure. Stop a capture early, use an ambiguous patient identifier in a non-production environment, and create a draft with a material correction. The team should know who notices, who fixes it, and where the final approval is recorded.

## Make the decision from your own workflow

The NextGen option may be the right route when it satisfies your clinical needs inside the product and contract you already use. A separate scribe may fit when its output, commercial terms, and alongside workflow pass your practice's tests. Neither conclusion should be assumed from the vendor name.

If you want to evaluate the Patient Square route, Request your 7-day trial. Test with an approved workflow, keep the existing EHR boundary explicit, and let the results decide.

---

## AI Scribe for Orthopedic Clinics in India: Faster Notes
https://patientsquare.com/in/blog/ai-scribe-for-orthopedic-clinics-india/
Published 2026-07-09 · Tags: specialty, ai-scribe, orthopedics

An ambient AI scribe for busy ortho OPDs, multilingual capture, clean English notes, ICD-10 suggestions. Per-doctor pricing from ₹1,599/mo + GST.

Yes. The scribe listens during the visit and drafts a structured SOAP note about two minutes after the patient leaves, so it keeps pace with a fracture-clinic queue. There's no per-note charge and no visit cap, so a packed ortho day costs the same as a light one: a flat per-doctor price from ₹1,599/mo annual plus GST. The busier your OPD, the more the flat pricing works in your favour.

For a busy orthopedic OPD in India, the scribe worth buying is the one that writes as fast as you see patients. AI Medical Scribe by Patient Square listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the patient leaves. It captures the consult in Hindi, Marathi, or a Hinglish mix and writes the note in clean English. Flat per-doctor price from [₹1,599/mo on annual billing](../../pricing/) plus 18% GST, unlimited visits, no per-note charge. Your busiest fracture-clinic day costs the same as a quiet one.

This is the ortho-specific case: why high-volume orthopedic clinics are a hard documentation problem, how ambient capture handles the mechanism-of-injury detail, what the scribe drafts, and where the EHR fits for follow-up-heavy cases.

> **Key takeaways**
>
> - Built for volume: a review-ready SOAP note about two minutes after each patient, so it keeps pace with an ortho queue.
> - Captures the consult conversation, including how the injury happened, into a structured note you review and sign.
> - Multilingual input, English output. Hindi, Marathi, Telugu, Hinglish in; clean clinical English notes out.
> - Flat per-doctor pricing from ₹1,599/mo annual (ex-GST). Unlimited visits, no per-note metering, no setup fee.
> - Scribe runs standalone; the bundled AI Copilot EHR (₹2,399/mo annual) is one tier up for connected follow-up records.

## Why is an orthopedic OPD hard to document?

Two things collide: throughput and detail. A fracture follow-up, then an acute knee injury, then a chronic low-back case, then a post-op review, each needs its own history and plan, and the queue doesn't slow down for any of them. In a 67-country study in BMJ Open, the average Indian consult ran about two minutes, among the shortest anywhere. In a packed ortho clinic it's often tighter.

Ortho notes also carry detail other specialties skip: the mechanism of injury, the exact site, the range of motion, the plan for immobilisation or physiotherapy. That's a lot to capture in two minutes while also examining a swollen joint. So the note gets written from memory later, or thinned out, and a thin ortho record is exactly the one you don't want if a case is ever disputed.

The scribe writes while you work instead of after. Book a demo and watch it draft an ortho note from a real consult.

## How ambient capture handles an ortho visit

The scribe listens during the consult and drafts the note the moment the patient leaves. It works off the actual conversation, so the details you say out loud, how the fall happened, which movement hurts, what you're advising, land in the note.

For orthopedics that's the point. When a patient explains a road-accident injury or a twist on the stairs, that mechanism is captured in the history section for you to confirm. The scribe structures the consult into a SOAP note, suggests ICD-10 codes, and drafts a prescription for the analgesic or anti-inflammatory you discussed. Specialty-aware templates ship out of the box, so the note comes back shaped like an ortho visit, not a blank generic form.

You review, tighten the clinical detail, and sign. The scribe does the typing; you keep the judgement. The Rx is a draft you check and sign, not an e-prescribing send button.

## Does it handle the languages an ortho OPD runs in?

Yes. A patient describes back pain in Hindi, names the painkiller in English, adds a Marathi phrase about how it started. Normal OPD sentence, and it trips up single-language tools.

The scribe listens in English, Hindi, and 20-plus Indian languages, including code-mixed Hinglish, and keeps up when the conversation switches mid-sentence. The note always comes out in clean clinical English. The flexibility is on input; your record stays consistent and readable. No half-Hindi note to clean up afterward.

## What does it cost for an orthopedic clinic in India?

Flat per-doctor, ex-GST, 18% shown once.

| Plan | What an ortho clinic gets | Monthly (annual billing) | With 18% GST |
|---|---|---|---|
| Assist | AI scribe, ICD-10 suggestions, eRx draft, scheduling | ₹1,599 | ₹1,887 |
| Copilot | Everything in Assist, plus bundled AI Copilot EHR + WhatsApp | ₹2,399 | ₹2,831 |
| Autopilot | Everything in Copilot, plus AI Receptionist, follow-ups, priority support | ₹3,999 | ₹4,719 |

The flat pricing suits a high-throughput specialty: no per-note billing, so a hundred-patient ortho day costs the same as a slow one. No setup fee, unlimited visits at every tier. [See the full ladder](../../pricing/). For a single-doctor ortho practice, [AI scribe for solo doctors in India](../ai-scribe-for-solo-doctors-india/) has the numbers for your size, and [scribe for doctors in India](../scribe-for-doctors-india/) covers the general case.

## When an AI scribe isn't the right fit for your ortho clinic

Straight talk on limits.

If your real problem is records, not writing, ortho is follow-up-heavy, so you may need history that connects across visits sooner than most, then the scribe alone (Assist) isn't the whole answer. That's what the bundled AI Copilot EHR at the Copilot tier is for. Be clear which you're buying: Assist is documentation, Copilot adds the record system.

If you need live ABDM or ABHA linkage today, know that ABDM integration is on our roadmap, not live. We don't claim a certification we don't have. You get records born digital and export-ready for the ABHA-linked era on your timeline. If live ABDM is a hard requirement now, verify every vendor's actual status.

If your footfall is light, the payback is smaller. The scribe earns its keep fastest in a busy OPD, which describes most ortho clinics in India.

## How to decide in a week

1. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, then run it on your busiest ortho session, real patients, real languages, real mechanism-of-injury histories.
2. Compare the note to how you'd chart it yourself. History, exam, plan, ICD-10 suggestions.
3. Test a Hindi or Hinglish consult on purpose and confirm the note comes out in clean English.
4. Time it from patient-leaves to signed note, and see if it holds pace with your queue.
5. Read the [security page](../../security/), audio handling, encryption, DPDP alignment, and the ABDM roadmap.

Book a short demo to see an ortho note drafted against your own visit type. For a high-volume orthopedic OPD, the scribe's value is simple: it writes at the speed you work, a clean, coded, defensible note about two minutes after each patient, in English, whatever language the consult happened in.

---

## Ambience Healthcare Pricing: The Real Cost in 2026
https://patientsquare.com/us/blog/ambience-healthcare-pricing/
Published 2026-07-09 · Updated 2026-08-27 · Tags: pricing, ai-scribe, ambience-healthcare, comparison

Ambience Healthcare publishes no price and sells enterprise-only. The real third-party estimates, plus a published $119 alternative with a bundled EHR.

Ambience publishes no price. It sells enterprise-only through a demo and sales process, with no pricing page and no self-serve signup. Third-party reviews estimate roughly $2,800 to $3,200 per provider per year for the base scribe, and $4,000 to $5,000 for the full AI suite, which is about $233 to $417 a month. Those are outside estimates, not Ambience figures.

Short version: Ambience Healthcare doesn't publish a price. There's no pricing page, no self-serve signup, and no small-practice tier, only "Book a demo." Third-party reviews estimate roughly **$2,800 to $5,000 per provider per year**, which works out to about **$233 to $417 a month**, and that buys a scribe, not an EHR. If you want a number you can read without a sales call, Patient Square lists it: **$119 per provider per month** on annual billing for an ambient scribe plus a bundled AI EHR. You can request an assisted 7-day trial; the seven days begin after setup.

None of this is an Ambience knock. It's a strong platform, well-funded, and clearly built for health systems. The point is the price, and the fact that a solo practice can't find it without entering an enterprise sales cycle.

> **Key takeaways**
>
> - Ambience publishes no per-provider price and sells enterprise-only through a demo.
> - Third-party estimates: ~$2,800–$3,200/provider/year (base scribe), $4,000–$5,000 (full suite), about $233–$417/month.
> - No free tier and no free trial; evaluation is enterprise-demo-only.
> - Ambience is a scribe that lives inside Epic, Cerner, and athenahealth; it isn't an EHR.
> - Patient Square publishes $79 (scribe) and $119 (scribe plus AI EHR), with a 7-day trial and no setup fee.

## What does Ambience Healthcare cost?

Ambience doesn't say. There's no pricing page on the site, no self-serve signup, and no listed tiers, just a demo request. One review sums it up plainly: you schedule a demo and start a full enterprise sales process to learn your number.

So the figures below come from third-party reviews, and they're estimates.

| Plan (third-party estimate) | Estimated cost per provider |
|---|---|
| AutoScribe base | $2,800–$3,200 / year (~$233–$267 / mo) |
| Full AI suite (CDI, AVS, Refer) | $4,000–$5,000 / year (~$333–$417 / mo) |
| Smaller orgs, no volume discount | ~$400–$500+ / month |

Those come from SOAP Note Buddy's 2026 review. Read them as directional. Ambience confirms none of them, and enterprise pricing usually bends with volume, contract length, and which modules you turn on. The one thing every source agrees on: there's no small figure and no self-serve door.

If you'd rather skip the estimate math, ours is published and starts at $79.

## Why can't you find Ambience's price?

Because Ambience sells to health systems, and enterprise software prices per deal, not per sticker. The company positions itself as an "AI platform for health systems," raised a **$243M Series C in July 2025 at a $1.25 billion valuation**, and supports inpatient, ED, and more than 100 ambulatory subspecialties. That's a company built to close large contracts, not to run a checkout.

That model makes sense for a 500-clinician system with a CMIO, a security review, and a procurement team. It's a poor fit for a three-doctor practice, which will get scoped as if it were a small hospital. The friction shows up before the product does: you can't even learn the price without a call.

We take the other view. A practice should be able to read the price before a call, request an assisted trial with a clear start point, and decide from real-workflow evidence. The full ladder is on our [pricing page](/us/pricing/), no asterisks.

## Ambience is a scribe, not an EHR: the bundle math

This is where the comparison shifts. Ambience documents the visit and writes into your existing chart. Its own funding announcement says it "integrates directly with Epic, Oracle Cerner, athenahealth, and other major EHRs." It doesn't give you the chart. So if you're pricing a practice, Ambience is one line item and your EHR is another.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing.

| | Ambience (estimated) | Patient Square |
|---|---|---|
| Ambient scribe | Yes | Yes |
| Bundled EHR | No (integrates with yours) | Yes, at Copilot ($119/mo annual) |
| Published price | No | Yes ($79 / $119 / $199) |
| Free trial | Enterprise demo only | 7-day trial |
| Setup fee | Enterprise onboarding | None |
| Target buyer | Health systems | Independent practices |

If you already run Epic and only want the note, Ambience or our Assist plan at $79 both fit that job. If you want to stop paying for two systems, the bundle is the cheaper path. See the note quality on your own visit type first.

## What you'd give up choosing a published-price scribe over Ambience

There's a real trade here. Ambience is engineered for enterprise scale: inpatient and ED coverage, a broad subspecialty catalog, and deep integration into the big EHRs, backed by serious funding. If you're a health system that needs the scribe embedded across your whole clinical footprint with enterprise support, that depth is exactly what you're paying for, and a self-serve tool isn't the same category.

You'd also trade a scoped enterprise rollout for a lighter, assisted practice setup. For an independent practice that can be a feature, not a loss. For a hospital, the enterprise process exists for good reasons.

What you keep with the published-price route is the daily part: a clean note in about two minutes, a visible rate, and an assisted trial that begins after the workspace is ready. For the wider enterprise-priced field, our [DeepScribe pricing](/us/blog/deepscribe-pricing/) breakdown and the [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup cover the other options.

## When Ambience is the better choice

Pick Ambience if you're a health system that wants ambient documentation across inpatient, ED, and dozens of ambulatory specialties, deployed inside Epic or Cerner with enterprise support and a contract that assumes scale. That's what the platform is built for, and it's what the funding is scaling. Switching to a self-serve tool to shave a seat price would cost you the system-wide reach you were buying.

Choose a published-price scribe if you're an independent practice that wants a note in two minutes, a price you can read, an assisted trial with a clear start point, and perhaps the record system in the same bill. That describes most of the practices reading this page.

## How to compare in a week

Skip the enterprise scoping and run the real test:

1. Ask Ambience for the all-in quote in writing, including which modules you'd actually use and the onboarding cost.
2. Decide whether you also need an EHR. If you do, add that vendor's price, then compare against a bundle.
3. Match the clinical output: note, ICD-10 suggestions, and a prescription draft, so you're comparing like for like.
4. Settle the audio question with every vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits. A scripted enterprise demo flatters every scribe equally.

The receipts behind our claims, encryption, access, and audit status, are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to check the note against your own visits, then run the 7-day trial on a real clinic week. When a vendor sells enterprise-only and won't publish a number, that's a signal about who they're built for.

---

## Ophthalmology EMR Software in India: What Eye Clinics Need
https://patientsquare.com/in/blog/ophthalmology-emr-software-india/
Published 2026-07-09 · Updated 2026-07-22 · Tags: ophthalmology-emr, eye-clinic-software, emr, india, buyers-guide

Compare ophthalmology EMR software in India for refraction records, IOL biometry, imaging, optical inventory, pricing, privacy, and AI notes.

Six things do the real work: a structured refraction and vision record (Sph, Cyl, Axis, VA), an IOL master with biometry capture for cataract planning, a way to attach ophthalmic images (OCT, fundus, topography, fields) to the record, optical-shop and lens inventory with GST billing, high-volume OPD queue plus OT scheduling, and DPDP-clean data handling. Generic clinic software covers the billing and appointments. The refraction chart and IOL master are where eye-specific software earns its keep.

An eye clinic does not document like a GP clinic. A refraction is not a symptom; it is a set of numbers per eye that has to be exact, and the cataract list runs on biometry the doctor read a week before surgery. Add the optical shop out front, the OCT and fundus prints stacking up in a folder, and a Tuesday OPD that clears sixty patients, and you get a workflow that generic clinic software was never shaped for. This guide covers what an eye clinic in India actually needs from its software, what "ophthalmology EMR" buys you over a general tool, how to read the word "integration" on an imaging line, what the prices look like, and where an AI documentation layer fits without pretending to be your whole system.

> **Key takeaways**
>
> - Six functions carry an eye clinic: a structured refraction record (Sph, Cyl, Axis, VA), an IOL master with biometry, image attachment for OCT and fundus and fields, optical-shop and lens inventory with GST, OPD queue plus OT scheduling, and DPDP-clean data handling. The refraction chart and the IOL master are the eye-specific parts.
> - Most India-native eye-EMR tools gate pricing behind a demo. Get the quote in writing, ex-GST, and pin down what one seat means.
> - "Integration" on an imaging line usually means attach-and-store, not a live device feed. Make the vendor demo it on your machine before you believe it.
> - Under the DPDP Act 2023 the clinic is the data fiduciary. Where serial images sit, how long they are kept, and how you get them back are legal questions now.

_Sources: Irving et al., BMJ Open 2017; MeitY, DPDP Act 2023._

If you already know your billing and appointments are fine and the drain is the note you type between patients, skip ahead and book a short demo to see where the documentation piece lands. Otherwise, start with what the software has to do.

## What does an eye clinic actually need from software?

Ignore the brochure feature count. Six functions do the real work in an ophthalmology practice, and if a tool nails these, the rest is garnish.

1. **A structured refraction and vision record.** This is the dividing line. Every visit produces Sph, Cyl, Axis, and add per eye, plus visual acuity, and those belong in fields you can compare against last year, not in a free-text box. A tool that makes you type "OD -2.25/-0.75 x 90" into a notes field loses the plot the moment you want to track a myope's progression.
2. **An IOL master with biometry capture.** Cataract is the volume surgery in most Indian eye clinics, and it runs on biometry: axial length, keratometry, the IOL power the formula gives you. The software should hold the biometry reading and the chosen lens against the surgery plan so the OT list is not a paper chit.
3. **Image attachment for the record.** OCT, fundus photography, corneal topography, visual fields. The clinic generates images constantly, and the record has to hold them against the eye and the date so the doctor can line up serial scans. Note the honest version of this below; "integration" is a slippery word.
4. **Optical-shop and lens inventory with GST.** The dispensing counter is a retail business bolted to a clinic: frames, lenses, contact lenses, solutions, each with stock and a GST invoice. This is inventory a GP clinic simply does not carry, and it is where eye-specific billing pulls its weight.
5. **OPD queue and OT scheduling.** A high-volume eye OPD needs a queue that survives sixty walk-ins, and the theatre needs a cataract list that ties back to each patient's biometry. Two different scheduling problems, both daily.
6. **DPDP-clean data handling.** Where the record lives, how long serial images are kept, and who can see them. Under the [DPDP Act 2023](../dpdp-act-clinics-guide/) this is a legal question, not an IT footnote.

Everything else, from teleconsult to loyalty schemes for the optical shop, is a real need for some clinics and noise for others. Decide which of the six you cannot live without, then treat the extras as tie-breakers. Our wider [EMR buyer's guide](../emr-software-india-guide/) walks the same sorting exercise for a general clinic.

## What makes ophthalmology software different from generic clinic software?

Plenty of clinic tools will sell you an "eye module," and some are usable. But two things separate software built for ophthalmology from software that merely tolerates it.

The first is the **refraction and IOL layer**. An eye-native tool treats the eye as the unit of work: two eyes, structured refraction, a biometry-fed IOL master that feeds the surgery plan. A generic OPD tool, even a good one, treats the visit as a consult with notes, so you end up shoehorning refraction numbers and lens powers into free text. You can make it work the way you can hammer a screw. The friction never goes away, and it compounds across a busy list.

The second is **the optical shop and image-heavy record**. Dentistry consumes stock per procedure; ophthalmology runs a dispensing counter and accumulates imaging over years. A generic clinic tool usually has a thin inventory bolt-on built for pharmacy stock, not for frames and lenses with their own GST lines, and it rarely gives the record a clean home for serial OCT and fundus images. If your clinic is mostly consults with the odd referral out, a generic tool with an eye veneer may be enough, and the [clinic management scorecard](../best-clinic-management-software-india/) is the right read for that. If refraction, cataract lists, and an optical counter are daily work, buy the eye-specific tool and stop fighting the form.

## What does "integration" with my OCT or biometry machine really mean?

Here is the line most buyers get burned on. A vendor page says "integrates with imaging devices," and a clinic hears "the software talks to my OCT live." Usually it does not.

In practice, "integration" for India-native ophthalmology EMR tools most often means you can **attach and store** the image or the printout against the patient's record, sometimes by upload, sometimes by pulling from a shared folder the device writes to. That is genuinely useful. It keeps the scan with the eye and the date, and it is what most clinics actually need day to day. But it is not the same as a live device feed that reads structured data straight off the machine, and it is a much smaller claim than a full DICOM or device link.

So put the question plainly, and get it demonstrated on your own machine, not a slide:

- Does the software read a live feed from the device, or do we attach the image and printout?
- Which exact device models and firmware are supported?
- If we buy a new OCT next year, does the link still hold, or is it a fresh integration project?
- Who owns the link when it breaks: the software vendor, or the device vendor?

A vendor that can show attach-and-store working on your topographer today is being honest. A vendor that says "yes, full integration" without naming your device model is selling the word, not the feature. To be clear on our own scope: our documentation layer does not claim device integration of any kind. It drafts the note; it does not read your OCT.

## What does ophthalmology EMR software cost in India?

Here is the part most listicles skip: the India-native eye-EMR vendors mostly do not publish a price. That is not a scandal; it is how mid-market Indian clinic software is often sold, demo-led, with the number flexing on how hard you negotiate and how many chairs you have.

| | India-native ophthalmology EMR | Generic clinic tool with eye module | Practice Copilot: Patient Square EHR or existing-EHR path |
|---|---|---|---|
| **Built for** | Eye clinics, refraction to OT | General clinic, eye bolt-on | AI clinical workflows; refraction, imaging, and optical-shop modules remain specialist scope |
| **Structured refraction / IOL master** | Yes | Varies, often free-text | No (not its job) |
| **Image attachment (OCT, fundus, fields)** | Attach-and-store, ask about device feed | Usually generic file upload | No |
| **Optical-shop / lens inventory** | Yes, with GST | Pharmacy-style stock at best | No |
| **Published price** | Usually demo-gated, no rupee figure | Varies | ₹1,999/mo; ₹1,599/mo annual (Assist), ex-GST |
| **ABDM** | Ask which milestone, is it live | Ask which milestone | On the roadmap, not shipped |
| **Trial** | Varies | Varies | assisted 7-day |

Where a cell says "ask," the vendor's public material did not name a specific status, so confirm it before you buy. When a rupee figure does surface for these eye-EMR tools, it tends to land in the low thousands per doctor a month before the 18% GST on software subscriptions ([CBIC / GST](https://cbic-gst.gov.in/)). Do not anchor on a number a reseller quotes over the phone. Anchor on the written quote with GST spelled out. The one practical rule: get it in writing, ex-GST, and pin down whether a seat is a doctor, a chair, or a location, because "₹X per month" means very different things depending on the answer.

## How does the DPDP Act change an eye-clinic software purchase?

More than most eye surgeons realise, and the imaging is exactly why. Under the [DPDP Act 2023](../dpdp-act-clinics-guide/), the clinic is the **data fiduciary** for its patients' data ([MeitY](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf)). That is a legal role, and it comes with duties you cannot hand to the software vendor.

Three of those duties bite on the software choice, and an eye clinic feels them harder because it holds so much imaging over so long:

- **Purpose limitation.** You collect and use patient data only for the purpose the patient consented to, treatment, and not for anything outside the notice you gave. A vendor that quietly repurposes your patient list for marketing creates a liability that lands on you.
- **Storage limitation.** Data is kept only as long as the purpose needs it. An eye clinic naturally wants serial OCT and fundus images held for years to track progression, which is clinically sound, but it means you need a deliberate retention policy, not a vendor that keeps everything forever "just in case."
- **Where the data physically sits.** Cloud eye-clinic software puts records and images on someone else's servers. Ask where, ask how it is protected, and ask how you get it back if you stop paying.

Two clean questions for any vendor: *where does our data live, and how do we get it and the images back if we leave?* A tool that cannot answer both crisply will make your DPDP compliance harder. This is not a reason to fear cloud software. It is a reason to buy it with your eyes open.

## Where does AI documentation fit in an eye clinic?

In the consult note, and only there. This is where an ambient layer earns its place without pretending to be your clinic system.

An eye consult still produces a written record: the complaint, the findings, the plan, the follow-up. Typing that between patients on a sixty-patient day is where evenings quietly go. An ambient documentation layer listens during the visit and drafts that note, which the doctor then reviews, edits, and signs. It does not touch the refraction chart, the IOL master, the optical-shop billing, or the imaging. It sits on top of whatever EMR you run and hands back a draft, faster than typing from memory after the patient has left.

A few design points matter for an Indian eye clinic specifically. Consults happen in braided Hindi and English, so the layer takes code-mixed speech on input and returns the note in clean clinical English. The visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner posture under the DPDP Act. Any prescription it suggests is a draft to check, not an order it sends, and any diagnosis code it offers is a suggestion, not a final code. The output is always a **draft**: the doctor signs it, the software never signs for you. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That layer is [Practice Copilot](/in/products/practice-copilot/), our AI bundle for Indian clinics, with the ambient documentation module doing the note-taking. We publish our prices rather than gating them: the Assist plan is ₹1,999 per clinician a month, or ₹1,599 on annual billing, all ex-GST, with a 7-day free trial through the India signup page. At the monthly price, the with-GST math is ₹1,999 plus 18% GST, so about ₹2,359 a month; on annual billing ₹1,599 works out to about ₹1,887 with GST. Copilot and Autopilot add the bundled AI Copilot EHR, messaging, and higher-tier modules above that. We are candid about scope too. ABDM integration is on our roadmap, not shipped, and we will not badge a status we do not hold. If the documentation drain is what you feel most, the [scribe guide for Indian doctors](../scribe-for-doctors-india/) covers where that fits alongside your EMR.

The buying advice we would give a friend who runs an eye clinic: pick your ophthalmology EMR on the refraction record, the IOL master, and the optical-shop inventory, then decide separately whether the note is eating your evenings. If it is, add a documentation layer on top rather than ripping out a system that already handles your charts and imaging. Book a short demo and watch where a real consult lands as a note before you commit to anything.

_Sources: MeitY, DPDP Act 2023; NHA / ABDM portal; CBIC / GST; Irving et al., BMJ Open 2017._

---

## athenahealth EHR Cost: The Percentage-of-Collections Math
https://patientsquare.com/us/blog/athenahealth-ehr-cost/
Published 2026-07-08 · Updated 2026-08-27 · Tags: pricing, ehr, athenahealth, comparison

athenahealth prices as a percentage of collections, so your EHR bill grows with revenue. The real cost model, the switching friction, and a flat $119 bundle.

athenahealth prices as a percentage of what you collect, not a flat per-seat fee. Third-party sources cite roughly 4% to 8% of monthly collections, most independent practices landing at 5% to 7%. Estimated per-provider equivalents run near $140 a month, but athenahealth publishes no seat price, so every dollar figure is an outside estimate. Your real cost rises as your revenue rises.

Short version: athenahealth doesn't charge a flat per-seat price. It bills a **percentage of what you collect**, which third-party sources put at roughly **4% to 8% of collections**, so your EHR cost climbs as your practice earns more. On top of that, the ambient scribe isn't built in; athenahealth integrates partners like Abridge and Suki that bill separately. If you want a flat number that doesn't move with your revenue, Patient Square's Copilot plan is **$119 per provider per month** annually with the scribe and an AI EHR bundled. You can see it on a real visit before you switch.

This isn't an athenahealth takedown. It's a top-three ambulatory EHR with a real revenue-cycle engine, on a network of 170,000-plus clinicians. The point is the cost model, because a percentage of collections behaves very differently from a flat bill, and most practices don't run the math until they're in it.

> **Key takeaways**
>
> - athenahealth prices as a percentage of collections; third-party sources cite roughly 4% to 8%, with most independents at 5% to 7%.
> - Your bill scales with revenue: a high-collecting practice pays more for the same software.
> - Contract friction is real: third parties report multi-year terms, auto-renewal, and $50,000 to $90,000 termination penalties; athenahealth counters that you can leave anytime.
> - The ambient scribe isn't native; athenahealth integrates Abridge, Suki, iScribe, and Dragon Copilot, all billed separately.
> - Patient Square Copilot is a flat $119 per provider per month, scribe and AI EHR bundled, no collections percentage.

## What does athenahealth actually cost?

athenahealth doesn't publish a per-provider price. Its own cost-and-value page says the pricing model "corresponds to your organization's collections," charged through athenaCollector, its revenue-cycle platform. So the cost isn't a seat fee. It's a cut of what you bring in.

Third-party sources put that cut in a range.

| Pricing detail (third-party estimate) | Figure |
|---|---|
| Percentage of collections | ~4%–8% (most independents 5%–7%) |
| Per-provider equivalent | ~$140 / month (widely cited) |
| Implementation | $2,000–$5,000 per provider |
| Data migration | $500–$10,000 |

Everything in that table except the model itself is an outside estimate. athenahealth confirms the collections-based model on its own site; it does not confirm the percentages or the dollar figures. Sources cite the 4% to 8% range and the roughly $140-per-month equivalent, but your real number depends on your collections, your module mix, and what you negotiate.

The mechanics matter more than the exact percent. Because the fee tracks your revenue, a growing practice pays a growing bill for the same software. That aligns athenahealth's incentives with your billing, which is the pitch. It also means you can't lock your software cost, because it moves every month with your collections. A flat plan doesn't.

## Why a percentage of collections is a different kind of bill

Think about two practices running the same athenahealth setup. One collects $80,000 a month, the other $200,000. At the same percentage, the second practice pays more than twice as much for identical software. Nothing about the product changed. Only the revenue did.

That's the trade-off with collections-based pricing. When you're small, the bill is small, which is genuinely helpful for a new practice. As you grow, the percentage keeps taking its slice, and the software gets more expensive precisely because you're doing better. A flat per-provider price behaves the opposite way: it's the same in a strong month and a slow one, so you can budget it and forget it.

Neither model is dishonest. They just suit different practices. If your collections are lumpy or climbing, the percentage is a moving target. Our [pricing page](/us/pricing/) lists a fixed number instead.

## The switching cost nobody quotes you

Here's the part that gets buried. athenahealth's own page says customers can "leave at any time and take all your data." Third-party sources tell a different story: multi-year initial terms, automatic renewal, advance-notice cancellation requirements, and reported termination penalties of **$50,000 to $90,000 or more** depending on contract size.

Both claims are out there, so we're citing both rather than pretending one settles it. The honest takeaway: read the term, the renewal clause, and the cancellation notice before you sign, and treat the cost of leaving as part of the cost of joining. A big EHR is a big commitment, and the exit is where the friction lives. That's true of athenahealth and true of most enterprise EHRs.

A practice-sized plan sidesteps that by design. There's an assisted 7-day trial after workspace setup, a published price, and no multi-year term to unwind if it isn't a fit.

## athenahealth vs a flat bundle: the total-cost view

Let's compare like for like. athenahealth is a full revenue-cycle platform. Patient Square isn't, and we'll be clear about that.

| | athenahealth (estimated) | Patient Square Copilot |
|---|---|---|
| Pricing model | % of collections (~4%–8%) | Flat $119/provider/mo (annual) |
| Cost as you grow | Rises with revenue | Fixed |
| Ambient scribe | Partner add-on (Abridge, Suki, others) | Bundled, unlimited |
| Bundled AI EHR | Yes (full platform) | Yes |
| Revenue-cycle depth | Deep (athenaCollector) | ICD-10 suggestions, not an RCM engine |
| Contract | Multi-year terms reported | Month-to-month or annual, 7-day trial |
| Published price | No | Yes |

Read that honestly. If deep revenue-cycle management runs your practice, athenaCollector is a real reason to choose athenahealth, and a flat bundle can't match it. What Patient Square gives you instead is one predictable bill for the two things most independent practices touch every day: writing the note and keeping the record.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. Put it in front of your own visit type and judge the note.

## What you give up leaving athenahealth

Be clear-eyed about the trade. athenahealth isn't priced high by accident.

- **A mature revenue-cycle engine.** athenaCollector handles claims, denials, and payment posting at scale across a huge network. Patient Square offers ICD-10 *suggestions* to speed coding, not a claims-scrubbing platform.
- **Network scale.** 170,000-plus clinicians, more than 315 million claims a year, and rules-engine intelligence built from that volume. If you lean on that, weigh it.
- **A wide module catalog.** Population health, patient engagement, and a long tail of integrations. Heavy users of those should factor it in.

Patient Square's export claim is precise: **EHR-ready export (PDF, HL7, FHIR)**. That's a clean export, not a certified interoperability engine. If your practice depends on deep bidirectional feeds today, keep that in mind. For a broader look, our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup and the [eClinicalWorks cost](/us/blog/eclinicalworks-cost/) breakdown cover the other end of the market.

## When athenahealth is the better choice

Stay with athenahealth, or pick it, if billing runs your practice. If you need a deep RCM engine, complex claims workflows, and a platform that scales across many providers with enterprise support, athenahealth earns its cost, and the collections model can even help while you're small. A flat scribe-plus-EHR bundle isn't competing at that level, and switching to save on price would cost you more in lost billing capability than you'd save.

Choose a flat bundle if your day is mostly visits and notes, you want the scribe and the record in one predictable bill, and you'd rather your software cost not climb every time your collections do. That describes a lot of independent primary-care and specialty practices. If you're actively planning a move, our [switch from athenahealth](/us/blog/switch-from-athenahealth/) guide walks the migration.

## How to price your real athenahealth cost in an afternoon

Skip the marketing math and build your own number:

1. Take your average monthly collections and multiply by the percentage in your quote. Use a strong month, not a slow one, so you see the ceiling.
2. Add the partner scribe cost (Abridge, Suki, or another), since it's separate.
3. Add implementation and migration as one-time costs, amortized over year one.
4. Read the contract term and the termination clause. Price the exit.
5. Compare that total against a flat $119 per provider annually with the scribe and EHR included, then trial it on a real week.

The receipts behind our claims, encryption, access, and audit status, are on the [security page](/us/security/), and the fixed price ladder is on the [pricing page](/us/pricing/). Book a short demo to check the note against your own visits, then run the 7-day trial on a real clinic week. For many independent practices, a bill that doesn't grow with your revenue is the whole point.

---

## Augmedix Alternatives: Fully Ambient, No Contract Minimums
https://patientsquare.com/us/blog/augmedix-alternatives/
Published 2026-07-08 · Updated 2026-07-22 · Tags: ai-scribe, comparison, augmedix, pricing

Augmedix is part of Commure and sold through sales. Compare it with published-price ambient scribes from $79 and a bundled AI EHR from $119.

Augmedix is sales-led and publishes no self-serve per-provider price. Its roots are human-assisted scribing, historically listed by third parties at roughly $1,200 to $2,000 per provider per month, and it's now part of Commure's platform, which lists a broad range across products. Those are outside figures. Patient Square publishes $79/mo for the scribe and $119/mo for the plan with a bundled AI EHR.

Augmedix started as human-assisted scribing, added ambient AI, and is now part of Commure. If you're shopping for a scribe today, that lineage means a managed, sales-led model with no self-serve price. The alternative worth naming is fully ambient AI with no contract minimums and a number you can read. Patient Square's scribe is $79 per clinician per month on annual billing, unlimited notes, with a bundled AI EHR from $119/mo at the Copilot tier. The note drafts the moment the visit ends, no human scribe in the loop. See the ladder on our [pricing page](../../pricing/), or book a demo.

This isn't an Augmedix knock. It's a fit question. Below: how the human-assisted lineage shapes the buy, a side-by-side, and when the managed model is the right call.

> **Key takeaways**
>
> - Augmedix grew from human-assisted remote scribing, historically listed by third parties near $1,200 to $2,000 per provider per month, and is now folded into Commure after a 2024 deal valued around $139M.
> - Augmedix is sales-led with no self-serve per-provider price. Patient Square publishes $79 / $119 / $199 per clinician per month, annual.
> - Patient Square is fully ambient AI: the note drafts the moment the visit ends, no human scribe, no per-hour scribe billing, no contract minimum.
> - The Copilot tier bundles an AI EHR from $119/mo, so the note lands in a chart.
> - When you want a managed or human-assisted service, Augmedix's model fits. We say so below.

## How does Augmedix compare to Patient Square?

Here's the side-by-side. Augmedix's price is a third-party or historical figure, because it's sales-led and now consolidating into Commure.

| | Augmedix | Patient Square |
|---|---|---|
| Model | Human-assisted lineage plus ambient AI | Fully ambient AI, no human in the loop |
| Published price | No; sales-led, now via Commure | Yes. $79 / $119 / $199 per clinician/mo, annual |
| Historical price | ~$1,200–$2,000/provider/mo (third-party, scribe service) | $79/mo (Assist) |
| Contract minimums | Common in managed-scribe models | None; 7-day trial, month or annual |
| Bundled EHR | Part of the broader Commure platform | Yes, AI Copilot EHR from $119/mo |
| Best fit | Managed or enterprise documentation service | Small practices wanting published-price ambient AI |

If you're an independent practice, book a demo and see fully ambient AI on your own visits before committing to a managed service.

## How does the human-assisted lineage shape the buy?

Augmedix built its business on remote human scribes, then layered ambient AI on top. That history matters when you buy. Managed-scribe models tend to come with contract minimums, per-hour or per-provider service billing, and an onboarding process, because there's a service operation behind the product, not just software. Historically, third-party listings put Augmedix's scribe service near $1,200 to $2,000 per provider per month, which reflects a staffed model, not a self-serve app. Treat that as a historical, outside figure, not a current quote.

The 2024 Commure acquisition, valued around $139 million, folds Augmedix into a broader healthcare AI platform. Practically, that means the standalone product and its price are consolidating, and increasingly what you buy runs through Commure's sales motion.

Patient Square is the other model entirely. It's fully ambient AI, no human scribe in the loop, no per-hour billing, no contract minimum. The note drafts after the visit ends. You can read all three prices on the [pricing page](../../pricing/) before speaking with anyone, then request an assisted 7-day trial; the trial begins after the workspace is ready.

## What do you keep, and what do you give up?

The trade is service versus software.

You give up the managed, human-assisted layer. If you value having a service operation behind your documentation, a fully ambient tool doesn't replicate that. It's software you run yourself, and the note is yours to review and sign.

What you keep is speed and simplicity. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. No scribe to schedule, no minimum to hit. At the Copilot tier, a bundled AI Copilot EHR comes with it from $119/mo, so the note lands in a chart. Audio is processed in memory and discarded once the note drafts, so no recording is kept. A BAA is available for every customer.

If you're comparing more scribes, [Ambience Healthcare alternatives](../ambience-healthcare-alternatives/) covers the health-system platform, and [DeepScribe alternatives](../deepscribe-alternatives/) covers another sales-led enterprise scribe.

## When is Augmedix the better choice?

It comes down to whether you want a service or a self-serve tool.

Choose Augmedix, or the Commure platform it now lives in, if you specifically want a human-assisted or enterprise-managed documentation service, or you're standardizing a large group on Commure's broader stack. That managed model is what the lineage is built for, and a self-serve app doesn't replace a staffed service.

Choose a fully ambient, practice-sized scribe if you're an independent practice or small group that wants a clean note in about two minutes, no contract minimum, a price you can read now, and a short assisted setup before a trial on real visits. That describes most of the practices reading this page. And if you want the chart bundled in, that's the Copilot tier.

## How to decide in a week

Run the real test.

1. Decide whether you want a managed service or self-serve software. That's the fork, and it changes everything downstream.
2. If self-serve, shortlist fully ambient tools with published prices and no contract minimum.
3. Match the clinical output: note plus ICD-10 suggestions plus a prescription draft, like for like.
4. Ask about minimums and billing units. Per-hour or per-provider service billing behaves differently from a flat published seat price.
5. Settle the audio question: stored or not, and for how long. Ours is never stored.

The receipts behind our claims are on the [security page](../../security/), and the price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visit type, then request the assisted 7-day trial for a real clinic week. If you want a managed service, Augmedix's model fits. If you would rather evaluate practice-sized ambient AI at a published price, that is what you are shopping for.

---

## Augnito Alternatives in India: Dictation vs Ambient (2026)
https://patientsquare.com/in/blog/augnito-alternatives-india/
Published 2026-07-08 · Updated 2026-08-27 · Tags: alternatives, comparison, augnito, pricing

Augnito Spectra is medical dictation you drive by voice. Compare it with ambient scribing that writes the SOAP note for you, from ₹1,599/mo per doctor.

Fast, accurate medical dictation. Augnito Spectra is speech-to-text you drive by voice: you speak your report and voice commands, and it types into a Smart Editor or straight into Word, your HIS, or a PACS/RIS. It supports 50-plus specialties and recognises many English accents with no voice training. For radiology and pathology reporting, where a doctor wants to narrate a full structured report, that's a strong fit.

If you're weighing Augnito, decide one thing first: do you want to dictate, or do you want to stop dictating? Augnito Spectra is medical speech-to-text you drive with your voice, you narrate the report and it types. Patient Square is ambient, it listens to the consultation and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the patient leaves, no narration step at all. Augnito's price is quote-gated behind a demo form. Patient Square publishes it: Practice Copilot from ₹1,599/mo per doctor, the bundled AI EHR from ₹2,399/mo (ex-GST, so with 18% GST that's about ₹1,887 and ₹2,831). You can book a demo and watch a note write itself on a real visit.

This isn't a takedown. Augnito is a serious, established Indian medical-speech company. It's a fit question: some doctors genuinely want to dictate, and for them Augnito is a good answer. Below is where each model wins.

> **Bottom line**
>
> - Augnito Spectra = dictation you drive (speak the report, it types). Patient Square = ambient capture (it listens, you don't narrate).
> - Augnito has an ambient product too (Omni), but it's a separate, enterprise-facing offering, and both are quote-gated.
> - Patient Square publishes per-doctor pricing: ₹1,599/mo entry, ₹2,399/mo with a bundled AI EHR. Augnito routes you to a sales quote.
> - Third-party estimates put Augnito near ₹4,000-16,000/user/mo equivalent, but that's an outside guess, not their rate card.

## Augnito vs Patient Square: dictation or ambient?

The split is the model, not the accuracy. Read the row that matches how you want to work.

| | Augnito (Spectra) | Patient Square |
|---|---|---|
| Built for | Doctors who want to dictate reports by voice | Doctors who want the note written for them |
| What it does | Speech-to-text you drive: narrate + voice commands | Ambient capture: it listens, no narration |
| Output | Text you dictated, into Smart Editor / Word / HIS / PACS | Structured SOAP note, drafted for you |
| ICD-10 | Coding in the separate Omni product | Suggestions only (never a coding engine) |
| Prescription | You dictate it | Draft, ready for you to check |
| Languages | Dictate in English, many accents supported | Speak English, Hindi, 20+ Indian languages; English note out |
| Pricing | Quote-only, demo form | Published per doctor: ₹1,599 / ₹2,399 / ₹3,999 |
| Implementation | Scoped, EMR integration | None for clinics; sign up and consult |

Want to narrate a radiology report in your own words? Augnito's your tool. Want to finish a 30-patient OPD without touching the keyboard? Keep reading.

## What Augnito Spectra is genuinely good at

Credit where it's due. Augnito Spectra is a mature medical speech-to-text engine. You speak your report at your own pace, use voice commands to format and correct, and it types into its Smart Editor or straight into Word, your HIS, or a radiology PACS/RIS. It covers 50-plus specialties and sub-specialties and recognises a range of English accents without a training step. Scribetech, the company behind it, has years of NHS transcription heritage, so this is battle-tested plumbing, not a weekend project.

For a radiologist reading twenty scans, or a pathologist narrating a structured report, dictation is the right shape. You're already composing the report in your head; you just want it on the page faster than typing. Spectra does that well, and I'd point a reporting-heavy specialist at it before pointing them at an ambient tool.

The mismatch shows up somewhere else: the crowded OPD. In a 8pm Pune clinic with fourteen patients still waiting, you don't want to narrate a report between consults. You want the note already done when the patient stands up. That's a different job, and dictation, however fast, still asks you to stop and compose.

## What does Augnito cost in India, and why isn't it published?

Augnito doesn't put a number on the page. Both Spectra and the ambient product route you to a demo-and-quote form, because the price genuinely tracks user count, EMR integration work, and which specialty modules you switch on. That's normal for clinical software sold into hospitals. It also means a scoping call before you know your figure.

Third-party listings estimate Augnito somewhere around 50 to 200 US dollars per user per month, roughly ₹4,000 to ₹16,000 at current rates. Treat that as an outside estimate, not a quote, the real number comes from their sales team and can sit well above or below that band depending on your setup. For a large hospital, scoping is fine. For a solo doctor who just wants notes done, entering an enterprise quote cycle to solve a documentation problem is a lot of friction.

Patient Square prices for the doctor buying it directly. Practice Copilot is per doctor: Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp), Autopilot ₹3,999/mo, all ex-GST, add 18%. It's on the [pricing page](https://patientsquare.com/in/pricing), no form required. If you're comparing what a scribe costs a solo doctor, the [AI scribe cost breakdown for solo doctors](https://patientsquare.com/in/blog/ai-scribe-cost-for-solo-doctor-india) walks the maths.

## Dictation vs ambient: what actually changes at the desk

Here's the difference in plain workflow terms, per visit.

| Step | Dictation (Spectra) | Ambient (Patient Square) |
|---|---|---|
| During the visit | You consult, then narrate | You just consult |
| Writing the note | You speak the report aloud | The scribe drafts it from the conversation |
| Your effort after | Review + fix dictation errors | Review a ready SOAP note |
| Coding | Dictate, or use Omni's coder | ICD-10 suggestions surfaced for you |
| Prescription | You dictate each line | Draft ready to check |
| Time to a finished note | Depends on how fast you narrate | About two minutes, drafted for you |

Dictation moves the typing off your hands but keeps the composing on your shoulders. You still decide every sentence and say it out loud. Ambient removes the composing step too: the note is drafted from what you and the patient actually said, and you switch from author to editor. For a doctor drowning in charting after clinic hours, that shift, author to editor, is the whole point.

Patient Square's canonical shape: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Book a demo and run it on your own visit type.

## What every Patient Square plan includes

No matter which tier, every plan includes: unlimited visits and notes with no per-note metering, EHR-ready export (PDF, HL7, FHIR), specialty-aware templates ready out of the box, and capture on web or mobile. The scribe listens in Hindi, Kannada, Bengali, Tamil, and 20-plus Indian languages, even Hinglish, and always returns a clean clinical English note, so a colleague or a referral reads the same standardised record every time. Audio is processed in memory and discarded once the note drafts, nothing sits in a recording bucket, and offline capture is encrypted with AES-256-GCM. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On compliance, straight talk: data is handled to DPDP Act 2023 standards, the SOC 2 Type II audit is in progress (not certified yet), and ABDM integration is on the roadmap, not live. Records are born digital, ready for the ABHA-linked era on your timeline. If any vendor claims live, certified ABDM today, ask for the NHA certificate before you sign.

## When Augnito is the better choice

Choose Augnito if you want to dictate. If you're a radiologist, pathologist, or any reporting-heavy specialist who composes a full structured report in your head and just wants it on the page fast, Spectra's speech-to-text is purpose-built for exactly that, and its accent handling and specialty vocabulary are strong. A hospital that already runs a dictation workflow across PACS/RIS and wants to standardise on one voice engine also has a real reason to pick Augnito, and to look at Omni if it wants an ambient layer under the same vendor.

Choose Patient Square if the pain is charting time, not typing speed. An OPD doctor seeing thirty patients on a Tuesday doesn't want a faster way to narrate reports; they want to not narrate at all. Ambient capture drafts the note from the conversation and hands it back in about two minutes, in clean English whatever language you consulted in, at a published per-doctor price with no scoping call. If you're a clinic comparing the broader field, the [DocOnline](https://patientsquare.com/in/blog/doconline-alternatives-india) and [Halemind](https://patientsquare.com/in/blog/halemind-alternatives-india) alternative breakdowns cover adjacent options.

## How to decide this week

Skip the feature-sheet standoff and run the test:

1. Say which you want out loud: do I want to dictate reports, or stop composing notes? That answer picks your category before any demo.
2. If dictation, trial Augnito Spectra on your real reports and check accent and specialty vocabulary on your worst-case cases.
3. If ambient, trial Patient Square on a real OPD, Hindi or Kannada in, clean English note out, and time how long the finished note actually takes.
4. Match the clinical output like for like: a structured note, ICD-10 suggestions, and a checked prescription draft, and be honest about which coding claims are suggestions versus a real coding engine (Patient Square's are suggestions, and it says so).
5. Settle the money question up front. Get Augnito's real quote, don't rely on the third-party estimate, and put it next to Patient Square's published ₹1,599 / ₹2,399 / ₹3,999 ladder.

The per-doctor prices sit on the [pricing page](https://patientsquare.com/in/pricing), and you can book a short demo to check note quality on your own visit type. If you want to dictate, Augnito earns the look. If you want the note written for you, you're in the right place.

---

## Augnito Price vs AI Scribe in India: What Each Really Costs
https://patientsquare.com/in/blog/augnito-price-vs-ai-scribe-india/
Published 2026-07-08 · Updated 2026-08-29 · Tags: pricing, comparison, augnito, ai-scribe

Compare a dated Augnito quote with an ambient AI scribe. Dictation and ambient note review are different workflows.

Augnito's web pricing route redirected to contact sales when checked in August 2026. Its India App Store listing shows ₹1,199, ₹3,299, and ₹11,900 in-app purchases, but it does not label their billing periods. Ask for a dated quote instead of inferring a billing cycle from those amounts.

If you're pricing Augnito against an AI scribe, start with the honest gap: Augnito's web pricing route redirects to contact sales. Its India App Store listing shows ₹1,199, ₹3,299, and ₹11,900 purchases without billing periods. A useful comparison starts with a dated quote, not an inferred subscription. Patient Square publishes Assist at ₹1,599 per doctor per month on annual billing, plus GST, with unlimited visits and notes.

But price isn't the real story here, because these two tools do different jobs. Augnito is dictation you drive. An ambient scribe drafts the whole note from the conversation. Line up what each costs and what each does, then decide which one your day actually needs.

> **Key takeaways**
>
> - Augnito's web route redirects to contact sales, and its visible App Store purchases have no stated billing period.
> - Patient Square publishes ₹1,599 per doctor per month (Assist, annual, ex-GST), unlimited notes, no per-line metering.
> - Augnito's material describes dictation into text. Patient Square's ambient scribe provides a structured SOAP note, ICD-10 suggestions, and a prescription draft for review.
> - Dictation can fit doctors who prefer word-for-word control.

## What does Augnito actually cost?

The web pricing route redirects to a contact-sales form. The India App Store listing shows ₹1,199, ₹3,299, and ₹11,900 purchases, but none has a billing period. Those are purchase amounts, not monthly, quarterly, or annual prices. Ask Augnito for a dated written quote that names the product, usage unit, GST, term, support, and exit terms. If you want a wider comparison, see [Augnito alternatives](/in/blog/augnito-alternatives-india/).

For an ambient-workflow trial, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> and use the same scorecard on real visits.

## How is the ambient scribe priced instead?

Published, flat, and unlimited. Patient Square's Assist plan is ₹1,599 per doctor per month on annual billing, plus GST. Copilot is ₹2,399 and Autopilot is ₹3,999, also monthly equivalents on annual billing. All plans include unlimited visits and notes, with no per-note metering or setup fee. The bundled AI EHR starts at Copilot.

| Plan | Price (annual, per doctor, ex-GST) | With 18% GST | What you get |
|---|---|---|---|
| Assist | ₹1,599/mo | ₹1,887/mo | AI Medical Scribe, ICD-10 suggestions, prescription drafts, scheduling |
| Copilot | ₹2,399/mo | ₹2,831/mo | Everything in Assist, plus bundled AI Copilot EHR and WhatsApp |
| Autopilot | ₹3,999/mo | ₹4,719/mo | Everything in Copilot, plus AI Receptionist, follow-ups, analytics |

On the number Patient Square publishes, the scribe is a known cost you can budget. Whether Augnito's quote lands above or below ₹1,599 depends entirely on what you negotiate, and you won't know until you've asked. Confirm current figures on the [pricing page](/in/pricing/).

## Dictation or a drafted note: what are you buying?

This is the part the price tag hides. Augnito and an ambient scribe aren't two versions of the same tool.

Augnito's published material describes medical speech-to-text. You dictate, and the output follows the words you provide. The work of composing and structuring the note remains with the clinician.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

| | Augnito (dictation) | Patient Square (ambient scribe) |
|---|---|---|
| How you use it | You dictate; it types | You consult; it drafts |
| Output | Your spoken words as EMR text | Structured SOAP note, ICD-10 suggestions, prescription draft |
| Your effort during the visit | Compose and dictate each line | Just talk to the patient |
| Pricing | Quote-only (contact sales) | Published: from ₹1,599/mo, ex-GST |
| Language question | Confirm in the dated quote | English, Hindi, Hinglish, 20+ languages, code-mixed |

The honest trade: dictation gives you word-for-word control; an ambient scribe produces a structured draft for review. Neither is strictly better. They fit different doctors. For the wider field, our [India AI scribe comparison](/in/blog/india-ai-scribe-comparison/) and [Augnito alternatives](/in/blog/augnito-alternatives-india/) coverage lay out more options side by side.

## When is Augnito the better fit?

When you genuinely prefer to dictate. Some doctors think out loud and want exact control over every word in the note. If your EMR is already where you want your spoken text to land and you like being the author, dictation may be the workflow you prefer. That is a workflow preference, not a head-to-head performance finding.

Choose the ambient scribe if you'd rather not dictate at all, want the note drafted from a normal conversation, need multilingual capture, and want a price you can see before a sales call.

## How to decide in a week

1. Decide first whether you want to dictate or not. If dictating with full control appeals, put Augnito on your list and ask for its India quote in writing.
2. If you'd rather just talk to the patient, shortlist ambient scribes with published prices.
3. Match the output honestly: EMR text versus a structured note with codes and an Rx draft. They're not the same deliverable.
4. Trial on real visits. A scripted demo flatters every tool; a busy Tuesday tells the truth.
5. Confirm Patient Square's current price and GST on the [pricing page](/in/pricing/), then <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> on real visits.

The encryption, access, and audio-retention receipts are on the [security page](/in/security/). Audio is processed in memory and discarded once the note drafts, so nothing is retained. If dictation is the workflow you want, ask Augnito to demonstrate it on the clinic's visits and provide a dated written quote. If you want a reviewable note draft with published practice pricing, start your 7-day free trial with Patient Square and agree its start date. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

---

## Bahmni vs an AI-Native EHR in India: The Real TCO
https://patientsquare.com/in/blog/bahmni-vs-ai-native-ehr-india/
Published 2026-07-07 · Updated 2026-07-22 · Tags: comparison, ehr, bahmni, open-source, pricing

Bahmni is free to license but you pay in hosting, implementation, and no AI documentation. Honest total cost vs a bundled AI EHR from ₹2,399/mo, ex-GST.

The software licence is free. Bahmni is open source under the AGPL, so there's no per-seat or per-doctor licence fee, and per its own FAQ, anyone may charge for implementation services but the code itself costs nothing. What isn't free is running it: hosting, setup, configuration, staff training, upgrades, and ongoing support. Those are real, recurring costs, and for most clinics they're paid to an implementation partner.

"Free EHR" and "Bahmni" go together in a lot of Indian clinic searches, and the licence really is free. Bahmni is open source under the AGPL, with no per-doctor fee. But free-to-licence isn't free-to-run: you pay in hosting, implementation, staff training, and ongoing support, and Bahmni doesn't include AI documentation, so you still write every note yourself. An AI-native EHR flips that trade. Patient Square bundles the AI Copilot EHR with an ambient scribe at ₹2,399 per doctor per month, ex-GST, with no infrastructure to manage. The [India pricing](/in/pricing/) is one click away.

So the real question isn't "free versus paid." It's whether you'd rather own and run the system, or subscribe and have the documentation done for you. Both cost money. They just cost it in different places.

> **Key takeaways**
>
> - Bahmni's licence is free (open source, AGPL), but hosting, setup, training, and support are real recurring costs, per Bahmni's own FAQ.
> - A real Bahmni implementation is a project. Open-source EHR deployments commonly run consultant-led installs in the ₹4 to ₹15 lakh range, plus config and hosting.
> - Bahmni has no AI scribe or ambient documentation. You still write every note yourself.
> - Patient Square bundles an AI EHR and ambient scribe at ₹2,399/doctor/mo, annual, ex-GST, with no setup fee and no hosting to run.
> - Bahmni wins for hospitals wanting self-hosted control with technical staff; an AI-native EHR wins for clinics whose drain is documentation time.

## What does "free" mean with Bahmni?

The licence, and only the licence. Bahmni is a mature open-source EMR and hospital-information system, built on OpenMRS and proven across many countries and hundreds of sites. Under the AGPL there's no software licence fee, which is a genuine advantage over subscription EHRs. Per Bahmni's FAQ, the software is free, but anyone may charge for implementation services, and that second half is where the money goes.

Running Bahmni means someone installs it, configures it to your workflows, hosts it (cloud or on-premise), trains your staff, and supports it through upgrades. For most clinics that's an implementation partner with an invoice. A hands-on hospital IT team can do it in-house, trading cash for staff time. Either way, the licence being ₹0 tells you almost nothing about what the system costs to operate.

If your reason for looking at free EHRs is the documentation burden rather than the licence line, book a demo and see what an ambient scribe removes that a records system doesn't touch.

## What does Bahmni really cost to run?

Budget for a project, not a subscription. Precise numbers depend on scope and who does the work, so treat these as estimates: consultant-led installation of an open-source EHR commonly falls in a rough ₹4 to ₹15 lakh range for a real deployment, with configuration and customization on top and ongoing hosting and support after that. A 50-bed hospital's Bahmni go-live is typically a one-to-two-month implementation, per Bahmni's own guidance, not a same-day signup.

Here's the honest cost shape, Bahmni versus a bundled AI EHR:

| Cost line | Bahmni (self-hosted, open source) | Patient Square (AI-native, cloud) |
|---|---|---|
| Software licence | ₹0 | Included in subscription |
| Setup / implementation | ₹4-15L (consultant) or your team's time | ₹0 (no setup fee) |
| Hosting | You provision and pay for it | Included |
| Ongoing support / upgrades | Paid partner or in-house staff | Included |
| Recurring price | Hosting + support, ongoing | ₹2,399/doctor/mo, ex-GST |
| AI documentation | None | Ambient scribe included |

The DIY column can look cheaper in cash if you have the technical skill and the time. It rarely stays cheaper once you count the hours. And none of it buys you the one thing an AI-native EHR includes by default: a scribe that writes the note.

## What does Bahmni not do?

Documentation. Bahmni stores and organizes records well; it doesn't reduce the time you spend creating them. Its FAQ describes no ambient scribe or AI documentation feature, and that's not a knock, it's just a different category of tool. With Bahmni, every note is still yours to type or dictate, patient after patient.

An AI-native EHR is built around closing exactly that gap. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The record that scribe produces lives in the bundled AI Copilot EHR, so the documentation and the storage are one system, not two you have to wire together.

That matters when the operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A records system helps you store the note. An AI-native EHR helps you actually write it, on a two-minute Tuesday and a hundred-patient one alike. For the broader free-versus-paid picture, our [honest look at free EMR software](/in/blog/free-emr-software-india-honest/) covers OpenEMR and others too. And if you want to understand what the paid EHR market in India actually costs before you commit to the free route, [EHR software cost guide](/in/blog/ehr-software-cost-india-buyers-guide/) names every setup fee and AMC that rival vendors bury in their quotes. For the hospital-side picture specifically, [HMS software cost in India](/in/blog/hms-software-cost-breakdown-india/) decodes what a full quote-only hospital system really runs.

## What does the AI-native EHR cost?

Published and flat, with the documentation included. Patient Square's bundled AI Copilot EHR ships in the Copilot plan at ₹2,399 per doctor per month, annual, ex-GST. No setup fee, no hosting to run, no implementation project.

| Plan | Price (annual, per doctor, ex-GST) | With 18% GST | EHR included? |
|---|---|---|---|
| Assist | ₹1,599/mo | ₹1,887/mo | No, scribe + scheduling only |
| Copilot | ₹2,399/mo | ₹2,831/mo | Yes, bundled AI Copilot EHR |
| Autopilot | ₹3,999/mo | ₹4,719/mo | Yes, plus receptionist and follow-ups |

You're paying a recurring subscription in exchange for zero infrastructure work and an ambient scribe. Confirm current figures on the [pricing page](/in/pricing/). One honest note on our side: ABDM integration is on our roadmap, not live yet. If ABHA linking is a hard requirement today, factor that in. Our [cloud versus on-premise guide](/in/blog/cloud-emr-vs-on-premise-india/) weighs the hosting question in more depth.

## When is Bahmni the better choice?

When you want to own the system and can support it. A hospital or large clinic with technical staff, a preference for self-hosting, and a real value on open-source flexibility and no licence fee is exactly who Bahmni is built for. It's proven at national scale in several countries, it handles records, labs, and hospital operations in one stack, and the control it gives is genuine. If customization and ownership matter more to you than AI documentation, and you have the hands to run it, Bahmni is the right call, not a compromise.

Choose an AI-native EHR when documentation time is your bottleneck and you'd rather not run infrastructure at all. A solo doctor or small clinic that wants records plus an ambient scribe, no hosting to manage, and a price on a page is better served by the bundle. You give up self-hosting control. You get a note drafted from every consult and your evenings back.

## How to decide in a week

1. Decide who runs your infrastructure. If you have technical staff and want ownership, Bahmni is viable. If you don't, a cloud subscription removes the whole question.
2. Price Bahmni as a project: get an implementation partner's quote for setup, hosting, training, and annual support in writing. Add them up.
3. Ask the question free-versus-paid hides: does the system write the note, or just store it?
4. If documentation is your real drain, trial an AI-native EHR on real visits and watch the note quality.
5. Confirm Patient Square's current price and GST on the [pricing page](/in/pricing/), then book a short demo to see the bundled EHR and scribe together.

The security and data-ownership receipts are on the [security page](/in/security/). Notes belong to the clinic; export or delete any visit anytime. Free-to-licence is a real advantage if you can run the system. If your problem is the time you spend writing notes, that's the one thing the free option leaves on your desk.

---

## AI Scribe or EMR First? A Clinic's Order (India)
https://patientsquare.com/in/blog/best-ai-scribe-vs-emr-which-first-india/
Published 2026-07-07 · Tags: decision, ai-scribe, emr, pricing

Fixing one thing this quarter? Start with the AI scribe. The honest order for an Indian clinic, with per-doctor pricing from ₹1,599/mo + GST.

Start with the AI scribe. It removes the biggest daily drain, writing the note, on day one, needs no data migration, and works on web or mobile. A full EMR touches your whole front office and takes longer to adopt. With Patient Square, you don't have to pick: the scribe is the Assist tier at ₹1,599/mo annual plus GST, and the bundled AI Copilot EHR arrives at the Copilot tier when you're ready.

Buy the AI scribe first. If your clinic can fix one thing this quarter, fix the note, because that's the task eating your evenings and your patience. The scribe works on day one, needs zero data migration, and runs on the phone in your coat pocket. An EMR is a bigger project that touches your whole front office. So start narrow, get the win, then widen. With Patient Square you don't actually have to choose the two apart: the scribe is the Assist tier at [₹1,599/mo on annual billing](../../pricing/) plus 18% GST, and a bundled AI EHR is waiting one tier up when you're ready for it.

This post is the order of operations, not a spec sheet. What the scribe fixes now, what the EMR fixes later, the honest signs you actually need the record system, and where a plain PDF beats a half-adopted platform.

> **Key takeaways**
>
> - Start with the scribe. It kills the biggest daily drain, writing the note, with no migration and no rollout project.
> - A scribe runs fine with no EMR: draft the note, sign it, export PDF, HL7, or FHIR into whatever you already use.
> - You need the EMR when records must connect across visits: searchable history, past prescriptions, shared charts for multiple doctors.
> - Patient Square: scribe from ₹1,599/mo annual (Assist), bundled AI Copilot EHR from ₹2,399/mo annual (Copilot), both ex-GST, unlimited visits, no setup fee.
> - Notes come out in clean English even when the consult ran in Hindi or a mix. The Rx is a draft you sign, not e-prescribing.

## Scribe or EMR first? Start with the scribe

Here's the fork, in one table. Read the left column as "what hurts today" and the right as "what you get when you fix it."

| | AI scribe first | EMR first |
|---|---|---|
| Fixes | The note. Charting time, thin records, evenings spent typing | Structured records, history, front-office workflow |
| Time to value | Same day. Talk to a patient, get a note | Weeks. Setup, data entry, staff retraining |
| Data migration | None. Nothing to move | Real project. Old records, patient lists, templates |
| Runs on | Web or mobile, standalone | A platform your whole clinic logs into |
| Adoption risk | Low. It's one habit for one doctor | Higher. Everyone has to change how they work |
| Best when | You're drowning in documentation right now | You need records that connect across visits |

For most solo doctors and small clinics in India, the pain that shows up first is the note. In a 67-country study published in BMJ Open, the average Indian consult ran about two minutes, among the shortest anywhere. Two minutes leaves no room to also write a defensible record. That's the gap the scribe closes immediately, without asking your clinic to reorganise itself. Book a demo and watch it draft a note from a real consult before you decide anything else.

## What does the scribe fix that you feel on day one?

The scribe is the thing that hands your evening back. AI Medical Scribe by Patient Square listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the patient leaves. No typing while the patient talks. No charting from the couch at 9pm.

Three reasons it's the right first move:

It needs nothing else to work. You don't migrate a single record. You open it on web or mobile, see a patient, and get a note. That's the whole setup.

It's one habit for one person. A scribe is a change one doctor makes to one part of the day. An EMR is a change your receptionist, your nurse, and every doctor has to make at once. Small blast radius, faster payoff.

It stays useful even if you never buy the EMR. The note exports as PDF, HL7, or FHIR. Keep the PDFs in a folder, or push them into whatever system you already run. The scribe earns its price on documentation alone.

If the consult ran in Hindi, Tamil, or a Hinglish mix, the scribe keeps up on the input side and still writes the note in clean clinical English. Your record reads the same no matter what language the room was speaking. That single detail is why a lot of Indian OPDs try the scribe before anything else.

## When do you actually need the EMR, not just the scribe?

A scribe writes one excellent note. An EMR is where notes live and connect. You've outgrown scribe-only when you hit any of these:

You keep flipping back to find what you prescribed last visit. A folder of PDFs stops scaling once you need to *search* history, not just store it.

More than one doctor sees the same patients. Shared, structured records beat a stack of separate note files the moment two clinicians need the same chart.

Follow-ups and messaging start mattering as much as the note itself. That's front-office territory, and it's where the platform tiers earn their keep.

The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. You can meet that with organised PDFs for a while. Past a certain volume, a real record system is simply easier to defend.

With Patient Square, moving up is a tier change, not a migration. The scribe you already use is the same product; the [bundled AI Copilot EHR](../../pricing/) switches on at the Copilot tier. Nothing to re-learn, nothing to export and re-import.

## What does having both cost in India?

Here's the money, stated plainly, ex-GST with the 18% shown once.

| Plan | What you get | Monthly (month-to-month) | Monthly (annual billing) | With 18% GST (annual) |
|---|---|---|---|---|
| Assist | AI scribe, ICD-10 suggestions, eRx draft, scheduling | ₹1,999 | ₹1,599 | ₹1,887 |
| Copilot | Everything in Assist, plus bundled AI Copilot EHR + WhatsApp | ₹2,999 | ₹2,399 | ₹2,831 |
| Autopilot | Everything in Copilot, plus AI Receptionist, follow-ups, priority support | ₹4,999 | ₹3,999 | ₹4,719 |

The point of the table: the EHR isn't a separate purchase with its own sales cycle. It's ₹800 a month more than the scribe, before GST, and it's already wired to the notes you're producing. That's a very different shape from buying a standalone EMR that quotes per-module and per-user and then asks you to feed the scribe's output into it. Every tier is unlimited visits, no per-note metering, no setup fee. [See the full ladder](../../pricing/).

## How this compares to buying a full EMR outright

Plenty of Indian EMRs are priced fine on their own. [HealthPlix](../healthplix-alternatives-india/), for instance, lists Pro at ₹11,999/year and Elite at ₹17,999/year per doctor, roughly ₹1,000 to ₹1,500 a month. That's a competent record system. What it isn't is an ambient scribe: you still drive the note yourself, or dictate it, or type it.

So the real comparison isn't "scribe vs EMR" on price. It's "who writes the note." Buy an EMR-first and you've organised where notes go without fixing the two minutes it takes to write one. Buy the scribe-first and you fix the writing immediately, then add the record layer when you need it. For the head-to-head on the EMR side specifically, our [HealthPlix alternatives](../healthplix-alternatives-india/) post lays it out, and if you're a one-doctor practice, [AI scribe for solo doctors in India](../ai-scribe-for-solo-doctors-india/) covers your exact case. For the full picture on what EHR software costs in India before you decide which to buy first, [EHR software cost guide](/in/blog/ehr-software-cost-india-buyers-guide/) names every fee that makes the EMR-first route more expensive than it looks.

## When is EMR-first the right call?

Be honest with yourself here, because sometimes the order flips.

Go EMR-first if your clinic's actual bottleneck is records, not writing: you have years of paper or scattered files, multiple doctors who need one shared chart today, and a front desk that's the real chokepoint. In that case the note isn't your worst problem, and a scribe bolted onto chaos doesn't fix the chaos. Sort the record system, then add the scribe.

Go scribe-first, which is most clinics, if the thing you dread is the documentation itself, you want a same-week win with no migration, and you'd rather grow into the record system than run a rollout project cold. That's the path Patient Square is built for: start on Assist, move to Copilot when the records need to connect.

The split isn't about which tool is better. Both matter. It's about which pain you're paying to remove first. For nearly every solo doctor and small clinic we talk to, that's the note.

## How to decide in a week

Skip the feature grid. Run the test:

1. Name the pain out loud. "I write notes at home" points to the scribe. "I can't find last visit's prescription" points to the record system.
2. If it's the note, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, then run it on a real clinic day after the workspace is ready, Hindi consults included.
3. Check the exported note against how you actually chart. PDF, HL7, or FHIR into your current setup.
4. Only then ask whether you need records that connect across visits. If yes, it's a one-tier move to the bundled EHR, not a second purchase.
5. Read the receipts. Encryption, access, audit status, and our roadmap (including ABDM, which is on our roadmap, not live) sit on the [security page](../../security/).

Book a short demo if you want to see the note quality against your own visit type first. For most Indian clinics the answer is simple: the scribe fixes today, the EHR is there for tomorrow, and you can start with one and grow into the other without ever migrating a thing.

---

## Best EHR for Pediatrics: Honest Picks for 2026
https://patientsquare.com/us/blog/best-ehr-for-pediatrics/
Published 2026-07-07 · Updated 2026-08-27 · Tags: best, pediatrics, ehr-comparison, emr-for-pediatrics

Comparing the best EHR for pediatrics in 2026, from dedicated peds platforms to bundled AI EHR options from $119/mo. 6 options, one honest verdict.

It depends on how much you need pediatric-specific tooling. PCC and Office Practicum are built for pediatrics and include growth charts, VFC support, and immunization registry integration out of the box. If documentation speed and cost matter more than deep peds-specific features, Patient Square's Copilot tier at $119/mo annual gives you a bundled AI EHR and ambient scribe in one package. Try both categories before committing.

If you run a pediatric practice and you need growth charts, immunization registry connections, and VFC inventory built into your EHR, the honest answer is a dedicated pediatric platform. PCC or Office Practicum will serve you better than anything a general-purpose EHR can offer. That includes Patient Square.

But if your biggest problem is documentation time, 25 back-to-back well-child and sick visits with a half-hour of notes waiting at the end, then a bundled ambient scribe and AI EHR is worth evaluating. Patient Square's Copilot tier does exactly that, at $119/mo per clinician on annual billing. You can request an assisted 7-day trial after workspace setup. Book a demo or see the full breakdown on the [pricing page](/us/pricing/).

The rest of this page maps where each option wins and why.

> **Key takeaways**
>
> - Dedicated pediatric EHRs (PCC, Office Practicum) win on growth charts, immunization registry, VFC inventory, and Bright Futures. If those are hard requirements, start there.
> - PCC has earned Best in KLAS for Ambulatory Pediatric EMR eight years running, with a 2026 score of 94.8 per KLAS Research.
> - Neither PCC nor Office Practicum publishes pricing. Both are quote-based.
> - Patient Square bundles an ambient AI scribe and AI Copilot EHR from $119/mo annual. No pediatric-specific tooling, but documentation is fast and the price is on a public page.
> - If you see 20+ patients a day, documentation speed is not a minor concern. A scribe that hands back a structured note in about two minutes changes what your evenings look like.

## What pediatric EHR buyers are actually choosing between

There are two real axes here, and most comparison posts pretend they're one.

The first is clinical depth for pediatrics specifically: growth charting, immunization registry, VFC inventory, Bright Futures templates. CDC/WHO growth curves that generate automatically from vitals rather than requiring manual entry. State IIS connections that pull a new patient's vaccination history at intake without transcription. VFC lot tracking and expiration management. Pre-loaded screening questionnaires (M-CHAT-R, Vanderbilt, PHQ-A) tied to age-appropriate visit types. If these are table stakes for your practice, you need a platform built for pediatrics. Full stop.

The second axis is visit volume and documentation speed. A peds practice sees a different patient every 10 to 15 minutes. Well-child checks, sick visits, sports physicals, vaccine-only appointments, all day. This is where most dedicated peds EHRs fall short: the clinical tools are thorough, but documentation without an ambient scribe creates a backlog that follows the physician home. That second axis is where Patient Square competes.

These aren't trade-offs in a single dimension. They're different problems, and you should know which one you have.

## The comparison table

| EHR | Growth charts | Immunization registry (IIS) | VFC inventory | Built-in ambient scribe | EHR included | Pricing |
|---|---|---|---|---|---|---|
| PCC | Yes | Yes | Yes | No (third-party options) | Yes | Quote only |
| Office Practicum | Yes | Yes | Yes (VacLogic+) | No native | Yes | Quote only |
| athenahealth | Partial | Varies by state | No | No | Yes | Quote only |
| eClinicalWorks | Yes | Yes | Varies | No native | Yes | Quote only |
| Epic (large groups) | Yes | Yes | Yes | Optional add-on | Yes | Quote only |
| **Patient Square** | **No** | **No** | **No** | **Yes, native** | **Yes (Copilot+)** | **$119/mo annual** |

No asterisks on the Patient Square row. Those three "No" entries are real gaps. If those columns are non-negotiable, this table is doing its job.

## The dedicated pediatric EHRs: what each one actually does

### PCC (Physician's Computer Company)

PCC is the benchmark for independent pediatric practices, and it has been for a while. Eight consecutive Best in KLAS wins for Ambulatory Pediatric EMR, with a 2026 KLAS score of 94.8. That's not a marketing claim; KLAS scores come from peer-reported data, and 94.8 is unusually high. The platform covers growth charting, immunization registry connections, Bright Futures protocols, and a parent-facing portal. It was built for peds from day one and it shows. Pricing is quote-based, so you'll need a sales call to get a number.

### Office Practicum

OP's depth shows up in the details. The VacLogic+ system handles VFC lot tracking, state registry submissions, and catch-up schedule management. The template library runs to 200+ visit templates tied to Bright Futures, plus 30+ pediatric-specific screening tools: CRAFFT, M-CHAT-R, PHQ-2/9, Vanderbilt ADHD. Growth charts support hybrid WHO/CDC standards, Down syndrome curves, and Fenton charts for preterm infants. Also quote-based, no public pricing.

One thing worth noting: OP doesn't ship a native ambient scribe. High-volume peds practices often layer on a third-party transcription tool, which adds another subscription and another integration to manage.

### athenahealth

athenaOne has pediatric modules and configurable templates, but it's a multi-specialty platform being asked to serve peds workflows. SelectHub puts its peds satisfaction score at a B-minus, with 77% of customers satisfied or highly satisfied. If your group already runs on athena and you're adding a peds panel, it's workable. If pediatrics is your entire practice from day one, you'll probably find the peds-specific tooling thinner than the dedicated platforms above.

### eClinicalWorks

eCW covers the basics: pediatric templates, growth charts, immunization tracking. Common in community health settings and federally qualified health centers partly because it's cost-competitive, and partly because it handles the volume. The PRISMA search and healow patient portal are real additions. But SelectHub's peds-specific data is telling: C-minus, 62% satisfied or highly satisfied. Practices that switch from PCC or OP often find the pediatric workflows shallower than what they came from.

### Epic

Epic has everything on the peds checklist: growth charts, IIS integration, VFC support, weight-based dosing tools, the works. It's the right choice for academic medical centers and large pediatric health systems with an implementation team to support it. EHR Source puts first-year total ownership for a 3-provider practice at $30,000 to $75,000 (third-party estimate, not an Epic figure). For an independent practice, that's a different category of decision than the others on this list.

## A Tuesday in flu season

It's 8am. A pediatrician walks in. Twenty-seven patients on the schedule: 9-month well-child, strep throat, two ear infections, a sports physical, back-to-back sick visits through lunch, a few vaccine-only afternoon slots. By 5pm, if every note was done in the room, it was a good day. If notes are still open at 5pm, that doctor is staying.

Most dedicated peds EHRs are thorough. The templates are good. But none of the platforms above shipped with ambient capture, and without it, documentation at the end of a 27-patient day is still a manual job. An ambient scribe changes that. It listens during the visit, structures the SOAP note, surfaces ICD-10 suggestions and a prescription draft, and has it ready in about two minutes. The physician signs or edits. Done. Next room.

Patient Square's scribe is built into the subscription. Not a third-party plugin, not a separate seat.

AI Medical Scribe by Patient Square is one module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit; move up to the Copilot plan and it comes bundled with an AI EHR.

For peds practices where the documentation problem is bigger than the clinical-tooling problem, the [AI scribe for pediatrics post](/us/blog/ai-scribe-for-pediatrics/) goes deeper on the workflow. And the [AI scribe export guide](/us/blog/ai-scribe-any-ehr-export/) explains how the output format works if you're checking fit with your current setup.

## Our honest take on Patient Square for peds

If you've already got growth charting and IIS covered, or you're part of a larger system that handles that layer, Patient Square is worth a look. The Copilot tier bundles the ambient scribe and a full AI Copilot EHR in one subscription at $119/mo annual. Specialty-aware templates ship ready. Audio is processed and discarded; nothing is stored. A BAA is available for every customer.

If you need growth charts auto-generating from vitals, immunization registry pull at intake, or VFC inventory management, Patient Square doesn't do those things. We're not planning to replicate what PCC and OP do natively. The honest choice in that scenario is one of the dedicated platforms above.

The [best EMR for small practice](/us/blog/best-emr-for-small-practice/) roundup covers the broader field if you're not sure which category you're in.

## When to choose a dedicated pediatric EHR

Go with PCC, Office Practicum, or a comparable platform when any of these are true:

- State immunization registry pull at new-patient intake is a daily workflow, not a nice-to-have
- VFC inventory tracking and lot documentation are required for your practice type
- Growth charting auto-populating from vitals is expected by your clinical staff
- Bright Futures questionnaires pre-loaded by age are core to your well-visit workflow
- You're a large group or pediatric health system where clinical integration depth outweighs per-seat cost

Documentation time being the main pain? Try [Patient Square's pricing page](/us/pricing/) and the 7-day trial before calling anyone.

## How to evaluate in a week

Skip the vendor presentations to start. Do this instead.

List your hard requirements. Growth charts, IIS, VFC: yes or no? One yes short-lists you to PCC or OP. If no across the board (or you have those covered elsewhere), the field opens up.

Run each finalist on a real patient day. Not a scripted demo. Those are designed to look good. A Tuesday morning of well-child checks and sick visits will tell you things no demo will.

Ask the audio question before you sign anything. For every ambient scribe on your list: what happens to the recording once the note is done? Is it stored? For how long? The answer matters clinically and under HIPAA.

Get the total cost in writing. Monthly fee, setup, per-feature add-ons, portal fees if there are any. Headline pricing is often the cheapest number available; the full invoice is what counts.

Patient Square publishes everything on the [pricing page](/us/pricing/). The 7-day free trial requires no credit card. Book a short demo if you want to see the note output on a real peds visit type before committing to a trial week.

---

*Comparing AI scribe options more broadly? The [AI scribe for family practice](/us/blog/best-ehr-for-family-practice/) roundup covers the adjacent specialty. Weighing a full EHR switch? The [best EMR for small practice](/us/blog/best-emr-for-small-practice/) guide covers the selection criteria that apply across specialties.*

---

## Best EHR for Psychiatry: A Prescriber-First Scorecard
https://patientsquare.com/us/blog/best-ehr-for-psychiatry/
Published 2026-07-07 · Updated 2026-08-29 · Tags: best, psychiatry, ehr, comparison

Choose a psychiatry EHR by testing EPCS, medication workflow, labs, scales, billing, therapy notes, privacy, and AI documentation before price.

For a prescribing practice, the best EHR is the one that passes the medication, pharmacy, EPCS, monitoring, billing, and safety workflows you actually use. For therapy-led work, behavioral templates, groups, portal, telehealth, and claims may matter more. There is no honest universal winner.

The best EHR for psychiatry is decided by one question: does the practice prescribe, or is it primarily therapy? A prescriber needs a medication and pharmacy system that can survive an EPCS audit. A therapist may care more about behavioral notes, groups, claims, portal, and telehealth.

Start there. Ambient documentation is useful, but it cannot turn a missing prescribing workflow into a psychiatry EHR.

> **Key takeaways**
>
> - EPCS and pharmacy transmission are hard stops for many prescribing practices. Patient Square does neither.
> - A therapy-led practice should score DAP/BIRP support, group sessions, portal, telehealth, billing, and outcome measures.
> - CMS documentation principles still apply: the record should identify the encounter, findings, assessment, plan, date, and author and support submitted codes.
> - Practice Copilot can use the Patient Square EHR from the Copilot tier or work alongside an existing EHR. The published Copilot annual monthly equivalent is $119.

## The psychiatry-versus-therapy scorecard

Use a zero-to-two score for each row: 0 means absent, 1 means available with a separate product or manual step, and 2 means demonstrated inside the proposed workflow. A hard-stop row cannot be averaged away.

| Requirement | Prescribing psychiatry | Therapy-led practice | Hard stop? |
|---|---:|---:|---|
| Pharmacy transmission | 2 | 0 | Yes for electronic prescribing |
| EPCS application and audit evidence | 2 | 0 | Yes when required by workflow or law |
| Medication list, allergies, reconciliation | 2 | 0-1 | Often |
| PDMP access and controlled-substance workflow | 2 | 0 | Often |
| Lab ordering, results, and monitoring | 2 | 0 | Often |
| Structured new evaluation and follow-up | 2 | 1 | No |
| Therapy note formats and treatment plans | 1 | 2 | Often |
| Group, family, and collateral encounters | 1 | 2 | Practice dependent |
| Outcome scales and longitudinal trends | 2 | 2 | Practice dependent |
| Claims, authorizations, ERA, and balances | 1-2 | 1-2 | Payer dependent |
| Portal, intake, messaging, and telehealth | 1-2 | 2 | Practice dependent |
| Ambient draft and review | 1-2 | 1-2 | No |
| Record export and termination test | 2 | 2 | Yes |

The numbers do not rank brands. They expose which category you need.

## EPCS cannot be replaced by a prescription draft

DEA says an electronic prescription application can transmit controlled-substance prescriptions only when it meets the applicable requirements. The application provider must make its audit or certification report available so practitioners can determine compliance and limitations. The practitioner still reviews the prescription and remains responsible.

DEA also notes that its rules do not make EPCS universally mandatory by themselves and that state laws may add requirements. Check the jurisdiction in which you practice. This is a procurement gate, not legal advice.

Ask a candidate vendor to demonstrate:

1. practitioner identity proofing and two-factor credential use;
2. access approval and removal when a prescriber joins or leaves;
3. the review and legal-signature screen;
4. transmission, cancellation, correction, and pharmacy response;
5. the audit or certification report and any limitations;
6. the prescribing log and incident process.

A text draft with medication name and dose is not that system.

## The eight-event psychiatry demo

Give each finalist the same cases. Do not accept slides.

| Event | Evidence to capture |
|---|---|
| New psychiatric evaluation | Required sections, author, time, diagnosis rationale, care plan |
| Medication follow-up | Reconciliation, side effects, adherence, assessment, monitoring |
| Controlled-substance scenario | EPCS path, credentials, review, transmission, audit trail |
| Abnormal lab | Result receipt, acknowledgement, task, patient communication |
| Therapy plus medication visit | Narrative quality without losing medication facts |
| Safety-sensitive session | Consent choice, pause or no-record workflow, access controls |
| Signed-note amendment | Original version, author, reason, date, downstream effect |
| Contract exit | Usable sample export with notes, medications, documents, and audit data |

CMS tells practitioners to document during the encounter or as soon as practicable after it, and to make records complete, legible, attributable, and supportive of billed services. Score the final signed record, not the beauty of the generated draft.

## When a dedicated psychiatry EHR wins

A dedicated system should lead the shortlist when prescribing and monitoring are central. Built-in or proven connected workflows for EPCS, pharmacy transmission, PDMP, medication history, labs, refill requests, and clinical roles reduce the number of handoffs that can fail.

Behavioral depth can matter just as much. A group may need outcome measures, treatment-plan reviews, supervision, multiple participants, payer authorizations, ERA posting, patient balances, and a portal. If those jobs run the practice, a documentation-first product is the wrong center of gravity.

This is the honest better-fit case for a specialty EHR. Pay for it even if another product drafts prettier notes.

## When Patient Square belongs on the shortlist

Patient Square is a narrower option. Its public plan says the scribe returns a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Audio is processed in memory and discarded when the note is drafted. Scheduling starts on Assist. Copilot adds the bundled AI Copilot EHR and WhatsApp messaging.

The public US rates are $99 monthly or $79 annual monthly equivalent for Assist, $149 or $119 for Copilot, and $249 or $199 for Autopilot. Visits and notes are listed as unlimited.

The limitations matter:

- the prescription is a draft, with no pharmacy transmission or EPCS;
- the public product surface does not list PDMP, medication reconciliation, drug-interaction checking, labs, behavioral scales, patient portal, telehealth, or insurance billing;
- specialty-aware templates do not prove DAP, BIRP, psychiatry, or group-session depth;
- EHR-ready export (PDF · HL7 · FHIR) does not promise native write-back into another EHR.

Practice Copilot can use the Patient Square EHR from the Copilot tier or work alongside an existing EHR while the practice retains separate prescribing and billing systems. It is a poor choice for a psychiatrist who wants one product to own medication, monitoring, claims, and patient access.

## Privacy is a workflow, not a badge

Psychiatry records demand a concrete data map. HHS says a software seller is not automatically a business associate, but PHI hosting or support access can create that role. Establish the relationship and put any required BAA in place before access.

For every product, record:

- what is captured and whether audio is retained;
- where notes, transcripts, prompts, and logs live;
- who can access them for support;
- retention and deletion by data type;
- how role and emergency access are reviewed;
- how the practice receives a usable export;
- what survives account termination and for how long.

Some visits should not be recorded at all. Your consent process needs a no-record path that does not block care.

## Price the complete psychiatry stack

A low EHR subscription can sit beside separate charges for EPCS, ePrescribe, labs, clearinghouse, claims, telehealth, portal, scribe, migration, training, and support. Put them on one sheet:

| Cost row | Monthly | One-time | Usage based | Evidence |
|---|---:|---:|---:|---|
| EHR and staff seats |  |  |  | Current quote |
| EPCS/ePrescribe |  |  |  | Included roles and state scope |
| Lab or exchange interfaces |  |  |  | Named connections |
| Billing and clearinghouse |  |  |  | Claims, ERA, eligibility |
| Portal and telehealth |  |  |  | Required tier |
| Scribe or AI notes |  |  |  | Required seats and limits |
| Migration, training, support |  |  |  | Fixed scope |
| Exit and record export |  |  |  | Format, timing, fee |

Do not enter zero for an unanswered row.

## Named options and their price context

These are not rankings. They are five first-party-published starting points for a psychiatry shortlist, checked August 29, 2026. Prices can change, and quote-only vendors should be asked for the full configuration that handles the practice's actual work.

| Option | First-party price context | Psychiatry workflow to test |
|---|---|---|
| SimplePractice | The live page displays a 50% introductory price for the first 3 months. Standard Starter is $49/month; Note Taker is $35 per clinician monthly after its promotion; ePrescribe is $49 per clinician monthly plus an $89 setup fee. | A therapy-led or smaller practice that needs to verify the add-on cost and prescribing path before choosing it for medication management. |
| ICANotes | Part-time monthly rates are $35 Notes Only, $45 Non-Prescribing, and $138 Prescribing. Full-time rates are $55, $75, and $213. A $99 activation fee applies. Part-time Notes Only and Non-Prescribing include 60 notes monthly; part-time Prescribing includes 100. | A psychiatry practice that needs the Prescribing plan's medication-management and lab workflow shown on its own cases. |
| Valant | Custom pricing. Valant says quotes vary by practice size, workflow, included features, and support. | A behavioral-health group that wants a vendor-led configuration review rather than a public seat price. |
| TherapyNotes | Solo is $69/month. TherapyFuel is $40 per clinician monthly; ePrescribe is $65 per prescriber monthly. | A therapy-led practice that needs to price behavioral-health billing, portal, telehealth, and prescribing alongside documentation. |
| Osmind | Osmind One lists its EHR at $249 per clinician monthly. It is software-only for practices that bill cash or insurance themselves; controlled-substance e-prescribing is listed separately at $49 per clinician monthly. | An interventional psychiatry practice running TMS, Spravato, or ketamine workflows. |

The shortlist does not need a universal winner. Each candidate belongs in the evaluation only if it can show the medication, therapy, financial, or specialty workflow that would otherwise stay with staff.

For a medication-management practice, begin with the prescribing path. Ask each finalist to show a routine refill, a controlled-substance exception, an outside result that changes the plan, and an amendment after the note is signed. For therapy-heavy work, reverse the sequence: start with the therapy note, treatment-plan review, group or family encounter, patient access, and claims handoff. A platform may be excellent at one set of jobs and a poor fit for the other.

Published subscription prices are only the first number in this category. Add the seats and add-ons required for the work you cannot leave outside the system: prescribing, claims, telehealth, portal access, outcomes, AI documentation, onboarding, and record exit. A quote-only product is not automatically expensive, and a low published price is not the all-in cost. Write down the missing rows before comparing totals.

That is also how Patient Square should be evaluated. Its paid path starts at $79 per clinician per month as an annual monthly equivalent for Assist. Copilot is $119 and adds the bundled AI Copilot EHR and WhatsApp messaging. Those prices do not replace the separate specialty tools a prescriber may need. They make sense when the practice's unresolved job is documentation and the product boundary fits.

Keep the notes from each evaluation in one place. The useful evidence is concrete: a screen recording of the exception workflow, the quoted price with its required seats, the contract answer on data access, and the name of the person who will own a failure. A vendor can improve its product after the trial. The decision record should still explain why the practice chose its current path.

## The decision

For prescribing psychiatry, choose the system that passes EPCS, medication, monitoring, and pharmacy tests before you score its scribe. For a therapy-led practice, switch the weights toward behavioral notes, groups, portal, telehealth, and billing. Patient Square deserves a trial only when its narrower public scope matches the job.

The [best EHR for therapists](../best-ehr-for-therapists/) uses a therapy-specific disqualification scorecard, while the [AI scribe for therapists](../ai-scribe-for-therapists/) covers consent and do-not-record decisions. Request your 7-day trial when the documented workflow matches your practice.

## Patient Square and your existing record system

Practice Copilot can use the bundled AI Copilot EHR from the Copilot tier, or work alongside an existing EHR. It does not promise automatic third-party filing or write-back. Keep the incumbent system when it owns the specialty workflow that Patient Square does not publicly list.

---

## AI Scribe for Physical Therapy: Notes, Units and the 8-Minute Rule
https://patientsquare.com/us/blog/ai-scribe-for-physical-therapy/
Published 2026-07-06 · Tags: ai-scribe, physical-therapy, specialty

How an AI scribe drafts physical therapy notes, what it captures for timed CPT codes, and what a PT still owns for units and medical necessity.

No. It captures what you narrate during the visit, but the treatment-minute totals that drive your units under the 8-minute rule stay yours to track and confirm. CMS ties billable units to documented one-on-one minutes for each timed code, and you own that math. Read the draft, check the minutes against what you did, and sign.

An AI medical scribe for physical therapy listens while you run the session and drafts the note as you cue the squat or reset the tape measure, so you finish charting minutes after the patient leaves. It captures what you say out loud during the exam, the intervention, and the plan, then hands back a structured note you review and sign. What it does not do is your units. The 8-minute rule math stays yours.

> **Key takeaways**
> - Office-based physicians spend more than five hours in the EHR for every eight hours scheduled with patients, per AMA-cited research.
> - Under the CMS 8-minute rule, billable units come from documented one-on-one treatment minutes for each timed CPT code. A scribe doesn't count those minutes for you.
> - APTA warns that lines like "patient tolerated treatment well" don't prove skilled care. You still voice the medical-necessity reasoning.
> - AI Medical Scribe by Patient Square drafts the note fast, suggests ICD-10 codes you confirm, and exports into your EMR. It does not integrate.

## The 6pm problem in an outpatient PT clinic

Picture a Thursday in a busy outpatient clinic. Sixteen patients on your board. A post-op knee at 8, a rotator cuff at 8:45, two low-back cases back to back before lunch, a balance eval you're squeezing in. Between each one you're supposed to write a note that captures the exercises, the manual work, the cues you gave, the progress toward goals, and the treatment minutes that decide your units.

You don't. Nobody does, not in real time. So the notes stack up. By 6pm the last patient is gone and you've got a dozen encounters to reconstruct from memory and a smartphone photo of your minute grid. That's the pajama-time charting PTs know too well.

The burden isn't imagined. Office-based physicians spend more than five hours in the EHR for every eight hours of scheduled patient time, according to research the [AMA](https://www.ama-assn.org/practice-management/digital-health/digging-data-cut-ehr-burdens-drive-burnout) cites on documentation. PT documentation carries its own weight on top of that. You're not just describing a visit. You're defending skilled care and lining up timed-code minutes that an auditor might read line by line.

An ambient scribe moves where the note gets written. You talk through the session the way you already coach the patient, and the draft is waiting when you walk to the next table.

## What a scribe captures in a PT session

The scribe writes what it hears. Narrate the exercise, it captures the exercise. Say the rep count and the assist level, they land in the note. Work in silence, and the draft comes back thin. The therapist who talks through the session gets a fuller note than the one who doesn't.

Here's what that looks like across a typical caseload.

| PT note element | What you say out loud | What lands in the draft |
|---|---|---|
| Therapeutic exercise | "Three sets of ten, closed-chain squats to 60 degrees, min assist for form" | Exercise, dosage, assist level under the right code |
| Manual therapy | "Grade III mobilization, right glenohumeral joint, posterior glide, five minutes" | Technique, joint, grade, region |
| Gait training | "Ambulated 150 feet with rolling walker, contact guard, on level surface" | Distance, device, assist level, surface |
| Neuromuscular re-ed | "Single-leg stance, eyes open then closed, 30 seconds each, tactile cue for hip strategy" | Task, progression, cue type |
| Progress toward goal | "Up from 90 to 110 degrees knee flexion, on track for the 120 short-term goal" | Objective change tied to a stated goal |
| Home program | "Added band walks, cut the wall slides, reviewed pain rules" | HEP update with reasoning |

Notice what's missing from that table: minutes. The scribe records that you did closed-chain squats. It does not decide that closed-chain squats plus your manual work equals three units. That decision is yours, and it's where PT documentation gets sharp.

## The 8-minute rule is still your job

This is the part specialty scribe pitches tend to skate past, so let's be blunt about it.

Under Medicare, timed CPT codes bill in 15-minute units, and the units you can bill come from the total one-on-one treatment minutes you document for those codes. The [CMS Claims Processing Manual](https://www.cms.gov/medicare/billing/therapyservices/downloads/clm104c05.pdf) sets the threshold: a single 15-minute unit covers 8 through 22 minutes of a timed service, and the total timed minutes for each date have to be documented to support the units billed. That's the 8-minute rule PTs live by.

A scribe captures your narration. It does not run a stopwatch on your hands-on time. So the minute totals that drive 97110, 97140, 97530, and the rest still come from you. If you voice "twelve minutes of manual therapy on the shoulder," the scribe can put that line in the note. Whether that adds up to a billable unit, and how it combines with your other timed minutes, is a call you make and confirm.

One more wrinkle worth saying out loud: CMS treats documentation time spent away from the patient as non-billable. Charting done at the table, in front of the patient, can count toward your treatment minutes. Charting done at 6pm at your desk cannot. That's a quiet argument for drafting in the room, which is exactly where an ambient scribe drafts.

So keep your minute grid. The scribe frees up the sentence-writing, not the unit math. Confirm both before you sign.

## Medical necessity and skilled care still come from you

Payers deny PT claims for two reasons more than any other: no proof of medical necessity, and no proof the work needed a skilled therapist. A scribe can't fix that gap on its own, because it only writes down the reasoning you actually voice.

[APTA](https://www.apta.org/your-practice/documentation/defensible-documentation/elements-within-the-patientclient-management-model/documentation-of-a-visit) frames the note around two questions: why now, and why you. The note has to show the type and level of skilled assistance you gave, your clinical decision-making, and the patient's progress or lack of it. APTA calls out the lazy line directly. "Patient tolerated treatment well" proves nothing about skilled care. It's the kind of phrase an aide could write.

So voice the reasoning. "Progressed to closed-chain because open-chain was pain-free and quad activation improved" is skilled-care language. Say it, and the scribe captures it. Stay silent, and you get a bland note that reads like anyone could have run the session, which is precisely what gets a claim flagged.

We think this is the honest heart of a PT scribe. It's a stenographer for your clinical thinking. It records the why. It cannot supply a why you never said.

## What this scribe cannot do

Buying software on marketing gloss is how clinics end up disappointed. So here are the lines we won't cross in describing it.

- It does not integrate with your EMR. It drafts the note, and you copy or export it into your system. No HL7, no FHIR, no live chart write-back.
- It does not count your timed-code units. The 8-minute rule math stays yours to track and confirm.
- ICD-10 codes are suggestions you confirm, not auto-posted charges. You read them, accept or fix them, and own them.
- Prescriptions or referral requests come back as a draft. You review and sign. Nothing routes on its own.
- Notes are English. If your session runs in another language, the note still comes back in English.
- Audio is never stored. The scribe listens, drafts, and discards the recording. There's no audio file sitting on a server.
- No accuracy percentage is promised, because note quality tracks what you say. Silent session, thin note.

That last one is the whole deal. The scribe captures your words. It does not evaluate the patient, it does not invent a finding you didn't voice, and it does not decide your billing. For the code-review side of that, our explainer on [what to expect from AI scribe accuracy](/us/blog/ai-scribe-accuracy-what-to-expect/) walks through where the draft is strong and where you have to read closely.

## How it fits your existing PT EMR

Plenty of PT EMR platforms already bake in documentation templates and flowsheets, and some large systems run ambient scribing wired straight into the chart. If your clinic already runs a system-wide ambient tool tied to your EMR, that tight integration is a real advantage and probably the better fit. Bolting a second tool onto it rarely pays off.

Where a lighter scribe fits is the cash-based, small-group, or independent PT clinic that wants faster notes without an IT project. You export the draft into whatever EMR you run. You're not waiting on an integration team. You're reviewing drafts on day one. The scribe doesn't care which system you use, because it never touches it. For how that export lands in practice, see [how an AI scribe exports into any EHR](/us/blog/ai-scribe-any-ehr-export/).

## How to roll it out without a mess

Start with one therapist and one clinic day. Pick a caseload with clear intervention narration, since that's the fastest win. Have the PT talk through exercises, manual work, and reasoning the way they'd teach a student, then read the first week of drafts closely to calibrate the voice.

A few practical notes:

- Keep your minute grid running alongside. The scribe writes the note; you own the units. Confirm both.
- Voice the skilled-care why. "Progressed because" beats a silent rep count every single time.
- Brief your techs and aides. Their in-room narration gets captured too, which fills out the picture.
- Keep a human on every code and every draft. That's the design, not a nice-to-have.

Curious whether the time savings pencils out for your caseload? Our [AI scribe ROI walkthrough](/us/blog/ai-scribe-roi-calculator-guide/) shows the math on minutes-per-note against your visit volume. And if you run overlapping caseloads with mid-levels, [the AI scribe guide for nurse practitioners](/us/blog/ai-scribe-for-nurse-practitioners/) covers the same review-and-sign workflow from their side.

For the record, the canonical version: AI Medical Scribe by Patient Square is one module inside Practice Copilot. It listens during the visit and hands back a structured note, ICD-10 suggestions, and a draft for your review, ready to sign about two minutes after the session ends. It does not integrate with your EMR, it does not store audio, and it does not decide your billing.

Want to see it on your own PT notes? Book a demo and bring a typical Thursday board. Walk us through a session the way you'd coach it, and watch what the draft catches.

---

## Best Clinic Software for a Single Doctor in India (2026)
https://patientsquare.com/in/blog/best-clinic-software-for-single-doctor-india/
Published 2026-07-06 · Updated 2026-08-27 · Tags: india, comparison, clinic-software, solo-practice

Best clinic software for a single doctor in India: transparent pricing from ₹1,599/mo + GST, zero implementation, and an AI scribe, compared honestly.

For a solo doctor, the winner is usually the one with a published per-doctor price, no implementation project, and fast documentation. Patient Square's Practice Copilot leads on that: ₹1,599/mo for the AI scribe (annual, ex-GST) and ₹2,399/mo for the Copilot tier with a bundled AI EHR, with no setup fee. HealthPlix is the other transparent option (₹11,999–₹17,999/yr per doctor). Practo Ray suits doctors who want patient-facing booking but gates its price behind a demo.

For a single doctor in India, the best clinic software is the one with a price you can see, no implementation project, and documentation that doesn't follow you home. Patient Square's Practice Copilot leads on all three: ₹1,599 per month for the AI scribe (annual, ex-GST), ₹2,399 for the Copilot tier with a bundled AI Copilot EHR, no setup fee. HealthPlix is the other transparent choice; Practo Ray suits doctors who want patient-facing booking but hides its price behind a demo. The full ladder is on the [pricing page](/in/pricing/), and you can book a demo to see a finished note in about two minutes.

> **Key takeaways**
>
> - For a solo doctor, three things decide it: published price, zero implementation, fast documentation. Patient Square wins on all three.
> - Patient Square: ₹1,599/mo scribe, ₹2,399/mo scribe plus bundled AI EHR (both annual, ex-GST), no setup fee.
> - HealthPlix publishes per-doctor plans (₹11,999–₹17,999/yr); Practo Ray gates pricing behind a demo but is strong on patient booking.
> - No enterprise HMS implementation cost: a single-doctor clinic shouldn't pay lakhs to get started.
> - Multilingual capture matters in India, but note output is clean English. Confirm language needs before buying.

## The pick at a glance

The honest table up front. A single doctor is choosing between tools that solve different problems, so match the row to your day.

| Option | Best for a solo doctor who... | Pricing | AI scribe | Bundled EHR | Setup cost |
|---|---|---|---|---|---|
| Patient Square (Practice Copilot) | loses time to charting and wants records in one place | ₹1,599/mo scribe, ₹2,399/mo with EHR (annual, ex-GST) | Yes, ambient | Yes, at Copilot tier | None |
| HealthPlix | wants a published-price EMR with regional-language Rx printing | ₹11,999–₹17,999/yr per doctor | No | EMR | Low |
| Practo Ray | prioritises patient booking and Practo-network visibility | Est. ₹2,000–₹4,000/mo, disclosed on demo | No | Records | Varies |

None of these is a bad tool. The question is what your bottleneck is: writing notes, keeping records, or getting booked.

## What a single doctor actually needs

A solo practice is not a small hospital, and buying like one is the classic mistake. You don't need bed management, an in-house pharmacy module, or a six-week implementation. You need three things.

First, a price you can see, so learning what a subscription costs doesn't require a demo and a procurement call. Second, a practice-sized assisted setup rather than a lakhs-scale implementation project built for buyers with 50 users. Third, documentation that keeps up. The average Indian consult runs about two minutes and the queue sets the pace, so if the software makes you type notes after clinic, it's adding work, not removing it.

Patient Square is built around exactly this. The price is on the page, there's no setup fee or implementation, and the ambient scribe hands back the note the moment the patient leaves. That's the whole pitch for a solo doctor: less friction to start, less charting to carry.

## Where Patient Square wins for a solo doctor

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

On a real Tuesday OPD, here's what that means. You start the visit; a live transcript runs as you talk. The patient speaks Hindi, you answer in English, they slip into Marathi, and it keeps up. The moment they leave, a structured SOAP note is ready in clean clinical English, with ICD-10 suggestions and a prescription draft to review and sign. No typing after clinic. Audio isn't stored; it's processed in memory and discarded once the note drafts. Start with the ₹1,599 Assist scribe tier, or take the ₹2,399 Copilot tier to add the bundled AI Copilot EHR so records live in one place. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The honest limits, because a roundup that only sells is useless. Languages are input only: the note comes out in English, not Hindi. The prescription is a draft, not e-prescribing to a pharmacy. ICD-10 is suggestions, not a coding engine. And ABDM integration is on the roadmap, not live, so records are born digital and ABDM-ready on your timeline but we won't claim ABHA linking as shipped. If any of those is a dealbreaker, a different tool may fit better. For more, our [AI scribe for solo doctors post](/in/blog/ai-scribe-for-solo-doctors-india/) and [AI scribe cost for a solo doctor](/in/blog/ai-scribe-cost-for-solo-doctor-india/) go deeper.

## The pricing math for one doctor

One doctor, so the sums are simple. Patient Square is per clinician, and a single-doctor clinic pays exactly one seat.

| Plan | Annual, per mo (ex-GST) | With 18% GST | Annual all-in (with GST) |
|---|---|---|---|
| Assist (scribe) | ₹1,599 | ~₹1,887 | ~₹22,644 |
| Copilot (scribe + AI EHR) | ₹2,399 | ~₹2,831 | ~₹33,972 |

That's the full year, including GST, no setup fee. HealthPlix's published plans (₹11,999 Pro, ₹17,999 Elite per doctor per year) are the other transparent comparison, and cheaper on paper if you don't need the ambient scribe. Practo Ray's third-party-estimated ₹2,000 to ₹4,000 a month is disclosed only after a demo, so you can't line it up without a call. The point of transparent pricing isn't that Patient Square is always the lowest sticker; it's that a solo doctor can compare the visible options on the page and only sit through a demo to price the opaque one. For the broader ranges, the [clinic software cost guide](/in/blog/clinic-software-cost-guide-india/) covers the field.

## When another tool is the better call

The fork, stated straight. Practice Copilot can use Patient Square EHR as the system of record or work alongside an existing EHR, and there are solo doctors better served elsewhere.

Choose HealthPlix if your priority is a published-price EMR with regional-language prescription printing and you don't need an ambient AI scribe. It's a mature per-doctor EMR with a clear rate. Choose Practo Ray if getting found and booked through Practo's patient network is central to your practice, and you'll accept a demo to learn the price. That patient-acquisition angle is a real strength Patient Square doesn't claim.

Choose Patient Square if your main daily pain is documentation and you value a price you can see. Practice Copilot can use Patient Square EHR from the Copilot tier or work alongside an existing EHR through the Assist tier. That's most solo doctors whose evenings disappear into charting.

The split isn't quality; all three are solid. It's whether your bottleneck is notes, records, or bookings. Buy for the one that actually hurts.

## How to decide in a week

1. Name your bottleneck: "I chart after clinic" points to Patient Square; "I need more patients" points to Practo Ray; "I want a cheap published EMR" points to HealthPlix.
2. Decide between the alongside Assist path and Patient Square EHR from the Copilot tier based on whether your records already live somewhere workable.
3. Get every price as an all-in annual figure with GST, and refuse any large setup fee for a single-doctor clinic.
4. Match the output: note, ICD-10 suggestions, prescription draft, and confirm the note language you need.
5. Trial on a real clinic day, not a scripted demo. A busy Tuesday tells you more than any feature sheet.

Encryption and audit posture sit on the [security page](/in/security/), and the price ladder with no asterisks is on the [pricing page](/in/pricing/). Book a short demo to see the note against your own visits, then run the 7-day trial on a real week. For a solo doctor drowning in charting, an ambient scribe at a published rate is usually the one that pays for itself.

---

## Best EHR with AI Scribe Built In: Our Honest 2026 Pick
https://patientsquare.com/us/blog/best-ehr-with-ai-scribe-built-in/
Published 2026-07-06 · Updated 2026-08-27 · Tags: best, roundup, ehr, ai-scribe

Most EHRs bolt an AI scribe on as a paid add-on. We compare 5 options and pick the one that ships scribe + EHR as a true bundle from $119/mo.

A built-in scribe is developed by the same company that makes the EHR, ships inside the same subscription, and requires no separate vendor contract, login, or per-seat add-on fee. A bolt-on scribe is a third-party tool layered over the EHR: you pay for it separately, manage a second vendor relationship, and copy-paste or push notes between two systems. The difference shows up in pricing simplicity and single-vendor accountability.

If you're shopping for an EHR and an AI scribe at the same time, our pick is Patient Square. The Copilot tier ($119/mo per clinician on annual billing) ships the AI Copilot EHR and the ambient scribe in one subscription. One vendor, one contract, one price. Most competitors make you buy the scribe separately, from a different company, at an extra monthly fee.

That bundled framing is the wedge this post is built around. Before you evaluate five platforms with overlapping feature lists, it helps to know what "built in" actually means, because vendors use the phrase loosely, and the difference between genuinely native and "partnership-embedded" shows up in your bill and your support queue.

Book a demo to see the scribe and EHR running together on a real visit, or request a 7-day trial to test with your own patients after setup.

> **Key takeaways**
>
> - Most EHRs that offer AI scribing use a partner integration or a separate add-on, not a single-vendor bundle.
> - Patient Square's Copilot tier ($119/mo annual) ships the ambient scribe and the AI Copilot EHR in one subscription, with no per-note fees and unlimited visits.
> - Elation, NextGen, and DrChrono each have native or embedded scribes, but none publish a bundled price that includes both EHR and scribe in one line item.
> - athenahealth's Ambient Notes was in limited availability as of mid-2026; no separate price is listed.
> - If you already own an EHR you like and just want the scribe layer, the Assist tier ($79/mo annual) covers that without the bundled EHR.

| Vendor | Scribe type | EHR included | Published bundle price | Free trial |
|---|---|---|---|---|
| **Patient Square (Copilot)** | Native, same vendor | Yes (AI Copilot EHR) | $119/mo annual | 7 days |
| Elation Health | Native (Note Assist) | Yes | Not published | Demo-led |
| NextGen (Enterprise/Office) | Native (Ambient Assist) | Yes | Not published | Demo-led |
| DrChrono (EverHealth Scribe) | Partner (CarePilot, embedded) | Yes | Not published | Demo-led |
| athenahealth (Ambient Notes) | Native, limited availability | Yes | Not published | Demo-led |
| Practice Fusion | None native (third-party only) | Yes | EHR separate, scribe separate | Yes (EHR) |

## What "built in" actually means

Vendors describe their AI scribes as "built in," "embedded," "native," and "integrated," often interchangeably. The terms map to meaningfully different things.

**Same-vendor bundle**: The EHR company wrote the scribe, ships it inside the same product, and prices it in the same subscription. One contract, one support line, one invoice.

**Partner-embedded**: The scribe is built by a third party but installed directly into the EHR's workflow, often via a marketplace or an OEM deal. You typically don't manage two separate logins, but the vendors are different companies, and the scribe's roadmap is controlled elsewhere.

**Marketplace add-on**: The EHR has a partner directory. You find a scribe tool, sign up separately, and wire it in yourself. Two subscriptions, two support queues, two renewal conversations.

Most EHRs in 2026 operate in the second or third bucket. A single company building both the scribe and the EHR under one roof: that's the shortest list.

## Our honest pick: Patient Square Copilot

AI Medical Scribe by Patient Square is one module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

The scribe and the AI Copilot EHR ship together at the Copilot tier. That's $149/mo month-to-month or $119/mo on annual billing, per clinician. Unlimited visits and notes, no per-note metering, no encounter fees.

**Who this fits well:**

- Solo or small-group practices (1–5 clinicians) shopping for a complete system, not piecing one together
- Practices that want one vendor to call when something breaks, not a scribe company pointing at the EHR company and vice versa
- Clinicians who want to see real published pricing before getting on a call

**Honest limitations:**

The AI Copilot EHR is a bundled AI EHR. We haven't enumerated every sub-module here because the product is GA and growing. If you have specific needs around labs, patient portal, or billing integrations, book a demo and ask directly. We'd rather you know what you're getting than discover a gap post-signup.

The prescription output is a draft for your review. It's not e-prescribing and nothing sends on its own: the draft reflects what was decided in the visit, and you review, adjust, and sign it. The scribe doesn't screen for drug interactions, dosing, or contraindications. That safety check stays with you, the prescriber, exactly as it does today.

Audio is never stored. It's processed in memory and discarded once the note drafts.

For practices that don't want to switch EHRs and just need the scribe layer, the Assist tier at $79/mo annual covers the scribe, ICD-10 suggestions, and eRx drafts with no bundled EHR. You'd export notes as PDF, HL7, or FHIR into whatever chart system you're already using. For more on that use case, see our post on [using an AI scribe with any EHR export](/us/blog/ai-scribe-any-ehr-export/).

## The alternatives, honestly

### Elation Health (Note Assist)

Elation is a strong primary care EHR. Note Assist is genuinely native, built by Elation, embedded in the chart, not a partner tool you separately configure. In March 2026, Elation also announced AI billing workflows with agentic automation. That's a real differentiator, especially if revenue cycle sits near the top of your evaluation.

The problem: no published price for Note Assist. You need a demo call to find out what the scribe tier costs on top of the base EHR. For practices that want to compare options on a spreadsheet first, that's a friction point Patient Square doesn't have.

### NextGen Healthcare (Ambient Assist)

Elation skews primary care and small practice. NextGen is the next step up. Ambient Assist is native to both NextGen Enterprise and NextGen Office, and the scribe drops structured notes and ICD-10 suggestions directly into the chart. Rural FQHCs that piloted the tool reported meaningful drops in after-hours charting, which is a real problem at that scale.

Pricing is sales-led. Solo and two-clinician shops will likely find the implementation cycle and contract structure heavier than necessary. This one is built for practices with more than a handful of seats.

### DrChrono (EverHealth Scribe)

DrChrono is interesting. They launched EverHealth Scribe in March 2026 via a CarePilot partnership, and it's embedded in the DrChrono workflow, no separate login. Early pilot data from CarePilot cited eight minutes saved per visit and a 32% increase in same-day claim submissions. Worth noting those are CarePilot's own metrics from their pilot, not an independent study.

Pricing isn't published separately from the base DrChrono subscription. And the partnership structure is something to think about: if CarePilot's roadmap diverges from DrChrono's down the line, that embedded scribe could look different at renewal.

### athenahealth (Ambient Notes)

athenahealth is rolling Ambient Notes out natively into athenaOne. As of mid-2026 it was in limited availability, getting added to athenaOne subscribers' workflows with no separate price listed. Newsweek quoted athenahealth calling it "foundational" to their AI direction, which is a directional signal, not a shipping date.

If you're already on athenaOne, ask your rep about the rollout timeline for your region. If you're not: athenahealth is enterprise-priced and enterprise-procured. Not a self-serve evaluation track.

### Practice Fusion

No native scribe. Every AI documentation option for Practice Fusion is a third-party tool: Freed, Tali, DeepCura, and a few others. You paste or export notes into the chart. Two subscriptions, two vendors, two renewal cycles. Fine if you know going in, frustrating if you assumed "AI scribe" was part of the package.

## The price math on a bundle vs. two separate subscriptions

Say you're a solo clinician seeing 20 patients a day, 20 days a month: 400 visits.

| Approach | EHR cost (est.) | Scribe cost (est.) | Total/mo | Per-visit |
|---|---|---|---|---|
| EHR + standalone scribe | ~$100–200/mo | $89–149/mo (typical) | ~$189–349/mo | ~$0.47–0.87 |
| Patient Square Copilot (bundle) | n/a | n/a | $119/mo (annual) | ~$0.30 |

The scribe-only market runs $89–149/mo for popular tools. Stack that on a mid-tier EHR and you're at $190–350/mo before any premium features. Patient Square's Copilot tier at $119/mo on annual billing covers both.

The math isn't magic. If you already own an EHR and aren't looking to move, adding a separate scribe subscription at $89/mo may still be the right call. But if you're starting fresh or evaluating your current stack, the bundle structure is a simpler line item.

See our post on [comparing standalone AI scribe vs. switching EHRs](/us/blog/ai-scribe-vs-new-ehr/) for a longer treatment of when the switch cost is worth it.

## When a bolt-on or separate scribe is the better fit

This post has a point of view, so let's be honest about where it doesn't apply.

**You already own a well-integrated EHR and like it.** Switching EHRs mid-practice is expensive in training time and data migration, even if the new system is better on paper. If Elation, NextGen, or athenaOne is working well for you and a native scribe is coming (or already available), switching to a new EHR for the bundled scribe doesn't pencil out.

**You need deep revenue-cycle features.** Some enterprise EHRs have billing, coding, and RCM workflows that took years to build. A bundled scribe with a simpler EHR won't replicate that. If RCM depth is the top of your evaluation list, weight it accordingly.

**You're a large health system.** Practice Copilot is built for independent practices and clinics. Hospital Copilot is the separate, demo-priced hospital product and can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. A multi-site system should still verify every required enterprise module, integration, and migration path against Epic, Oracle Health, or another incumbent.

**You want to try the scribe without committing to a new EHR.** The Assist tier at $79/mo annual (or $99/mo month-to-month) covers the scribe with no bundled EHR. You keep your existing chart and use the [EHR-ready export (PDF · HL7 · FHIR)](/us/blog/ai-scribe-any-ehr-export/) to get notes into it.

## How to evaluate in a week

Skip the side-by-side spec sheet. Here's what actually moves the needle:

1. **Run the scribe on real visits.** Every ambient tool sounds good in a scripted demo. Use your own visit types, your own patient phrasing, your own specialty templates. A family medicine visit sounds different from a psychiatry note.
2. **Ask every vendor one audio question.** Where does the audio go after the note drafts? Stored or discarded? For how long? If the answer is vague, it's a red flag. Ours is discarded in memory once the note is ready.
3. **Check the note structure, not just the summary.** Does it produce a structured SOAP note or a freeform paragraph? ICD-10 suggestions or just a narrative? A prescription draft or just a med list? The specifics matter for your workflow.
4. **Confirm the BAA situation.** For small practices, some enterprise tools reserve the BAA for larger accounts or make it a separate negotiation. Patient Square offers a BAA to every customer.
5. **Understand what "support" means.** A self-serve tool with a chat widget is different from an enterprise platform with a named implementation manager. Know which one you're buying.

The [pricing page](/us/pricing/) has the full tier breakdown with no asterisks. If you want to compare against your current setup before committing, book a short demo and we'll run the scribe on a sample visit in your specialty so you're comparing notes you'd actually sign, not marketing screenshots.

For practices evaluating across the full small-practice EHR market, our [best EMR for small practice guide](/us/blog/best-emr-for-small-practice/) covers the field without the scribe lens. For the inverse question, keeping your EHR and adding just the scribe layer, [free EHR plus AI scribe vs. standalone](/us/blog/free-ehr-ai-scribe-vs-standalone/) walks through that. And if the family practice use case is your context, [best EHR for family practice](/us/blog/best-ehr-for-family-practice/) narrows it further.

---

## Hospital Revenue Cycle Management in India: The Real Chain
https://patientsquare.com/in/blog/hospital-revenue-cycle-management-india/
Published 2026-07-06 · Updated 2026-09-08 · Tags: revenue-cycle-management, hospital-rcm, cashless, nhcx, pmjay, india

How the revenue cycle actually runs in an Indian hospital: registration, TPA cashless pre-auth, NHCX claims, PMJAY billing, denials, and the note that feeds it all.

Revenue cycle management (RCM) is the whole chain a hospital runs to turn a treated patient into collected money: registration and estimate, cashless pre-authorisation with the TPA, service capture and billing, claim submission, denial handling, scheme billing under PMJAY or CGHS, and final collection. In India the cashless and scheme layers make it more complex than a straight cash bill, because the insurer, the TPA, and the state health agency each have their own rules and timelines.

It's the 28th at a 150-bed hospital in a Tier-2 city near Pune. The billing desk has a queue at the counter, three cashless files open on one screen, and a WhatsApp thread with a TPA co-ordinator who last replied at 11:40am. Two discharges are stuck because the pre-auth came back with a query. The revenue for the month is real, treated, documented somewhere. It just hasn't turned into money yet.

That gap, between care delivered and cash collected, is the revenue cycle. In an Indian hospital it runs through more hands than most vendors admit, and the weakest link is almost never the billing engine.

> **Key takeaways**
>
> - The Indian revenue cycle has a cashless and a scheme layer on top of ordinary billing, so a claim passes through the TPA, sometimes the insurer, and sometimes a state health agency before it settles.
> - IRDAI's 29 May 2024 Master Circular puts a one-hour clock on cashless authorisation and a three-hour clock on discharge authorisation, and both depend on a pre-auth that's complete on first read.
> - NHCX was nationally launched on 29 June 2026, while NHA's July review still described an NHCX–HMIS pilot. Verify production support across your own participants.
> - AB-PMJAY covers ₹5 lakh per family a year across 36,229 empanelled hospitals; scheme billing runs on its own tariff master and portal, separate from private cashless.
> - Most denials trace back to documentation, not the billing software. That's the part a hospital can fix first.

---

## What the revenue cycle actually covers

Think of it as one chain with several handoffs, each of which can leak money.

A patient registers and gets a UHID. The front desk gives an estimate. If it's a cashless case, someone raises a pre-authorisation with the TPA and waits for approval before the surgery is scheduled. Services get delivered and captured against a tariff. The bill is assembled with GST where it applies. The claim goes out. It either clears, gets queried, or gets partly disallowed. Collections chase whatever the insurer, the scheme, or the patient still owes. Then the finance head reconciles all of it at month-end and finds the shortfall.

Nine steps, and only two or three of them are things the billing module does well on its own. The rest is coordination between the clinical side, the insurance desk, and the counter.

## Where an Indian hospital's cycle gets complicated

A cash-paying patient is simple. You treat, you bill, they pay at discharge. That's a small and shrinking share of most hospitals' revenue.

The volume sits in cashless and scheme cases, and each one splits the cycle into a parallel track that runs on someone else's rules.

### The TPA and cashless track

A Third Party Administrator runs the cashless desk on the insurer's behalf. It processes the pre-authorisation, assesses the claim, and settles on the insurer's account. Worth being precise about one thing: a TPA can flag a claim as not admissible, but it can't deny it. Only the insurer can repudiate a claim, and it has to state reasons against the policy terms (IRDAI Policyholder portal). So a cashless rejection that lands back through the TPA traces to an insurer decision. The [TPA and cashless glossary](/in/blog/tpa-full-form-cashless-explained/) walks through that chain if your desk staff are new to it.

The pre-auth is where the money either flows or stalls. It's built from the treating doctor's diagnosis, indication, and plan. If that documentation is complete and consistent, the request is approvable on first read. If it's a phrase in a text box, the TPA sends a query, and the whole thing waits.

### The IRDAI clock

The 29 May 2024 IRDAI Master Circular put hard timelines on this. The insurer must decide on a cashless authorisation request within one hour, and grant final discharge authorisation within three hours of the hospital's discharge request (IRDAI Master Circular, 29 May 2024). If final authorisation is delayed past three hours, the extra hospital charges from that delay are borne by the insurer.

Here's the operational catch. The clock is only useful to the hospital if the pre-auth is clean. A query resets the practical timeline and holds the bed. Discharges pile up in the afternoon because the documentation to close them arrived late. The [IRDAI cashless timelines](/in/blog/irdai-cashless-rules-doctors/) breakdown covers exactly where a note sits on that clock.

### NHCX and the claims rail

For years the billing desk kept a mental map of which insurer wants which portal and which TPA still takes a PDF over email. The National Health Claims Exchange is aimed at that mess. NHCX is a single digital channel, built by the National Health Authority under ABDM and shaped with IRDAI, for hospitals, insurers, and TPAs to pass claim messages in one FHIR-based format.

Where does it actually stand? The Ministry announced NHCX's national launch for 29 June 2026, and NHA's 17 July review described the NHCX–HMIS implementation as a pilot with an implementation roadmap. That supports rollout, not a universal hospital cut-over. Ask whether your hospital, payer or TPA, and software have completed your claim type in production. There is a financial nudge attached: Corrigendum 7 lists ₹200 per eligible AB PM-JAY claim or 10% of claim value, whichever is lower, for the facility, plus ₹10 for the DSC, subject to its NHCX, ABHA, FHIR, security, version, and cap conditions. The [NHCX guide](/in/blog/nhcx-claims-explained-clinics/) explains the rail, while the [source-dated DHIS guide](/in/blog/abdm-incentives-for-doctors/) owns the volatile incentive rules.

One thing NHCX doesn't change: the IRDAI rules and the documentation. It moves the message faster. It doesn't write the note.

### The PMJAY and scheme track

Then there's the scheme layer, which runs on its own tariff and its own portal. AB-PMJAY provides ₹5 lakh per family a year for secondary and tertiary care, across 36,229 empanelled hospitals nationwide, covering 1,961 procedures across 27 specialties (Press Information Bureau, 17 March 2026). CGHS and state schemes add their own package rates and pre-authorisation flows.

Scheme billing isn't cashless-with-a-different-logo. The package rate is fixed, the documentation requirements are specific to the procedure, and a mismatch between the coded procedure and the operative note is a straight rejection. Hospitals that run a heavy PMJAY load usually have a separate desk for it, because the workflow shares almost nothing with private cashless beyond the word "cashless."

## What software should own, and what it can't

A good hospital RCM setup handles the deterministic work without drama:

- Registration, UHID, and the patient estimate at the front desk.
- Tariff and package pricing, including scheme masters and TPA rate lists.
- GST-correct invoicing and receipts.
- Pre-auth request generation and a claim-tracking status board.
- A denial worklist so nothing ages past the appeal window unseen.

That list is mature in most Indian hospital systems. If you want the module-by-module view of where each of these lives, the [hospital management system breakdown](/in/blog/hospital-management-system-explained/) maps it.

What software can't manufacture is the clinical content the claim is built from. The billing team codes what the note supports. When the operative note says "as above" and the discharge summary is three lines a resident typed at 11pm, the coder guesses, downcodes, or leaves the field blank. That's the root of a large share of denials, and no billing engine fixes it, because the problem starts in the consulting room and the OT, not the finance office.

I'll say it plainly: most hospitals buy more RCM software when the actual bottleneck is documentation. The new module changes the plumbing, not the note that feeds it.

## Where the denials really start

Trace a denied cashless claim backwards and it usually lands in one of four places.

The diagnosis on the pre-auth doesn't match the final coded diagnosis. The indication for surgery isn't documented in a way the TPA's medical officer accepts. The discharge summary is missing the continuity detail a scheme auditor needs. Or the procedure code and the operative note simply disagree. Each of those is a documentation defect wearing a billing costume.

The finance head sees it as a rejection rate. The billing manager sees it as rework. The reason sits upstream, in how the encounter got written down under time pressure, in the two minutes a doctor had between one patient and the next.

## Where Hospital Copilot fits

Documentation and claim submission are different problems, and Patient Square works on the first one only.

Hospital Copilot and Practice Copilot are the products here, with an ambient documentation module inside them. During the consult or the ward round, the module listens and drafts a structured note, ICD-10 code suggestions, and a prescription draft, ready to review and sign a couple of minutes after the encounter. That's the raw material the pre-auth desk builds on.

For the revenue cycle, that means the coder is reading a documented encounter instead of interpreting a terse string. The indication, the diagnosis, and the plan are present and consistent, so the pre-auth goes out approvable on first read more often, and fewer of them bounce back as queries against the IRDAI clock.

A few design choices matter for an Indian hospital. Ward rounds and OPD consults come in braided Hindi and English, so the module takes code-mixed speech on input and returns the note in clean clinical English, which is what the medico-legal record and the claim need. The ICD-10 output is a suggestion the clinician confirms, not an auto-code. The prescription is a draft the doctor reviews and signs. And visit audio is processed in memory and discarded once the note drafts, so there's no recording sitting on a server. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

To be straight about the boundary: this is not a claims-submission tool. Hospital Copilot does not connect to NHCX, any insurer, or any TPA, and it does not file pre-authorisations. ABDM and NHCX integration are on our roadmap, not shipped, and we won't wear an ABDM badge we don't hold. The hospital can use the complete Patient Square HIS/EHR or keep an incumbent HIS/EHR, but live NHCX transacting still requires a claims platform that provides it.

## Fix the cycle in the order that pays

If your rejection rate is climbing, the instinct is to look at the billing software or the insurance desk. Look at the note first. It's cheaper to fix and it's usually the real leak.

Run the trace on your last 50 denied cashless claims. Sort them by root cause. If more than a third come back to thin or late documentation, a new RCM module won't move your numbers, and a documentation layer might. That 150-bed hospital on the 28th doesn't have a billing-engine problem. It has two discharges stuck behind a query on a pre-auth that went out incomplete.

<a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">Compare the options</a> to see what an ambient consult produces as a note, and how much cleaner a pre-auth reads when the encounter behind it is fully written down. Or start with the [hospital management system map](/in/blog/hospital-management-system-explained/) if you're still working out which module actually owns which part of your cycle.

---

## Best EHR for a Nursing Home in India (2026)
https://patientsquare.com/in/blog/best-ehr-for-nursing-home-india/
Published 2026-07-03 · Updated 2026-08-27 · Tags: india, comparison, ehr, nursing-home

Best EHR for a nursing home in India: the honest options for documentation and resident records, plus transparent per-doctor pricing from ₹2,399/mo + GST.

The Indian nursing-home software market is thin and mostly repurposed clinic or hospital systems, so match the tool to your real need. If your burden is doctor documentation and clean resident records, Patient Square's Practice Copilot fits: an ambient AI Medical Scribe plus a bundled AI Copilot EHR from ₹2,399 per clinician per month (annual, ex-GST). If you need bed management, nursing rosters, and IPD-style operations, look at a hospital HMS or Hospital Copilot (demo-priced) instead.

The Indian nursing-home software market is thin, and most of what's sold is a clinic or hospital system repurposed, so the best EHR for your nursing home depends on which problem you're solving. If it's doctor documentation and clean resident records, Patient Square's Practice Copilot fits: an ambient AI Medical Scribe plus a bundled AI Copilot EHR from ₹2,399 per clinician per month (annual, ex-GST). If it's bed management, nursing rosters, and IPD-style operations, that's a hospital HMS or Hospital Copilot (demo-priced), not a documentation tool. The scribe price is on the [pricing page](/in/pricing/), and you can book a demo to see a resident note in about two minutes.

> **Key takeaways**
>
> - India has no strong nursing-home-specific EHR category; most tools are repurposed clinic or hospital systems. Scope to your real need.
> - For doctor documentation and resident records, Patient Square fits: ambient scribe plus bundled AI EHR from ₹2,399/clinician/mo (annual, ex-GST).
> - For beds, rounds, and nursing rosters, that's hospital-operations tooling: a full HMS or Hospital Copilot (demo-priced), not a solo documentation tier.
> - Most nursing homes overbuy hospital modules they don't use. Split the need before you buy.
> - Records are born digital and export-ready (PDF, HL7, FHIR). ABDM integration is roadmap, not live; verify any "ABDM today" claim in production.

## The honest options at a glance

Before recommending anything, name the split. A nursing home has two distinct software needs, and one tool rarely does both well.

| Need | What it is | Where it fits |
|---|---|---|
| Doctor documentation + resident records | Notes per visit, a clean shared chart per resident | Patient Square Practice Copilot; per-doctor EMRs like HealthPlix |
| Bed and IPD operations | Bed status, admissions, rounds, discharge | Hospital HMS; Hospital Copilot (demo-priced) |
| Nursing care logs + rosters | Daily-care records, staff shifts, medication rounds | Dedicated nursing/LTC operations tools |
| Billing + pharmacy stock | Charges, in-house pharmacy | HMS suite modules |

Most of the "best nursing home software" lists mix these together. Deciding which row is your actual bottleneck is the whole job. Overbuy the operational modules you don't run and you pay for a hospital you don't have.

## Where Patient Square fits a nursing home

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

For a nursing home, the fit is specific: the doctor-side documentation. A visiting physician doing rounds on 20 residents carries the same charting load as a busy OPD. The scribe listens during each visit, in Hindi, English, or a regional language, even code-mixed, and hands back a finished note in clean clinical English the moment the visit ends, with ICD-10 suggestions and a prescription draft to review and sign. The Copilot tier's bundled AI Copilot EHR keeps one digital record per resident, export-ready as PDF, HL7, and FHIR.

That's the honest scope, and here's what it isn't. Practice Copilot doesn't manage beds, nursing rosters, medication rounds, or daily-care logs. Those are operational modules, and in Patient Square they live in Hospital Copilot (demo-priced), not the solo tiers. ICD-10 is suggestions only, the prescription is a draft not e-prescribing, and ABDM integration is roadmap, not live. If your nursing home's core need is bed and roster operations, this isn't your tool; if it's fast, defensible documentation of resident visits, it is. For the documentation angle deeper, see our [AI scribe for solo doctors post](/in/blog/ai-scribe-for-solo-doctors-india/).

## Why documentation matters more than you'd think in elder care

Elder-care visits are the ones you most want on record. Residents are often on multiple medications, seen repeatedly, and the ones whose families are most likely to question care later. A complete note per visit is both good medicine and the defence that holds up.

The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. In a nursing home, where the same residents are seen again and again and complications can be slow-building, a thin or missing note is a real exposure. India sees an estimated 65,000 medical-negligence cases reach courts and consumer forums a year, and the record is what wins them.

An ambient scribe closes that gap without adding minutes to a round. The doctor talks; the note writes itself. So the case for the tool in elder care isn't productivity for its own sake. It's that every resident visit ends with a complete, defensible record, even when the visiting doctor is moving fast through a full floor.

## The pricing picture

There's no standard India price for nursing-home software; most vendors quote per bed or per module. Global long-term-care EHRs are typically priced per bed per day, which doesn't map cleanly to how Indian nursing homes buy or operate, so treat those quotes with caution.

For the documentation-and-records slice, Patient Square is transparent per clinician. For a fuller picture of how single-doctor documentation costs work, [AI scribe cost for a solo doctor in India](/in/blog/ai-scribe-cost-for-solo-doctor-india/) runs the per-visit math, and [best clinic software for a single doctor in India](/in/blog/best-clinic-software-for-single-doctor-india/) is the closest roundup for small nursing-home setups with one or two visiting doctors:

| Plan | Annual, per mo (ex-GST) | With 18% GST | What a nursing home gets |
|---|---|---|---|
| Assist | ₹1,599 | ~₹1,887 | AI scribe, ICD-10 suggestions, eRx drafts, scheduling |
| Copilot | ₹2,399 | ~₹2,831 | Everything in Assist, plus the bundled AI Copilot EHR |

If a nursing home has one or two visiting doctors, that's the whole software bill for documentation and records, priced on the page. Bed and IPD operations, if you need them, are a separate quote through a hospital HMS or Hospital Copilot. Splitting the buy this way usually beats one big suite quote where half the modules never get switched on. For the broader ranges, the [hospital management software price guide](/in/blog/hospital-management-software-price-india/) covers the operational end.

## When a nursing home needs more than Patient Square

The clear fork. If your nursing home runs like a small hospital, a documentation platform isn't enough on its own.

Look at a full HMS or Hospital Copilot (demo-priced) if you manage inpatient beds and admissions, need nursing rosters and medication-round tracking, run an in-house pharmacy store, or handle TPA and government-scheme claims. Those are operational systems, and no AI scribe replaces them. A dedicated long-term-care operations tool may also cover the daily-care logging that nursing staff, not doctors, maintain.

Choose Patient Square if the software problem you actually have is doctor documentation: visiting physicians losing time to charting rounds, resident records that should be clean and defensible, and you want the price on the page. Pair it with an operations tool if you need both, rather than forcing one system to do everything.

The split is about whether your bottleneck is care operations or medical documentation. Be honest about which, and don't pay for the other.

## How to choose in a week

1. Write down your top software pain in one line. "Our visiting doctors chart forever" points to Patient Square; "we can't track beds and rounds" points to an operations tool.
2. Separate the doctor-documentation need from the nursing-operations need. They're different tools, and one big suite rarely does both well.
3. Get any per-bed or per-module quote as an all-in annual total, ex-GST, and challenge every module you won't actually use.
4. For documentation, match the output: a note per resident visit, ICD-10 suggestions, a prescription draft, and an export-ready record.
5. Trial on a real rounds day, checking whether notes land finished as the doctor moves floor to floor.

Encryption and audit posture are on the [security page](/in/security/), and the transparent price ladder is on the [pricing page](/in/pricing/). Book a demo to see a resident note against your own rounds, then run the 7-day trial on a real week. For documentation, Patient Square is a clean, honestly-priced fit; for bed and roster operations, buy the tool built for that and don't overpay for a suite.

---

## Best EMR for a Multispecialty Clinic in India (2026)
https://patientsquare.com/in/blog/best-emr-for-multispecialty-clinic-india/
Published 2026-07-03 · Updated 2026-08-27 · Tags: india, comparison, emr, multispecialty

Best EMR for a multispecialty clinic in India: specialty-aware templates, shared records, and transparent per-doctor pricing from ₹1,599/mo + GST, compared.

It depends on where your pain is. If billing, lab, and pharmacy modules across many specialties are the priority, a broad suite like MocDoc fits. If the daily drain is documentation across different specialties with shared patient records, Patient Square's Practice Copilot is the AI-native pick: specialty-aware templates out of the box, an ambient scribe, and a bundled AI EHR from ₹2,399 per doctor per month (annual, ex-GST). Match the tool to your bottleneck, not to a feature checklist.

For a multispecialty clinic in India, the best EMR is the one that matches your real bottleneck. If it's documentation across different specialties with a shared patient record, Patient Square's Practice Copilot is the AI-native pick: specialty-aware templates ready out of the box, an ambient AI Medical Scribe, and a bundled AI Copilot EHR from ₹2,399 per doctor per month (annual, ex-GST). If your drain is deep billing, pharmacy, and lab modules across specialties, a broad suite like MocDoc fits better. The price is on the [pricing page](/in/pricing/), not behind a demo, and you can book a demo to see a specialty note in about two minutes.

> **Key takeaways**
>
> - Match the EMR to your bottleneck: documentation and shared records, or deep billing/pharmacy/lab modules. Different tools win each.
> - Patient Square ships specialty-aware templates out of the box, an ambient scribe, and a bundled AI EHR from ₹2,399/doctor/mo (annual, ex-GST).
> - Broad suites (MocDoc, Insta by Practo) win when you need IPD, pharmacy stock, or lab modules tightly integrated.
> - Most suites are quote-only; HealthPlix publishes per-doctor annual plans (₹11,999/₹17,999); Patient Square is transparent per clinician.
> - India-specific: multilingual capture matters when patients and doctors switch languages mid-consult. Notes come out in clean English.

## The pick at a glance

Here's the honest comparison up front, because a multispecialty clinic is deciding between different kinds of tool, not different versions of the same one.

| Option | Best for | Pricing | Specialty templates | AI scribe | Bundled EHR |
|---|---|---|---|---|---|
| Patient Square (Practice Copilot) | Documentation-heavy multi-specialty clinics wanting shared records | ₹2,399/doctor/mo (annual, ex-GST), transparent | Yes, out of the box | Yes, ambient | Yes, at Copilot tier |
| MocDoc | Clinics needing broad EMR + billing + lab + pharmacy | Quote-only | Yes | No | EMR/EHR module |
| Insta by Practo | Mid-size clinics/hospitals wanting an integrated suite | Quote-only | Yes | No | Yes |
| HealthPlix | Solo/small multi-specialty wanting published per-doctor EMR | ₹11,999–₹17,999/yr per doctor | Yes | No | EMR |
| Practo Ray | Clinics wanting scheduling + records + patient booking | Third-party est. ₹2,000–₹4,000/mo, disclosed on demo | Some | No | Records |

The line that separates them isn't quality. It's whether your problem is writing notes fast across specialties or running billing, lab, and pharmacy across them.

## What a multispecialty clinic actually needs from an EMR

A multispecialty clinic has a specific problem a single-specialty clinic doesn't: one system serving a dermatologist, a cardiologist, a paediatrician, and a gynaecologist, each of whom documents differently. Get this wrong and everyone fights a generic form.

Four things matter more than the feature count.

Specialty-aware templates come first. A cardiology note and a derm note aren't the same shape, and the EMR should give each specialty an appropriate structure without a consultant building it. Next, a shared patient record: a patient seen by two specialists in the same clinic should have one chart, not two disconnected notes. Then per-doctor pricing that scales cleanly, so adding a fifth specialist doesn't trigger a fresh negotiation. And fast documentation, because multispecialty means volume; if doctors are typing notes after clinic, the EMR is adding burden, not removing it.

Patient Square is built around the last two hard, and ships the first two. Specialty-aware templates are ready out of the box, the ambient scribe adapts to each room's conversation, and the Copilot tier's bundled AI EHR keeps one record per patient across specialties.

## Where Patient Square is the AI-native pick

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

For a multispecialty clinic, three things do the work. The scribe listens across specialties and hands each doctor a finished note the moment the patient leaves, in clean clinical English, even when the consult ran in Hindi, Tamil, or code-mixed Hinglish. Specialty-aware templates mean the paediatrician and the orthopaedist aren't sharing one generic form. And the bundled AI Copilot EHR at the ₹2,399 Copilot tier keeps records in one place, export-ready as PDF, HL7, and FHIR.

Two honest limits. ICD-10 arrives as suggestions, not a coding engine; there's no CPT or E&M behind it. And records are born digital and ABDM-ready on your timeline, but ABDM integration is on our roadmap, not shipped, so we won't claim ABHA linking as live. If deep per-specialty billing or a diagnostic-lab LIMS is central to your evaluation, weigh a broader suite. For the wider field, our [best EMR software roundup](/in/blog/best-emr-software-india-roundup/) and [AI scribe for multi-specialty clinics post](/in/blog/ai-scribe-for-multi-specialty-clinics-india/) go deeper.

## The pricing picture, without the quote wall

Most multispecialty EMR pricing is quote-only, stacked per user plus per module plus a setup fee. A 5-doctor clinic can land ₹2,00,000 to ₹6,00,000 a year depending on modules, and you can't see the number without two demos.

Patient Square prices per clinician on the page. Copilot with the bundled AI EHR is ₹2,399 per doctor per month on annual billing, ex-GST. Five doctors work out to ₹1,43,940 a year, plus 18% GST (about ₹1,69,849 all in), EHR included, no setup fee. HealthPlix is the other transparent option, publishing per-doctor annual plans at ₹11,999 (Pro) and ₹17,999 (Elite). The point isn't that transparent is always cheapest; it's that you can compare Patient Square and HealthPlix on the page and only have to sit through a demo to price the rest.

Do the with-GST math once and budget from the real number. For the broader cost picture, the [clinic software cost guide](/in/blog/clinic-software-cost-guide-india/) lays out the ranges. If your group is large enough that HMS pricing has come up in your search, [HMS software cost in India](/in/blog/hms-software-cost-breakdown-india/) decodes the per-bed and per-module structure so you can see what you'd actually be buying. And for the full breakdown of every hidden EHR cost, [EHR software cost guide](/in/blog/ehr-software-cost-india-buyers-guide/) names the setup, AMC, and per-user fees that make the sticker price misleading.

## When a broad suite beats Patient Square

The honest fork. Patient Square is documentation-and-records first, not a full hospital suite. That's a strength for a clinic whose burden is notes, and a limit for one whose burden is operations.

Choose MocDoc, Insta by Practo, or a similar suite if your multispecialty clinic runs an in-house pharmacy store with stock and billing, a diagnostic lab needing a LIMS, inpatient beds, or TPA and scheme claim workflows, and you want those tightly integrated with the EMR. That breadth is exactly what those suites are built for, and a documentation platform can't replace them.

Choose Patient Square if the specialties share a building and the real daily cost is writing notes and keeping records straight, you want specialty-aware templates without building them, and you'd rather see the price than negotiate it. That's the clinic this page is for.

If your clinic has grown into a small hospital with wards and a pharmacy, look at Hospital Copilot (demo-priced) rather than a solo tier. The split is about operations depth, not note quality.

## How to choose in a week

1. Name your bottleneck in one sentence: "we lose evenings to charting" points to Patient Square; "our pharmacy and lab don't talk to the EMR" points to a suite.
2. List the specialties you actually run and confirm each gets an appropriate template, not one generic form.
3. Get every quote as an all-in annual total at your real doctor count, ex-GST, so you're comparing the same thing.
4. Match the clinical output across specialties: note, ICD-10 suggestions, prescription draft, and a shared record.
5. Trial on a real multispecialty clinic day, watching whether notes land finished across different rooms.

Our encryption and audit posture is on the [security page](/in/security/), and the price ladder is on the [pricing page](/in/pricing/). Book a demo to see a specialty note against your own clinic, then run the 7-day trial across a real week. If documentation is your bottleneck, the AI-native pick usually wins; if operations depth is, a broad suite earns its quote.

---

## Charm EHR Pricing: Free Tier, Add-Ons, and the Real Total
https://patientsquare.com/us/blog/charm-ehr-pricing/
Published 2026-07-02 · Updated 2026-08-27 · Tags: pricing, ehr, charm-ehr, comparison

Charm EHR is free under 50 encounters, then $0.50 per encounter or $350 per provider, plus stacking add-ons. The real total, and a flat $119 bundle alternative.

Charm publishes pricing. The free plan covers up to 50 encounters a month. Above that, the Encounter plan bills $0.50 per encounter with a $25 monthly minimum, or the Provider plan is $350 per physician per month ($200 for non-physician providers). Practices pick whichever is cheaper for their volume. Add-ons like the AI scribe, EPCS, and telehealth stack on top, so your real total is base plus extras.

Short version: Charm EHR is free under 50 encounters a month, then it's **$0.50 per encounter** ($25 monthly minimum) or **$350 per provider per month**, whichever is cheaper for your volume. The catch is the add-ons: the native AI scribe is a separate **$125 per provider per month**, and EPCS, telehealth, and messaging stack on top. Add the scribe to the Provider plan and you're near **$475 per provider**. If you want the scribe and the EHR in one bill, Patient Square's Copilot plan is **$119 per provider per month** annually with the ambient scribe already bundled. You can see the note on a real visit first.

This isn't a Charm takedown. Its free tier and usage-based pricing are genuinely small-practice-friendly, and it ships a real native scribe. The point is the *total*, because Charm's price is honest but modular, and the modules add up.

> **Key takeaways**
>
> - Charm is free up to 50 encounters a month, then $0.50/encounter ($25 minimum) or $350/provider/month.
> - The native Charm AI Scribe is a paid add-on: $125/provider/month unlimited, or $2/encounter.
> - Add-ons stack: EPCS ($250 one-time plus $10/month), telehealth ($20/month), plus SMS and e-fax overages.
> - Scribe plus EHR on Charm's Provider plan runs near $475/provider/month once you add both.
> - Patient Square Copilot is a flat $119/provider/month with the ambient scribe and AI EHR bundled.

## What does Charm EHR actually cost?

Charm publishes its pricing, which is a real point in its favor, and the model is usage-based. Here's the base structure from Charm's own pricing pages.

| Charm plan | Price |
|---|---|
| Free | $0, up to 50 encounters / month |
| Encounter (Flexi) | $0.50 / encounter, $25 / month minimum |
| Encounter, high volume | $1,000 + $0.30 / consult beyond 2,000 |
| Provider (physician) | $350 / provider / month, unlimited encounters |
| Provider (non-physician) | $200 / provider / month |

The logic is simple: low-volume practices ride the free tier or pay per encounter, and busy practices flip to the flat $350 Provider plan once that's cheaper than metered encounters. That's a fair model. It means a slow clinic pays little and a full one pays a predictable flat rate.

One data caveat worth flagging: some aggregators list the Provider plan at $200, but Charm's own FAQ shows $200 is the **non-physician** rate; the physician Provider plan is **$350**. Use the first-party number.

The base plan isn't the whole bill, though. The scribe is where it grows.

## Why the Charm scribe changes the price

Charm ships a native ambient AI scribe, Charm AI Scribe, that transcribes the visit and drafts notes with diagnosis-code suggestions. That's a genuine feature, and it's real ambient documentation, not a third-party bolt-on. But it's a paid add-on, priced separately: **$125 per provider per month** for unlimited use, or **$2 per encounter** with a $20 monthly minimum.

Do the arithmetic on a typical setup. A physician on the Provider plan at $350 who wants the scribe adds $125, landing at **$475 per provider per month**. That's the number to compare, because most practices reading a pricing page want the note automated, not typed by hand.

Patient Square bundles the same category of tool, an ambient scribe, into one price with no separate scribe line. Check the note quality against your own visit before you decide which model fits.

## The add-ons that stack on Charm

Charm's base tier is the floor. The total is what shows up once you turn on the modules a real practice needs. From Charm's own pricing FAQ:

- **Charm AI Scribe.** $125 per provider per month unlimited, or $2 per encounter.
- **EPCS (controlled-substance prescribing).** $250 per provider as a one-year license, plus a $10 monthly Rx subscription fee.
- **Telehealth.** $20 per provider per month.
- **SMS and e-fax overages.** $0.08 per message and $0.10 per fax beyond your plan's allowance.

None of that is unusual for a modular EHR, and Charm is upfront about each line. But it means the free or low sticker isn't the total. A practice that wants the scribe, controlled-substance prescribing, and telehealth is stacking three add-ons on top of the base plan. Add the modules you'll actually use before you compare, or you'll compare the wrong number.

## Charm vs a flat bundle: the total-cost view

Let's compare like for like. Say you run a two-provider practice that wants the ambient scribe on every visit.

| | Charm (Provider plan + AI Scribe) | Patient Square Copilot |
|---|---|---|
| EHR base (per provider / mo) | $350 | $119 (annual billing) |
| Ambient scribe | $125 add-on | Bundled, unlimited |
| Combined (per provider / mo) | ~$475 | $119 |
| Per-encounter metering | Optional (Encounter plan) | No |
| Free tier | Yes (under 50 encounters) | No, but 7-day trial |
| Published price | Yes | Yes |

Read that honestly. Charm's free tier is a real advantage for a brand-new or very low-volume practice, and its usage-based option genuinely helps a seasonal clinic. What Patient Square gives a busier practice is the scribe-plus-EHR combination in one flat bill, without adding the scribe as a separate module.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. Put it in front of your visit type and judge the note.

## What you give up leaving Charm

Be fair about the trade. Charm is a capable, low-cost EHR with a genuinely useful free tier.

- **The free and usage-based options.** If your volume is tiny or seasonal, Charm's model can be cheaper than any flat plan, including ours. That's a real reason to stay.
- **A mature module catalog.** Charm has years of depth in billing, patient portal, labs, and practice management. Patient Square offers ICD-10 *suggestions* and a bundled AI EHR, not a full practice-management suite.
- **Controlled-substance prescribing.** Charm's EPCS add-on transmits controlled-substance prescriptions. Patient Square's eRx is a **draft** for you to review and sign, not a transmission engine.

Patient Square's export claim is precise: **EHR-ready export (PDF, HL7, FHIR)**. That's a clean export, not a certified interoperability engine. For a broader look at bundled options, our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup and the [Elation EHR pricing](/us/blog/elation-ehr-pricing/) breakdown cover the other end of the market.

## When Charm is the better choice

Stay with Charm, or pick it, if you run a very low-volume or startup practice that can live on the free tier, or if you want granular usage-based pricing and a deep module catalog you'll configure yourself. Charm's free plan and per-encounter option are real cost advantages that a flat bundle can't match at the low end. If controlled-substance prescribing is central to your day, Charm's EPCS transmission is a genuine feature we don't match.

Choose a flat bundle if you're a busier practice that wants the scribe on every visit, you'd rather not stack add-ons to get there, and you want the note and the record in one predictable bill. Once you add Charm AI Scribe to the Provider plan, a flat $119 with the scribe included is the cheaper path. The full ladder is on the [pricing page](/us/pricing/).

## How to price your real Charm cost in an afternoon

Skip the marketing math and build your own number:

1. Count your monthly encounters. Under 50, Charm is free. Above it, compare $0.50 per encounter against the $350 flat Provider plan and pick the cheaper one.
2. Add the scribe: $125 per provider per month, or $2 per encounter, since it's not in the base plan.
3. Add EPCS, telehealth, and any messaging overages you'll actually use.
4. Compare that total against a flat $119 per provider annually with the scribe and EHR bundled.
5. Trial the alternative on a real clinic week before you decide. A demo flatters everyone.

The receipts behind our claims, encryption, access, and audit status, are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to check the note against your own visits, then run the 7-day trial on a real week. For a busy practice that wants the scribe on every visit, the bundle usually beats the add-on stack.

---

## CrelioHealth Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/crelio-health-alternatives-india/
Published 2026-07-02 · Updated 2026-08-27 · Tags: alternatives, comparison, pricing

CrelioHealth is lab-first LIMS from ₹8,000/mo per centre. If your real drain is documentation, here's the honest fork and a bundled AI EHR from ₹2,399/mo.

Not really. CrelioHealth is a Laboratory Information Management System (LIMS) built for diagnostic labs: sample tracking, test reporting, insurance billing, multi-centre monitoring. If you run a pathology lab, that's the point. A solo doctor or an OPD clinic whose real problem is writing notes after every visit is buying a lab engine to solve a documentation problem.

If you're a doctor or a clinic looking at CrelioHealth and wondering whether it fixes your paperwork, here's the short answer: probably not, because it isn't built for that. CrelioHealth is a LIMS, a lab engine for diagnostic centres, priced per centre from about ₹8,000/mo plus GST. If the thing eating your evenings is notes, not lab samples, Practice Copilot fits that clinical workflow. It starts at ₹1,599/mo per doctor, and Patient Square EHR is included from the Copilot tier for ₹2,399/mo; an alongside path keeps an existing EHR (ex-GST, add 18%). You can book a demo and watch a finished SOAP note land in about two minutes.

This isn't a knock on CrelioHealth. It's a category question. Below: what CrelioHealth is genuinely good at, what it costs, where a clinic's real cost actually sits, and the honest case for staying with Crelio.

> **Bottom line**
>
> - CrelioHealth is lab software (LIMS), priced per centre from ~₹8,000/mo + GST, with onboarding fees from ₹10,000.
> - Patient Square is documentation software, priced per doctor from ₹1,599/mo + GST, EHR bundled at ₹2,399/mo.
> - Different jobs. A lab buys Crelio. A clinic drowning in notes buys a scribe plus EHR.
> - We don't do LIMS. If lab operations are your core, Crelio wins, full stop.

## CrelioHealth vs Patient Square at a glance

Here's the split, so you can decide in thirty seconds whether to keep reading.

| | CrelioHealth | Patient Square (Practice Copilot) |
|---|---|---|
| Core job | Lab / diagnostics management (LIMS) | Clinical documentation + records |
| Built for | Pathology labs, diagnostic centres | Solo doctors, OPD clinics, practices |
| Pricing basis | Per centre | Per doctor |
| India entry price | ~₹8,000/mo + GST (Standard) | ₹1,599/mo + GST (Assist) |
| Bundled EHR price | n/a (it's a lab system) | ₹2,399/mo + GST (Copilot tier) |
| Onboarding fee | ₹10,000 to ₹50,000 | None |
| AI ambient scribe | No | Yes, English + Hindi + 20+ languages |
| ICD-10 suggestions | No | Yes (suggestions, not a coding engine) |
| Prescription draft | No | Yes (draft to review, not e-prescribing) |

If your row-by-row read says "I need a lab system," stop here and go with Crelio. If it says "I need my notes done," keep going.

## What CrelioHealth is actually good at

Give it its due. CrelioHealth is a mature LIMS with real depth for diagnostic labs. It handles the full lab workflow: patient registration, sample tracking, report generation, and dispatch. It monitors multiple centres from one dashboard in real time. It automates insurance billing with revenue-cycle integration, and it hosts data on cloud infrastructure inside India. Its own pricing pitches the Standard plan at new and small labs and physician-office labs running up to about 75 tests a day.

That's a lab product doing lab things well. A pathologist or a diagnostic-chain owner should have Crelio on the list. None of what follows says otherwise.

The question is whether that describes you. A lot of doctors land on Crelio because it shows up in "healthcare software India" searches, then realise the sample-accession and referral-lab machinery isn't the problem they have. If your problem is a 40-patient OPD and a stack of half-written notes, you can [see the alternative in a demo](https://patientsquare.com/in/) before committing to a lab platform you'll half-use.

## What does CrelioHealth cost in India?

Credit to Crelio here, they publish it. The India LIMS pricing page lists per-centre monthly plans: Standard at about ₹8,000/mo, Advanced at ₹15,000/mo, Premium at ₹25,000/mo, each plus 18% GST, with Enterprise custom-quoted. On top of the subscription sit one-time onboarding fees, from ₹10,000 for Standard up to ₹50,000 for Premium. Billing is annual-contract based.

Read the unit carefully: that's per centre. A lab pays it because one centre serves many doctors and thousands of tests. For a single-doctor clinic, ₹8,000/mo plus a ₹10,000 setup fee to run software that doesn't write your notes is a hard sell.

Patient Square prices the other way, per doctor, for the documentation job. Assist is ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo. All ex-GST; add 18%, so Copilot lands near ₹2,831/mo all-in. No onboarding fee, unlimited visits and notes. The full ladder sits on the [pricing page](https://patientsquare.com/in/pricing).

## Where a clinic's real recurring cost hides

Lab software solves lab economics. It does nothing for the cost most clinics actually carry, which is time on documentation. In a 67-country study published in BMJ Open, Indian consultations averaged about two minutes, among the shortest anywhere. Two minutes with the patient, and the record is what gets shortchanged.

That thin record is expensive in a way that doesn't show on an invoice. Roughly 65,000 medical-negligence matters reach Indian courts and consumer forums each year, and the defence that holds up is a complete contemporaneous record. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A LIMS won't help you there. A scribe that finishes a defensible note during the visit will.

That's the wedge. Here's the canonical version of what Patient Square does: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. If that's the problem on your desk, book a demo and test it on a real OPD day.

## What you give up by choosing Practice Copilot

Be honest about the trade. If you pick Patient Square over Crelio, you don't get a LIMS. No sample accession, no referral-lab workflows, no lab-grade RCM, no per-test turnaround tracking. If those are core to your business, that's a real loss and Crelio is the right call.

There's also the compliance framing to keep straight. Patient Square handles data to DPDP Act 2023 standards, consent-first and purpose-limited, with a SOC 2 Type II audit in progress (not certified) and ABDM integration on the roadmap, not live today. We keep records born digital so you're ready for the ABHA-linked era on your timeline, but we don't claim ABDM integration you can switch on this week. If a vendor tells you their ABDM is live and certified, ask to see the NHA certificate.

What you keep is the part a busy clinic uses every hour: capture in the patient's language, a clean English note the moment they leave, ICD-10 suggestions, and a prescription draft you review and sign. Notes belong to your clinic; export or delete any visit anytime.

## When CrelioHealth is the better choice

Stay with Crelio, or choose it, if diagnostics is your business. If you run a pathology lab, a radiology centre, or a diagnostic chain, and your daily fight is sample leakage, turnaround time, referral-lab reconciliation, and lab billing, CrelioHealth is purpose-built for that and priced for a centre that runs volume. A per-doctor scribe isn't competing with it; it's the wrong category. Buying a documentation tool to run a lab would leave you missing the exact machinery Crelio exists to provide.

Choose Practice Copilot if you're a doctor or clinic whose evenings disappear into charting and you want transparent per-doctor pricing. Use Patient Square EHR or keep an existing EHR; an in-house lab can still run CrelioHealth for LIMS workflows. A few clinics genuinely run both, a LIMS for the lab and the ambient scribe for consults, and that's a fine answer too.

## How to decide this week

Skip the feature-sheet staring contest and run the test:

1. Track where your time actually goes for three days. If it's samples and lab reports, you want a LIMS. If it's notes and records, you want a scribe.
2. If it's documentation, shortlist per-doctor tools with published pricing and no setup fee.
3. Match the clinical output: a structured note, ICD-10 suggestions, and a checked prescription draft, so you compare like for like.
4. Run it on real OPD visits in your own languages, not a scripted demo. Capture in Hindi or Marathi; check the English note.
5. Settle the data question with any vendor: where it's hosted, who owns it, and the real ABDM status.

The receipts, encryption, access, audit status, sit on our security page, and the per-doctor ladder with no asterisks is on the [pricing page](https://patientsquare.com/in/pricing). Book a short demo if you want the note quality checked against your own visit type. If you run a lab, Crelio is your tool. If you're a clinic buried in notes, you're in the right place.

---

## DeepScribe Alternatives: A Published-Price Option
https://patientsquare.com/us/blog/deepscribe-alternatives/
Published 2026-07-02 · Updated 2026-07-22 · Tags: ai-scribe, comparison, deepscribe, pricing

DeepScribe is sales-led with no public price. When a self-serve scribe from $79/mo and a bundled AI EHR from $119/mo fit a practice better, and when they don't.

DeepScribe publishes no per-provider price and sells through a sales team. Third-party review sites estimate roughly $350 to $750 per provider per month, closer to $500 with EHR integration, with annual discounts. Those are outside estimates, not DeepScribe figures. Patient Square publishes its price: $79/mo for the scribe, $119/mo for the plan that bundles an AI EHR, on annual billing.

DeepScribe is a capable ambient scribe. It's also sales-led, so you can't learn your price without a call. If you're an independent practice that wants a number you can read today, the honest alternative is a scribe with published pricing. Patient Square's scribe starts at $79 per clinician per month on annual billing, and the Copilot plan bundles a real AI EHR from $119/mo. The whole ladder is on our [pricing page](../../pricing/), no quote required. Want to see a finished note first? Book a demo and watch one draft in about two minutes.

This isn't a DeepScribe takedown. It's a fit question. Below: what DeepScribe costs (nobody publishes it, so we'll be careful), a side-by-side, and the cases where the enterprise tool is the right call.

> **Key takeaways**
>
> - DeepScribe publishes no per-provider price. Third-party sites estimate roughly $350 to $750 per provider per month, near $500 with EHR integration. Those are outside guesses, not DeepScribe numbers.
> - Patient Square publishes all three US tiers: $79 (scribe), $119 (scribe plus bundled AI EHR), $199 (full front office), per clinician per month on annual billing.
> - The clinical output is the same shape: a structured SOAP note, ICD-10 suggestions, and a prescription draft to review and sign.
> - DeepScribe's edge is enterprise EHR integration depth. A small practice rarely uses it and still pays for it.
> - When you run a large EHR-embedded group, DeepScribe is the better tool. That's the design, not a knock.

## How does DeepScribe compare to Patient Square?

Here's the honest side-by-side. The prices in DeepScribe's row are third-party estimates, because DeepScribe doesn't publish one.

| | DeepScribe | Patient Square |
|---|---|---|
| Published price | No. Sales-led quote | Yes. $79 / $119 / $199 per clinician/mo, annual |
| Entry price | ~$350–$750/provider/mo (third-party estimate) | $79/mo (Assist) |
| Bundled EHR | Not the core pitch; integrates with your EHR | Yes, AI Copilot EHR, bundled from $119/mo |
| Clinical output | SOAP note, ambient capture | SOAP note, ICD-10 suggestions, Rx draft |
| Trial | Demo-led | 7-day trial |
| Best fit | Larger groups, deep EHR integration | Solo and small practices wanting a published price |

If your practice is on the small side, book a demo and check the note against your own visit type before you assume a bigger tool is the safer bet.

## What does DeepScribe actually cost?

The first friction is the missing number. DeepScribe's site is sales-led, with demo and contact CTAs where a pricing page would sit. That's normal for software that scales price with provider count, visit volume, and integration scope. It also tells you what buying feels like: a sales cycle, not a checkout.

Third-party review sites fill the gap. SoftwareFinder and similar pages estimate DeepScribe somewhere between $350 and $750 per provider per month, with figures near $500 once EHR integration is in the mix and discounts of up to 20% for annual commitments. Be precise about those: they're outside estimates that appear on comparison sites, not prices DeepScribe publishes. Treat them as directional, not a quote.

Patient Square works the other way. We publish $79, $119, and $199 per clinician per month on annual billing, the full ladder readable on the [pricing page](../../pricing/) without a call. The bundled AI EHR shows up at the Copilot tier, folded into that $119 line rather than sold as a separate integration project.

## What do you give up leaving DeepScribe for a self-serve scribe?

There's a real trade. Pretending otherwise gets you a bad Tuesday later.

You give up deep EHR integration as a managed deployment. DeepScribe pushes into major EHRs as part of an enterprise rollout, with a project team and a timeline. Patient Square takes a lighter path: you review the note and it exports EHR-ready (PDF, HL7, FHIR), or you use the bundled AI Copilot EHR at the Copilot tier so the note already sits in a chart. For a solo doctor, that's a few seconds. For a 300-clinician system, that difference is the whole evaluation.

What you keep is the part a small practice uses every day. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Audio is processed in memory and discarded the moment the note drafts, so no recording is kept. A BAA is available for every customer, solo practices included.

If your shortlist is wider, [Nabla alternatives](../nabla-alternatives/) covers the free-tier-and-caps end of the market, and [Suki alternatives](../suki-ai-alternatives/) looks at the voice-assistant angle. If you want DeepScribe's price unpacked in more depth before you compare, [DeepScribe pricing](../deepscribe-pricing/) pulls together what third-party sites estimate and what those estimates leave out. And if you're weighing DeepScribe head-to-head against Freed specifically, [DeepScribe vs Freed](../deepscribe-vs-freed/) does that comparison directly.

## When is DeepScribe the better choice?

It comes down to size and how deep you need the EHR.

Choose DeepScribe if you run a larger group or health system that wants the scribe embedded in a major EHR, tuned to your coding workflows, and deployed across many clinicians with enterprise support. At that scale, a self-serve tool isn't competing with DeepScribe. It's a different category. Trying to shave a per-seat price by dropping the integration would cost you more in lost workflow than you'd save.

Choose a practice-sized scribe if you're an independent practice or small group that wants a clean note in about two minutes, a price you can read now, a BAA without an enterprise contract, and an assisted trial after workspace setup. That describes most of the practices reading this page. And if you want the chart and the front desk in the same subscription, that's the Copilot bundle.

## How to decide in a week

Skip the spec sheet and run the real test.

1. Name your EHR-integration need honestly. If "the scribe writes into my EHR automatically, across dozens of clinicians" is a hard requirement, you're in enterprise territory, and DeepScribe belongs on the list.
2. If it isn't, shortlist practice-sized tools that publish a price and document how their trial is requested and started.
3. Match the clinical output: note plus ICD-10 suggestions plus a prescription draft, so you compare like for like.
4. Settle the audio question with each vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits. A scripted demo flatters every scribe equally.

The receipts behind our claims live on the [security page](../../security/), and the price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visit type, then request the 7-day trial for a real clinic week. If you run a big EHR-embedded system, DeepScribe is your tool. If you would rather read the price before a smaller assisted setup, that is the route you are shopping for.

---

## Dental Clinic Management Software in India: A Practical Buyer's Guide
https://patientsquare.com/in/blog/dental-clinic-software-india/
Published 2026-07-02 · Updated 2026-07-22 · Tags: dental-software, clinic-management-software, dental-emr, india

Compare dental clinic software in India for odontograms, recalls, GST billing, consumable inventory, pricing, and AI documentation.

Six things carry most of the weight: an appointment book with recall reminders, treatment charting on an odontogram, GST-compliant billing and receipts, inventory for consumables, a patient record that holds history and images, and clean handling of patient data under the DPDP Act. Imaging integration and lab-work tracking are nice-to-haves that some practices lean on heavily. A generic clinic tool covers the first three; the odontogram and consumable inventory are where dental-specific software earns its keep.

A dental practice runs on a different clock than a GP clinic. The chart is a mouth, not a symptom list; the recall drives repeat revenue; and half the cost of a visit walks out the door as consumables. So the software that fits a dental clinic is not the same as the software that fits an OPD, even when a vendor sells you both under one name. This guide walks through what a dental clinic in India actually needs, what "dental-specific" really buys you over generic clinic software, what the prices look like, and where an AI documentation layer fits without pretending to be your whole system.

> **Key takeaways**
>
> - Six functions carry a dental practice: appointment book with recalls, odontogram charting, GST billing, consumable inventory, a patient record with images, and DPDP-clean data handling. The odontogram and consumable stock are what separate dental software from generic clinic tools.
> - Most India-native dental tools (BestoSys, Dentee, MocDoc) gate pricing behind a demo. Get the quote in writing, ex-GST, and confirm what one seat means.
> - Under the DPDP Act 2023 the clinic is the data fiduciary. Where data sits, how long it is kept, and what happens when you leave are now legal questions, not IT trivia.
> - An ambient documentation layer drafts the visit note for the dentist to review and sign. It sits on top of your clinic software; it does not replace the chart or the billing.

_Sources: Irving et al., BMJ Open 2017; MeitY, DPDP Act 2023._

If you already know your practice management is fine and the real drain is the note you type between patients, you can skip ahead and [explore Practice Copilot](/in/products/practice-copilot/) to see where the documentation piece fits. Otherwise, start with what the software has to do.

## What does a dental clinic actually need from software?

Ignore the feature list on the brochure. Six functions do the real work in a dental practice, and if a tool nails these, the rest is garnish.

1. **Appointments with recalls.** The recall is dental's quiet revenue engine. A six-month cleaning reminder that fires on its own, over SMS or WhatsApp, brings patients back without a receptionist chasing a spreadsheet. If the appointment book cannot schedule a recall at the point of care, you will lose the follow-up.
2. **Treatment charting on an odontogram.** This is the dividing line. A dental tool lets you click a tooth and record the finding, the plan, and the work done, tooth by tooth. Generic software makes you type "36, RCT started" into a box. Do that forty times a day and the difference is an hour.
3. **GST billing and receipts.** Invoices need to be GST-compliant, tied to the treatment, and printable or shareable. Revenue reporting that ties back to the chair matters once you have more than one dentist.
4. **Inventory for consumables.** Composite, burs, gloves, impression material, endo files. A practice that does not track consumable stock either overbuys or runs out mid-procedure. Dental inventory is heavier and more granular than a GP clinic's, which is why it belongs on this list.
5. **Patient record with images.** History, allergies, past treatment, and ideally the ability to attach or view radiographs and intra-oral photos against the chart.
6. **DPDP-clean data handling.** Where the record lives, how long it is kept, and who can see it. This used to be an IT footnote. Under the [DPDP Act 2023](../dpdp-act-clinics-guide/) it is a legal one.

Everything else, from lab-work tracking to imaging device integration, is a real need for some practices and a distraction for others. Decide which of the six you cannot live without, then treat the extras as tie-breakers.

## What makes dental software different from generic clinic software?

Plenty of clinic tools will happily sell you a "dental module," and some are fine. But two things separate software built for dentistry from software that merely tolerates it.

The first is the **odontogram**. Dental-specific tools like BestoSys build restorative and perio charting into the core, so the tooth is the unit of work. A generic OPD tool, even a good one, treats the visit as a consult with notes. You can make it work, the way you can hammer a screw, but the charting friction never goes away.

The second is **consumable-aware inventory and lab work**. Dentistry consumes physical stock per procedure and often sends work out to a lab. BestoSys, for instance, names lab-work management with tracking and alerts as a headline feature, which tells you the vendor understands the workflow. A generic clinic tool usually has a thin inventory bolt-on that was designed for pharmacy stock, not for tracking how many composite syringes a restorative-heavy month burns through.

If your practice is mostly consults and simple procedures, generic clinic software with a dental veneer may be enough, and you will find our wider [clinic management software scorecard](../best-clinic-management-software-india/) and the [OPD software guide](../opd-software-for-clinic-india/) useful for that comparison. If charting and consumables are daily work, buy the dental-specific tool and stop fighting the form.

## What does dental clinic software cost in India?

Here is the honest part most listicles skip: the India-native dental vendors mostly do not publish a price. We checked. BestoSys describes "flexible features and pricing to suit practices at every stage" and routes you to a free trial or a demo, with no rupee figure on the page. Dentee's plan pages sit behind a sign-up. MocDoc positions dental practice management as a demo-led sale. That is not a scandal; it is just how mid-market Indian clinic software is often sold, and it means the price flexes with how hard you negotiate.

| | BestoSys | Dentee | Generic clinic tool with dental module | Practice Copilot: Patient Square EHR or existing-EHR path |
|---|---|---|---|---|
| **Built for** | Dental practice management | Dental practice management | General clinic, dental bolt-on | AI clinical workflows; dental charting remains specialist scope |
| **Odontogram / perio charting** | Yes (restorative + perio) | Yes | Varies, often thin | No (not its job) |
| **Consumable inventory / lab work** | Lab-work tracking headlined | Yes | Usually pharmacy-style stock | No |
| **GST billing** | Yes | Yes | Yes | No |
| **Published price** | Demo-gated, no rupee figure | Sign-up-gated | Varies | Assist ₹1,999/mo; ₹1,599 annual, ex-GST (+18% GST) |
| **ABDM** | Ask which milestone | Ask which milestone | Ask which milestone | On the roadmap, not shipped |
| **Trial** | Free trial | Get started free | Varies | assisted 7-day |

All vendor rows come from each company's own pages in July 2026; where a cell says "ask," the vendor's public material did not name a milestone, so confirm it before you buy. The single practical rule on price: get the quote in writing, ex-GST, and pin down what one seat covers, a chair, a dentist, or a location, because the same "₹X per month" means very different things depending on the answer.

When a rupee figure does surface for these tools, it tends to land in the low thousands per seat a month before the 18% GST. Do not anchor on a number a reseller quotes over the phone; anchor on the written quote with GST spelled out.

## How does the DPDP Act change a dental software purchase?

More than most dentists realise. Under the [DPDP Act 2023](../dpdp-act-clinics-guide/), the clinic is the **data fiduciary** for its patients' data. That is a legal role, and it comes with duties you cannot outsource to the software vendor.

Three of those duties bite directly on a software choice:

- **Purpose limitation.** You collect and use patient data only for the specified purpose the patient consented to, treatment, and not for anything outside the notice you gave when you took that consent. A vendor that quietly repurposes your patient list for its own marketing is creating a liability that lands on you.
- **Storage limitation.** Data is kept only as long as the purpose needs it. Indefinite retention "just in case" is now a defect, not a feature. Note the tension with clinical record-keeping norms that expect records held for a defined period; the answer is a deliberate retention policy, not "keep everything forever."
- **Where the data physically sits.** Cloud dental software puts your patients' records on someone else's servers. Ask where, ask how it is protected, and ask what happens to it if you stop paying. BestoSys, for its part, headlines encryption and multi-level protection, which is the kind of claim you want in writing.

Two clean questions to put to any vendor: *where does our data live, and how do we get it back if we leave?* A tool that cannot answer both crisply is a tool that will make your DPDP compliance harder. This is not a reason to fear cloud software; it is a reason to buy it with your eyes open.

## Where does AI documentation fit in a dental practice?

In the note, and only the note. This is the part where an ambient layer earns its place without pretending to be your clinic system.

A dental consult still produces a written record: the complaint, the findings, what you did, what comes next. Typing that between patients is where evenings quietly disappear. An ambient documentation layer listens during the visit and drafts that note, which the dentist then reviews, edits, and signs. It does not touch the odontogram, the billing, or the inventory. It sits on top of whatever you already run and hands back a draft, faster than typing from memory after the patient has left.

A few design points matter for an Indian practice specifically. Consults happen in braided Hindi and English, so the layer takes code-mixed speech on input and returns the note in clean clinical English. The visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner posture under the DPDP Act. And the output is always a **draft**: the dentist reviews and signs it, the software never signs for you. Any prescription it suggests is a draft to check, not an order it sends. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That layer is [Practice Copilot](/in/products/practice-copilot/), our AI bundle for Indian clinics, with the ambient documentation module doing the note-taking work. We publish our prices rather than gating them: the entry Assist plan is ₹1,999 per clinician a month, or ₹1,599 on annual billing, all ex-GST (GST is added at the prevailing 18%, so about ₹1,887 a month with GST), with a 7-day free trial through the India signup page. We are candid about scope too. ABDM integration is on our roadmap, not shipped, and we will not badge a status we do not hold. If you also need drafting help for your prescriptions, the [prescription software guide](../prescription-software-for-doctors-india/) covers where that fits.

The buying advice we would give a friend who runs a chair: pick your dental practice management software on the odontogram, the recalls, and the inventory, then decide separately whether the note is eating your evenings. If it is, add a documentation layer on top rather than ripping out a system that already handles your chart. Explore [Practice Copilot](/in/products/practice-copilot/) and test where a real consult lands as a note before you commit to anything.

_Sources: BestoSys and Dentee vendor pages (July 2026); MeitY, DPDP Act 2023; NHA / ABDM portal; Irving et al., BMJ Open 2017._

---

## AI Medical Scribe With Cerner: Three Integration Options
https://patientsquare.com/us/blog/ai-scribe-for-cerner/
Published 2026-07-01 · Updated 2026-07-22 · Tags: ai-scribe, cerner, oracle-health, ehr, workflow

The three ways a scribe note reaches a Cerner (Oracle Health) chart, why our standalone tool uses the simplest one, and when Oracle's own Clinical AI Agent fits better.

Yes, but the word covers three different things. A standalone ambient scribe like ours captures the visit separately, drafts the note, and you paste or import the finished text into the Cerner Millennium chart. It does not file into Cerner by itself. There is no Cerner API, HL7 feed, or FHIR write-back on our side, by design. Vendors that push notes straight into the chart are a different, deeper kind of integration.

Yes, a standalone AI scribe works with Cerner. It just does not work the way "integration" makes it sound. The scribe captures the visit on its own, drafts the note, and you paste or import the finished text into the Cerner Millennium chart. It never files into Cerner by itself. There is no Cerner API on our side, and that is a deliberate design choice, not a gap we forgot to close.

If you landed here looking for a tool that pushes notes straight into Millennium with zero clicks, that is a real thing, and it is not what a standalone scribe is. The rest of this page lays out the three ways a note can reach a Cerner chart, which one we use, and when Oracle's own scribe is the smarter buy.

One naming note before anything else. Oracle bought Cerner in a deal that closed on June 8, 2022, and rebranded the business Oracle Health ([Oracle](https://www.oracle.com/news/announcement/oracle-completes-cerner-acquisition-2022-06-08/)). The EHR itself is still Cerner Millennium. You will see both names used, sometimes in the same sentence. Throughout this page, "Cerner" and "Oracle Health" point at the same platform.

> **Key takeaways**
>
> - There are three ways a scribe note reaches a Cerner chart: copy-paste or export, a FHIR or HL7 push your Oracle Health team stands up, and Oracle's own built-in scribe. We do the first.
> - A standalone scribe works *alongside* Cerner. You copy the finished note in, or export it. It does not auto-file into Millennium.
> - No Cerner API, no HL7 or FHIR write-back, no bidirectional sync on our side. We name that up front because the alternative is a claim you would disprove in week one.
> - Oracle Health ships its own ambient scribe, the Clinical AI Agent, that drafts notes directly into Millennium. For an all-Cerner shop, that is the obvious first thing to try.
> - A standalone earns its place when you also work off Cerner, see patients in more than one language, or want a checked prescription draft and ICD-10 suggestions.

## What are the three ways a scribe note reaches a Cerner chart?

Every "Cerner integration" claim in the scribe market is one of three things. They differ in engineering, in cost, and in who has to maintain them, so it is worth naming them before you compare vendors.

**Path one: copy-paste or export.** The scribe drafts the note in its own window, and the clinician copies it into the open Millennium encounter, or exports it as a file and imports it. No interface, no IT project, nothing to configure inside Oracle Health. This is what a standalone tool does, and it is what this page is about.

**Path two: a FHIR or HL7 push.** A vendor writes the note into the chart through an interface. In an Oracle Health environment that typically runs over the platform's FHIR APIs or an HL7 feed, and your Oracle Health team has to help stand it up and keep it running. The note lands in the chart without a paste step, at the cost of a real integration to build, test, and maintain.

**Path three: native.** Oracle's own ambient scribe, the Clinical AI Agent, drafts the note directly inside Millennium. Nothing crosses a boundary because the scribe *is* part of the EHR. We cover that tool below, because for some Cerner shops it is the right answer.

We do path one. Not path two, not path three. The next sections are the honest version of why, and when that is the wrong choice for you.

## Does a standalone AI scribe actually work with Cerner?

Short version: it works *near* Millennium, not *inside* it.

A standalone ambient scribe is software that listens to the visit and writes the note, running on your phone or laptop, separate from the EHR. When the note is ready, you move it into Cerner the same way you would move any block of text: select, copy, paste into the encounter. Some teams export the note as a file and import it instead. Either way, the scribe never touches Millennium directly.

This is a real, common category with a plain name in the market: paste-window vendors. The app generates the note in a sidebar or its own window, and the clinician drops it into the open chart. It is the standard shape for EHR-agnostic scribes that are not wired into a hospital's IT stack. The AI Medical Scribe by Patient Square is one of them, and we are not going to dress that up as something it is not.

What it buys you is independence. The scribe does not care whether the chart in front of you is Cerner, another EHR, or a telehealth note you keep outside any of them. It captures the visit and hands back the note regardless. For a clinician whose week is split across systems, or a group weighing whether it will still be on Millennium in three years, that portability matters more than it first sounds.

## What does the scribe hand back, and what do you do with it in Cerner?

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. That is the output. Here is the Cerner part.

The note arrives as clean, structured text: subjective, objective, assessment, plan. You read it, fix what needs fixing, and paste the finished version into the Millennium encounter. The ICD-10 suggestions come alongside, so the codes you would otherwise be searching for are already in front of you. They are suggestions, not a coding engine, and they do not touch your E/M level. You stay the one who decides.

The prescription draft is deliberately just that: a draft. The scribe writes down the medication you discussed, and it does not screen the draft for interactions, dosing, or pregnancy. A draft an LLM wrote is still a draft an LLM wrote, so the safety review stays with you, not a rule engine. None of that draft files into Cerner on its own, and it is not e-prescribing. You review, you adjust, you sign, and you send it through Millennium yourself.

One thing that happens well away from Cerner: the visit audio. It is processed in memory and discarded the moment the note is drafted. No archive, not for us, not for the practice. What survives is the note you reviewed and pasted in. The full posture is on our [security page](../../security/), and the consent side is in our [HIPAA, BAA, and consent guide](../ai-scribe-hipaa-baa-consent/).

## Why isn't there a Cerner or Oracle Health integration? The honest answer

Because we do not have one, and writing a fake one into the marketing copy is how you lose a health system in the first week.

Here is what path two actually involves. A vendor that pushes notes into the chart has to build against Oracle Health's interfaces, whether that is the platform's FHIR APIs or an HL7 feed, and your Oracle Health team has to help configure and maintain the connection. That is the difference between "the note appears in the chart automatically" and "you paste the note in." The first is a genuine integration project with your IT department in the loop. We do not do it. We do the second one.

So when another scribe advertises "Cerner integration," ask which of the three paths they mean. A FHIR or HL7 push into Millennium is a genuine capability with a genuine build behind it. A paste window is a different thing wearing the same word. Native is a third thing again, and it is Oracle's, not a third party's. All three are legitimate. They are not the same product, and the price, the setup burden, and the lock-in differ across them.

We chose the standalone path on purpose. The cost is the copy-paste step. The benefit is that the scribe works with any EHR or none, your notes belong to your practice, and you can export or delete any visit whenever you want without filing a ticket with an integration team. For an independent practice or a department that documents in more than one place, that trade usually favors independence. For a large Cerner shop that wants the note in the chart with zero clicks, it does not, and Oracle already sells the tool for that.

## Standalone scribe with Cerner vs. Oracle's Clinical AI Agent

Oracle Health ships its own ambient scribe. The Clinical AI Agent listens during the appointment and drafts the note directly into Millennium, and in February 2026 Oracle expanded it to draft clinical orders too, including labs, imaging, prescriptions, and follow-ups ([Oracle](https://www.oracle.com/news/announcement/oracle-health-adds-order-creation-capabilities-to-clinical-ai-agent-2026-02-02/)). That reshapes the question for anyone on Cerner, so here are the two side by side.

| | Standalone scribe with Cerner (ours) | Oracle Clinical AI Agent (native) |
|---|---|---|
| **How the note reaches the chart** | You paste or import it | Drafted directly inside Millennium |
| **Works off Cerner too** | Yes, EHR-agnostic | No, lives inside Oracle Health |
| **Available without Cerner** | Yes | No, Oracle Health customers only |
| **Cost shape** | Published per-clinician price | Sold through your Oracle Health contract |
| **Prescription draft (you review and sign)** | Yes, a draft only, no pharmacy transmission | Order drafting inside Oracle's own tooling |
| **ICD-10 suggestions** | Yes | Within Oracle's own coding features |
| **Multilingual capture** | Yes, English plus more, note in English | Per Oracle's language support |
| **Audio retention** | Never stored, in-memory only | Per Oracle's policy |

The native tool has one large advantage: the note lands in the chart with no paste step, and it is bought and provisioned through the Oracle Health relationship you already have. For a shop whose whole day happens in Millennium, that convenience is hard to argue with, and we are not going to pretend otherwise.

What it does not do is leave Cerner. If a real slice of your documentation happens somewhere else, a tool that only works inside Oracle Health covers only that slice. And the prescription-draft-with-a-hard-safety-screen and the multilingual capture are not the native tool's job. That is the boundary between the two.

The all-Epic version of this comparison follows the same logic, and if your organization runs both systems it is worth reading too: [AI scribe with Epic](../ai-scribe-for-epic/) and the [head-to-head with Epic's own AI Charting](../ai-scribe-vs-epic-ai-charting/). This page is about working alongside Cerner; those cover the Epic side of a mixed estate.

## When Oracle's native scribe is the better fit

Here is the verdict without the hedging, because the honest version is the useful one.

Use Oracle's Clinical AI Agent if your practice lives entirely inside Cerner Millennium, every visit you document happens there, you do not need a separate prescription draft to review, and your patients speak the language Oracle's build supports. For a deep all-Cerner enterprise with no off-Cerner documentation and no multilingual case mix, direct drafting into the chart and provisioning through a contract you already hold are exactly right. Paying a second vendor to draft the note and then pasting it in by hand would be paying twice for less convenience. Do not do that.

Use a standalone scribe with Cerner if any of these is true: you document visits outside Cerner too, you want a prescription draft you review and sign, you see patients in more than one language, or you would rather your notes not be tied to one EHR's roadmap. That last point is not abstract for Oracle Health customers right now. KLAS reported 2025 as the third straight year Oracle Health saw the largest net loss in acute-care EHR market share, sliding to roughly 22% of hospitals behind Epic ([HIT Consultant](https://hitconsultant.net/2026/05/14/klas-2026-ehr-market-share-report/)). Plenty of those systems are re-examining their platform. A scribe that travels with the clinician instead of the EHR is one less thing to migrate if the chart underneath ever changes.

The mistake runs both ways. Buying a standalone when the native agent already covers your whole day is waste. Assuming the native agent covers you when a third of your visits happen off Cerner, or end in a prescription draft you want to review outside the chart, is a different kind of waste. Match the tool to how the week actually runs.

## How to decide in five minutes

1. Is every visit you document inside Cerner Millennium? If yes, look at Oracle's Clinical AI Agent first; it is native and provisioned through a contract you already have. If no, you need a tool that works off Cerner, which the native one does not.
2. Which of the three integration paths do you actually want: a paste step, a FHIR or HL7 push your IT team maintains, or native drafting? Be honest about who owns the upkeep on the middle one.
3. Do you want the scribe to draft and safety-screen prescriptions, or just write the note? Note-only leans native. Note-plus-screened-prescription leans standalone.
4. What languages do your visits actually happen in? A US-tuned tool may not cover a multilingual clinic. A standalone built for it does, with the note always returned in clinical English.
5. Where does the visit audio go, on whichever tool you pick? Ask both. Ours: processed in memory, discarded at note draft, no archive.

If you are leaning standalone, settle it on your real visits, not a demo script. Compare against your own Tuesday: your patients, your prescriptions, your languages, your tolerance for a paste step. For the wider picture of how a standalone fits any chart system, our [any-EHR export guide](../ai-scribe-any-ehr-export/) walks the workflow across Cerner, Epic, athenahealth, and the rest. The full price ladder, no asterisks, is on the [pricing page](../../pricing/).

We will make the cheap call when it is right: if you are all-in on Cerner and Oracle's agent covers your day, use it. If your work spills outside Millennium, or your notes need more than a transcript, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run it on a real clinic week. A 7-day trial on your own visits will tell you more than any table here. Then let the paste step, or the absence of one, decide it for you.

---

## DeepScribe Pricing: What It Actually Costs in 2026
https://patientsquare.com/us/blog/deepscribe-pricing/
Published 2026-07-01 · Updated 2026-08-27 · Tags: pricing, ai-scribe, deepscribe, comparison

DeepScribe publishes no price and gates every quote behind a demo. Here are third-party estimates and a published $79 alternative with an assisted trial.

DeepScribe publishes no per-clinician price. Its site is demo-only, and the pricing URL 404s. Third-party review sites estimate roughly $200 to $750 per provider per month depending on practice size, with EHR-integrated plans and setup fees on top. Those are outside estimates, not DeepScribe numbers. To learn your actual rate you have to book a sales call.

Short version: DeepScribe doesn't publish a price. Its pricing page 404s, and every quote runs through a sales call. Third-party review sites estimate somewhere between **$200 and $750 per provider per month**, but those are outside guesses, not DeepScribe figures, and they don't include a record system, because DeepScribe is a scribe, not an EHR. If you want a number you can read before you talk to anyone, Patient Square lists it: **$79 per provider per month** for the scribe on annual billing, or **$119** with a bundled AI EHR. You can request a 7-day trial through a short setup call.

This isn't a DeepScribe takedown. It's a good scribe, and it's clearly won trust in oncology. The point is the price, or the fact that you can't find it, and what that tells you about the buying process.

> **Key takeaways**
>
> - DeepScribe publishes no per-clinician price; the pricing page returns a 404 and the site is demo-only.
> - Third-party estimates run $200 to $750 per provider per month, often with EHR-integration add-ons and $500 to $1,000 setup fees.
> - There's no verifiable free tier or trial; Capterra lists none.
> - DeepScribe is a scribe only, not an EHR, and it's aimed at enterprise health systems and oncology.
> - Patient Square publishes $79 (scribe) and $119 (scribe plus AI EHR), with an assisted 7-day trial.

## What does DeepScribe cost per month?

Here's the honest answer: nobody outside DeepScribe knows for sure. The company's site is built around "Request a demo," and the URL where a pricing page would sit returns a 404. Capterra, which tracks this kind of thing, lists DeepScribe with "Contact vendor for pricing" and no free trial. So there's no first-party number to quote.

What you can find are third-party estimates, and they don't agree with each other. Here's the range the review sites land on.

| Source (third-party estimate) | Estimated cost per provider / month |
|---|---|
| Software Finder | ~$350–$500+ (EHR-integrated adds ~$100) |
| Software Finder (by practice size) | $200 solo to $5,000+ multi-location |
| Vero (veroscribe.com) | $350–$750 |

Read those as directional, not as quotes. They come from review and comparison sites, some of which sell competing scribes, and they contradict each other on the floor ($200 versus $350). Every one of them is an estimate. DeepScribe itself confirms none of them.

Setup isn't free either. The same trackers mention **$500 to $1,000 in setup fees** and an extra charge for EHR-integrated plans. So the real total is the estimate plus onboarding plus whatever the integration costs.

If you'd rather see a real number, ours is published and starts at $79.

## Why can't you find DeepScribe's price?

Because DeepScribe sells the way enterprise software sells. Price tracks system size, integration scope, and a contract, so there's no single sticker to post. That's normal for a company chasing health-system and oncology deals. Its homepage leads with large-system logos, not a checkout.

It also tells you what buying will feel like. To learn your price, you book a demo, get scoped, and negotiate. That's a reasonable process for a 200-clinician system with an IT team. For a small practice, having to phone someone to find out what a subscription costs is friction you feel before you've written a single note.

Published pricing works the other way around. A practice should be able to read the price before speaking with anyone, then request a real-workflow trial with a clear start point. That's why our [pricing page](/us/pricing/) lists the full ladder with no asterisks.

## DeepScribe is a scribe, not an EHR: the bundle math

This is the part that changes the comparison. DeepScribe documents the visit and writes into your existing chart. It doesn't give you the chart. So if you're pricing a practice from scratch, DeepScribe is one line item, and your EHR is another.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. That's the scribe and the record in one bill.

| | DeepScribe (estimated) | Patient Square |
|---|---|---|
| Ambient scribe | Yes | Yes |
| Bundled EHR | No (integrates with yours) | Yes, at Copilot ($119/mo annual) |
| Published price | No | Yes ($79 / $119 / $199) |
| Free trial | Demo-led, none verifiable | 7-day trial |
| Setup fee | $500–$1,000 (estimate) | None |
| Target buyer | Enterprise / oncology | Independent practices |

If you already run an EHR you love and only need the note, DeepScribe or our Assist plan at $79 both fit. If you want to stop paying for two systems, the bundle is the cheaper path. See the note quality on your own visit type before you decide.

## What you'd give up choosing a published-price scribe over DeepScribe

There's a real trade, and pretending otherwise sets you up to be disappointed.

DeepScribe has gone deep on oncology, with an enterprise deployment model, dedicated integration work, and a track record across large community-oncology groups. If you're a system that needs the scribe wired into a complex EHR across many clinicians, that depth is the point, and a self-serve tool isn't the same category.

You'd also be trading a scoped enterprise rollout for a lighter, assisted practice setup. For a small practice that can be a feature. For a health system with a compliance review and an integration team, the enterprise process exists for a reason.

What you keep with the published-price route is the part a small practice uses every day: a clean note in about two minutes, a visible rate, and an assisted trial that begins after the workspace is ready. For the wider field, our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup and the [Ambience Healthcare pricing](/us/blog/ambience-healthcare-pricing/) breakdown cover the other enterprise-priced options.

## When DeepScribe is the better choice

Pick DeepScribe if you're an oncology group or a health system that wants an ambient scribe built around your specialty and deployed across your EHR with enterprise support. That focus is real, and it's what DeepScribe is investing in. Switching to a general-purpose self-serve tool to save on a seat price would cost you the specialty depth you were buying.

Choose a published-price scribe if you're an independent practice that wants a note in two minutes, a price you can read, an assisted trial with a clear start point, and perhaps the record system in the same bill. That describes most of the practices reading this page.

## How to compare in a week

Skip the spec sheet and run the real test:

1. Ask DeepScribe for the all-in quote in writing: subscription, EHR-integration fee, and setup. Don't accept a range.
2. Decide whether you also need an EHR. If you do, add that vendor's price to DeepScribe's, then compare against a bundle.
3. Match the clinical output: note, ICD-10 suggestions, and a prescription draft, so you're comparing like for like.
4. Settle the audio question with every vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits. A scripted demo flatters every scribe equally.

The receipts behind our claims, encryption, access, and audit status, are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to check the note against your own visits, then run the 7-day trial on a real clinic week. When a vendor won't publish a number, that's information too.

---

## DocOnline Alternatives for Doctors & Clinics (2026)
https://patientsquare.com/in/blog/doconline-alternatives-india/
Published 2026-07-01 · Updated 2026-08-27 · Tags: alternatives, comparison, pricing

DocOnline is a teleconsult and corporate-health network, not clinic software. See the decision path for practices and a bundled AI EHR from ₹2,399 per doctor.

DocOnline is a telemedicine and corporate-health platform, not clinic software you buy to run your own practice. It delivers consultations to patients and employees through its own network of in-house doctors, sold to families (B2C plans) and employers (workplace wellness), in 14+ languages across 27+ specialities. You'd use DocOnline as a doctor by joining its network, not to document your own OPD.

If you're a doctor or a clinic looking at DocOnline as software to run your practice, here's the mismatch up front: DocOnline isn't that. It's a teleconsultation and corporate-health network that delivers consultations to patients and employees through its own panel of doctors. You join it or an employer buys it; you don't use it to document your own OPD. If your real need is software to run and document your practice, that's a different product. Patient Square's Practice Copilot is per doctor from ₹1,599/mo, with the AI Copilot EHR bundled at ₹2,399/mo (ex-GST, add 18%). You can book a demo and watch a SOAP note land in about two minutes.

Not a takedown, a category correction. Below: what DocOnline actually is, how its model differs, where a practice's real cost sits, and when DocOnline is the right thing for you.

> **Bottom line**
>
> - DocOnline is a teleconsult / corporate-health network (B2C family plans, B2B employer wellness), not clinic software.
> - Patient Square is software for your own practice: ambient AI scribe plus bundled AI EHR, per-doctor pricing.
> - If you want to run and document your clinic, Patient Square fits. If you want consult volume or employee healthcare, DocOnline fits.
> - They can coexist: document with Patient Square, join a network for reach. Different jobs, not rivals.

## DocOnline vs Patient Square: two different products

They get compared because both say "healthcare" and "doctors." They do opposite jobs. Read the split.

| | DocOnline | Patient Square (Practice Copilot) |
|---|---|---|
| What it is | Teleconsult + corporate-health network | Software to run and document your practice |
| Who buys it | Families (B2C), employers (B2B) | Doctors, clinics, practices |
| For a doctor | You join the panel for consult volume | You run your own OPD with it |
| Core value | Consults delivered via in-house doctors | Ambient scribe + bundled AI EHR |
| Pricing model | Consult subscriptions (from ~₹399/consult) | Per doctor: ₹1,599/mo entry + GST |
| Documentation of your visits | Not the product | The whole point |
| Ambient AI scribe | No | Yes, Hindi + 20+ languages, English output |
| Bundled AI EHR | No | ₹2,399/mo + GST (Copilot tier) |

If you want more patients or employee healthcare, DocOnline's model is right. If you want your own clinic documented, keep reading.

## What DocOnline actually is

Give it a clear read. DocOnline is a telemedicine-led healthcare company that delivers care through its own in-house, telemedicine-trained doctors. It sells to families through subscription health plans and to employers through workplace-wellness and employee-assistance programs. Members get 24x7 consultations across 27-plus specialities in 14-plus languages, plus mental-wellness programs, chronic-disease management, medicine and diagnostics delivery, and access to a wide partner network of clinics, pathology centres, and pharmacies. Consults start from a few hundred rupees, and it reports strong satisfaction and volume.

That's a consult-delivery and corporate-wellness business, and it does that job well. A family wanting round-the-clock access, or an HR team wanting one health partner for staff, is exactly who DocOnline is for. Nothing below argues against that.

The confusion is only about what it isn't. DocOnline doesn't sell you a system to document the visits you run in your own clinic. If that's what you came for, [see what practice software looks like in a demo](https://patientsquare.com/in/).

## How the models differ, and why it matters for you

The two products sit on opposite sides of the consult. DocOnline is upstream of a doctor's panel time: it acquires the patient or the employer contract and routes the consult to a doctor. Its economics are consult subscriptions and employer contracts. As a doctor, you'd engage DocOnline to get more consults, not to handle the paperwork of consults you already have.

Patient Square is inside your own clinic. It doesn't bring you patients; it takes the documentation load off the patients you're already seeing. Its economics are simple per-doctor software: Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo, all ex-GST, add 18%. Unlimited visits and notes, no per-note metering, no setup fee, on the [pricing page](https://patientsquare.com/in/pricing).

So the choice isn't "which is cheaper." It's "which job do I have." Patient volume, or paperwork. They're genuinely different, which is why plenty of doctors could sensibly use both.

## Where a practice's real recurring cost sits

If you run your own clinic, the cost that quietly grows is documentation, and neither a consult network nor a family health plan touches it.

Indian consultations average about two minutes, per a 67-country BMJ Open study, among the shortest anywhere. In that window the record is what gets shortchanged, and a thin record is expensive later. Roughly 65,000 medical-negligence matters reach Indian courts and consumer forums a year, and the defence that holds is a complete contemporaneous note. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A teleconsult network run by someone else's doctors doesn't help your own OPD records. A scribe that finishes your note during the visit does.

That's Patient Square's job. Canonically: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens as you consult, in Hindi, Tamil, Bengali, and 20+ Indian languages, even code-mixed, and returns a clean English note. Book a demo and test it on a real clinic day.

## What Patient Square doesn't do

Be honest about the boundary. Practice Copilot can use Patient Square EHR or work alongside an existing EHR, but it is not a consult network. We claim capture on web or mobile; we do not market a patient-facing teleconsult product, video-consult network, or employer-wellness program like DocOnline. If a built-in consult network or corporate-health delivery is your core need, DocOnline is built for it and we aren't.

Keep the rest of the scope straight too. We claim a bundled AI Copilot EHR at the plan level, not a list of internal modules the product pages don't name. eRx is draft-only, no pharmacy transmission. On compliance, handled to DPDP Act 2023 standards, SOC 2 Type II audit in progress (not certified), ABDM integration on the roadmap, not live. Records born digital, ready for the ABHA-linked era on your timeline. We don't claim live ABDM you can switch on today.

What you get is the documentation win for your own practice: ambient capture in the patient's language, a clean English note the moment they leave, ICD-10 suggestions, and a prescription draft to review and sign. Notes belong to your clinic, export or delete any visit anytime.

## When DocOnline is the better choice

Choose DocOnline if the job is consults or corporate health, not documenting your own clinic. If you're a doctor who wants to join a teleconsult panel for extra volume, or an employer looking for one partner to cover staff healthcare, mental wellness, and 24x7 access, DocOnline is purpose-built for that and has the network to deliver it. Software to write your own notes isn't competing with that; it's a different thing entirely.

Choose Patient Square if you run your own practice and the pain is documentation and records. You get published per-doctor pricing, an ambient scribe in Indian languages, and a bundled EHR without a project. And the two aren't mutually exclusive: a doctor can document their own clinic with Patient Square and still join a network for reach. Pick by the job in front of you.

## How to decide this week

Skip the apples-to-oranges comparison and answer one question first:

1. Do you want more patients, or less paperwork? More patients points to a consult network like DocOnline. Less paperwork points to a scribe.
2. If it's paperwork, shortlist per-doctor practice software with published pricing and no setup fee.
3. Match the clinical output: a structured note, ICD-10 suggestions, and a checked prescription draft, like for like.
4. Trial on real OPD visits in your own languages, Hindi or Tamil in, clean English note out, not a scripted demo.
5. Settle the data question with any vendor: hosting, ownership, and the true ABDM status, roadmap or live.

The security details, encryption, access, audit status, sit on our security page, and the per-doctor ladder with no asterisks is on the [pricing page](https://patientsquare.com/in/pricing). Book a short demo to check note quality against your own visit type. If you want consult volume or employee healthcare, DocOnline is the right partner. If you want your own clinic documented, you're in the right place.

---

## NHCX for Clinics: How the Health Claims Exchange Changes Cashless
https://patientsquare.com/in/blog/nhcx-claims-explained-clinics/
Published 2026-07-01 · Updated 2026-09-08 · Tags: nhcx, abdm, cashless, claims, india

What the National Health Claims Exchange is, where its rollout actually stands, and what an Indian clinic should do now so its notes are ready for a claim on NHCX.

NHCX stands for the National Health Claims Exchange. It is a single digital rail built by the National Health Authority under the Ayushman Bharat Digital Mission, in consultation with IRDAI, that lets hospitals, insurers, and TPAs exchange claim messages in one standard format instead of through dozens of separate insurer and TPA portals. It runs on the FHIR healthcare data standard.

If your billing desk keeps a mental map of which insurer wants which portal and which TPA still takes a PDF over email, the National Health Claims Exchange is aimed at that mess. NHCX is a single digital channel, built by the National Health Authority under the Ayushman Bharat Digital Mission and shaped with IRDAI, for hospitals, insurers, and TPAs to pass claim messages back and forth in one standard format. This is the clinic-owner's read: what it actually is, where the rollout really stands right now, and the small set of things worth doing before it reaches your OPD.

> **Key takeaways**
>
> - NHCX is one interoperable claims rail, not a new insurer and not a new set of rules. It replaces the portal-per-payer patchwork with a single standard channel.
> - It is in rollout, not evidence of a universal clinic cut-over. NHA launched NHCX nationally on 29 June 2026 and described the NHCX–HMIS implementation as a pilot in July.
> - NHCX runs on FHIR, the same healthcare data standard the rest of ABDM uses, and rides on the ABDM identity layer (ABHA, HFR, HPR).
> - It does not change the IRDAI cashless clocks. The one-hour and three-hour timelines come from the 29 May 2024 Master Circular and apply either way.
> - What a clinic can do now: sort out ABDM basics and keep per-visit documentation complete, so the claim behind every pre-auth is clean before it hits any rail.

_Source: PIB / Ministry of Health & Family Welfare releases dated 27 June and 17 July 2026; NHCX portal. Sources checked 8 September 2026._

## What is the National Health Claims Exchange, actually?

Strip away the acronyms and NHCX is a shared pipe. The National Health Authority, the same body that runs the Ayushman Bharat Digital Mission, built it in consultation with IRDAI so that a claim or a pre-authorisation can move between a hospital, an insurer, and a TPA over one standardised connection rather than a different portal for each payer.

The problem it targets is one every Indian clinic already lives with. There is no common language for a claim. One insurer wants a web form, another wants documents uploaded to a TPA portal, a third accepts email, and each has its own fields and quirks. Your desk absorbs that fragmentation as time: re-keying the same case into different systems, chasing status across channels, waiting on settlements that hospitals have long reported stretching to a month or more. NHCX is the attempt to give every party one machine-readable format and one route, so the message stops getting reshaped at every hop.

It sits inside ABDM by design. NHCX uses FHIR, the international healthcare data standard the rest of the digital-health stack already runs on, and it leans on the same identity layer: the ABHA number that ties a claim to a verified patient, the Health Facility Registry that identifies your clinic, and the Healthcare Professionals Registry that identifies your clinicians. If you have read our [plain-English TPA and cashless glossary](/in/blog/tpa-full-form-cashless-explained/), think of NHCX as re-plumbing the pipe that pre-auth and claim messages already travel through, not as a new player at the table.

## Where does the NHCX rollout actually stand?

This is the part where marketing tends to outrun reality, so here is the careful version. The Ministry of Health and Family Welfare announced NHCX's national launch for 29 June 2026. A later NHA review on 17 July still described the NHCX–HMIS implementation as a pilot and discussed an implementation roadmap. Those statements support active rollout; they do not establish a universal clinic cut-over.

The safe procurement question is therefore specific: can your hospital, payer or TPA, and software exchange the claim types you need in production today? Ask for a successful production transaction and the supported NHCX FHIR profiles. A launch release or sandbox demonstration does not answer that question.

There is also a provider incentive, but it is easy to quote the obsolete amount. The current DHIS framework has a separate category for eligible AB PM-JAY claims linked to ABHA and filed in FHIR format through NHCX, with additional facility, DSC, security, version, and cap conditions. The [source-dated DHIS guide](../abdm-incentives-for-doctors/) owns that volatile rate and its next review date. Do not carry an old ₹500 figure into a 2026 forecast.

The honest summary: official sources show a national launch and an implementation pilot, not universal completion. Be ready, but verify every participant in your own transaction path before treating NHCX as live for your clinic.

## How is a claim on NHCX different from the process you run today?

The clinical work is identical. The message routing is what changes.

Today the flow is per-payer. Your insurance desk figures out the right portal or format for that patient's insurer or TPA, keys the case in, and tracks the response wherever that particular payer publishes it. Multiply that across every payer your clinic sees and you get the portal maze most billing teams describe.

On NHCX, the same pre-auth or claim goes out once, in one FHIR-based structure, and the response comes back through the same standardised channel. The pre-authorisation still gets assembled from the treating doctor's diagnosis, indication, and plan. The insurer still decides against the policy terms. What compresses is the friction in between: fewer formats to maintain, less re-keying, a cleaner audit trail of who sent what and when. For the patient, the promise is faster cashless approval and discharge, because a structured message is quicker to read and act on than a stack of scanned documents.

One caution worth stating plainly. A standardised rail moves a claim faster; it does not make a thin claim approvable. If the underlying note is missing the indication or the diagnosis does not match the plan, NHCX carries an incomplete claim just as efficiently as a complete one. The rail is only as good as what you put on it.

## Does NHCX change the IRDAI cashless timelines?

No, and it is worth being exact because the two get blurred together. NHCX is the transport layer. The timelines are the rulebook, and they live in a different document.

The one-hour cashless authorisation clock and the three-hour discharge authorisation clock come from the IRDAI Master Circular of 29 May 2024, not from NHCX. Those clocks apply to a cashless claim whether it travels over NHCX or an older insurer portal. We walk them in detail in the [IRDAI cashless rules explainer](/in/blog/irdai-cashless-rules-doctors/); the short version is that the insurer has to decide a cashless request within an hour and grant final discharge authorisation within three hours, and if it overruns the three hours it bears the extra hospital charges.

What NHCX is meant to do is help a claim meet those clocks, not reset them. A structured, machine-readable message is faster for a pre-auth desk to process than a PDF someone has to open and interpret, so a well-formed claim on a fast rail is more likely to clear the one-hour and three-hour marks without a round of queries. The clock is the deadline; NHCX is a faster way to get the message there. Neither one waives a policy term.

## What should a clinic do now to be ready for NHCX?

Two moves, and both pay off even if NHCX takes another year to reach your payers.

The first is the ABDM identity layer, because NHCX rides on it. Get your clinic registered in the Health Facility Registry so it has a verified HFR ID, and get your clinicians onto the Healthcare Professionals Registry. This is the same groundwork that underpins linking records to a patient's ABHA number, and it is the prerequisite for transacting on the exchange later. Doing it now means you are not scrambling for registrations the week a major insurer asks you to onboard.

The second is documentation, and it is the one entirely inside your control. NHCX standardises the container a claim travels in, but the content of that container is still your clinical note: the diagnosis, the indication for treatment, the plan. A machine-readable claim assembled from a thin or inconsistent note is a thin claim in a tidy envelope. The clinics that will get the most out of NHCX are the ones already producing complete, consistent per-visit records, because those feed a clean pre-auth on any rail. If cashless queries at your desk keep clustering on missing indications or summaries that do not hold together, that is a note-quality gap you can close today, independent of any exchange. Our reads on [how notes affect cashless approvals](/in/blog/ai-scribe-cashless-claim-documentation/) and [whether better notes cut claim denials](/us/blog/ai-scribe-claim-denials-documentation/) draw that line carefully.

## Where does an AI scribe fit, and where does it not?

At the note, and nowhere near the exchange. We will be blunt about the boundary, because this is exactly the kind of claim a health vendor is tempted to overreach on.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Read what is not in that sentence. It does not submit claims. It does not file pre-authorisations. It does not connect to NHCX, to any insurer, or to any TPA. ABDM and NHCX connectivity are not features we ship; they sit on a roadmap, not in the product, and we never describe ourselves as ABDM-integrated or NHCX-integrated. The scribe writes the clinical note, full stop.

The benefit to your claims is upstream and indirect, and it is deliberately small. A complete, consistent note is better raw material for whoever prepares the pre-auth, so the request that goes out, over NHCX or an older portal, is cleaner and clears the IRDAI clock with fewer queries. The ICD-10 outputs are suggestions for your coder or billing desk to confirm, not a coding engine and not a claim submission. For an Indian OPD there is a practical detail: the scribe captures the code-mixed Hindi and English of a real consult, and the note always comes back in clean clinical English. Visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. Data is encrypted in transit and at rest, notes belong to your practice to export or delete, and a SOC 2 Type II audit is underway; the full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That is the whole claim. Better notes in, faster and cleaner pre-auth out. The rail underneath, NHCX or otherwise, is somebody else's job.

## The short version, and where to look next

NHCX is one standard channel for health-claim messages, built by the National Health Authority under ABDM on the FHIR standard, meant to replace the portal-per-payer patchwork. Official sources checked on 8 September 2026 show a 29 June national launch followed by an NHCX–HMIS implementation pilot and roadmap review in July—not proof of a universal clinic cut-over. It does not change the IRDAI one-hour and three-hour cashless clocks; it aims to help claims meet them. The two useful preparations are still to verify production support across your hospital, payer or TPA, and software, and to keep per-visit documentation complete.

When cashless delays involve missing indications or inconsistent summaries, review the clinical record and the claim packet together. Check whether the indication, findings, treatment, and discharge summary agree before submission. A complete note supports the packet; it does not establish NHCX connectivity or guarantee acceptance.

---

## DeepScribe vs Freed: Which AI Scribe, and a Third Option
https://patientsquare.com/us/blog/deepscribe-vs-freed/
Published 2026-06-30 · Tags: ai-scribe, comparison, deepscribe, freed

DeepScribe is sales-led and enterprise-priced; Freed publishes $39–$119/mo self-serve. Which fits your practice, plus a bundled-EHR option at $119/mo.

Pricing model and buyer. DeepScribe is sales-led and enterprise-priced; it publishes no per-provider number, and third-party estimates put it near $400–$500 a month. Freed publishes its prices: $39 a month for a capped Starter, $79 for unlimited Core, $119 for Premier with EHR push and ICD-10. DeepScribe targets groups and systems; Freed is self-serve for independents.

DeepScribe and Freed are two of the most-searched AI scribes, and they barely compete. DeepScribe is sales-led and enterprise-priced, built for groups and systems; Freed publishes self-serve prices from $39 to $119 a month for independents. Pick DeepScribe if you're a system that wants deep EHR integration; pick Freed if you're a solo doctor who wants a note tonight. And if you want the note plus a chart you own, there's a third option: a scribe that bundles an EHR at $119 a month. You can book a demo and see a finished note before you choose.

Here's the honest head-to-head, then where the third option fits.

> **Key takeaways**
>
> - DeepScribe is sales-led; it publishes no per-provider price. Third-party estimates land around $400–$500/mo depending on EHR integration.
> - Freed publishes prices: $39/mo Starter (40 notes), $79/mo Core (unlimited), $104 annual / $119 monthly Premier (EHR push, ICD-10).
> - Neither ships an EHR. Both write into your existing chart.
> - DeepScribe suits groups and systems; Freed suits independents.
> - A bundled-EHR scribe at $119/mo annual is the third option when you want the note and the chart together.

| | DeepScribe | Freed | Patient Square |
|---|---|---|---|
| Published price | No (quote only) | Yes ($39/$79/$119) | Yes ($79/$119/$199) |
| Est. / list monthly | ~$400–$500 (estimate) | $39–$119 | $79–$199 |
| Buying path | Sales-led | Self-serve | Assisted setup |
| Bundled EHR | No | No | Yes (Copilot, $119/mo annual) |
| Target buyer | Groups, systems | Independents | Independents, small groups |
| Free trial | Demo required | 7-day | 7-day |

Freed and Patient Square figures are from each vendor's pricing page (July 2026). DeepScribe publishes no price; the range is a third-party estimate, not a DeepScribe quote.

## What separates DeepScribe from Freed

Start with the buyer, because that's what actually differs. DeepScribe sells to groups and health systems. It integrates with major EHRs like Epic and athenahealth, deploys with a sales and implementation process, and prices per contract, which is why there's no public number. That model makes sense at scale; it's heavy for a solo doctor.

Freed goes the other way. Self-serve signup, published prices, a 7-day trial you start yourself. It's built for the independent clinician who wants to be documenting by this afternoon without a procurement call. The two tools show up on the same search results, but they're aimed at different practices with different budgets.

So "which is better" is the wrong question. "Which buyer are you" is the right one. If you're weighing the self-serve field more broadly, our [best AI medical scribes](/us/blog/best-ai-medical-scribes/) roundup lays it out, and you can book a demo to see how a bundled option compares. For a fuller breakdown of what DeepScribe is estimated to cost before you get a quote, [DeepScribe pricing](/us/blog/deepscribe-pricing/) pulls together the third-party ranges. And if you want the broader context on just DeepScribe vs the alternatives field, [DeepScribe alternatives](/us/blog/deepscribe-alternatives/) covers that.

## DeepScribe vs Freed on price

Freed is easy to price because Freed tells you. Per its pricing page (July 2026): Starter at $39 a month, capped at 40 notes; Core at $79 a month, unlimited notes but monthly billing only; Premier at $104 a month on annual billing or $119 monthly, which adds EHR push and ICD-10 and CPT codes. Groups is a custom quote.

DeepScribe is harder, because DeepScribe publishes nothing. You request a demo and get a quote scoped to your practice. Third-party estimates put it around $400 to $500 per provider a month, higher with EHR integration, per software-comparison sites, but treat that as a directional anchor, not a DeepScribe figure. The gap between "$79 published" and "$400+ estimated, quote required" isn't really about the dollars. It's about whether you want to phone someone to learn your price.

Patient Square sits in the published camp, in US dollars, on the [pricing page](/us/pricing/): $79 for Assist, $119 for Copilot with the bundled AI EHR, $199 for Autopilot, per clinician on annual billing, unlimited visits and notes, no per-note metering. No quote, no sales cycle to learn what you'll pay.

## Do DeepScribe or Freed include an EHR? Neither does

Both tools share one gap, and it's the one the third option fills. Neither DeepScribe nor Freed ships a record system. Freed's Premier tier pushes the finished note into your EHR via a browser extension; DeepScribe integrates with major EHRs on enterprise deployments. Either way, the chart is something you already own and pay for separately.

For a lot of practices that's fine. But if you're reading a scribe comparison because your documentation is broken AND your chart is clunky, you're really shopping for two things, and both of these tools solve only one. Stacking a scribe subscription on top of a separate EHR is two logins, two renewals, and a handoff step in between.

Patient Square's Copilot plan bundles both. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. At the Copilot tier ($119/mo annual) that scribe ships with a bundled AI Copilot EHR, so the note lands in the chart you're already in. If your gap is "note plus chart," book a demo and see the two together.

One honesty note on scope: our eRx is a draft you review and sign, not pharmacy transmission, and ICD-10 is suggestions, not a certified coding engine. Freed's Premier lists CPT codes too; if coding depth is central to your buy, put it on your demo checklist for all three.

## The per-visit math for an independent practice

Run the arithmetic. Say you see 20 patients a day, 20 days a month, 400 visits.

| | DeepScribe (est. ~$450/mo) | Freed Core ($79/mo) | Patient Square Copilot ($119/mo) |
|---|---|---|---|
| Monthly cost per clinician | ~$450 | $79 | $119 |
| Visits per month | 400 | 400 | 400 |
| Cost per visit | ~$1.13 | $0.20 | $0.30 |
| Bundled EHR | No | No | Yes |

DeepScribe's per-visit cost is a third-party estimate; DeepScribe publishes no price. Freed and Patient Square figures are published list prices on annual/Core billing.

All three are cheap per visit against an evening lost to charting. So price alone doesn't decide it. What decides it is what the money buys: DeepScribe buys enterprise integration you'll use at scale; Freed buys a clean self-serve note; Patient Square's Copilot buys the note plus the chart. Match the spend to the gap you actually have. If you want the enterprise-versus-self-serve version of this, [Abridge alternatives](/us/blog/abridge-alternatives/) covers that end.

## When DeepScribe is the better choice, and when Freed is

Pick DeepScribe if you're a group or health system that wants deep EHR integration, an enterprise contract, and a vendor that shows up with an implementation team. That's what DeepScribe is built for, and a self-serve tool can't match it at that scale. The sales cycle isn't friction there; it's how enterprise software gets deployed.

Pick Freed if you're an independent clinician who wants published pricing, self-serve signup, and a note the same day, and you already have an EHR you're keeping. It's a clean, focused tool for exactly that buyer, and the $79 Core tier is honest value.

Pick a bundled-EHR scribe if your gap is both the note and the chart, and you'd rather run one subscription than two. That's the case neither DeepScribe nor Freed is built for, and it's why we wrote this page. Note quality is close across all three; the deciding factor is your buyer profile and whether you also need the record system.

## How to decide in a week

1. Name your buyer. System that needs EHR integration at scale, DeepScribe. Independent who wants a self-serve note, Freed. Practice that wants note plus chart, a bundled tool.
2. For Freed, follow its self-serve trial path. For the bundled Patient Square option, request the assisted trial and wait for the workspace-ready confirmation. For DeepScribe, book the demo and expect a sales cycle.
3. Match the clinical output: a note plus ICD-10 suggestions plus a checked prescription draft, so you compare like for like.
4. Settle the audio question with every vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits. A scripted demo flatters every scribe.

The receipts behind our claims are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to see the note against your own visit type, then run the 7-day trial on a real clinic week. If your real gap is the note and the chart together, that's the option neither of these two was built to fill.

---

## DocPulse Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/docpulse-alternatives-india/
Published 2026-06-30 · Updated 2026-08-31 · Tags: alternatives, comparison, pricing

DocPulse is a broad HMS with quote-only pricing. If documentation is your real drain, here's the honest fork and a bundled AI EHR from ₹2,399/mo per doctor.

Breadth. DocPulse is a cloud HMS that bundles appointments, EMR, billing, pharmacy, lab (LIMS), inventory, IPD, telemedicine, and IVR booking into one platform for clinics, multi-specialty centres, hospitals, and clinic chains. If you want one system to run the whole operation, front desk to pharmacy to beds, that width is the reason to pick it.

If you're comparing DocPulse and wondering whether a broad HMS is what your clinic actually needs, start here: DocPulse is wide, one platform for appointments, EMR, billing, pharmacy, lab, IPD, and more, but its pricing is quote-only, and its documentation is form-filling, not an ambient scribe. If your real daily drain is writing notes, Practice Copilot addresses that workflow directly. It is priced per doctor from ₹1,599/mo, with Patient Square EHR from the Copilot tier at ₹2,399/mo or an alongside path for an existing EHR (ex-GST, add 18%). You can book a demo and watch a SOAP note land in about two minutes.

This isn't a takedown. It's breadth versus depth. Below: what DocPulse does well, why the price is hidden, where a clinic's real cost sits, and when DocPulse is the right pick.

> **Bottom line**
>
> - DocPulse is a full HMS (appointments, EMR, billing, pharmacy, lab, IPD, telemedicine), quote-only pricing.
> - Practice Copilot supports Patient Square EHR or an existing EHR, with an ambient AI scribe and published per-doctor pricing.
> - If your pain is notes, Patient Square is cheaper, faster to start, and knows your price up front (₹1,599/mo entry).
> - If your pain is running the whole operation on one system, DocPulse's breadth wins. We don't do pharmacy or beds.

## DocPulse vs Patient Square at a glance

Read the row that matches your problem, then decide.

| | DocPulse | Patient Square (Practice Copilot) |
|---|---|---|
| Core job | Full HMS: run the whole clinic/hospital | Documentation + records for doctors |
| Module breadth | Wide: pharmacy, lab, IPD, inventory, IVR | Focused: scribe + bundled AI EHR |
| Pricing | Quote-only, modular | Published, per doctor |
| India entry price | Not published | ₹1,599/mo + GST (Assist) |
| Bundled EHR price | Bundled in the quote | ₹2,399/mo + GST (Copilot tier) |
| Setup fee | In the quote | None |
| Ambient AI scribe | No (form-based EMR) | Yes, Hindi + 20+ languages, English output |
| Time to know your price | A sales call | The pricing page |

If you need pharmacy, IPD beds, and an in-house lab in one system, DocPulse's width is the point. If you need your notes done, keep reading.

## What DocPulse is genuinely good at

Fair credit. DocPulse is a legitimately broad HMS built for Indian workflows. It bundles appointments and queue management, EMR/EHR, medical billing, pharmacy, LIMS lab management, inventory, IPD, telemedicine, and IVR appointment booking into one interconnected system. It scales from a solo doctor up to a clinic chain running every branch from one dashboard, and it describes itself as HIPAA compliant and compliant with the DPDP Act 2023, with SHA-256 encryption on Google Cloud. Implementation runs about three to seven days for clinics, two to four weeks for larger hospitals.

That's a lot of surface area, and for the right buyer it's exactly right. A multi-specialty centre that wants one vendor for front desk, pharmacy, lab, and beds should look hard at DocPulse. Nothing below argues against that.

The question is whether you need all of it. Many doctors buy a full HMS and use a quarter of it, mostly the appointment book and the EMR forms, while the note-writing pain they actually had goes unsolved. If that's the risk, [see the focused alternative in a demo](https://patientsquare.com/in/) first.

## What does DocPulse cost, and why isn't it published?

DocPulse calls its pricing modular and transparent, but the actual rate isn't on the site. The pricing page is a request-a-quote form. Cost depends on which modules you switch on and how many users, so you learn your number in a sales conversation, not on a page. There's an assisted trial of roughly a week.

Quote-only isn't unusual for a full HMS, price tracks module mix and clinic size. But it has a cost of its own: you can't compare vendors on price without booking calls, and the renewal conversation later is shaped the same way. For a solo doctor or a small clinic, "call us to find out what it costs" is friction before you've even started.

Patient Square prices in the open. Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo. All ex-GST; add 18%, so Copilot is around ₹2,831/mo all-in. No setup fee, unlimited visits and notes, and the full ladder is on the [pricing page](https://patientsquare.com/in/pricing). You know your cost before you talk to anyone.

## Where the real recurring cost sits in a clinic

A full HMS organises your operation. It doesn't give you back the hour you lose to documentation every day. That's the cost most clinics never price, and it's the biggest one.

Indian consultations run about two minutes on average, per a 67-country study in BMJ Open, among the shortest measured. In that window, the record is what gets shortchanged, and a thin record is expensive later. Around 65,000 medical-negligence matters reach Indian courts and consumer forums a year, and the defence that holds is a complete contemporaneous note. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. Form-based EMR helps only if someone has time to fill the forms. In a packed OPD, nobody does.

That's the gap Patient Square is built for. Here's the canonical version: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens while you consult, in Hindi, Tamil, Bengali, and 20+ Indian languages, even code-mixed, and the note comes back in clean clinical English. Book a demo and run it on a real 8pm OPD.

## What you trade with Practice Copilot

No pretending here. Choosing Patient Square over DocPulse means giving up the operational breadth. Patient Square bundles an AI EHR at the Copilot tier, but it does not run pharmacy stock and suppliers, IPD and bed management, an in-house LIMS, or IVR call routing. If those modules are core to how your clinic runs, that's a real gap and DocPulse (or another full HMS) covers it.

Keep the EHR scope honest too. We claim a bundled AI Copilot EHR at the plan level; we don't enumerate internal modules like patient portal, telehealth capture, or a billing engine the product pages don't name. On compliance, Patient Square is handled to DPDP Act 2023 standards with a SOC 2 Type II audit in progress (not certified) and ABDM integration on the roadmap, not live. Records are born digital and ready for the ABHA-linked era on your timeline; we don't claim live ABDM you can flip on today.

What you keep is the documentation win: ambient capture in the patient's language, a clean English note the moment they leave, ICD-10 suggestions, and a prescription draft to review and sign. eRx is draft-only, no pharmacy transmission. Notes belong to your clinic, export or delete any visit anytime.

## When DocPulse is the better choice

Choose DocPulse if you're running an operation, not just consults. A multi-specialty clinic, a small hospital, or a clinic chain that needs pharmacy, inventory, in-house lab, IPD beds, and IVR booking under one roof is the buyer DocPulse is built for. Stitching a documentation tool to four other point systems would cost you more in integration and headaches than DocPulse's single platform, and its Indian-workflow depth (GST billing, TPA insurance, DPDP framing) is real. At that scope, a per-doctor scribe isn't the competitor; it's the wrong tool.

Choose Practice Copilot if you're a doctor or focused clinic whose real problem is finishing notes and you want published per-doctor pricing with no setup fee. Use Patient Square EHR or work alongside an existing EHR. Some clinics also retain a specialist HMS for pharmacy, IPD, LIMS, or IVR workflows, and that is a reasonable split.

## How to decide this week

Cut the demo-deck comparison and run the real test:

1. List what actually eats your day. If it's pharmacy, beds, lab, and inventory, you want a full HMS. If it's notes and records, you want a scribe.
2. If it's documentation, shortlist per-doctor tools with published pricing and no setup fee, so you can compare without sales calls.
3. Match the clinical output: a structured note, ICD-10 suggestions, and a checked prescription draft, like for like.
4. Trial on real OPD visits in your own languages, Hindi or Tamil in, clean English note out, not a scripted demo.
5. Settle the data question with any vendor: hosting, ownership, and the true ABDM status (roadmap or live).

The security details, encryption, access, audit status, sit on our security page, and the per-doctor ladder with no asterisks is on the [pricing page](https://patientsquare.com/in/pricing). Book a short demo to check note quality against your own visit type. If you need to run the whole operation, DocPulse earns the look. If you need your notes done, you're in the right place.

---

## Heidi Health Alternatives: Scribe Plus a Bundled EHR
https://patientsquare.com/us/blog/heidi-health-alternatives/
Published 2026-06-30 · Updated 2026-07-14 · Tags: ai-scribe, heidi, alternatives, ehr

Heidi Health is an ambient AI scribe. Patient Square is a scribe plus a bundled EHR and front-office automation, priced from $79/mo. The honest comparison.

Fast, EHR-agnostic ambient documentation. Heidi listens during the visit and drafts a structured note you paste into whatever chart you already use. It runs across specialties and offers a free tier for individual clinicians, which makes it easy to try. If all you need is a clean note and you're happy with your current EHR, that focus is the point.

If you're comparing Heidi Health, you're comparing an ambient AI scribe: it listens, it drafts a note, you paste that note into whatever EHR you already run. That's a clean, focused tool. Patient Square answers the same job from a different angle. It's a scribe too, but the Copilot plan bundles a real EHR and front-office automation, so the note lands in a chart instead of your clipboard, and the front desk runs itself a little. Published pricing starts at $79/mo for the scribe, and the EHR is bundled from $119/mo on annual billing. The full ladder is on our [pricing page](../../pricing/).

So which one fits? It depends on whether you want a note drafter bolted onto your current stack, or one tool that does the note, the chart, and the front office together. Below: what Heidi is genuinely good at, where Patient Square pulls ahead, the price math, and the honest case for staying with Heidi.

> **Key takeaways**
>
> - Heidi is an ambient AI scribe: EHR-agnostic, specialty-flexible, with a free individual tier as of 2026.
> - Patient Square is a scribe plus a bundled EHR (AI Copilot EHR) plus front-office automation, so the note has somewhere to go.
> - Patient Square US pricing: Assist $99/mo ($79 annual, no EHR), Copilot $149/mo ($119 annual, EHR bundled), Autopilot $249/mo ($199 annual).
> - The trade is scope. Heidi does one thing; Patient Square does three. If you love your current EHR, one thing may be all you want.
> - Both draft solid notes. The split is how much of the visit you want automated, not note quality.

## What Heidi Health is good at

Give Heidi its due. It's a focused ambient scribe that does the core job well: it captures the conversation and hands back a structured note, fast, without asking you to change the EHR you already know. It's EHR-agnostic by design, which is exactly what a clinician wants who has no intention of switching charts. And the free individual tier means a doctor can try it on a Tuesday afternoon without a contract or a card.

That's a real product with a clear point of view. A solo clinician who's happy with their current chart and just wants to stop typing at 9pm can pick Heidi up and feel the benefit the same day. Nothing here argues against that.

The question is whether a note drafter is the whole job you're solving. If your evenings go to charting *and* your front desk is buried in intake and follow-up, one tool that does both might be worth a look. You can book a demo and see the note quality against your own visits before deciding.

## Where Patient Square is different

Here's the honest split. Heidi ends at the note. Patient Square keeps going.

Patient Square is an ambient AI clinical platform, live now, built around Practice Copilot. The scribe layer works like Heidi's: it listens during the visit and drafts a structured SOAP note with ICD-10 suggestions and a prescription draft you review and sign. But the Copilot plan bundles AI Copilot EHR, a real electronic health record, so the note isn't something you copy anywhere. It's already in the chart. On the same plan, the front office gets automated too: intake, scheduling, and the follow-up busywork a scribe never touches.

That's the difference in one line. A scribe gives you a note and a clipboard. Patient Square gives you a note, a chart it lives in, and a front desk that runs a little on its own.

If you already have an EHR you love and won't leave, that bundle is more than you need, and we'll say so plainly below. But if you're shopping for a scribe *because* your whole workflow is a mess, the wider tool is the point. Book a demo and check whether the EHR and front-office pieces solve problems you actually have.

## What Patient Square costs

We publish the price. No sales cycle to learn what you'll pay.

Three US tiers, per clinician:

| Tier | Monthly | Annual (per mo) | What you get |
|---|---|---|---|
| Assist | $99 | $79 | Documentation essentials, no EHR |
| Copilot | $149 | $119 | Scribe plus AI Copilot EHR bundled, front-office automation |
| Autopilot | $249 | $199 | Everything, deepest automation |

The scribe starts from $79 a month on annual billing. The bundled EHR starts from $119 a month on annual billing, which is the Copilot tier. A 7-day free trial runs on the scribe, so you can test note quality on a real clinic week before committing.

Heidi's free individual tier is genuinely cheaper for a solo clinician who wants documentation and nothing else, and we won't pretend otherwise. What $119 a month buys that free doesn't is the EHR the note lands in and the front-office automation around it. Don't want those? Don't pay for them. Do want them? One bundled price is simpler than a scribe subscription plus a separate EHR bill. The full ladder with no asterisks sits on the [pricing page](../../pricing/).

## When Heidi is the better choice

There's a clean case for staying with Heidi, and it's worth stating.

Choose Heidi if you already run an EHR you're happy with and have no plans to move. Its EHR-agnostic design and free tier are built for exactly that clinician: someone who wants a note drafter on top of a stack that already works, not a new platform. Buying a bundled EHR you'll never switch to is money spent on a feature you leave idle. In that situation, a focused standalone scribe is the right call.

Choose Patient Square if the scribe is only half your problem. If your charting *and* your front office both eat time, and you'd rather buy one tool than wire a scribe to a separate EHR and a separate scheduling system, the bundle earns its price. The Copilot plan puts the note in a chart and automates the desk in one subscription.

The split is scope, not quality. Both tools draft good notes. Heidi assumes you have the rest of your stack sorted. We assume you might not.

Want to see the rest of this market? [Freed alternatives](../freed-ai-alternatives/) covers the solo-clinician scribe incumbent, and [Suki alternatives](../suki-ai-alternatives/) looks at the voice-assistant angle.

## How to decide in a week

Skip the feature-grid staring contest and run the real test:

1. Name your actual problem. Just charting? A scribe alone fits, and Heidi's free tier is easy to try. Charting plus front-office chaos? Weigh the bundle.
2. Count what you'd have to buy separately. If a Heidi-style scribe means also paying for an EHR and scheduling tools, add those bills before you compare.
3. Trial on real visits. Run Patient Square's 7-day scribe trial across your busiest clinic days and judge note quality against your own edits.
4. Settle the audio question with every vendor: stored or not, and for how long.
5. Check EHR fit. Keeping your chart? Confirm the scribe drops in cleanly. Open to switching? Look hard at the bundled EHR on the demo.

The price ladder with no fine print is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visit type, then run the trial on a real week. If a note drafter is the whole job, a focused scribe wins. If the note is only part of the mess, the bundle is what you're actually shopping for.

---

## Teleconsultation Rules in India: The NMC Guidelines, Plainly
https://patientsquare.com/in/blog/teleconsultation-guidelines-india-nmc/
Published 2026-06-30 · Updated 2026-07-22 · Tags: telemedicine, nmc, compliance, india

What the 2020 Telemedicine Practice Guidelines require for documentation, consent, and prescriptions, written for a working clinic, plus the medicine lists.

Yes. The Telemedicine Practice Guidelines were issued on 25 March 2020 by the Board of Governors of the Medical Council of India with NITI Aayog, and were placed in Appendix V of the 2002 Regulations on Professional Conduct and Ethics under the Indian Medical Council Act 1956. They carry validity under the National Medical Commission Act 2019. A registered medical practitioner who ignores them is exposed on professional-conduct grounds.

India's telemedicine rules are real, binding, and shorter than most doctors fear. The Telemedicine Practice Guidelines, issued on 25 March 2020 by the Board of Governors of the Medical Council of India with NITI Aayog, set out what a registered medical practitioner must do on a remote consult: confirm who the patient is, take and record consent, document the consultation like an in-person visit, and prescribe only within defined medicine lists. This walks each of those for a working clinic, and is general information, not legal advice; confirm specifics against the current guidelines and your medical council.

> **Key takeaways**
>
> - The guidelines are binding: they sit in Appendix V of the 2002 Professional Conduct Regulations and carry NMC Act 2019 validity.
> - You must document a teleconsult like an in-person visit: identity, consent, the conversation trail, and the prescription.
> - Medicines are sorted into List O, List A, List B, and a prohibited list (Schedule X, narcotics, psychotropics).
> - An AI scribe can produce the required note faster; it cannot make you compliant. That responsibility stays with the RMP.

## Are the telemedicine guidelines actually binding?

Yes, and this is the part doctors most often get wrong by treating them as advisory. The Telemedicine Practice Guidelines were issued on 25 March 2020 by the Board of Governors that then ran the Medical Council of India, in partnership with NITI Aayog. They were folded into Appendix V of the 2002 Regulations on Professional Conduct, Etiquette and Ethics under the Indian Medical Council Act 1956, and they remain valid under the National Medical Commission Act 2019.

In plain terms: this is professional-conduct law, not a suggestion deck. An RMP who consults remotely and ignores the documentation or prescription rules is exposed on conduct grounds if a complaint lands. Treat the guidelines as the standard of care for a remote visit, because the council does.

## What do you actually have to document?

The simplest rule the guidelines give you is the most useful one: keep records similar to an in-person consultation. That breaks into a few concrete things.

First, identity. The RMP confirms the identification and credentials of the patient or caregiver at the start. Second, the consultation trail, meaning the record of the conversation and the treatment advised, the same clinical note you'd write in clinic. Third, consent, captured in the patient's notes. Fourth, the prescription, in the standard format, sent to the patient. The guidelines also expect a log of the interaction itself: the phone record, the email thread, the chat transcript, or the video session that the consult ran on.

How long to keep all this? The guidelines point to the retention periods the various medical-record acts require, and they note a second reason to keep them: your own protection if the consult is ever disputed. A thin or missing record is a liability long after the visit ends.

## How does consent work for a teleconsultation?

Consent is documented, but it isn't always a signed form. The guidelines accept implied consent when the patient initiates the consult, the common case where someone calls or messages you for advice. When you or a health worker initiates the consult, explicit consent is expected. Either way, you record the consent, along with the basics of data privacy and confidentiality, in the patient's notes.

The practical takeaway: consent is part of the documented record, not a step you do verbally and forget. A note that captures the consult should capture that consent was taken and how. This is exactly the kind of structured detail a scribe-drafted note can carry, as long as you review and confirm it.

## Which medicines can you prescribe remotely?

This is where the guidelines are most specific, and where the risk of a misstep is highest. Medicines are sorted into lists:

| List | What it covers | Telemedicine rule |
|---|---|---|
| **List O** | Over-the-counter (paracetamol, antacids) | Generally prescribable |
| **List A** | Relatively safe, low abuse potential (eye drops, skin creams, some oral agents) | First prescription on a video consult; refills permitted |
| **List B** | Add-on medicines optimising an existing regimen | Prescribable for an established condition |
| **Prohibited** | Schedule X drugs; narcotic and psychotropic substances | Cannot be prescribed over telemedicine |

Beyond the lists, the prescribing standard is judgment-based. The guidelines let you prescribe over telemedicine only after a provisional diagnosis and when you're reasonably satisfied with the information gathered, and they require confirming the patient's age before prescribing. Some medicine categories have been amended since 2020, so check the current list rather than a two-year-old summary before you prescribe anything borderline.

A note on what we don't do here. AI Medical Scribe by Patient Square drafts a prescription as part of the note, which you review and sign; it is a draft, not e-prescribing, and it doesn't decide what's permissible under these lists. That decision is the RMP's, every time.

## So where does an AI scribe actually fit?

At the documentation layer, and nowhere near the compliance decision. We'll be blunt about the line, because health vendors blur it constantly. **An AI scribe does not make your teleconsultations compliant. You do, as the RMP.** What a scribe changes is the effort of producing the record the guidelines require.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On a teleconsult that means the conversation trail, the assessment, and a prescription draft arrive as a clean note for you to check, edit, and sign, instead of you typing it up after a back-to-back remote OPD. In a consult that runs in code-mixed Hindi and English, it captures the conversation and the note comes out in clean clinical English.

Here's the rest of the line we hold. We are not ABDM-integrated; that's on our roadmap, not live, so we don't link records to ABHA from inside the tool and we never call ourselves ABDM-compliant. We don't store the visit audio; it's processed in memory and discarded once the note drafts. Data is encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice to export or delete anytime. We handle data to DPDP Act 2023 standards, and a SOC 2 Type II audit is underway. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing is published and ex-GST: it starts from ₹1,599 per clinician a month on annual billing (the Assist plan), plus 18% GST (so Assist works out to about ₹1,887 a month all-in), with Copilot and Autopilot tiers above it and a 7-day free trial. If you want the wider documentation picture, the [NMC record-keeping guide](../nmc-record-keeping-ai-scribe/) covers what a clean clinical record needs, and the [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) covers the data side that telemedicine and in-person visits both have to meet. Or <a href="/in/security/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">review the security details</a> and ask where the audio goes and how the note reads after a remote consult.

---

## DrChrono Alternatives: A Modern AI Bundle for $119/mo
https://patientsquare.com/us/blog/drchrono-alternatives/
Published 2026-06-29 · Updated 2026-08-27 · Tags: alternatives, ehr, drchrono, comparison, pricing

DrChrono publishes no price and gates AI as an add-on. Here's the case for a bundled AI EHR from $119/mo with the scribe built in from day one.

DrChrono publishes no per-provider price on its website. Third-party estimates from sources like Pabau and EHR Source put entry-level plans between $199 and $299 per provider per month, with billing-inclusive tiers reaching $499-$599. All tiers require a custom quote. That opacity is itself a signal: you won't know your price until you've already been on a sales call.

DrChrono doesn't publish a price. If you want a number, you schedule a demo, talk to sales, and find out. Meanwhile, the AI scribe you've probably heard about, EverHealth Scribe, launched in March 2026 and it's included only in the Premium plan, an add-on on everything below. Patient Square's Copilot plan is **$119 per provider per month** on annual billing and bundles the AI Medical Scribe with the AI Copilot EHR from the first dollar, no tier-gating required. You can [see a note in about two minutes](/us/pricing/) before you talk to anyone.

That's the core comparison. What follows: what DrChrono is genuinely good at, why the pricing opacity matters, how the EverHealth Scribe add-on changes the math, what you actually give up by leaving, and when DrChrono is the smarter call.

> **Key takeaways**
>
> - DrChrono publishes no per-provider price; third-party estimates put entry plans at $199-$299/provider/month, billing-inclusive tiers at $499-$599.
> - EverHealth Scribe (launched March 2026) is only included in DrChrono's Premium plan; Foundation and Growth users pay extra.
> - Patient Square Copilot is $119/provider/month (annual) and bundles the ambient AI Medical Scribe with the AI Copilot EHR, with no plan-gating.
> - DrChrono's native iPad app and Apple Pencil support are genuinely differentiated. If you're iPad-first, that's a real reason to stay.
> - A 7-day trial on real visits, not a sales demo, is the only reliable way to compare note quality.

## DrChrono vs. Patient Square: side by side

| | DrChrono | Patient Square Copilot |
|---|---|---|
| Pricing transparency | No published rate; quote-required | $119/mo annual, listed publicly |
| Ambient AI scribe | EverHealth Scribe: Premium only, add-on on lower tiers | Bundled in Copilot tier and above |
| Bundled AI EHR | Yes (EHR is the product) | Yes, AI Copilot EHR included at Copilot tier |
| Native iPad app | Yes, cornerstone feature | Web or mobile browser |
| Migration / export | Patient record export available | EHR-ready export (PDF, HL7, FHIR) |
| Free trial | Demo-led | Assisted 7-day trial |
| HIPAA safeguards | Yes | HIPAA compliant; BAAs available |

Third-party pricing figures for DrChrono are estimates from Pabau and EHR Source, not DrChrono-published rates.

## What DrChrono is actually good at

Give credit where it's due. DrChrono, now branded DrChrono by EverHealth under EverCommerce, built its reputation as the iPad-first EHR, and that reputation holds. The native iOS app with Apple Pencil support is a genuinely different experience from browser-based charting. Point-of-care documentation on a tablet, with touch-optimized templates and a form builder you can customize per specialty, is the thing DrChrono does better than most cloud EHRs at its tier.

The platform also has a reasonably open API for a mid-market EHR, which matters if you want to wire in third-party tools without fighting integration walls. Implementation is fast too: most practices are live in two to four weeks. For practices that want the EHR, practice management, and billing in one system, DrChrono offers that stack. That billing depth is actually why the pricing conversation gets complicated, which we'll get to next.

If you chart at the bedside, at the exam table, or anywhere a keyboard is awkward, DrChrono is a legitimate recommendation. Nothing below argues otherwise.

## What DrChrono costs, and why nobody will tell you

Here's the friction: DrChrono's website has no prices on it. Every plan says "Request A Quote." That's normal for enterprise software; it's less normal for a small-practice EHR. Third-party review sites fill the gap. Pabau puts the entry-level estimate at $199/provider/month; EHR Source's early 2026 review estimates $299/provider/month for the EHR-only tier and $499-$599 for billing-inclusive plans. Annual contracts are standard, and some long-term users have reported annual price increases of 10-15%.

Be precise about those numbers. They're third-party estimates, not DrChrono rates. The point isn't the specific figure. It's that you can't learn your own price without going through a sales call first. And that's before you know what EverHealth Scribe will add on top.

The contrast is simple. Patient Square lists prices on the [pricing page](/us/pricing/). No call required. Copilot is $119/provider/month annually. You know before you sign.

## The EverHealth Scribe add-on math

DrChrono announced EverHealth Scribe in March 2026, built through a partnership with CarePilot. It captures the visit conversation, generates a structured note with ICD-10 suggestions, and drops it into your DrChrono chart for review. The underlying capability is real.

The problem is where it sits in the plan structure. On Foundation and Growth plans, EverHealth Scribe is a paid add-on. Only the Premium tier includes it. DrChrono publishes no price for that add-on, which means the EHR cost plus the scribe cost equals two unknown numbers. You sign for one, then negotiate the other.

On a 20-patient Tuesday, that matters. The AI Medical Scribe by Patient Square listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It ships inside the Copilot plan at $119/mo, bundled with the AI Copilot EHR rather than sold as a separate add-on. One line item, not two.

If you're shopping a DrChrono plan specifically for the scribe, run this comparison against the [best EHR for family practice](/us/blog/best-ehr-for-family-practice/) roundup to see how the all-in bundled cost stacks up before you commit to any quote.

## What you give up by leaving DrChrono

Don't minimize this. A few things are real.

If you chart on an iPad with Apple Pencil, DrChrono's native iOS app is purpose-built for that. A browser-based tool is functional but it's a different feel. Plenty of clinicians built their workflow around that tablet experience and genuinely don't want to give it up. Fair.

Billing integration is the other real trade-off. DrChrono's higher tiers include revenue cycle management as part of the platform. Patient Square doesn't have a billing engine; it focuses on the clinical side. If RCM in the same system is your evaluation center of gravity, DrChrono's upper tiers are built for that and a scribe-plus-EHR bundle isn't a direct substitute.

Template depth matters too. DrChrono has had a custom form builder and specialty-specific templates for over a decade. Patient Square offers specialty-aware templates ready out of the box, but a newer platform won't have the same years of specialty-specific tuning. If you've built a library of custom forms in DrChrono, that's migration work.

What you keep is what a 20-patient day runs on. A note ready about two minutes after the visit ends. ICD-10 suggestions at sign time. A prescription draft to review. Audio processed in memory and discarded the moment the note is ready, nothing retained. And a BAA available for any practice size, which isn't always automatic when you're a small account in a large software contract.

For practices weighing whether to carry an AI scribe on their current EHR or swap the whole stack, our [AI scribe vs. new EHR](/us/blog/ai-scribe-vs-new-ehr/) page walks that decision specifically.

## When DrChrono is the smarter choice

Stay with DrChrono if you chart on an iPad as your primary device and the native app is part of how you practice. That's not a feature, it's a workflow identity. Also stay if you need deep billing integration in the same system: DrChrono's higher tiers do that in a way a clinical-focused bundle doesn't. And stay if you're already trained on it and your custom templates make the switching cost real. Moving for its own sake is friction without a payoff.

Choose a bundled AI-scribe-plus-EHR if you want published pricing, a scribe built in rather than plan-gated, and an assisted 7-day trial after workspace setup, all without a second contract. Most practices that feel the quote-required friction and the add-on structure are in that camp.

The honest split: DrChrono for iPad-first clinicians who need billing depth in the same platform. Patient Square for practices where the scribe and the EHR being one thing, at one published price, is the point.

## How to decide this week

Don't compare spec sheets. Run real visits.

1. Ask yourself whether the iPad native app is a genuine requirement or a preference. If it's a requirement, DrChrono belongs on your shortlist and the browser alternative doesn't.
2. If it's a preference, shortlist tools with published prices and clearly documented trial setup.
3. Get a DrChrono quote. You need it to know the actual number. Do the same for any alternative, then compare scribe-bundled vs. scribe-as-add-on at whatever tier you actually need.
4. Run a 7-day trial on real visits. A scripted demo flatters every tool equally; a live clinic week doesn't.
5. Check the note quality on your specialty. Ambient documentation that produces a generic note fast is not the same as one that matches your documentation style.

The full price ladder is on the [pricing page](/us/pricing/), no call required. Book a short demo if you want to see a finished note on a real visit type before you request a DrChrono quote. For a small practice spending a chart-filled evening after every clinic day, knowing the price before you talk to anyone is its own argument.

For a broader look at how AI scribes work across any EHR, the [AI scribe with any EHR export](/us/blog/ai-scribe-any-ehr-export/) guide covers the integration path. And if you're evaluating the wider field of lower-cost EHRs, the [free EHR vs. AI scribe standalone](/us/blog/free-ehr-ai-scribe-vs-standalone/) comparison covers the other end of the market.

---

## eClinicalWorks Cost: The Real Per-Provider Math for 2026
https://patientsquare.com/us/blog/eclinicalworks-cost/
Published 2026-06-29 · Updated 2026-08-27 · Tags: pricing, ehr, eclinicalworks, comparison

eClinicalWorks EHR costs about $449 per provider monthly, with Sunoh billed per encounter. See the total-cost breakdown and a flat bundle from $119.

Third-party pricing trackers put eClinicalWorks near $449 per provider per month for the EHR-only plan and about $599 with practice management added. eCW doesn't publish a standard per-provider rate, so these are outside estimates. On top of the base fee you'll see per-statement charges, per-message fees, and Sunoh scribe costs that meter by encounter.

Short version: eClinicalWorks lists no public per-provider price, but third-party trackers put the EHR near **$449 per provider per month**, closer to $599 with practice management added, and the Sunoh scribe bills **per encounter** on top of that. The sticker looks low until you stack the add-ons. If you want the documentation piece and the record system in one flat bill, Patient Square's Copilot plan is **$119 per provider per month** on annual billing with the ambient scribe bundled in. You can see the note quality on a real visit before you switch.

This isn't an eCW takedown. It's a big, capable suite. The point is the *total* cost, because that's the number that surprises practices six months in.

> **Key takeaways**
>
> - eCW's per-provider price is roughly $449 (EHR only) to $599 (with PM), per third-party trackers; eCW publishes no standard rate.
> - The Sunoh scribe is a separate, per-encounter line item, so your documentation cost scales with patient volume.
> - Add-ons stack: patient-statement fees, messenger transaction charges, $2,000 to $5,000 per-provider implementation, and data migration.
> - Patient Square Copilot is $119 per provider per month annually, with an ambient scribe bundled, no per-note meter, no setup fee.
> - eCW still wins if you need a deep billing and RCM engine at scale; a flat bundle wins if you mostly want a note and a record.

## What does eClinicalWorks actually cost per month?

eClinicalWorks doesn't publish a plain per-provider number. Its pricing page routes you to a sales conversation, which is normal for a full practice-management platform. So the figures below come from third-party trackers that survey buyers, and they're estimates, not eCW quotes.

| eClinicalWorks plan | Estimated cost (per provider / month) |
|---|---|
| EHR only | ~$449 |
| EHR + Practice Management | ~$599 |
| EHR + PM + RCM add-ons | higher, quote-based |

Those numbers come from ITQlick and Software Finder's 2026 buyer surveys. Treat them as a directional anchor. Your real number depends on module mix, volume, and what you negotiate.

Here's the part that matters for documentation: the ambient scribe isn't in that base price. eCW pairs with **Sunoh.ai**, which bills on a per-encounter basis. So the more you document, the more you pay, visit by visit. That's a fine model if your volume is low and steady. It's a rough one if you run a heavy clinic day.

If you'd rather not do encounter math, check what a flat bundle covers.

## Why the eClinicalWorks sticker price hides the real total

The base subscription is the floor. The total is what shows up after implementation. Practices weighing eCW usually miss a few lines:

- **Per-encounter scribe fees.** Sunoh meters by visit. A 30-patient Wednesday costs more to document than a 12-patient Friday.
- **Patient-statement charges.** Fees apply per statement sent through the platform.
- **Messenger transaction fees.** eClinicalMessenger interactions can carry per-transaction costs.
- **Implementation.** Third-party trackers cite $2,000 to $5,000 per provider for setup, configuration, and training.
- **Data migration.** Moving records from your old system runs $2,000 to $10,000 or more, depending on volume.

None of that is unusual for enterprise practice-management software. But it means the number you signed for isn't the number you pay. For a small independent practice, the metered scribe is the sneakiest one, because it's the cost that never stops growing.

## eClinicalWorks vs a flat AI-scribe bundle: the total-cost view

Let's compare like for like. Say you run a two-provider practice, each seeing 400 visits a month.

| | eClinicalWorks + Sunoh (estimated) | Patient Square Copilot |
|---|---|---|
| EHR base (per provider / mo) | ~$449 | $119 (annual billing) |
| Ambient scribe | Sunoh, per-encounter | Bundled, unlimited |
| Per-note metering | Yes (Sunoh) | No |
| Setup / implementation | $2,000–$5,000 per provider | None |
| Practice management / RCM depth | Deep (add-on) | Not a billing engine |
| Published price | No | Yes |
| Free trial | Demo-led | 7-day trial |

Read that honestly. eClinicalWorks is a full revenue-cycle platform, and Patient Square isn't. If billing depth is the center of your evaluation, eCW's RCM tooling is a real reason to pick it. What Patient Square gives you instead is one predictable bill for the two things most practices actually touch every day: writing the note and keeping the record.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. You can put it in front of your own visit type and judge the note yourself.

## What you give up by leaving eClinicalWorks

Be clear-eyed about the trade. eCW isn't expensive by accident. You'd be walking away from:

- **A mature revenue-cycle engine.** eCW's billing, claims, and RCM workflows are deep and battle-tested across large practices. Patient Square offers ICD-10 *suggestions* to speed coding, not a claims-scrubbing platform.
- **A very wide module catalog.** Patient portal depth, telehealth, population health, and a long tail of integrations. If you use those heavily, weigh that.
- **An established switching path.** Big EHRs have big migration playbooks. That cuts both ways: the playbook exists, but so does the lock-in.

Patient Square's export claim is precise: **EHR-ready export (PDF, HL7, FHIR)**. That's a clean export, not a certified interoperability engine. If your practice depends on deep bidirectional feeds today, keep that in mind. For a broader look at bundled options, our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup and the [athenahealth EHR cost](/us/blog/athenahealth-ehr-cost/) breakdown cover the other end of the market.

## When eClinicalWorks is the better choice

Stay with eClinicalWorks, or pick it, if billing runs your practice. If you need a deep RCM engine, complex claims workflows, and a platform that scales to dozens of providers with enterprise support, eCW earns its cost. A flat scribe-plus-EHR bundle isn't competing at that level, and switching to save on a per-seat price would cost you more in lost billing capability than you'd save.

Choose a flat bundle if your day is mostly visits and notes, you want the scribe and the record in one predictable bill, and you're tired of the encounter meter climbing every busy day. That describes a lot of independent primary-care and specialty practices. The [pricing page](/us/pricing/) lists the full ladder with no asterisks.

## How to price your real eCW cost in an afternoon

Skip the marketing math and build your own number:

1. Get the eCW quote in writing, including the module mix you'll actually use.
2. Add Sunoh per-encounter cost times your real monthly visit count. Use a busy month, not an average one.
3. Add implementation and migration as one-time costs, amortized over your first year.
4. Compare that total against a flat bundle at $119 per provider annually with the scribe included.
5. Trial the alternative on a real clinic week before you decide. A demo flatters everyone.

The receipts behind our claims, encryption, access, and audit status, are on the [security page](/us/security/). Book a short demo to check the note against your own visits, then run the 7-day trial on a real week. For most independent practices, the flat bundle does the job you actually have without the encounter meter running in the background.

---

## EHR Software Cost in India: A Buyer's Guide to Hidden Fees
https://patientsquare.com/in/blog/ehr-software-cost-india-buyers-guide/
Published 2026-06-29 · Tags: pricing, ehr, buyers-guide, cost

What EHR software really costs in India: setup, per-user, AMC, and per-module fees rivals bury. Plus a bundled AI EHR from ₹2,399/mo, ex-GST.

The honest range is wide because most vendors quote, not publish. Cloud clinic EHRs commonly land between ₹800 and ₹3,000 per doctor per month, but the sticker price rarely includes setup, training, annual maintenance, or per-module add-ons. Patient Square publishes its number: the bundled AI Copilot EHR ships in the Copilot plan at ₹2,399 per doctor per month, annual, ex-GST, with no setup fee.

The real cost of EHR software in India is almost never the number on the sticker. Add setup, per-user seats, an annual maintenance contract, and per-module add-on charges, and a ₹1,000 quote can land near ₹2,500 in year one. This guide names every fee rivals bury, then anchors against a bundled AI EHR that publishes its price: Patient Square's Copilot plan at ₹2,399 per doctor per month, annual, ex-GST, no setup fee. You can open the [India pricing](/in/pricing/) in another tab and check it as you read.

The point isn't that cheaper is always better. It's that you can't compare vendors until you can see the whole bill. Most won't show it to you. So here's how to build it yourself.

> **Key takeaways**
>
> - Cloud clinic EHRs in India commonly run ₹800 to ₹3,000 per doctor per month, but the sticker rarely includes setup, AMC, or per-module fees.
> - Five hidden costs: setup/onboarding, per-user seats, annual maintenance (AMC, often 15-25% of licence), per-module add-on charges, and data migration.
> - A bundle can beat buying modules separately. Patient Square's Copilot plan folds the AI EHR, scribe, scheduling, and WhatsApp into ₹2,399/mo, ex-GST.
> - True cloud subscriptions usually include maintenance; a low monthly rate plus a yearly AMC means you add both before comparing.
> - Free EHRs like Bahmni carry no licence fee but real hosting and setup costs, and no AI documentation.

## What does EHR software actually cost in India?

The honest answer is a range, because the market is mostly quote-only. Ask ten clinic EHR vendors for a price and most will send you to a demo before they send you a number. From the ones that do publish, cloud clinic EHRs commonly sit between ₹800 and ₹3,000 per doctor per month. Lybrate, for one, publishes its clinic-management product from around ₹799 a month for a single clinic. Enterprise HMS and hospital systems run higher and almost always quote-only.

That spread is real, but it's also incomplete, because the monthly licence is only one line of the bill. The fees that decide whether an EHR is cheap or expensive usually sit below it, and they're the ones you have to ask about by name. Patient Square is on the transparent end: the bundled AI Copilot EHR ships at ₹2,399 per doctor per month in the Copilot plan, annual, ex-GST, and the number is on the page. Book a demo if you want to see the EHR before you compare it to anyone's quote.

## What are the hidden EHR costs vendors bury?

Five of them come up again and again. Build your comparison around these, not the sticker.

**Setup and onboarding.** A one-time fee to configure your account, import templates, and train staff. Enterprise HMS treats this as a project with its own invoice. Clinic EHRs vary: some waive it to win the subscription, some charge it separately. Patient Square charges no setup fee on any plan.

**Per-user seats.** The quote is per doctor, but your front desk, nurses, and junior doctors may each need a login, and each login may cost. A "₹1,500 a month" EHR can be ₹1,500 times five once the whole clinic is on it. Ask what a seat costs and who needs one.

**Annual maintenance contract (AMC).** A recurring fee, often 15 to 25% of the licence, for updates, patches, and support. Common on on-premise and self-hosted systems. A true cloud subscription usually folds this into the monthly price. If a vendor quotes a low monthly rate and a separate yearly AMC, add both before you compare.

**Per-module add-on charges.** Billing, lab, inventory, patient portal, and reporting are often sold separately, not included. The base price looks lean because half the product is behind a paywall. List the modules you actually need and price the bundle that includes them.

**Data migration.** Moving your existing records from paper or an old system can carry its own charge. If you're switching, ask for the migration cost up front, not after you've signed.

Here's how those stack up on a deliberately cheap-looking quote:

| Line item | Buried quote | What it becomes |
|---|---|---|
| Base licence, 1 doctor | ₹1,000/mo | ₹1,000/mo |
| Setup / onboarding | "one-time" | ₹5,000-20,000 once |
| Extra seats (front desk, nurse) | not in sticker | +₹500-1,000/mo each |
| AMC (18% of annual licence) | separate | +~₹180/mo equivalent |
| Billing + lab modules | add-on | +₹500-1,500/mo |
| Data migration | on request | ₹5,000-25,000 once |

The ₹1,000 sticker is realistically a ₹2,500-plus monthly commitment once the clinic is fully on it, plus one-time fees. That's not a scam; it's just how modular pricing works. You only get burned if you compare stickers instead of totals.

## Is a bundled AI EHR cheaper than buying modules?

Often, yes, when the bundle covers what you need. The alternative to a bundle is stitching together a scribe from one vendor, an EHR from another, scheduling from a third, and messaging from a fourth. That's four bills, four contracts, four support desks, and four things that have to talk to each other.

Patient Square's Copilot plan folds the AI Copilot EHR together with the AI Medical Scribe, scheduling, and WhatsApp messaging into one line: ₹2,399 per doctor per month, annual, ex-GST (₹2,831 with 18% GST). There's no per-module add-on charge underneath it and no setup fee. The scribe listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the patient leaves, and the record it produces lives in the bundled EHR.

Here's the full ladder so you can see where the EHR turns on:

| Plan | Price (annual, per doctor, ex-GST) | With 18% GST | EHR included? |
|---|---|---|---|
| Assist | ₹1,599/mo | ₹1,887/mo | No, scribe + scheduling only |
| Copilot | ₹2,399/mo | ₹2,831/mo | Yes, bundled AI Copilot EHR |
| Autopilot | ₹3,999/mo | ₹4,719/mo | Yes, plus receptionist and follow-ups |

The bundled AI EHR starts at the Copilot tier. If you only want documentation, Assist is cheaper and the EHR simply isn't part of it. Confirm current numbers on the [pricing page](/in/pricing/). For the deeper category walkthrough, our [EMR software guide](/in/blog/emr-software-india-guide/) covers what an Indian clinic EHR should and shouldn't include.

## When is a cheaper or free EHR the right call?

When your needs are genuinely basic and you have the technical support to run the thing. Free and open-source systems like Bahmni carry no licence fee at all, which is a real advantage. But per Bahmni's own FAQ, the software is free while implementation and support are not: you pay a partner to install, configure, host, train, and maintain it. And an open-source records system doesn't include AI documentation, so the typing burden stays with you.

So the free route makes sense for a clinic that wants a plain records system, has low volume, and can support the setup, either in-house or with a paid partner. It's the wrong route if you're buying to escape after-hours charting, because that's the one thing it doesn't solve. Our [honest look at free EMR software](/in/blog/free-emr-software-india-honest/) walks through where free stops paying off. For the full cost breakdown on the hospital side of the market, [HMS software cost in India](/in/blog/hms-software-cost-breakdown-india/) decodes the per-bed and per-module pricing that clinic buyers should not be paying for. And if you're a solo doctor trying to size the spend for one clinic, [AI scribe cost for a solo doctor in India](/in/blog/ai-scribe-cost-for-solo-doctor-india/) runs the per-visit math at your scale. If Bahmni specifically is on your shortlist, [Bahmni vs an AI-native EHR](/in/blog/bahmni-vs-ai-native-ehr-india/) compares the total cost of the free-licence route versus a bundled subscription.

If your reason for buying is the documentation load, an AI-native plan earns its price the first week. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. An EHR that also writes the note keeps that record complete without eating your evenings.

## How to price any EHR in a week

1. Ask every vendor for the all-in first-year total in writing: licence, setup, seats, AMC, modules, migration. Not the monthly sticker.
2. Count the seats your clinic actually needs, not just the doctors. Multiply.
3. Separate one-time fees from recurring ones so you can compare monthlies fairly.
4. List the modules you'll genuinely use and make sure each quote includes them or prices them.
5. Trial the shortlist on real clinic days, and confirm Patient Square's current price and GST on the [pricing page](/in/pricing/), then book a short demo to see the bundled EHR and scribe together.

The security and data-ownership receipts are on the [security page](/in/security/). The vendor that shows you the whole bill up front is telling you something good about the renewal conversation later. The one that hides it is telling you something too.

---

## Halemind Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/halemind-alternatives-india/
Published 2026-06-29 · Updated 2026-08-27 · Tags: alternatives, comparison, pricing

Halemind is a unified HMS/EHR with per-seat and per-location caps. If notes are your real drain, here's the honest fork and a bundled AI EHR from ₹2,399/mo per doctor.

Being a unified platform. Halemind bundles automated EHR, hospital management, appointment scheduling, OPD/IPD, billing, a patient portal, CRM with SMS marketing, and specialty templates for private practices, clinics, and hospitals. If you want one cloud system to run records, front desk, and outreach together, that unified scope is why you'd choose it.

If you're weighing Halemind and asking whether a unified platform is what your clinic really needs, here's the honest read: Halemind is broad, one system for EHR, front office, patient portal, and CRM outreach, and its headline price is low. But its documentation is form-filling, its tiers cap doctors and locations, and it doesn't do ambient scribing. If your real daily drain is writing notes, Practice Copilot addresses it directly. It starts at ₹1,599/mo per doctor, with Patient Square EHR at ₹2,399/mo or an alongside path for an existing EHR (ex-GST, add 18%). You can book a demo and watch a SOAP note land in about two minutes.

Not a takedown, a fit question. Below: what Halemind does well, how its pricing actually behaves as you grow, where a clinic's real cost sits, and when Halemind is the right pick.

> **Bottom line**
>
> - Halemind is a unified HMS/EHR (records, front office, patient portal, CRM), tiered by doctors, staff, SMS, and location.
> - Practice Copilot supports Patient Square EHR or an existing EHR, with an ambient AI scribe, per-doctor pricing, and no seat caps.
> - Low Halemind headline (~₹999/mo), but it caps at 2 doctors and 1 location; cost climbs with seats and add-ons.
> - If your pain is notes, Patient Square is the cleaner fit. If your pain is running a unified front office, Halemind wins.

## Halemind vs Patient Square at a glance

Match your problem to a row.

| | Halemind | Patient Square (Practice Copilot) |
|---|---|---|
| Core job | Unified HMS/EHR + front office + CRM | Documentation + records for doctors |
| Documentation | EHR forms, case sheets, templates | Ambient AI scribe, auto-drafted note |
| Pricing basis | Tiered by doctors + staff + location | Per doctor, no seat cap |
| India entry price | ~₹999/mo (2 doctors, 1 location) + GST | ₹1,599/mo + GST (Assist) |
| Bundled EHR | Included in platform | ₹2,399/mo + GST (Copilot tier) |
| Location limit on entry tier | 1 location | None; scale by doctor |
| Ambient scribe (Hindi + languages) | No | Yes, 20+ languages, English output |
| Add-on metering (SMS, extras) | Yes on lower tiers | No plan-level metering |

If you want a patient portal and CRM outreach in the same system, Halemind's breadth is the point. If you want your notes done, keep reading.

## What Halemind is genuinely good at

Credit where due. Halemind is a capable unified platform. It pairs an automated EHR with a hospital management system and a patient portal, and layers on appointment scheduling, OPD and IPD management, automated billing, smart analytics, visual case sheets, integrated CRM with SMS marketing, role-based multi-user access, and specialty-driven templates. It's aimed at private practices, clinics, and hospitals that want one cloud system rather than a stack of tools.

For a clinic that wants records, front desk, and patient outreach under one login, that's a genuinely useful shape, and the entry price looks friendly. A practice building its digital front office should have Halemind on the list. Nothing below says otherwise.

The catch is the same one every unified platform has: you're buying breadth, and documentation is one form-based module inside it, not the thing the product is built around. If notes are your actual pain, [see a documentation-first alternative in a demo](https://patientsquare.com/in/) before you commit to a platform.

## What does Halemind cost, and how does it behave as you grow?

Halemind publishes tiers, which is a point in its favour, but read the caps. Starter is around ₹999/mo and covers 2 doctors, 1 location, 500 SMS, and 1 staff login. Standard is ₹2,499/mo for 10 doctors, 1 location, 1,000 SMS, 2 staff logins. Premium is ₹4,999/mo for 25 doctors, 1 location, 2,500 SMS, 5 staff logins. Add GST. On the lower tiers, extra add-ons run ₹199/mo (Starter) or ₹149/mo (Standard).

The ₹999 headline is real but narrow: two doctors, one location, a small SMS bundle. A third doctor, a second clinic, or more staff logins pushes you up a tier or into add-ons. That's normal platform pricing, but it means your real cost depends on your shape, not the headline.

Patient Square prices per doctor with no seat cap. Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo. All ex-GST; add 18%. Unlimited visits and notes, no per-note metering, no setup fee, no SMS bundle baked into the plan. You add a doctor, you add a seat; the maths stays linear. The full ladder is on the [pricing page](https://patientsquare.com/in/pricing).

## Where the real recurring cost sits

A unified platform organises your clinic. It doesn't hand back the hour lost to documentation each day, and that's the cost most clinics never put a number on.

Indian consultations average about two minutes, per a 67-country BMJ Open study, among the shortest measured anywhere. In that window the record is what suffers, and a thin record is costly later. Roughly 65,000 medical-negligence matters reach Indian courts and consumer forums a year, and the defence that holds is a complete contemporaneous note. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. EHR forms and specialty templates only help if someone has time to fill them. In a full OPD, that time doesn't exist.

That's the wedge Patient Square is built for. Canonically: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens as you consult, in Hindi, Telugu, Bengali, and 20+ Indian languages, even mixed mid-sentence, and returns a clean English note. Book a demo and test it on a real clinic day.

## What you trade by choosing Practice Copilot

Say the trade plainly. Picking Patient Square over Halemind means giving up the unified front office. Patient Square bundles an AI EHR at the Copilot tier, but it doesn't run a patient portal, a CRM/SMS-marketing engine, IPD/bed management, or pharmacy as named modules. If patient-portal access or marketing outreach is central to your clinic, that's a real gap and Halemind covers it.

Keep the EHR scope honest. We claim a bundled AI Copilot EHR at the plan level; we don't enumerate internal modules the product pages don't name. On compliance, Patient Square is handled to DPDP Act 2023 standards with a SOC 2 Type II audit in progress (not certified), and ABDM integration on the roadmap, not live today. Records are born digital and ready for the ABHA-linked era on your timeline; we don't claim live ABDM you can switch on this week.

What you keep is the documentation win: ambient capture in the patient's language, a clean English note the moment they leave, ICD-10 suggestions, and a prescription draft to review and sign. eRx is draft-only, no pharmacy transmission. Notes belong to your clinic, export or delete any visit anytime.

## When Halemind is the better choice

Choose Halemind if you're building a unified front office, not just fixing notes. A practice that wants EHR, patient portal, CRM outreach, OPD/IPD, and billing in one cloud system, and is comfortable with form-based documentation, is exactly Halemind's buyer. Its tiered pricing is friendly at the entry point, and running one platform beats stitching several together for a lot of clinics. At that scope, a per-doctor scribe isn't the competitor; it solves a different problem.

Choose Practice Copilot if you're a doctor or growing group whose real pain is finishing notes and you want per-doctor pricing with no seat cap or setup fee. Use Patient Square EHR or keep an existing EHR. Some clinics retain Halemind for its patient portal, CRM, IPD, or pharmacy workflows, and that split is fine too.

## How to decide this week

Skip the feature-grid staring and run the test:

1. Track where your day actually goes. If it's patient outreach, portal, and front-office ops, you want a unified platform. If it's notes, you want a scribe.
2. If it's documentation, shortlist per-doctor tools with published pricing and no seat cap, so growth doesn't trigger a tier jump.
3. Match the clinical output: a structured note, ICD-10 suggestions, and a checked prescription draft, like for like.
4. Trial on real OPD visits in your own languages, Hindi or Telugu in, clean English note out, not a scripted demo.
5. Settle the data question with any vendor: hosting, ownership, and the true ABDM status, roadmap or live.

The security details, encryption, access, audit status, sit on our security page, and the per-doctor ladder with no asterisks is on the [pricing page](https://patientsquare.com/in/pricing). Book a short demo to check note quality against your own visit type. If you want a unified front office, Halemind earns the look. If you want your notes done, you're in the right place. For a full breakdown of what Indian EHR and clinic software really costs beyond the headline rate, [EHR software cost guide](/in/blog/ehr-software-cost-india-buyers-guide/) names every setup, per-user, and AMC fee that vendors leave out of the first quote.

---

## Elation EHR Pricing: What It Costs and the Scribe Question
https://patientsquare.com/us/blog/elation-ehr-pricing/
Published 2026-06-26 · Updated 2026-08-27 · Tags: pricing, ehr, elation-health, comparison

Elation now quotes pricing privately, third-party estimates near $275 to $399 per provider. The real cost, its native scribe, and a $119 bundle alternative.

Elation no longer publishes a price. Its pricing page is quote-only and routes you to a specialist. Third-party trackers estimate roughly $275 per provider per month on annual billing (about $349 monthly) for the direct-care plan, and near $333 to $399 for the insurance plan. Those are outside estimates, not Elation figures. The old $275 rate now survives only as a third-party annual-billing estimate.

Short version: Elation Health used to publish a price and now doesn't; its pricing page is quote-only. Third-party trackers estimate roughly **$275 per provider per month** on annual billing (about **$349 monthly**), and near **$333 to $399** for the insurance plan. The important thing to know before you switch: Elation ships its own native ambient scribe, Note Assist, **at no extra cost**, so it isn't a scribe-less EHR. If you're weighing a move, Patient Square's Copilot plan is **$119 per provider per month** annually with a bundled AI EHR and scribe. You can compare the note on a real visit before deciding.

This isn't an Elation takedown. It's a genuinely well-liked EHR for independent primary care, and its native scribe is a real strength. The point is the price you can't quite see anymore, and an honest read on whether switching even makes sense.

> **Key takeaways**
>
> - Elation no longer publishes pricing; the page is quote-only. Third-party estimates: ~$275/provider/month annual, ~$349 monthly, ~$333–$399 for insurance.
> - Elation's Note Assist is a native ambient scribe, included at no added cost, a real reason to stay if you're happy.
> - No clearly published free-trial length; Elation offers a demo and product tour.
> - Elation is built for independent primary care and direct primary care, less so for multi-specialty groups.
> - Patient Square Copilot is $119/provider/month with a bundled AI EHR and scribe, with a stated 7-day trial.

## What does Elation Health cost per provider?

Elation stopped publishing a plain price. Its pricing page now routes you to a form where a practice specialist responds with a personalized quote. So there's no first-party number to post, which is a change: Elation historically listed around $275 per provider per month.

The third-party trackers still carry estimates, and they roughly match that history.

| Plan (third-party estimate) | Estimated cost per provider / month |
|---|---|
| Direct care, annual billing | ~$275 |
| Direct care, monthly | ~$349 |
| Insurance plan, annual | ~$333 |
| Insurance plan, monthly | ~$399 |

Those come from Software Finder's 2026 estimates. Read them as directional. Elation confirms none of them, and a quote-only vendor's real number depends on plan, term, and practice size. The takeaway: the old $275 rate didn't vanish, it just moved behind a form and now shows up as a third-party annual-billing estimate.

If you'd rather read a fixed number instead of requesting a quote, ours is published at $119.

## The scribe question, and why it matters here

This is where Elation is different from a scribe-less EHR, and it's the honest heart of the comparison. Elation ships **Note Assist**, a native ambient AI scribe embedded in its own EHR, not a third-party add-on. Elation's own page says it's natively built and included at no additional cost to EHR users, and Fierce Healthcare reported the same when Elation rolled out its native AI suite.

That changes the math. Some EHRs make you buy the scribe separately, so the wedge is "we bundle it and they don't." With Elation, that wedge doesn't apply, because Elation already bundles its own scribe for free. So if you're on Elation and you like Note Assist, price alone isn't a reason to switch. We'd rather say that plainly than pretend otherwise.

Where the comparison stays live is note quality and fit. Both tools do ambient documentation. The right way to choose is to run each on your own visits and read the output, which you can do with a short demo.

## Elation vs Patient Square: the honest comparison

Let's compare like for like, without stacking the deck.

| | Elation Health (estimated) | Patient Square Copilot |
|---|---|---|
| EHR base (per provider / mo) | ~$275 annual (estimate) | $119 (annual billing) |
| Ambient scribe | Native (Note Assist), included | Native, bundled |
| Published price | No (quote-only) | Yes ($79 / $119 / $199) |
| Free trial | Demo / product tour, no stated length | 7-day trial |
| Target audience | Independent primary care, DPC | Independent practices, multi-specialty |
| Specialty templates | Primary-care focused | Specialty-aware, out of the box |

On the estimated price, Patient Square is lower. But Elation isn't charging extra for its scribe, so the real question isn't just the number, it's whether Elation's primary-care fit or Patient Square's bundle and price serve your practice better. That depends on your specialty mix and how the notes read on your visits.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The bundled AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** on annual billing. Put it in front of your visit type and judge the note against Note Assist directly.

## What you give up leaving Elation

Be clear-eyed about the trade. Elation earned its reputation in primary care.

- **A primary-care-tuned EHR with a native scribe.** Elation's workflows and Note Assist are built for family medicine, internal medicine, and direct primary care. If that's your world and it fits, it fits well.
- **A DPC-friendly design.** Elation is a common pick for direct-primary-care practices. If you run a membership model, weigh how well an alternative maps to it.
- **An established install base.** Migrating any EHR is real work. That's true leaving Elation and true leaving anyone.

Patient Square's export claim is precise: **EHR-ready export (PDF, HL7, FHIR)**. That's a clean export, not a certified interoperability engine. For a broader look at bundled options, our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup and the [Charm EHR pricing](/us/blog/charm-ehr-pricing/) breakdown cover the other end of the market.

## When Elation is the better choice

Stay with Elation, or pick it, if you're an independent primary-care or direct-primary-care practice that likes its workflow and its native Note Assist scribe. It's a focused, well-regarded EHR for exactly that audience, and its scribe is included, so there's no add-on to escape. If primary-care fit is your priority and you're happy with the notes, switching to save on an estimated price isn't obviously worth the migration.

Choose Patient Square if you want a published, lower price, specialty-aware templates beyond primary care, or a bundle you can test on real visits after a short assisted setup. If Elation's quote comes back higher than you expected, or you want to compare note quality head to head, that's the moment to run both. The full price ladder is on the [pricing page](/us/pricing/).

## How to decide in a week

Skip the spec-sheet comparison and run the real test:

1. Get Elation's actual quote in writing, since the site won't show it. Note whether it's the direct-care or insurance plan.
2. Turn on Note Assist and Patient Square's scribe on the same real visits. Read both notes side by side.
3. Check specialty fit: if you're pure primary care, weight Elation's tuning; if you're mixed, weight broader templates.
4. Settle the audio question with each vendor: stored or not, and for how long. Ours is never stored.
5. Trial the alternative on a real clinic week before you move anything. A demo flatters everyone.

The receipts behind our claims, encryption, access, and audit status, are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to compare the note against Note Assist on your own visits, then run the 7-day trial on a real week. If you're already happy on Elation, that's a fine answer too, and we'll tell you so.

---

## HMS Software Cost in India: A Line-by-Line Breakdown (2026)
https://patientsquare.com/in/blog/hms-software-cost-breakdown-india/
Published 2026-06-26 · Updated 2026-08-29 · Tags: india, pricing, hms, cost

Calculate hospital management software cost across beds, modules, users, hosting, implementation, migration, interfaces, devices, GST, support, labour, and exit.

There is no defensible universal price. Enterprise quotes vary by facility, beds, locations, modules, users, hosting, interfaces, migration, devices, implementation, support, and contract. Ask for a line-item year-one total and a steady-state annual total.

Hospital management software in India has no honest single price. A quote changes with beds, locations, modules, users, hosting, interfaces, migration, devices, implementation, support, and contract. Public government software and open-source code also carry eligibility or operating costs that a licence column does not show.

The useful answer is a workbook. Collect buyer-entered figures from the quotes, preserve every unit, and calculate year one separately from a normal operating year. Hospital Copilot is demo-priced, so its quote belongs in the same sheet.

> **Decision summary**
>
> - Do not use a national average or an invented facility-size band.
> - Keep one-time and recurring costs separate.
> - Treat unknown setup, hosting, support, and maintenance rows as unknown, not zero.
> - Hospital Copilot has no practice-tier price; it is scoped and priced through a demo.
> - Record the hospital quote's stated tax rate and amount separately.

## Normalize scope before price

Send every shortlisted supplier the same scope sheet. A lower number is not useful if it omits wards, interfaces, migration, or support that another quote includes.

| Scope field | Buyer entry |
|---|---|
| Facilities and locations |  |
| Licensed beds and operational beds |  |
| OPD encounters per day |  |
| Admissions and discharges per day |  |
| Clinical departments and specialties |  |
| Named, concurrent, or role-based users |  |
| Registration and patient identity |  |
| ADT, wards, beds, nursing, eMAR |  |
| CPOE, pharmacy, inventory |  |
| LIS, analyzers, RIS, PACS |  |
| Billing, packages, deposits, refunds |  |
| Payers, TPA, government schemes |  |
| Finance, procurement, stores, HR |  |
| Existing systems to retain |  |
| Data sources and history to migrate |  |
| Availability and disaster-recovery target |  |
| Implementation locations and sequence |  |

Write exclusions beside the table. "Pharmacy" may mean a formulary in one quote and stock, batches, expiry, dispensing, returns, purchase, and accounting handoff in another.

## The complete cost workbook

| Cost row | Quantity and unit | One-time | Annual recurring | GST status | Evidence and date |
|---|---|---:|---:|---|---|
| Core subscription or licence |  |  |  |  |  |
| Bed, user, facility, or module increment |  |  |  |  |  |
| Discovery and workflow design |  |  |  |  |  |
| Configuration and approved customisation |  |  |  |  |  |
| Master data preparation |  |  |  |  |  |
| Patient and encounter migration |  |  |  |  |  |
| Billing, inventory, finance, and document migration |  |  |  |  |  |
| Lab analyzers and LIS interface |  |  |  |  |  |
| RIS, PACS, and modality interface |  |  |  |  |  |
| Pharmacy, payment, payer, TPA, or accounting interface |  |  |  |  |  |
| Interface engine, API, VPN, certificate, or message fees |  |  |  |  |  |
| Hosting, database, storage, backup, and recovery |  |  |  |  |  |
| Servers, network, power, kiosks, printers, scanners |  |  |  |  |  |
| Security testing, logging, and monitoring |  |  |  |  |  |
| Training, super-users, and floor support |  |  |  |  |  |
| Project management and go-live |  |  |  |  |  |
| Support SLA and after-hours escalation |  |  |  |  |  |
| Updates, major releases, and regression testing |  |  |  |  |  |
| SMS, WhatsApp, email, payment, and other usage |  |  |  |  |  |
| Internal clinical and operational labour |  |  |  |  |  |
| Internal IT, finance, quality, and legal labour |  |  |  |  |  |
| Downtime and dual-running allowance |  |  |  |  |  |
| Data export, archive, termination, and transition |  |  |  |  |  |
| GST and other applicable tax |  |  |  |  |  |

Require a named owner and source for each row. A blank remains a commercial question. It must not silently become ₹0 in the total.

## Calculate two totals

**Year-one total = quoted one-time cost + first-year recurring cost + hardware and network + internal implementation labour + GST and other applicable taxes.**

**Steady-state annual total = quoted recurring cost + hosting and interfaces + support and upgrades + internal operating labour + GST and other applicable taxes.**

Add a cash-flow column if annual amounts are paid upfront. A monthly equivalent is not a monthly cancellation right.

For a three-to-five-year view, use the renewal, inflation, currency, volume, and module rules in the contract. Do not invent an annual maintenance percentage when the supplier has not quoted one.

### Compare three views of the same quote

One total is not enough for procurement, finance, and operations to see the same decision.

| View | Include | Decision it supports |
|---|---|---|
| Contracted cash | Invoices, payment dates, deposits, taxes, renewal | Budget and cash-flow approval |
| Full economic cost | Contracted cash plus devices, network, internal labour, dual running, downtime allowance | TCO comparison |
| Exit-adjusted cost | Full economic cost plus archive, export, termination, and transition | Lock-in and replacement risk |

For each view, calculate year one, a normal later year, and the chosen contract horizon. If a supplier will not state a renewal or exit figure, keep the value unknown and make that uncertainty visible beside the total.

### Record quote provenance

Every number should carry the vendor, proposal version, date, currency, tax status, billing unit, quantity, term, and owner who confirmed it. Keep the original proposal as evidence. When a sales email changes a figure, update the workbook as a new version rather than overwriting the old one.

This catches a common comparison error: one team uses a tax-inclusive three-year total while another enters an ex-tax first-year invoice. Both numbers may be accurate and still be useless beside each other.

## Licence models hide different risks

| Model | Headline | Rows buyers often miss |
|---|---|---|
| Hosted subscription | Recurring facility, bed, user, or module charge | Implementation, migration, interfaces, storage, usage, support tier, renewal, exit |
| Perpetual licence | Software licence and quoted support or maintenance | Infrastructure, upgrades, database, security, support gaps, major releases |
| Government programme | Programme access | Eligibility, rollout, local devices, connectivity, implementation, support, change control |
| Open source | No proprietary licence for the core source | Implementation partner, configuration, hosting, interfaces, security, support, upgrades, recovery |

NIC describes e-Hospital as an as-is government-hospital SaaS product. Bahmni is open source. Neither page supplies a universal private-hospital price, so neither should be converted into one.

## Migration is a cost centre

Inventory every source before asking for a migration quote:

- patient identities, duplicates, merges, and aliases;
- visits, admissions, diagnoses, procedures, and discharge records;
- allergies, medication history, prescriptions, and administrations;
- orders, results, images, reports, and attachments;
- charges, receipts, deposits, refunds, packages, claims, and balances;
- items, batches, expiry, suppliers, purchase, issue, and stock; and
- users, roles, signatures, amendments, and audit history.

Require profiling, mapping, trial migration, clinical and financial validation, correction, final migration, reconciliation, sign-off, and legacy archive access. "Data migration included" is not a complete scope.

## Interfaces need lifecycle pricing

An interface price should cover more than initial development. Ask for:

1. specification and mapping;
2. build or configuration;
3. test environment and test messages;
4. production setup;
5. acknowledgment, retry, and error queue;
6. monitoring and support;
7. correction and reconciliation; and
8. change testing when either connected system is upgraded.

A standards label alone does not show whether the interface works. Test patient identity, order, result, correction, duplicate, downtime, recovery, and audit.

## Internal labour belongs in TCO

Record hours and a defensible internal rate for:

- clinical design and order-set review;
- nursing, pharmacy, lab, radiology, billing, finance, and quality workshops;
- data cleaning and validation;
- super-user training and floor support;
- policy, privacy, security, and contract review;
- testing and defect retesting;
- dual entry during transition; and
- post-go-live correction.

This is not a reason to reject digitisation. It is how the hospital plans enough time to make it work.

## Quote questions that change the total

- Which rows are fixed, estimated, capped, or usage based?
- Which prices change with beds, users, facilities, modules, storage, or transactions?
- What tax rate and treatment does each quote state?
- What is excluded from implementation and support?
- What response and restoration times are contractual?
- Are upgrades included? Who pays for interface regression testing?
- What is the renewal rule?
- What happens after termination?
- What complete data export is supplied, in which format, within what time, and at what cost?
- Who assists transition to the next system?

## Put Hospital Copilot in the correct row

Hospital Copilot is separately demo-priced. It does not inherit Practice Copilot's published per-clinician rates. A hospital can deploy the complete Patient Square HIS/EHR or retain its existing HIS/EHR and define Hospital Copilot workflows during discovery.

Required ADT, CPOE, eMAR, LIS, RIS, PACS, pharmacy, billing, interface, migration, and specialist workflows are scope and acceptance-test requirements, not automatic inclusions. If EHR-ready export is discussed, the exact product claim is `EHR-ready export (PDF · HL7 · FHIR)`. That phrase does not promise certified interoperability or third-party write-back. ABDM integration remains roadmap-only.

Use the workbook before the sales call, then make each supplier fill the same rows. Book a demo to obtain the Hospital Copilot scope and quote, with its stated tax treatment recorded separately.

---

## Insta by Practo Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/insta-by-practo-alternatives-india/
Published 2026-06-26 · Updated 2026-08-27 · Tags: alternatives, comparison, insta-health, pricing

Insta by Practo is enterprise HMS with per-user seat minimums. Clinics can start at ₹1,599/mo per doctor with no rollout. Segment split, priced honestly.

Running a facility end to end. Insta by Practo (Insta Health Solutions, acquired by Practo) is a cloud HMS that spans front office, out-patient and in-patient management, billing and insurance, pharmacy and inventory, and lab and radiology. It's pitched at clinics, polyclinics, nursing homes, and hospitals across 22 countries. If your pain is operations, not just notes, that breadth is the point.

If you're weighing Insta by Practo, sort out one thing first: are you running a facility, or just trying to get your notes done? Insta is a full cloud HMS, front office, out-patient and in-patient, billing, pharmacy, lab, all in one system, and it's priced in seats with minimums (roughly 5 users to start on outpatient, 20 on inpatient). A three-doctor clinic that mainly wants documentation handled ends up buying a multi-seat operations platform to solve a notes problem. Patient Square splits it clean: clinics run Practice Copilot from ₹1,599/mo per doctor (ex-GST, add 18%, so about ₹1,887 all-in), no seat floor, no rollout; hospitals and nursing homes get Hospital Copilot, demo-priced. You can book a demo and watch a SOAP note land in about two minutes.

This isn't a takedown. It's a fit question. Below: what Insta genuinely does well, how its pricing actually works, where a small clinic's real cost hides, and when Insta is the right call over a scribe.

> **Bottom line**
>
> - Insta by Practo is a full HMS: front office, OP/IP, billing, pharmacy, lab, insurance, sold in seats with 5 and 20-user minimums.
> - Patient Square splits by segment: Practice Copilot for clinics (₹1,599/mo per doctor, no minimum), Hospital Copilot for facilities (demo-priced).
> - A small clinic buying an HMS pays for pharmacy and IP modules it won't run. A facility buying a clinic scribe is under-scoped.
> - Need operations run from one system? Insta fits. Need the record finished during the visit? Patient Square does.

## Insta by Practo vs Patient Square: match your building first

Read the row that fits your setup, not the whole deck.

| | Insta by Practo | Patient Square |
|---|---|---|
| Built for | Clinics, nursing homes, hospitals running full operations | Clinics (Practice Copilot) + facilities (Hospital Copilot) |
| Scope | Full HMS: front office, OP/IP, billing, pharmacy, lab, insurance | Practice Copilot: Patient Square EHR or existing EHR; Hospital Copilot: complete Patient Square HIS/EHR or incumbent-system path |
| Ambient AI scribe | Not the core | Yes, note ready about 2 min after the visit |
| ICD-10 | Coding module | Suggestions only, doctor confirms |
| Prescription | e-prescribing module | Draft only, doctor signs |
| Languages | Interface-level | Input in Hindi + 20+ Indian languages, clean English note out |
| Pricing | Per user/month, 5-user (OP) / 20-user (IP) minimums | Clinics: published per doctor, no minimum. Facilities: demo-priced |
| Implementation | Platform rollout | Clinics: none. Facilities: scoped |

If you run beds and a pharmacy, keep reading the Insta case. If you're a clinic drowning in charting, skip to the documentation section.

## What Insta by Practo is genuinely good at

Credit where it's due. Insta Health Solutions has been at this since 2008 and was acquired by Practo, and the product covers a real hospital's day. Its own site lists twelve connected departments: front office and patient relations, billing and insurance, diagnostics and lab and radiology, out-patient and in-patient management, pharmacy and inventory, plus IT, management, and medical records. Third-party listings describe the same breadth, revenue cycle, EMR, claims, inventory, appointment scheduling. It runs in the cloud on AWS, and it's used across 1,250-plus centers in 22 countries by Insta's own count.

That's an operations platform, not a note-taker. A polyclinic or nursing home that needs one system to handle admissions, the pharmacy counter, lab orders, and insurance billing should have Insta on the list. Nothing below argues against that.

The mismatch shows up when a small clinic lands on Insta through a generic "hospital software India" search and starts scoping a pharmacy ledger and an IP module it will never touch. If that's you, [see the clinic-scoped option in a quick demo](https://patientsquare.com/in/) before you commit to a 5-seat platform.

## Insta's pricing is published, but read the minimums

Insta does publish seat prices, which is more transparent than most HMS vendors. But read the fine print. Third-party listings put the outpatient plan around $25 per user/month with a 5-user minimum, and the inpatient plan around $40 per user/month with a 20-user minimum. Separate sources cite per-installation figures near $5,000, with the real number scoped by hospital size and module mix. Confirm your exact quote with Insta, don't take a comparison-site figure as gospel.

Here's what that means for a small clinic. Even the lightest plan asks you to buy five seats. A solo doctor or a two-doctor practice is paying for a multi-user operations platform to solve what's usually one problem: the record isn't getting finished during the visit. That's a lot of platform for a documentation job.

Patient Square prices to the segment instead. Clinics get published per-doctor pricing with no seat floor: Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo, all ex-GST, add 18%, on the [pricing page](https://patientsquare.com/in/pricing). Buy for one doctor if you're one doctor. Facilities that genuinely need operations run Hospital Copilot on a demo-priced conversation, because that scope, like Insta's, really does need scoping. We break the full seat-versus-per-doctor math down in the [HMS cost breakdown for India](https://patientsquare.com/in/blog/hms-software-cost-breakdown-india).

## The clinic decision, in one table

Put the two side by side for a small clinic that mainly wants notes handled:

| For a 3-doctor clinic | Insta by Practo (outpatient) | Patient Square (Practice Copilot) |
|---|---|---|
| Seats you must buy | 5-user minimum | 3, one per doctor |
| What you're paying for | Full HMS incl. modules you may not run | Documentation + bundled AI EHR |
| Note written when | You still chart it | Ready about 2 min after the visit |
| Go-live | Platform rollout | Same week, no project |
| Entry price | About $25/user/mo, 5 seats | ₹1,599/mo per doctor + GST |

The point isn't that Insta is expensive. It's that a clinic buying an HMS is buying facility infrastructure to fix a charting habit. If operations aren't your pain, you're overbuying.

## Where a small clinic's real cost hides

An HMS runs your operation. It does nothing for the one cost almost every clinic carries and never puts on an invoice: the hour a day you lose to writing notes.

Indian OPD consultations run about two minutes on average, per a 67-country BMJ Open study, among the shortest anywhere. In that window the record is what gets shortchanged, and a thin note is expensive later. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours, and a complete contemporaneous note is the defence that holds if a case ever reaches a consumer forum. No amount of pharmacy-inventory tooling fixes a doctor charting at 9pm. A scribe that finishes the note during the visit does.

That's the whole design of Patient Square. Canonically: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens while you consult, in Hindi, Bengali, Tamil, Hinglish, and 20-plus Indian languages, and returns a clean clinical note in English, always. ICD-10 codes come as suggestions you confirm; the prescription is a draft you sign. Audio is never stored, and capture keeps working offline with encrypted local buffering. Book a demo and run it on a real OPD hour. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## What every plan includes

Worth being precise here, because "included" varies wildly across HMS vendors. Every Patient Square plan carries: unlimited visits and notes with no per-note metering; EHR-ready export (PDF, HL7, FHIR); specialty-aware templates ready out of the box; and capture on web or mobile. That export is a data-portability feature, not a certified interoperability integration, so don't read HL7 or FHIR as a conformance claim.

On compliance, the honest version: handled to DPDP Act 2023 standards, SOC 2 Type II audit in progress (not yet certified), and ABDM integration on the roadmap, not live. Records are born digital, ready for the ABHA-linked era on your timeline. If any vendor tells you they're live and certified on ABDM today, ask for the NHA certificate before you believe it.

## When Insta by Practo is the better fit

Pick Insta if you run a facility, not just a clinic. A nursing home or hospital with in-patient stays, a pharmacy counter, lab and radiology orders, and insurance billing needs one system to run operations end to end, and that's exactly what Insta is built for. Its seat minimums stop being a tax and start making sense once you actually have twenty-plus people touching the system. A documentation tool doesn't compete with that; it's a layer you'd add on top, not a replacement for the operational spine.

Pick Patient Square if its verified scope fits. A clinic can use Patient Square EHR or an existing EHR through Practice Copilot. A hospital can use the complete Patient Square HIS/EHR or keep Insta through Hospital Copilot's alongside path. If Insta-only modules are load-bearing, keep them explicit. Either way, the ambient workflow finishes the draft while the patient is still in the room.

## How to decide this week

Skip the feature-matrix comparison and run this instead:

1. Name what hurts. Running beds, pharmacy, and claims? You need an HMS. Just the notes? You need a scribe.
2. Count your seats. If you're under five doctors and only want documentation, an HMS seat minimum is working against you.
3. If you're a clinic, shortlist per-doctor tools with published pricing and no implementation project.
4. If you're a facility, decide whether the pain is operations (scope Insta) or documentation at scale (talk to us about Hospital Copilot).
5. Trial on real visits, in your own languages, and settle the data questions: hosting, ownership, and the true ABDM status.

For a fuller sense of what an AI scribe costs a solo practice, see [the scribe cost breakdown for a solo doctor](https://patientsquare.com/in/blog/ai-scribe-cost-for-solo-doctor-india). The clinic per-doctor ladder is on the [pricing page](https://patientsquare.com/in/pricing), and a [short demo](https://patientsquare.com/in/) will tell you in ten minutes whether the note quality holds up on your visit type. If you need an HMS, Insta earns the look. If you just need your notes done, you're already in the right place.

---

## Prior Authorization: Cut the Documentation Work
https://patientsquare.com/us/blog/prior-authorization-documentation/
Published 2026-06-26 · Tags: prior-authorization, clinical-documentation, workflow

Why thin notes drive prior-authorization delays, what documentation a PA actually needs, and how an ambient scribe cuts the legwork while you still submit it.

A typical payer wants the diagnosis with a specific ICD-10 code, a clinical rationale for why the service is medically necessary, the conservative treatments already tried with their dates and outcomes, and the relevant exam or test findings. CMS frames it plainly: prior authorization needs the same information already required to support payment.

Prior authorization runs on documentation. A payer wants the diagnosis, the medical-necessity rationale, and the conservative care already tried, all pulled into a form. A thorough visit note carries most of that clinical story, so an ambient scribe that drafts a complete note cuts the legwork. It can't file the PA, though, and this page is honest about that line.

So let's draw it clearly. An AI scribe is not a prior-authorization tool. It doesn't fill payer forms, it doesn't touch a payer portal, and it doesn't submit anything. What it does is hand you a more complete note, which is where a PA gets its evidence. Real lever, narrow one. The 2025 AMA survey puts the burden at about 13 hours of physician and staff time a week, so the part a scribe can cut is worth understanding precisely.

> **Key takeaways**
>
> - The 2025 AMA survey found practices complete 40 prior authorizations per physician per week and spend ~13 hours on them; 95% of physicians say PA delays care.
> - A PA needs the diagnosis, the medical-necessity rationale, conservative care tried with dates, and supporting findings. CMS says it's the same information already required for payment, just earlier.
> - A complete visit note covers most of that clinical content. It does not cover the form, the codes, or the submission.
> - An AI scribe drafts the note and suggests ICD-10 codes. A person still assembles and files the PA.

## Why does prior authorization create so much documentation work?

Because a PA is a payer asking you to prove the case before the service, in writing. And the proof lives in the chart.

The numbers are not small. The 2025 AMA Prior Authorization Physician Survey, which polled 1,000 practicing physicians (400 primary care, 600 specialists) in December 2025, found that practices complete an average of 40 prior authorizations per physician every week and burn about 13 hours of physician and staff time getting them through. That's most of a full working day, every week, spent largely on paperwork rather than patients. The same survey found 95% of physicians say PA delays access to necessary care, 79% report patients abandoning treatment over authorization struggles, and 26% report a PA that led to a serious adverse event for a patient. This is not a minor admin tax. It's a patient-safety problem with a documentation core.

Here's the part worth sitting with. A chunk of that 13 hours isn't the submitting. It's the reconstructing. Someone has to find the diagnosis, dig out which conservative treatment the patient already failed and when, and write up why this drug or this imaging study is necessary now. When the note from the original visit is thin, that's a research project. When the note is complete, it's a copy job. The documentation burden of a PA is, to a real degree, the cost of a note that didn't capture enough the first time.

## What documentation does a prior authorization actually need?

Less mysterious than it feels. CMS puts it about as plainly as it gets: prior authorization "does not create new clinical documentation requirements," it "requires the same information that is already required to support Medicare payment, just earlier in the process." The patient's medical record, CMS says, has to "contain documentation that fully supports the medical necessity for services." Read that twice if you've ever felt like a PA was asking for something exotic. Mostly it's asking for a good note.

What a typical payer PA wants, and where a well-drafted visit note covers it:

| What a typical PA asks for | Where a complete visit note covers it | Does the note cover it on its own? |
|---|---|---|
| The diagnosis, coded specifically | Assessment, with an ICD-10 suggestion to confirm | Mostly. You confirm the code. |
| Medical-necessity rationale | Subjective and assessment: why this, why now | Yes, if the note captured your reasoning |
| Conservative treatments already tried | History and plan: prior meds, therapy, outcomes, dates | Yes, when those details were said and captured |
| Relevant exam and test findings | Objective: vitals, exam, results referenced | Yes, for what was discussed in the visit |
| Symptom duration, severity, functional impact | Subjective: onset, frequency, how it limits the patient | Yes, when it surfaced in the conversation |
| The specific payer form and fields | Not in the note | No. A person fills the form. |
| CPT / procedure or drug codes for the request | Not produced by the scribe | No. That's coding, downstream of the note. |
| Submission through the payer's portal or fax | Not in the note | No. The note is evidence, not a transmission. |

The top five rows are the clinical substance of a PA, and they're exactly what a thorough note already contains. The bottom three are the parts a note will never be: the form, the procedure codes, the act of submitting. That split is the whole honest story of this page. Worth flagging too: exact requirements vary by payer, plan, and service. Treat the table as the pattern, not a checklist any single insurer guarantees.

If you want to judge how much of that top half a note actually captures on your visits, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a structured note land about two minutes after a sample encounter, then read the assessment and history sections against this table yourself.

## How does an ambient scribe cut the prior-authorization legwork?

By making sure the clinical story is captured at the visit, complete and specific, so nobody has to rebuild it later from a four-line note.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For prior authorization, the value is concentrated in that note. A note written while the patient is describing which medication they tried last year and why it didn't work tends to capture the conservative-care history a PA hinges on. A note built from memory at 9pm tends to lose it. The ICD-10 suggestions narrow the diagnosis code your team confirms, and the medical-necessity reasoning lands in the assessment because it was said out loud in the room.

What that buys you is upstream, and it's specific: when your biller or care coordinator opens the chart to build the PA, the clinical evidence is already there, legible and dated. They're transcribing a complete record into a form, not chasing you down the hall to ask what the patient failed before. That's the legwork an ambient scribe cuts. If you want to see how complete the notes come out on your own visits, our [pillar on cutting charting time](../reduce-charting-time-clinicians/) walks through the time math, and the [pricing page](../../pricing/) lists exactly what ships today, with no PA-submission asterisks.

## Can't the AI just do the prior authorization for me?

No. And we're going to be blunt here because this is where the category gets sold dishonestly.

AI Medical Scribe by Patient Square does not submit prior authorizations. It does not fill out payer forms. It does not integrate with payer portals or clearinghouses. It does not generate CPT procedure codes or E&M visit levels, and it does not e-prescribe. It drafts a clinical note and suggests ICD-10 diagnosis codes for your team to confirm. Full stop. A person still reads the note, decides the service, fills the payer's form, attaches the record, and submits the request. The human owns the PA from form to fax.

If a vendor's pitch implies the AI "handles prior auth" end to end, ask them three things: does it connect to my payers, does it submit the request, and who's liable when an auto-submitted PA is wrong. Those questions usually end the overclaim. We hold the line on the boundary the same way we do with coding, which we lay out in [the honest version of ICD-10 suggestions](../ai-scribe-icd-10-suggestions-explained/): a scribe suggests, a person decides. The honest tool helps you build the documentation faster. It does not pretend to be the payer-facing workflow, because it isn't one, and a draft an LLM wrote has no business being auto-filed to an insurer.

## Where does a better note stop helping your PAs?

At the edge of the documentation. Past that, a note does nothing, and pretending otherwise is how this topic goes wrong.

A complete note helps the denials and delays that turn on clinical evidence: insufficient medical-necessity documentation, missing history of conservative care, a diagnosis that wasn't specific enough. Those are real, and they're common. But a thorough note can't move a denial caused by a formulary exclusion, a coverage limit, a plan that simply doesn't authorize that service, or a request that went in on the wrong form. In the 2025 AMA survey, 32% of physicians said PA requests are often or always denied, and plenty of that is policy, not paperwork. No scribe touches policy.

So the honest framing stays narrow. Documentation is a large, fixable part of the prior-authorization burden. An ambient scribe attacks that part by capturing a complete note at the visit. It does not attack the form-filling, the codes, the submission, or the payer rules, and we won't dress it up as if it does. Buy it as a way to make your notes more complete and your PA paperwork less of a research project. Don't buy it as a prior-authorization engine, because that's not what it is. If documentation completeness is the bottleneck you actually feel, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a structured note appear about two minutes after a sample visit, then run the 7-day free trial and check whether your real notes come out complete enough to build a PA from. For the post-submission side of revenue, where the same documentation logic applies to bounced claims, see [whether better notes cut claim denials](../ai-scribe-claim-denials-documentation/).

---

## KareXpert Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/karexpert-alternatives-india/
Published 2026-06-25 · Updated 2026-08-27 · Tags: alternatives, comparison, karexpert, pricing

KareXpert is a quote-only enterprise cloud HIMS for hospitals. For a clinic that wants AI notes now, Patient Square starts at ₹1,599/mo per doctor.

Running a whole hospital on one cloud platform. KareXpert is a Jio Platforms-funded enterprise HIMS with modules spanning HIMS, EMR, LIMS, RIS/PACS, pharmacy, telemedicine, connected ambulance, and BI. If you're a hospital or a multi-specialty group standing up a full cloud information system, that breadth is the reason to shortlist it.

Here's the quick read. KareXpert is an enterprise cloud HIMS, a Jio Platforms-funded platform that runs a whole hospital on one system, and its price is quote-only. If you run a hospital, that breadth is worth scoping. If you run a clinic and what you actually want is your notes done tonight, it's the wrong size of tool, and you'll spend a demo cycle scoping modules you'll never open. Patient Square's Practice Copilot goes the other way: published per-doctor pricing from ₹1,599/mo (ex-GST, add 18%, so about ₹1,887 all-in), bundled AI EHR at ₹2,399/mo, no rollout project. Hospitals with real HIMS needs look at Hospital Copilot, which is demo-priced. You can book a demo and watch a SOAP note land in about two minutes.

This isn't a takedown. It's a fit question. Below: what KareXpert is genuinely built for, why its price is scoped instead of listed, where a clinic's real recurring cost hides, and when KareXpert is the right call.

> **Bottom line**
>
> - KareXpert is enterprise cloud HIMS for hospitals: HIMS, EMR, LIMS, RIS/PACS, pharmacy, telemedicine, BI. Quote-only.
> - Patient Square splits by segment: Practice Copilot for clinics (₹1,599/mo entry), Hospital Copilot for hospitals (demo-priced).
> - A clinic buying a full HIMS platform is buying hospital plumbing it won't run.
> - If you need the whole module suite, KareXpert fits. If documentation is the pain, Patient Square finishes the note during the visit.

## KareXpert vs Patient Square: pick your building first

The right answer depends on your setting. A multi-department hospital and a 3-doctor clinic pull in opposite directions, so read the row that fits you.

| | KareXpert | Patient Square |
|---|---|---|
| Built for | Hospitals, multi-specialty groups | Clinics (Practice Copilot) + hospitals (Hospital Copilot) |
| Scope | Full cloud HIMS: HIMS, EMR, LIMS, RIS/PACS, pharmacy, telemedicine, BI | Practice Copilot: Patient Square EHR or existing EHR; Hospital Copilot: complete Patient Square HIS/EHR or incumbent-system path |
| Ambient AI scribe | Not the core pitch | Yes, note back in about 2 minutes |
| ICD-10 | Platform coding modules | Suggestions on the note, you confirm |
| Prescription | Pharmacy module | Draft you review, not auto-sent |
| Languages | Platform-dependent | Speak Hindi, English, Hinglish, 20+ Indian languages. Note in English |
| Pricing | Quote-only, demo-gated | Clinics: published per doctor. Hospitals: demo-priced |
| Implementation | Enterprise cloud rollout | Clinics: none. Hospitals: scoped |

Hospital scoping a full platform, keep reading the KareXpert case. Clinic drowning in charting, skip down to the cost section.

## What KareXpert is genuinely built for

Credit where it's due. KareXpert is a Jio Platforms-funded venture, and it's built a broad cloud healthcare platform, not a single tool. The suite spans Advanced HIMS, EMR and EHR, a laboratory information system, RIS and PACS for radiology, pharmacy, telemedicine, medical IoT, connected ambulance, and business intelligence, all delivered as SaaS on a fixed monthly fee so a hospital doesn't carry a big upfront licence. The company says the platform is running in top hospitals across India and expanding internationally, including a national-cloud deployment lined up with Telecom Egypt.

That's a real enterprise platform for real hospital operations. A hospital or a multi-specialty group standing up or replacing its information system should have KareXpert on the list, alongside the other cloud HIMS players. Nothing here argues against that.

The mismatch shows up when a single clinic lands on KareXpert through a broad "hospital software India" search and starts scoping a radiology PACS and a blood-tracking pharmacy module it will never run. No solo clinic operates a RIS. If that's the trap you're in, [see the clinic-scoped option in a demo](https://patientsquare.com/in/) instead of scoping a hospital-grade platform.

## Why isn't KareXpert's price on the page?

Because enterprise HIMS genuinely can't sit on a rate card. KareXpert runs a SaaS fixed-monthly model, but the actual number is gated behind a demo and enquiry, since cost tracks hospital size, which modules you switch on, how many sites, and the rollout scope. You can't quote a 300-bed multi-site platform the way you quote a per-seat app. For a hospital, that scoping is expected and fine.

For a clinic, it's a mismatch. You'd be entering an enterprise sales motion to solve a documentation problem that a per-doctor tool handles the same afternoon you sign up. Different problem, different buying experience.

Patient Square matches the price model to the building. Clinics get published per-doctor pricing: Assist ₹1,599/mo annual, Copilot ₹2,399/mo (that tier adds the bundled AI Copilot EHR plus WhatsApp), Autopilot ₹3,999/mo, all ex-GST, add 18%, right there on the [pricing page](https://patientsquare.com/in/pricing) with a 7-day free trial. Hospitals get Hospital Copilot on a demo-priced conversation, because hospital scope, like KareXpert's, honestly needs scoping. Right price model for the right building. If you want the per-doctor math laid out plainly, our [AI scribe cost breakdown for solo doctors](https://patientsquare.com/in/blog/ai-scribe-cost-for-solo-doctor-india) walks through it.

## Where a clinic's real recurring cost hides

A full HIMS is built to run a hospital. It does nothing for the one cost every clinic pays and almost never prices: the hours lost to writing notes after the last patient leaves.

Indian outpatient visits run short, often just a couple of minutes at the consult, and in that window the record is the first thing that gets thin. A thin note is cheap today and expensive later, when a query, a consumer forum, or an NMC records request lands and the file has to hold up. A hospital platform, however broad, still leaves the solo doctor charting at 9pm. A scribe that finishes the note while the patient is still in the room removes that entirely.

That's the whole point of Patient Square. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens as you consult, in Hindi, Bengali, Tamil, English, even code-mixed Hinglish, and returns a clean English note. Every plan includes unlimited visits and notes with no per-note metering, EHR-ready export (PDF, HL7, FHIR), specialty-aware templates ready out of the box, and capture on web or mobile. Audio is never stored, and capture is encrypted offline. Book a demo and run it on a real OPD, not a slide. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If you want to see how this reads against other India platforms, our takes on [Halemind](https://patientsquare.com/in/blog/halemind-alternatives-india) and [DocOnline](https://patientsquare.com/in/blog/doconline-alternatives-india) frame the same segment split from different angles.

## The honest limits, both directions

If you actually run a hospital, be straight about the trade. Hospital Copilot is a separate, demo-priced product with two record-system paths: the complete Patient Square HIS/EHR, or an alongside deployment that keeps KareXpert or another incumbent. Patient Square does not claim KareXpert's LIMS, RIS/PACS, pharmacy, telemedicine, or connected-ambulance depth, so verify those modules rather than assuming module-for-module parity.

Practice Copilot can use Patient Square EHR or work alongside an existing EHR, with ambient scribing, scheduling, and messaging. It does not claim KareXpert's LIMS, RIS/PACS, pharmacy inventory, or telehealth modules. Hospital Copilot likewise supports either the complete Patient Square HIS/EHR or an existing HIS/EHR, so validate those specialist modules for the selected hospital path.

On compliance, the same honesty holds. Records are handled to DPDP Act 2023 standards, the SOC 2 Type II audit is in progress and not yet certified, and ABDM integration is on the roadmap, not live. Records born digital, ready for the ABHA-linked era on your timeline. If a vendor claims live, certified ABDM, ask to see the NHA certificate.

## When KareXpert is the better choice

Choose KareXpert if you're a hospital or multi-specialty group that needs its LIMS, RIS/PACS, pharmacy, telemedicine, and BI modules on one cloud system. Hospital Copilot supports a complete Patient Square HIS/EHR or an existing HIS/EHR, but it does not claim KareXpert's specialist-module depth.

Choose Patient Square if its verified scope fits. A clinic can use Patient Square EHR or an existing EHR through Practice Copilot. A hospital can use the complete Patient Square HIS/EHR or keep KareXpert through Hospital Copilot's alongside path. Either way the ambient workflow finishes the record while the patient is still in the room.

## How to decide this week

Skip the enterprise-deck comparison and run a five-minute test:

1. Name your building. Hospital with labs, radiology, and pharmacy under one roof, you want a platform. Solo or small clinic, you almost certainly don't.
2. Clinic? Shortlist per-doctor documentation tools with published pricing and no rollout project.
3. Hospital? Decide whether the real need is the full HIMS module suite (scope KareXpert) or documentation at scale (talk to us about Hospital Copilot).
4. Match the clinical output like for like: a structured SOAP note, ICD-10 suggestions, a checked prescription draft.
5. Trial on real visits in your own languages, Hindi in, clean English note out, and settle the data questions: hosting, ownership, and the true ABDM status of anyone claiming it.

The [pricing page](https://patientsquare.com/in/pricing) has the clinic per-doctor ladder, and a [short demo](https://patientsquare.com/in/) shows note quality on your own visit type. If you need the full platform, KareXpert earns the look. If you just need your notes done tonight, you're already in the right place.

---

## Lybrate Alternatives for Clinics: Docs Over Listings
https://patientsquare.com/in/blog/lybrate-alternatives-for-clinics-india/
Published 2026-06-25 · Tags: alternatives, comparison, lybrate, clinic-software, ai-scribe

Lybrate started as patient acquisition; its Cube clinic tool is priced from ₹799/mo. If your real drain is documentation, here is the AI-scribe alternative.

For a specific job, yes. Lybrate built its name on patient acquisition through a consumer app, and now sells Cube, a clinic-management tool from about ₹799 a month. Patient Square goes at a different problem: the documentation and records load. Its ambient AI scribe drafts the note, ICD-10 suggestions, and prescription from the consult, and the bundled AI EHR ships in the Copilot plan at ₹2,399 per doctor per month, ex-GST.

If you're searching for a Lybrate alternative, first get clear on which job you're hiring for. Lybrate made its name on patient acquisition through a consumer app, and it now sells Cube, a clinic-management tool priced from about ₹799 a month. That's a fine answer if your goal is filling the appointment book. It's not built to solve documentation. If your real daily drain is writing notes after every patient, the alternative you want is an ambient AI scribe: Patient Square drafts the note from the consult, and the bundled AI EHR starts at ₹2,399 per doctor per month, ex-GST. The [India pricing](/in/pricing/) is one click away.

The two tools aren't rivals so much as answers to different questions. Sort out which question is yours before you compare prices.

> **Key takeaways**
>
> - Lybrate is patient-acquisition-first: a consumer app that lists doctors, plus Cube, a clinic-management tool from about ₹799/mo.
> - Practice Copilot supports Patient Square EHR or an existing EHR, with an ambient scribe that drafts the note, ICD-10 suggestions, and Rx from the consult.
> - Patient Square publishes ₹1,599/mo for the scribe (Assist) and ₹2,399/mo for the bundled-EHR Copilot plan, annual, ex-GST.
> - Lybrate can bring you patients; Patient Square can't. Patient Square documents your visits; a listing tool doesn't.
> - They can run side by side. Match each tool to the job it's built for.

## What is Lybrate actually built for?

Patient acquisition, at its core. Lybrate grew on a consumer app where patients search for doctors, ask health questions, and book appointments, and doctors gain visibility, some of it through paid sponsored placement. That reach is a genuine asset. A clinic that needs more new patients gets something from a marketplace that a documentation tool simply can't offer.

On top of that, Lybrate now publishes Cube, a practice-management product from around ₹799 a month for a single clinic on an annual plan, with appointments, patient records, billing, and reminders. Credit where it's due: that price is transparent and published, which a lot of Indian clinic software isn't. Cube is a real practice-management tool, not just a listing.

What Cube isn't is an ambient documentation system. It helps you manage the practice around the visit. It doesn't sit in the room and write the note for you. That's the line that decides whether Lybrate is your alternative or the wrong category. Book a demo if you want to see what "writes the note for you" actually looks like.

## What does Patient Square do differently?

It goes after the one cost a listing tool leaves untouched: the note. The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. You have the consult in whatever language it naturally runs in, Hindi, English, or a mix, and the note lands in clean clinical English.

That drafting-from-conversation is the whole product. Patient Square has no consumer marketplace and makes no attempt to bring you patients. It assumes you already have a full OPD and that the problem is documenting it fast enough to keep a defensible record. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. An ambient scribe closes that visit-to-record gap before the next patient walks in.

Here's the honest side-by-side:

| | Lybrate | Patient Square |
|---|---|---|
| Core job | Patient acquisition + practice management | Ambient documentation + records |
| Brings you new patients | Yes, via consumer app | No |
| Writes your clinical note | No | Yes, drafts SOAP + ICD-10 + Rx |
| Published price | Cube from ~₹799/mo | Assist ₹1,599/mo; Copilot (with EHR) ₹2,399/mo |
| Bundled AI EHR | Not the focus | Yes, at the Copilot tier |
| Indian-language capture | App supports Indian users | English, Hindi, Hinglish, 20+ languages |

For the broader clinic-software field, our [best clinic management software roundup](/in/blog/best-clinic-management-software-india/) puts acquisition and documentation tools in one map.

## What does Patient Square cost?

Published and flat, like Lybrate's Cube. Patient Square's Assist plan is ₹1,599 per doctor per month, annual, ex-GST, for the scribe, scheduling, ICD-10 suggestions, and eRx drafts. The bundled AI Copilot EHR turns on at the Copilot tier, ₹2,399 per doctor per month, ex-GST.

| Plan | Price (annual, per doctor, ex-GST) | With 18% GST | What you get |
|---|---|---|---|
| Assist | ₹1,599/mo | ₹1,887/mo | AI Medical Scribe, ICD-10 suggestions, eRx drafts, scheduling |
| Copilot | ₹2,399/mo | ₹2,831/mo | Everything in Assist, plus bundled AI Copilot EHR and WhatsApp |
| Autopilot | ₹3,999/mo | ₹4,719/mo | Everything in Copilot, plus AI Receptionist, follow-ups, analytics |

Unlimited visits and notes, no per-note metering, no setup fee. Confirm current numbers on the [pricing page](/in/pricing/). The two products aren't priced to be compared head to head, because they don't do the same thing. Lybrate's Cube is priced to manage a practice; Patient Square is priced to document one.

## When is Lybrate the better call?

When your priority is patients, not paperwork. A newer clinic that needs to fill its book, or a doctor who wants low-cost practice management with booking and reminders and is fine driving the documentation by hand, is better served by Lybrate. Its acquisition reach is real and its Cube pricing is reasonable. An ambient scribe won't put a single new patient in your waiting room, and if that's your bottleneck, it's the wrong tool.

Choose Patient Square when the visits are already there and the problem is documenting them: the after-hours typing, the thin notes, the records you can't produce fast when a claim or a court asks. That's the drain an ambient scribe removes.

And you can run both. Let Lybrate handle listings and booking while Patient Square handles the note inside the visit. Our [Practo Ray alternatives](/in/blog/practo-ray-alternatives-india/) coverage makes the same split for another acquisition-plus-management incumbent.

## How to decide in a week

1. Name your bottleneck honestly. Too few patients points to Lybrate. Too much charting points to an ambient scribe.
2. If it's acquisition, price Lybrate's listing reach and Cube plan for your clinic count.
3. If it's documentation, trial an ambient scribe on real visits and watch how much editing the note needs.
4. If it's both, plan to run an acquisition tool and a documentation tool together, not one stretched to do both.
5. Confirm Patient Square's current price and GST on the [pricing page](/in/pricing/), then book a short demo to see a finished note against your own visit type.

The encryption and data-ownership receipts are on the [security page](/in/security/). Notes belong to the clinic; export or delete any visit anytime. A listing tool and an ambient scribe answer different questions. Buy the one that answers yours.

---

## ModMed Alternatives: Specialty Templates Without the Lock-In
https://patientsquare.com/us/blog/modmed-alternatives/
Published 2026-06-25 · Updated 2026-08-27 · Tags: alternatives, ehr, modmed, comparison

Compare ModMed with options for specialty-aware templates and ambient documentation, including a published-price bundled EHR from $119 per provider.

ModMed uses custom, quote-based pricing, so there's no published per-provider rate. Third-party trackers estimate a range from roughly $50 per user monthly for small practices up to several hundred per provider, with a common cloud-EMR band of $200 to $700. Implementation runs $2,000 to $10,000. Because it's quote-driven, your real number comes only from a sales conversation.

If you're weighing a ModMed alternative, it's usually about two things: the price you can't see until you're on a sales call, and the lock-in that comes with a deeply specialty-built system. ModMed is excellent inside dermatology, GI, ophthalmology, and orthopedics. It's also quote-priced and heavy to implement. If you want specialty-aware templates and an ambient scribe without that commitment, Patient Square's Copilot plan is **$119 per provider per month** annually, with templates ready out of the box. You can see a finished note in about two minutes before anything else.

Straight talk: for a true single-specialty derm or ophthalmology practice, ModMed's depth is hard to beat, and this page says so. The alternative is for practices that want most of that value without the price and the lock.

> **Key takeaways**
>
> - ModMed uses custom, quote-based pricing; third-party estimates span roughly $200–$700 per provider, plus $2,000–$10,000 implementation.
> - Its edge is deep, single-specialty workflows for derm, GI, ophthalmology, and orthopedics.
> - Patient Square ships specialty-aware templates out of the box, bundled with the scribe and AI EHR.
> - Patient Square Copilot is $119/provider monthly (annual), with a published price and no per-note metering.
> - ModMed still wins if your practice lives inside one of its core specialties and needs that depth.

## ModMed alternatives at a glance

The split is specialty depth versus flat, published, bundled value.

| Alternative | Best for | Ambient scribe | Pricing |
|---|---|---|---|
| ModMed (staying) | Deep single-specialty (derm, GI, ophtho, ortho) | Suite AI tooling | Quote-based, ~$200–$700+/provider |
| Patient Square Copilot | Broad or multi-specialty, wants templates + scribe | Yes, bundled | $119/provider/mo (annual), published |
| General EHR + separate scribe | Custom stacks | Separate subscription | Varies |

ModMed figures are third-party estimates as of this writing; only a quote gives your real number. The table shows direction, not a bid.

If quote-priced lock-in is the thing you want to avoid, start with the published-price option. If you're deep in a single specialty ModMed was built for, keep reading for the honest case to stay.

## Why practices shop for ModMed alternatives

Two reasons come up again and again.

First, **the price is invisible until you're in sales.** ModMed uses custom pricing, so you can't compare it on a spreadsheet the way you can a published plan. Third-party trackers estimate a wide band, roughly $200 to $700 per provider for cloud EMR, but your number depends entirely on the quote. For a practice that just wants to know what it'll pay, that opacity is friction.

Second, **specialty depth means lock-in.** ModMed's value is that it's built around one specialty's exact workflow. That's also what makes it hard to leave: the deeper the specialty tooling, the more your team is trained into it, and the bigger the migration. Practices that don't need that depth end up paying and committing for value they only partly use.

A published-price bundle answers both: you see the number before you commit, and the templates are broad rather than locking you into one specialty's engine.

## What "specialty-aware templates" means in a bundle

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Specialty-aware templates ship ready out of the box, part of what every plan includes.

Be precise about what that is and isn't. These templates cover common specialties well, so the note comes back shaped for your visit type rather than as a generic block. What they aren't is ModMed's deep, single-specialty workflow engine, the kind that encodes years of dermatology or ophthalmology practice into structured fields, imaging tie-ins, and specialty-specific coding paths. If that depth is your requirement, name it early.

The bundle wins on breadth and price: templates, an ambient scribe, and the AI Copilot EHR at $119 per provider annually, published, no per-note meter, no setup fee. Book a demo and check the template output against your own specialty's visit.

## ModMed vs Patient Square: what you're really choosing

| | ModMed (estimated) | Patient Square Copilot |
|---|---|---|
| Pricing | Quote-based, ~$200–$700+/provider | $119/provider/mo (annual), published |
| Specialty templates | Deep, single-specialty | Specialty-aware, broad, out of the box |
| Ambient scribe | Suite AI tooling | Bundled, note ~2 min after visit |
| Implementation | $2,000–$10,000 | None |
| Best fit | Derm, GI, ophtho, ortho | Broad / multi-specialty |
| Free trial | Demo-led | 7-day trial |

The honest read: these serve different practices. ModMed is a specialty operating system. Practice Copilot is an AI clinical platform with an ambient scribe and either Patient Square EHR or an alongside path for an existing EHR. Your specialty and your appetite for lock-in decide it. For related reading, see our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup and the [best EHR for psychiatry](/us/blog/best-ehr-for-psychiatry/) page.

## When ModMed is the better choice

Stay with ModMed, or choose it, if your practice lives inside one of its core specialties. If you run a dermatology, GI, ophthalmology, or orthopedics practice and rely on specialty-specific workflows, imaging, and coding paths built for exactly your field, ModMed's depth is worth its price and its lock-in. A general bundle with broad templates can't replicate that, and switching away to save on price would trade a specialty engine for a generalist tool.

ModMed is also the safer call if your specialty depends on integrated imaging, inventory, or procedure workflows that a documentation-first bundle doesn't offer. Match the tool to the specialty. If ModMed was built for your field, it's usually built better for you than anything general.

For broader or multi-specialty practices, though, the trade flips: templates plus a scribe plus an EHR at a published $119 beats paying enterprise specialty pricing for depth you don't fully use.

## How to decide in a week

Run it on real visits before you commit either way:

1. Ask whether your practice is one specialty or several. One of ModMed's core specialties tilts toward staying.
2. Get ModMed's quote in writing so you can actually compare a number.
3. Trial a bundled tool's templates against your own specialty's visit type.
4. Check the ambient note quality on a real, unscripted visit.
5. Weigh migration cost honestly; deep specialty tooling is harder to leave than to join.

The receipts, encryption, access, and audit status, are on the [security page](/us/security/), and the full price ladder is on the [pricing page](/us/pricing/). Book a short demo to see the templates and note against your own visits, then run the 7-day trial on a real week. For most broad or multi-specialty practices, specialty-aware templates plus a scribe at a published $119 give you the value without the ModMed lock-in.

---

## Progress Note Examples and Template
https://patientsquare.com/us/blog/progress-note-examples/
Published 2026-06-25 · Updated 2026-07-22 · Tags: clinical-documentation, progress-note, templates

What a progress note is, the formats it can take (SOAP, DAP, narrative), two worked examples, a blank template, and a guide to picking the right format.

A progress note is the entry a clinician writes after a patient encounter to record what happened and what comes next. It is the running account of a patient's course of care across visits. Each note captures the current status, your clinical thinking, and the plan, so the next person who opens the chart knows where things stand.

A progress note is the entry you write after a patient encounter to record what happened and what comes next. It's the running account of a patient's care, one note per visit, building into the story of how they're doing over time. "Progress note" is the umbrella. SOAP, DAP, BIRP, and plain narrative are formats you can write one in. This page covers what goes in a progress note, how to pick a format, two worked examples, and a blank template.

The word trips people up because "progress note" and "SOAP note" get used as if they mean the same thing. They don't. The note is the document; the format is how you organize it. Once that's clear, the real question is which format fits which encounter, and that's mostly about whether the visit has measurable findings to separate from the patient's own report. We'll sort that out below.

> **Key takeaways**
>
> - A progress note is one document; SOAP, DAP, BIRP, and narrative are four formats for writing it.
> - Pick the format by the encounter: SOAP for visits with exam findings, DAP or BIRP for talk therapy, narrative for short interval updates.
> - No payer or law mandates a format. They require content: medical necessity, legible, dated, signed, per 42 CFR 482.24 and CMS guidance.
> - Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit, so the note now outlasts the visit it describes.
> - An AI scribe drafts the progress note for you in about two minutes; you still read and sign every one.

## What is a progress note, and what does it record?

A progress note documents one encounter and connects it to the ones before and after. That's the whole job. Someone covering your panel next week opens the chart, reads your last note, and knows what's going on without calling you. A reviewer pulls the record a year later and sees that the visit happened, what you found, and why you did what you did. The note is the only durable trace of a conversation that's otherwise gone the moment the patient leaves.

Per StatPearls, the SOAP note, the most common form, is "an essential piece of information about the health status of the patient as well as a communication document between health professionals." That second half matters. A progress note isn't a diary. It's written to be read by other clinicians, by you on a worse day, by a coding team, sometimes by a court. So it carries a fixed core no matter which format you choose:

- What the patient reports today, in their words where it counts.
- What you observe or measure: exam, vitals, scores, results.
- Your clinical read of it: the diagnosis or working impression, the reasoning.
- The plan: medications, tests, referrals, the next visit, what changed.

Federal rules set the floor for how that entry has to look. Under 42 CFR 482.24, medical records must be "accurately written, promptly completed, properly filed and retained, and accessible," and every entry has to be "dated, timed, and authenticated." None of that says SOAP. It says the note must be real, complete, and signed by you. The format is your call inside those lines.

## What are the common progress note formats?

Four formats cover almost everything you'll write. They differ in how they slice the same content, not in what counts as a good note.

| Format | Sections | What it's tuned for |
|---|---|---|
| **SOAP** | Subjective, Objective, Assessment, Plan | The cross-discipline default. Splits the patient's report from your measured findings, then your judgment. Fits any visit with an exam. |
| **DAP** | Data, Assessment, Plan | Folds report and observation into one Data block. Faster for talk therapy, where reported-versus-observed is a blurry line. |
| **BIRP** | Behavior, Intervention, Response, Plan | Separates what you did from how the client reacted. Common in Medicaid and substance-use work because medical necessity reads off it cleanly. |
| **Narrative / interval** | No fixed headers; chronological prose | Short updates: an inpatient interval note, a quick follow-up, a phone check. Less structure, faster, easier to leave a gap in. |

SOAP is what most clinicians trained on, and it's what most AI scribes draft by default. DAP and BIRP are behavioral-health adaptations: DAP collapses a section to write faster, BIRP adds a section to make a billable intervention obvious to a reviewer. Narrative notes are the oldest form and still the right tool for an interval update where four headers would be overkill.

We go deep on the behavioral-health formats in their own guides. The [DAP note guide](../dap-note/) covers Data-Assessment-Plan with a worked therapy example. The [BIRP note guide](../birp-note/) walks through Behavior-Intervention-Response-Plan. And if you write SOAP for therapy specifically, [how to write a mental-health SOAP note](../how-to-write-a-mental-health-soap-note/) has a six-point rubric for grading drafts. This page is the level above those: which one to reach for, and why.

## Which progress note format should you use?

This is the picker most of this page builds toward. Match the row to your encounter, and if your agency or payer already named a format, that overrides everything below.

| If the encounter is... | Reach for | Because |
|---|---|---|
| A medical visit with an exam, vitals, or labs | **SOAP** | You have objective findings worth keeping in their own section, separate from what the patient told you. |
| A primary-care or specialty follow-up | **SOAP** | The four headers map cleanly to how the visit runs, and coders and reviewers expect them. |
| A talk-therapy or counseling session | **DAP** | The line between reported and observed is blurry in therapy; one Data section reads more naturally than forcing Subjective-versus-Objective. |
| A session where you must show a billable intervention worked | **BIRP** | The Intervention and Response sections put medical necessity on the page for a payer to read. |
| A short interval update, a phone follow-up, an inpatient daily | **Narrative** | A quick chronological note beats four mostly-empty headers; just don't let it drop the plan. |
| A note your employer or Medicaid program specifies | **Their format** | A contract requirement isn't a preference. Match the headings they audit against. |

Two honest caveats, because the table makes it look cleaner than practice is. First, plenty of clinicians keep two formats in their head and switch per encounter, a SOAP note for the medication-management half of a visit, a DAP note for the therapy half. That's normal. Second, the format is the smallest decision here. A SOAP note with a hollow Assessment is worse than a narrative note that actually says what you were thinking. Structure helps; it doesn't substitute for content.

## A worked progress note example in SOAP format

This is the artifact. Below is a complete progress note for a routine primary-care follow-up, written the way a competent scribe should draft it from the visit audio. The case is invented; no real patient. The shape and detail are what you should expect on screen about two minutes after a visit ends.

**Encounter:** Established adult patient, type 2 diabetes and hypertension, three-month follow-up.

> **Subjective:** Patient reports feeling well overall. Checking blood glucose most mornings, fasting values "usually around 130 to 145." Taking metformin 1000 mg twice daily and lisinopril 20 mg daily as prescribed, no missed doses this month. Denies polyuria, blurred vision, chest pain, or swelling in the legs. Walking 20 minutes most days, down from the soda he cut out two months ago. One concern: occasional lightheadedness when standing quickly, two or three times a week, resolves in seconds.
>
> **Objective:** BP 128/78 seated, 122/76 standing. Weight 94 kg, down 2 kg since last visit. Heart regular rate and rhythm, lungs clear, no peripheral edema. Feet examined: intact sensation to monofilament, no ulcers or lesions. Point-of-care A1c 7.1%, down from 7.6% three months ago.
>
> **Assessment:** Type 2 diabetes, improving glycemic control (A1c 7.6 to 7.1). On track toward the under-7 goal with current regimen and lifestyle changes. Hypertension well controlled on lisinopril. Orthostatic lightheadedness is mild and positional; no orthostatic drop on today's readings, likely benign, will monitor. No signs of diabetic neuropathy or retinopathy reported.
>
> **Plan:** Continue metformin 1000 mg twice daily and lisinopril 20 mg daily, no changes. Continue current diet and walking. Recheck A1c in three months. Referred to ophthalmology for annual diabetic eye exam, last one over a year ago. Counseled to stand up slowly and stay hydrated; return sooner if lightheadedness worsens or he has a near-fall. Follow-up in three months.

Read it the way you'd read your own. The Subjective is the patient's report, including the lightheadedness he volunteered. The Objective is what was measured, the two blood-pressure readings, the A1c, the foot exam, and nothing interpretive. The Assessment is where the thinking lives: the trend, the goal, the read on the lightheadedness. The Plan is specific. Not "continue treatment" but the actual doses held, the actual referral, the actual safety advice. A vague Plan is a Plan you'll rewrite.

## A worked progress note example in narrative format

Same patient class, different format, to show the contrast. A narrative interval note has no headers; it's chronological prose. It's faster, and it's easier to leave a hole in, so the discipline is making sure the plan still lands. This one is an inpatient daily progress note, again invented.

**Encounter:** Hospital day 3, adult admitted for community-acquired pneumonia.

> Day 3 of admission for community-acquired pneumonia. Patient reports the cough is looser and less frequent, no chest pain, appetite returning. Overnight temperature peaked at 37.8 C, down from 38.9 C on admission. This morning afebrile at 36.9 C, oxygen saturation 95% on room air, off supplemental oxygen since yesterday evening. Lungs with improving air entry at the right base, scattered crackles persist but reduced. Tolerating oral intake, IV fluids discontinued. White count trending down, 11.2 from 14.6 on admission. Clinically improving on day 3 of oral antibiotics after transition from IV yesterday. Plan: continue oral amoxicillin-clavulanate to complete a 7-day course, encourage ambulation and incentive spirometry, anticipate discharge tomorrow if afebrile overnight and saturations hold on room air. Discharge planning started with nursing; will arrange primary-care follow-up within one week.

No headers, but every part of a SOAP note is in there, woven into the timeline: what the patient reports, the vitals and exam, the clinical read, the plan. That's the trick with narrative notes. The structure is invisible, but the content can't be. Drop the plan and you've left the next clinician guessing.

## A blank progress note template you can copy

Below is a format-agnostic template. Fill the sections that fit your encounter; for a narrative note, treat the headers as a checklist of things the prose has to cover rather than literal labels.

| Section | What to put here | Skip if |
|---|---|---|
| **Identifier / context** | Date, visit type, who the patient is in one line, why they're here today | Never. Every note needs this. |
| **Subjective / what's reported** | The patient's account: symptoms, changes since last visit, adherence, concerns. Quotes where they carry weight. | Nothing reported (rare; usually there's something). |
| **Objective / what's measured** | Vitals, exam findings, scores, lab and imaging results, anything you observed firsthand | A pure phone or message check with no exam, fold it into the narrative. |
| **Assessment / your read** | Diagnosis or working impression, the trend, your reasoning, risk if relevant | Never. This is the section that justifies the visit. |
| **Plan / what's next** | Medications held or changed, tests ordered, referrals, patient instructions, next visit | Never. A note with no plan is incomplete. |
| **Signature** | Your name, credential, date and time, attribution for any later edits | Never. 42 CFR 482.24 requires every entry dated, timed, and authenticated. |

Copy it, drop the rows you don't need for a given encounter, and you have SOAP, DAP, or a narrative scaffold. The two rows you can never cut are Assessment and Plan. Those carry the clinical weight, and they're the two an audit reads first.

## What does every progress note need to be defensible?

Whatever format you pick, a handful of things have to be true before the note is one you'd defend. We've anchored this to the federal record rule rather than to any vendor's marketing, because the audit standard is what matters when someone pulls the chart.

42 CFR 482.24 requires entries to be "accurately written, promptly completed, properly filed and retained," and "dated, timed, and authenticated." CMS's documentation guidance adds the content side: a note must reflect medical necessity, be legible and complete, and justify the service billed. The same CMS guidance warns specifically about "cloned" notes, ones that look identical across different visits, because they "may not reflect the uniqueness of the encounter." That warning was written about copy-paste and templates. It applies word for word to an AI draft you didn't read.

| Check before you sign | Why it matters |
|---|---|
| **Nothing invented.** No symptom, finding, or result the patient never reported or you never measured. | A confident wrong detail is worse than a blank field. You have to already know it's wrong to catch it. |
| **Nothing dropped.** Every decision you made is in the Plan: the referral, the dose change, the safety advice. | A missing plan item is a missed action and a documentation gap a reviewer will find. |
| **The Assessment is yours.** Real clinical reasoning, not a paraphrase of the Subjective. | This is the section that shows medical necessity. A recycled Assessment doesn't. |
| **It doesn't look cloned.** This note reflects this visit, not last month's with the date changed. | CMS flags cloned notes by name. An AI draft that reuses phrasing trips the same wire copy-paste does. |
| **It's dated, timed, and signed by you.** Your credential, the correct time, edits attributed. | 42 CFR 482.24 makes this the baseline. The signature is you taking ownership of the content. |

Run a real note through this, not a demo. The note that matters is the one from your messiest visit, the patient who buried the real complaint in the last two minutes. A format change won't save a sloppy note, and neither will a fast one.

## Where AI Medical Scribe by Patient Square fits

The reason progress notes eat your evenings isn't that the format is hard. It's the volume. Primary-care physicians in a 2023 JAMA Network Open study logged a median of 36.2 minutes of EHR time per 30-minute visit, which the American Medical Association summed up the obvious way: the note now takes longer than the appointment. Pick whatever format you like; the typing is the tax.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The default structure is SOAP, the format most clinicians and payers expect. The ICD-10 codes are suggestions, not automated coding; the prescription is a draft, not an order sent anywhere. The note is yours to read, edit, and sign. The draft saves the typing, not the judgment.

On the part that should decide any vendor: visit audio is processed in memory and discarded the moment the note is drafted. There's no recording kept to retain, train on, or produce under a subpoena. Notes are encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice, which can export or delete any visit at any time. We maintain HIPAA compliant safeguards and offer a BAA to every customer, and our SOC 2 Type II audit is underway.

The honest limit: if you write notes reflectively, as part of how you think a case through, a scribe is a poor fit no matter whose it is. If you need a format the default draft doesn't produce, like BIRP for a managed-care contract, confirm the draft maps cleanly to your headings before you commit, since it drafts SOAP first. And we don't write back into an EHR, so weigh that gap if you need the note to land automatically. For a clinician who just wants the documentation load off their evenings, a scribe that drafts a clean note and keeps none of your audio is a straight win.

The way to know is to grade a real note. Review the [pricing page](../../pricing/), then run the 7-day free trial on your own visits and put three notes through the checklist above. If a tool can't produce a sign-ready note on your hardest visit, no time-saved number will rescue it.

---

## EHR vs HMS in India: Which One Does Your Clinic Need
https://patientsquare.com/in/blog/ehr-vs-hms-india/
Published 2026-06-24 · Tags: ehr, hms, buyer-guide, india

EHR or HMS for an Indian clinic or hospital? A buyer guide on what each one actually does, where the line blurs, and how to decide by your real bottleneck.

An EHR (electronic health record) is built around the patient record: history, diagnoses, prescriptions, lab results, and the clinical note from each visit. An HMS (hospital management system) is built around running the facility: OPD and IPD registration, bed and ward management, billing, pharmacy, stores, the lab, and staff. An HMS almost always contains an EHR-like clinical module inside it. A standalone EHR rarely contains the full operational machinery of an HMS.

An EHR and an HMS are not two names for the same thing, and buying the wrong one is an expensive way to learn that. An EHR is built around the patient record. An HMS is built around running the facility. The fast version: if your problem is notes, prescriptions, and clinical history, you want an EHR. If your problem is beds, departments, pharmacy stock, and facility-wide billing, you want an HMS. This guide walks the line between them so you buy for the bottleneck you actually have.

> **Key takeaways**
>
> - An EHR is organised around the patient record. An HMS is organised around running the facility and usually contains an EHR-like clinical module inside it.
> - Most small OPD clinics do not need a full HMS. The bed, ward, and multi-department billing modules sit unused while you pay for them.
> - In India "EMR" and "EHR" are used almost interchangeably in vendor marketing; check what the product stores, not the label.
> - Both categories can integrate with ABDM through the NHA gateway, so ABDM readiness is a per-product check, not a reason to pick one type.
> - Whichever you buy, an AI scribe sits on top and removes the typing. AI Medical Scribe by Patient Square is that documentation layer, not a replacement for either system.

## What an EHR actually does

An EHR keeps the clinical story of each patient in one place. Demographics, past visits, diagnoses, prescriptions, lab and imaging results, allergies, and the note from today's consult all live in the record and follow the patient across visits. The MoHFW EHR Standards 2016 set out what a compliant Indian record should hold and how it should be coded, so the data stays usable when it moves between providers (MoHFW, EHR Standards for India, 2016).

For an OPD clinic, the EHR is the workhorse. You register a patient, pull up history, examine, prescribe, and the visit goes into a record you can find again next month. A clinic EHR, often sold as clinic-management software in India, wraps that record with appointment booking, a queue, and simple billing. It is sized for a practice, not a hospital. No wards, no inter-department transfers, no central stores to reconcile.

The thing an EHR does not solve is the time cost of filling it. Doctors spend a large and well-documented share of the working day on documentation; an international comparison in BMJ Open found clinicians giving up substantial clinic time to administrative and record-keeping work (Irving et al., BMJ Open 2017). The record is essential. Typing it during the consult is the part that eats the day.

## Why an HMS is a different animal

So if the EHR already holds the clinical record, why would a facility buy something bigger? Because the record is only one of the things a hospital has to coordinate, and an OPD-sized clinic EHR has no answer for the rest. That gap is exactly where an HMS lives.

An HMS runs the facility. On top of an EHR-style clinical module, it adds OPD and IPD registration, bed and ward management, admission and discharge flows, operation-theatre scheduling, a pharmacy with inventory, central stores, the lab, payroll, and billing that spans every department. A 200-bed hospital cannot run on a clinic EHR. It needs the whole operational backbone, and that backbone is the HMS.

The trade-off is weight. An HMS is more to buy, more to configure, and more to train staff on, because it does far more. Drop one into a two-doctor OPD clinic and most of it goes unused while you still pay and still train for it. The clinical module you actually touch ends up doing the job a clinic EHR would have done at a fraction of the cost and effort.

## The grey zone, and how to read it

Here is where buyers get stuck. The categories overlap. Every HMS has an EHR-like module inside it, and many clinic EHRs have grown billing and pharmacy features that edge toward HMS territory. Vendors blur the line further by stacking "EHR", "EMR", "HMS", and "clinic management" into one feature page. The words stop being a reliable guide.

So stop reading labels. Read modules instead. List what each product actually stores and runs, then match that against your real workflow.

A few sharp questions cut through the marketing. Do you admit patients and manage beds, or is it all walk-in OPD? Do you run a pharmacy and stores you need to reconcile, or do patients fill scripts outside? Does billing span departments, or is it one counter? Beds and departments push you toward an HMS. A walk-in OPD with one billing counter points at an EHR. The honest answer to those three usually settles it.

## Where the AI scribe fits, on either system

Notice that the scribe column above answers a different question from the other two. EHR and HMS are about what your facility stores and runs. The scribe is about who does the typing. That is why it sits on top of either one instead of competing with them.

AI Medical Scribe by Patient Square listens to the consult and, in about two minutes after the visit, drafts a structured SOAP note, suggests ICD-10 codes for you to confirm, and drafts a prescription for you to check and finalise. It is a documentation layer. It does not store the long-term record, run billing, manage beds, or hold pharmacy stock. Those stay with your EHR or HMS. The scribe removes the part doctors hate, the live typing, and hands back a draft you review.

On compliance, we build to DPDP Act 2023 standards, and ABDM integration is on our roadmap rather than live today. So when you pick the EHR or HMS underneath, weigh its ABDM support on its own terms; both categories can integrate with the national stack through the NHA gateway (National Health Authority, ABDM).

## How to decide

Buy for the bottleneck you have now, not the org chart you might grow into.

1. Name the real pain. Is it the patient record, prescriptions, and notes, or is it coordinating beds, departments, pharmacy, and facility billing? The first is an EHR problem. The second is an HMS problem.
2. Read modules, not labels. Make each shortlisted vendor show you what it stores and runs against your actual workflow.
3. Confirm the standards. Check that the product follows the MoHFW EHR Standards 2016 and helps you meet your DPDP Act 2023 obligations, and verify ABDM support if record portability matters to you.
4. Then add the scribe. Whichever system you land on, an AI scribe layered on top removes the documentation time. That part of the pain is the same on an EHR or an HMS.

If your facility is OPD-led and the daily grind is notes and prescriptions, start with the focused options in our [EMR software in India guide](../emr-software-india-guide/) and the [best clinic management software in India](../best-clinic-management-software-india/) roundup. If you keep tangling the terms, [EMR vs EHR in India](../emr-vs-ehr-india/) untangles those two, and [hospital management system explained](../hospital-management-system-explained/) covers the HMS side in depth. Already weighing a switch? [AI scribe vs a new EHR](/in/blog/best-ai-scribe-vs-emr-which-first-india/) walks the cheaper-fix-first sequence.

When you want to see how the scribe rides on top of whatever you choose, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> or start a <a href={CTA_URLS.in.trial}>7-day free trial</a>. No card, no integration setup.

_Reviewed by the Patient Square clinical team._

---

## Medixcel Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/medixcel-alternatives-india/
Published 2026-06-24 · Updated 2026-08-27 · Tags: alternatives, comparison, medixcel, pricing

Medixcel is a modular clinic-chain EMR you fill in, priced by quote. Patient Square drafts the note for you and bundles the EHR from ₹2,399/mo per doctor.

Running a clinic or chain as a system of record. Medixcel, from Plus91 Technologies, pulls appointments, EMR, billing, pharmacy and inventory, lab and radiology, insurance, a patient portal, and multi-clinic controls into one platform. If you need those operational modules under one login across several locations, that breadth is the reason to pick it.

If Medixcel is on your list, here's the honest split. Medixcel is a modular clinic and chain EMR, the kind you fill in: appointments, EMR, billing, pharmacy, lab, insurance, a patient portal, all under one login, priced by quote. Patient Square works the other way round. Instead of handing you empty fields to type into, an ambient scribe listens to the visit and drafts the record for you, then bundles an AI EHR on top. The price is published: ₹1,599/mo per doctor to start, ₹2,399/mo once the bundled EHR is in (ex-GST, add 18%, so about ₹2,831 all-in on the Copilot tier). You can book a demo and watch a SOAP note land in roughly two minutes.

Different tools for different problems. Below: what Medixcel is genuinely good at, why its price is a quote not a page, what you type versus what gets drafted, and when Medixcel is the smarter buy.

> **Bottom line**
>
> - Medixcel is a modular clinic/chain EMR from Plus91: EMR, appointments, billing, pharmacy, inventory, lab, radiology, insurance, patient portal, multi-clinic. Quote-priced.
> - Practice Copilot supports Patient Square EHR or an existing EHR, with an ambient scribe and published per-doctor pricing from ₹1,599/mo.
> - Medixcel gives you fields to fill in. Patient Square fills the note in for you, then structures it.
> - Need pharmacy, lab, and insurance modules across sites? Medixcel. Buried in charting after every OPD? Patient Square.

## Medixcel vs Patient Square: which problem are you solving?

One is a records-and-operations platform. The other drafts the record itself. Match the row to your actual pain.

| | Medixcel | Patient Square |
|---|---|---|
| Built for | Clinics and chains that need operational modules | Doctors drowning in documentation |
| Scope | Modular clinic/chain EMR: EMR, billing, pharmacy, lab, insurance, portal, multi-clinic | Ambient scribe that drafts the record + bundled AI EHR |
| How the note happens | You type into EMR fields | Scribe drafts a structured note from the visit |
| Ambient AI scribe | Not the core | Yes, note ready in about 2 minutes |
| ICD-10 | Manual entry | Suggestions on the drafted note |
| Prescription | Manual | Draft prescription (you review and issue) |
| Languages | English data entry | Speak Hindi, Hinglish, 20+ Indian languages; note in clean English |
| Pricing | Quote / demo, not published | Published per doctor: from ₹1,599/mo, bundled EHR from ₹2,399/mo (+GST) |
| Implementation | Rollout across modules and sites | Assisted workspace setup, then web or mobile capture |

If you need Medixcel's module breadth, keep reading its case. If the pain is the note, skip to what gets drafted for you.

## What is Medixcel genuinely good at?

Credit where it's due. Medixcel, from Pune-based Plus91 Technologies, is a mature clinic and chain platform, and its strength is breadth. One login covers patient registration and a portal, appointment scheduling, EMR, billing and invoicing, prescription management, lab and radiology integration, inventory and pharmacy, insurance handling, a doctor dashboard, teleconsultation, and analytics. It runs across single and multi-specialty clinics, clinic chains, diagnostic groups, and hospitals, and manages multiple locations with per-clinic rates, timings, and services. Plus91 lists deployments up to a nearly paperless 2,300-bed hospital and multi-location diagnostic chains.

That's a real system of record. A clinic chain standing up billing, pharmacy, lab, and insurance across four locations, with one place to see it all, should have Medixcel on the shortlist. Nothing below argues with that.

The mismatch is quieter. Medixcel gives you a well-built EMR, but it's still a form you fill in. The doctor at that 4-location chain who finishes OPD at 8pm and then sits typing structured EMR fields until 9 is doing data entry the software captured but didn't write. That's the gap Patient Square is built for, and if it's your gap, [see the drafting approach in a demo](https://patientsquare.com/in/) instead of scoping more modules.

## What does Medixcel cost, and why isn't it on the page?

Medixcel doesn't publish a price. The vendor site and the major listings route you to a demo or an enquiry form, and the honest reason is that a modular platform's cost genuinely moves with your clinic count, which modules you switch on, and how many sites you're rolling out. You can't put a 4-clinic pharmacy-plus-lab-plus-insurance deployment on a rate card.

Fair enough, but it tells you what buying feels like: a scoping and quoting cycle before you know your number. For a chain standing up operations, that's expected. For a solo doctor who mostly wants the notes done, it's friction, an enquiry process to solve a charting problem.

Patient Square just shows you the ladder. Assist is ₹1,599/mo annual, Copilot is ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot is ₹3,999/mo, all ex-GST, add 18%, on the [pricing page](https://patientsquare.com/in/pricing). Every plan includes unlimited visits and notes with no per-note metering, EHR-ready export as PDF, HL7, or FHIR, specialty-aware templates out of the box, and capture on web or mobile. You know the number before the first call.

## What you type vs what gets drafted

This is the real difference, so here it is plainly. In a records-first EMR, the visit happens and then you enter it. With an ambient scribe, the visit happens and the note is already written when the patient leaves.

| During and after a visit | Records-first EMR (fill in) | Patient Square (drafted for you) |
|---|---|---|
| History and complaint | You type it into fields | Captured from the conversation |
| Examination findings | You type it in | Drafted into the SOAP note |
| Structured note | You assemble it | Structured SOAP note in about 2 minutes |
| Diagnosis codes | You look up and enter ICD-10 | ICD-10 suggestions on the draft |
| Prescription | You type each line | Prescription draft to review and issue |
| Language | English entry | Speak Hindi or Hinglish; note in clean English |

The scribe listens during live consultations in Hindi, Kannada, Bengali, and 20-plus Indian languages, including code-mixed speech, and returns a clean English note. Live consultation audio is processed in memory and discarded once the note drafts; uploaded recordings use a separate retention mode with explicit consent. Capture works offline with AES-256-GCM encryption when the connection drops. Canonically: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Want to see it on your own visit type? Book a demo.

## The cost a modular EMR doesn't fix

A broader EMR gives you more modules. It does nothing for the one cost every doctor carries and rarely prices: time lost to writing the record.

Indian consultations run about two minutes on average, per a 67-country BMJ Open study, among the shortest anywhere. In that window the record is what gets shortchanged, and a thin note is expensive later. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours, and the defence that holds in a negligence matter is a complete, contemporaneous note. A pharmacy module or an insurance module doesn't fix a solo GP's 9pm charting. A scribe that finishes the note during the visit does. Patient Square is built around that single problem, not around adding more fields to fill.

## Where Patient Square stays honest

Straight about the trade: Practice Copilot can use Patient Square EHR as the system of record or work alongside an existing EHR. It does not claim Medixcel's pharmacy, inventory, lab, radiology, insurance-claims, or multi-location billing modules. If those modules are what you're buying, we won't pretend to match them.

On compliance, the same honesty: data handled to DPDP Act 2023 standards, SOC 2 Type II audit in progress (not certified), ABDM support on the roadmap, not live. Records born digital, ready for the ABHA-linked era on your timeline. If any vendor tells you they're live and certified on ABDM today, ask to see the NHA certificate. And note the export line precisely: EHR-ready export as PDF, HL7, and FHIR means you can get clean data out, not that we're certified for interoperability.

## When Medixcel is the better fit

Pick Medixcel if you need its settled multi-clinic workflows for pharmacy, inventory, lab and radiology, insurance handling, a patient portal, and per-location billing under one roof. Practice Copilot supports Patient Square EHR or an existing EHR, but it does not claim those specialist modules, and pretending otherwise would waste your time.

Pick Patient Square if the actual pain is the record itself. A doctor who wants notes drafted during the consult, at a per-doctor price they can see up front, with no rollout project, is in the right place. Plenty of clinics run a records platform for operations and add an AI scribe on top so nobody's typing SOAP fields at 9pm.

## How to decide this week

Cut the feature-matrix comparison and run the test:

1. Name the real pain. Operations across sites (billing, pharmacy, lab, insurance) points to a modular EMR. Charting time points to a scribe.
2. If it's operations, scope Medixcel and get the quote for your clinic count and modules.
3. If it's the note, trial an ambient scribe on real visits, Hindi or Hinglish in, clean English SOAP out.
4. Check the clinical output like for like: structured note, ICD-10 suggestions, a prescription draft you review.
5. Settle the data questions early, hosting, ownership, export format, and true ABDM status, not the marketing claim.

Sibling reads if you're weighing this class of tool: [Crelio Health alternatives for India](https://patientsquare.com/in/blog/crelio-health-alternatives-india), [DocPulse alternatives](https://patientsquare.com/in/blog/docpulse-alternatives-india), and, if you're solo, [what an AI scribe actually costs a single doctor](https://patientsquare.com/in/blog/ai-scribe-cost-for-solo-doctor-india). The per-doctor ladder sits on the [pricing page](https://patientsquare.com/in/pricing). Book a short demo and check note quality against your own OPD. If you need the modules, Medixcel earns the look. If you need the writing done, you're already here.

---

## Nabla Alternatives: Past the Free-Tier Cap
https://patientsquare.com/us/blog/nabla-alternatives/
Published 2026-06-24 · Updated 2026-07-22 · Tags: ai-scribe, comparison, nabla, pricing

Compare the Nabla free-tier cap with unlimited scribe plans from $79 and a bundled AI EHR from $119, including cases where Nabla remains the better fit.

Nabla offers a free tier that third-party review sites describe as capped at around 30 consultations a month, with a paid plan for unlimited use. Nabla doesn't publish a clean self-serve price page, and organizations run through a sales conversation, so treat the free-cap and paid figures as third-party estimates. Patient Square has no per-note meter at any tier: unlimited visits and notes, from $79/mo.

Nabla's free tier is a good on-ramp. It's also capped, and it doesn't give you a chart, only a note. If you've outgrown the free plan or you want more than documentation, the alternative worth naming is an unlimited scribe that bundles a record system. Patient Square's scribe is unlimited from $79 per clinician per month on annual billing, with a bundled AI EHR from $119/mo at the Copilot tier. No per-note meter, ever. The full ladder is on our [pricing page](../../pricing/). Want to see a note draft first? Book a demo.

None of this is a Nabla knock. For a resident under the cap, the free plan is hard to beat. Below: where the free tier pinches, a side-by-side, and when Nabla is still the right call.

> **Key takeaways**
>
> - Nabla's free tier is capped at roughly 30 consultations a month per third-party sites; unlimited use moves you to a paid plan.
> - Nabla doesn't publish a clean self-serve price. Third-party estimates put the paid individual tier near $119/mo; enterprise is custom and sales-led.
> - Patient Square charges no per-note fee at any tier. Unlimited visits and notes from $79/mo, published.
> - Nabla is a scribe, not a record system. Patient Square's Copilot tier bundles an AI EHR from $119/mo, so the note lands in a chart.
> - If you fit inside Nabla's free tier and only want a note, keep it. That's an honest call, and we say so below.

## How does Nabla compare to Patient Square?

Here's the side-by-side. Nabla's paid figure is a third-party estimate, because Nabla doesn't publish a clean per-clinician price.

| | Nabla | Patient Square |
|---|---|---|
| Free tier | Yes, ~30 consults/mo (third-party estimate) | No free tier; 7-day trial |
| Note metering | Free tier is capped | Unlimited at every tier |
| Published paid price | No; ~$119/mo per third-party sites | Yes. $79 / $119 / $199 per clinician/mo, annual |
| Bundled EHR | No, integrates with yours | Yes, AI Copilot EHR from $119/mo |
| Clinical output | SOAP note, ambient capture | SOAP note, ICD-10 suggestions, Rx draft |
| Best fit | Light-volume clinicians under the cap | Practices that want unlimited notes plus a chart |

If your volume regularly clears a free-tier cap, book a demo and see what unlimited plus a bundled chart looks like on your own visits.

## Where does the free tier pinch?

Free tiers are a great way to try a scribe. They're a bad way to run a busy Tuesday. Third-party review sites describe Nabla's free plan as capped near 30 consultations a month, with unlimited use gated behind a paid tier. That works for a resident or a clinician doing a handful of encounters. For a family doctor seeing 24 patients a day, you'll hit the ceiling before lunch on the second day, and then you're either paying or rationing your own documentation.

The paid figure itself is fuzzy. Nabla doesn't publish a clean self-serve price page, and organizations run through a sales conversation. Third-party sites list an individual paid tier near $119 a month for unlimited consultations, with enterprise pricing custom. Treat that $119 as an outside estimate, not a Nabla-published number.

Patient Square has no meter to hit. Every tier is unlimited visits and notes, no per-note fee, starting at $79 per clinician per month on annual billing. You can read all three prices on the [pricing page](../../pricing/) without talking to anyone.

## What does Nabla not give you that a bundle does?

Nabla drafts the note. It doesn't hold the chart. It's an ambient scribe that integrates with your existing EHR, which is fine if you already have an EHR you like and only wanted documentation help.

The gap shows up when the note has nowhere good to go. You draft it in Nabla, then paste it into a record system you may also be paying for separately. Two tools, two bills, two vendors to chase when something breaks.

Patient Square's Copilot tier folds those together. The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. At the Copilot tier, a bundled AI Copilot EHR comes with it, so the note lands in a chart instead of your clipboard, all in one $119-a-month line. Audio is processed in memory and discarded once the note drafts, so no recording is kept.

If you're comparing more scribes, [DeepScribe alternatives](../deepscribe-alternatives/) covers the enterprise, sales-led end, and [Ambience Healthcare alternatives](../ambience-healthcare-alternatives/) looks at the health-system platform. If the Nabla vs Freed head-to-head is the specific question, [Nabla vs Freed](../nabla-vs-freed/) runs that comparison including the free-tier cap math on both sides.

## When is Nabla the better choice?

Be honest about volume and scope. If you're a resident, an intern, or a clinician doing light encounter counts that stay under a free-tier cap, Nabla's free plan is genuinely useful and cheaper than anything we sell, because it's free. If a note drafter is the entire job and you never clear the cap, you may not need to pay us or anyone.

Choose the bundle when the cap starts to bite or when the note is only half your problem. If your front desk is also underwater and your EHR fights you daily, a capped scribe leaves most of that untouched. One subscription that is the scribe, the chart, and the front office solves more of the actual mess.

## How to decide in a week

Run the real test, not the demo.

1. Count your monthly encounters. If you regularly clear a free-tier cap, the free plan is a trial, not a solution.
2. Decide whether you want a note or a note plus a chart. If it's both, shortlist tools that bundle an EHR.
3. Compare unlimited-note pricing, not free-tier headlines. A capped free plan and an unlimited paid plan are different products.
4. Ask each vendor the audio question: stored or not, and for how long. Ours is never stored.
5. Trial on a real clinic week, at your real volume, so the cap either bites or it doesn't.

The receipts behind our claims are on the [security page](../../security/), and the full price ladder with no fine print is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visits, then run the 7-day trial on a real week. If you live under Nabla's free cap and only want a note, keep it. If the cap pinches or the note needs a chart, the unlimited bundle is what you're actually shopping for.

---

## SOAPIE Note: Nursing Format, Example, Template
https://patientsquare.com/us/blog/soapie-note-nursing/
Published 2026-06-24 · Updated 2026-07-22 · Tags: nursing, clinical-documentation, soap-note

SOAPIE notes add Intervention and Evaluation to the SOAP format. Here is what each letter carries, a worked post-op nursing example, and a blank template.

SOAPIE stands for Subjective, Objective, Assessment, Plan, Intervention, and Evaluation. It is the SOAP note with two extra sections nurses add: Intervention records the actions you took, and Evaluation records how the patient responded. Those last two letters map directly to the implementation and evaluation steps of the nursing process.

A SOAPIE note is a nursing progress note with six sections: Subjective, Objective, Assessment, Plan, Intervention, and Evaluation. It's the SOAP note plus two letters. Intervention is what you did. Evaluation is how the patient responded. Those two additions are what turn a plan into a record of care that closed the loop.

If you trained on SOAP and your unit charts in SOAPIE, the gap is small but it matters. The first four letters are the same. The last two are the part of nursing the SOAP format leaves out: carrying out the plan and judging whether it worked. Below is what each section carries, a full worked example for a post-op patient, and a blank template you can keep.

> **Key takeaways**
>
> - SOAPIE = SOAP plus Intervention and Evaluation. Six sections, not four.
> - The two extra letters map to the last two steps of the nursing process: implementation and evaluation.
> - Intervention is the action you took. Evaluation is the patient's measured response to it.
> - The worked example below charts a post-op patient with uncontrolled pain, each section annotated.
> - No law requires SOAPIE. Your facility picks the format; many use it because it makes nursing reasoning legible.

## What is a SOAPIE note?

It's a structured nursing note that records a patient problem from what they reported all the way through to how they responded to your care. Six sections, in order.

**Subjective** is what the patient tells you. Their pain in their words, what they feel, what they're worried about. "It feels like a 9, worse when I move." Their voice, not your read of it.

**Objective** is what you measure and observe. Vital signs, the wound, intake and output, the grimace, the guarding. Numbers and observations a colleague could verify. Per StatPearls, this is the measurable, tangible data: vitals, exam findings, anything you can point to.

**Assessment** is your nursing judgment about what's going on. Not a medical diagnosis necessarily, but your conclusion: pain uncontrolled on the current regimen, risk for impaired mobility, anxiety contributing to the pain experience.

**Plan** is what you intend to do about it. The goal and the approach. "Reduce pain to 4 or below within an hour; reposition, medicate per order, reassess."

**Intervention** is what you actually did. This is the first new letter, and it's where SOAPIE departs from SOAP. You gave the medication at 1410. You repositioned. You raised the head of the bed. You called the provider. Actions, with times.

**Evaluation** is what happened next. The patient rates pain at 3 forty minutes later. Breathing eased. Or it didn't, and you escalated. This is the second new letter, and it's the one most drafts get thin. Evaluation is the proof the care worked, or the trigger to change course.

The base SOAP format, used widely across medicine, stops at the Plan. StatPearls notes that SOAP doesn't capture how a plan worked over time, which is why extension formats exist that add an explicit evaluation step. Nursing took that further and added two: the doing and the result.

## Why does nursing documentation add Intervention and Evaluation?

Because the nursing job doesn't end at the plan. It includes carrying the plan out and checking whether it helped. The note has to show that.

Look at the nursing process. StatPearls describes it as five sequential steps: assessment, diagnosis, planning, implementation, and evaluation. A SOAP note covers the front half of that. Subjective and Objective are assessment. Assessment is your diagnosis and reasoning. Plan is planning. Then SOAP stops, right at the point where nursing does most of its work.

The implementation step, per StatPearls, "involves action or doing and the actual carrying out of nursing interventions outlined in the plan of care." That's the I. The evaluation step is where you "reassess to ensure the desired outcome has been achieved," and "the plan of care may be adapted based on new assessment data." That's the E. SOAPIE exists so the note matches the process the nurse is already following.

There's a reason the order matters, too. The nursing process isn't a straight line. The Nursing Fundamentals text from Open RN calls it "a continuous, cyclic process that is constantly adapting to the patient's current health status." Your Evaluation isn't the end. A pain score still at 8 sends you back to a new Assessment, a revised Plan, another Intervention. SOAPIE charts one turn of that loop. The next note picks it up.

One opinion, since we've seen a lot of notes: the Evaluation section is where good charting separates from box-checking. Anyone can write "medication given." Whether the patient got better, and what you did when they didn't, is the part a chart review actually reads.

## SOAP vs SOAPIE: what each letter captures, and who uses it

Same first four letters. Two different jobs at the end. The side-by-side:

| Letter | SOAP | SOAPIE | What it captures | Who leans on it |
|---|---|---|---|---|
| **S (Subjective)** | Yes | Yes | What the patient reports, in their words | Both |
| **O (Objective)** | Yes | Yes | Vitals, exam findings, measurable data | Both |
| **A (Assessment)** | Yes | Yes | Clinical judgment about the problem | Both |
| **P (Plan)** | Yes | Yes | The intended next steps and goals | Both |
| **I (Intervention)** | No | Yes | The specific actions you carried out, with times | Nurses, who execute the plan |
| **E (Evaluation)** | No | Yes | The patient's measured response to the intervention | Nurses, who close the loop |

The split tracks the role. A physician's SOAP note ends at the Plan because, for the physician, the plan is often the order: prescribe this, refer there, follow up then. The carrying-out happens elsewhere. A nurse is frequently the one who carries it out, at the bedside, that shift, and then watches what happens. So the nurse's note keeps two more sections to record exactly that. Same patient, same encounter, a longer tail on the documentation because the work has a longer tail.

This is also why you'll see SOAP in a clinic progress note and SOAPIE on a med-surg floor. It's not that one is more rigorous. It's that they document different spans of the same care.

## A worked SOAPIE example for a post-op patient

Below is a full SOAPIE note for a routine scenario: a patient on a surgical floor the evening after an open appendectomy, reporting poorly controlled pain. This is an illustrative example written to show the shape. It is not a real patient record, and the medication details are generic for teaching, not a dosing recommendation.

---

**S (Subjective):** Patient reports incisional pain at the lower right abdomen, rated 8 out of 10, "sharp and worse when I take a deep breath or try to move." States the last dose of pain medication "didn't really touch it." Reports reluctance to cough or get out of bed because of the pain. Denies nausea. Asks whether "something stronger" is possible.

**O (Objective):** Post-op day 0, open appendectomy. Vital signs: HR 102, BP 138/86, RR 22 and shallow, temp 37.4 C, SpO2 95 percent on room air. Surgical dressing to RLQ clean, dry, intact. Patient guarding the abdomen, shallow breathing, grimacing with movement. Has not ambulated since returning from PACU. Last analgesic dose documented 3 hours ago.

**A (Assessment):** Acute post-operative pain inadequately controlled on the current regimen. Shallow, splinted breathing and refusal to mobilize raise the risk of atelectasis and delayed recovery. Pain is the primary barrier to deep breathing and early ambulation.

**P (Plan):** Goal: reduce reported pain to 4 out of 10 or lower within 60 minutes, and support deep breathing and first ambulation once pain is controlled. Administer analgesia per the provider's order set, reassess pain and respiratory status, reinforce incentive spirometry, and notify the provider if pain remains uncontrolled after intervention.

**I (Intervention):** At 2010, administered ordered analgesic per the post-op order set. Repositioned patient, raised the head of the bed, and gave a pillow to splint the incision for coughing. Coached on incentive spirometry and demonstrated splinted deep breathing. Encouraged slow position changes. Set a 40-minute reassessment. Pain pump and call light within reach.

**E (Evaluation):** At 2050, patient rates pain 3 out of 10 and describes it as "way more manageable." RR down to 16 and deeper; SpO2 97 percent on room air. Completed incentive spirometry to 1500 mL with splinting and tolerated sitting at the edge of the bed without a pain spike. Goal met. Plan to attempt short ambulation at the next check and continue scheduled analgesia. Will reassess pain before and after activity; escalate to provider if it climbs above 4 again.

---

Read the I and E sections back to back and you can see the point of the format. The Plan said "reduce pain to 4 or below and support breathing." The Intervention shows what was actually done and when. The Evaluation shows it worked, with numbers, and sets up the next move. A SOAP note would have ended at "administer analgesia, reassess" and left the rest to memory. The SOAPIE note carries the proof.

Notice what's in the Intervention that wasn't in the Plan: the exact time, the splinting pillow, the spirometry coaching. Plans are intentions. Interventions are the record of the shift. Keep them separate. If you find yourself copying the Plan into the Intervention word for word, you skipped the documentation that matters.

## A blank SOAPIE note template you can copy

Use this as a skeleton. Fill each section with the patient in front of you, keep Intervention in the past tense with times, and make Evaluation measure against the goal you set in the Plan.

```
SOAPIE NOTE

Date / Time:
Patient / Room:

S (Subjective)
  What the patient reports, in their own words.
  Pain rating, symptoms, concerns, relevant statements.

O (Objective)
  Vital signs:
  Observations / exam findings:
  Measurable data (intake/output, wound, labs available):

A (Assessment)
  Your nursing judgment about the problem.
  What the subjective and objective data add up to.

P (Plan)
  Goal (specific and measurable, with a timeframe):
  Intended actions to reach it:

I (Intervention)
  What you actually did, with times.
  Medications given, care provided, teaching, escalation.

E (Evaluation)
  Patient's response, measured against the goal.
  Did it work? Reassessment. Continue, change, or escalate.
```

Two habits make these notes hold up. First, write the Plan goal so the Evaluation has something concrete to check against. "Pain to 4 or below in an hour" is gradeable; "manage pain" isn't. Second, don't let Intervention drift into Plan or Evaluation drift into Assessment. The whole value of six sections is that each one answers a different question.

## Can an AI scribe write a SOAPIE note?

It can draft the SOAP part of one well. The line falls in a specific place, and you should know exactly where.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. That's a SOAP-structured note. We don't ship a SOAPIE template or any specialty-specific format, and we're not going to claim one we don't have.

Here's the honest framing, because the format question is a fair one. The same ambient-drafting idea applies to nursing documentation: capture the encounter, structure it, hand back a draft. What the scribe can draft from the conversation is the front of the note, the subjective and objective and your stated assessment and plan. The Intervention and Evaluation are the part you add, because they're the actions you took at the bedside and the patient's response you measured afterward, often minutes or hours later. That's nursing judgment and bedside work, not transcription. A tool that claimed to write your Evaluation for you would be making something up, which is the opposite of what documentation is for.

So the realistic fit is the drafting underneath the format, not a magic SOAPIE button. The ICD-10 codes are suggestions, not automated coding. The prescription piece is a draft only, built from what the clinician dictated; the clinician reviews the drugs, doses, and instructions and signs. It doesn't run an automated interaction or dosing check, and it never goes to a pharmacy on its own, so the safety call stays with the clinician, the same as it is today. The audio is processed in memory and discarded the moment the note is drafted, so there's no recording sitting in an archive. Notes are encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice to export or delete anytime. We maintain HIPAA compliant safeguards and offer a BAA to every customer; our SOC 2 Type II audit is underway. The full posture is on our [security page](../../security/).

For the format mechanics, our [mental-health SOAP note guide](../how-to-write-a-mental-health-soap-note/) goes deep on the four-letter version and a grading rubric, and the [SOAP note quality guide](../ai-scribe-soap-note-quality/) gives you a six-point scorecard for judging any AI draft against a real encounter, not a demo.

## Try it on a real shift's documentation

A template and a worked example only get you so far. The test is whether a draft holds up against your actual patients and your actual charting standard.

Review the [pricing page](../../pricing/), then run the 7-day free trial on your own visits and read every draft closely. The format you finish in is yours. What we can do is take the typing off the front of it.

---

## MocDoc Alternatives for Indian Clinics (2026)
https://patientsquare.com/in/blog/mocdoc-alternatives-india/
Published 2026-06-23 · Updated 2026-08-27 · Tags: alternatives, comparison, mocdoc, pricing

MocDoc is a broad cloud HMS suite, quote-only. If your real drain is documentation, Patient Square starts at ₹1,599/mo per doctor, published.

Running the whole operation. MocDoc is a cloud suite that spans hospital management, clinic management, a NABL-ready lab system (LIMS), pharmacy, dental, ophthalmology, and an ART module, and it says it's trusted by 1500+ institutions across 25+ states. If you need one system to run OP and IP billing, a lab, and a pharmacy counter together, that operational breadth is the reason to pick it.

If you're weighing MocDoc, start with an honest question: is your problem running the clinic, or writing the notes? MocDoc is a broad cloud suite. It runs hospital management, clinic management, a lab system, pharmacy, dental, and more, and it lists 1500+ institutions across 25+ states. That breadth is real, and quote-only. But if your actual daily drain is documentation, a suite that hands you fifteen modules is solving a problem you may not have. Patient Square does one thing and finishes it: an ambient AI scribe that writes your note during the visit, with a bundled AI EHR, scheduling, and messaging up the plan. It's published, from ₹1,599/mo per doctor, and the bundled EHR is ₹2,399/mo (ex-GST, add 18%, so about ₹1,887 and ₹2,831 all-in). You can book a demo and watch a SOAP note land in about two minutes.

This isn't a takedown. It's a breadth-versus-depth call. Below: what MocDoc genuinely covers, why its price is scoped not printed, where a clinic's real recurring cost actually sits, and when MocDoc is the smarter buy.

> **Bottom line**
>
> - MocDoc is a full operational suite: HMS, clinic management, LIMS, pharmacy, dental, ART. 1500+ institutions, 25+ states. Quote-only pricing.
> - Practice Copilot supports Patient Square EHR or an existing EHR, with ambient scribing and published pricing from ₹1,599/mo per doctor; it does not claim MocDoc's lab or pharmacy modules.
> - Many modules solve operations; a finished note solves the thing every clinic loses hours to. Different problems.
> - Need a lab or pharmacy run inside the software? MocDoc. Buried in charting after clinic? Patient Square.

## MocDoc vs Patient Square: match the problem, not the feature count

MocDoc is an operational suite; Practice Copilot is an AI clinical platform with two record-system paths. Read the row that matches your pain.

| | MocDoc | Patient Square |
|---|---|---|
| Built for | Clinics, hospitals, labs, pharmacies running full operations | Clinics buried in documentation (Practice Copilot) |
| Scope | Full suite: HMS, LIMS, pharmacy, dental, ART, ophthalmology | Patient Square EHR or existing-EHR path, ambient scribe, scheduling, messaging |
| Ambient AI scribe | Not the core | Yes, note ready about 2 min after the visit |
| ICD-10 | Not the pitch | Suggestions in the note (not a coding engine) |
| Prescription | Pharmacy billing module | Draft Rx in the note (not transmitted to a pharmacy) |
| Languages | Indian-market localized | Input in Hindi, Hinglish, 20+ Indian languages. Output always clean English |
| Lab / pharmacy modules | Yes, LIMS + pharmacy | No, not a LIMS or pharmacy suite |
| Pricing | Quote-only, scoped to modules and scale | Published: ₹1,599/mo entry, ₹2,399/mo with bundled EHR (+GST) |
| Implementation | Suite rollout, module by module | None for a clinic. Trial in a day |

If you need a lab counter and a pharmacy running inside one system, keep reading the MocDoc case. If you just need your notes done, skip to the documentation section.

## What MocDoc actually covers

Give it full credit. MocDoc is a genuinely broad cloud platform. Its product line spans a Hospital Management System with EMR and OP/IP billing, a Clinic Management System with prescriptions and appointments, a NABL-ready Lab Information Management System with barcode and sample tracking, a Pharmacy Management module with stock and expiry alerts, plus Dental, Ophthalmology, and an ART (assisted reproduction) module. It runs 100% cloud on Indian hosting with AES-256 encryption, and it states adoption of 1500+ institutions across 25+ states.

That's a serious operational suite. A multi-department clinic, a small hospital, or a diagnostic lab that needs sample tracking, analyzer integration, GST-ready billing, and a pharmacy counter all under one login should absolutely have MocDoc on the shortlist. Nothing here argues against that.

The mismatch shows up when a solo doctor or a two-doctor clinic lands on a suite like this and starts scoping a LIMS, an ART module, and a pharmacy inventory system it will never switch on. If that's you, the breadth isn't a feature, it's overhead you pay for and don't use. In that case, [see the documentation-first alternative in a demo](https://patientsquare.com/in/) before you scope a full suite.

## What does MocDoc cost, and why isn't it on the page?

MocDoc doesn't publish a price. The site routes you to a Book a Demo form, and pricing comes back scoped to your beds, module mix, lab and pharmacy setup, and rollout. That's normal for an operational suite, cost genuinely tracks how many modules you switch on and how big the site is.

Third-party listings float annual estimates, roughly from ₹60,000 up past ₹3,00,000 depending on scale, but those are unofficial and one analysis flags extra line items like customization fees and add-ons for things such as video consultation. Treat any number you see off-site as an estimate, not MocDoc's own quote. The honest takeaway isn't the figure, it's the shape: you find out your price after a sales and scoping conversation, not at a checkout.

Patient Square prices the other way. Practice Copilot is per doctor and printed: Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo, all ex-GST, add 18%, on the [pricing page](https://patientsquare.com/in/pricing/). A solo doctor knows the number before anyone picks up the phone. For a clinic solving a documentation problem, that pricing clarity matters more than a fifteen-module catalogue.

## Where a clinic's real recurring cost sits

A full suite runs your operation. It does nothing for the one cost almost every clinic carries and rarely puts a number on: the time lost to writing records.

Picture a Coimbatore clinic on a 40-patient day. Consultations in India run short, often just a couple of minutes each, so the record is the first thing that gets squeezed. The doctor scribbles a line, means to fill it in later, and later becomes 9pm. A thin note is cheap to write and expensive to defend. NMC conduct rules expect outpatient records kept and produced on request, and when a complaint lands, the note that holds up is the complete one written at the time of the visit. No lab module or pharmacy counter fixes a doctor charting after dinner. A scribe that finishes the note inside the consult does.

That's the whole point of Patient Square. Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens as you consult, in Hindi, Tamil, Hinglish, and 20+ Indian languages, even when you code-mix, and returns a clean English note. ICD-10 comes as suggestions, not a coding engine, and the prescription is a draft you check, not something transmitted to a pharmacy. Audio is never stored, and capture works offline with encryption when your connection drops. Book a demo and run it on a real OPD block. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## What every Patient Square plan includes

Every Practice Copilot plan carries unlimited visits and notes with no per-note metering, so a heavy OPD day never costs extra. Notes export EHR-ready as PDF, HL7, or FHIR, which is an export format, not a claim of certified interoperability. Specialty-aware templates are ready out of the box, and you can capture on web or mobile.

On compliance, plain facts. Patient Square is handled to DPDP Act 2023 standards, with a SOC 2 Type II audit in progress, not certified yet. ABDM is on the roadmap, not live, so records are born digital and ready for the ABHA-linked era on your timeline. If any vendor tells you it's live, certified ABDM today, ask for the NHA certificate. There's a 7-day free trial, so you can test note quality on your own visits before you commit.

What Patient Square deliberately isn't: a LIMS, a pharmacy or inventory system, or a full hospital operations platform. If those are on your must-have list, that's a MocDoc job, and we won't pretend to match its module count.

## When MocDoc is the better choice

Pick MocDoc when you need its sample tracking, analyser integration, stock and expiry control, GST-ready billing, and OP/IP workflows. Practice Copilot and Hospital Copilot support their approved record-system paths, but neither claim turns the ambient scribe module into MocDoc's LIMS or pharmacy suite.

Pick Patient Square when the pain is documentation. Practice Copilot can use Patient Square EHR or work alongside an existing EHR at published per-doctor pricing. Plenty of practices retain a specialist operational system for billing or inventory while the ambient scribe drafts notes during the visit.

## How to decide this week

Skip the feature-count comparison and run the test:

1. Name the problem. Running a lab, pharmacy, or multi-department operation points to a suite. Losing hours to notes points to a scribe.
2. If you need operations, scope MocDoc across the modules you'll actually switch on, and get the quote in writing including customization and add-ons.
3. If you need documentation, shortlist per-doctor tools with published pricing and no rollout project.
4. Match the clinical output like for like: a structured note, ICD-10 suggestions, and a checked prescription draft.
5. Trial on real visits in your own languages, Hindi or Tamil in, clean English note out, and settle the data question: hosting, ownership, and true ABDM status.

The clinic per-doctor ladder sits on the [pricing page](https://patientsquare.com/in/pricing), and you can book a short demo to check note quality against your own visit type. If you need a suite to run the operation, MocDoc earns the look. If you need your notes finished during the visit, you're in the right place. Weighing other Indian systems too? The [Halemind comparison](https://patientsquare.com/in/blog/halemind-alternatives-india), the [DocPulse comparison](https://patientsquare.com/in/blog/docpulse-alternatives-india), and the [Crelio Health comparison](https://patientsquare.com/in/blog/crelio-health-alternatives-india) run the same segment test.

---

## Nabla vs Freed: Free Tiers, Caps, and the Upgrade Math
https://patientsquare.com/us/blog/nabla-vs-freed/
Published 2026-06-23 · Tags: ai-scribe, comparison, nabla, freed

Nabla caps its free plan at 30 consults/mo; Freed's Starter caps at 40 notes. Compare the free tiers, the paid unlimited step, and a bundled-EHR option at $119/mo.

Nabla runs a permanent free tier capped at 30 consultations a month. Freed's cheapest plan, Starter at $39 a month, caps at 40 notes; its actual free offering is a 7-day trial, not an ongoing free plan. So Nabla is the one with a lasting free tier, but both cap volume at the low end, and a full-time clinic blows past 30 or 40 in the first week or two.

Nabla and Freed are the two scribes most people search when they want a free or cheap option. Both put a low ceiling on the free end: Nabla caps its free tier at 30 consultations a month, Freed's cheapest paid plan caps at 40 notes. A full-time clinic clears either in a week or two, so you're really choosing between paid unlimited plans, and there they're close: $79 to $119 a month. If you also want the chart, not just the note, there's a bundled-EHR option at $119 that ends the two-subscription problem. You can book a demo and see a finished note first.

Here's the free-tier reality, the upgrade math, and where the third option fits.

> **Key takeaways**
>
> - Nabla runs a permanent free tier capped at 30 consults/mo. Freed's "free" is a 7-day trial; its cheapest paid plan (Starter, $39) caps at 40 notes.
> - Unlimited use: Nabla Pro $119/mo; Freed Core $79/mo (monthly only) or Premier $104 annual/$119 monthly.
> - Both cap volume at the low end. A high-volume clinic outgrows the free tiers fast.
> - Neither ships an EHR. Both write into your existing chart.
> - A bundled-EHR scribe at $119/mo annual is the option when you want note plus chart in one subscription.

| | Nabla | Freed | Patient Square |
|---|---|---|---|
| Permanent free tier | Yes (30 consults/mo) | No (7-day trial) | No (7-day trial) |
| Cheapest paid | Pro $119/mo | Starter $39/mo (40 notes) | Assist $79/mo |
| Unlimited plan | Pro $119/mo | Core $79/mo | Assist $79/mo (all plans) |
| Bundled EHR | No | No | Yes (Copilot, $119/mo annual) |
| Trainee free use | Unlimited for interns/residents | No | No |

Figures from each vendor's pricing page (July 2026). Confirm current caps at signup; free-tier limits change often.

## Nabla vs Freed: the free-tier reality

The free tier is why people compare these two, so start there and be honest about it. Nabla's free plan gives you 30 consultations a month, plus EHR integration, and it throws in unlimited consultations for interns and residents, which is a genuinely nice touch for a teaching clinic. Freed doesn't have a permanent free plan at all; its "free" is a 7-day trial, after which the cheapest option is Starter at $39 a month, capped at 40 notes.

So on paper Nabla is the free-tier winner. But look at the caps against a real week. Thirty consults is a day and a half for a busy primary-care doc. Forty notes on Freed's Starter is about two days. Neither survives a full-time schedule; they're built for light use, trainees, or a trial period dressed up as a plan. That's not a criticism, it's just what "free" means here, and it's worth knowing before you build a workflow on it.

If your volume is low or you're testing the water, the free tiers are a real gift. If you're documenting 20-plus patients a day, you're shopping for the unlimited plan, and you should price that from the start. You can also book a demo to see how an unlimited bundled option compares before you commit to either.

## The upgrade math: what unlimited actually costs

Once you outgrow the cap, here's the real comparison. Nabla's Pro tier is $119 a month for unlimited consultations. Freed's unlimited path is Core at $79 a month, though Core is monthly billing only, or Premier at $104 on annual billing ($119 monthly), which adds EHR push and ICD-10 and CPT codes. Both publish these numbers, per their pricing pages (July 2026), and published pricing is the thing to reward here.

The lesson in the math: the free tier is marketing; the unlimited tier is the actual product for a working clinic. Freed's Core is the cheapest published unlimited plan at $79. Nabla's Pro matches Premier at $119. So the paid step, not the free tier, is where your real annual cost gets set.

Patient Square prices every plan as unlimited from the entry tier: $79 for Assist, $119 for Copilot, $199 for Autopilot, per clinician on annual billing, no per-note metering at any level, on the [pricing page](/us/pricing/). There's no cap to outgrow because there's no cap. For the full self-serve field, our [best AI medical scribes](/us/blog/best-ai-medical-scribes/) roundup is the honest map.

## Do Nabla or Freed include an EHR? Neither does

This is the gap that decides it for a lot of buyers. Neither Nabla nor Freed ships a record system. Nabla integrates with your EHR on paid tiers; Freed's Premier pushes the note into your chart via a browser extension. In both cases the chart is a separate product you own and pay for on its own.

For a practice that's happy with its EHR, that's fine, bolt the scribe on. But if you landed here because both your documentation and your chart are painful, you're shopping for two things and these tools each solve one. Free scribe plus paid EHR still leaves you with two logins, two bills, and a copy step between them.

Patient Square's Copilot plan puts both in one place. The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. At the Copilot tier ($119/mo annual) that scribe ships with a bundled AI Copilot EHR, so the note lands where you already work. If your gap is note plus chart, book a demo and see them together.

To keep it honest on scope: our eRx is a draft you review and sign, not pharmacy transmission, and ICD-10 is suggestions, not a certified coding engine. If coding or e-prescribing depth is central to your buy, check it against all three on the demo.

## Which wins for a high-volume clinic

If you run a high-volume schedule, the free tiers are off the table before you start, so ignore them. You're comparing Nabla Pro at $119, Freed Core at $79 or Premier at $119, and a bundled option at $119. Price is close enough that it shouldn't be the tiebreaker.

The real tiebreaker is two things: is every plan truly unlimited with no hidden per-note metering, and do you also want the chart bundled. Confirm the first with each vendor directly. For the second, the answer depends on whether your EHR is part of the problem you're trying to fix. A high-volume clinic that's fighting its chart as much as its notes is exactly who a bundled tool is built for. If you want the enterprise end of the market instead, [Abridge alternatives](/us/blog/abridge-alternatives/) covers that. If you want to look at Nabla's alternatives field beyond Freed, [Nabla alternatives](/us/blog/nabla-alternatives/) covers the full comparison.

## When Nabla or Freed is the better choice

Pick Nabla if a lasting free tier matters to you: light-use clinicians, a teaching practice with residents (they get unlimited free), or a careful trial before paying. The 30-consult cap is real, but the free plan is genuinely free, and that's Nabla's edge.

Pick Freed if you want the cheapest published unlimited plan, $79 Core, and you already have an EHR you're keeping. It's a focused, well-priced scribe for the independent who just needs clean notes.

Pick a bundled-EHR scribe if your gap is the note and the chart together and you'd rather run one subscription than stack two. That's the case neither Nabla nor Freed is built for. Note quality is close across all three; decide on free-tier needs, unlimited price, and whether the chart is part of your buy.

## How to decide in a week

1. Estimate your monthly volume honestly. Over 30–40 encounters means the free tiers don't apply; price the unlimited plans from the start.
2. Start the free trials or free tiers today and run them on real visits, not a scripted demo.
3. Match the clinical output: a note plus ICD-10 suggestions plus a checked prescription draft, so you compare like for like.
4. Confirm "unlimited" means unlimited with every vendor, and settle the audio question: stored or not, and for how long. Ours is never stored.
5. Decide if the chart is part of your buy. If it is, put the bundled option on your list.

The receipts behind our claims are on the [security page](/us/security/), and the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to see the note against your own visit type, then run the 7-day trial on a real clinic week. If your volume is real and your chart is part of the problem, a capped free tier was never going to be the answer.

---

## Suvarna Alternatives for Indian Clinics & Hospitals (2026)
https://patientsquare.com/in/blog/suvarna-alternatives-india/
Published 2026-06-23 · Updated 2026-08-27 · Tags: alternatives, comparison, pricing

Suvarna is enterprise HIS for large hospitals, quote-only. Clean segment split: hospitals to Hospital Copilot, clinics to Practice Copilot from ₹1,599/mo per doctor.

Enterprise hospital scale. Suvarna HIMS is a mature hospital information system used by 300-plus hospitals, with modules across admissions-to-discharge, LIS, blood bank, OT management, nursing, multi-site enterprise, and billing. If you run a large or multi-site hospital that needs deep, accredited HIS plumbing, Suvarna's 25 years of depth is the reason to choose it.

If you're looking at Suvarna, the first question is which building you're in. Suvarna HIMS is enterprise hospital software, deep HIS plumbing for large, multi-site hospitals, quote-only, built over 25 years. If you run a hospital, that depth is real and worth scoping. If you run a clinic, it's almost certainly oversized, and your actual pain is documentation, not admissions-to-discharge machinery. Patient Square splits cleanly: hospitals look at Hospital Copilot (demo-priced), clinics run Practice Copilot from ₹1,599/mo per doctor, with the AI Copilot EHR bundled at ₹2,399/mo (ex-GST, add 18%). You can book a demo and see a SOAP note land in about two minutes.

Not a takedown, a segment question. Below: what Suvarna is genuinely built for, why the price is scoped not published, where a clinic's real cost sits, and when Suvarna is the right call.

> **Bottom line**
>
> - Suvarna is enterprise HIS for large/multi-site hospitals: 300+ hospitals, blood bank, OT, LIS, nursing, multi-site billing. Quote-only.
> - Patient Square splits by segment: Hospital Copilot for hospitals (demo-priced), Practice Copilot for clinics (₹1,599/mo entry).
> - A clinic buying enterprise HIS is buying hospital plumbing it won't run. A hospital buying a clinic scribe is under-scoped.
> - If deep enterprise HIS is the need, Suvarna wins. If documentation is the need, Patient Square fits either segment.

## Suvarna vs Patient Square: match your segment first

The right pick depends on your building: hospital or clinic. Read the row that fits.

| | Suvarna HIMS | Patient Square |
|---|---|---|
| Built for | Large / multi-site hospitals | Clinics (Practice Copilot) + hospitals (Hospital Copilot) |
| Scope | Full enterprise HIS: admissions, OT, blood bank, LIS, nursing, multi-site | Documentation-first + bundled AI EHR |
| Adoption | 300+ hospitals | Clinic + hospital products |
| Pricing | Quote-only, scoped | Clinics: published per doctor. Hospitals: demo-priced |
| Clinic entry price | Oversized for a clinic | ₹1,599/mo + GST (Assist) |
| Bundled EHR (clinic) | n/a | ₹2,399/mo + GST (Copilot tier) |
| Ambient AI scribe | Not the core | Yes, Hindi + 20+ languages, English output |
| Implementation | Enterprise rollout | Clinics: none. Hospitals: scoped |

Hospital with deep HIS needs, keep reading the Suvarna case. Clinic buried in notes, skip to the documentation section.

## What Suvarna is genuinely built for

Full credit. Suvarna Technosoft has spent about 25 years building enterprise HIMS and EMR, and it shows. The system spans the whole hospital: rules-based OPD and daycare workflows, admissions-to-discharge management, real-time bed board, nursing management, ordering and clinical documentation across inpatient units, a laboratory information system, blood bank, operation-theatre management, diagnostics, billing with payment-gateway integration, and multi-site enterprise support. More than 300 hospitals of varying sizes run it, and it carries NABH-relevant accreditation framing.

That's a serious enterprise platform for serious hospital operations. A large or multi-site hospital standing up or replacing its HIS should have Suvarna on the shortlist. Nothing below argues against that.

The mismatch happens when a clinic lands on Suvarna via a generic "hospital software India" search and starts scoping modules it will never run, no clinic has an operation theatre or a blood bank. If that's you, [see the clinic-scoped alternative in a demo](https://patientsquare.com/in/) instead of scoping a hospital system.

## What does Suvarna cost, and why isn't it published?

Suvarna doesn't put a price on the page. HIMS pricing is quote-only, gated behind an enquiry and demo form, because enterprise HIS cost genuinely tracks hospital size, module mix, number of sites, and implementation scope. That's the honest reason: you can't price a 400-bed multi-site rollout off a rate card.

But it also tells you what buying feels like: a scoping and procurement cycle, not a checkout. For a hospital, that's expected and fine. For a clinic, it's a mismatch, you'd be entering an enterprise sales process to solve a documentation problem a per-doctor tool handles in an afternoon.

Patient Square matches the price model to the segment. Clinics get published per-doctor pricing: Assist ₹1,599/mo annual, Copilot ₹2,399/mo (adds the bundled AI Copilot EHR and WhatsApp messaging), Autopilot ₹3,999/mo, all ex-GST, add 18%, on the [pricing page](https://patientsquare.com/in/pricing). Hospitals get Hospital Copilot on a demo-priced conversation, because hospital scope, like Suvarna's, genuinely needs scoping. Right price model for the right building.

## Where a clinic's real recurring cost sits

Enterprise HIS is built to run a hospital. It does nothing extra for the one cost every clinic carries and rarely prices: time lost to documentation.

Indian consultations average about two minutes, per a 67-country BMJ Open study, among the shortest anywhere. In that window the record is what gets shortchanged, and a thin record is expensive later. Around 65,000 medical-negligence matters reach Indian courts and consumer forums a year, and the defence that holds is a complete contemporaneous note. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A hospital HIS doesn't fix a solo doctor's 9pm charting. A scribe that finishes the note during the visit does.

That's what Patient Square is built for. Canonically: Practice Copilot brings the whole practice under one AI copilot, an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The scribe listens as you consult, in Hindi, Kannada, Bengali, and 20+ Indian languages, even code-mixed, and returns a clean English note. Book a demo and run it on a real OPD. For a full breakdown of what enterprise HMS pricing really covers and what a clinic doesn't need to pay for, [HMS software cost in India](/in/blog/hms-software-cost-breakdown-india/) decodes the quote structure line by line.

## What the hospital segment should know

If you run a hospital, Hospital Copilot offers two deployment paths and is demo-priced. The complete Patient Square HIS/EHR can be the record system, or Patient Square can work alongside Suvarna as the incumbent HIS/EHR. The complete path does not imply Suvarna's blood-bank, OT, LIS, nursing, or multi-site depth; verify every required module during discovery.

An established hospital may sensibly keep Suvarna as the system of record and run Hospital Copilot alongside it. A greenfield hospital can instead evaluate the complete Patient Square HIS/EHR. Talk to us about both paths and keep the Suvarna module comparison explicit.

On compliance, the same honesty applies across both products: handled to DPDP Act 2023 standards, SOC 2 Type II audit in progress (not certified), ABDM integration on the roadmap, not live. Records born digital, ready for the ABHA-linked era on your timeline. If a vendor claims live, certified ABDM, ask for the NHA certificate.

## When Suvarna is the better choice

Choose Suvarna if you're a hospital that needs deep enterprise HIS. Large or multi-site, running OT, blood bank, LIS, nursing, and admissions-to-discharge across sites, with billing and accreditation depth, is exactly what Suvarna is built for and priced to scope. A documentation-first tool isn't competing with that; it's a layer, not a replacement. Trying to run hospital operations off a clinic scribe would leave you missing the core HIS machinery Suvarna exists to provide.

Choose Patient Square if its verified scope fits. A clinic can use Patient Square EHR or an existing EHR through Practice Copilot. A hospital can use the complete Patient Square HIS/EHR or keep Suvarna through Hospital Copilot's alongside path. Either way, the ambient workflow finishes the draft while the patient is still in the room.

## How to decide this week

Cut the enterprise-deck comparison and run the test:

1. Name your building. Hospital with OT, beds, and blood bank, you need enterprise HIS. Clinic, you almost certainly don't.
2. If you're a clinic, shortlist per-doctor documentation tools with published pricing and no implementation project.
3. If you're a hospital, decide whether the pain is core HIS operations (scope Suvarna) or documentation at scale (talk to us about Hospital Copilot).
4. Match the clinical output: a structured note, ICD-10 suggestions, and a checked prescription draft, like for like.
5. Trial on real visits in your own languages, Hindi or Kannada in, clean English note out, and settle the data question: hosting, ownership, true ABDM status.

The security details, encryption, access, audit status, sit on our security page, and the clinic per-doctor ladder is on the [pricing page](https://patientsquare.com/in/pricing). Book a short demo to check note quality against your own visit type. If you need enterprise HIS, Suvarna earns the look. If you need your notes done, you're in the right place, whichever segment you're in.

---

## What Is a Medical Scribe? Human, Virtual, and AI
https://patientsquare.com/us/blog/what-is-a-medical-scribe/
Published 2026-06-23 · Updated 2026-08-27 · Tags: medical-scribe, basics, ai-scribe

A medical scribe documents the visit so the clinician can focus on the patient. Here are the three kinds, in-person, remote, and AI, and how they differ.

A medical scribe documents the clinical visit so the clinician doesn't have to. The scribe records the history, exam findings, assessment, and plan in real time while the clinician sees the patient. The scribe can be a person in the room, a person off-site on a call, or software that listens and drafts the note.

A medical scribe documents the clinical visit so the clinician doesn't have to. The scribe captures the history, exam, assessment, and plan in real time while the doctor sees the patient, then the doctor reviews and signs. A scribe can be a person in the room, a person off-site on a call, or software that listens and drafts the note.

That's the role in one sentence. The interesting part is that "medical scribe" now covers three very different things, and they don't cost the same, don't carry the same privacy footprint, and don't scale the same way. This page sorts them out.

> **Key takeaways**
>
> - A medical scribe handles the documentation so the clinician can stay with the patient. The clinician still reviews and signs every note.
> - There are three kinds today: an in-person human scribe, a remote (virtual) human scribe, and an ambient AI scribe.
> - The two human options put a salary on your books and a second person in the visit. Most are pre-med or pre-PA students passing through.
> - US physicians log a median of 36.2 minutes of EHR time per primary-care visit (JAMA Network Open, 2023). That's the burden every scribe type exists to cut.

## What does a medical scribe actually do?

A scribe writes down the visit. That's the whole job, and it's a bigger job than it sounds.

The American Association of Medical Colleges puts it plainly: a scribe "helps physicians provide more effective and efficient care by saving them time by documenting findings from patient exams and assessments." In practice that means the chief complaint, the history, what the exam showed, the results you talked through, your assessment, and the plan, all captured while the visit happens. One scribe profiled by the AAMC "transcribed hundreds of physician-patient encounters, medical histories, and diagnostic test results" in an ENT clinic.

The point of all that is simple. When someone else is typing, you can look at the patient. You can think instead of chart. The note gets written at the speed of the conversation rather than waiting for you at 9pm.

One thing a scribe is not: the author of the record. The scribe drafts. You read it, fix it, and sign it. Whether the scribe is a person or a piece of software, the documentation responsibility stays with the clinician who signs. That doesn't move.

## Scribe versus transcriptionist: what's the difference?

People mix these up, and they're not the same job.

A transcriptionist works from your dictation. You finish the visit, you narrate what happened, and they type that narration into text. The visit gets documented twice: once when you live it, again when you describe it. A scribe skips the second pass by capturing the visit itself, structuring the note as the encounter unfolds.

So the test is timing. A transcriptionist turns your words about the visit into text afterward. A scribe turns the visit into a note while it's happening. An ambient AI scribe does the live, structuring job too, just without a person. If you want the difference between live capture and after-the-fact dictation laid out in full, our [ambient AI versus dictation](../ambient-ai-vs-dictation/) breakdown covers it.

## What are the three kinds of medical scribe?

Here's where the word splits. The same job, three delivery models.

**The in-person human scribe.** A trained person, usually hired through a scribe staffing company, stands in the exam room with you and types as you work. The AAMC's profile describes a scribe working "closely alongside" the physician, "typically work[ing] with a single physician on a given day," learning each provider's charting habits. Most of these scribes are pre-med, pre-PA, or pre-NP students earning clinical hours before professional school. Pay runs roughly $12 to $20 an hour. It's the oldest model and the most flexible, because a person can do more than document.

**The remote (virtual) human scribe.** Same idea, but the person is off-site. They join the visit over a secure audio or video link and document in real time. ScribeAmerica, one of the larger vendors, connects its virtual scribes "via a tablet on a stand, mobile cart, or a phone," and the scribe "documents [the] encounter directly into [the] EHR using their own account in real-time." You get a live human without a third body in the room. The trade-off: a stranger is listening to the whole visit, which makes the Business Associate Agreement and the encryption their own thing to vet.

**The ambient AI scribe.** Software, not a person. It listens to the visit, transcribes it, and drafts the structured note itself, then hands it back for you to review and sign. Nobody else hears the conversation. We won't re-explain the step-by-step here, because we already wrote that page: [how an AI medical scribe works](../what-is-an-ai-medical-scribe/) walks through capture, transcription, structuring, and review in detail.

## The three scribe types, side by side

This is the table worth keeping. Same documentation job, very different shape.

| | In-person human scribe | Remote (virtual) human scribe | Ambient AI scribe |
|---|---|---|---|
| **Who does the work** | A person in the exam room | A person off-site, on audio or video | Software, during the visit |
| **Cost shape** | A salary, scaling per clinician (a US scribe averages near $41k/yr) | A salary or per-hour contract, usually below an in-room hire | A per-clinician subscription, no hiring |
| **Patient privacy footprint** | A third person physically in the room | A third person listening remotely, under a BAA | No extra person; audio handling depends on the vendor |
| **Scales to a group practice** | Linearly and painfully; one hire per clinician | Linearly, but easier to staff than in-room | Per seat, flat, no recruiting |
| **Main trade-off** | Most expensive; high turnover; a stranger in the room | Privacy of a remote listener; depends on the vendor's security | Drafts only; you must read every note before signing |

A note on the cost cells: we've kept them to the shape, not the full math, on purpose. If you want the staffing economics in detail, salary, benefits, turnover, the per-note breakdown, that's its own page: [AI scribe versus human scribe cost](../ai-scribe-vs-human-scribe-cost/).

## Why do human scribes turn over so often?

Because for most of the people doing it, scribing isn't the career. It's the on-ramp.

The workforce is largely pre-med and pre-PA students collecting clinical hours before they apply to school. The AAMC features exactly that path. So a practice doesn't hire a scribe once and keep them for a decade. You hire, you train for a few weeks while they shadow, you get a productive stretch, and then they leave for medical school. ProScribe, a national scribe company, says the average length of employment with them is 16 to 18 months. That's one vendor's number, not a law of nature, but the pattern holds across the field: the staff is transient by design.

The scale of that churn is easy to underestimate. ScribeAmerica, the largest US scribe company, says it currently employs more than 15,000 scribes across 3,500-plus healthcare facilities in all 50 states, and that it has hired and trained over 100,000 scribes across its history. Read those two numbers together and the model comes into focus: a standing workforce in the low tens of thousands, and a lifetime headcount six times larger, because the people cycle through. Every one of those seats is a hire, a training block, and eventually a goodbye. A subscription is none of those things.

That churn is the quiet tax on the human model. The salary line is visible. The recruiting and re-training cycle that comes around every year or two is the part nobody puts on the invoice. It's also the part software doesn't have: a subscription doesn't graduate and move to Ohio.

## The documentation burden a scribe is fighting

It's big enough that the whole category exists to fix it.

In a 2023 JAMA Network Open study, primary-care physicians logged a median of 36.2 minutes of EHR time for every visit, with a quarter of doctors above 45 minutes. The study also measured "pajama time," the EHR work that spills into evenings and weekends, at 6.2 minutes per visit. Stack that across a full clinic day and you get the after-hours charting that scribes, in every form, are meant to claw back.

Whichever scribe you choose, the goal is the same: get that time back so the note stops outliving the appointment that created it. Our [reduce charting time](../reduce-charting-time-clinicians/) guide gets into the specifics for clinicians weighing the options.

## Where AI Medical Scribe by Patient Square fits

It's the AI option in that table, built so the only person in the visit is you.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. No second person in the room, no off-site listener on a call. The prescription is a draft built from the plan you stated; you review the drugs, doses, and instructions and sign. It doesn't run an automated interaction check, and it never goes to a pharmacy on its own. The safety check is you, the same as when you write the script yourself.

On privacy, the footprint is the smallest of the three: visit audio is processed in memory and discarded the moment the note is drafted, so there's no recording and no human transcriber who heard the conversation. Notes are encrypted in transit and at rest, they belong to your practice, and you can export or delete any visit anytime. For US practices the floor is a signed BAA, which we offer every customer, with HIPAA-compliant safeguards and a SOC 2 Type II audit underway. The receipts live on our [security page](../../security/).

On cost, it's a per-clinician subscription, not a salary: the Assist plan starts from $79 per clinician per month on annual billing in the US, with a 7-day free trial, and moving up to Copilot bundles an AI EHR and messaging. The full ladder, with no asterisks, is on the [pricing page](../../pricing/), and we break down what drives the number in [AI medical scribe pricing](../ai-medical-scribe-pricing/).

## When is a human scribe still the better fit?

Honest answer: more often than a software pitch will admit. Here's the verdict, no hedging.

Keep a human scribe, in the room or remote, when you need a person who does more than write the note. A scribe who can take a verbal order to staff, chase a pending result, queue the next patient, or handle the unscripted parts of a visit is doing a job no AI touches. If "scribe" in your clinic really means "flexible clinical assistant," software replaces one slice of that role, not the whole thing. And a teaching practice that wants to give pre-med students real clinical hours has a second, legitimate reason to keep humans on: the turnover you'd otherwise grumble about is the entire point of the arrangement.

Go with the AI scribe when the job is the note. If your scribe's day is mostly typing the visit into the chart, you're paying salary-and-turnover for documentation that software now drafts in about two minutes, with no second person hearing the visit. That describes a lot of practices, honestly. Many of them hired scribes for one reason only: to stop charting at midnight.

So it comes down to scope. A human can do more than document. An AI does the documentation far cheaper and never leaves for medical school. Want to see the AI version against your own visit type? <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and run the 7-day trial on a real clinic week before you decide.

---

## Clinic Copilot Software in India: What Ships Today
https://patientsquare.com/in/blog/clinic-copilot-software-india/
Published 2026-06-22 · Updated 2026-07-22 · Tags: clinic-copilot, practice-copilot, clinic-software, india

Clinic copilot software assists doctors during and after visits. See what the category covers and what Patient Square currently ships in India.

Clinic copilot software is the emerging category name for AI tools that assist a doctor during and after a consultation, handling cognitive work like documentation, ICD code suggestions, and prescription drafting. The term borrows from aviation, where a copilot shares the operational load. Applied to a clinic, it covers any tool that monitors, assists, and offloads without the doctor having to operate it directly. The most mature technology in the category today is the ambient AI medical scribe.

Every clinic in India already runs on some mix of paper, WhatsApp, and the doctor's memory. The question is not whether software helps. It is which layer of software you actually need.

"Clinic copilot software" is the label settling onto a new category: tools that ride alongside a doctor during and after a consultation, taking on the cognitive overhead that currently falls on the clinician. Not just the record. Not just the appointment book. The active assistant layer.

Patient Square calls itself "Practice Copilot" for exactly that reason. What it ships today is an ambient AI medical scribe. It listens during the consultation, doctor and patient, in any language, and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the visit ends. No typing during the consult. No charting session after the last patient. The draft goes back to you for review and sign-off; nothing moves without your approval.

That documentation layer is the core of what Practice Copilot does, and it is the most time-intensive part of clinic work for most solo and small-clinic doctors. The plans build outward from there: scheduling is included from the entry Assist plan, the Copilot plan bundles an AI EHR and WhatsApp messaging, and the Autopilot plan adds an AI receptionist and automated follow-ups. Insurance billing automation is not part of the solo plans today.

A 2017 BMJ Open study across 67 countries found average primary-care consultation times of roughly two minutes in India. Two minutes is not enough to take a good history, examine, prescribe, and write a legible note. Something gets cut. Usually the note. That is the problem the scribe layer exists to fix.

_Sources: Irving et al., BMJ Open 2017; National Health Authority / DD News, May 2026._

## What "clinic copilot" actually means as a category

The term comes from aviation, where a copilot shares the operational load of flying. Applied to a clinic, it covers anything that monitors, assists, and offloads work, ideally without the doctor having to operate it directly.

In practice, the category breaks into four functional layers:

- **Documentation.** The scribe layer. Listens to the visit, produces clinical notes and structured outputs like ICD code suggestions and Rx drafts. This is where the technology is most mature today, and it is the core of Practice Copilot.
- **Patient communication.** Recall messages, appointment confirmations, follow-up reminders. In most Indian clinics this falls to the receptionist, or it does not happen at all. WhatsApp messaging is bundled from the Copilot plan; automated follow-ups and an AI receptionist come in at the Autopilot plan.
- **Scheduling.** Online booking, waitlist management, rescheduling. Scheduling is included from the entry Assist plan.
- **Billing.** Insurance claim preparation, payment tracking, outstanding-invoice management. This is not part of the solo Practice Copilot plans today.

Patient Square covers documentation, scheduling, messaging, and the record system across its plan ladder; insurance billing is not part of the solo plans yet.

## How the AI scribe works in an Indian clinic

The setup is simpler than most doctors expect. You open the Patient Square app on a phone or tablet before the consultation, tap to begin, and set it aside. It listens through the visit, in English, Hindi, Hinglish, or any of 20-plus Indian languages, picks out the clinical content, and builds the note in the background.

After the visit you get a draft: a SOAP note in clean clinical English, ICD-10 code suggestions, and a prescription draft ready for your review. You correct what needs correcting, sign off on the rest, and the note is done.

A few things that matter for Indian clinic conditions:

- **Live consultation audio is discarded after drafting.** Uploaded recordings use a separate retention mode with explicit consent.
- **Notes always come out in English.** The system understands Hindi, Hinglish, and regional-language code-mixing, but the note itself is always clinical English, which is what a hospital referral, an insurance claim, or a legal challenge needs.
- **The prescription is a draft.** It reflects what was decided in the consult, and you review the full draft before anything reaches the patient. The scribe does not screen for drug interactions, dosing, or contraindications; that clinical check stays with you, the prescriber. There is no pharmacy gateway; it is a structured draft you take into your existing prescribing workflow.
- **ABDM integration is on the roadmap, not live.** If ABHA record linking is a requirement for your clinic right now, confirm that directly with the team before signing up.

India documentation backlog is not a minor inconvenience. Doctors running 60-patient days sometimes spend two to three hours after clinic hours finishing notes they could not complete during consultations. Those records matter for continuity of care, for medico-legal purposes under the Indian Medical Council Regulations (which require indoor patient records be kept a minimum of three years), and increasingly for ABDM record linking once that integration matures.

## India compliance: DPDP Act 2023 and medical records

Any software that processes patient consultation audio in India is handling sensitive personal data under the Digital Personal Data Protection Act 2023. Patient Square processes this with consent-first, purpose-limited handling. The patient audio is used to generate the clinical note and nothing else.

On certification: Patient Square has a SOC 2 Type II audit underway. That is the accurate phrasing. The audit is in progress, not complete. If you are evaluating clinic software for a multi-doctor practice where a finished certification is a gate, ask the team for the current status.

## Who gets the clearest return

Solo GPs and specialists running high-volume OPD clinics. If you see 40-plus patients a day and your notes are either incomplete at the end of the session or finished at 9pm, a documentation layer pays for itself quickly.

The numbers: from Rs 1,599 per clinician per month on annual billing for the entry Assist plan (India solo pricing, ex-GST, plus 18% GST, so about Rs 1,887 with GST; 7-day free trial through the India signup page), the monthly cost is around one patient consultation fee. If the scribe saves 45 minutes of post-clinic documentation across 25 working days, that is 18-plus hours back per month. What a doctor does with that time is their call, but the time is real.

Multi-doctor clinics get two things: the documentation gain across all providers, and consistency. Notes are structured the same way regardless of which doctor saw the patient.

The fit is weaker for clinics where the primary problem is billing, scheduling, or pharmacy inventory. The scribe layer does not address those. You would be adding one tool on top of a different underlying problem.

## What "Practice Copilot" does not do yet

Insurance claim preparation and billing automation are not part of the solo Practice Copilot plans. If revenue-cycle work is your main pain, that gap is worth naming before you buy.

Notes do not come out in Hindi or any regional language. The scribe understands them as input, but the note itself is always clinical English. If your hospital or referral network requires regional-language documentation, account for that gap.

ABDM integration is on the roadmap, not live. The NHA ecosystem now covers more than 450 integrated health-tech solutions and over one billion ABHA-linked health records as of mid-2026, but Patient Square certification against NHA milestones is not live yet. The record system it does bundle at the Copilot plan is the AI Copilot EHR, with EHR-ready export (PDF, HL7, FHIR); it does not yet write back into a third-party EHR or link ABHA numbers.

## The evaluation question worth asking

When you evaluate clinic copilot software in India, the right question is not whether the tool does everything. No single tool does. The question is: what is the largest time drain in your clinic, and does this tool address that specific thing?

If the answer is documentation, an ambient scribe is the most direct fix on the market today. If it is something else, solve that first. For the wider buying view, the [best clinic management software in India](/in/blog/best-clinic-management-software-india/) roundup and the [EMR software in India guide](/in/blog/emr-software-india-guide/) cover the storage-layer choices that sit underneath.

Practice Copilot from Patient Square brings the practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after the visit, plus scheduling from the entry plan and a bundled AI EHR and messaging as you move up. A 7-day free trial is available through the India signup page. India pricing starts from Rs 1,599 per clinician per month on annual billing, ex-GST (plus 18% GST). See the [India pricing page](/in/pricing/) for current numbers.

_Reviewed by the Patient Square clinical team._

---

## Practice Fusion Alternatives: The Upgrade Path for 2026
https://patientsquare.com/us/blog/practice-fusion-alternatives/
Published 2026-06-22 · Updated 2026-08-27 · Tags: alternatives, ehr, practice-fusion, comparison

Practice Fusion is a low-cost cloud EHR with no ambient scribe. Here are the best alternatives for a solo practice that's outgrown it, plus a bundled AI EHR from $119.

Not anymore. Practice Fusion built its early reputation on a free, ad-supported EHR, but its current pricing starts around $199 per provider per month on an annual commitment, with a two-week trial. The ad-supported free tier is retired. If you remember Practice Fusion as the free option and are surprised by the bill, you're not alone.

If you're looking for a Practice Fusion alternative, the honest first question is: what did you outgrow? For most solo practices it's one of two things, the price crept up past what "free" used to mean, or you're still typing every note by hand while newer tools draft it for you. Patient Square's Copilot plan is **$119 per provider per month** on annual billing and bundles an ambient AI scribe with the AI Copilot EHR, so documentation and the record live in one bill. You can see a finished note in about two minutes before you decide anything.

Practice Fusion isn't a bad product. It's a clean, low-friction cloud EHR. But it hasn't been free for a while, and it doesn't write your notes for you. This page maps the alternatives by what you're actually trying to fix.

> **Key takeaways**
>
> - Practice Fusion's ad-supported free tier is gone; current pricing starts near $199 per provider per month on annual terms.
> - It has no ambient AI scribe, so you still type or dictate every note.
> - The best alternative depends on your gap: bundled AI scribe plus EHR, or a deeper billing suite.
> - Patient Square Copilot is $119 per provider monthly (annual), with the scribe bundled and no per-note metering.
> - Practice Fusion still fits a practice that wants a simple, cheap record system and doesn't mind typing notes.

## Practice Fusion alternatives at a glance

Here's the field, framed by what a former Practice Fusion user usually needs next.

| Alternative | Best for | Ambient scribe | Published starting price |
|---|---|---|---|
| Patient Square Copilot | Solos who want to stop typing notes | Yes, bundled | $119/provider/mo (annual) |
| Practice Fusion (staying) | Simple, cheap record system | No | ~$199/provider/mo |
| Full PM suite (e.g. athenahealth) | Deep billing and RCM | Varies / add-on | Quote-based, higher |
| Behavioral-health tools (e.g. SimplePractice) | Therapy-specific workflows | Add-on note-taker only | $49–$99/mo |

Prices for competitors are third-party or vendor figures as of this writing; verify current numbers before you sign. The point of the table is direction, not a final quote.

If your main pain is charting time, start with the bundle option. If it's billing depth, keep reading; that's a different tool.

## Wait, isn't Practice Fusion free?

It used to be. Practice Fusion made its name as a free, ad-supported EHR, and a lot of clinicians still picture it that way. That model is retired. Practice Fusion's current pricing page lists a starting rate around **$199 per provider per month** on an annual commitment, with a two-week trial. There's no ad-supported free tier anymore.

That matters because "we'll upgrade later" was the whole appeal of starting free. If you're already paying, the calculus changes. You're now comparing paid tools on features, and the feature a lot of practices care most about, an ambient scribe that drafts the note, is exactly what Practice Fusion doesn't have.

## Why "no ambient scribe" is the real reason to leave

Practice Fusion charts fine. You can e-prescribe, order labs, and keep records. What it won't do is listen to the visit and hand you back a note. You still type it, or you dictate and clean up.

That's the gap that sends solo practices shopping. If you're doing an hour of charting after a full clinic day, a cheaper record system doesn't fix your evening. A scribe does.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** annually. So you can land below Practice Fusion's current price and stop typing notes at the same time. Book a demo and check that claim against a real visit.

## What the bundle gives you that a bare EHR doesn't

Concretely, moving from a charting-only EHR to an AI-scribe bundle changes the shape of your day:

- **The note drafts itself.** Ambient capture during the visit, structured SOAP note ready the moment the visit ends, roughly two minutes later.
- **ICD-10 suggestions** to speed your coding. These are suggestions, not a certified coding engine, so you stay in control of what's billed.
- **A prescription draft** you review and sign. It's a draft, not automated transmission to a pharmacy.
- **Unlimited notes, no per-note meter.** A 20-patient Tuesday costs the same as a 10-patient Friday.
- **One bill** for the scribe and the record, instead of a bare EHR plus a separate scribe subscription.

The record system is the AI Copilot EHR bundled at Copilot. Audio is processed in memory and discarded once the note drafts, so there's no recording kept. For the full head-to-head on bundled tools, see our [best EHR with AI scribe built in](/us/blog/best-ehr-with-ai-scribe-built-in/) roundup.

## When Practice Fusion is still the right call

Don't switch for the sake of it. Practice Fusion is the better choice if you want a simple, inexpensive cloud EHR, you're comfortable typing or dictating your own notes, and you don't need an ambient scribe or a bundled AI layer. Its e-prescribing and lab connectivity are solid, and for a low-volume practice that's already trained on it, "if it isn't broken" is a fair answer.

It's also fine as a landing spot if your budget is truly fixed and the scribe isn't worth the difference to you. Just know that the free version you may remember is gone, so you're comparing paid tools now, not paid against free.

If your needs run toward heavy billing instead, a full practice-management suite fits better; our [athenahealth EHR cost](/us/blog/athenahealth-ehr-cost/) page covers that end.

## How to pick your Practice Fusion replacement in a week

Make the decision on real visits, not a spec sheet:

1. Name the thing you outgrew: price, charting time, or missing features. That picks your category.
2. If it's charting time, shortlist bundled AI-scribe-plus-EHR tools with published prices.
3. Export a set of your Practice Fusion records to confirm the migration path is clean.
4. Run a 7-day trial of the new tool on a real clinic week, not a scripted demo.
5. Compare the finished note to what you'd have typed. That's the whole test.

The receipts, encryption, access, and audit status, are on the [security page](/us/security/), and the full price ladder is on the [pricing page](/us/pricing/). Book a short demo to see the note quality, then run the 7-day trial before you move a single chart. For a solo practice that's outgrown "free," a bundle that writes your notes and holds your records for $119 is usually the upgrade that pays for itself in reclaimed evenings.

---

## SOAP Note Examples and a Free Template
https://patientsquare.com/us/blog/soap-note-examples/
Published 2026-06-22 · Updated 2026-07-22 · Tags: soap-note, clinical-documentation, templates

Three full worked SOAP note examples, each section annotated, plus a blank copy-paste template. SOAP means Subjective, Objective, Assessment, Plan.

SOAP stands for Subjective, Objective, Assessment, Plan. The Subjective is what the patient tells you. The Objective is what you measure and examine. The Assessment is your clinical judgment, the diagnosis and reasoning. The Plan is what happens next: tests, medications, referrals, follow-up. The four sections form one encounter note.

A SOAP note records a clinical visit in four parts: Subjective (what the patient reports), Objective (what you measure and examine), Assessment (your diagnosis and reasoning), and Plan (what happens next). Below are three full worked examples for different visits, each section annotated so you can see what belongs where, plus a blank template to copy.

The fastest way to learn the format isn't a definition. It's reading real notes and seeing why each line sits where it does. So that's most of this page: a primary-care cold, a blood-pressure check, and an anxiety visit, written out in full, followed by a blank you can paste straight into your chart.

> **Key takeaways**
>
> 1. SOAP = Subjective, Objective, Assessment, Plan. Four sections, one encounter note, the same order every time.
> 2. The Assessment is the section that fails most often. "Sore throat, query viral" is a restated complaint, not an assessment.
> 3. Three full worked examples below cover an upper-respiratory visit, a hypertension follow-up, and a behavioral-health visit.
> 4. A blank copy-paste template sits at the end. Steal it.
> 5. Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit (JAMA Network Open, 2023). The note now outlasts the appointment.

## What does each SOAP section actually carry?

Quick version before the examples, because the examples make more sense once the buckets are clear. Per the StatPearls reference, the SOAP note is the standard documentation method for an encounter, and Dr. Lawrence Weed devised it about half a century ago as part of his problem-oriented medical record.

**Subjective** is the patient's account. Chief complaint, history of present illness (onset, character, severity, what helps, what worsens), associated symptoms, and the past history that frames today's visit. Their story, in clinical language. Not your interpretation.

**Objective** is what you observe and measure. Vitals, exam findings, results in front of you. Facts only. One discipline worth keeping: write only what you actually checked. "Abdomen soft, non-tender" when you never touched the abdomen is how a note becomes a liability.

**Assessment** is your clinical judgment. The working diagnosis, the differential, and the reasoning that connects the subjective and objective to it. This is the hardest section to write well and the one a reviewer or a covering colleague reads first.

**Plan** is what you do about it. Tests ordered, medications started or changed, referrals, patient instructions, follow-up interval. A decision you made in the room but left out of the Plan is a decision that didn't happen, as far as the chart is concerned.

## Worked example 1: an upper-respiratory visit (primary care)

A 29-year-old comes in with a few days of cold symptoms. This is the bread-and-butter acute visit. The illustrative note:

---

**Subjective:** 29-year-old presents with 3 days of sore throat, nasal congestion, and a dry cough. Reports low-grade fevers to 100.4F at home, worse in the evening. No difficulty swallowing solids, no ear pain, no shortness of breath. No sick contacts known. No chronic conditions, no regular medications, no known drug allergies. Has tried acetaminophen with partial relief.

**Objective:** Temp 99.1F, HR 78, BP 122/74, RR 14, SpO2 99% on room air. Alert, comfortable, not in distress. Oropharynx mildly erythematous, no tonsillar exudate. No anterior cervical lymphadenopathy. Tympanic membranes clear bilaterally. Lungs clear to auscultation, no wheeze or crackles.

**Assessment:** Acute viral upper respiratory infection. Presentation is consistent with a viral course: gradual onset, low-grade fever, no exudate, clear chest. Streptococcal pharyngitis unlikely given absent exudate, absent anterior cervical nodes, and presence of cough (Centor criteria low). No red flags for lower respiratory involvement.

**Plan:** Supportive care discussed: hydration, rest, acetaminophen or ibuprofen for fever and throat pain, saline nasal spray. No antibiotic indicated; rationale explained to patient. Return precautions given: shortness of breath, fever above 102F, symptoms beyond 10 days, or difficulty swallowing. Follow up if not improving in 7 to 10 days. No work note requested.

---

What's worth noticing here. The Subjective carries the actual history, not just "sore throat." The Objective records the exam that rules pharyngitis in or out, which is exactly what the Assessment then reasons about. The Assessment explains why this is viral instead of just labeling it, and the Plan does the unglamorous but legally important work: it documents that no antibiotic was given on purpose, and it spells out when to come back. That last line is the one busy notes drop.

## Worked example 2: a hypertension follow-up

A 54-year-old returns to review blood pressure six weeks after starting a medication. Follow-up visits trip people up because the Subjective is thinner and the Assessment has to compare today against last time. The illustrative note:

---

**Subjective:** 54-year-old returns for hypertension follow-up, 6 weeks after starting amlodipine 5 mg daily. Reports good adherence, no missed doses. No headaches, no chest pain, no palpitations, no ankle swelling. Has been checking home BP most mornings, averaging around 140/88. Reports cutting back on added salt; has not yet started regular walking. No new medications or supplements.

**Objective:** BP 142/90 right arm seated, repeat 138/88 after 5 minutes. HR 72 regular. Weight 92 kg (down 1 kg from last visit). No peripheral edema. Heart sounds normal, no murmurs. Home BP log reviewed: morning readings 135 to 145 systolic over the past 3 weeks.

**Assessment:** Essential hypertension, not yet at goal on amlodipine 5 mg. Home and office readings agree, so this is not white-coat effect. Tolerating current therapy without side effects. Stage 2 by office reading; lifestyle modification partially adopted. Reasonable to intensify pharmacotherapy while reinforcing non-pharmacologic measures.

**Plan:** Increase amlodipine to 10 mg daily. Continue home BP monitoring, morning and evening, log to bring next visit. Reinforced salt reduction; set a starting goal of a 15-minute walk most days. Basic metabolic panel ordered to recheck renal function and electrolytes. Follow up in 4 weeks to reassess BP and tolerance. Return sooner for swelling, dizziness, or BP above 180/110.

---

The thing this example teaches is the comparison move. A follow-up Assessment is almost useless if it just says "hypertension." The useful version says where the patient is *relative to the plan*: on treatment, not yet at goal, tolerating it, real (not white-coat). Everything in the Plan then follows from that one sentence. Note also that the Objective records two BP readings and the home log, because the Assessment leans on agreement between them.

## Worked example 3: a behavioral-health visit

A 41-year-old presents with worsening anxiety. Behavioral-health notes lean harder on the Subjective and Assessment, and the Objective shifts toward mental-status observations and a screening score. The illustrative note:

---

**Subjective:** 41-year-old presents with 2 months of increasing anxiety, describing constant worry about work and finances, trouble falling asleep, and a "wired but tired" feeling most days. Reports irritability and difficulty concentrating. Denies panic attacks. Denies suicidal ideation, no thoughts of self-harm, no plan. No alcohol or substance use beyond occasional coffee. Taking sertraline 50 mg daily for 4 weeks, started by primary care, reports it "might be helping a little."

**Objective:** Alert, cooperative, well-groomed. Speech normal in rate and volume. Mood reported as "on edge," affect anxious but reactive. Thought process linear and goal-directed. No psychosis. GAD-7 administered this visit: score 14 (moderate to severe anxiety), down from 17 at the prior visit. Insight and judgment intact.

**Assessment:** Generalized anxiety disorder, moderate to severe by GAD-7, showing early partial response to sertraline at 4 weeks. Trajectory is downward (17 to 14), consistent with a medication that has not yet reached full effect. Risk is low: no suicidal ideation, no self-harm, stable support. Sleep disturbance is a prominent and treatable feature.

**Plan:** Continue sertraline 50 mg daily; full effect can take 6 to 8 weeks, so hold current dose and reassess. Discussed sleep hygiene and a brief breathing exercise for evening worry. Provided referral information for cognitive behavioral therapy. GAD-7 to be repeated at next visit to track response. Follow up in 3 weeks. Patient given crisis-line information and advised to return sooner if mood worsens or any thoughts of self-harm emerge.

---

Two things to call out. First, the Objective here is the mental-status exam plus a validated score (GAD-7), which gives you something to track instead of a vibe. Second, the risk statement in the Assessment is not optional in behavioral health; "no suicidal ideation, no plan, stable support" belongs in the note even when the answer is reassuring. If your visits are mostly behavioral-health, the [mental-health SOAP note guide](../how-to-write-a-mental-health-soap-note/) goes deeper into formulation and includes a rubric for grading a draft.

## A blank SOAP note template you can copy

Here's the reusable skeleton. Paste it into your chart and fill each line. The prompts in brackets are reminders, not text to keep.

---

**Subjective:**
[Chief complaint in the patient's words]
[History of present illness: onset, character, severity, what helps/worsens, associated symptoms]
[Relevant past history, current medications, allergies]
[Pertinent negatives the patient reports]

**Objective:**
[Vitals: BP, HR, RR, temp, SpO2, weight if relevant]
[General appearance]
[Focused exam findings: only what you actually checked]
[Results reviewed today: labs, imaging, screening scores]

**Assessment:**
[Working diagnosis, stated plainly]
[Differential and the reasoning that supports or excludes it]
[For follow-ups, where the patient is relative to the plan: at goal, improving, tolerating treatment]
[Risk statement where relevant]

**Plan:**
[Investigations ordered]
[Medications started, changed, or continued, with dose]
[Referrals]
[Patient instructions and education given]
[Return precautions / red flags]
[Follow-up interval]

---

Keep the order fixed and the section labels explicit. The structure is the whole point: a reader should be able to jump to the Assessment without hunting for it. If you want the same skeleton with the four sections explained line by line for an Indian OPD context, the [SOAP full-form and format breakdown](/in/blog/soap-note-full-form-format-india/) covers that.

## How an AI scribe drafts the SOAP note from the conversation

Filling that template by hand, on every patient, is the part that follows you home. A 2023 JAMA Network Open study found primary-care physicians logged a median of 36.2 minutes of EHR time per 30-minute visit. The note now takes longer than the appointment it describes. That's the gap an ambient scribe is built to close.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

In practice, that flips your job from writing to editing. The scribe maps the conversation onto the four sections: the Subjective from what the patient reported, the Objective from the findings you said out loud, the Assessment and Plan from your stated reasoning and the decisions you made in the room. You read the draft, correct anything off, and sign. The ICD-10 entries are suggestions you confirm, not codes filed for you. The prescription is a draft too, built from the plan you stated; you check the drugs, doses, and instructions and sign. It doesn't run an automated interaction check, so the prescribing call stays yours, the same as when you write it by hand.

A few honest limits. The Assessment is where you should spend your review time, because synthesizing your reasoning is harder for a model than transcribing what was said; grade that section first on your own visits. The note comes out in clean clinical English. The visit audio is processed in memory and discarded the moment the draft is ready, so there's no recording sitting in an archive. If you want a way to judge whether a drafted note is actually good enough to sign, the [SOAP note quality rubric](../ai-scribe-soap-note-quality/) gives you six points to score it on, and the [generator comparison](../ai-soap-note-generators-compared/) lays out how the ambient tools differ.

The examples above are the bar. A drafted note should read like one of them after a quick edit, not like a transcript you have to rebuild. The way to know is to run it on real visits, not a demo. Read the [pricing page](../../pricing/), then try structured SOAP notes for a week on your own patients and read every draft closely.

---

## Switching From HealthPlix: A Migration Guide (India)
https://patientsquare.com/in/blog/switch-from-healthplix-to-ai-native-ehr-india/
Published 2026-06-22 · Tags: switching, healthplix, ehr, pricing

Moving off HealthPlix? What actually exports, what doesn't, and how to switch to an AI-native scribe + EHR. Per-doctor pricing from ₹1,599/mo + GST.

Per HealthPlix's own FAQ, access to patient records stays with the doctor. In practice, what moves cleanly to a new system is registration data, patient names, ages, phone numbers, and IDs. Migration cases reported by other Indian EMRs show past prescriptions and treatment history often don't import as structured data. Ask HealthPlix for a full export in writing before you switch, and plan for the history to arrive as PDFs, not fields.

Switching off HealthPlix is doable, but plan for the history to move as documents, not clean fields. Registration data, patient names, ages, phones, IDs, usually carries over. Structured clinical history, past prescriptions, diagnoses, templates, often doesn't import as searchable data; that's true across Indian EMR migrations, not a knock on any one vendor. So the smart switch keeps your old system read-only for a transition window while new visits start clean somewhere better. If "somewhere better" means removing the note-writing entirely, Patient Square leads with an ambient scribe and bundles an AI EHR one tier up, from [₹1,599/mo annual](../../pricing/) plus GST.

This is the migration playbook: what exports and what doesn't, the switch sequence that avoids a data gap, the honest price comparison, and when staying on HealthPlix is the right call.

> **Key takeaways**
>
> - Registration data usually migrates. Structured clinical history (past Rx, diagnoses) often arrives as PDFs, not fields, plan for it.
> - Get a full export from HealthPlix in writing, and keep read-only access during the switch so nothing goes dark.
> - HealthPlix is an EMR you drive; Patient Square adds an ambient scribe that writes the note, plus a bundled AI EHR at Copilot.
> - Pricing: HealthPlix Pro ₹11,999/yr, Elite ₹17,999/yr. Patient Square scribe from ₹1,599/mo annual, scribe + EHR from ₹2,399/mo annual, both ex-GST.
> - Notes come out in clean English even from Hindi or mixed consults. ABDM is on our roadmap, not live, verify vendor claims either way.

## Should you switch off HealthPlix? The honest table

Before the mechanics, the decision. Here's what you're actually trading.

| | Stay on HealthPlix | Switch to Patient Square |
|---|---|---|
| Writing the note | You type or dictate it | Ambient scribe drafts it for you |
| Record system | Mature EMR you already know | Bundled AI Copilot EHR at Copilot tier |
| Price (per doctor) | ₹11,999–17,999/year | ₹1,599/mo scribe · ₹2,399/mo scribe+EHR (annual, ex-GST) |
| Migration effort | None, you're already on it | Real, but mostly registration data moves cleanly |
| Language | Regional support | English, Hindi, 20+ languages in; English notes out |
| Best when | Records are fine, you don't need a scribe | Documentation time is your real drain |

HealthPlix is a competent EMR with a large doctor base. The reason to switch isn't that it's bad; it's that an EMR organises where notes go without touching the two minutes it takes to write one. If your worst daily problem is the writing, a scribe-led platform changes the math. Book a demo and see a note drafted from a real consult before you commit to any migration.

## What exports from HealthPlix, and what doesn't

This is the part people get wrong, so be precise.

HealthPlix's own FAQ states that access to patient information and records stays with the doctor, and that it doesn't share patient details with other clinics or third parties. Good. But "access stays with you" is not the same as "one-click structured export into a competitor."

What migrates cleanly in practice: registration data. Patient names, ages, phone numbers, addresses, and patient IDs. Other Indian EMRs have documented migrating 20,000-plus patient records of this type off HealthPlix.

What usually doesn't come across as structured data: past prescription history and treatment records. In reported migrations, those either don't import or arrive as documents rather than searchable fields. Again, this is the normal shape of EMR-to-EMR migration in India, not a HealthPlix-specific failure. Clinical history is the hardest thing to move between any two systems because every vendor stores it differently.

So the realistic expectation: your patient *list* moves; your patient *history* mostly arrives as PDFs. Plan around that instead of being surprised by it.

## The switch sequence that avoids a data gap

Don't flip the switch overnight. Run it in overlap.

1. **Request a full export from HealthPlix in writing.** Ask specifically for registration data and clinical history, in whatever format they provide, and get the timeline in writing. Don't cancel anything yet.
2. **Keep HealthPlix read-only for a transition window.** Sixty to ninety days. Your full history stays reachable there while you build forward in the new system. No gap, no panic.
3. **Import the registration list into the new system.** This is the part that moves cleanly. Your patient directory comes across so front-desk lookups work from day one.
4. **Start new visits clean in Patient Square.** From the switch date, every new consult produces a fresh, structured note via the scribe. Your searchable history rebuilds from real visits, fast, because the scribe writes every one.
5. **Attach old history as reference where needed.** For patients with important past records, keep the HealthPlix PDF handy in the chart until the new record has enough visits to stand on its own.
6. **Only then close the HealthPlix account.** Once the export is verified and the transition window has passed. Never cancel before you've confirmed you can read your own data.

The reason this works: because Patient Square's scribe writes every new note automatically, your fresh record fills in faster than a typed-EMR would. You're not manually re-keying history; you're generating a new, clean one at OPD speed.

## What does the switch cost in India?

Here's the money, both sides, stated plainly.

| | HealthPlix | Patient Square (Assist) | Patient Square (Copilot) |
|---|---|---|---|
| What it is | EMR you drive | AI scribe, standalone | AI scribe + bundled AI EHR |
| Price per doctor | ₹11,999–17,999/year | ₹1,599/mo annual, ex-GST | ₹2,399/mo annual, ex-GST |
| With 18% GST | (annual, quoted ex-GST) | ₹1,887/mo | ₹2,831/mo |
| Per-note charges | None advertised | None | None |
| Setup fee | Ask before switching | None | None |

Read this honestly. On a pure record-system basis, HealthPlix's annual price is competitive with, and at Elite roughly matches, Patient Square's Assist tier, which works alongside an existing EHR. The Copilot tier at ₹2,399/mo annual adds Patient Square EHR to the ambient scribe. So the switch isn't about shaving rupees; it's about whether removing the writing and changing the record path are worth it. [See the full ladder](../../pricing/), and for the deeper feature comparison, our [HealthPlix alternatives](../healthplix-alternatives-india/) post covers it.

## When staying on HealthPlix is the right call

Don't switch for the sake of switching. Stay put if:

Your records are genuinely fine and typing notes doesn't bother you. If documentation isn't your pain, a scribe-led platform solves a problem you don't have. HealthPlix's EMR is mature; if it fits your workflow, migration risk isn't worth it.

You depend on a HealthPlix-specific feature or integration you can't replace. Check that first. If something in your daily flow only exists there, price the loss before you move.

You'd rather not run any migration this quarter. A switch, even a clean one, is work. If the timing's wrong, it's wrong. The scribe will still be there next quarter.

Switch if the writing is the drain, you want the note handled and the record system in one product, and you're willing to run a 60-to-90-day overlap to do it safely. That's the case Patient Square is built for. For a one-doctor practice weighing it, [AI scribe for solo doctors in India](../ai-scribe-for-solo-doctors-india/) has the numbers for your size. If you're still deciding whether to start with the scribe alone or jump straight to the bundled EHR, [AI scribe vs EMR: which to buy first](/in/blog/best-ai-scribe-vs-emr-which-first-india/) walks through that sequencing question. And for a full picture of what EHR software costs in India before you price the switch, [EHR software cost guide](/in/blog/ehr-software-cost-india-buyers-guide/) names every fee vendors bury.

## How to switch in a week

You can't finish a migration in a week, but you can decide in one:

1. Ask HealthPlix, in writing, exactly what a full export includes and how long it takes. Their answer tells you most of what you need.
2. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, then run the scribe on real consults after the workspace is ready, Hindi and mixed-language included, to see if the note quality holds.
3. Check the exported note format, PDF, HL7, or FHIR, against how you want records stored.
4. Confirm the price with GST against HealthPlix's annual figure, and decide whether the scribe is worth the difference.
5. Read the receipts on the [security page](../../security/), including the honest note that ABDM integration is on our roadmap, not live.

Book a short demo if you want the migration walked through against your own setup. The switch is manageable when you plan for history to move as documents, keep your old access read-only during the overlap, and let the scribe rebuild a clean record from your very next visit.

---

## Choosing EMR Software in India: A 2026 Buyer's Guide
https://patientsquare.com/in/blog/emr-software-india-guide/
Published 2026-06-19 · Updated 2026-07-22 · Tags: emr, india, buyer-guide

A practical guide to choosing EMR software in India in 2026: cloud vs on-premise, ABDM readiness, honest pricing, and when to add a documentation layer.

No single answer fits every clinic. For a solo GP who bills simply and needs clean notes, a lightweight EMR plus a documentation layer solves more than an expensive suite. For a multi-speciality clinic that also handles pharmacy and cashless insurance, a full-featured EMR like HealthPlix is a better fit. Match the tool to what is actually broken in your workflow, not to a feature checklist.

EMR software in India is not one thing. It runs from bare-bones digital registers to full clinic-management suites with billing, pharmacy, and ABDM record linking built in. The right choice comes down to one honest question: what is actually broken in your clinic? If the answer is billing and appointments, a full EMR earns its fee. If it's the hour of charting after the last patient leaves, adding a documentation layer on top of whatever you already run solves more than replacing the whole system.

What follows covers what to look for, what vendors actually cost, and where the cloud vs. on-premise decision matters under India's DPDP Act 2023.

> **Key takeaways**
>
> - India-native EMR prices cluster around ₹1,000–1,500 per doctor per month plus 18% GST. HealthPlix publishes ₹11,999–17,999/year. Practo Ray publishes nothing first-party.
> - "ABDM compliant" masks three separate NHA milestones. Ask any vendor which one it has cleared and whether it is live in production.
> - For most solo and small-clinic buyers, the documentation layer is the missing piece, not the storage layer.
> - A cloud EMR under India's DPDP Act 2023 makes the vendor a Data Fiduciary. Data-centre location, consent handling, and deletion rights all become your checklist items at contract time.

_Sources: Irving et al., BMJ Open 2017; National Health Authority / DD News, May 2026._

## Start here, before the vendor calls

Indian clinic software markets itself under four overlapping labels: EMR, EHR, clinic management software, practice management system. They're not synonyms, and conflating them is how clinics overbuy.

Per the MoHFW's EHR Standards 2016, an EMR is the digital chart of one clinic. It doesn't travel easily outside the practice. An EHR is built to share records across providers using SNOMED CT, ICD, and LOINC, which is what ABDM's Health Information Provider model (M2) is built on. Most Indian clinic software sold today is an EMR in design, regardless of the label on the login screen. That's fine for a single clinic. Worth knowing what you bought, though.

A clinic management suite goes further. It bundles billing, pharmacy, appointment scheduling, sometimes lab-order management, into one system alongside the clinical record. If you run all of those in-house and want one login, a suite makes sense. If you don't, you're paying for modules you'll never open.

The deciding question is simple. If your clinic's main friction is billing, inventory, or scheduling, buy an EMR or clinic-management suite. If the friction is documentation, notes that don't get written, or get compressed to a line because the consult is two minutes long, the fix is a documentation layer, not a new EMR.

Our [EMR vs. EHR India explainer](/in/blog/emr-vs-ehr-india/) covers this distinction in more depth, and the [India clinic software scorecard](/in/blog/best-clinic-management-software-india/) scores the main options on that exact lens.

## What EMR software in India actually costs

Most vendors gate pricing behind a demo call. Here is what is actually published, as of June 2026.

| Vendor | Type | Published price | Price source |
|---|---|---|---|
| **HealthPlix** | Specialty EMR (billing, pharmacy, ABDM, DDI) | ₹11,999/yr Pro; ₹17,999/yr Elite (≈₹1,000–1,500/mo, computed) | First-party (healthplix blog) |
| **Practo Ray** | Clinic-management suite | No first-party price; third-party listings ≈₹1,000–6,000/doctor/mo | Third-party (sales-gated) |
| **EkaScribe** | Ambient scribe (eka.care platform) | ₹1,499/mo Pro; free tier 5 consults/day; ~17% off annual | First-party (ekascribe.ai) |
| **AI Medical Scribe by Patient Square** | Ambient scribe, part of Practice Copilot | From ₹1,599/mo (Assist annual), ex-GST; ₹2,399 (Copilot annual) adds a bundled AI EHR; ₹1,599 + 18% GST ≈ ₹1,887/mo | First-party |

All figures from each vendor's own pages in June 2026. Confirm before you buy.

A few honest notes. HealthPlix annual fees compute to ₹1,000–1,500 a month, which lands in the same band as a standalone scribe. Practo Ray is genuinely sales-gated; their website shows no prices. If the table above leaves a gap, the [full India clinic software comparison](/in/blog/best-clinic-management-software-india/) goes deeper on per-feature scoring.

## Cloud EMR vs. on-premise: what DPDP Act 2023 adds

Five years ago, the cloud vs. on-premise debate came down to internet reliability and upfront hardware cost. The DPDP Act 2023 changes that calculation, and the draft DPDP Rules 2025 published by MeitY add detail on what it means for clinic software specifically.

When patient records sit on a cloud vendor's servers, that vendor becomes a Data Fiduciary. They take on consent, purpose-limitation, security, and deletion obligations under the Act. That's not necessarily a problem. A reputable cloud vendor with serious security handles those obligations better than a local server nobody's patching. But the contract matters more than it used to.

Three specific questions belong in every EMR contract now. First: where are the data centres? India-domiciled storage sidesteps the cross-border transfer restrictions that DPDP Rules 2025 impose on specified categories of personal data. Second: what is the deletion process when the clinic ends its subscription? Patient records belong to the patient and the clinic, not the vendor. A contract that doesn't clearly specify the deletion timeline and the data hand-off process is a liability. Third: what is the breach notification procedure? The Act requires prompt reporting to the Data Protection Board; a cloud EMR vendor who can't tell you how they handle breach notification in one paragraph hasn't thought it through.

On-premise keeps the data under the clinic's roof. Which, for a practice running on a five-year-old Windows PC with no regular backups, is not obviously better. The real question isn't cloud vs. on-premise in the abstract; it's which option the clinic can actually secure, patch, and recover from a ransomware event.

Cloud wins for most small clinics on accessibility, auto-updates, and basic disaster recovery. On-premise fits clinics with specific data-sovereignty requirements or genuine local IT infrastructure. The DPDP Act doesn't ban cloud hosting. It raises the bar for the vendor you pick, and surfaces the questions that were always worth asking.

## ABDM, plainly stated

The National Health Authority's Ayushman Bharat Digital Mission crossed 100 crore ABHA-linked health records in May 2026, with more than 450 health-tech solutions integrated. ABDM is real infrastructure. It's where India's interoperable patient record is heading.

But "ABDM compliant" on a pricing page can mean almost anything. The NHA's sandbox-to-production process certifies software against three separate milestones, and each one does a different job.

M1 makes the software an identity provider: it can create and verify an ABHA number and register the clinic on the Health Facility Registry (HFR) and Health Professional Registry (HPR). M2 makes it a Health Information Provider: it can share a patient's records as FHIR bundles when the patient gives consent. M3 makes it a Health Information User: it can pull records from other providers into your view.

Certification is per-software, not per-clinic. The vendor clears the sandbox once; each facility registers itself separately. A product that can create ABHAs (M1) but hasn't reached record-sharing (M2) is "ABDM-ready" in marketing and half-built in practice.

We'll be straight here: AI Medical Scribe by Patient Square has ABDM integration on its roadmap, not shipped. We won't claim a milestone we don't hold. If you need live ABDM record linking today, your shortlist is an EMR that has cleared at least M1 and M2 in production. Ask for the NHA certification reference. Not just the badge.

## One more factor for empanelled hospitals: NHCX

If your clinic or hospital processes cashless insurance claims, the IRDAI's National Health Claims Exchange (NHCX) is now in the picture. NHCX is a standardised digital gateway for cashless claim pre-authorisation and settlement, launched for registered hospitals. IRDAI has pushed participating hospitals to route claims through NHCX rather than through disparate TPA portals.

This matters for EMR selection because NHCX integration is not yet table-stakes for most mid-market Indian EMRs. For an empanelled hospital that sees meaningful cashless claim volumes, ask any EMR vendor two specific questions: does the product currently send pre-auth and claim data to NHCX in the standard format, and if not, what is the roadmap. One manual re-entry per claim is annoying. At 30 claims a day, it is a part-time job.

For a small clinic without insurance empanelment, NHCX is not a factor today. For anything processing 10 or more cashless claims a month, it belongs on the shortlist criteria.

## Five questions that cut the shortlist fast

Most EMR buying decisions get tangled in feature lists that are 40 rows deep. These five questions get you to a shortlist without a month of demos.

Start with the basic category question: records or documentation? Is your real problem storing, billing, and scheduling, or is it getting the note written? Every other decision flows from this one.

Then: does the vendor publish a first-party price? Sales-gated pricing usually means the number flexes with how hard you negotiate. A vendor who puts a rupee figure on the page is signaling something real about how they run.

For ABDM, don't accept a badge. Ask which milestone the software has cleared and whether it's live in production or still in sandbox. "ABDM ready" is a marketing phrase; M2 in production is a verifiable fact.

If the product listens to the consultation, ask where visit audio goes. That question should get a one-sentence answer. Vague answers on data handling tend to predict vague practices on data handling.

Finally: what is the renewal price? Launch pricing and year-two pricing can be very different things. Get that number in writing before you sign anything.

## When a full EMR actually earns its fee

Be honest about this. A full EMR is the right call when the clinic genuinely runs records, billing, pharmacy, and scheduling through one system, and when the front-desk staff need all of that in the same view.

That's the case if you bill in-house and need GST invoicing, receipts, and revenue reports alongside the clinical note. Running billing in one place and records in another means reconciling the two every month. If you have a pharmacy or hold drug inventory, a dispensing module wired to the EMR keeps stock counts accurate and ties dispensing to the prescription. For multi-speciality clinics or small hospitals managing inpatients, lab orders, or referrals across sites, a full suite earns every rupee. A solo GP sitting in a single-room clinic almost never does.

HealthPlix is the clearest example of this category done honestly: it publishes its prices first-party, lists ABDM as a feature, and bundles billing, pharmacy, drug-interaction alerts, and teleconsultation in one product. That's a legitimate choice for a clinic that runs all of those functions. It's overkill for a doctor who mainly needs clean, retrievable notes from a 50-patient OPD day.

## Where a documentation layer fits alongside your EMR

The Indian OPD moves fast. Average primary-care consultation time in India is about two minutes, per Irving et al.'s 67-country BMJ Open review, which put India near the short end of a wide global range (48 seconds in Bangladesh, 22.5 minutes in Sweden). Two minutes to listen, examine, decide, and prescribe. The documentation loses that race every time. The note gets compressed to a line, or written from memory after the queue clears, or skipped entirely.

No EMR fixes this. A better storage system doesn't make the note appear; it just gives the thin note a nicer home. The constraint is upstream of the database. Under the Indian Medical Council's Professional Conduct Regulations 2002, indoor patient records should be kept three years and produced within 72 hours on request. Thin notes are a medico-legal liability. That liability sits with the clinician.

Patient Square is an AI clinical platform, and the AI Medical Scribe is its ambient scribe module: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The scribe sits alongside your existing EMR if you want to keep it. Move up to the Copilot plan and a bundled AI EHR comes with it, so you can fix the writing problem first and adopt the record system later, or not at all.

A few things that matter specifically for an Indian OPD. The scribe captures English, Hindi, and 20+ Indian languages, including the mid-sentence Hindi-English mixing of a real consult, and the note always comes back in clean clinical English. The prescription is a draft you review and sign. The scribe doesn't screen it for interactions or dosing, so that clinical check stays with you, the same call you make on every script now. Visit audio is processed in memory and discarded the moment the note drafts. There's no recording sitting on a server anywhere, which is the cleaner answer under DPDP Act 2023 and the one we'd want if the roles were reversed. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On pricing, the plans run per clinician per month, ex-GST. Assist starts at ₹1,599 on annual billing and covers the documentation essentials. Add 18% GST and the Assist invoice lands at about ₹1,887 a month. Copilot at ₹2,399 annual adds the bundled AI EHR and WhatsApp messaging; Autopilot at ₹3,999 adds an AI receptionist and follow-ups. So the tiers do differ, and you pay up only when you want the record system or the automation. There is a 7-day free trial through the India signup page. The Assist entry sits inside the ₹1,000–1,600 band India-native clinic software occupies, so it reads as one more clinic tool rather than an import priced for a different market.

If you're comparing the India-facing ambient scribes head to head, EkaScribe, Augnito, and AI Medical Scribe by Patient Square are compared at [India AI Medical Scribe Comparison](/in/blog/india-ai-scribe-comparison/).

## Deciding in one pass

Three questions get most clinics to a decision without spending a month on vendor demos.

Does your clinic move patient records between sites, hospitals, or specialists as a routine part of care? If yes, you need real EHR-level interoperability and ABDM certification at the milestones you actually require. Start with an EMR that has cleared those in production.

Are your notes actually complete and retrievable today? If they're thin or missing because there's no time to write them in a two-minute OPD, the fix is a documentation layer, not a better database. Adding a scribe to a working EMR costs less and solves more than replacing the EMR wholesale.

Does the vendor answer "where does the visit audio go" and "what's the year-two price" in one sentence each? Vague answers on either tell you something about how the rest of the relationship will go.

Sort those out and the decision mostly makes itself. If the missing layer is documentation rather than storage, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a real consult turn into a signed note. Or read through [pricing](../../pricing/) first. Either way, fix the layer that's actually broken.

---

## What ABDM Pays Your Clinic: DHIS Incentives, Honestly
https://patientsquare.com/in/blog/abdm-incentives-for-doctors/
Published 2026-06-18 · Updated 2026-10-15 · Tags: abdm, dhis, india, incentives

What NHA Corrigendum 7 paid for eligible clinic records through September 2026, and why clinics must confirm current DHIS terms before forecasting incentives.

NHA Corrigendum 7 set ₹10 or ₹5 facility rates for eligible DHIS records above the first 100 monthly transactions, but its stated period ended in September 2026. Those rates cannot be assumed for later transactions; confirm the applicable terms with NHA before planning or filing.

The National Health Authority's [Corrigendum 7](https://abdm.gov.in/strapicms/uploads/DHIS_corrigendum_7_c1d7e09cc2.pdf) set facility rates of ₹10 for an eligible Category 1 record or ₹5 for Category 2 after the first 100 eligible monthly transactions. Its stated period was April through September 2026, subject to scheme funds, and **that period has ended**. The rates below explain that period; they are not a forecast for later transactions. Confirm the current scheme and claim terms with the [NHA DHIS page](https://abdm.gov.in/DHIS) before planning or filing. This guide was source-checked on 15 October 2026; no later official rate schedule could be verified in the public NHA materials reviewed. It will be reviewed again on 22 October. It is educational, not financial or legal advice.

> **Key takeaways**
>
> - Category 1 means a diagnostic report or discharge summary: ₹10 for the health facility and ₹5 for the digital solution company (DSC).
> - Category 2 covers other listed health-information types, including prescriptions and OP consultations: ₹5 for the facility and ₹2.50 for the DSC.
> - Nothing is payable at 100 or fewer eligible monthly transactions. Above 100, NHA deducts the lowest-value 100 transactions first.
> - Records must be linked to a KYC-verified ABHA, and the one-transaction-per-day and five-per-month patient limits apply.
> - Corrigendum 7 applied from April through September 2026, subject to funds. Its rates cannot establish what applies to later transactions.

100', label: 'Eligible monthly transactions required before either the facility or DSC receives a record-linking incentive' },
    { value: 'Sep 2026', label: 'End of the period stated in Corrigendum 7; continuation is not guaranteed' },
  ]}
/>

_Source: NHA, DHIS Corrigendum 7, 9 April 2026. Its stated period ended September 2026; reviewed 15 October 2026._

## What does DHIS actually pay a clinic?

For its April–September 2026 period, Corrigendum 7 split eligible KYC-verified ABHA-linked records into two categories:

| Record category | Examples in Corrigendum 7 | Health facility | Digital solution company |
|---|---|---:|---:|
| Category 1 | Diagnostic report or discharge summary | ₹10 | ₹5 |
| Category 2 | Prescription, OP consultation, immunization, health document, wellness record, invoice, and other listed types | ₹5 | ₹2.50 |

If one health record contains several health-information types and at least one is a diagnostic report or discharge summary, Corrigendum 7 treats it as Category 1. These are rates used in the calculation, not a promise that every document earns money. The transaction must pass the KYC, volume, patient-frequency, registration, software, security, and claim-window conditions described below.

The first 100 eligible transactions were a baseline in Corrigendum 7. Its calculation removed the value of the lowest-rate 100 records first. In the corrigendum's example, a clinic recorded 70 eligible discharge summaries and 80 eligible OPD prescriptions. The gross facility calculation was ₹700 plus ₹400. NHA deducted all 80 ₹5 records and 20 of the ₹10 records, leaving **₹500 for the facility** and **₹250 for the paired DSC** under those terms.

## What shrinks or eliminates the payout?

Start with KYC and patient frequency. Only records linked to an ABHA address whose KYC status is verified on the last day of the transaction month count. For a given facility or DSC, at most one transaction for an ABHA can earn an incentive per day and five can earn an incentive per month. Corrigendum 7 applies these controls across the incentive categories and separately explains the limit for record-linking and consent-based incentives. Repeated documents for the same patient do not automatically multiply the payout.

Next, do not count registration activity as clinical-record activity. Corrigendum 7 removes record-linking incentives for Scan & Share and health-locker interactions. A separate consent-sharing stream can pay ₹10 to the Health Information User and ₹5 to each eligible source of successfully shared records, including an eligible private health locker, but only when the consent and record-sharing conditions are completed. Scan & Pay also has separate ₹5 facility and ₹1 DSC rates above its baseline. Those are different transaction categories, not add-ons to every OPD record.

The NHCX amount changed too. For an eligible AB PM-JAY insurance claim linked to ABHA and filed in FHIR format through NHCX, Corrigendum 7 lists **₹200 or 10% of the claim amount, whichever is lower**, for the health facility and ₹10 for the DSC. That category has a separate ₹1 crore cap per facility or DSC. The overall DHIS cap remains ₹5 crore per entity. A cap is a ceiling, not a forecast.

Finally, claims are time-bound. A facility can claim from its DHIS registration month and can generally include only the three preceding months with a current submission. Corrigendum 7 gives the example that an August 2026 filing can include May, June, and July, not April. Public-facility exceptions are narrow and tied to the utilisation-certificate rules; a private clinic should not build its process around them.

## How long does Corrigendum 7 apply?

The stated period is **April through September 2026**, and payment remains subject to available scheme funds. NHA also reserves the ability to continue, modify, or otherwise change the scheme. Nothing in Corrigendum 7 guarantees an October extension.

Corrigendum 6 covered November 2025–March 2026 and was superseded by Corrigendum 7 for the following period. Neither document establishes an October 2026 rate. Use the [NHA DHIS page](https://abdm.gov.in/DHIS) as the starting point for the terms applicable to a later transaction; do not rely on this historical table to forecast one.

## What software and registration conditions apply?

HFR registration is necessary but not sufficient. Your facility must register for DHIS, use qualifying software, produce eligible transactions, and submit claims. Corrigendum 7 draws these technical boundaries:

| Participant | Corrigendum 7 record-linking gate for its stated period |
|---|---|
| Health facility or clinic | More than 100 eligible monthly transactions; KYC-verified ABHA linkage; transactions through a system integrated through M3; July 2026 onward payouts depend on the DSC's full v3 M1–M3 compliance |
| Diagnostic facility, lab, or pharmacy | More than 100 eligible monthly transactions; the corrigendum permits the role-specific transaction through M2, while the July-onward v3 rule still governs the supporting DSC and payout |
| Digital solution company | The facility generates more than 100 eligible monthly transactions; the DSC meets the original 10-facility condition, holds a valid Web Application Security Assessment report, and meets the applicable v3 rule |

The April–June transition has passed. Corrigendum 7 allowed non-v3 transactions in that period at Category 2 rates. From July 2026 onward, it says no facility or DSC incentive is payable until the DSC is fully compliant with the v3 versions of M1, M2, and M3; eligibility resumes from the following month in its examples. Ask a vendor for its production status, version, and valid WASA evidence. “ABDM-ready” is not enough for your DHIS forecast.

## Is chasing DHIS worth it for a small clinic?

For a historical Corrigendum 7 example, if all 150 eligible monthly transactions were Category 2, the gross facility calculation was ₹750 and the first-100 deduction was ₹500, leaving ₹250 before any other eligibility failure. Its mixed example reached ₹500. A clinic at 100 eligible transactions reached zero. KYC failures, repeated transactions for one ABHA, late claims, or a non-compliant vendor could reduce the amount again. Use current NHA terms for any new forecast.

For most small OPDs, DHIS is better treated as conditional upside on documentation and ABDM workflows that already make operational sense. A complete, structured, retrievable record has value every visit whether the scheme is renewed or not. It is also the raw material for an eligible ABHA-linked record. The practical order is documentation first, verified ABDM production capability second, incentive math third.

## Where does an AI scribe fit, and what won't we claim?

Right at the documentation layer, and we'll be precise about the line we don't cross.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In a Pune OPD running code-mixed Hindi and English, it captures the conversation and the note comes out in clean clinical English, every time. That clean, structured note is exactly the raw material an ABHA-linked record is built from. Faster, more complete documentation is the thing DHIS quietly rewards, because you can't link a record that was never written down properly.

Here's the line. **ABDM integration is on our roadmap, not live today.** We don't link records to ABHA inside the tool yet, we are not a DHIS-registered digital solution company, and we never call ourselves "ABDM-compliant," because we aren't. If linking records to ABHA from inside the scribe is a requirement for you right now, perhaps because you're actively chasing DHIS or AB PM-JAY workflows, then eka.care, which ships live ABDM integration across the M1 to M3 milestones, is the honest pick today, and we'd point you there for it. We're building toward it. We're not there. What we do now is make the documentation clean enough to feed whatever ABDM workflow you run, and we keep the data discipline tight: visit audio is processed in memory and discarded once the note drafts, so there's no audio archive; data is encrypted in transit (TLS 1.2+) and at rest (AES-256); access is role-scoped and logged; the notes belong to your practice, export or delete any visit anytime. We handle data to DPDP Act 2023 standards, and a SOC 2 Type II audit is underway. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing is per clinician and ex-GST, from ₹1,599 a month on the annual Assist plan, plus 18% GST (so Assist works out to about ₹1,887 a month all-in), with a 7-day free trial. The plan you're on decides what's bundled: Copilot (₹2,399/mo annual) adds an AI EHR and WhatsApp, and Autopilot (₹3,999/mo annual) adds the AI receptionist and follow-ups. If you want to see how the main India options handle data and ABDM, the [India scribe comparison](../india-ai-scribe-comparison/) lays it out, and the [2026 best-for-India breakdown](../best-ai-scribe-for-india-2026/) gives the per-situation picks with eka.care's ABDM lead conceded in full. Or just [review the India product options](/in/compare/) and ask where the audio goes, and how fast the note is ready. Then decide what, if anything, DHIS adds on top.

---

## AI Medical Scribe for Hospitalists: H&P, Progress & Discharge
https://patientsquare.com/us/blog/ai-scribe-for-hospitalists/
Published 2026-06-18 · Updated 2026-08-27 · Tags: ai-scribe, hospitalist, inpatient, specialty

How an AI scribe fits the hospitalist day: H&P on admit, daily SOAP progress notes, discharge summaries, and transition-of-care documentation.

Yes. The scribe listens during the admission interview and hands back a structured H&P draft (chief complaint, HPI, PMH/PSH/FH/SH, ROS, physical exam, assessment, and plan) about two minutes after you finish the encounter. You review and edit before signing. Nothing files automatically.

An AI scribe for hospitalists is most useful when you're on an 18-patient census, halfway through rounds, and the discharge summary for room 412 is still blank because you haven't had four consecutive minutes to sit down. Inpatient documentation is different from primary care in one specific way: the notes are longer, the stakes are higher, and you write them across a shift while still managing everything else on the floor.

This page covers how a scribe fits the three main inpatient writing tasks (the admission H&P, the daily SOAP progress note, and the discharge summary) plus the two edge cases hospitalists actually hit: overnight admits and cross-coverage on a patient you've never met.

> **Key takeaways**
>
> - The admission H&P, daily SOAP, and discharge summary each have a different structure; an AI scribe handles all three from ambient capture during the encounter.
> - On a 15-patient daily census, shaving 5-8 minutes per note across rounds is roughly 1.5-2 hours back per shift.
> - Discharge summaries are the highest-stakes note in the hospitalist chart. A scribe drafts from the discharge conversation, but a close read before signing is non-negotiable.
> - AI Medical Scribe by Patient Square is EHR-agnostic: it hands you a drafted note, you paste it into Epic, Cerner, or whatever the hospital uses. No IT project, no enterprise rollout.
> - Plans start from $79/month per clinician (annual Assist), with an assisted 7-day trial after workspace setup. No EHR integration project is required.

Book a demo to see what the H&P and progress note drafts actually look like on your case type.

## The hospitalist documentation problem is about note type, not note count

Primary-care physicians write short notes quickly on the same visit type all day. Hospitalists write three substantially different note types in a single shift: the long H&P on admit, the shorter but still-demanding daily progress note on each patient, and the full-hospitalization-synthesizing discharge summary that can run three pages.

The AMA's data on EHR burden (5.8 hours of EHR time per 8 hours of scheduled patient care) was collected across ambulatory settings. Inpatient documentation sits in a different category: notes are longer by design, often require citing prior documentation in the chart, and carry real downstream liability. They're what the outpatient doctor reads when the patient follows up the next week.

That's the specific problem an AI scribe addresses for hospitalists. Not the number of notes, but the time-per-note on documentation that genuinely has to be detailed.

## Admission H&P: the 20-minute note nobody has 20 minutes for

The H&P is the most time-intensive note in hospital medicine. You need chief complaint, full HPI, PMH/PSH, family history, social history, medication reconciliation, review of systems, physical exam findings, differential, assessment, and plan. A thorough one takes 15-25 minutes to write even when you know the patient. Typing it from memory after a busy admit, at midnight, is where things go wrong: the note gets abbreviated, the ROS is templated, and the physical exam is copied from triage.

With an ambient scribe running during the admit interview, you have a different process. You talk to the patient the way you always have. You do the physical exam. You think out loud a little more naturally. Two minutes after the encounter ends, you have a draft H&P structured across the standard sections: HPI in paragraph form, ROS by system, exam with your findings, assessment and plan.

You still have to read it. You still have to catch what the audio missed (the silent stethoscope, the exam finding you noted in your head but didn't say out loud). But reading and editing a structured draft is 5-10 minutes of work, not 20. At midnight, that's the difference between writing the note in-house and writing it at 2am when you get home.

## Daily progress notes: rounding faster when the chart writes itself

On a 15-patient census, the progress notes for rounds are the single biggest documentation time block in the hospitalist day. Each note should document what happened overnight, the current assessment across active problems, and the plan going forward. Most hospitalists know how long it actually takes to write a proper progress note versus how long the template-and-sign version takes. The ones written by the book are the ones that protect you when something goes wrong.

Here's what the scribe workflow looks like on rounds:

1. You walk into room 7, greet the patient, ask how the night was.
2. The patient tells you: the pain is better, they had a rough time sleeping, they're asking about going home.
3. You do a quick focused exam, note what you find verbally as you go.
4. You step out, and the scribe hands you a SOAP note: subjective (what the patient reported), objective (vitals, exam), assessment, plan.
5. You read it in the hallway, make your edits, paste it into the chart.

On a 15-patient day, if that process trims even 5 minutes per note, you get 75 minutes back. The 2025 UCLA randomized trial in NEJM AI measured roughly 41 seconds per note for one ambient tool across a mixed clinical setting. Hospitalist notes typically run longer than a short primary-care visit note, so the per-note savings may differ. Even conservatively, the arithmetic is favorable across a full census.

The more important win is note quality. A scribe captures what was actually said in the room. It doesn't paste last Tuesday's plan into today's note.

## Discharge summaries: the highest-stakes note in the hospitalist chart

Discharge summaries are where ambient scribes have the clearest upside and where the hospitalist has to stay most engaged.

The note synthesizes the entire hospitalization: admitting diagnosis, course of events, procedures, the labs that mattered, medications started or stopped, and the follow-up plan. It's what the outpatient cardiologist, PCP, or SNF reads when the patient arrives. Errors in discharge summaries create downstream harm: medication errors, missed follow-ups, duplicated workups.

An AI scribe helps by capturing the discharge conversation. You talk through the course with the patient or family, review what happened, explain follow-up. The scribe drafts from that conversation, giving you a structured starting point instead of a blank field.

The disciplined rule for discharge summaries: read every line before signing. The scribe drafts from the conversation you had during the discharge visit; it doesn't have access to the chart. You need to add the labs that mattered, confirm medication reconciliation is accurate, and verify the follow-up plan is complete. Use the draft as scaffolding, not a finished product.

When it works well, discharge summaries go from a 20-minute note written at the end of a long day to a 10-minute review and edit of a drafted document. That's the real time return.

## Overnight admits and cross-coverage: where the math is sharpest

Hospitalists writing notes on a 2am admit already know the baseline: you see the patient, you think through the case, and then you have to write a note on a clinical situation you're still organizing in your head, while exhausted, under time pressure to get to the next admit.

The note is often the part that suffers. Not because hospitalists cut corners intentionally, but because note-writing at 2am is genuinely hard.

An ambient scribe running during the admit interview does something useful here. You talk through the case with the patient, which you'd do anyway. The scribe drafts. You read a structured H&P instead of starting from scratch. The notes written at 3am start to look like the notes written at 11am.

Cross-coverage is similar. You're seeing a patient you don't know, documenting a conversation with someone else's patient at the end of a long call shift. The scribe captures exactly what the patient told you and what you found. The note reflects that encounter, not a reconstruction from memory six hours later.

## How it fits a hospital medicine workflow (EHR-agnostic)

The thing most hospitalists ask about first is the EHR. Epic is in most major hospitals. Cerner is in many. Some systems are on Meditech or a custom build.

AI Medical Scribe by Patient Square doesn't integrate with any of them. It works alongside your EHR.

That means: you run the scribe on your phone or laptop during the encounter. It hands you a drafted note as a text output. You copy it, paste it, or retype it into whatever your hospital's system uses. No IT project. No waiting for an Epic-IT meeting to clear an integration. No hospital contracts. You start using it the day you sign up.

For a hospitalist employed by a group or working at multiple facilities, that portability is worth naming. The scribe works the same way regardless of which hospital's EHR you're on.

What the scribe produces: a structured SOAP note or H&P, ICD-10 suggestions (not a coding engine; you review and confirm), and a prescription draft if medications came up in the encounter. Nothing files automatically. You review and sign before anything enters the chart.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Hospital-wide deployments run on Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. A hospitalist evaluating the standalone scribe module can start on the Practice Copilot plans.

Audio is processed in memory and discarded once the note is drafted. There is no audio archive. Data is encrypted in transit and at rest; notes belong to your practice, and you can export or delete any visit.

## What an inpatient note type comparison looks like

| Note type | Avg draft-from-scratch time | With AI scribe draft | What you still do |
|---|---|---|---|
| H&P (admission) | 15–25 min | 5–10 min review/edit | Add silent exam findings; verify med rec |
| Daily progress note | 4–8 min | 2–3 min review/edit | Confirm overnight data; update plan |
| Discharge summary | 15–25 min | 8–12 min review/edit | Add chart data; verify med rec + follow-up |
| Cross-coverage note | 6–12 min | 3–5 min review/edit | Confirm what patient said vs chart |

*Draft times estimated from clinical workflow literature and hospitalist-reported norms; per-hospitalist variation is real. The scribe captures the encounter conversation; you supply what the ambient audio couldn't hear.*

On a shift with 15 progress notes, 2 admissions, and 1 discharge summary, the arithmetic across those rows is meaningful. Even the conservative end of the range returns an hour or more per shift.

## Who should look at this seriously

If your current workflow includes any of these, the scribe is worth a trial:

- Progress notes that don't get written until after rounds because you ran out of time during rounding
- Discharge summaries sitting blank at 4pm because the patient is ready to leave but the note isn't
- Overnight admit notes that are abbreviated versions of what they should be
- Cross-coverage notes that are mostly a template with minimal specifics

The hospitalists who get the most out of it tend to have a specific pain point rather than a vague "documentation takes too long." If you know which note type is eating your shift, the scribe can target that.

The [AI scribe evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) covers the 9 questions worth asking any scribe vendor: audio handling, note quality, EHR posture, export rights, pricing transparency. Worth running through before you commit to anything.

For comparison with how the scribe performs in a higher-volume outpatient setting, the [primary care day-in-the-life model](../ai-scribe-for-primary-care/) runs the same arithmetic on a 20-patient ambulatory day.

Pricing runs on three plans per clinician: Assist at $99/month ($79 on annual billing), Copilot at $149 ($119 annual), and Autopilot at $249 ($199 annual). The scribe is the Assist plan; the bundled AI EHR, messaging, and receptionist and follow-up automation arrive as you move up. Full pricing with no asterisks is on the [pricing page](../../pricing/). The assisted trial is 7 days and begins after workspace setup.

If you want to see what the H&P and discharge summary drafts look like on a real case type before committing, book a demo and we'll walk through it with inpatient examples.

---

## SimplePractice Alternatives: Ambient Notes for Therapists
https://patientsquare.com/us/blog/simplepractice-alternatives/
Published 2026-06-18 · Updated 2026-08-27 · Tags: alternatives, behavioral-health, simplepractice, comparison

Compare SimplePractice with options for therapists who want ambient notes drafted from sessions, including a bundled AI EHR from $119.

Not a true ambient one. SimplePractice offers an AI Note Taker add-on at about $35 a month, but its core strength is behavioral-health practice management: scheduling, billing, telehealth, and client portals. If your main pain is writing progress notes after every session, an ambient scribe that drafts the note from the visit itself is a different and more direct fix.

If you're a therapist searching for a SimplePractice alternative, it usually comes down to one thing: the notes. SimplePractice runs behavioral-health admin well, scheduling, billing, client portals, but it doesn't draft your progress note from the session. Its AI Note Taker is a $35-a-month add-on, not a true ambient scribe. If writing notes after every client is what's eating your evening, Patient Square's Copilot plan is **$119 per provider per month** annually with a real ambient scribe bundled in. You can watch it draft a note in about two minutes before you decide.

Fair warning up front: Patient Square isn't behavioral-health-specific, and SimplePractice is. That's the honest trade this page walks through.

> **Key takeaways**
>
> - SimplePractice's plans run about $49 (Starter), $79 (Essential), and $99 (Plus), before add-ons.
> - The AI Note Taker is a ~$35/month add-on; ePrescribe is ~$49/month plus an $89 setup fee.
> - SimplePractice's edge is therapy-native admin, not ambient documentation.
> - Patient Square Copilot is $119/provider monthly (annual) with an ambient scribe and bundled AI EHR, no per-note meter.
> - SimplePractice still wins for therapists who need behavioral-health templates, insurance panels, and superbills out of the box.

## SimplePractice alternatives at a glance

The field splits by whether your pain is admin or documentation.

| Alternative | Best for | Ambient scribe | Published starting price |
|---|---|---|---|
| SimplePractice (staying) | Therapy-native admin, panels, superbills | Add-on note-taker (~$35/mo) | $49–$99/mo |
| Patient Square Copilot | Therapists who want notes drafted from the session | Yes, bundled | $119/provider/mo (annual) |
| General EHR + separate scribe | Custom stacks | Separate subscription | Varies |

Competitor figures are published or third-party as of this writing; confirm before you sign. This table is direction, not a quote.

If the notetaking is your problem, start with the ambient option. If it's the insurance and superbill workflow, SimplePractice's therapy-native tooling is genuinely hard to beat.

## Why the AI Note Taker isn't the same as an ambient scribe

SimplePractice's AI Note Taker helps, and for some clinicians it's enough. But it's an add-on layered onto a practice-management tool, and it prices separately at about $35 a month. Stack that with ePrescribe at roughly $49 a month plus setup, and an additional-clinician fee near $74, and the "starts at $49" headline drifts.

An ambient scribe works differently. It listens during the session and hands back a structured note the moment you're done. You're not filling a template after the fact; the draft is already there. For a therapist doing seven or eight sessions a day, that's the difference between charting until 7pm and closing your laptop when your last client leaves.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The AI Copilot EHR ships at the **Copilot tier, $119 per provider per month** annually. Book a demo and run it against a real talk-based visit to see if the note holds.

## What an ambient scribe changes for a talk-heavy practice

Behavioral-health visits are conversation, start to finish, which is exactly what ambient capture is built for. Practically:

- **The note drafts from the session.** Ambient capture during the visit, structured note ready roughly two minutes after you finish.
- **Unlimited notes, no per-session meter.** A full day of clients costs the same as a light one.
- **A prescription draft** for prescribers, reviewed and signed by you. It's a draft, not automated pharmacy transmission.
- **Audio is never stored.** It's processed in memory and discarded once the note drafts, which matters for the privacy expectations of mental-health work.
- **One bundled bill** for the scribe and the record system, rather than a base plan plus a note-taker add-on plus an e-prescribe add-on.

The privacy piece deserves a line of its own. Mental-health sessions are sensitive, and a scribe that keeps no audio archive is a cleaner story to tell a client than one that retains recordings. Patient Square's safeguards are HIPAA compliant, with BAAs available for every customer. For the broader specialty view, our [best EHR for psychiatry](/us/blog/best-ehr-for-psychiatry/) page covers prescriber-side behavioral health.

## When SimplePractice is the better choice

Here's the honest concession. Stay with SimplePractice if your practice lives on therapy-native admin. It ships treatment-plan templates, superbills, insurance-panel workflows, a polished client portal, and telehealth built for behavioral health. Patient Square doesn't replicate that. If your daily friction is claims, panels, and client-facing scheduling rather than note-writing, SimplePractice is the tool that fits, and switching away would trade a workflow you rely on for a scribe you might not need.

SimplePractice is also the safer pick if you bill insurance heavily and lean on its claims tooling. Patient Square offers ICD-10 suggestions, not a claims-management engine. Match the tool to the pain that actually costs you time.

For therapists whose main complaint is documentation load, though, the math tilts the other way: the bundle drafts the note and holds the record, and the note-writing evening goes away.

## How to decide in a week

Test it on real sessions, not a demo script:

1. Name your worst daily friction: notes, or admin. That picks your category.
2. If it's notes, shortlist tools with a *built-in* ambient scribe, not an add-on note-taker.
3. Export a sample of your SimplePractice data to confirm the migration path is clean.
4. Run the new tool's 7-day trial across a real week of sessions.
5. Compare the finished note to what you'd have written yourself. That's the decision.

The receipts, encryption, access, and audit status, are on the [security page](/us/security/), and the full price ladder is on the [pricing page](/us/pricing/). Book a short demo to see the note against a real talk-based visit, then run the 7-day trial before moving any clients. If notetaking is what's stealing your evenings, an ambient scribe fixes the exact problem SimplePractice's admin tools were never built to solve.

---

## AI Scribe for Therapists: Consent, DAP, and BIRP Notes
https://patientsquare.com/us/blog/ai-scribe-for-therapists/
Published 2026-06-17 · Updated 2026-08-29 · Tags: ai-scribe, therapists, behavioral-health, dap, birp

How therapists (LCSW, LPC, LMFT) use an AI scribe to finish DAP and BIRP notes during the session gap, not at 10pm. Workflow, privacy, and a trial plan.

Some vendors support DAP or BIRP templates, but don't infer that from the term AI scribe. Patient Square publicly claims specialty-aware templates and a structured SOAP output, not a guaranteed DAP or BIRP workflow. Ask for the exact format, run a sample, and reject the tool if you must rebuild the note structure after every session.

An AI scribe for therapists captures a consented session and drafts a clinical note for the therapist to review. It should not be assumed to support DAP, BIRP, sensitive-session minimization, or a particular EHR handoff until those are tested. Some sessions should not be recorded at all. Patient Square publicly claims a structured SOAP note and specialty-aware templates, not a guaranteed DAP or BIRP output.

> **Key takeaways**
>
> - A 2023 National Council for Mental Wellbeing survey found 93% of behavioral health workers reported burnout, with documentation cited as a named driver.
> - Treat DAP and BIRP as acceptance tests, not assumed formats. Patient Square's public output claim is structured SOAP with specialty-aware templates.
> - Audio is processed in memory and never stored; the note, not the recording, is what remains.
> - Payer status doesn't decide whether capture is appropriate. Consent, sensitivity, modality, documentation purpose, and the client do.
> - Use a one-week failure log. There is no universal trial length or guaranteed time saving.

## Why after-hours documentation needs a real test

A 2023 National Council for Mental Wellbeing survey found that 93% of behavioral health workers reported burnout, and it named documentation as a contributing pressure. That finding does not establish a standard number of after-hours note minutes for therapists. Caseload, note policy, session type, and the workflow between sessions all change the answer.

Measure your own baseline before the trial. For one week, record the time from session end to a signed note, then separate drafting from review and correction. That gives the practice a comparison it can actually use.

## DAP notes and BIRP notes: what the scribe actually drafts

These are common outpatient therapy structures, but the product label doesn't prove either one. If your practice uses them, turn the format into an acceptance test. The linked [DAP note guide](../dap-note/) and [BIRP note guide](../birp-note/) explain the structures you can use for a synthetic sample.

For DAP, check whether the draft separates reported or observed data from the therapist's assessment and the forward plan. An assessment that merely repeats the client's words isn't enough. A plan that invents an intervention is worse.

For BIRP, check whether behavior, intervention, response, and plan remain distinct. The draft must not turn an inference into observed behavior or invent a client response. Use a synthetic session first, then a consented real session if the format survives.

Patient Square's public claim is a structured SOAP note, ICD-10 suggestions, and a prescription draft for review, plus specialty-aware templates. It does not publicly promise a DAP or BIRP output. If a trial evaluation cannot produce your required structure, a dedicated behavioral-health EHR or another scribe is the better fit.

One format note: the standard progress note a scribe drafts is not a "psychotherapy note" as HIPAA defines that term. Under 45 CFR § 164.501, psychotherapy notes are the clinician's separately-kept process notes analyzing a session. The Privacy Rule separately requires authorization for most uses and disclosures of psychotherapy notes under 45 CFR § 164.508. Keep the regular progress note and separately kept psychotherapy notes distinct in the practice policy.

## Self-pay therapy and documentation choices

Payer status does not decide what a therapist should capture. The practice still needs a documentation policy that reflects its jurisdiction, license, contracts, continuity needs, and the client's consent. The therapist decides what belongs in the official progress note and what remains outside it.

An AI scribe can draft from a consented session in either payment model. It does not submit claims, and Patient Square's ICD-10 output is suggestions for review, not a coding or billing engine.

## The consent, minimization, and do-not-record tree

This is the artifact to use before every session. It is stricter than a blanket consent form because context can change from one visit to the next.

| Decision | If yes | If no or uncertain |
|---|---|---|
| Does the client understand what is captured, why, what remains, and that refusal won't block care? | Record the choice according to clinic policy | Don't start capture; use the normal documentation path |
| Is capture appropriate for this session's sensitivity and modality? | Continue to the minimum-necessary check | Don't record crisis, intimate, legal, multi-party, or otherwise sensitive work merely because standing consent exists |
| Can unnecessary details be excluded from the official record? | Tell the system and reviewer what belongs in the progress note | Use manual documentation if minimization cannot be trusted |
| Are every participant's identity and permission clear? | Record the participants and proceed under policy | Stop when a caregiver, partner, group member, or unexpected person changes the consent context |
| Is the therapist able to pause or stop immediately? | Test the control before the session | Don't use the tool until stop behavior is reliable |
| Does the draft keep progress-note content separate from psychotherapy process notes? | Review against the practice's record policy | Use a dedicated workflow or write manually |
| Can the reviewed note reach the system of record without exposing extra session data? | Complete and log the handoff | Keep the current EHR or dedicated behavioral workflow |

Run a baseline week and a trial week. For each consented session, record whether capture was used, minutes to a signed note, omissions, invented facts, over-disclosure, format repair, and handoff failure. For each session not captured, record only the category of reason, not sensitive details. We think the do-not-record count is a quality signal, not a product failure.

Use a real therapy-visit trial: begin with a synthetic DAP or BIRP sample, then capture only consented routine sessions under your clinic policy. Request your 7-day trial when the therapist, consent process, note standard, and stop rule are ready.

## HIPAA in a therapy practice

The confidentiality stakes in therapy are higher than in most other clinical settings. What's said in a therapy session is personal in a way that a blood pressure reading isn't. So the question of where the audio goes matters more here than in a lot of specialties.

With AI Medical Scribe by Patient Square: the audio is processed in memory during the session and discarded once the note draft is generated. There is no audio archive, no replay capability, no server-side retention of the recording. The note is what exists. Notes are encrypted at rest (AES-256) and in transit (TLS 1.2+), access is role-scoped and logged, and the notes belong to your practice. You can export or delete any session record at any time.

Patient Square is HIPAA compliant, Business Associate Agreements are available, and SOC 2 Type II is in progress. None of that makes a therapy workflow automatically compliant. The practice still owns consent, minimum necessary use, access, devices, retention, and incident procedures. The [security page](/us/security/) gives the current platform posture.

If you need to understand how a scribe's note differs from the HIPAA definition of a psychotherapy note, or how 42 CFR Part 2 might apply if you treat substance use disorder, the live [psychiatry and privacy post](../ai-scribe-for-psychiatry-privacy/) covers that in detail. Those regulatory questions sit in a different clinical domain from the DAP/BIRP talk-therapy workflow, so we've written them separately.

## Notes templates versus an ambient scribe: what you're trading

A lot of therapists use note templates, sometimes built into their EHR, sometimes a Google Doc they've refined over years. Templates are fast for routine sessions. They're slower and more error-prone when the session goes somewhere unexpected, which therapy sessions often do.

With a template, you reconstruct the session from memory and fit it into a fixed structure. With a scribe, you review a draft that came from the actual session. Routine days? The template might be faster. Complex sessions (a dissociation episode, a crisis disclosure, a breakthrough after six months of flat affect), the scribe gives you a starting point grounded in what actually happened, not a blank form you fill at 9pm from a fading memory.

For a deeper look at when to use templates versus when to step away from them, the [therapy notes template guide](../therapy-notes-template/) covers the tradeoffs.

## One careful week gives you evidence

AI Medical Scribe is one module inside Practice Copilot. It captures the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft for review around two minutes later. For a therapy buyer, the SOAP limitation matters. DAP or BIRP fit must be demonstrated rather than assumed.

You remain the clinical author. Review what is accurate, remove unnecessary detail, correct what is wrong, and sign only when the record reflects your judgment. The tool doesn't decide whether the session should be captured.

Pricing runs on three plans per clinician: Assist at $99 monthly or $79 on annual billing, Copilot at $149 or $119 annual, and Autopilot at $249 or $199 annual. Copilot adds the bundled AI Copilot EHR and WhatsApp messaging. Autopilot adds the named AI Receptionist and AI Follow-ups modules. The full breakdown is on the [pricing page](/us/pricing/), which also states a seven-day free trial.

A one-week test can show whether the workflow deserves more time. Use synthetic material first, then consented sessions under clinic policy. If DAP or BIRP structure fails, sensitive details spill into the note, or review takes longer than the baseline, stop. A dedicated behavioral-health EHR may be the better fit.

Start with the synthetic session, then use consented routine visits and the same review log for one week. Request your 7-day trial only if the therapist can stop capture, decline capture for sensitive sessions, and review every draft before it becomes part of the clinical record. The [therapist EHR guide](/us/blog/best-ehr-for-therapists/) covers the system-of-record decision this page intentionally does not own.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot works alongside it. A new practice can instead use the bundled Patient Square EHR, available from the Copilot tier, as its system of record. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## Sunoh.ai Alternatives: Beyond the eCW Ecosystem
https://patientsquare.com/us/blog/sunoh-ai-alternatives/
Published 2026-06-17 · Updated 2026-07-22 · Tags: ai-scribe, comparison, sunoh-ai, pricing

Sunoh.ai runs $149/user/mo and is tied to eClinicalWorks. When a scribe from $79/mo that exports to any EHR, with a bundled AI EHR from $119/mo, fits a practice better.

Sunoh.ai publishes $149 per user per month, described on its site as a limited-time rate down from $199, with a free trial. It's a paid add-on for eClinicalWorks users, not a bundled feature. Patient Square's scribe starts at $79 per clinician per month on annual billing, undercutting Sunoh's published rate, with a bundled AI EHR available from $119/mo at the Copilot tier.

Sunoh.ai is a solid scribe if you live inside eClinicalWorks. It's also $149 per user per month and tied to that ecosystem, sold as an add-on rather than a standalone tool. If you want a lower published price, EHR flexibility, or a bundled chart, the alternative worth naming isn't locked to one vendor. Patient Square's scribe is $79 per clinician per month on annual billing, undercutting Sunoh's rate, exports to any EHR, and bundles an AI EHR from $119/mo at the Copilot tier. See the ladder on our [pricing page](../../pricing/), or book a demo.

This isn't a Sunoh takedown. For an eCW shop, it's a good fit. Below: the price and ecosystem tradeoffs, a side-by-side, and when staying in eCW's world is the right call.

> **Key takeaways**
>
> - Sunoh.ai publishes $149 per user per month, a limited-time rate down from $199, as an eClinicalWorks add-on with a free trial.
> - Patient Square's scribe starts at $79 per clinician per month on annual billing, below Sunoh's published rate, with unlimited notes.
> - Sunoh is built for the eCW ecosystem. Patient Square's note exports EHR-ready (PDF, HL7, FHIR) and the Copilot tier bundles its own AI EHR.
> - Both are flat monthly, not per encounter. Sunoh's older per-visit pricing no longer appears on its site.
> - When you're staying on eClinicalWorks, Sunoh's native fit is a real edge. We say so below.

## How does Sunoh.ai compare to Patient Square?

Here's the side-by-side. Sunoh's price is published, so this is a clean comparison, not an estimate.

| | Sunoh.ai | Patient Square |
|---|---|---|
| Published price | $149/user/mo (limited-time, from $199) | $79 / $119 / $199 per clinician/mo, annual |
| Entry price | $149/mo | $79/mo (Assist) |
| Ecosystem | eClinicalWorks add-on | EHR-agnostic; exports to any EHR |
| Bundled EHR | No; extends eCW | Yes, AI Copilot EHR from $119/mo |
| Clinical output | SOAP note, ambient capture | SOAP note, ICD-10 suggestions, Rx draft |
| Best fit | Practices committed to eCW | Practices wanting a lower price or EHR flexibility |

If you're not locked to eCW, book a demo and see an EHR-agnostic scribe on your own visits before you buy into one ecosystem.

## Price and ecosystem: what's the real tradeoff?

Two things separate these tools: the number and the lock-in.

On price, this is a rare clean comparison, because both vendors publish. Sunoh.ai lists $149 per user per month on its site, a limited-time rate down from $199, with a free trial. That's transparent, and we'll give it credit for that. Patient Square's scribe starts at $79 per clinician per month on annual billing, below Sunoh's published rate, with unlimited visits and notes. One older wrinkle: Sunoh's 2024 marketing referenced a per-visit rate, but the current site shows the flat monthly figure, so treat it as flat monthly today.

On ecosystem, Sunoh is built and sold within eClinicalWorks. It's a paid add-on, not a bundled feature, and its tightest fit is for eCW practices. That's an advantage if you run eCW and you're staying. It's a risk if you don't, or if you might switch EHRs later, because your scribe is tied to a system you may leave.

Patient Square stays EHR-agnostic. The note exports EHR-ready (PDF, HL7, FHIR), so it works with whatever chart you keep, and the Copilot tier bundles its own AI Copilot EHR from $119/mo if you'd rather have the record system in the same subscription. Read the whole ladder on the [pricing page](../../pricing/).

## What do you keep leaving Sunoh for an EHR-agnostic scribe?

The trade is native fit versus flexibility.

You give up eCW-native workflow depth. Sunoh lives inside eClinicalWorks, so for an eCW practice, the integration is tighter than a general-purpose tool will match. If eCW is your permanent home, that fit is worth something.

What you keep is portability and a lower entry price. The AI Medical Scribe by Patient Square is one module inside Practice Copilot, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The note exports EHR-ready (PDF, HL7, FHIR), so switching EHRs doesn't strand your scribe, and the Copilot tier bundles a chart if you want one. Audio is processed in memory and discarded once the note drafts. A BAA is available for every customer.

If you're comparing more scribes, [DeepScribe alternatives](../deepscribe-alternatives/) covers the enterprise, sales-led end, and [Nabla alternatives](../nabla-alternatives/) covers the free-tier-and-caps end. If the eClinicalWorks total cost is the question behind the Sunoh question, [eClinicalWorks cost](../eclinicalworks-cost/) breaks down what eCW plus its add-ons actually runs per month.

## When is Sunoh.ai the better choice?

It's about your EHR commitment.

Choose Sunoh.ai if you're already on eClinicalWorks and staying. A scribe built for your exact ecosystem fits the workflow more natively than a general-purpose tool can, and that native fit is a real reason to keep it inside the eCW stack.

Choose an EHR-agnostic scribe if you want a lower published price, the freedom to change EHRs without losing your scribe, or a bundled record system in one subscription. If you're not permanently married to eCW, that flexibility is worth more than ecosystem-native depth you may not keep. And at $79 to start, the entry price is lower too.

## How to decide in a week

Run the real test.

1. Decide how committed you are to eClinicalWorks. If it's your permanent EHR, Sunoh's native fit is a strong reason to stay in the ecosystem.
2. If you're EHR-flexible or price-sensitive, shortlist EHR-agnostic tools with published prices.
3. Compare the published numbers directly. Both vendors publish, so there's no estimate to hedge here.
4. Check EHR export: PDF, HL7, FHIR, so your scribe survives an EHR change.
5. Settle the audio question: stored or not, and for how long. Ours is never stored.

The receipts behind our claims are on the [security page](../../security/), and the full price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visit type, then run the 7-day trial on a real clinic week. If eCW is your home for good, Sunoh's native fit is your edge. If you want a lower price and EHR freedom, the EHR-agnostic route is what you're shopping for.

---

## TPA, IRDAI, Cashless: A Plain-English Glossary for Clinics
https://patientsquare.com/in/blog/tpa-full-form-cashless-explained/
Published 2026-06-17 · Updated 2026-07-22 · Tags: tpa, irdai, cashless, glossary, india

TPA full form, IRDAI full form, cashless vs reimbursement, and pre-auth — explained for clinic staff, with the IRDAI rules and where your notes fit in.

TPA stands for Third Party Administrator. The IRDAI defines it as a company registered with the Authority and engaged by an insurer, for a fee, to provide health services. In practice the TPA runs the cashless desk, processes pre-authorisation requests, and settles claims on the insurer's behalf. It does not sell the policy and cannot reject a claim on its own.

If you run a clinic in India, three letters decide a lot of your front-desk day: TPA. The full form is Third Party Administrator, the company an insurer hires to run its cashless desk and process claims. IRDAI is the Insurance Regulatory and Development Authority of India, the regulator that sets the rules those desks follow. This is the plain-English glossary for the words that show up on every pre-auth form, with the IRDAI rules that actually bind and the one place your clinic touches the chain: the note.

> **Key takeaways**
>
> - TPA full form: Third Party Administrator, the insurer's agent for cashless and claims. It cannot reject a claim on its own; only the insurer can.
> - IRDAI full form: Insurance Regulatory and Development Authority of India, the statutory regulator behind the cashless timelines.
> - Cashless vs reimbursement: cashless settles the bill directly via pre-auth; reimbursement pays the patient back after documents.
> - The IRDAI Master Circular (29 May 2024) sets a 1-hour cashless and 3-hour discharge clock, and bars rejecting claims for "want of documents".
> - This is a glossary, not a sales page. Where notes help is narrow and real: a cleaner pre-auth, processed faster.

_Sources: IRDAI Policyholder portal (TPA); IRDAI Master Circular on Health Insurance Business, 29 May 2024._

## What is the full form of TPA, and what does a TPA actually do?

TPA stands for Third Party Administrator. The IRDAI's own definition is precise: a TPA is "a company registered with the Authority and engaged by an insurer, for a fee... for providing health services." Read that twice. The TPA works for the insurer, not for you and not for the patient. It is the operations arm the insurer outsources the paperwork to.

Day to day, that means three jobs your clinic sees. The TPA issues the patient's health card and ID. It runs the cashless desk: receiving pre-authorisation requests, asking for clarifications, and approving or escalating them. And it processes the claim through to settlement on the insurer's behalf. When your billing desk uploads documents to a portal or waits on a pre-auth approval, it's usually talking to a TPA, not the insurer directly.

Here's the part most clinic staff get wrong, and it's worth getting right. A TPA cannot reject a claim. Under IRDAI's rules a TPA can assess a claim, query it, and tell the insurer it looks inadmissible, but the actual denial or repudiation has to come from the insurer, with reasons stated against the policy conditions. So when a cashless request comes back declined "from the TPA," the decision underneath it is the insurer's. That distinction matters when you're deciding who to escalate to.

## What is IRDAI, and why does it matter to a clinic?

IRDAI is the Insurance Regulatory and Development Authority of India. It's the autonomous statutory body under the Ministry of Finance that regulates the whole insurance industry, set up under the IRDA Act of 1999. Insurers answer to it. TPAs are licensed by it. The cashless rules your hospital works against are written by it.

You'll see the name on circulars, and one circular matters more than the rest right now. The IRDAI Master Circular on Health Insurance Business, dated 29 May 2024 (reference IRDAI/HLT/CIR/MISC/77/05/2024), pulled 55 older circulars into a single rulebook and rewrote how cashless is supposed to run. If anyone at your clinic argues about a cashless timeline or a document demand, that circular is the document to point at.

| Term | Full form / meaning | Who it is to your clinic |
|---|---|---|
| TPA | Third Party Administrator | The insurer's agent that runs cashless and processes claims |
| IRDAI | Insurance Regulatory and Development Authority of India | The regulator that licenses insurers and TPAs and sets the rules |
| Pre-auth | Pre-authorisation | The request, built from your notes, that asks the insurer to approve cashless |
| Cashless | Direct bill settlement via pre-auth | Insurer pays the hospital; patient pays little at discharge |
| Reimbursement | Pay-then-claim | Patient pays, then claims the money back with documents |
| Master Circular | IRDAI consolidated health-insurance rulebook (29 May 2024) | The current rules on cashless timelines and claim handling |

## Cashless or reimbursement: what's the difference, in practice?

Two ways a health-insurance claim gets paid, and the difference is mostly about who's out of pocket and when.

Cashless is the one everyone wants. The hospital sends a pre-authorisation to the TPA before or at admission, the insurer approves a sum, and the bill gets settled directly between insurer and hospital. The patient pays the deductibles and the non-covered bits, and walks out without funding the whole stay. The catch is that it only works at a hospital the cashless arrangement covers, and it lives or dies on that pre-auth being approved.

Reimbursement is the fallback. The patient pays the hospital in full, collects the bills, discharge summary, and reports, and files a claim afterwards to get the money back. No pre-auth gate, but the patient carries the cash and the paperwork, and waits for the refund. Even now, a large share of claims still go this route: when the General Insurance Council launched its "Cashless Everywhere" push in January 2024, it noted only about 63% of customers opt for cashless, with the rest on reimbursement.

On "Cashless Everywhere" itself, one clarification, because clinics get sold a fuzzy version. It's an initiative by the General Insurance Council, the industry body of non-life insurers, launched on 24 January 2024 to extend cashless even to hospitals outside an insurer's network, subject to policy terms and prior notice. It's an industry promise, not an IRDAI circular. Useful to know which is which when a patient quotes it at your desk.

## What does the IRDAI Master Circular require on cashless?

The 29 May 2024 circular put a clock on the cashless process. Two deadlines shape your discharge desk.

_Sources: IRDAI Master Circular on Health Insurance Business, 29 May 2024; General Insurance Council press release, 24 January 2024._

The insurer has to decide a cashless authorisation request within one hour of getting it. At discharge, final authorisation has to come within three hours of the hospital's request, and if the insurer drags past that three-hour mark, it bears the extra hospital charges from the delay. The point of both rules is the same: stop patients sitting on a bed waiting for an approval that should have been quick.

There's a second rule on the circular that you have to read correctly, because it's easy to twist. Insurers are barred from rejecting a claim for "want of documents." The required documents are meant to be sorted at the proposal stage, and where something is missing for a claim, the insurer or TPA is expected to collect it from the hospital rather than bounce the claim back at the patient. We'll come back to why this rule shapes exactly what good documentation can and can't do for you.

## Where does a clinic's documentation fit in this chain?

Right at the start of it. Walk the cashless path backwards and you land on the note. The insurer decides on a pre-authorisation. The pre-auth is assembled by the hospital's insurance desk. And that desk builds it from what the treating doctor wrote: the diagnosis, the clinical indication for the treatment, and the plan. The note is the source document for the whole request.

So the honest, narrow benefit of good documentation is about speed, not rejection. Because IRDAI bars rejecting a claim for missing documents, a clean note does not "stop your claims from being rejected for paperwork." That's not a thing the rules allow in the first place. What a complete, internally consistent note does is give the pre-auth desk a request that's approvable on first read, which is what lets it clear that one-hour and three-hour clock without a round of queries. Faster, cleaner cashless. Fewer documentation back-and-forths. That's the real mechanism, and it's worth being exact about it.

What documentation cannot touch is the policy. A complete note doesn't lift a sub-limit, waive a waiting period, or cover an excluded treatment. Those are insurance terms, decided by the insurer against the policy, and no note quality moves them. Anyone selling you software that "gets your cashless approved" is blurring that line. The note affects how fast and how cleanly a covered, admissible claim gets processed. It does not decide admissibility.

## Where does an AI scribe sit, and what it does not do

This is a glossary, so let's be plain about the product behind this site and draw the boundary hard. The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

Notice what's not in that sentence. It does not submit claims. It does not file pre-authorisations. It does not connect to any TPA, insurer, or hospital claims system. There's no claims rail here, on the roadmap or off it. The scribe writes the clinical note, full stop. The benefit to cashless is upstream and indirect: a complete, consistent note is better raw material for whoever prepares the pre-auth, so the request is cleaner and clears the IRDAI clock with fewer queries. The ICD-10 outputs are suggestions for your coder or billing desk to confirm, not a coding engine and not a billing submission.

That's the whole claim, and it's deliberately small. Better notes in, faster and cleaner pre-auth out. The pre-auth desk still does its job, the TPA still processes, the insurer still decides on the policy terms. If a vendor tells you more than that about your claims, the burden of proof is on them.

## The short version, and where to go deeper

TPA is the insurer's claims-and-cashless agent. IRDAI is the regulator behind it. Cashless settles the bill directly through a pre-auth; reimbursement pays the patient back later. The 29 May 2024 Master Circular puts a one-hour and three-hour clock on cashless and forbids rejecting claims for missing documents. And the one place your clinic touches all of it is the note, where a clean record means a faster, cleaner pre-auth, not a magically approved one.

If the documentation angle is what you're chasing, the deeper reads are next door: how [notes affect cashless approvals](../ai-scribe-cashless-claim-documentation/) walks the pre-auth chain in detail, [can better notes cut claim denials](/us/blog/ai-scribe-claim-denials-documentation/) draws the same honest line on the revenue side, and the [records-as-defence read](../ai-scribe-medico-legal-documentation-india/) covers the medico-legal side of complete notes. For the data-protection duties that ride alongside, the [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) is the one to bookmark.

Use a sample of queried cashless claims to check which information was missing from the clinical record and which was missing only from the submission. Compare the indication, findings, treatment plan, and requested attachments before changing the documentation process.

---

## Using an AI Scribe Alongside Your Existing EHR
https://patientsquare.com/us/blog/ai-scribe-any-ehr-export/
Published 2026-06-16 · Updated 2026-08-29 · Tags: ai-scribe, ehr, export, workflow

A careful guide to evaluating note export beside an existing EHR, including format checks, field mapping, review, security, and ownership.

Yes. A practice can keep its existing EHR as the system of record and use Patient Square alongside it. The public claim is EHR-ready export (PDF · HL7 · FHIR). This is not a named-EHR integration, automatic filing, or a guarantee that a receiving product will accept every format or field.

An AI scribe can sit alongside an existing EHR without being integrated into it. That distinction matters. AI Medical Scribe in Patient Square's Practice Copilot can draft the clinical note while the practice keeps its current EHR as the system of record, but it does not promise automatic filing, write-back, or a connector for a named EHR.

The public portability claim is **EHR-ready export (PDF · HL7 · FHIR)**. It tells you which export formats are available. It does not tell you that a particular EHR will accept the file, map every field, or place the note in the right chart. Those are destination-specific questions, and they need a real test.

> **Key takeaways**
>
> - "Alongside" means the systems remain separate unless a specific, documented connection exists.
> - Patient Square does not promise automatic filing or named-EHR write-back.
> - An export format and a successful import are different claims.
> - Test the exact destination, fields, permissions, and failure path before rollout.
> - Patient Square EHR is available from the Copilot tier if a bundled system of record fits better.

## Map the workflow before you compare tools

Start with the record that must exist at the end of a visit. Write down who reviews it, who signs it, where it is stored, and how an error is corrected.

AI Medical Scribe by Patient Square returns a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. A draft is not a final clinical record. The clinician checks the history, exam, assessment, plan, suggested codes, and prescription details before approval. The prescription draft is not sent to a pharmacy.

If the existing EHR remains the system of record, the practice must define how the approved note gets there. The safe answer is not "it works with any EHR." The safe answer is: test the destination you actually use.

## Export is only one part of the path

An export can be useful even when the destination does not support a structured import. A PDF may support archiving or human review. HL7 or FHIR may support a structured workflow when the receiving system accepts the specific resource, message, version, identifiers, and fields involved.

That is why **EHR-ready export (PDF · HL7 · FHIR)** should not be read as certification, conformance, or universal interoperability. Patient Square does not make those broader claims on this page.

Before rollout, ask the receiving EHR vendor:

1. Which file or message types can this product accept for a clinical note?
2. Which versions, profiles, resources, and fields are supported?
3. How are the patient, encounter, author, and signer matched?
4. Where does imported text appear in the chart?
5. What happens when a required field is missing or invalid?
6. Does an import create an audit event and a visible error report?
7. Can the practice correct or remove a test record safely?

Get the answers for your licensed version and configuration. A vendor's general standards support does not prove your exact route.

## Use a non-production acceptance test

Build a small test set that reflects your real documentation. Include a routine follow-up, a long assessment and plan, a medication change, and a note with the formatting your clinicians use most.

For each note, check:

| Test | Pass condition |
|---|---|
| Clinical review | Clinician can find and correct material errors before approval |
| Patient match | Record is associated with the intended test patient and encounter |
| Structure | Headings and required fields remain readable and complete |
| Attribution | Author, reviewer, and signer are represented correctly |
| Failure handling | Staff can see an error and know what to do next |
| Audit trail | Practice can reconstruct who exported, moved, reviewed, and signed the note |
| Recovery | A bad test record can be corrected through an approved process |

Do not start with live patient records if the destination workflow has not passed technical and privacy review. Your EHR vendor and compliance team should approve the test method.

## Decide between alongside and bundled EHR routes

Keeping an existing EHR can be the sensible choice when the practice already depends on its chart, billing, reporting, patient portal, or established staff workflows. In that route, Patient Square handles its published scribe functions and stays alongside the system of record.

Patient Square EHR is included from the Copilot tier. That bundled route deserves its own evaluation. Confirm the records, operational, reporting, billing, and migration requirements your practice needs. Do not infer a feature because another EHR includes it.

The choice is not about which architecture sounds more modern. It is about which route passes the practice's clinical, technical, security, and operational checks.

## Keep security in the workflow

Patient Square says visit audio is processed in memory and discarded when the note is drafted. It says notes are encrypted in transit and at rest, a BAA is available to US customers, and visits can be exported or deleted. Review the current [security page](/us/security/) and agreement with your privacy lead.

Also review the destination. Exporting a file can move data onto a workstation, download folder, shared drive, or message channel. Define where exported records may be stored, who can access them, how long they remain, and how they are deleted. A secure source does not make every transfer step secure.

## Ask for evidence, not an "any EHR" slogan

A useful vendor answer names the format, destination, fields, review step, and failure path. A vague promise hides the work your practice will have to discover later.

If you want to evaluate Patient Square beside your current system, [compare the product options](/us/compare/). Use test data first, involve the EHR vendor, and make the acceptance checklist part of the buying decision.

---

## Switch from athenahealth: A Step-by-Step Migration Guide
https://patientsquare.com/us/blog/switch-from-athenahealth/
Published 2026-06-16 · Updated 2026-07-22 · Tags: switching, migration, ehr, athenahealth

Leaving athenahealth is genuinely hard - percentage-of-collections pricing, RCM entanglement, and data export friction are real. Here's how to do it in 6 steps.

Yes. athenahealth supports EHI (Electronic Health Information) export, CCDA export, and clinical chart export via the Manage Data Exports workflow inside athenaOne. You can also export patient demographics and billing data through the same workflow. Request this early - the process can take time, and you'll want the files before you terminate your account.

You can switch from athenahealth. Plenty of practices have done it. The honest caveat: it's one of the harder EHRs to leave, for specific reasons that are worth naming before you start.

The percentage-of-collections pricing model means athenahealth earns a slice of everything you bring in. Third-party estimates put the rate at 4-7% of collections, though the actual figure depends on your contract and practice size (athenahealth doesn't publish a rate card). If you want a full breakdown of what athenahealth costs before you calculate what you'd save, [athenahealth EHR cost](/us/blog/athenahealth-ehr-cost/) does that math in detail. Multi-year contracts with auto-renewal clauses are common. And if you're on athenaCollector for RCM, you're not just switching an EHR - you're disentangling a billing engine too. None of that is insurmountable. It just means "I'll switch next month" usually becomes a 60-90 day project when you plan it properly.

The destination in this guide is Patient Square's AI Copilot EHR, which ships inside the Copilot tier at $119 per clinician per month on annual billing. Flat. Per clinician. No percentage of anything. Book a demo and you can see a finished note in two minutes before you touch your contract.

> **Key takeaways**
>
> - athenahealth's percentage-of-collections model (commonly 4-7%, per third-party estimates) scales against your revenue. A flat $119/mo per clinician is a different economic structure entirely.
> - Contracts typically auto-renew; check your MSA for the notice window before you plan a go-live date.
> - athenahealth does provide data export (EHI, CCDA, clinical chart) via athenaOne - request it early.
> - If athenaCollector is your RCM engine, the billing transition is a separate workstream from the EHR switch. Plan for both.
> - Patient Square is an AI EHR and scribe - not a full RCM replacement. That's the honest trade-off.
> - A 7-day parallel trial lets you validate note quality on real visits before you commit.

## The honest difficulty map

Before the step-by-step, a table. The friction is real in some places and manageable in others.

| What you're moving | The friction | How to handle it |
|---|---|---|
| Patient records & clinical data | EHI/CCDA export exists but needs advance planning; post-shutdown exports take weeks | Request export 30+ days before termination; download and verify before closing account |
| Contract / notice period | Multi-year contracts with auto-renewal are common; early termination fees can be substantial | Read your MSA now; time your switch to a renewal window if possible |
| RCM / billing (athenaCollector) | Leaving means replacing your billing workflow too | Decide: standalone biller, clearinghouse, or new RCM vendor - plan this in parallel |
| New note documentation | Ramp period on any new system | 7-day parallel trial removes the guesswork before you cut over |
| Note portability going forward | Patient Square notes export as PDF, HL7, FHIR | You're never locked in again - EHR-ready export any time |

### How the two pricing models compare

| | athenahealth | Patient Square (Copilot tier) |
|---|---|---|
| Model | Percentage of collections | Flat per clinician |
| Rate | ~4–7% of collections (third-party estimates; rate varies by contract) | $149/mo month-to-month, $119/mo annual |
| 500-visit/month practice at $300K annual collections | ~$12,000–$21,000/year (at 4–7%) | $1,428/year per clinician on annual billing |
| Predictability | Scales with revenue; rises when collections rise | Fixed - same bill every month |

*athenahealth rate is a third-party estimate; the actual rate is set in your contract. Verify your own MSA.*

## Why athenahealth is genuinely hard to leave

Three things create the stickiness, and knowing them upfront makes the switch less surprising.

**The RCM entanglement.** athenaCollector is a real billing engine: claims scrubbing, denial management, patient billing follow-up. It's one of the reasons practices choose athenahealth in the first place. When you leave, that workflow needs a home. You're not just picking a new place to write notes. You're re-solving a billing problem.

**The contract structure.** athenahealth contracts commonly run multiple years with auto-renewal clauses and termination fees. This isn't unusual for enterprise software, but it does mean the decision to switch needs to be made with your renewal date in mind, not spontaneously. Pull out your MSA and find the notice clause before you call anyone.

**The data export friction.** The export tools exist: EHI export, CCDA export, and clinical chart export are all available inside athenaOne. What bites practices is not requesting the export early enough, or not verifying the files before closing the account. Post-shutdown exports exist as a fallback but take weeks and may involve additional fees.

None of these are reasons to stay if the fit isn't right. They're reasons to plan.

## The 6-step migration plan

### Step 1: Pull your contract and find your notice window

Before you tell anyone you're leaving, find your MSA. Look for the termination notice requirement (often 60–90 days), auto-renewal language, and any early-termination fee clauses. If your renewal window is coming up in the next few months, that's your cleanest exit. If you're mid-contract, factor in the fees when you calculate the cost of switching.

### Step 2: Request your data export from athenahealth

Log into athenaOne, go to Manage Data Exports, and request your EHI export, CCDA export, and clinical chart export. Also export patient demographics and billing data. Do this 30 or more days before your intended termination date. Download and verify the files. athenahealth retains your exported data for one calendar year from file creation if you chose Practice Files, but you don't want to depend on that.

### Step 3: Decide your RCM path

This is the fork in the road. If you're using athenaCollector as your billing engine, you need a plan for what replaces it: a standalone billing service, a clearinghouse relationship, or a new RCM vendor. This timeline runs in parallel with your EHR transition, not sequentially. Sorting out the billing path before you pick your go-live date prevents the most common migration delay.

### Step 4: Arrange an assisted 7-day parallel trial

Book a demo to arrange an assisted 7-day trial alongside athenahealth. Don't rely on a scripted demo. Use representative patient types, specialties, and note templates only after your practice has approved the trial setup and consent process. The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. By day 3 or 4, you should have enough examples to judge whether the note quality holds up for your workflow.

The Copilot tier (which includes the bundled AI Copilot EHR) is [$119 per clinician per month on annual billing](/us/pricing/). That's the tier you're evaluating for the full EHR switch.

### Step 5: Move documentation

Once you're satisfied with note quality, shift your active documentation to Patient Square. Your historical records stay accessible in your exported athenahealth files; you're not erasing the clinical history, you're just writing new notes in a new system. Your clinical staff typically adapts faster than the billing side.

### Step 6: Cut over and close your athenahealth account

Give the termination notice per your contract: in writing, to the right contact, with the right lead time. Confirm receipt. Verify your exported files one more time before the account closes. If you need anything post-shutdown, request it promptly - the timeline for post-shutdown data requests runs weeks, not days.

## When you should stay on athenahealth

This belongs in a switching guide. Not every practice should leave.

If athenaCollector is central to your revenue cycle and you don't want to unbundle it (the denial management, the claims scrubbing, the patient billing follow-up as an integrated system), then switching EHRs without solving the RCM side is a bad trade. Patient Square is not a full RCM replacement. The bundled AI Copilot EHR handles documentation, scheduling, eRx drafts, and ICD-10 suggestions. It is not athenaCollector.

Stay if: the billing integration is the thing you're buying athenahealth for, and you're not ready to build a new billing workflow.

Switch if: the documentation burden is the pain, the percentage-of-collections bill is rising faster than your satisfaction with the tool, and you're willing to handle billing separately.

## Note portability you won't have to fight for

One of the quieter costs of EHR entrenchment is the exit friction. You just spent this guide planning a way out of a system that made leaving complicated. Patient Square's notes export as EHR-ready export (PDF, HL7, FHIR) - that's the exact phrase we use because it's the accurate one. Export or delete any visit, any time. Audio is processed in memory and discarded the moment the note drafts. No recording retained. Your notes belong to your practice, and when the next renewal conversation comes around, you're not trapped.

For more on why data ownership is the right criterion when evaluating AI scribes, see our [data ownership and export guide](/us/blog/ai-scribe-data-ownership-export/).

For practices already mid-search across several tools, the [AI scribe vs new EHR comparison](/us/blog/ai-scribe-vs-new-ehr/) covers the decision frame in depth.

## How to run the parallel trial in a week

Concrete steps for the 7-day window:

1. Request an assisted trial and agree on the evaluation setup.
2. Pick 10–15 visits across your most common appointment types.
3. Run Patient Square on each one alongside your current charting process.
4. Review the draft SOAP note, ICD-10 suggestions, and prescription draft for each.
5. By day 4–5, score the notes against your usual standard: does this save 30–45 minutes of end-of-day charting, or not?
6. If yes, request a demo call to map the Copilot EHR to your practice setup before you give athenahealth notice.

The [migration checklist for switching your AI scribe](/us/blog/switch-ai-scribe-migration-checklist/) walks through the documentation-workflow side in more detail if you want a parallel reference.

One more thing worth checking if you're evaluating the broader EHR market alongside this: [best EHR for small practices](/us/blog/best-emr-for-small-practice/) covers what to look for beyond the vendor's own pitch.

---

Patient Square's [pricing page](/us/pricing/) has the full tier breakdown. Security details (encryption, access controls, BAA availability, SOC 2 Type II audit status) are on the [security page](/us/security/). You can request an assisted 7-day trial after workspace setup. Book a short demo if you want to see the note against your own visit type.

---

## AI Medical Scribe FAQ: Questions Clinicians Ask
https://patientsquare.com/us/blog/ai-medical-scribe-faq/
Published 2026-06-15 · Updated 2026-08-27 · Tags: ai-scribe, faq, basics

Straight answers to the questions clinicians actually ask about AI medical scribes: audio, consent, HIPAA, languages, pricing, E/M, EHR fit, and accuracy.

That depends on the vendor, so ask each one. Some keep recordings for days or weeks; some let you opt out; some stay vague. AI Medical Scribe by Patient Square processes visit audio in memory and discards it the moment the note is drafted. There is no audio archive, for us or for your practice.

Clinicians keep asking the same questions about AI medical scribes, just not in the keyword form a search engine expects. They ask the way you'd ask a colleague: does this store my patients' audio, do I need consent, will it mess with my billing, what does it cost. This page answers the ones we hear most, in plain language, each one short enough to quote and each one linked to a deeper post if you want the long version.

One ground rule before we start. We answer for AI Medical Scribe by Patient Square specifically, and where a question is really about the whole category, we say "ask every vendor." A few answers concede where we don't fit. That's deliberate. A FAQ that pretends the product is perfect isn't a FAQ, it's an ad.

> **Key takeaways**
>
> - Visit audio is processed in memory and discarded once the note is drafted. No archive, for anyone.
> - We suggest ICD-10 codes only. We do not set your E/M level, and that protects you from upcoding exposure.
> - Pricing starts at $79/clinician/month on the annual Assist plan, with a 7-day trial; Copilot and Autopilot add more as you climb.
> - We capture English and more languages; the note always comes back in clean clinical English.
> - Our SOC 2 Type II audit is underway, and we don't call it "certified" until it's done.

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Most of the questions below are about that scribe module, since it's where documentation starts.

## Privacy, consent, and your data

These come up first in almost every demo, and they should.

### Does an AI scribe store my patients' audio?

It depends on the vendor, and you should ask each one directly. Some retain recordings for days or weeks, some let you opt out, some won't give you a straight number. Ours doesn't keep it: visit audio is processed in memory and discarded the moment the note is drafted, so no archive exists. The full breakdown, with competitor policies quoted and dated, is in our [audio-retention comparison](../ai-scribe-audio-retention/).

### Is an AI medical scribe HIPAA compliant?

Software by itself is never "HIPAA certified." That certificate doesn't exist, so be wary of anyone who implies they hold one. What actually matters: does the vendor sign a BAA, encrypt PHI in transit and at rest, scope access by role, and tell you where the audio goes. We maintain HIPAA compliant safeguards and sign a [BAA with every US customer](../ai-scribe-hipaa-baa-consent/).

### Do I need patient consent to record, and is it state-specific?

Yes, and yes. US recording-consent law splits by state: some need one party to agree, others need everyone in the room. Get a clear verbal yes before capture starts and note it in the chart. Cross a state line and the rule can change. We keep a [state-by-state consent breakdown](../ai-scribe-patient-consent-by-state/) so you can check yours before you start.

### What do I tell the patient before I start recording?

Keep it short and routine. Something like: "I use a secure tool that helps me write my notes so I can focus on you instead of the screen. It's fine with you?" Most patients say yes and appreciate the eye contact. For telehealth, say the same thing and get the yes on the call. If a patient declines, you turn it off and chart the usual way.

### Is my patient data used to train your AI?

No. We don't train our model on your visits, and we don't sell or share your clinical data with anyone. The structure of the product makes this easy to promise: since audio is discarded once the note is drafted, there's no recording to feed into a training set later. What remains is the note you signed, and that note is your practice's property. You can [export or delete any visit](../ai-scribe-data-ownership-export/) whenever you want.

### How is the data encrypted and stored?

Notes are encrypted in transit with TLS 1.2 or higher and at rest with AES-256. Access is role-scoped and logged, so you can see who opened what. Notes belong to your practice, not to us. The whole posture sits on our [security page](../../security/) and in our [security checklist](../ai-scribe-security-checklist/).

## How it works and what it hands back

### How fast is the note?

About two minutes after the visit ends. The draft is ready while the patient is still leaving, not waiting for you that night. You read it, correct anything off, and sign. That speed is the whole pitch of an ambient scribe: the chart closes when the visit closes. More on the mechanics in [what an AI medical scribe is](../what-is-an-ai-medical-scribe/).

### Does it write prescriptions?

It writes a prescription draft. It does not e-prescribe, send to a pharmacy, or touch SureScripts. The draft saves you typing; you review and sign like everything else.

### So who catches a bad dose or a drug interaction?

You do, the same as you do today. The scribe does not run a drug-interaction check, a dosing check, or a pregnancy screen, and it will not block or flag an unsafe combination for you. It drafts what the visit called for; the safety review is yours. A draft an LLM wrote is still a draft an LLM wrote, which is exactly why you read it, adjust the medicines, and sign. More on that in [reviewing an AI-drafted prescription safely](../ai-scribe-prescription-draft-safety/).

### Will an AI scribe change my E/M level?

Not ours, by design. We surface ICD-10 diagnosis suggestions you review and confirm. We do not set your E/M visit level, generate CPT or HCC codes, or file claims. Tools that auto-assign an E/M level take on the upcoding and audit risk that's legally yours. We think that's a line worth keeping, and we explain why in [ICD-10 suggestions versus a coding engine](../ai-scribe-icd-10-suggestions-explained/).

### How accurate is it?

We don't publish an accuracy percentage, and we'd distrust any vendor who waves one around without saying how it was measured. Drafts contain errors: a misheard drug name, two complaints compressed into one. That's exactly why review-and-sign is load-bearing and not optional. We wrote an honest piece on [what accuracy actually means](../ai-scribe-accuracy-what-to-expect/) for a scribe and how to test it on your own visits.

## Languages, connectivity, and your setting

### What languages does it support?

English and more languages, with the note always returned in clean clinical English. The honest advice is to read any vendor's language list literally, then test it on your own patients during a trial. Accents and code-switching are where models quietly break, and "multilingual" without a named list is marketing, not a feature.

### Does it work offline or on low connectivity?

Yes. Capture works offline with on-device AES-256-GCM encryption, then syncs when the connection returns. That matters for any setting where the link drops mid-visit. The patient conversation isn't lost, and the encryption travels with the captured data. Full detail in [offline and low-connectivity capture](/in/blog/ai-scribe-offline-low-connectivity/).

### Does it work with my EHR?

It works with any of them, because it doesn't integrate with any of them. You export the structured note and bring it into Epic, athenahealth, eClinicalWorks, Elation, or whatever your clinic runs. No live write-back, no integration fee, no waiting on an IT ticket. That EHR-agnostic design is a feature, and we contrast it with [free EHR-bundled scribes](../free-ehr-ai-scribe-vs-standalone/).

## Compliance and certifications

### Is it SOC 2 certified?

Not yet. Our SOC 2 Type II audit is underway, and we won't call ourselves "certified" until it's done. Be careful with vendors who blur "audit in progress" into "certified," because those are different things. What we can offer today is HIPAA compliant safeguards and a BAA, covered in our [HIPAA and BAA guide](../ai-scribe-hipaa-baa-consent/).

### What happens if I want to leave?

Your notes are your practice's property, full stop. You can export or delete any visit yourself, with no support ticket and no per-record fee, and we never sell or share clinical data. Export friction is how vendors keep you, so read the contract on this point before you sign, not after. Detail in [data ownership and export](../ai-scribe-data-ownership-export/).

## Fit: specialty, segment, and the honest limits

### Is it good for behavioral health or therapy?

The zero-audio-retention design fits behavioral health well, because no recording of a therapy session ever persists. That's the single biggest privacy worry in this space, alongside 42 CFR Part 2 and psychotherapy-note sensitivity. Read the [psychiatry and privacy](../ai-scribe-for-psychiatry-privacy/) post for the specifics before you decide it fits your practice.

### Does it work for my specialty?

It works across specialties, but we won't pretend a generic scribe is tuned to every one of them. We don't ship per-specialty note templates today. The honest test is to run it on your own case mix during the trial and read the drafts closely. We have focused write-ups for [primary care](../ai-scribe-for-primary-care/), [pediatrics](../ai-scribe-for-pediatrics/), and [nurse practitioners](../ai-scribe-for-nurse-practitioners/).

### How does it help with insurance claims and denials?

A complete, structured note at the time of the visit is the documentation a payer wants to see. Broadly, that means fewer [claim denials traced to thin documentation](../ai-scribe-claim-denials-documentation/). The scribe doesn't file or code the claim. It makes the underlying record defensible, which is upstream of every denial fight.

## How much does it cost, really?

Plain numbers, since this is where most evaluations end up.

| Plan | Per clinician / mo (annual billing) |
|---|---|
| **Assist** | $79 |
| **Copilot** (most popular) | $119 |
| **Autopilot** | $199 |
| **Trial** | 7-day free |

These are annual-billing rates; month-to-month runs higher ($99 / $149 / $249) and the full ladder sits on the [pricing page](../../pricing/). The tiers gate features: Assist covers the scribe and scheduling, Copilot adds a bundled AI EHR and WhatsApp, and Autopilot adds an AI receptionist, follow-ups, and priority support.

For comparison, published US self-serve scribes run roughly $39 to $199 a month, and several large vendors (Suki, DeepScribe, Nabla) publish no price and route you to sales. Transparent list pricing makes a vendor easier to evaluate without a sales call. We lay out the full rate card in our [pricing breakdown](../ai-medical-scribe-pricing/).

Does it pay for itself? Primary-care physicians in a 2023 JAMA Network Open study logged a median of 36.2 minutes of EHR time per 30-minute visit. Against a $79 monthly line item, recovering even part of that isn't a close call. Run the math on your own visit volume, though, not ours.

## Which scribe should I actually pick?

We're one option, and the honest answer depends on your constraints. If you need deep bidirectional EHR integration or an enterprise health-system rollout today, a different vendor likely fits better, and we'll tell you that on a call. If your priorities are zero audio retention, flat transparent pricing, ICD-10 and Rx drafts you control, and a BAA, we're built for exactly that.

The way to know is to run it on a real clinic day. Take the 7-day trial, use it on your own patients, your own accents, your own interruptions, and read every draft for the first week. That's the evaluation that settles it. When you're comparing options, our [how-to-evaluate guide](../how-to-evaluate-ai-medical-scribe/) and the [best-scribes roundup](../best-ai-medical-scribes/) lay out the questions to ask everyone. Then <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and bring your hardest case.

---

## Tali AI Alternatives: When You Want More Than Search + Scribe
https://patientsquare.com/us/blog/tali-ai-alternatives/
Published 2026-06-15 · Tags: ai-scribe, comparison, tali-ai, pricing

Compare Tali AI clinical search and ambient scribing with structured-output options and a bundled EHR from $119, including where Tali fits best.

Tali pairs an ambient scribe with a clinical search assistant, so you can ask drug and reference questions inside the same tool that writes your note. It has a real free tier (5 scribes plus 60 minutes of dictation a month) and unlimited dictation on paid plans. If you want a search co-pilot beside your notes and you're fine with Canadian-dollar billing, that combination is Tali's point of difference.

Tali AI is two tools in one: an ambient scribe and a clinical search assistant. That's genuinely useful if you want to ask a drug question without leaving the note. But Tali doesn't ship a record system, and it prices in Canadian dollars, which trips up a US practice doing the math. If you want structured output plus a chart you own, the honest alternative is a scribe that bundles an EHR. Patient Square's Copilot plan does exactly that at $119 a month on annual billing, and you can book a demo and see a finished note before you decide.

This isn't a knock on Tali. It's a fit question. Below: what Tali does well, what it costs once you convert the currency, where a bundled-EHR tool pulls ahead, and the cases where Tali is still the right call.

> **Key takeaways**
>
> - Tali bundles an ambient scribe with a clinical search assistant and has a real free tier: 5 scribes plus 60 minutes of dictation a month.
> - Tali prices in Canadian dollars. Starter runs about CA$60/mo but caps ambient notes at 40; Pro is about CA$100/mo annual (CA$150 regular) for unlimited.
> - Tali doesn't ship an EHR. If you also need the chart, that's Tali plus a separate record system.
> - Patient Square's Copilot plan bundles an AI EHR with the scribe at $119/mo annual, in US dollars, one subscription.
> - Tali wins when the search assistant is the feature you want, or you only need a scribe layer over an EHR you're keeping.

| | Tali AI | Patient Square |
|---|---|---|
| Ambient scribe | Yes | Yes (AI Medical Scribe) |
| Structured note + ICD-10 + Rx draft | SOAP note; search assistant | SOAP note, ICD-10 suggestions, Rx draft in one pass |
| Bundled EHR | No | Yes, at Copilot ($119/mo annual) |
| Currency | Canadian dollars | US dollars |
| Free tier | Yes (5 scribes, 60 min dictation/mo) | 7-day trial |
| Published price | Yes (CAD) | Yes ($79 / $119 / $199/mo annual) |

Prices verified against each vendor's pricing page in July 2026. Tali figures are in CAD; convert before comparing.

## What Tali AI is actually good at

Give Tali credit for the idea. Most scribes write the note and stop. Tali adds a clinical search assistant in the same window, so a question like "what's the renal dosing here" doesn't send you to a browser tab mid-visit. For a clinician who reaches for a reference tool a dozen times a day, that's a real time save, not a checkbox.

The free tier is the other honest thing about Tali. Five ambient scribes and 60 minutes of dictation a month, no card required, per Tali's pricing page. That's enough to feel whether ambient documentation fits your visit style before you pay a cent. Not every vendor lets you do that.

So if a search co-pilot beside your notes is the thing you want, Tali has a clear answer. The question is whether that's your actual need, or whether you're really shopping for structured output and a chart. If it's the latter, you can book a demo and compare a finished note side by side.

## What Tali AI costs once you convert the currency

Here's where a US practice has to slow down. Tali prices in Canadian dollars, and its pricing page (fetched July 2026) lists a free Personal plan, a Starter plan around CA$60 a month, and a Pro plan around CA$100 a month on annual billing (CA$150 at the regular rate). Enterprise is custom.

Two details matter more than the headline number. First, Starter caps ambient scribes at 40 a month. If you see 20 patients a day, you'll blow past 40 in the first week, so Starter isn't really a full-time scribe plan; it's a light-use tier. Second, the prices are in CAD, so a US buyer has to convert before comparing against a US-dollar tool, and the exchange rate moves. Neither is a dealbreaker. Both are things you want to know before the renewal, not after.

Patient Square prices in US dollars, on the [pricing page](/us/pricing/) with no conversion step: $79 a month for Assist, $119 for Copilot with the bundled AI EHR, $199 for Autopilot, all per clinician on annual billing, all with unlimited visits and notes and no per-note metering. If you want the whole self-serve field laid out, our [best AI medical scribes](/us/blog/best-ai-medical-scribes/) roundup is the honest version.

## Does Tali AI bundle an EHR? No, and here's why that matters

This is the split that decides most of these evaluations. Tali is a layer that sits on top of your chart. It writes the note and answers reference questions; it doesn't store the record. If you already run an EHR you're happy with, that's a clean fit: bolt Tali on, keep your chart.

But a lot of practices reading a page like this are shopping for two things at once, a better scribe and a better chart, and they haven't realized those are separate purchases with Tali. Buy Tali plus a standalone EHR and you're running two subscriptions, two logins, two renewal conversations, and a copy-paste step between them.

Patient Square's Copilot plan puts both in one place. The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. At the Copilot tier ($119/mo annual) that scribe is bundled with an AI Copilot EHR, so the note lands in the chart you're already in. One subscription, US dollars. If you're weighing scribe-plus-EHR against a bolt-on layer, book a demo and see how the two feel in a real workflow.

A note on scope, so we're honest: our eRx is a draft you review and sign, not pharmacy transmission, and ICD-10 is suggestions, not a coding engine. If those are the features you're buying for specifically, put them on your demo checklist for every vendor.

## What you trade by leaving Tali for a bundled-EHR scribe

There's a real trade, and pretending otherwise helps nobody.

You give up the clinical search assistant. That's Tali's signature feature, and Patient Square doesn't replicate it. If asking reference questions inside your notes tool is core to how you work, weigh that seriously; it's the one thing you'd miss.

You also give up the free tier as a permanent option. Patient Square runs a 7-day trial, not an ongoing free plan. The trial is enough to test note quality on real visits, but if "free forever for light use" is what you want, Tali's Personal plan is a genuine advantage.

What you gain is the chart and the codes in one pass. A SOAP note, ICD-10 suggestions, and a prescription draft, plus a bundled EHR at the Copilot tier, all in US dollars. Audio is processed in memory and discarded the moment the note drafts, so nothing is retained. And a BAA is available for every customer, solo practices included. If you want the enterprise-versus-self-serve version of this comparison, [Abridge alternatives](/us/blog/abridge-alternatives/) covers the other end of the market.

## When Tali AI is the better choice

Stay with Tali, or pick it, if the clinical search assistant is the feature you actually came for. Nothing here replaces it, and if you lean on a reference tool all day, that integration is worth real money to you.

Tali also wins if Canadian-dollar billing suits your practice, if you only need a scribe layer over an EHR you're keeping, or if you want to trial ambient documentation on a free plan before paying. Those are legitimate reasons, and Tali serves them well.

Choose a bundled-EHR scribe if you want US-dollar pricing you can read at a glance, structured output in one pass, and the chart and the scribe under one subscription. That's most of the US practices landing on this page, which is why we wrote it.

The split is about what you're buying, a search-plus-scribe layer or a scribe-plus-chart bundle, not about note quality. Both write good notes. Match the tool to the actual gap.

## How to decide in a week

Skip the feature grid and run the real test:

1. Name your real gap. If it's "I want reference answers inside my notes," Tali belongs on your list. If it's "I want a better scribe and a better chart," you're shopping for a bundle.
2. Convert the currency. Put Tali's CAD prices into US dollars at today's rate so you're comparing like for like, and check the 40-scribe cap on Starter against your daily volume.
3. Match the clinical output. A note plus ICD-10 suggestions plus a checked prescription draft, so you're comparing the same thing across vendors.
4. Settle the audio question with every vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits, not a scripted demo. Every scribe looks good on a canned encounter.

The receipts behind our claims, encryption, access, audit status, are on the [security page](/us/security/); the price ladder with no asterisks is on the [pricing page](/us/pricing/). Book a short demo to see the note against your own visit type, then run the 7-day trial on a real clinic week. If your real need is a chart plus a scribe in US dollars, a bundled tool does the job a search-plus-scribe layer wasn't built for.

---

## How Clinicians Cut Charting Time in 2026
https://patientsquare.com/us/blog/reduce-charting-time-clinicians/
Published 2026-06-12 · Updated 2026-07-22 · Tags: charting, documentation-burden, ai-scribe, pillar

Where the documentation hours go, what the 2026 studies show an AI scribe can claw back, and the questions that separate real time savings from marketing.

A 2023 JAMA Network Open study found primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit. About 1 in 5 US physicians also spend more than eight hours a week on after-hours EHR work, the AMA reports. The note now outlasts the appointment it describes.

Charting is the longest task in most clinicians' day, and almost none of it happens in front of the patient. Cutting it comes down to one move: stop building the note from memory after the visit and start reviewing a draft that wrote itself during the visit. That's the whole game. The tools differ. The evidence is honest about how much they save. And the gap between a good answer and a sales pitch is wide.

This is the pillar page for everything we've written on documentation burden. Below: where the hours actually go, what the 2026 studies show you can realistically claw back, the methods that get you there, and links down to the specific playbooks, the ROI math, the pajama-time breakdown, the SOAP-note quality test, and the accuracy question nobody answers straight.

> **Key takeaways**
>
> - Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit (JAMA Network Open, 2023).
> - About 1 in 5 US physicians spend 8+ hours a week on after-hours EHR work; that share was 20.9% in 2023 and 22.5% in 2024 (AMA).
> - A 2026 JAMA study across five health systems measured about 16 minutes of documentation time saved per 8 hours of patient care with ambient AI. Real, not revolutionary.
> - The reliable win is removing the keyboard from the visit. With an ambient scribe, the draft lands about 2 minutes after the visit ends.

## Where does the charting time actually go?

It goes after the visit, and after the workday. That's the part the schedule hides.

A 2023 JAMA Network Open study of primary-care physicians found a median of 36.2 minutes of EHR time for every 30-minute visit slot. Read that twice: the documentation now runs longer than the appointment it documents. An older time-and-motion study in the Annals of Internal Medicine put it differently, nearly two hours of EHR and desk work for every hour of direct patient care.

Then there's the part that follows you home. The AMA's data shows about 1 in 5 physicians spend more than eight hours a week on after-hours EHR work, what clinicians call "pajama time." That share was 20.9% in 2023 and ticked up to 22.5% in 2024. Family physicians in one Annals of Family Medicine study averaged 86 minutes of after-hours administrative EHR work a night. The note doesn't disappear when the clinic closes. It waits.

We dug into the after-hours piece specifically in [beating pajama time](../ai-scribe-pajama-time/), because that's where the burnout pressure concentrates.

## How much charting time can an AI scribe actually save?

Here's where most vendor pages overreach and the studies don't. We'll use the studies.

The largest 2026 read is a JAMA study published in April that tracked more than 1,800 clinicians using ambient AI scribes against nearly 6,800 controls across five health systems. The result was modest and measured: about 16 minutes of documentation time saved and 13 fewer minutes in the EHR per eight hours of patient care. Notably, it found no significant drop in after-hours EHR time, and the time freed up translated to roughly half an extra visit a week. The researchers called the savings "modest," and so do we.

A separate randomized trial from UCLA, published in NEJM AI, measured one tool (Nabla) cutting average note-writing time by about 41 seconds per note, from 4 minutes 30 seconds to 3 minutes 49 seconds, across 72,000 encounters and 238 physicians. The other tool in the trial showed a smaller, statistically insignificant change. Both nudged burnout scores down by around 7%.

So the honest headline isn't "two hours back every night." It's "a real, repeatable slice of documentation time, larger for some clinicians than others, with primary care and high-note-volume practices benefiting most." If a vendor promises more than the studies support, that's a flag, not a feature. We worked the dollars-and-cents version in [the real ROI of an AI scribe](../ai-scribe-roi-calculator-guide/).

## What's the fastest way to cut charting time?

Get the keyboard out of the visit. Every method that works does this one thing.

| Method | When you write the note | Your time per note | What it costs |
|---|---|---|---|
| Type during/after the visit | During or at day's end | Full write, 5-15+ min | Your evenings |
| Dictation software | After the visit, from memory | 5-10 min speaking + cleanup | Low subscription |
| Human scribe | During the visit (someone else types) | Review only | A salary |
| Ambient AI scribe | During the visit (software drafts) | ~2 min review | A subscription, ~1/10th a scribe salary |

Dictation moved typing to talking, but you still narrate visits you already did once. Human scribes solve the time problem and create a hiring one. Ambient AI is the first version where the documentation happens while the medicine happens. We laid out the head-to-head in [ambient AI vs dictation](../ambient-ai-vs-dictation/).

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. You read it, you sign it. Which is exactly why "how good is the draft" matters more than any time number. We built a [6-point SOAP-note rubric](../ai-scribe-soap-note-quality/) so you can grade any scribe's output, ours included.

## Does cutting charting time reduce burnout?

For the documentation slice of burnout, the evidence says yes, and it's the strongest claim in the category right now.

A 2025 JAMA Network Open study across Mass General Brigham and Emory, surveying more than 1,400 clinicians, found a 21.2% absolute drop in burnout prevalence at Mass General Brigham over 84 days, and a sharp rise in documentation-related well-being at Emory. That's a bigger effect on how clinicians *feel* than the raw time numbers alone would predict, which is itself a finding: even modest time savings, applied to the most resented task, move the needle on burnout.

What it doesn't touch: inbox volume, prior authorization, staffing shortages, the parts of burnout that come from workload rather than typing. If charting is your largest after-hours burden, an AI scribe targets it directly. If it isn't, expect a smaller effect. We covered the full evidence base in [the 2026 evidence on AI scribes and burnout](../ai-scribe-burnout-evidence/) and in [do AI scribes reduce burnout](../do-ai-scribes-reduce-burnout/), caveats and all.

## What questions separate real time savings from marketing?

Before you trust any time number, ask these. They map to the deeper pages in this hub.

1. "How accurate is the note, and what do you publish about it?" A scribe that drafts a bad note costs you time, it doesn't save it. Be suspicious of vendors quoting a clean accuracy percentage; we explain why in [how accurate are AI medical scribes](../ai-scribe-accuracy-what-to-expect/).
2. "What happens to the audio?" Ours is processed in memory and discarded the moment the note drafts. No archive. The full posture is on our [security page](../../security/).
3. "What's the real per-note time, on my patient mix?" Test it on your accents, your languages, your noisy room, during the trial.
4. "What does it cost against the time it saves?" Run the [ROI math](../ai-scribe-roi-calculator-guide/) on your own visit volume, not a vendor's.
5. "Does the note quality survive my hardest visit?" Grade it with the [SOAP-note rubric](../ai-scribe-soap-note-quality/).

A scribe that survives those questions will probably survive your Tuesday clinic.

## Start with your own clinic day

The honest way to find out how much charting time you'd save is to measure it on real visits, not to trust a number on a pricing page.

Practice Copilot starts from $79 per clinician per month on annual billing (the Assist plan), with a 7-day free trial. The full ladder, with no asterisks, is on the [pricing page](../../pricing/), and the rate card breakdown sits beside it in our [AI medical scribe pricing breakdown](../ai-medical-scribe-pricing/).

The best next step is to <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a finished note appear about two minutes after a sample visit, then run the trial on a real clinic week and time yourself. That's the only charting-time number that matters: yours. If you're still narrowing the field, our [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) scorecard and [best AI medical scribes](../best-ai-medical-scribes/) roundup are the next two stops.

---

## Can an AI Medical Scribe Draft a Prescription Safely?
https://patientsquare.com/us/blog/ai-scribe-prescription-draft-safety/
Published 2026-06-11 · Updated 2026-07-22 · Tags: ai-scribe, prescription, safety

How the AI scribe's prescription draft works: it mirrors the plan you dictated, stays a draft you review and sign, and the clinician is the safety check.

It drafts one; it does not prescribe or transmit it. An AI scribe can turn the plan discussed in the visit into a prescription draft. You review it, adjust it, and sign it. Nothing is sent to a pharmacy automatically. The draft is a starting point that saves typing, with the clinician as the prescriber throughout.

Yes, and the safety comes from you, not the software. Here's the fear people actually have: the AI invents a dangerous combination, you're tired, you sign it on autopilot. The honest fix isn't a magic screen inside the scribe. It's the same review you already do. The scribe drafts a prescription that mirrors the plan you discussed in the visit, and then it stops. It stays a draft until you read it, adjust it, and sign it. Nothing goes to a pharmacy on its own. You are the prescriber, and your signature is where the safety check happens. Here's how the draft works and why that split matters.

> **Key takeaways**
>
> - An AI scribe drafts a prescription; it does not prescribe or transmit it. You review and sign, and nothing reaches a pharmacy automatically.
> - The draft mirrors what you dictated in the visit. It is a starting point that saves typing, not a clinical decision the software made for you.
> - There is no automated interaction, renal, or pregnancy screen inside the scribe. It does not block, override, or attest to anything.
> - The clinician is the safety check. You screen the draft exactly as you screen any prescription you write today, before you sign.

## How does the prescription draft actually work?

The scribe listens to the visit. When you and the patient land on a plan, and you say it out loud, the draft reflects that. If you say "start lisinopril ten milligrams daily," the draft comes back with lisinopril, 10 mg, once daily. It's turning the spoken plan into a written starting point, not inventing a treatment on its own.

That's the whole job. The draft mirrors what was said. It saves you the typing and the clicking, so you review a filled-in prescription instead of a blank field. But it does not decide the medication is correct for this patient. It can mishear a drug name. It can transpose a dose. Like any AI output, it can read fine and still be wrong. That's exactly why it stays a draft.

For the broader set of evaluation questions, including what to make a vendor demo prove about Rx, our [9-question scorecard](../how-to-evaluate-ai-medical-scribe/) is the companion guide.

## Why the clinician is the safety check

Be plain about what the scribe does not do. It does not run a drug-interaction check. It does not screen for renal dosing. It has no pregnancy-flag engine, no contraindication database, no hard-block, no override, no attestation gate. There is no automated safety screen inside the product that stands between the draft and your signature.

We think that's the honest design, not a gap. Screening a prescription for interactions, dosing, and contraindications is clinical judgment. It's the work you already do every time you write an Rx, and it's the work that a language model should not be quietly trusted with. Build your safeguard as "the software will catch it" and you've built a system that assumes a rule engine understands your patient better than you do. It doesn't. You do.

So the safety layer is you. You read the draft, you apply the same screening you'd apply to anything you write yourself, and you sign. The draft changes how fast you get to that review. It doesn't change who does it.

## What to check before you sign

Read an AI-drafted prescription the way you'd read one a resident handed you: assume nothing, verify everything that matters.

Right patient, right drug, right dose, right frequency. Then the clinical screen that's yours to run: does this interact with what the patient is already on, does the dose need adjusting for their kidney function, is there a pregnancy or contraindication concern here. The draft won't have done any of that for you. It has drafted; you decide. The same review-and-sign discipline governs our codes, where suggestions are confirmed not assigned, covered in our [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/).

The point of the draft is speed to a good review, not a shortcut around it. A draft that reflects the visit gets you to "is this right?" faster. Answering that question stays your job.

## What the AI scribe deliberately does not do

What we don't do with the prescription matters as much as what we draft. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription is a draft. It stays a draft until you make it real inside your own workflow.

No e-prescribing. The draft never gets transmitted to a pharmacy, never gets routed through a prescribing network, never touches a controlled-substance prescribing system. We drew that boundary on purpose, because drafting a prescription and transmitting one are different jobs carrying different regulatory weight, and we do only the first. For context, US telemedicine controlled-substance prescribing rules are still in flux, with HHS and DEA extending the current flexibilities through the end of 2026 while a permanent framework is finalized. We sidestep all of that by simply not transmitting prescriptions. You carry the reviewed, signed Rx into your existing process yourself.

## Is an Rx draft worth it if I still have to review it?

Yes, because reviewing a filled-in prescription is faster than typing one from scratch, and you were always going to review it anyway. You start from a draft that already reflects the visit's plan instead of a blank field, and you sign knowing you ran the same screen you run on every prescription. The draft ships with the product everyone gets, with no Rx tier you pay extra for. The full ladder is on the [pricing page](../../pricing/).

Ask us what makes our scribe different and we'll be straight about the Rx draft: it's fast, it mirrors what you said, and it never pretends to be the prescriber. The safety isn't a feature we sell you. It's the review you already do, made quicker to get to. <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and ask us to draft a prescription from a real visit, then check it the way you'd check your own. That's the test worth running.

---

## Is an E-Prescription Legally Valid in India? A Buyer's Checklist
https://patientsquare.com/in/blog/e-prescription-software-india-legal/
Published 2026-06-11 · Tags: prescription, rx, india, legal, software

Review electronic-prescription rules in India, including IT Act e-signatures, Telemedicine Practice Guidelines, and a software buyer checklist.

Yes, if it is signed the way the law recognises. A typed prescription carries the same legal weight as a handwritten one when the doctor signs it with a valid signature. Under the Information Technology Act 2000, a digital signature or a recognised electronic signature is treated as equivalent to a handwritten one. A typed prescription with a typed name and nothing else is weaker. The signature is what makes it hold up, not the fact that it was generated by software.

Yes, an electronic prescription is legally valid in India, but not because the software made it. It is valid because you signed it the way the law recognises. A typed prescription with a typed name at the bottom is weak. The same prescription carrying a valid signature, your registration number, and the mandatory fields holds the same weight as the one you used to scrawl on a pad. So when a vendor sells you "e-prescription software" and implies the legality comes built in, the honest version is narrower: the software produces a clean document, and the signature is what makes it count. This page walks through what the law actually asks for, and the checklist to run a tool against before you buy.

> **Key takeaways**
>
> - A typed prescription is legally valid when signed in a form the law recognises. The Information Technology Act 2000 treats a digital signature, and a recognised electronic signature, as equivalent to a handwritten one.
> - The Telemedicine Practice Guidelines 2020 let a registered doctor prescribe during a teleconsult and send the prescription electronically, with name, registration number, and signature on it, and a list of drugs that cannot be prescribed remotely.
> - Software does not supply legal validity. Your signature and the mandatory prescriber fields do. Good software makes both easy and hard to skip.
> - DPDP Act 2023 makes the prescription personal health data, so ask every vendor where the text lives, whether audio is kept, and whether you can export and delete.
> - AI Medical Scribe by Patient Square drafts the prescription, including prescriber fields, but leaves the signature and the clinical call to you. It does not transmit anything to a pharmacy.

_Sources: The Information Technology Act 2000; Telemedicine Practice Guidelines 2020, MoHFW; Irving et al., BMJ Open 2017._

## What actually makes an e-prescription legal in India

Start with what the law cares about, because it is narrower than most vendor pages suggest. A prescription is a clinical instruction signed by a registered practitioner. The format, paper or screen, is not the thing that makes it valid. The signature is. Strip the signature off a beautifully formatted digital prescription and you have a document, not a prescription.

For a typed or software-generated prescription, the question becomes: how do you sign it so the signature is recognised? That is the gap the Information Technology Act 2000 fills. The Act gives legal recognition to electronic records and to signatures applied electronically. A digital signature, the certificate-backed kind issued by a licensed Certifying Authority, is treated as equivalent to a handwritten signature. The Act was later amended to also recognise a broader class of electronic signatures, provided they are reliable and attributable to the signer. In plain terms: a prescription you sign with a recognised electronic signature is not a lesser document than one you signed by hand. It is the same legal object.

The weak case is the one clinics fall into by accident. A prescription typed on a screen, with the doctor's name typed underneath and no signature applied at all, leans entirely on the clinic's word that the doctor authorised it. That is the version that gets challenged. The fix is not more software. It is applying a signature the law recognises, every time, on every prescription.

So the first thing to settle about any e-prescription tool is mechanical: how does it let you sign, and is that method one the IT Act recognises?

## The mandatory fields, and why software is good at them

A valid prescription is more than a signature. It has to say who prescribed, who they are registered as, and what they prescribed in enough detail to be dispensed and audited. The standard expectation includes the prescriber's name, their medical registration number, the patient's identifying details, each medicine with its strength, dose, frequency, and duration, and the date.

This is the part software genuinely helps with, and it is worth giving the tools credit where it is due. A handwritten pad relies on the doctor remembering to write the registration number on a busy day. A well-built prescription tool puts the prescriber fields in by default and refuses to produce a prescription with a blank dose or a missing duration. The legal value here is not glamorous, it is completeness, and completeness is exactly what fails under pressure at the end of a long clinic.

So the second checklist item: does the tool enforce the mandatory fields, or does it let you generate a half-filled prescription? A tool that lets you ship a prescription with no registration number is not saving you from the failure mode that actually bites.

## Telemedicine prescriptions: a stricter set of rules

If any of your consultations happen over phone or video, a second rulebook applies on top of the IT Act. The Telemedicine Practice Guidelines 2020, issued under the Ministry of Health and Family Welfare, set out how a registered medical practitioner may prescribe during a teleconsultation.

The guidelines do three things that matter for software selection. First, they confirm that a doctor can prescribe remotely and can share the prescription with the patient electronically, by email, by message, or by another digital channel. Second, they require the prescription to carry the doctor's name, registration number, and signature, the same identity backbone as an in-person Rx. Third, and this is the one tools rarely flag, they place certain categories of medicine off-limits for telemedicine prescribing entirely, with tighter conditions on others.

That third point is where a thoughtful tool earns its place and a careless one creates risk. The guidelines set the conduct rules; they do not bless any particular product, and no vendor can claim the guidelines "certify" their software, because the guidelines do not certify software at all. What a good tool can do is make the required fields automatic and make the restricted categories visible to the prescriber, so the decision is informed. What it cannot do is make a remotely-prescribed restricted drug legal. That stays on the doctor.

So the third checklist item, if you teleconsult: does the tool carry the prescriber identity fields through to the shared prescription, and does it surface, rather than hide, the categories that telemedicine prescribing restricts?

## DPDP turns the prescription into a data obligation

There is a fourth dimension that did not exist a few years ago, and it changes how you should read every vendor's data page. The Digital Personal Data Protection Act 2023 treats any organisation that processes a person's digital personal data as a Data Fiduciary, with duties attached. A prescription is personal health data. The moment it lives inside software, the vendor, and you, are handling data the Act protects.

Practically, this turns three quiet questions into buying criteria. Where does the prescription text actually live, and for how long? If the tool listens to your consultation, is that audio stored anywhere, or processed and discarded? And can you export and delete a patient's prescriptions on request, since the Act gives the patient rights over their own data? This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

These are not theoretical. A vendor that keeps your consultation audio on a server is holding the most sensitive version of the visit, the prescription discussion plus everything else the patient said, and you are now responsible for that storage existing. A vendor that cannot give you a clean export is a vendor you cannot leave, which is its own kind of risk. For the longer treatment of what DPDP asks of a clinic, the [DPDP Act clinic guide](../dpdp-act-clinics-guide/) goes field by field.

So the fourth checklist item: get the data-handling answers in writing before you sign, not after.

## The buyer's checklist, in one place

Run any e-prescription tool against these. They map to the four legal dimensions above, and they are the questions a vendor demo should be able to answer without a follow-up call.

| Checklist item | What you are confirming | Why it matters legally |
|---|---|---|
| **Signature method** | How the tool applies a signature, and whether it is IT Act recognised | An unsigned typed prescription is the weak case that gets challenged |
| **Mandatory fields** | Prescriber name, registration number, drug, dose, frequency, duration enforced | A prescription missing the registration number or dose is incomplete |
| **Telemedicine identity** | Prescriber fields carry through to the electronically-shared prescription | Telemedicine Practice Guidelines 2020 require name, registration, signature |
| **Restricted-drug visibility** | Whether the tool surfaces the categories telemedicine restricts | The restriction is on the doctor; visibility supports the decision |
| **Data residence** | Where the prescription text is stored and for how long | DPDP makes the vendor and you accountable for the data |
| **Audio handling** | Whether consultation audio is retained or discarded | Stored audio is the most sensitive record of the visit |
| **Export and delete** | Whether you can export and delete a patient's records | DPDP gives patients rights; you need the mechanism to honour them |

Notice what is not on this list: a vendor's claim that their software is "legally compliant" or "approved." No e-prescription software in India is approved or certified for legal validity, because legal validity is not a property the software can hold. It is a property of how you sign and what you include. Treat "legally compliant software" as marketing and check the seven rows instead.

## Where AI Medical Scribe by Patient Square sits, and the line we don't cross

We build an ambient scribe, and the prescription is one of the things it drafts. So it is fair to ask where it lands on this checklist, and equally fair to ask what it deliberately does not do.

AI Medical Scribe by Patient Square listens during the consultation and, after the patient leaves, hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready for you to review about two minutes after the visit. The draft is populated with the prescriber fields and the medicines discussed, so the completeness problem, the missing registration number, the blank duration, is handled before you ever look at it. The ICD-10 entries are suggestions for you to confirm, not codes assigned by an engine.

Here is the line we will not cross, and it is the honest centre of this whole topic. We draft; we do not dispense, and we do not transmit. The prescription stays a draft until you sign it, and how it reaches the chemist is your call, paper or print. We do not route it to a pharmacy, and we do not run any e-prescribing transmission. That is a deliberate choice, not a missing feature. Drafting a prescription and transmitting one carry different regulatory weight, and we do only the first, which means the legal validity rests exactly where the law puts it: on your review and your signature.

On the data side, consultation audio is processed in memory and discarded once the note is drafted, so there is no recording sitting on a server. The prescription text lives in the note record, which belongs to your practice, and you can export or delete any visit. On ABDM, we have it on the roadmap; it is not shipped, and we will not mark a roadmap feature as available. Our security posture, including SOC 2, is underway rather than finished, and we say so plainly rather than implying a certification we do not hold. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If you want the deeper engineering detail on how the prescription draft is screened for safety before you sign, the [Rx draft safety explainer](/us/blog/ai-scribe-prescription-draft-safety/) covers the deterministic check. For the wider view of how the prescription tools in this market compare, including where each one fits a real clinic day, the [prescription software guide for India](../prescription-software-for-doctors-india/) lays out the three categories. And for the medico-legal documentation angle that sits next to prescribing, the [medico-legal documentation guide](../ai-scribe-medico-legal-documentation-india/) is the companion.

The thing worth remembering after all the checklist rows: the software is the easy part. A clean, complete, well-signed prescription is something a good tool hands you. Whether it holds up is still about your signature and your judgment, and that is the right place for it to rest. If you want to see your own consults turn into drafts for review, book a short demo or <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>; the seven days begin after your workspace is ready.

---

## Do AI Medical Scribes Code Your Notes? ICD-10 Suggestions, Honestly
https://patientsquare.com/us/blog/ai-scribe-icd-10-suggestions-explained/
Published 2026-06-10 · Tags: ai-scribe, icd-10, coding

The honest difference between an AI scribe that suggests ICD-10 codes and a coding engine that assigns them, and why a person still confirms the code.

A responsible AI scribe suggests ICD-10 codes from the visit; it does not assign or bill them. The difference matters. A suggestion is a starting point a coder or clinician confirms. A coding engine claims to produce the final, billable code. Most AI scribes, ours included, do the first, not the second.

Short answer: a responsible AI scribe suggests ICD-10 codes; it doesn't code your notes. That distinction is the whole point of this page, and it's where honest vendors part ways from the rest. A suggestion is a likely diagnosis code, drawn from the visit, that you confirm. A coding engine claims to assign the final, billable code itself. We do the first. We don't do the second, and we won't pretend to. Here's the difference, why it matters clinically and financially, and what to ask any vendor that blurs the line.

> **Key takeaways**
>
> - An AI scribe should suggest ICD-10 codes, not assign or bill them. A person confirms the code against the documentation.
> - A coding engine claims to finalize codes, often with E&M levels and modifiers; that takes on clinical and financial responsibility a scribe shouldn't.
> - We offer ICD-10 diagnosis suggestions only. No CPT, no E&M leveling, no HCC, no claim submission.
> - Suggestions still save time, because recalling the right code is the slow part; confirming a shortlist is fast.

## Do AI scribes code your notes, or just suggest codes?

They should suggest, and the honest ones say so. Here's the line. An AI scribe listens to the visit and can surface the diagnosis codes that fit what it heard. That's a suggestion: a shortlist, a starting point. You look at it, check it against what's documented, and confirm or change it. The responsibility stays with you.

A coding engine is a different claim. It says: here's the final, billable code, assigned and ready. Often it goes further, attaching an E&M visit level and modifiers. That's not a documentation tool anymore; it's a tool asserting the answer to a question that carries audit and denial risk.

ICD-10-CM has more than 70,000 diagnosis codes, per the CDC's classification. The hard part for a clinician usually isn't deciding the diagnosis, it's finding the exact code among thousands of near-neighbors. A suggestion solves that without taking the decision away from you. For the full set of questions to ask a vendor, including this one, our [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) is the companion guide.

## Suggestion versus coding engine: the honesty table

This is the table to keep in mind when a vendor demo gets vague about "AI coding."

| | ICD-10 suggestion (what we do) | Coding engine (what we don't) |
|---|---|---|
| What it produces | Likely diagnosis codes from the visit | Final, assigned, billable codes |
| Who decides | You confirm against the documentation | The tool claims to decide |
| E&M / visit level | Not produced | Often claimed |
| CPT / procedure codes | Not produced | Often claimed |
| HCC / risk codes | Not produced | Sometimes claimed |
| Claim submission | Never | Sometimes implied |
| Who carries the risk | You, as always | Ambiguous, which is the problem |

The right-hand column isn't inherently wrong to exist; dedicated coding and billing systems are a real category. The problem is a scribe quietly implying it does that work when it doesn't, or doing it without the audit trail a billing system needs. Ask which column a vendor is actually in.

## Why doesn't the scribe just finish the coding?

Because finishing the coding is a clinical-and-financial decision, not a transcription task. The code drives the claim. The documentation has to support the code. Get it wrong and you've got a denial, or worse, an audit exposure. That's a responsibility that belongs to a clinician or a certified coder looking at the whole chart, not to a draft an LLM produced from the conversation.

There's a simple integrity test here. A tool that drafts a note can be wrong and you'll catch it on review, because you're reading the note anyway. A tool that silently finalizes a billable code is asking you to trust an output you might not scrutinize the same way. We'd rather hand you a suggestion you'll obviously confirm than a "final code" that invites you to skip the check. The same logic governs our prescription drafts: the scribe drafts what was said and leaves the safety check to you, the clinician, covered in our [prescription draft safety explainer](../ai-scribe-prescription-draft-safety/).

## What AI Medical Scribe by Patient Square actually does with codes

Plainly: ICD-10 diagnosis suggestions, and nothing past that. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The ICD-10 part is suggestions you confirm.

What we don't do, said clearly so there's no ambiguity in your evaluation:

- We don't assign CPT procedure codes.
- No E&M visit levels computed.
- No HCC risk-adjustment codes.
- We don't submit claims or touch your billing.

If your practice needs an automated coding or billing engine, that's a different product category, and the honest answer is that we're not it. What we are is a scribe that drafts a clean note and narrows the diagnosis-code search so you spend less time hunting through 70,000 codes and more time confirming the right one.

## When is the coding honesty the deciding factor?

For some buyers it's the whole decision. If you're being pitched "AI that codes your visits," slow down and find out whether the vendor means suggestions you confirm or codes they assign. The first is a time-saver. The second is a liability question dressed up as a feature.

We think the honest version is the one that survives an audit: the clinician or coder confirmed every code, the scribe just made the confirmation faster. That's the position we hold, and we'd rather lose a deal to a "full coding engine" pitch than overclaim our way into one. The full price ladder, with no coding-engine asterisks, is on our [pricing page](../../pricing/).

If suggestions-you-confirm is the right fit, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch how the ICD-10 suggestions appear against a real visit, then see the [prescription draft safety](../ai-scribe-prescription-draft-safety/) explainer for the same honesty applied to Rx. The product is a scribe that respects where the decision belongs: with you.

---

## Hospital Management System in India: Modules, Explained
https://patientsquare.com/in/blog/hospital-management-system-explained/
Published 2026-06-10 · Updated 2026-08-29 · Tags: hms, hospital-management, india, emr, clinic-software

A plain-English map of HMS modules for Indian hospitals: OPD, IPD, billing, pharmacy, lab, and the one documentation gap every HMS leaves.

An HMS is a software platform that coordinates the main operational workflows of a hospital or multi-doctor clinic: patient registration, OPD and IPD scheduling, billing, pharmacy, lab, and radiology. In India, most mid-size and larger facilities run some form of HMS. It handles the facility, not the clinical note inside it.

A hospital management system is software that coordinates the facility around the clinical encounter. It commonly covers registration, scheduling, billing, pharmacy, and the lab. Some deployments also include the clinical record. The important procurement question is how the operational modules, record system, and documentation workflow work together at your facility.

This is a module-by-module map of how Indian HMS software is built, where each module lives in a hospital, and what that documentation gap can cost at the end of a long OPD day.

> **Key takeaways**
>
> - This guide maps 8 to 12 common HMS modules. Start with registration, OPD, IPD, billing, pharmacy, and lab.
> - Many HMS deployments coordinate the facility while leaving clinicians with form-heavy documentation. Test the documentation workflow, not just the module list.
> - India's primary-care consultation averages about two minutes (Irving et al., BMJ Open 2017). HMS scheduling reflects that throughput, but documentation does not compress with it.
> - ABDM readiness is becoming a real shortlisting criterion for Indian hospitals; ask which NHA sandbox milestones a vendor has cleared.
> - Hospital Copilot can use the complete Patient Square HIS/EHR as the record system or work alongside an existing HIS/EHR. Both paths require a facility-specific demo.

---

## What an HMS actually manages

The label covers a lot of ground, and vendors use "HMS," "HIS" (hospital information system), and "HIMS" (hospital information management system) almost interchangeably. The working definition in India: an HMS is the platform that moves a patient from the gate to the discharge paper and tracks everything in between.

An HMS can include a clinical record, but a module list alone does not tell you how the record system or documentation work will perform. In many hospitals, the HMS records that a visit happened, who the patient was, what was billed, and what was dispensed while the doctor still writes the note and documents the plan. In a heavy OPD day, that can mean a long stretch of typing after the last patient has left.

This guide maps 8 to 12 modules. Start with the six that matter in almost every shortlist:

### 1. Patient registration and front desk

This is the entry point. New-patient registration, UHID (Unique Hospital Identification) number generation, appointment booking across departments, OPD token queues, and, increasingly, ABHA number linking for facilities working toward ABDM integration.

A well-built registration module avoids repeated data entry. A badly built one creates the queue that backs up into the car park on a busy Monday.

### 2. OPD management

The outpatient module is where most of a hospital's patient volume passes through, and it is where documentation pressure concentrates. The module handles appointment scheduling, vitals entry by a nurse or ward boy, doctor queue management, and the patient handoff to the consulting room.

What it does not do well, in many Indian HMS implementations: the actual consultation note. Doctors get a form. Some systems give a structured template; many give a text box. The OPD module records the slot. It does not write the note.

### 3. IPD and ward management

Inpatient management covers bed allocation and transfers, admission and discharge workflows, nursing notes and care plans, surgeon and anaesthesia documentation, and the discharge summary. The discharge summary is worth separate attention: under the NMC Professional Conduct Regulations 2002, indoor records are expected to be retained for three years, and the discharge summary is the primary transfer-of-care document for insurance cashless claims.

A discharge summary is also one of the highest-friction documentation tasks in a hospital. It often gets written late because the structured format the HMS provides is neither fast nor particularly useful for the next treating doctor.

### 4. Billing and revenue cycle

Billing is usually the module the CFO cares about most, and it shows. Most Indian HMS billing modules are mature: outpatient billing with GST, inpatient billing with room charges and procedure packages, insurance pre-authorisation request generation, TPA claim submission, and co-payment management.

The friction point here is not the billing engine. It is the documentation that feeds it. ICD-10 coding for billing purposes requires a confirmed diagnosis from the clinical note. When that note is thin, a phrase in a text box rather than a structured encounter, the billing team codes what they can and leaves the rest. That is where claim rejections begin.

The scale of that leak is bigger than most finance teams track visit by visit. In FY2024-25, Indian general and health insurers settled 3.26 crore health-insurance claims and paid out ₹94,248 crore, but only about 87% of registered claims were settled: roughly 8% were repudiated and another 5% still sat pending as on 31 March 2025, per IRDAI's annual report.

Not every repudiation is a documentation failure, and it's worth being precise about that. A repudiated claim is one the insurer reviewed and declined, which can turn on policy terms as easily as on paperwork. But IRDAI's own commentary in the prior year flagged documentation gaps and disallowances as a live cause, and a hospital only controls one side of that equation: whether the discharge summary, the diagnosis, and the coded encounter are complete and defensible when the TPA asks.

That is exactly the chain the billing, IPD, and pharmacy modules are supposed to hold together, and exactly the chain a thin clinical note breaks. It changes what a procurement team should weigh, too. A billing module that ingests a complete, coded encounter is worth more than one with a longer feature list, because the feature that pays for itself is the one that gets a cashless claim settled the first time.

### 5. Pharmacy management

Pharmacy covers dispensing against a prescription, inventory management across store and ward stock, expiry tracking, return and wastage recording, and in some systems, drug interaction alerts at the point of dispensing.

The prescription that feeds the pharmacy module comes from the doctor's module, which in most HMS implementations is still a manually typed text field. If the prescription is illegible, abbreviated, or missing a dose, the pharmacist interprets it. That interpretation is a risk.

### 6. Laboratory management

The lab module handles test ordering from OPD and IPD, sample tracking through collection and processing, result entry, and result distribution back to the treating doctor. Integration with analyzers (HL7 or direct API, depending on equipment age) is standard in well-implemented systems; manual result entry remains common in smaller labs.

Result turnaround and communication back to the clinician is where most failures surface. Results land in the HMS. The doctor sees them at the end of the OPD session, if at all, rarely mid-clinic when they could still change management.

---

## The additional modules (and when they matter)

The six above form the core. A larger or multi-specialty hospital may also need:

| Module | What it handles | When it matters |
|---|---|---|
| Radiology / PACS | Imaging orders, film archiving, radiologist reporting | Any hospital with its own imaging |
| Operation theatre | OT scheduling, anaesthesia notes, surgical checklists | Surgical departments |
| Blood bank | Donor registration, blood group inventory, cross-matching | Hospitals with active surgical load |
| HR and payroll | Staff records, attendance, salary processing | When workforce administration needs its own workflow |
| Inventory / central stores | Consumable procurement, indent, stock reconciliation | Any hospital with ward and pharmacy stores |
| CSSD / sterilisation | Instrument tracking through sterilisation cycles | Hospitals with OT and day-care procedures |
| Diet and kitchen | Patient meal ordering by diet type and ward | Larger tertiary hospitals |

You do not need all of these on day one. Check whether a vendor's quote prices a base package plus modules. The procurement question is which workflows you cannot operate without, not which modules look good in a demo.

---

## The documentation gap an HMS leaves

This is the part most HMS vendor pitches skip, because it is not their problem. It is the doctor's problem.

An HMS optimises flow. A patient can check in, wait, see the doctor, have vitals taken, and leave with a prescription while the system records each handoff. What the HMS log may not contain is the doctor's clinical reasoning, the differential, or the finding that made this patient different from the last one with the same chief complaint.

Indian OPDs run on throughput. The 67-country consultation-time analysis published in BMJ Open found that Indian primary-care visits averaged about two minutes in its included studies. That average makes the documentation problem hard. A form-heavy record can consume more time than the visit itself.

The results stack up:

- Notes are thin. A diagnosis code and a prescription list rather than a structured SOAP encounter.
- Discharge summaries are written under time pressure, late, and often lack the continuity detail that a specialist referral or a cashless claim actually needs.
- ICD-10 coding is done by the billing desk, not by a doctor looking at a documented encounter.
- Medico-legal risk concentrates in the gap between what happened and what was recorded.

The HMS knows the slot happened. The note, if it exists, is whatever the doctor managed to type while asking the patient the next question.

---

## Where Hospital Copilot fits into this picture

Hospital Copilot gives a hospital two record-system choices. It can use the complete Patient Square HIS/EHR as the system of record, or it can work alongside an existing HIS/EHR. The second path can suit a hospital that is keeping an incumbent system while assessing selected Hospital Copilot workflows.

The core Copilot set includes the AI Medical Scribe, which hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review and sign-off. Hospital Copilot also names AI Copilot EHR, Claims Management, AI Discharge Summary, and Bed / IPD Management. The names are the product-scope ceiling. They do not establish a named-vendor integration, automatic filing or write-back, a coding engine, or a full billing engine.

For the alongside path, that means:

- The OPD scheduling and queue management stays in the HMS.
- Billing, pharmacy, and lab flow stays in the HMS.
- The consultation note can be drafted from the conversation for clinician review and sign-off.

The output is a structured SOAP note the doctor reviews and signs, not a form they fill in parallel with talking to a patient. ICD-10 suggestions are not automated claim coding and do not set the billing code.

For an Indian OPD, three design decisions are worth knowing about. The scribe handles code-mixed Hindi and English on input and returns the note in clean clinical English, which is what the medico-legal record needs, not what the conversation sounded like. The prescription comes back as a draft from the consult. The scribe doesn't screen it for interactions or dosing; the doctor makes that call when they review and sign, the same as they do today. And visit audio is processed in memory and discarded once the note drafts: no recording sitting on a server, which matters under the [DPDP Act 2023 framework](../dpdp-act-clinics-guide/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

This is not an HMS integration claim. For the alongside path, Hospital Copilot works beside the existing HIS/EHR. For the complete path, evaluate the Patient Square HIS/EHR as the hospital's record system. In both cases, validate required OT, pharmacy, LIMS, RIS/PACS, billing, and specialist workflows in the demo.

---

## ABDM and the HMS procurement question

Hospitals shortlisting HMS software increasingly have ABDM questions on their checklist. The right question is not "are you ABDM-ready?" It is "which milestones have you cleared, and are they live in production?"

The NHA's sandbox-to-production process certifies software against three milestones:

- **M1** (identity provider): ABHA number creation and verification, plus facility registration on HFR and professional registration on HPR.
- **M2** (Health Information Provider): sharing FHIR-format records with a patient's consent to another provider.
- **M3** (Health Information User): fetching records from other providers into the treating clinician's view.

India has crossed 100 crore ABHA-linked health records under ABDM, with more than 450 health-tech solutions integrated into the ecosystem (National Health Authority, May 2026). Cross-provider delivery needs both sides of the exchange: the sending system must share as an M2 Health Information Provider and the receiving system must fetch as an M3 Health Information User, with the patient's consent. A vendor who says "ABDM-ready" without naming the milestone may be describing anything from M1 to all three.

Patient Square's ABDM integration is on the roadmap and is not yet shipped. A hospital that needs live ABHA record linking today should select an HMS that has cleared the relevant milestones rather than rely on a roadmap.

---

## How to evaluate an HMS: a field checklist

Most Indian hospitals evaluate HMS software through demos and references. The demo usually shows the system working well. The reference call usually reaches the IT manager, not the nurse or the OPD doctor who runs it daily.

Start before the shortlist, not during it. Map your existing modules and where they actually break. Billing? Pharmacy inventory? Doctor documentation? The module you are trying to fix should drive the shortlist. A system built for a teaching hospital may struggle in a focused surgical hospital, and a vendor's references will show that faster than any demo.

In the demo itself, have the doctor who will use it daily run the OPD module, not the IT team. Count the clicks from vitals entry to prescription. Ask billing to pull a sample cashless claim and trace the ICD-10 code back to the documented encounter. Ask the pharmacy team what happens when a prescription comes through illegible or missing a dose. Those three scenarios reveal more than any features walkthrough.

On ABDM: ask which milestones are certified and live. Ask for the NHA production certificate, not a sandbox one. Ask whether the ABHA linking is patient-opt-in or automatic. They are not the same thing clinically or legally.

On pricing: many Indian HMS vendors do not publish prices. Get implementation, servers, network, training, and annual maintenance alongside the software licence. Ask for references from hospitals with a similar size and specialty mix that have a live deployment.

For a smaller clinic rather than a hospital, a full HMS may be more than the problem warrants. The [clinic management software scorecard](../best-clinic-management-software-india/) covers that category separately, including where a documentation layer fits if billing and scheduling are already handled.

---

## A note on the documentation problem before you buy

The HMS decision is a facility decision, not a clinical one. The right HMS cuts the administrative time your billing team spends chasing data, the time your pharmacy spends clarifying prescriptions, and the time your admissions desk spends reconciling a discharge without a proper summary.

It does not cut the time your doctors spend documenting.

That is a different problem. Across a busy OPD, a few extra minutes of post-visit typing becomes hours of doctor time. It happens between patients, at lunch, and after the last patient. The HMS schedules it; the doctor absorbs it.

If that is the fire you are fighting, assess both Hospital Copilot deployment modes before buying another HMS module that leaves the documentation workflow unchanged.

<a href="/in/products/hospital-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> and bring your facility size, department mix, incumbent HIS/EHR, and one difficult workflow. The demo should test whether the complete Patient Square HIS/EHR path or the alongside path fits the hospital. If you are mapping a smaller clinic category instead, the [clinic management software scorecard](../best-clinic-management-software-india/) is the better starting point.

---

## AI Medical Scribe for Pediatrics: Caregiver-in-the-Room Notes
https://patientsquare.com/us/blog/ai-scribe-for-pediatrics/
Published 2026-06-09 · Updated 2026-07-22 · Tags: ai-scribe, pediatrics, multi-speaker

How an AI scribe handles the multi-speaker pediatric visit, where a parent answers for the child, plus the caregiver-consent nuance you should plan for.

A good ambient scribe handles multiple speakers, which is exactly the pediatric case: the clinician, the child, and a caregiver who often answers for the child. The note should attribute history sensibly and come back as a clean SOAP note. The multi-speaker room is the real test, so trial it on your actual visits.

The pediatric visit is the case that breaks weaker scribes. A parent reports the symptoms. The clinician asks the questions. Sometimes the child chimes in too. Three voices, one note, and the history has to land on the right source. A capable ambient scribe handles that and returns a clean SOAP note. Pediatrics also adds a consent wrinkle most specialties don't have: the caregiver gives consent on the child's behalf, so both your script and your tool's audio handling matter. Here's how the fit works, and where to be careful.

> **Key takeaways**
>
> - The pediatric visit is a multi-speaker room: clinician, child, and a caregiver who often answers for the child. Handling that well is the test.
> - Consent comes from the caregiver on the child's behalf. A tool that never stores audio shrinks the exposure either way.
> - We don't ship pediatric templates. Specialty fit means handling the pediatric conversation, not a pre-built form.
> - The hard version of the room is a noisy exam space, a restless toddler, and a parent talking over the clinician. Trial that, not a quiet demo.

## Can an AI scribe handle the caregiver-in-the-room visit?

This is the pediatric question, and it's a real one. Most documentation tools are demoed on a clean two-person consult. A pediatric visit isn't that. A caregiver reports the history, often in more detail than the child could, the clinician asks and examines, and the child may answer some questions directly. The note has to make sense of who said what.

A capable ambient scribe manages multiple speakers and attributes the history sensibly. The caregiver's account of the cough. The clinician's exam findings. The plan as discussed. The genuinely hard version is a noisy exam room next to a crowded waiting area, a restless toddler, a parent talking over the clinician. That's where products diverge. So trial that visit, not a quiet scripted one.

If you want the broader evaluation lens first, our [9-question scorecard](../how-to-evaluate-ai-medical-scribe/) lays out what to test across any specialty.

## Who consents to recording a pediatric visit?

The caregiver consents on the child's behalf. Your script should say so plainly: the conversation is being captured to help draft the note, and the caregiver can decline. In the 11 US all-party-consent states this isn't optional.

This isn't hypothetical. A proposed class action filed against Sharp HealthCare in late 2025 alleges patients were recorded by an ambient AI tool without consent. Pediatrics raises the stakes, because the person giving consent isn't even the patient. Two things protect you. A clear caregiver-facing script. And a tool that doesn't keep the audio at all. Ours processes in memory and discards the moment the note drafts, so no recording of a child's visit sits in storage for anyone to find later. Our [psychiatry privacy guide](../ai-scribe-for-psychiatry-privacy/) walks the highest-stakes version of this question, and the same logic carries straight over to pediatrics.

## Specialty fit without specialty templates: the honest version

Here's a claim we won't make: that we have a "pediatric template." We don't ship per-specialty templates. Saying so out loud is the honest move. Specialty fit isn't a pre-built form. It's whether the scribe can follow the pediatric conversation, pick up the caregiver-reported history, the weight-based dosing context, the developmental notes, and turn all of it into a clean SOAP note.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The Rx draft matters in a specific way for kids. Weight-based dosing is where errors hurt most, and the draft reflects the dose you dictated rather than checking it. The scribe does not screen for interactions or dosing, so you check every prescription against the child's weight and chart before you sign, exactly as you do now. The tool writes a draft. The dosing call is still yours.

## A pediatric visit, start to signed note

Picture a 20-minute well-child visit. A parent, a restless toddler, the clinician working through the exam. The scribe captures the caregiver's history and the findings as they're said, the note comes back drafted, and the clinician signs before the next patient walks in. That AMA median of 36 minutes of EHR time per 30-minute visit? That's the documentation load a scribe pulls off the evening.

The room gets harder than the demo version, and that's the part to plan for. A grandparent answering alongside the parent. A toddler crying through the exam. Two people talking over each other while you're trying to listen. A scribe that holds up there, attributing the history to the right source through the noise, is the one worth keeping. A quiet scripted consult won't tell you whether it can. Your loudest, most crowded visit will.

## The honest pediatric fit verdict

An AI scribe fits pediatrics when it handles the multi-speaker, caregiver-led conversation and leaves the dosing and consent decisions with you. It won't hand you a magic pediatric template, because we don't believe in selling one. It won't write your caregiver consent script either. What it does do is draft a clean note out of a genuinely messy room. That's the part that eats your evening.

So if your visits are caregiver-heavy and run loud, that's the trial to run. You can [compare the options](/us/compare/) and check the full price ladder on our [pricing page](../../pricing/). Then use the [comparison page](/us/compare/) to check the published scope against your busiest pediatric session.

---

## AI Medical Scribe for Nurse Practitioners and PAs: Fit and Limits
https://patientsquare.com/us/blog/ai-scribe-for-nurse-practitioners/
Published 2026-06-08 · Updated 2026-07-22 · Tags: ai-scribe, nurse-practitioner, physician-assistant

How an AI scribe fits NP and PA workflows, what it drafts and what it does not, and a scope-of-documentation table for advanced-practice clinicians.

Yes. The work an AI scribe automates, turning the visit conversation into a structured note, is the same whether the clinician is a physician, NP, or PA. It drafts a SOAP note, ICD-10 suggestions, and a prescription draft you review and sign. The role does not change how the scribe captures or structures the visit.

Short version: an AI scribe fits nurse practitioners and physician assistants for the same reason it fits physicians. What it automates, turning a visit into a structured note, doesn't care about your credential. NPs and PAs carry the same charting load, frequently the same full panels, plenty of the same after-hours note-finishing. So what an ambient scribe does, and what it won't do, looks identical across roles. One thing is worth spelling out, and that's scope. The tool drafts. You decide what falls inside your prescriptive authority, and you sign. Here's the fit, and where it stops.

> **Key takeaways**
>
> - An AI scribe fits NP and PA workflows the same way it fits physicians: it drafts the note, you review and sign.
> - The Rx draft is a starting point you confirm against your own prescriptive authority, which varies by state and, for PAs, by collaborative agreement.
> - The documentation responsibility stays with whoever signs. Co-signature workflows are unchanged.
> - A 2025 UCLA trial measured about 41 seconds saved per note; at a full advanced-practice panel that compounds into evenings back.

## Does an AI scribe actually fit an NP or PA workflow?

Yes. And the reason is simpler than the vendor pitches make it. An ambient scribe listens, transcribes, and drafts a structured note. That mechanism doesn't care who's in the room, physician or NP or PA. The visit sounds like a visit. The note that comes back is a SOAP note either way.

What's different for advanced-practice clinicians isn't the technology. It's the load. NPs and PAs run full patient panels across primary care, urgent care, and specialty clinics, and they describe the same documentation burden physicians do. The AMA found primary-care clinicians log a median of 36 minutes of EHR time per 30-minute visit. That number doesn't drop because the clinician is an NP. So the relief lands just as hard: the note drafted about two minutes after the visit ends.

If you want the broader buyer's view before you trial anything, our [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) is the place to start.

## What the scribe drafts, and what stays yours

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For an NP or PA, the whole picture comes down to one line: what it drafts, and what stays your call. The table:

| | The scribe drafts | You decide and sign |
|---|---|---|
| Clinical note | Structured SOAP from the visit | Edits, corrections, final content |
| Codes | ICD-10 suggestions | Which codes are right; a coder confirms |
| Prescriptions | A draft reflecting what you said | Dose, interactions, and whether it's within your authority |
| Attestation | Nothing | The signature and the record ownership |

The tool never files, codes, or prescribes on its own. For advanced practice that matters more than it looks at first. Every scope question lives in the right-hand column, the column where you already make the calls.

## How does scope of practice change the picture?

Not what the scribe does. What you do with the draft, which is how it should work.

Prescriptive authority for NPs and PAs varies by state. For PAs it often hangs on the collaborative or supervisory agreement in place. A scribe drafting a prescription doesn't know any of that, doesn't override it, and shouldn't. The draft is a starting point. You confirm it against your own authority before signing, the same judgment you already apply without a scribe. Where your state or agreement caps what you can prescribe, you trim the draft first.

One boundary on the Rx draft is worth stating plainly. It does not screen the chemistry for you. There is no drug-interaction check, no dose check, no block; the draft simply writes out the drug and dose you dictated. Checking interactions and renal dosing is the same clinical read you do on every prescription, and it stays yours. The scope call is a separate thing, and it's yours too.

## What about co-signature and supervising-physician workflows?

If your visits involve a co-signing or collaborating physician, the scribe doesn't disrupt that. It drafts the content of the note. Your existing attestation and co-signature process runs exactly as before, and the clinician who signs owns the record. A supervising physician reviewing an NP's or PA's note arguably gets through it faster when the draft is cleaner and more complete, because there's less to reconstruct.

Here's the honest limit. The scribe won't manage your co-signature logic or route notes through an approval chain. It documents; it doesn't run workflow. If you need automated routing between an NP and a supervising physician, that's a question for a workflow system, not for a scribe. We draft the note. Your practice handles the sign-off path.

## Where an AI scribe helps an NP or PA most

The biggest win is timing more than raw minutes. A 2025 UCLA randomized trial measured about 41 seconds saved per note for one ambient tool. Modest on a single note. But advanced-practice panels run high-volume, and 41 seconds a note adds up across a packed day. The felt difference is the one physicians report too: notes finishing during clinic instead of at 9pm.

Two settings where it earns its place fastest. The first is high-volume primary or urgent care, full panels and short visits and charting that never quite ends, where the scribe drafts while you move to the next patient. The second is the specialty clinic with a documentation-heavy visit, where detailed histories you'd otherwise rebuild from memory after hours come back drafted in two minutes.

The realities of a busy, multi-complaint visit, where ambient tools differ most, are covered in our [primary-care 20-patient-day model](../ai-scribe-for-primary-care/), which applies cleanly to a full NP or PA panel.

## The honest fit verdict for NPs and PAs

An AI scribe fits NP and PA workflows well. One boundary, stated plainly: it drafts documentation, and that's all it claims to be. Not a scope authority. Not a workflow engine. It drafts the note and the codes and the prescription draft, and you confirm what falls inside your practice authority and sign. That's the same line you already hold, just with the typing taken off your plate.

If that fit matches your clinic, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to see a finished note against your own visit type, and the full price ladder is on our [pricing page](../../pricing/) with no role-based gating, because the product is the same whoever signs. Then review the [product workflow](/us/products/practice-copilot/) against your real panel and judge the documented scope.

---

## Free EMR Software in India: What It Won't Do
https://patientsquare.com/in/blog/free-emr-software-india-honest/
Published 2026-06-08 · Updated 2026-07-22 · Tags: emr, free, open-source, india

Free EMR software like OpenEMR and Bahmni is real and usable. Here is when it is enough for an Indian clinic, and the one documentation gap it leaves.

Yes. OpenEMR and Bahmni are both open-source, zero-licence-cost EMRs used in India. You install them yourself, or pay a vendor to host and support them. The software is free; implementation, hosting, and ongoing IT support are not. A 5-doctor clinic can run OpenEMR for ₹0 in licence cost if someone on the team has the time and ability to set it up.

Free EMR software in India is real. OpenEMR and Bahmni are both zero-licence-cost, both actively maintained, and both running inside Indian clinics right now. Whether it's enough for your clinic depends entirely on what you need it to do. This post covers what each option actually handles, what it skips, and the one gap that surprises nearly every clinic that goes the free route.

> **Key takeaways**
>
> - OpenEMR and Bahmni are the two credible free/open-source options in India. Both are zero-licence-cost; neither is zero-effort-cost to run.
> - Free EMR software covers appointments, patient registration, clinical notes you type, billing, and basic lab orders. It does not draft the note from the consultation.
> - The documentation gap is the most common reason free EMR clinics eventually add a separate tool. On a 60-patient OPD day, typing every note yourself is the bottleneck, not the software.
> - ABDM integration in free EMRs is a work in progress. Neither OpenEMR nor Bahmni ships a universally certified, production-ready ABDM connection as a standard feature. AI Medical Scribe by Patient Square has ABDM on its roadmap only too.
> - Adding an ambient scribe on top of a free EMR is the most cost-effective path for a clinic that wants both records and documentation automation. The scribe works alongside your EMR; it does not replace it.

## OpenEMR: the one most Indian clinics mean when they say "free EMR"

OpenEMR has been around for more than three decades. It is the most widely deployed open-source EMR in the world by installation count, running in over 100 countries. For India, that matters because it means the community is large, the documentation is thorough, and most of the edge cases have already been hit and fixed by someone else.

What it covers out of the box:

- **Patient registration and demographics.** Name, contact, age, gender, allergies, insurance. Standard fields for a clinic intake form.
- **Appointment scheduling.** Single and multi-provider calendars, patient portal (if you set it up).
- **Clinical notes.** SOAP-structured forms, free-text fields, problem lists, medication lists, vitals.
- **Billing.** Claims, invoices, and a revenue module. This part takes configuration for Indian billing conventions, but the framework is there.
- **Lab orders and results.** Basic lab interface; more involved integration with external labs needs custom work.
- **Prescription list.** You enter what you're prescribing; it stores and prints it. It's a record, not a draft built from the consult.
- **Reports.** Patient-count reports, encounter summaries, basic analytics.

What it does not cover:

- **Ambient documentation.** OpenEMR does not listen to your consultation. It stores what you type. If you see 60 patients a day and type every note yourself, OpenEMR does not change that equation.
- **ICD-10 suggestions during the note.** You can add diagnoses from a pick-list, but the system does not suggest based on what was said in the room.
- **A prescription draft from the consult.** OpenEMR stores what you type into its prescription list. It doesn't draft the script from what was said in the room, ready for you to review and sign.
- **ABDM production integration.** There are community efforts to add ABDM connectivity, but this is not a standard, NHA-certified feature in the version you would download today.

The real cost of OpenEMR is time. Licensing is free; installation is not. A clinic that self-hosts on a cloud server (DigitalOcean, AWS LightSail, or a local machine) pays server costs: ₹800–2,500/month for a small cloud VM, or near zero if on-premise with existing hardware. Setup by a local IT vendor runs ₹15,000–50,000 one-time depending on scope and who you hire. Then there's ongoing: upgrades, backups, occasional bugs. If someone at your clinic has the skills, this is manageable. If not, you're paying a vendor anyway, and the comparison to a paid hosted EMR at ₹1,000–1,500/month narrows fast.

## Bahmni: built for South Asia, stronger for hospitals than solo practice

Bahmni was built by ThoughtWorks, originally for an NGO hospital in Bihar, and is now maintained by the Bahmni Coalition, a non-profit. The design goal was explicit: a system that works well in low-resource, low-connectivity environments in South Asia and Africa. Today it runs in hospitals, community health programs, and district-level facilities across India, Nepal, Bangladesh, Ethiopia, and elsewhere.

Technically, Bahmni wraps OpenMRS (an open-source patient record framework) with a clinic management layer that adds pharmacy, billing, radiology ordering, and a point-of-care interface. The stack is more complex than OpenEMR's single-application install. That complexity is worth it if you have multiple departments or inpatient beds. For a solo GP or a two-room clinic, it is probably more software than you need.

Where Bahmni is stronger than OpenEMR:

- **Pharmacy and dispensing.** Bahmni's pharmacy module is tighter and more configurable for Indian dispensing workflows.
- **Multi-department environments.** OPD, IPD, radiology, and lab can run as coordinated modules under one system.
- **Community health program workflows.** Visit scheduling, program enrolment, and basic population health tracking.
- **Offline capability.** Designed for sites with unreliable internet. Local sync handles gaps.

Where it is harder to deploy:

- **Technical complexity.** Bahmni's stack (multiple services, Linux server, PostgreSQL, Nginx) is a real DevOps project. Most clinics need a vendor or an in-house technical person to stand it up.
- **Support ecosystem.** The community is active but smaller in India than OpenEMR's. Finding a local implementation vendor is not hard in major cities; in smaller towns it can be.
- **Documentation burden.** Same as OpenEMR: the system holds what you enter, it does not generate the note. A Bahmni implementation does not solve the documentation problem.

| OpenEMR fits | Bahmni fits |
|---|---|
| Solo GPs and small clinics | Multi-department hospitals |
| Easier single-server setup | Pharmacy and dispensing workflows |
| Larger global community | Low-connectivity / offline environments |
| Billing module configurable for India | Community health programs |

_Which free EMR fits which setting. Both are zero-licence-cost; Bahmni requires more implementation effort._

## When free EMR software is actually enough

There is a category of clinic where a free EMR works well and the tradeoffs are worth accepting.

**It works when:**

You have a doctor or staff member with genuine technical ability, not just "comfortable with computers" ability. Setting up OpenEMR correctly takes hours. Keeping it updated takes time. If that person exists at your clinic, you are not paying a vendor's margin for something your team can handle.

You have low patient volume. Below around 20–30 patients a day, typing notes in a structured free-text field is annoying but not a bottleneck. The documentation problem compounds as volume rises.

You already have a separate billing workflow you don't want to replace. Some clinics run billing through a standalone accounting tool or an outsourced accountant. If that's working, an EMR that does only clinical records without billing integration is fine.

You explicitly don't need ABDM integration today. If you are not planning to link ABHA records in the near term, this constraint disappears.

**It starts to break when:**

Patient volume climbs past 40–50 per day. At 60 patients and a two-minute average consultation (the India primary-care average from a 67-country BMJ Open review by Irving et al., 2017), there is no time to type a thorough note between patients. The EMR is ready; the bottleneck is documentation speed.

Staff turnover hits your IT dependency. The person who set up your OpenEMR instance leaves. Nobody else knows how to update it. Suddenly your "free" software has a vendor dependency you didn't budget for.

You need an audit trail a regulator or insurer can read. The Indian Medical Council (Professional Conduct) Regulations 2002 expect indoor records retained for three years and producible within 72 hours of a request. A self-managed server backup is your problem.

## The documentation gap that surprises every clinic

The most common thing I hear from doctors who run OpenEMR or a similar free system is some version of: "The records are fine. The notes are the problem."

The records part is solved. OpenEMR holds every patient encounter. The documentation part, which means producing a legible, structured, clinically defensible note about what actually happened in the room, is still the doctor's job.

On a 14-patient Tuesday, that is manageable. On a 70-patient clinic day, typing those notes between consultations is the bottleneck, or it gets done at 10pm, which is worse. Free EMR software does not help with that. It is a record store, not a note generator.

This is what an ambient scribe does differently. Patient Square is an AI clinical platform, and its AI Medical Scribe is the ambient scribe module: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. It works alongside whatever you already use. If your records are in OpenEMR, you copy the note in. If you keep paper records, you copy it there. The scribe does not need to integrate with your EMR; it just removes the typing.

For a clinic already running a free EMR, adding a scribe is the biggest single upgrade available. The EMR cost stays at zero. Documentation time drops, ICD-10 suggestions appear during the note rather than after you've already moved on, and the prescription arrives as a draft from the consult, ready for you to review and sign. The scribe doesn't screen that draft for interactions or dosing. You make that call when you sign, the same as you do now.

The scribe's India price starts at ₹1,599 per clinician per month on the Assist annual plan, ex-GST. Add 18% GST and the invoice is about ₹1,887. That is the only layer you are adding to a free EMR setup, and you can stay on Assist since you already have the records handled.

_Sources: Irving et al., BMJ Open 2017; openemr.org; patientsquare.com._

## The honest comparison: free EMR vs paid hosted EMR vs free EMR plus a scribe

The "free EMR" choice is really a three-way decision.

| | Free EMR (OpenEMR / Bahmni, self-managed) | Paid hosted EMR (HealthPlix Pro) | Free EMR + ambient scribe |
|---|---|---|---|
| **Licence cost** | ₹0 | ~₹1,000/mo (₹11,999/yr) | ₹0 EMR |
| **Hosting / infra cost** | ₹800–2,500/mo (cloud VM) or hardware | Included | ₹800–2,500/mo (same) |
| **Setup effort** | High (hours to days) | Low (vendor-onboarded) | High for EMR; scribe is browser/app |
| **IT dependency** | High (you manage updates, backups) | Low (vendor manages) | Same as free EMR |
| **Documentation speed** | No change (you type every note) | No change (you type every note) | Drafts note from consultation audio |
| **ICD-10 suggestions** | Pick-list only | EMR-native pick-list | Suggested from consultation context |
| **Prescription** | Typed into Rx list | Rx module with drug-interaction alerts (HealthPlix) | Draft from the consult; you review and sign |
| **ABDM** | Community efforts, no standard certified feature | Listed as feature (HealthPlix) | Roadmap, not shipped |
| **Added cost for documentation** | A scribe (from ₹1,599/mo) or your evening | A scribe (from ₹1,599/mo) or your evening | from ₹1,599/mo (already included) |

The table makes the trade visible. A free EMR saves the ₹1,000/month licence fee; it doesn't touch the documentation problem. A paid hosted EMR is easier to run but doesn't fix documentation either. Neither column replaces the documentation layer.

The "free EMR plus scribe" path is what a lot of independent GPs in India are actually doing. Zero on the EMR licence, from ₹1,599 on the scribe. Total monthly cash out: ₹1,599 plus ₹800–1,000 for a cloud VM, roughly ₹2,400–2,600 all in. A hosted paid EMR with a separate scribe would still cost more.

The one scenario where a paid hosted EMR wins without question: you don't want the IT responsibility. If nobody at your clinic wants to manage servers, backups, and upgrades, pay a vendor to handle that and get back to patients. The convenience is real and the cost difference is not enormous.

If you are on the fence, the [India scribe comparison](../india-ai-scribe-comparison/) covers how different scribe tools (EkaScribe, Augnito, and AI Medical Scribe by Patient Square) compare on features and pricing. The US-facing post [free EHR and AI scribe vs standalone](/us/blog/free-ehr-ai-scribe-vs-standalone/) covers a different question entirely: embedded scribe in a US EHR vs a standalone tool, which is a distinct choice from the free-EMR-in-India question here.

## When to call a free EMR the wrong answer

Three situations where we'd tell a clinic to skip the free option:

**You need billing and EMR tightly coupled.** Free EMRs have billing modules, but configuring them for Indian GST invoicing and insurance formats is work. If billing errors cost you real money or time, the configuration risk of a self-managed billing module is worth paying a vendor to avoid.

**You want ABDM-linked records today.** If ABHA record sharing is a near-term need, a certified EMR vendor who has cleared the NHA sandbox milestones is the right answer, not a free tool with work-in-progress community integrations. HealthPlix, for instance, lists ABDM as a feature. AI Medical Scribe by Patient Square does not yet ship ABDM; it's on our roadmap, and we won't claim otherwise.

**You have a multi-specialty setup with inpatients.** Bahmni can handle this but it's a project. Paid, cloud-hosted HMS vendors with dedicated implementations make more sense at that scale.

## Starting point

If you're evaluating free EMR software for an Indian clinic:

1. Stand up the OpenEMR demo instance on your laptop. It takes under an hour with Docker. See if the patient registration and note workflow fits how you work.
2. Decide whether you'll self-host or use an OpenEMR hosting vendor. Several India-based vendors offer managed OpenEMR hosting for ₹1,000–2,000/month, which removes most of the IT burden.
3. Run a week on the free EMR and notice where your time actually goes. If the bottleneck is note-typing, add a scribe. If it's billing or ABDM, reconsider your options.

Book a 20-minute demo to see how AI Medical Scribe by Patient Square sits alongside a free EMR setup, or <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> to see what the documentation output looks like on your own patient conversations.

---

## How to Evaluate an AI Medical Scribe: 9 Questions
https://patientsquare.com/us/blog/how-to-evaluate-ai-medical-scribe/
Published 2026-06-05 · Updated 2026-07-22 · Tags: ai-scribe, buyer-guide, evaluation

A clinician-built scorecard for choosing an AI medical scribe: audio handling, Rx, coding honesty, languages, export rights, and pricing transparency.

What happens to the visit audio, and when is it deleted? It separates vendors faster than price or features. Accept only a one-sentence answer with a timeline. AI Medical Scribe by Patient Square processes audio in memory and discards it the moment the note is drafted, so there is no recording to retain, leak, or subpoena.

Most AI scribe demos look identical. Clean note, two minutes, scripted visit. The differences that decide it sit underneath: what the tool does with your audio, whether it drafts prescriptions and how it checks them, whether it suggests codes or pretends to bill them, which languages it actually handles, whether you can take your notes and walk, and what the price is after year one. Nine questions sort the field. Here's the scorecard.

Take it into every demo. A vendor who answers all nine cleanly, in plain sentences, is rare. That's the point.

> **Key takeaways**
>
> - Nine questions separate AI scribes faster than any feature grid: audio handling, Rx drafting, Rx safety, coding honesty, languages, export rights, BAA posture, pricing transparency, and trial quality.
> - The fastest disqualifier is the audio answer. A vendor who can't say where the recording lives and for how long, in one sentence, has answered the question.
> - Primary-care physicians log a median of 36 minutes of EHR time per 30-minute visit, so the tool you pick runs your evenings, not just your notes.
> - Make the scorecard your demo agenda. Ask the same nine of every vendor and compare the answers side by side.

## The 9-question scorecard, at a glance

Score each vendor 0 to 2 per row: 0 if the answer is evasive or wrong, 1 if partial, 2 if it's a clean, specific, in-writing yes. A tool worth trialing clears most of these without a follow-up email.

| # | Question | What a strong answer sounds like |
|---|---|---|
| 1 | What happens to the visit audio, and when is it deleted? | "Processed in memory, discarded when the note drafts. No archive." |
| 2 | Does it draft prescriptions, and who's the safety check? | "It drafts; you review and sign. The clinician is the check, not an automated screen." |
| 3 | Does it claim to code or bill? | "ICD-10 suggestions you confirm. Not a coding or billing engine." |
| 4 | Which languages does it actually capture? | A named list that matches your patients, with notes in clean English. |
| 5 | Can I export and delete any visit, anytime? | "Yes and yes, self-serve, no fee, no support ticket." |
| 6 | Will you sign a BAA, and are you "HIPAA certified"? | "BAA for any practice size. And no one is HIPAA certified, no such certificate exists." |
| 7 | What's the price after year one? | The full ladder in writing: launch, annual, month-to-month. |
| 8 | What's the real failure mode on a noisy, multi-speaker visit? | An honest answer, not "it's perfect." |
| 9 | Can I trial it on my own visits before I commit? | "Yes, after assisted setup: 7 days in your real clinic." |

The rest of this guide is one section per question, so you know what a good answer looks like and where vendors quietly fail.

## Question 1: what happens to the visit audio?

Ask this before you ask about price. A visit recording is more revealing than the note, because it holds everything that didn't make the note. Vendors handle it very differently. Some retain audio for days or weeks. Some let you opt out. Some are vague, which is its own answer.

This isn't theoretical. A proposed class action filed against Sharp HealthCare in late 2025 alleges patients were recorded by an ambient AI tool without consent, with more than 100,000 patients potentially affected. The cleanest defense against that whole category of risk is not retaining the audio at all.

Our position: audio is processed in memory and discarded the moment the note is drafted. No archive, not for us, not for the practice, not for anyone. What survives is the note you reviewed and signed. If you want the privacy and consent angle in depth, our [psychiatry privacy guide](../ai-scribe-for-psychiatry-privacy/) walks the behavioral-health version of this question, where the stakes are highest.

## Question 2: does it draft prescriptions, and what checks them?

A lot of scribes stop at the note. Some draft a prescription too, which saves real time, but a prescription draft an LLM wrote is still a draft an LLM wrote. The question isn't only "does it draft Rx," it's "who catches a bad one." The honest answer for any scribe is you, the prescriber. Be wary of any vendor that implies software will catch it for you.

The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The draft reflects what was said in the room. The scribe doesn't screen it for interactions, dosing, or contraindications, and it never goes to a pharmacy on its own. You do that check when you read and sign, exactly as you do today. It's a draft, not e-prescribing, and you stay the prescriber. The mechanics are in our [prescription draft explainer](../ai-scribe-prescription-draft-safety/).

## Question 3: does it claim to code or bill your notes?

Here's a line that separates honest vendors from the rest. A scribe can suggest ICD-10 codes from the conversation. It should not claim to be a coding engine, an E&M leveler, or a billing system. Coding is a human-confirmed clinical-and-financial decision, and a tool that pretends otherwise is selling risk.

We offer ICD-10 suggestions to speed your coding. A coder or clinician confirms them. That's the whole claim. We don't ship CPT, E&M, or HCC automation, and we won't pretend to. The honest version of this distinction is the entire point of our [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/). If a vendor blurs "suggests codes" into "codes your notes," ask exactly what gets submitted and by whom.

## Question 4: which languages does it actually capture?

Read the language list literally, then test it. "Multilingual" without a named list is marketing, and a list that looks long on a slide can still miss the accents and dialects your patients actually speak. The only proof is your own clinic.

We capture English and more languages, with notes always returned in clean clinical English. Input can be multilingual; the output note is English. In low-signal settings, capture works offline with on-device encryption and syncs later. If your patients code-switch or carry accents a model rarely hears, that's the test case to run on day one of a trial, not after procurement.

## Question 5: can you export and delete any visit, anytime?

This is the lock-in question, and it's easy to skip until you want to leave. Ask three things. Can I export any visit? Can I delete any visit? Do you sell or share clinical data? The answers you want are yes, yes, and no, and you want them in the contract, not the sales deck.

Our answer: notes belong to your practice, you can export or delete any visit at any time, and we never sell or share clinical data. If export needs a support ticket or carries a per-record fee, that's friction designed to keep you. For the buyer who wants the full ownership and exit checklist, run the same questions a switching practice runs.

## Question 6: will the vendor sign a BAA, and what's the compliance posture?

The compliance floor isn't optional, and a vendor who can't clear it is out, however good the note looks.

The floor is a signed BAA, available to any practice size, plus encryption in transit and at rest and access you can audit. Software is never "HIPAA certified," because no such certificate exists. Treat that phrase as a red flag. We maintain HIPAA compliant safeguards and offer a BAA to every customer.

One level up, ask where the vendor sits on an independent audit. Ours is straight: our SOC 2 Type II audit is underway, and we won't call ourselves "certified" until it's finished. "Audit in progress" and "certified" are different things, and a vendor who runs the two together has told you something about how carefully they'll describe everything else.

## Question 7: what's the price after year one?

Get the full ladder, per clinician, in writing: the launch rate, the annual-commitment rate, and the month-to-month rate. Three numbers, no asterisks. Vendors that route a per-seat subscription to "contact sales" are telling you the renewal will be a negotiation.

We publish the whole ladder: Assist from $79 per clinician per month on annual billing, Copilot at $119 (it adds a bundled AI EHR), Autopilot at $199. The tiers gate features, so you pay up only when you want the record system or the automation. The full table is on our [pricing page](../../pricing/). Compare cost per visit, not the sticker: $79 across 400 visits a month is about $0.20 a visit. For the head-to-head across the self-serve field, our [best AI medical scribes roundup](../best-ai-medical-scribes/) lays out the honest comparison.

## Question 8: what's the honest failure mode?

Every scribe has one. The vendor who admits it is more trustworthy than the one who claims perfection. Two failure modes are worth probing.

First, noisy, multi-speaker rooms. A quiet consult room is the easy case. A crowded clinic with a relative answering half the questions, or a pediatric visit with a caregiver in the room, is the real test, and quality varies sharply across products. If your setting is loud or multi-party, make the demo run on a recording that sounds like your room.

Second, the drafts themselves. Models mishear drug names. They compress two complaints into one. Now and then they write something plausible that didn't happen. That's why review-and-sign is load-bearing, why the clinician stays the safety check on every draft, and why you should distrust any pitch that implies you can skip reading the note.

## Question 9: can you trial it on your own visits?

The trial is the decision. A scripted demo flatters every scribe equally; your Tuesday clinic doesn't. Run a 7-day trial on a normal day, with your patient mix, your languages, your interruptions. Grade three real notes against what you'd have written. If the tool survives your worst visit of the week, it'll survive the rest.

We offer an assisted 7-day trial that begins after workspace setup. The structured way to run one, with a baseline day and a note-grading rubric, is in our [how to run a trial guide](../ai-scribe-trial-how-to-run/). And if you're about to roll a tool out across a small clinic, the [2-week implementation plan](../ai-scribe-implementation-small-clinic/) turns the trial into a rollout.

## Turn the scorecard into a demo agenda

Don't watch nine demos and try to remember the differences. Bring these nine questions to each one, write the answers in a row, and compare. The vendor with the most 2s, especially on audio, Rx safety, coding honesty, and export, is the one to trial.

When you're ready to see how AI Medical Scribe by Patient Square answers all nine against your own visit type, book a demo. Then run the 7-day trial on a real clinic week. The scorecard tells you what to ask; the trial tells you what's true.

---

## How to Run an AI Medical Scribe Trial That Tells You Something
https://patientsquare.com/us/blog/ai-scribe-trial-how-to-run/
Published 2026-06-04 · Tags: ai-scribe, trial, evaluation

A structured 7-day AI scribe trial protocol: a baseline day, a parallel-run day, and a note-grading rubric so the week actually decides the purchase.

Seven days of real clinic is enough if you structure it. Day one is a baseline with your usual documentation. The middle days run the scribe on real visits. One day you run both methods in parallel on a few visits to compare directly. By day seven you have graded notes, not impressions.

Most AI scribe trials prove nothing because nobody structures them. You install the tool, use it casually for a week, decide it "seems fine," and buy on a feeling. A trial that actually tells you something has three parts: a baseline day to measure what you do now, a parallel-run day where you document a few visits both ways, and a fixed rubric you score every note against. Do that and the week decides the purchase, not a sales call.

Here's the protocol, day by day, with the rubric you'll use.

> **Key takeaways**
>
> - A structured 7-day trial has three load-bearing pieces: a baseline day, a parallel-run day, and a 5-point note-grading rubric.
> - The parallel-run day is the most informative hour of the week. Document a few visits both ways and compare them line by line.
> - Grade notes on accuracy, completeness, structure, edit time, and invented content. Invented findings are the one dealbreaker no time savings offsets.
> - Run trials in sequence, not in parallel, when comparing tools, so your scoring stays clean.

## Why most AI scribe trials fail to decide anything

The default trial is unstructured. You turn the scribe on, use it when you remember, skim a few notes, and form a vibe. That vibe is shaped by the easy visits, the ones a scribe was always going to handle, and it misses the hard ones that actually distinguish tools. You end up buying on novelty.

The fix is to treat the week like a small study. Decide in advance what you'll measure, capture a baseline before the tool changes your behavior, and score notes against the same rubric every time. It takes maybe 30 extra minutes across the week. It's the difference between "seems fine" and "I graded eleven real notes and nine were sign-ready."

If you want the broader set of questions to ask alongside the trial, our [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) is the companion to this protocol. Before you start, you can book a demo to confirm the tool fits your visit type, so the trial week isn't your first look.

## Day 1: the baseline day

Before the scribe changes anything, measure your normal. Pick a typical clinic day, document the way you do now, and write down three things.

First, minutes per note, roughly how long each one takes you start to sign. A 2025 UCLA randomized trial found one ambient tool cut average note time by about 41 seconds per note, and you can only see a gain like that against a number you actually measured. Second, when the notes get finished, same day or in bed at 9pm. The AMA found primary-care physicians log a median of 36 minutes of EHR time per 30-minute visit, so "when" matters as much as "how long." Third, your edit instinct: jot the couple of visits where you'd have loved the help, the talkative patient, the multi-complaint visit, the one that ran in two languages.

You're not grading the scribe yet. You're recording the before, so the after means something.

## Days 2 to 4: run it on real visits

Turn the scribe on and use it on every visit you're comfortable with. Don't cherry-pick the easy ones. The whole point is to surface the failure modes.

Push the hard audio first: a noisy waiting room bleeding into the exam room, a soft-spoken patient, a relative answering half the questions. If your real clinic is loud, your trial should be loud too. Run your languages early. If your patients move between languages mid-sentence, those are the visits to test, and the thing to watch is whether the note comes back in clean clinical English. Input can be multilingual; the output note should be English, every time. Then the downstream drafts. If the tool drafts ICD-10 suggestions or a prescription, check them on real cases. Treat the Rx draft as a starting point you have to screen yourself: right drug, right dose, and any interaction or dosing concern for this patient. A good draft mirrors what you actually said in the visit; a careless one drifts from it.

Keep a running tally: how many notes came back sign-ready with light edits versus how many needed real rework. That ratio is most of your answer.

## Day 5: the parallel-run day

This is the hour that decides it. Pick five or six visits and document each one twice. Let the scribe draft its note. Separately, jot what you would have written yourself. Then put them side by side.

You're looking for three things. What did the draft catch that you'd have missed or rushed, often a fuller history than you'd type at clinic pace? What would you have included that the draft dropped, the clinically load-bearing detail it compressed away? And, most important of all, is there anything in the draft that didn't actually happen, an exam finding you didn't perform or a symptom nobody mentioned? That last one is the column that decides it.

By the end of the parallel-run day you know exactly where the tool helps and where you'll keep editing. No demo gives you that. Only your own visits do.

## Days 6 to 7: grade with a fixed rubric

Pull eight to twelve real notes from the week and score each one the same way. Use this rubric, zero to three per row:

| Criterion | What you're scoring | 3 = | 0 = |
|---|---|---|---|
| Factual accuracy | Does the note match what happened? | Every detail correct | Wrong meds, wrong findings |
| Completeness | Is the clinically important content there? | Nothing load-bearing missing | Key history dropped |
| Structure | Is it a clean, usable SOAP note? | Sign-ready format | Needs restructuring |
| Edit time | How long to make it signable? | Under a minute | A full rewrite |
| Invented content | Did it add anything that didn't happen? | Nothing invented | Fabricated a finding |

Add up the scores. A tool that consistently scores high on accuracy and invented-content, even if structure and edit-time are merely good, is a tool you can trust. A tool that's fast and tidy but occasionally invents a finding is not, however clean the demo looked. Weight the safety rows hardest.

For the broader evidence on what ambient scribes do and don't deliver, the [9-question scorecard](../how-to-evaluate-ai-medical-scribe/) puts your trial results in context against pricing and privacy.

## What a passing trial looks like

You don't need perfection. You need a clear, graded picture. A passing week usually looks like this: most notes sign-ready with light edits, the hard-audio and multilingual visits handled better than you feared, the Rx and code suggestions useful and checkable, and zero invented findings across the week. If the audio-retention answer stayed consistent and export was self-serve, you've cleared the structural questions too.

If the tool passes, the natural next step is rolling it out without disrupting the clinic, which our [2-week small-clinic implementation plan](../ai-scribe-implementation-small-clinic/) covers, from consent scripting to staff buy-in.

We offer an assisted 7-day trial that begins after workspace setup, so you can run this exact protocol on the AI Medical Scribe by Patient Square. The scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Book a demo first if you want to see the note quality against your visit type, then run the week. The trial, graded honestly, is the only evaluation that survives contact with a real Tuesday.

---

## 7 Myths About AI Medical Scribes, Checked Against Reality
https://patientsquare.com/us/blog/ai-scribe-myths-debunked/
Published 2026-06-03 · Tags: ai-scribe, myths, education

Seven myths about AI medical scribes, checked against 2026 evidence: do they replace doctors, store recordings, code your bills, or need a perfect signal?

No. An AI scribe drafts the note; the clinician reviews, edits, and signs it. Nothing is filed, coded, or prescribed without a human. It removes the typing, not the judgment. The signing clinician stays the author of the record and carries the documentation responsibility, exactly as before.

The fastest way to misjudge an AI medical scribe is to believe one of the seven myths that follow it around. That it replaces the doctor. That it secretly records everyone, codes your bills, needs a silent room. None of that survives contact with the 2026 evidence. So here's each myth, what's actually true, and where to read the longer version. If you're weighing a scribe and want the objections handled before a sales call, this is the page for it.

> **Key takeaways**
>
> - AI scribes draft notes; clinicians still review, edit, and sign. They remove typing, not judgment.
> - Audio retention varies by vendor. Some store recordings for days or weeks; others, including us, never store them at all.
> - A scribe should suggest ICD-10 codes, not code or bill your notes. Tools claiming to be coding engines are overclaiming.
> - No responsible vendor publishes a single accuracy percentage, because there's no standard benchmark to measure against.

## The 7 myths, at a glance

| Myth | The 2026 reality |
|---|---|
| 1. AI scribes replace doctors | They draft; you review and sign. Judgment stays human. |
| 2. They secretly record and store everyone | Retention varies; the cleanest tools store no audio at all. |
| 3. They code and bill your notes | A responsible scribe suggests ICD-10; a person confirms. |
| 4. They need a silent room and clear English | Good ones handle noise, accents, and multiple languages. |
| 5. They're only for big health systems | Self-serve tools are built for solo and small practices. |
| 6. They're accurate enough to skip reading | Accurate to draft, not to trust unread. Always sign. |
| 7. A free EHR-bundled scribe is always enough | Sometimes; often it's note-only, missing Rx and languages. |

The rest of this page takes each one apart.

## Myth 1: an AI scribe replaces the doctor

It replaces the typing, not the clinician. An AI scribe drafts the note. You read it, fix what's wrong, and sign. Nothing enters the record, gets coded, or becomes a prescription without you. The signing clinician stays the author and carries the documentation responsibility, exactly as before the scribe existed.

This matters legally, not just rhetorically. No scribe, silicon or human, moves the record off the signing clinician. A tool that implies you can stop reading the note is selling something dangerous.

## Myth 2: AI scribes secretly record and store every visit

Retention varies widely, and "secretly" is the part to attack. Some vendors retain audio for days or weeks. Some let you opt out. The cleanest answer is no retention at all.

This isn't abstract. A proposed class action filed against Sharp HealthCare in late 2025 alleges patients were recorded by an ambient AI tool without consent, with more than 100,000 patients potentially affected. The lesson is twofold: tell patients clearly, and prefer a tool that doesn't keep the audio. Ours is processed in memory and discarded the moment the note is drafted, so there's no archive to leak or subpoena. The consent mechanics, state by state, are in our [patient consent guide](../ai-scribe-patient-consent-by-state/), and the behavioral-health version, where the stakes are highest, is in our [psychiatry privacy guide](../ai-scribe-for-psychiatry-privacy/).

## Myth 3: an AI scribe codes and bills your notes

A responsible scribe suggests ICD-10 codes. It doesn't code or bill, and that distinction is the whole ballgame. Coding is a human-confirmed decision with clinical and financial weight. A tool that claims to be an automated coding engine, an E&M leveler, or a billing system is claiming a job it shouldn't have.

We offer ICD-10 suggestions to speed your coding. A coder or clinician confirms them. That's it. We don't ship CPT, E&M, or HCC automation. The honest version of this distinction, what a scribe may suggest versus what a coder must still confirm, is the entire point of our [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/).

## Myth 4: AI scribes need a silent room and clear English

Good ambient scribes handle real rooms, though quality varies by tool. Two speakers, interruptions, accents, the way real consultations loop back on themselves. The genuinely hard case is a busy clinic where a relative answers half the questions, a patient with a strong accent, a noisy hallway leaking through the door.

That's exactly where products diverge, so it's the case to test. AI Medical Scribe by Patient Square handles English plus more languages on the input side, and the note always comes back in clean clinical English. In low-signal clinics, capture works offline with on-device encryption. The myth is that you need a quiet, perfectly enunciated consult; the test is your actual one.

## Myth 5: AI scribes are only for large health systems

Enterprise tools exist, sure. But practice-sized products are built for small clinics. A solo doctor or a small clinic can evaluate a scribe with published pricing and a scoped trial without an enterprise integration team. Often the small practice gets more value, because it has no IT staff to absorb the documentation load and the most evenings to win back.

A 2025 UCLA randomized trial measured about 41 seconds saved per note for one ambient tool, which at 20 patients is roughly 14 minutes a day. For a solo doctor finishing notes at 9pm, that's the difference the myth obscures.

## Myth 6: it's accurate enough to skip reading the note

Accurate enough to draft, never accurate enough to trust unread. Models mishear drug names, compress two complaints into one, occasionally write something plausible that didn't happen. The review-and-sign step is load-bearing precisely because of this.

And notice what no honest vendor does: publish a single accuracy percentage. There's no standard benchmark for medical-note accuracy, so a number is marketing, not measurement. The better question is what to test instead, which our [accuracy explainer](../ai-scribe-accuracy-what-to-expect/) answers. Distrust any pitch built on a clean-looking percentage.

## Myth 7: a free EHR-bundled scribe is always enough

Sometimes, and often not. Free ambient scribes are arriving inside EHRs; athenahealth announced athenaAmbient, free for athenaOne users, in 2026. If all you need is note generation and you live inside that one EHR, a bundled free tool may be the right call, and we'll say so.

But many bundled scribes do note generation and little else. A standalone usually adds prescription drafting, ICD-10 suggestions, and genuine multilingual capture. The honest move is to evaluate against the work you actually do, not the longest feature list or the lowest price.

## How to stop believing the next myth

The pattern across all seven: the myth is a generalization, the truth is "it depends on the vendor, so test it." That's the habit worth keeping. Ask every tool what it does with the audio, what it drafts, what it claims to code, and which languages it really handles, then trial it on your own visits.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. If these myths were the reason you'd held off, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and check the published scope against your own clinic using the [product page](/us/products/practice-copilot/).

---

## Rolling Out an AI Medical Scribe in a Small Clinic: A 2-Week Plan
https://patientsquare.com/us/blog/ai-scribe-implementation-small-clinic/
Published 2026-06-02 · Tags: ai-scribe, implementation, rollout

A day-by-day 14-day rollout plan for an AI scribe in a sub-10-clinician practice: consent scripting, baseline, staff buy-in, and note-grading.

Two weeks is realistic for a practice under ten clinicians. Week one is one clinician proving the workflow and the consent script. Week two brings the rest of the team on with a shared note-grading standard. Most small clinics are fully switched over inside 14 working days without losing a clinic day.

A small clinic doesn't need a six-month implementation project to adopt an AI scribe. It needs two weeks, one willing clinician to start, a consent script, and a way to grade the notes. Week one proves the workflow with a single doctor. Week two brings the rest of the team on with a shared standard. For a practice under ten clinicians, that's enough to switch over completely without losing a clinic day. Here's the plan, day by day.

> **Key takeaways**
>
> - A sub-10-clinician practice can fully adopt an AI scribe in 14 working days, no IT project, no EHR-integration build.
> - Week one is one clinician proving the workflow and the consent script. Week two scales the team with a shared note-grading standard.
> - A plain one-sentence consent script matters most in all-party-consent US states; a tool that never stores audio shrinks the exposure regardless.
> - Measure a baseline day against a week-two day: minutes per note, when notes finish, how many come back sign-ready.

## Why a small clinic can skip the big-bang rollout

Enterprise scribe deployments are projects: EHR integration, procurement, change-management committees, months of timeline. A small practice has none of that overhead and shouldn't borrow it. A self-serve scribe runs on a phone or laptop, there's nothing to wire into your records system, and you copy the finished note into the chart. The work that remains is workflow and consent, not infrastructure.

That's why a phased two-week ramp beats a top-down switch. You de-risk by letting one clinician prove it, you build buy-in by showing graded results instead of mandating adoption, and you keep the clinic running the whole time. If you want the upstream evaluation that comes before rollout, our [9-question scorecard](../how-to-evaluate-ai-medical-scribe/) is how you pick the tool in the first place.

## Week 1: prove it with one clinician

The first week has one job: confirm the scribe works in your real clinic, run by one person, before you ask anyone else to change their day.

Day 1 is the baseline. Pick your most willing clinician and have them document a normal day the usual way. Record minutes per note, when notes get finished, and the visits they'd most want help with. This is the before. A 2025 UCLA randomized trial measured about 41 seconds saved per note for one ambient tool, and you can only see a gain like that against a baseline you captured.

Day 2, the consent script. Write the one sentence the clinician (or front desk) says at the start of the visit: that the conversation is being captured to help draft the note, and the patient can decline. This matters most in the 11 US all-party-consent states. A proposed class action against Sharp HealthCare in late 2025 alleges patients were recorded by an ambient tool without consent. The cleanest protection is a clear script plus a tool that doesn't retain the audio at all.

Days 3 to 4, run real visits. The willing clinician uses the scribe on every visit they're comfortable with, including the hard ones: noisy rooms, multilingual visits, multi-complaint patients. No cherry-picking.

Day 5, grade and decide whether to scale. Pull eight or so notes and score them on accuracy, completeness, structure, edit time, and whether anything was invented. If the notes are sign-ready and nothing's fabricated, you're cleared to bring the team on. The structured version of this is our [trial protocol](../ai-scribe-trial-how-to-run/), which is worth running in full during week one.

## Week 2: bring the team on with a shared standard

Week two scales what one clinician proved. The risk here isn't the tool, it's inconsistency, so you give everyone the same starting point.

Day 6 is the team kickoff. A 20-minute session. The week-one clinician shows their graded notes and their evening that didn't happen. Hand out the consent script and the grading rubric. Don't oversell; let the numbers do it.

Days 7 to 9, staggered onboarding. Add clinicians in twos, not all at once, so questions get answered fast. Each new clinician runs their own short baseline first, then starts using the scribe live. Pair each one with the week-one clinician for the first day.

Day 10, handle the holdouts. Every clinic has a skeptic. Resistance usually drops once they see their own charting load fall, not before, so don't argue, demo. Let them run it for two days and grade their own notes. The AMA found primary-care physicians log a median of 36 minutes of EHR time per 30-minute visit, and most holdouts convert when that number moves for them personally.

Days 11 to 13, full clinic at real load. Everyone's on. Keep the grading going lightly so quality issues surface while they're cheap to fix. Watch the multilingual and high-volume visits, which are where ambient tools differ most.

Day 14, measure against baseline. Compare a week-two day to your day-one baseline: minutes per note, when notes finish, sign-ready rate. If notes are finishing during clinic instead of at night, the rollout worked.

## A 2-week rollout calendar

| Day | Focus | Output |
|---|---|---|
| 1 | Baseline (1 clinician) | Minutes/note, finish-time, pain visits |
| 2 | Consent script | One-sentence script, state-checked |
| 3–4 | Real visits (1 clinician) | Hard-audio and multilingual cases run |
| 5 | Grade and gate | Go/no-go on scaling to the team |
| 6 | Team kickoff | Script + rubric distributed |
| 7–9 | Staggered onboarding | Clinicians added in pairs |
| 10 | Holdout conversion | Skeptics run their own graded trial |
| 11–13 | Full clinic | Quality watched at real load |
| 14 | Measure vs baseline | Did notes move off the evening? |

## What can derail a rollout, and how to avoid it

Three things sink small-clinic rollouts, all of them avoidable.

Skipping the baseline is the first. Without a before, you can't prove the after, and adoption stalls on "does this even help?" Spend the 20 minutes on day one.

Mandating on day one is the second. Top-down switches breed quiet resistance. The one-clinician-first ramp converts skeptics with evidence instead of authority.

And the third: no consent plan. Rolling out before you've settled how patients are told is a compliance gap, especially in all-party-consent US states. Settle the script on day two, not day twenty.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit, which is what makes a two-week rollout realistic rather than optimistic. When you're ready to plan your clinic's two weeks, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and review the [product workflow](/us/products/practice-copilot/) before planning week one. The plan is simple on purpose; small clinics don't have spare weeks to give a complicated one.

---

## AI Medical Scribe for Primary Care: The 20-Patient-Day Test
https://patientsquare.com/us/blog/ai-scribe-for-primary-care/
Published 2026-06-01 · Updated 2026-07-22 · Tags: ai-scribe, primary-care, time-savings

A 20-patient-day time-back model for primary care, built from verified per-note figures, plus the visit types where a scribe earns its keep.

A 2025 UCLA randomized trial measured about 41 fewer seconds per note for one ambient tool. At 20 patients a day that is roughly 14 minutes back daily, or about 4.6 hours a month. The bigger effect for many doctors is when the notes finish: during clinic, not at 9pm.

Test this on a real primary-care day, not a spec sheet. A 2025 UCLA randomized trial found one ambient scribe cut average note time by about 41 seconds per note. Multiply by a 20-patient day and you get roughly 14 minutes back daily, about 4.6 hours a month. That number is the cautious one. What actually changes a day is when the notes finish, during clinic instead of after dinner. Below is the day-in-the-life math, and what it takes for the savings to actually show up.

> **Key takeaways**
>
> - A 2025 UCLA trial measured about 41 fewer seconds per note for one ambient tool; at 20 patients that's roughly 14 minutes back daily, near 4.6 hours a month.
> - The bigger win is timing: notes that finish during clinic instead of at 9pm. The AMA found 36 minutes of EHR time per 30-minute visit.
> - The per-note saving is the floor. The visits where a scribe helps most are the long, talkative, multi-complaint ones you'd otherwise rebuild from memory.
> - Against a subscription that starts from $79 a month, recovering a fraction of an hour a day clears the cost long before you count the burnout you didn't have.

## What does a 20-patient primary care day actually cost you in notes?

Twenty patients is a normal primary-care day in a lot of clinics. The visits are short. The documentation isn't. The AMA found primary-care physicians log a median of 36 minutes of EHR time per 30-minute visit, which is why the note now outlasts the appointment it describes. Stack that across twenty visits and a chunk of it lands after hours.

So the honest framing isn't "save hours overnight." It's more like: shave a bit off every note, then push the rest off your evening. A 2025 UCLA randomized trial put the per-note saving at about 41 seconds for one ambient tool, from 4 minutes 30 to 3 minutes 49. Small on any single note. It adds up over a full day. And the per-note number undersells the timing shift, which is that you finish during clinic.

If you want the upstream question of how to pick a tool that delivers this, our [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) is the place to start.

## The 20-patient-day time-back model

Here's the arithmetic, conservatively, using the verified per-note figure.

| | Without an AI scribe | With an ambient AI scribe |
|---|---|---|
| Patients per day | 20 | 20 |
| Avg note time | ~4:30 per note | ~3:49 per note |
| Documentation time per day | ~90 min | ~76 min |
| Time back per day | n/a | ~14 min |
| Time back per month (20 days) | n/a | ~4.6 hours |
| When notes finish | Often after clinic | During clinic |

Fourteen minutes a day doesn't sound dramatic until you put it where it lands: the back of your evening. And remember the per-note figure is the cautious one. The visits where a scribe helps most are the ones you'd otherwise spend the longest reconstructing from memory afterward: the talkative patient, the multi-complaint visit, the one that loops back on itself three times before the real problem surfaces.

## A primary care day: the 6pm versus the 9pm sign-off

Picture a family-medicine doctor on a 20-patient Tuesday. Without a scribe, the visits end at five and the charting doesn't. The notes pile into the evening, and the median 36 minutes of EHR time per visit means a real share of the day's documentation happens at home. That's the pajama time the burnout studies keep measuring.

With an ambient scribe running, each note comes back drafted about two minutes after the visit ends. The doctor reads it, fixes what's off, and signs, between patients or in the gaps. By six, the charts are mostly done. The 14 minutes the model shows is just the floor. What you actually feel is signing in the clinic instead of in bed.

## Where the time-back model gets tested

The model assumes the scribe holds up. That's the part to check before you trust the number. A busy clinic isn't a quiet demo room. People interrupt. A patient buries the real complaint under three smaller ones. A relative answers half the questions. The exam room sits next to a loud waiting area. That's where weaker tools quietly fall apart, and where the per-note saving either holds or evaporates.

So the honest test isn't a scripted consult. It's your busiest, loudest hour, with the patient who's hardest to follow. If the note comes back clean from that, the 14 minutes is real. If it needs heavy cleanup, no average will rescue it.

## Does the subscription pay for itself in primary care?

The arithmetic is short. Take the conservative 14 minutes a day, value it at whatever your hour is worth, and set it against a plan that starts from $79 a month. For almost any primary-care doctor, even a fraction of that recovered time clears the subscription. And that's before the qualitative return the burnout studies measure: fewer evenings spent charting, more eye contact while the patient is actually in front of you.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The full price ladder, with no asterisks, is on our [pricing page](../../pricing/), and the way to roll it out across a small clinic is our [2-week implementation plan](../ai-scribe-implementation-small-clinic/).

The model only gives you the floor. The real number comes from your own 20-patient day. <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> to review the documented note workflow against your visit type, then use the [product page](/us/products/practice-copilot/) to check its published scope.

---

## Do You Need a New EHR or Just Better Documentation?
https://patientsquare.com/us/blog/ai-scribe-vs-new-ehr/
Published 2026-05-29 · Updated 2026-07-22 · Tags: ai-scribe, ehr, documentation

If documentation pain is the main reason you want to switch EHRs, fix it first. Here is how to tell which problem you actually have.

Depends on what is actually broken. If your complaint is that notes take too long to write, a scribe can fix that on your current EHR. If your complaint is about scheduling, billing workflows, lab ordering, or that the EHR itself is missing features your practice needs, a scribe does not help with any of that. Separate the complaints before you act.

If you want to switch EHRs because notes take too long, stop. The problem probably is not your EHR. It is your documentation workflow, and a new system with the same charting habits gives you the same charting problem — after months of disruption, retraining, and five-figure migration costs.

That is not an argument against ever switching EHRs. It is an argument for naming the actual problem before you act on it.

> **Key takeaways**
>
> - Physicians log a median of 36 minutes of EHR time per 30-minute visit, per AMA and JAMA Network Open data. Most of that time is note-writing, not a system flaw.
> - An EHR switch costs tens of thousands of dollars for a small practice and disrupts billing, staff workflow, and patient records for months.
> - An EHR-agnostic AI scribe works alongside whatever system you run — no integration, no migration, no IT ticket.
> - The right test: write down every complaint driving the switch. Anything on that list that is specifically about writing notes is a scribe problem, not an EHR problem.

## Two different problems that feel identical until you name them

Clinicians who are burned out on charting and clinicians who have a bad EHR use almost the same language. "This system is killing me. I need something different." The frustration is real in both cases. But the solutions are completely different.

**Documentation overload** looks like this: the visit is fine, the EHR is not actually broken, but the note takes 20 minutes to write, you are finishing charts at 9pm, and the morning is half gone before you feel caught up. That is a scribe problem.

**An EHR gap** looks like this: the billing module is missing capabilities your specialty needs, a critical lab or referral integration is unavailable, the patient portal does not work the way your front desk needs it to, or your vendor's support has become unreliable. Those are EHR problems. No amount of ambient capture fixes them.

The mistake most practices make is conflating the two. They reach the edge of their patience with charting, and the conclusion becomes "I need a new EHR." That is natural. It is also usually wrong if documentation was the main complaint.

## What a new EHR actually costs

Let's be specific. A small independent practice switching EHRs faces:

- Implementation and setup fees (typically four to five figures for a legitimate system)
- Data migration: moving charts, encounter history, and billing records — often billed per-chart or by the project
- Staff retraining: front desk, billing, clinical — everyone has to learn the new system, and productivity falls for months
- Downtime or parallel-run costs during the transition window
- Interface and workflow rebuilds (lab connections, fax routing, patient portal setup)

Switching cost estimates from healthcare IT analysts, including Black Book Research ambulatory surveys, put total all-in costs for a small practice — direct fees plus productivity loss — in the range of five figures or more, before accounting for the disruption hit on existing staff.

None of that is wrong to spend if you have a genuine EHR gap. But if the problem is documentation speed, you have spent that money and still have the same charting problem. The EHR changed. The note-writing didn't.

## What an EHR-agnostic scribe actually does

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. (Practice Copilot also bundles its own AI EHR at the Copilot tier if you ever want the record system too, but that's a separate decision from the one on this page.)

Run on the scribe alone and it does not write back into your existing EHR. That's the export model, by design, not by omission.

The scribe drafts the note, you export it into your current system — copy and paste, or a structured export — exactly as you would any text. It works alongside Epic, athenahealth, eClinicalWorks, Elation, NextGen, or whatever system your practice runs, including a legacy setup you have had for fifteen years. No API contract with your EHR vendor. No IT project. No waiting for a compatibility checklist.

For more on why the export model works for practices on any EHR, the [EHR-agnostic scribe explainer](../ai-scribe-any-ehr-export/) walks the mechanics. For the comparison between a free embedded EHR scribe and a standalone tool, the [free EHR scribe vs standalone guide](../free-ehr-ai-scribe-vs-standalone/) is the honest version of that decision.

## The complaint list test

Before doing anything, write down every reason you want to switch EHRs. Be specific.

Then go through each one:

| Complaint | What it actually is |
|---|---|
| Notes take too long to finish | Documentation problem — scribe can fix this |
| Charting runs past 7pm every night | Documentation problem — scribe can fix this |
| The ICD-10 coding step is slow | Documentation problem — scribe's ICD-10 suggestions help here |
| Rx writing is slow | Documentation problem — scribe's Rx draft you review and sign helps here |
| The EHR's billing module is missing features we need | EHR problem — scribe does not fix this |
| Lab integrations we rely on are not in this system | EHR problem — scribe does not fix this |
| Scheduling and patient portal are not working for staff | EHR problem — scribe does not fix this |
| Vendor support has become unreliable | EHR problem — scribe does not fix this |
| We need specialty-specific workflows the EHR lacks | EHR problem — scribe does not fix this |

If your list has three documentation complaints and one EHR complaint, try the scribe first. If the list is mostly EHR-structural, the switch might be right — but add an EHR-agnostic scribe to the plan so you are not starting from scratch on documentation in the new system either.

## When the switch is right — and how to still solve documentation independently

There are genuine reasons to switch EHRs. Multi-location practices outgrowing a solo-practice system. A specialty-specific capability gap that is well-documented and reproducible. A billing or compliance issue the vendor cannot resolve. If those are your complaints, a switch may be the right call.

An EHR-agnostic scribe belongs in your new workflow regardless. The documentation pain does not disappear when you switch — it follows you until you change how notes get written. Building the scribe layer into the new setup from day one means you do not go through six months of onboarding only to discover you still have a charting problem.

For the side-by-side on what a standalone scribe does that Epic's built-in charting tool does not, the [AI scribe vs Epic AI charting comparison](../ai-scribe-vs-epic-ai-charting/) runs through the specific gaps and when the built-in option is genuinely enough.

## What the scribe does not fix — be honest about this

We think the EHR-agnostic positioning is genuinely useful. We also think clarity matters more than a sale.

An AI scribe will not fix your billing workflow. It will not add a lab integration your current EHR is missing. It will not make your patient portal better. It will not solve a vendor support problem.

What it fixes is the time cost of writing structured clinical notes — the 36-minute median for a 30-minute visit, the evening charting sessions, the SOAP note backlog on a busy Tuesday. That is the specific problem it is built for, and it works on whatever EHR you already run.

If documentation is on your complaint list, fix that first. A 7-day trial on a real clinic week — your patient mix, your interruptions, no scripted demo — tells you whether that specific problem is solved before you spend anything.

If documentation is NOT on your complaint list, or if it is genuinely secondary to structural EHR gaps, the scribe is not the lever to pull. The switch might be.

Most of the time, for most practices running through this decision, documentation is the main complaint. And fixing that is a lot cheaper than a migration.

## The sequence that saves most practices the disruption

If you are genuinely weighing an EHR switch, try this order:

1. Run the complaint list test above. Separate documentation items from EHR structural items.
2. If documentation is among the top complaints, trial an EHR-agnostic scribe for one clinic week. One week of real visits tells you more than any demo.
3. If the scribe resolves the documentation pain, revisit the switch decision. It may no longer be urgent.
4. If the scribe helps and you still have genuine EHR structural gaps, plan the switch — but build the scribe layer into the new system from the start so you do not solve one problem and create another.

The goal is not to avoid switching EHRs forever. The goal is to not spend the switching cost on a problem the scribe would have solved from $79 a month (the annual Assist plan) on your current system.

When you're ready to see how the AI Medical Scribe by Patient Square works alongside your current EHR, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and review the [product workflow](/us/products/practice-copilot/) before planning an evaluation. Check integration requirements with your EHR vendor.

---

## EkaScribe Alternatives in India: An Honest Look (2026)
https://patientsquare.com/in/blog/ekascribe-alternatives-india/
Published 2026-05-29 · Updated 2026-07-22 · Tags: ekascribe, alternatives, india, comparison

A clinician-built comparison of EkaScribe alternatives in India, including the one thing EkaScribe does that we do not yet: live ABDM integration.

EkaScribe is an India-native ambient scribe with live ABDM integration and a published scribe-only price. Patient Square's AI Medical Scribe starts in the Assist plan and adds a bundled AI EHR in Copilot. Choose EkaScribe when live ABDM linking is essential; evaluate Patient Square when the broader practice bundle, prescription draft, and audio handling better fit your workflow.

Looking at EkaScribe and wondering what else is out there? Here's the honest version. EkaScribe is a strong, India-native AI scribe, and it does one thing we don't yet: live ABDM integration. So we'll lead with that concession, then show you where AI Medical Scribe by Patient Square is the better pick. No vendor is best at everything. Better you know the real trade-off before a trial than after.

> **Key takeaways**
>
> - EkaScribe has live ABDM integration (M1, M2, M3 certified). We don't. ABDM is on our roadmap, not shipping. If ABHA linking inside your scribe is non-negotiable today, that's a real reason to pick eka.care.
> - EkaScribe Pro is ₹1,499/month scribe-only; our entry Assist plan is ₹1,599/month ex-GST (about ₹1,887 with 18% GST) on annual billing, and the Copilot plan at ₹2,399 bundles the scribe with an AI EHR. Add an EMR to EkaScribe and the eka stack is ₹2,600–3,000/month, above our bundled Copilot tier.
> - Where we pull ahead: a prescription draft you review and sign, audio that's never stored, and notes always in clean clinical English from a Hinglish consult. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - Practo Ray and HealthPlix are EMRs with documentation features, not standalone scribes. Frame them that way when you compare.

## What does EkaScribe do well, honestly?

Credit where it's earned. That's the whole point of an honest comparison.

EkaScribe is built by eka.care, an India-native health platform. It was positioned as India's first AI medical scribe, runs on the company's own language model, and handles 20-plus Indian languages. Its published price is ₹1,499 per doctor per month for the scribe alone, with an annual plan near ₹12,492 a year and a free tier that allows five consultations a day. The EMR is a separate eka plan, so a clinic that needs both is buying two products. Still, that's a clear, India-denominated rate card, which already puts it ahead of the global vendors who quote you in dollars or route you to a sales call.

The biggest single thing EkaScribe has that we don't is live ABDM integration. eka.care has M1, M2, and M3 milestones certified by the National Health Authority, an ABDM Connect API, and a health locker for ABHA-linked records. If your clinic's workflow depends on creating or linking ABHA IDs and pushing records into the national health stack today, EkaScribe does that now. AI Medical Scribe by Patient Square does not. ABDM integration is on our roadmap. We're not going to pretend otherwise, and any comparison that buries this is lying to you.

So if you've read this far and ABDM-today is the deciding factor, you can stop here and choose eka.care with our blessing. For everyone else, here's where we're the stronger pick.

## EkaScribe vs the alternatives: the India scribe table

| | EkaScribe (eka.care) | AI Medical Scribe by Patient Square | Augnito | Practo Ray / HealthPlix |
|---|---|---|---|---|
| **Product type** | Ambient scribe inside a health platform | Focused ambient scribe | Dictation + voice commands (Spectra); ambient (Omni) | EMR with documentation features |
| **Published India price** | ₹1,499/mo (Pro, scribe-only); ~₹12,492/yr annual; EMR sold separately | Assist ₹1,599/mo ex-GST annual (~₹1,887 with GST); Copilot ₹2,399 bundles an AI EHR | Sales-led, no transparent self-serve ₹ rate | EMR subscription, not a scribe price |
| **Live ABDM integration** | Yes (M1–M3 certified) | Roadmap, not shipping | Not the product focus | Varies by platform |
| **Prescription handling** | Voice-to-prescription | Rx draft you review and sign | Dictation-led | EMR Rx module |
| **Visit audio** | Per their policy | Live consultation audio is processed in memory and discarded at note draft; uploads use a separate retention mode with explicit consent | Per their policy | Per their policy |
| **Note output language** | English / structured | Clean clinical English | English | English |
| **Free trial** | Free tier: 5 consults/day | 7-day full trial, no daily cap | 7-day trial | Demo-led |

A note on that last column. Practo Ray and HealthPlix come up constantly when doctors search for scribe alternatives, but they're EMR products with documentation features bolted on, not standalone ambient scribes. If you want a full practice-management EMR, look at them. If you want a tool that listens during the visit and hands back a note, they're not really in this comparison, and lumping them in would mislead you.

## Where is AI Medical Scribe by Patient Square the better pick?

Three places, and they're concrete.

Start with the prescription draft. AI Medical Scribe by Patient Square is an ambient AI medical scribe that builds a live transcript as you speak and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft the moment the visit ends, ready to review and sign. The draft reflects what was said in the visit. It isn't screened, dosed, or checked for interactions by any engine on our side, and it never goes to a pharmacy on its own. You are the safety check, exactly as you are today: you read the draft, adjust it, and sign it. A draft an LLM wrote is still a draft an LLM wrote, which is why review-and-sign is the whole point.

Then there's the audio, or rather the lack of it. Visit audio is processed in memory and discarded the moment the note is drafted. No audio archive, for us or for the practice. Under the DPDP Act 2023, the less sensitive data you retain, the smaller your exposure, and a recording is more revealing than the note. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

And the pricing is honest, with no daily cap. The entry Assist plan is ₹1,599 per clinician per month ex-GST on annual billing, about ₹1,887 once you add 18% GST. Move up to the Copilot plan at ₹2,399 and the same price carries the scribe plus a bundled AI EHR and WhatsApp messaging, rather than billing the EMR separately the way the eka stack does. There's a 7-day free trial, the real product, no five-consultations-a-day ceiling while you evaluate. The complete ladder, with the with-GST math, is on the [India rate card](../ai-medical-scribe-price-india/) and the [pricing page](../../pricing/).

If those three things matter more to you than ABDM-today, and you'd rather buy scribe and practice tools as one bundle than stitch two products together, we're the switch worth trialing. If you only want a standalone scribe and already run an EMR, EkaScribe's lower scribe-only price is the honest call.

## How do you actually choose between them?

Run both. Seriously. This is a clinical tool, and a feature list can't tell you whether the note from your Tuesday OPD is signable.

Pick a real clinic morning. Use EkaScribe's free tier for part of it and our 7-day trial for the rest, on the same kinds of patients, your accents, your Hinglish, your interruptions. Then read the notes side by side and ask three questions: Is the SOAP note clean enough to sign without a rewrite? Did the prescription draft catch anything risky? Where did the visit audio go, and can each vendor tell you in one sentence? The India scribe market is small enough that a parallel run takes a week, and the answer you get is worth more than any table, including this one.

When you're ready to see ours on your own consults, book a demo and we'll walk through it on the kind of cases you actually see. If you'd rather start with numbers, the [India comparison](../india-ai-scribe-comparison/) lines us up against EkaScribe and Augnito, and the [Hindi and Hinglish post](../ai-scribe-hindi-indian-languages/) shows a real code-mixed consult turning into an English note.

## When is EkaScribe the better fit?

Plainly: when live ABDM integration is a today requirement, not a someday one. If your clinic is building around ABHA linking, the national health stack, or AB-PMJAY workflows that depend on ABDM connectivity, eka.care has shipped that and we haven't. That's the cleanest reason to choose EkaScribe over us, and it's an honest one. It's also a roadmap item for us, so this gap is one we intend to close, but you should buy what ships, not what's promised.

For prescription safety, audio that's never stored, transparent uncapped pricing from ₹1,599 for the scribe (with an AI EHR bundled at the ₹2,399 Copilot tier), and a clean English note from a Hinglish visit, we think we're the better daily driver. The only way to know for your clinic is to run both for a week. Book a demo and put us on a real OPD morning. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

---

## AI Medical Scribe for Urgent Care: MDM-Complexity Documentation
https://patientsquare.com/us/blog/ai-scribe-for-urgent-care/
Published 2026-05-28 · Updated 2026-07-22 · Tags: ai-scribe, urgent-care, mdm, specialty

How an AI scribe handles urgent care MDM complexity under the 2023 CMS E&M rules — from walk-in acuity triage to fast dispo. Trial it on a real shift.

Yes. Urgent care spans low-MDM (minor laceration, URI) to moderate-MDM (chest pain risk-stratification, exacerbation of a chronic illness) within the same shift. An ambient AI scribe captures the full visit conversation and builds a SOAP note that reflects the decision-making documented — but the physician still reviews and signs every note. The tool does not auto-assign E&M codes.

Urgent care is the specialty where MDM complexity is hardest to capture quickly. You see a sprained ankle and a chest pain work-up in the same hour, at 4-5 patients per hour, with a disposition clock running the whole time. The 2023 CMS E&M guidelines made medical-decision-making the primary code selector. Good news for clinicians who think carefully. The catch: the quality of your MDM documentation now carries all the weight that history and physical exam used to.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

> **Key takeaways**
>
> - Urgent care uses office/outpatient E&M codes 99202-99215, determined since 2023 by medical decision making or total time, not by history and physical exam documentation.
> - MDM has three elements (problem complexity, data reviewed, risk); you need two of three to meet a level. Capturing that reasoning is where documentation gaps happen.
> - A 2025 Annals of Emergency Medicine study found ambient AI scribes cut on-shift documentation time by about 28% in an ED setting (2:45 vs 3:50 per encounter), the closest published analog to urgent care throughput.
> - At a 4-5 patient/hour UC pace, even 1 minute saved per encounter adds up to 4-5 minutes per hour back in your shift.

## What actually changed about urgent care E&M in 2023

The shift started in 2021 and was clarified for 2023: urgent care centers now use office and other outpatient E&M codes 99202 through 99215, with code selection driven by MDM or total time, not by whether you documented a 10-point review of systems or a full organ-system physical exam. History and exam still happen. You still document them. But they no longer determine the code.

That sounds like a documentation simplification. It is, partially. But it moved the load: now the three MDM elements carry all the weight. If your note reflects sound clinical reasoning, you code correctly. If the note is thin on reasoning, even if your actual decision-making was thorough, you are at risk for downcoding on audit.

The three MDM elements, under the current framework:

1. **Number and complexity of problems addressed.** "Acute" means recent or short-term, not necessarily new. A return visit for an ankle you splinted last week is still an acute problem. Self-limited problems (common cold, minor bruise) are the bottom tier.
2. **Amount and complexity of data reviewed.** Ordering or reviewing each unique test counts. Discussing a case with an external provider (not your own group) counts. An independent historian counts. A translator does not.
3. **Risk of complications, morbidity, or mortality.** This is about treatment risk, not inherent patient risk. Gastroenteritis treated with OTC recommendations is low risk. Social factors like homelessness or food insecurity now count toward moderate risk under the 2023 rules. The decision to forgo a test or treatment also earns MDM credit, if you document the reasoning.

To bill a given level, two of those three elements must meet that level's threshold.

## The acuity range problem in urgent care

Primary care deals with familiar patients and mostly chronic disease. The ED deals with higher average acuity and has more clinical support. Urgent care sits between them and sees the full spread: a 9-year-old with an ear infection at 9am, then a 58-year-old with hypertensive urgency at 10am, then a worker with a hand laceration at 10:15am.

That range is not a documentation problem when you have time. At 4-5 patients an hour, it is. The ear infection is a 10-minute encounter that codes moderate MDM if there is a prior antibiotic failure to work through, but you have to document the reasoning. The hypertensive urgency may code high MDM, but the note has to capture the risk discussion and the disposition logic. Type between patients or dictate in the hallway and those elements get thin.

A 2025 study in Annals of Emergency Medicine tracked 8,740 eligible encounters at an academic ED after ambient AI scribe deployment. On-shift documentation time dropped from 3:50 per encounter to 2:45, a 28% reduction. Total EHR time per encounter dropped 16% (10:21 to 8:39). This is the closest published evidence to a UC setting; no randomized trial has run exclusively in urgent care yet. The direction is consistent with other ambulatory studies, including a multi-site study of 1,800 clinicians that found scribe adopters saved 16 minutes of documentation time per 8-hour care block.

A 2026 STAT analysis comparing AI scribes to human scribes found AI saved about 1.6 minutes per patient in an ED context, versus 3.3 minutes for a human scribe. The AI tool costs a fraction of a human scribe's cost.

## What the MDM-to-documentation gap looks like in practice

Here is a typical urgent care scenario where the gap shows up. A 45-year-old comes in with right-sided chest pain, onset two hours ago. You take the history, do an ECG, review troponin, calculate a HEART score, and decide the probability is low enough to discharge with return precautions and next-day cardiology referral. That decision involves at least moderate MDM: acute problem with chronic illness interaction, data reviewed, moderate risk from the decision not to admit.

Without good contemporaneous documentation, the note might say: "Chest pain, 45yo, ECG unremarkable, troponin negative, discharged with follow-up." That reads like a low-MDM encounter on audit. The reasoning that justified moderate coding, the HEART score rationale, the explicit decision to forgo admission, the social history that factored in, is not there.

An ambient scribe running during that encounter captures the conversation: the HEART score discussion, the troponin-negative interpretation, the disposition reasoning you said out loud while wrapping up. The draft note includes it. You review and sign. The MDM documentation reflects the actual complexity of the visit.

A 2025 study comparing ED billing code distributions before and after the 2023 E&M guideline changes found Level 4 visits increased by about 7 percentage points and Level 3 visits dropped by about 8 percentage points across five hospitals. Community hospitals showed the strongest shift. Part of this reflects the guideline change reducing documentation requirements for higher codes. Part of it reflects clinicians now documenting reasoning more clearly rather than defaulting to conservative coding.

## The dispo clock and the note

Urgent care throughput runs on dispo speed. That means 12-15 minutes per encounter from door to dispo, which is not a lot of room to take a history, do an exam, order and review tests, and make a disposition call. The note has to happen somewhere.

Most urgent care physicians do one of three things. Type between patients (slows the floor). Hold notes until after the last patient (means reconstructing from memory). Or run some combination that produces thinner notes than the clinical encounters actually warrant.

An ambient scribe running during the visit removes that tradeoff. The note builds from the actual conversation: the patient's responses to your history questions, the exam findings you narrate, the plan you explain before they leave. By the time you're rooming the next patient, the draft is ready. You review it on the walk over.

For a 10-hour shift seeing 40-50 patients, those saved minutes add up. But the bigger return is note quality, not time. A note built from what was actually said in the room captures the MDM more completely than one reconstructed at the end of the day from a fading memory of 40 visits.

## The scribe reflects your reasoning, it doesn't generate it

The scribe captures what happens in the room. If you do not verbalize your differential, the risk stratification you ran through in your head, or why you chose observation over discharge, the note will not capture it. Your thinking has to be audible.

The ICD-10 suggestions that come back with the note are exactly that: suggestions. They are not a coding engine, and they do not auto-submit claims. The prescription draft is a draft you review before anything is signed. Nothing leaves your review queue automatically.

The scribe also does not handle documentation outside the encounter conversation, such as prior authorization letters, peer-to-peer calls, or forms that require separate completion. Those stay on your list.

What it does handle: the core visit note, structured as a SOAP note, including the elements that matter most for MDM, which are the problem complexity section, the data reviewed, and the risk reasoning as you stated it. In an urgent care setting where those elements are often the first thing thinned under time pressure, that is where the practical value sits.

## Evaluating a scribe for urgent care before you commit

A few questions worth answering before you pick a tool:

Does it handle the acuity range? A tool optimized for 20-minute primary care visits may produce generic notes for a chest-pain work-up or a pediatric respiratory distress visit. Run it on encounters across your acuity range, not just your easiest patients.

How does it handle interpreter-assisted visits? The 2025 ED study found physicians selectively avoided using AI scribes for interpreted encounters. If a meaningful share of your UC population uses interpreter services, test that scenario explicitly.

What is the note turnaround? In primary care, a 2-minute turnaround is fine. In a high-throughput UC setting where you are rooming the next patient before the previous one reaches the checkout, you want the note ready fast and the review to take under 60 seconds for straightforward visits.

What are the BAA terms? Any tool handling PHI from UC patient encounters needs a signed Business Associate Agreement. Confirm it before you start using it for real patient visits.

Our [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) walks through these questions and others in detail, and it is worth running through before you commit to any tool.

## Starting a trial in urgent care

The fastest way to validate a scribe for your UC workflow is a real shift, not a demo. Run it on a shift that covers your normal patient mix: some lower-acuity volume and a few higher-complexity encounters. Compare the note quality and your end-of-shift remaining documentation load against your baseline.

The 7-day trial is the right unit. One shift tells you if it works for simple visits. A week tells you if it holds up across the acuity range, handles your patient population, and fits into your pace without adding friction.

Pricing, with no hidden costs, starts from $79/month per clinician on the annual Assist plan. The full breakdown is on the [pricing page](../../pricing/). The plans differ by capability, not by volume: Assist is the scribe, Copilot adds a bundled AI EHR and messaging, and Autopilot layers on an AI receptionist and follow-up automation.

If you want to see a note built from a UC visit before running a trial, book a demo with a case from your actual workflow. Chest pain work-up, pediatric fever, laceration repair, bring the encounter type that puts your documentation under the most pressure, and see how the note comes back.

The MDM documentation gap in urgent care is not a knowledge problem. It is a time problem. The scribe addresses the time part.

---

## Ambient AI vs Dictation: Which Documentation Method Wins?
https://patientsquare.com/us/blog/ambient-ai-vs-dictation/
Published 2026-05-27 · Tags: dictation, ambient-ai, documentation-methods, ai-scribe

A three-way comparison of manual typing, dictation, and ambient AI on effort, eye contact, and edit load, so you pick the method that fits your day.

Dictation turns your speech into text: you narrate the note after the visit and the software transcribes it. Ambient AI listens to the whole visit conversation and drafts the structured note itself, so you don't narrate anything. Dictation moves typing to talking; ambient AI moves the writing off your plate entirely, with review.

Ambient AI beats dictation for most clinicians, because it removes a step dictation can't: the after-visit narration. With dictation you still reconstruct the visit aloud, 5 to 10 minutes of speaking plus cleanup. Ambient AI drafts the note while the visit happens, leaving you about two minutes of review. Dictation still wins if you like controlling every word. Below is the three-way comparison, manual typing included, on the things that actually matter in a clinic day.

These are three genuinely different ways to get a note written, and they trade off differently on effort, eye contact, and how much you edit afterward. Pick the wrong one and you've automated the wrong part of the problem.

> **Key takeaways**
>
> - Manual typing: full effort, eyes on screen, no transcription edits but maximum time.
> - Dictation: less effort than typing, but you still narrate the visit afterward (5-10 min) and fix misheard words.
> - Ambient AI: lowest in-visit effort, best eye contact, ~2 min review, but edits are clinical (catching invented findings), not just typos.
> - The dividing question: do you want to control every word (dictation) or get the visit off your plate (ambient)?

## Ambient AI vs dictation vs typing: the three-way comparison

Here's the whole picture in one table. The columns are the things you actually feel in a clinic day.

| | Manual typing | Dictation software | Ambient AI scribe |
|---|---|---|---|
| **When you write the note** | During or after the visit | After the visit, from memory | During the visit (software drafts) |
| **In-visit effort** | High, you type while talking | Medium, you speak findings or wait | Low, you just see the patient |
| **Eye contact with patient** | Poor, eyes on screen | Mixed, attention on narration | Best, nothing between you and the patient |
| **Your time per note** | Full write, 5-15+ min | 5-10 min narration + cleanup | ~2 min review |
| **Edit load** | None (you wrote it) | Transcription fixes (misheard words) | Clinical review (confirm assessment, catch errors) |
| **What it automates** | Nothing | The typing | The writing itself |
| **Cost shape** | Free (your time) | Low subscription | Subscription, ~1/10th a human scribe |

See the pattern? Each method takes more of the work off you and changes what's left over. Typing hands you the whole job. Dictation takes the typing but still makes you narrate the visit afterward. Ambient AI does the writing, so the leftover task is reading and confirming a draft. The real choice is which of those leftovers you'd rather live with: narrating a visit you already sat through, or reviewing a draft of it.

## Where does dictation still win?

Dictation isn't obsolete, and a fair comparison should say so out loud.

Its real strength is control. You decide exactly what goes in the note as you say it, with no model interpreting your meaning. For a fast dictator with a precise documentation style, or anyone who distrusts a system that paraphrases their clinical reasoning, that's worth a lot. The edit load is predictable too. Dictation errors are transcription errors, a misheard drug name or a wrong number, and they're easy to catch because you know what you said.

The weakness is the one step dictation can't remove. You still reconstruct the visit from memory once it's over, so the note keeps competing with your next patient or your evening. The 2016 Annals of Internal Medicine time-motion study found nearly two hours of EHR and desk work for every hour of direct care. Dictation trims that. It doesn't erase it, because the narration is still on you.

So dictation is the right call when control matters to you more than time. For most clinicians buried in after-hours charting, time is the thing in short supply.

## Where does ambient AI win?

On two fronts dictation can't touch. The narration step, and your attention during the visit itself.

Ambient AI takes out the after-visit reconstruction completely. The note is drafted from the actual conversation while you're having it, so there's no "now I sit down and narrate the visit" moment waiting at the end of the day. A 2025 UCLA trial measured one ambient tool cutting per-note documentation time. For a lot of clinicians the bigger change is the visit itself. With nothing to type or narrate, you can just look at the patient.

What changes is the kind of edit. With ambient AI you're not fixing typos. You're checking clinical substance: that the assessment matches your reasoning, and that nothing invented slipped into the note. That asks for a different kind of attention than spotting a misheard word, which is why note quality matters as much as it does. We built a [6-point rubric](../ai-scribe-soap-note-quality/) to grade exactly that. On routine visits a good ambient scribe leaves you less to edit than dictation does. A weak one can leave you more. That gap is the whole reason you test before you commit.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It captures English and more languages, and returns the note in clean clinical English. That last part is where dictation struggles, since a patient who switches languages mid-sentence leaves a dictation tool guessing.

## Which method should you actually pick?

Match the method to your actual bottleneck.

Manual typing is fine if your notes run short, your volume is low, and the screen time genuinely doesn't bother you. Some clinicians are wired that way, and there's nothing wrong with it.

Dictation makes sense when controlling every word matters to you more than the minutes it costs, and your after-hours load is something you can live with. The control it gives you is real.

Ambient AI is the pick when the after-visit reconstruction is the thing eating your evenings, when you'd rather have your eyes on the patient than the screen, and when you're comfortable reviewing a draft instead of writing one from scratch. That's most charting-heavy practices, frankly.

The honest way to settle dictation versus ambient is to run both for a week. It doubles as the cleanest A/B test you can do: keep dictating some visits, let an ambient scribe draft others, then compare your real time and your real edit load. We laid out that exact trial protocol in [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/).

## Run both for a week and compare

No need to guess which method fits your day. A trial week, dictation against ambient AI, tells you straight.

<a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">Compare the options</a> to watch an ambient scribe draft a structured note about two minutes after a sample visit, then run the 7-day free trial and put it head-to-head with how you document today. Time both, count the edits, and notice where your eyes are during the visit. For the dollars-and-minutes math, see [the real ROI of an AI scribe](../ai-scribe-roi-calculator-guide/); for the bigger documentation-burden picture, the [pillar on cutting charting time](../reduce-charting-time-clinicians/); and for how the field stacks up, the [best AI medical scribes](../best-ai-medical-scribes/) roundup.

---

## What Makes a Good AI-Generated SOAP Note?
https://patientsquare.com/us/blog/ai-scribe-soap-note-quality/
Published 2026-05-26 · Tags: soap-note, note-quality, ai-scribe

The anatomy of a clean SOAP note and a 6-point rubric you can use to grade any AI scribe, so you judge output quality instead of taking a demo on faith.

SOAP stands for Subjective, Objective, Assessment, Plan. The subjective is what the patient reports, the objective is what you observe and measure, the assessment is your clinical judgment, and the plan is what happens next. It is the standard structure for a clinical encounter note, and the format most AI scribes draft into.

A good AI-generated SOAP note is faithful, complete, and clean enough that you edit it in under a minute instead of rewriting it. It separates subjective from objective, gets the assessment and plan right, and invents nothing. The fastest way to tell a great scribe from a mediocre one isn't the demo, it's grading a real visit against a fixed rubric. We'll give you that rubric.

If you only evaluate scribes on a scripted demo, every product looks excellent, because demos are built to. The note you'll actually live with shows up on your messy Tuesday visit, with an interrupting relative and a patient who buries the real complaint in paragraph three. Here's how to judge it.

> **Key takeaways**
>
> - SOAP = Subjective, Objective, Assessment, Plan. A good AI note keeps the four sections clean and accurate.
> - The single biggest quality tell: does the Assessment and Plan match your reasoning, or just the transcript?
> - Every AI scribe makes errors, so review is non-negotiable; a 2025 UCLA trial noted notes "occasionally" contained clinically significant inaccuracies.
> - Grade a real visit with the 6-point rubric below, not a demo. Heavy editing on your hardest visit means the tool isn't saving time.

## What is a SOAP note, and what does each part carry?

Before you can grade an AI note, be clear on what each section is for. SOAP, per the StatPearls reference, is the standard encounter structure.

Subjective is what the patient tells you: the chief complaint, the history of present illness, symptoms, what they're worried about. Their account, in clinical language. Objective is what you measure and observe, the vitals and exam findings and results. Facts, not interpretation. Assessment is your clinical judgment, the diagnosis or differential and the reasoning behind it, and it's the section that's hardest for a model and most important to get right. Plan is what happens next: medications, tests, referrals, follow-up, patient instructions. A dropped plan item is a missed action, so completeness is the thing to watch.

An AI scribe listens to the conversation and drafts into those four buckets. The quality question is how faithfully it sorts what was said, and how well it handles the two sections, Assessment and Plan, that need clinical reasoning rather than transcription.

## The 6-point AI SOAP-note quality rubric

This is the artifact. Print it, grade a real note against it, and use the same six points on every scribe you trial. Each point scores 0 to 2: 0 fails, 1 is acceptable, 2 is good.

| # | Quality dimension | What "good" (2 points) looks like |
|---|---|---|
| 1 | **Faithfulness** | Every clinical fact in the note was actually said or observed. Nothing invented, no plausible-sounding finding the patient never reported. |
| 2 | **Section discipline** | Subjective, Objective, Assessment, Plan are cleanly separated. Symptoms don't leak into Objective; your judgment doesn't leak into Subjective. |
| 3 | **Assessment accuracy** | The diagnosis or differential matches your actual reasoning, not just the most-mentioned word in the transcript. |
| 4 | **Plan completeness** | Every action you decided, every med, test, referral, follow-up, is captured. Nothing dropped. |
| 5 | **Uncertainty handling** | When the audio was unclear or a detail was ambiguous, the note flags it rather than guessing a confident wrong answer. |
| 6 | **Edit load** | You can correct the draft in about a minute. If cleanup takes longer than writing from scratch would have, it scores 0. |

A perfect score is 12. Anything below about 9 on your real visits and you're buying cleanup work, not time. Number 1, faithfulness, catches the most scribes, because a confident hallucinated finding is worse than a blank field; you have to already know it's wrong to delete it. Number 3 is what separates the good scribes from the great ones. Anyone can transcribe. Getting the Assessment to match a clinician's reasoning is the hard part.

## Why does note quality matter more than the time-saved number?

Because a bad note erases the time saving and adds risk.

A 2025 UCLA randomized trial of ambient scribes noted that AI-generated notes "occasionally" contained clinically significant inaccuracies, and that physicians had to actively review outputs rather than passively accept them. That's the whole ballgame. If a scribe saves you 41 seconds of typing but adds two minutes of hunting for a hallucinated finding, you're worse off. The time figures from the [ROI math](../ai-scribe-roi-calculator-guide/) only hold if the note quality holds.

This is also why we won't quote you a single clean accuracy percentage for our own product, and why you should distrust any vendor who does. Note quality is multi-dimensional, the rubric above has six axes, and a single number papers over the ones that matter. We made that argument in full in [how accurate are AI medical scribes](../ai-scribe-accuracy-what-to-expect/).

## How an AI scribe should handle the hard parts

Grade these specifically. They're where real visits break a weak scribe.

Start with the multi-speaker room, a relative answering half the questions and a patient who keeps interrupting. A good scribe attributes statements to the right person and doesn't fold the relative's words into the patient's history. Then accents and crosstalk. A strong regional accent, a patient and a caregiver talking over each other, a noisy hallway bleeding through the door, that's the audio that trips a weak transcriber. AI Medical Scribe by Patient Square handles English plus more languages, and the note always comes back in clean clinical English. And the buried complaint: when the real reason for the visit surfaces late and offhand, a good scribe still lands it in the Assessment instead of losing it.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The Rx draft reflects the plan you discussed in the visit; it doesn't screen for interactions or dosing, so you review it before you sign, exactly as you review any prescription today. The note itself is still yours to read and approve.

## Grade your scribe on a real visit this week

The rubric is only useful with a real note in front of you. A scripted demo flatters every scribe equally; your actual patient mix sorts them out.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to watch a structured SOAP note appear about two minutes after a sample visit, then run the 7-day free trial and grade three real notes against the six points above. If a tool can't clear about 9 out of 12 on your own hardest visits, no time-saved claim will rescue it. For the wider buyer's view, our [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) scorecard turns this note grade into a full demo agenda, and the documentation-burden [pillar on cutting charting time](../reduce-charting-time-clinicians/) ties note quality back to the hours you're trying to recover.

---

## Best AI Medical Scribe for India in 2026: Honest Picks by Practice
https://patientsquare.com/in/blog/best-ai-scribe-for-india-2026/
Published 2026-05-25 · Updated 2026-08-30 · Tags: best-ai-scribe, india, roundup, comparison

An honest, India-segmented roundup of AI scribes for solo OPDs, multi-doctor clinics, and tier-2/3 practices, including where EkaScribe and Augnito fit better.

There is no single best AI scribe for every Indian practice. A solo OPD, a clinic that needs live ABDM workflows, and an enterprise dictation team have different requirements. Compare the exact product tier on language handling, prescription workflow, audio retention, connectivity, current price, and a real clinic-day test.

There's no single best AI scribe for India. Any roundup that crowns one winner without asking how you actually practice is trying to sell you something. The version that holds up sorts by practice type, because a solo OPD, a multi-doctor clinic, and a tier-2 or tier-3 practice want genuinely different things from the same tool. Below we name where AI Medical Scribe by Patient Square wins, and where EkaScribe or Augnito is the better fit. We have a horse in this race. We'll be clear about where it loses.

> **Key takeaways**
>
> - There's no universal best. A solo OPD, a multi-doctor clinic, and a low-signal practice each weight price, ABDM, and offline capture differently.
> - eka.care publishes ABDM platform material. Patient Square's ABDM integration is a roadmap item. Ask for a demonstration of the exact product and production workflow before relying on either vendor.
> - Patient Square Assist starts at ₹1,599 per clinician a month ex-GST, the monthly equivalent on annual billing. Copilot starts at ₹2,399 per clinician a month ex-GST, the monthly equivalent on annual billing, and includes the bundled AI EHR. EkaScribe publishes ₹1,499 a month for its scribe; request a separate EMR quote if that is required.
> - If Practo Ray or HealthPlix appears in your search, verify the current product and quoted scope before including it in an ambient-scribe comparison.

## Does an ambient scribe actually earn its place?

Fair question before you pick one, so here's the strongest recent evidence, with its limits stated. A quality-improvement study published in JAMA Network Open in October 2025 followed 263 clinicians across six US health systems for 30 days on an ambient AI scribe. Burnout among the ambulatory clinicians fell from 51.9% to 38.8%, and after-hours documentation dropped by roughly 0.9 hours per clinician a week. Those are real numbers from a peer-reviewed source, not a vendor deck.

Two honest caveats, because we'd want them if we were reading this. It's a US study, not Indian, and it's a before-and-after design with volunteers, not a randomised trial, so treat it as a strong signal rather than proof. What travels to an Indian OPD is the direction: when the note drafts itself, the documentation burden can shrink. Test that effect in your own visit length, language mix, and review workflow. That's what the roundup below is really sorting for.

## Who's actually in the India AI scribe market?

Before the picks, the field as it actually stands. Four names come up in scribe searches, and they aren't the same kind of thing.

EkaScribe (eka.care) publishes ₹1,499 a month for its scribe, a five-consult-a-day free tier, and 20-plus Indian languages; its EMR is a separate eka plan. eka.care also publishes ABDM platform material, but buyers should confirm the exact EkaScribe SKU and a clinic's production workflow. Augnito publishes Spectra for voice dictation and Omni for ambient documentation; request current scope and commercial terms from Augnito. AI Medical Scribe by Patient Square is one module inside Practice Copilot, which starts at ₹1,599 per clinician a month ex-GST, the Assist monthly equivalent on annual billing, for the scribe and adds a bundled AI EHR plus WhatsApp messaging from ₹2,399 per clinician a month ex-GST, the Copilot monthly equivalent on annual billing. It supplies a prescription draft for clinician review and processes visit audio in memory. If Practo Ray or HealthPlix appears in your search, verify the current product and written scope before treating it as an ambient-scribe comparator.

AI Medical Scribe by Patient Square is one module inside Practice Copilot. It builds a live transcript as you speak and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft the moment the visit ends, ready to review and sign; move up to the Copilot plan and it comes bundled with an AI EHR.

## Best AI scribe for a solo OPD doctor

Our pick here is AI Medical Scribe by Patient Square, with EkaScribe a close second.

For a solo doctor running a high-volume OPD, compare the published price and the prescription-review workflow. The scribe starts at ₹1,599 per clinician a month ex-GST, the Assist monthly equivalent on annual billing, with a prescription draft for clinician review and a 7-day free trial. Copilot starts at ₹2,399 per clinician a month ex-GST, the monthly equivalent on annual billing, and includes the bundled AI Copilot EHR and WhatsApp messaging. The [solo-doctor payback post](../ai-scribe-for-solo-doctors-india/) provides a separate buyer worksheet.

EkaScribe Pro publishes ₹1,499 a month for the scribe alone and a five-consult-a-day free tier. Its EMR is a separate plan, so request a current written quote before comparing a scribe-plus-record-system purchase. If ABDM matters, ask eka.care to demonstrate the exact product, clinic configuration, and production workflow. Request the same current scope and commercial terms from Augnito.

EkaScribe is a candidate to test when you want a standalone scribe or are evaluating eka.care's ABDM platform.

## Best AI scribe for a multi-doctor clinic

For a multi-doctor clinic, evaluate the scribe, record-system path, and commercial terms on the same visits. EkaScribe and Augnito remain candidates where their published scope fits the clinic's requirements.

A clinic adds two concerns a solo doctor doesn't have: per-seat economics, and whether the tool fits a workflow that's already running. Pricing is per clinician, so a multi-doctor clinic picks the tier that fits, Assist for the scribe or Copilot for the scribe plus the bundled AI EHR, and every seat on that plan gets the same prescription draft and the same language handling. Each doctor reviews and signs their own drafts, so the safety check stays where it belongs, with the prescriber, on every seat. The [India comparison](../india-ai-scribe-comparison/) lines us up against EkaScribe and Augnito seat by seat.

If the clinic is evaluating ABDM, ask eka.care to demonstrate the exact product and production workflow, including facility linkage, consent, sharing or receipt, failure handling, and audit records. Patient Square does not claim ABDM integration; it remains on the roadmap. Ask Augnito to demonstrate the relevant dictation or ambient product in the clinic's environment.

The right choice follows the demonstration and written scope, not the product name.

## Best AI scribe for a tier-2 or tier-3 clinic

Our pick here is AI Medical Scribe by Patient Square, and the reason is one feature most roundups skip entirely: offline capture.

In a low-signal town, the thing that matters isn't on most comparison tables. It's what happens when the connection drops mid-OPD. Patient Square documents [offline encrypted capture](../ai-scribe-offline-low-connectivity/) with on-device AES-256-GCM encryption for low-connectivity clinics. Ask the vendor to demonstrate the exact offline and language workflow, including recovery after a connection drop, in your environment. Visit audio is discarded once the note is drafted. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

For any candidate, test the exact low-signal workflow before buying. If connectivity is reliable, compare the remaining documented scope and commercial terms.

## The India AI scribe roundup, side by side

| | EkaScribe (eka.care) | AI Medical Scribe by Patient Square | Augnito |
|---|---|---|---|
| **Type** | India-native ambient scribe | Focused ambient scribe | Dictation + voice commands (Spectra); ambient (Omni) |
| **Published India price** | ₹1,499/mo scribe-only; EMR separate | from ₹1,599/mo ex-GST (Assist monthly equivalent on annual billing, scribe); ₹2,399/mo ex-GST (Copilot monthly equivalent on annual billing) adds the bundled AI EHR | Request current quote |
| **ABDM position** | eka.care publishes ABDM platform material; confirm exact SKU and production workflow | Roadmap, not shipping | Request current scope |
| **Rx handling** | Confirm the exact workflow with the vendor | Rx draft you review and sign | Dictation-led |
| **Visit audio** | Per their policy | Live consultation audio is processed in memory and discarded at note draft; uploads use a separate retention mode with explicit consent | Per their policy |
| **Offline capture** | Test with the vendor | Offline encrypted capture (AES-256-GCM on-device); test the exact workflow | Test with the vendor |
| **Trial / quote** | Free tier: 5 consults/day | 7-day free trial | Request current terms |
| **Buyer test** | Exact SKU and ABDM workflow | Note review, record path, and offline test | Exact dictation or ambient workflow |

## The honest verdict

Strip the marketing and start with the workflow you can demonstrate. eka.care is a candidate when its exact ABDM-enabled product and production workflow pass your test. Augnito is a candidate when its relevant dictation or ambient workflow passes. Practice Copilot from Patient Square is a candidate when you want transparent per-clinician pricing from ₹1,599 per month ex-GST on Assist's annual-billing equivalent, a bundled AI EHR from ₹2,399 per clinician a month ex-GST on Copilot's annual-billing equivalent, a prescription draft for clinician review, audio processed in memory, clean English notes from code-mixed input, and offline capture. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Patient Square's ABDM position is a roadmap item. Buy what the vendor can demonstrate in your environment, not what is promised.

The only useful test is a real OPD day. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, run it on your own Hindi, English, or Hinglish consults, and review the drafts before you decide. If price is your first question, the [India rate card](../ai-medical-scribe-price-india/) shows every figure in rupees with GST.

---

## What's the Real ROI of an AI Medical Scribe? The Per-Note Math
https://patientsquare.com/us/blog/ai-scribe-roi-calculator-guide/
Published 2026-05-22 · Updated 2026-07-22 · Tags: roi, pricing, ai-scribe

A worked ROI model for an AI medical scribe, built from the 2026 studies, priced against $79 a month, with the honest version of when it does not pay off.

It depends on your note volume and your hourly value, but the math is short. A 2025 UCLA trial measured about 41 fewer seconds per note for one ambient tool. At 20 patients a day that is roughly 14 minutes back daily. Against a $79 monthly subscription (the annual Assist plan), even a fraction of an hour saved per day clears the cost.

The real ROI of an AI scribe is whatever recovered time is worth to you, minus a small monthly fee. The honest 2026 studies put the time saved at about 41 seconds per note in one trial and roughly 16 minutes per eight clinical hours in another. At 20 notes a day, that's somewhere around 14 minutes back daily, against $79 a month. The arithmetic clears the cost long before you get to the burnout you didn't have.

Most "ROI calculator" pages inflate the inputs and skip the citations. We're going the other way. Real figures from the 2026 randomized trials, the math shown step by step, and an honest section on when it doesn't pay off so you can check your own situation against it.

> **Key takeaways**
>
> - A 2025 UCLA trial measured about 41 fewer seconds per note for one ambient tool; a 2026 JAMA study found ~16 minutes saved per 8 hours of patient care. Modest, real, well-sourced.
> - At 20 notes a day, ~41 sec each is roughly 14 minutes back daily. Over 20 working days that's about 4.6 hours a month.
> - At $79/month and 400 visits, the scribe costs about $0.20 a visit. Compare cost per visit, not the monthly sticker.
> - The break-even is tiny: recover about one hour of your time a month and the subscription has paid for itself at almost any clinician hourly rate.

## What does an AI scribe actually save you, in minutes?

Start with the studies, not the sales deck, because the inputs decide the answer.

The most rigorous 2026 read is a UCLA randomized trial published in NEJM AI: across 72,000 encounters and 238 physicians, one ambient tool cut average note-writing time by about 41 seconds, from 4 minutes 30 seconds to 3 minutes 49 seconds. A second tool in the same trial showed a smaller, statistically insignificant change. Separately, a JAMA study across five health systems found about 16 minutes of documentation time and 13 minutes of EHR time saved per eight hours of patient care, and called the effect "modest."

So we'll build the model on conservative numbers. If your notes track that 41-second figure and you write 20 a day, that's roughly 14 minutes back daily. Over 20 working days, about 4.6 hours a month. Some clinicians save more, the studies note primary care and high-note-volume practices benefit most, but 4.6 hours is a figure you can defend.

## The per-note math, worked out

Here's the whole calculation, no black box.

Say you see 20 patients a day, 20 days a month, 400 visits. At $79 a month on the annual Assist plan, the subscription cost per visit is:

| Input | Value |
|---|---|
| Monthly subscription (US, annual Assist) | $79 |
| Visits per month | 400 |
| **Cost per visit** | **$0.20** |
| Minutes saved per note (conservative, per UCLA) | ~0.7 |
| Total minutes saved per month | ~280 (about 4.6 hours) |
| Break-even time saving | recover ~1 hour/month and it has paid for itself at most clinician rates |

The break-even is the headline. You do not need to believe the optimistic time numbers. Even if you save a quarter of what the studies measured, the US subscription costs less per month than one recovered hour is worth to almost any clinician. That's why the ROI question is usually settled before you reach the patient-revenue argument. If you want the full price ladder rather than this single launch figure, it's on the [pricing page](../../pricing/), with the US rate card explained in our [AI medical scribe pricing breakdown](../ai-medical-scribe-pricing/).

There's a revenue angle too, and we'll state it carefully. The 2026 JAMA study found the time freed up allowed for about half an extra patient visit a week, which one estimate valued at roughly $167 a month per clinician. Treat that as a possible upside, not a promise, it depends entirely on whether you fill the recovered time with patients or with leaving on time.

## When does an AI scribe not pay off?

We'll say it plainly, because an honest ROI page has to.

Sometimes charting just isn't your bottleneck. If you already have a human scribe you're happy with, or your notes are short and fast, the time saved is small and the subscription is only a cost. Sometimes the problem is the opposite, that you won't actually read the drafts. The savings come from editing a near-complete note, not from skipping review, and any vendor implying you can sign unread is selling past the evidence. A wrong note you didn't catch costs far more than $79. And sometimes the note quality just fails on your visits. A scribe that drafts badly on your accents, your specialty, or your noisy room adds cleanup time instead of removing it. That's the one input the calculator can't fake, which is why you test before you trust. Grade it with our [SOAP-note quality rubric](../ai-scribe-soap-note-quality/), and read why we won't quote you a clean accuracy number in [how accurate are AI medical scribes](../ai-scribe-accuracy-what-to-expect/).

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The draft is a starting point you check and own. That review step is exactly why the ROI depends on quality, not just price.

## Run the calculator on your own numbers

The model above uses defensible figures, but yours are the ones that matter. Plug in your real note count, your real per-note time, and your own hourly value, then decide.

The fastest way to get a true per-note time figure is to measure it. Book a demo to see a finished note appear about two minutes after a sample visit, then run the 7-day free trial on a real clinic week and time both the saving and the cleanup. The number you get from your own visits is the only ROI number worth trusting. If you're comparing tools first, [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) and the documentation-burden [pillar on cutting charting time](../reduce-charting-time-clinicians/) are the next two reads, and the [best AI medical scribes](../best-ai-medical-scribes/) roundup lays out the field.

---

## Beating Pajama Time: After-Hours EHR Work and AI Medical Scribes
https://patientsquare.com/us/blog/ai-scribe-pajama-time/
Published 2026-05-21 · Tags: pajama-time, after-hours-ehr, burnout, ai-scribe

What "pajama time" really is, how much US physicians log, where the after-hours EHR minutes go, and how much of it an AI scribe can realistically take back.

Pajama time is the EHR work physicians do after hours, at home, outside the normal workday, typically between 5:30pm and 7am. It is charting, inbox, and orders that didn't fit into the clinic day. The AMA tracks it as a core measure of administrative burden, and it has barely moved in recent years.

Pajama time is the EHR work that follows you home, the charting, inbox, and orders you finish at 9pm because the clinic day had no room for them. About 1 in 5 US physicians spend more than eight hours a week on it, and that number hasn't budged in years. An AI scribe can take back the documentation slice, which for most clinicians is the largest piece, but not the inbox. Here's the honest breakdown of what moves and what doesn't.

If you've ever signed a note in bed, this is your category. Charting happens to be the most automatable part of the after-hours load, which is the good news. It's also not the whole load, and we'll be straight about where that line falls.

> **Key takeaways**
>
> - About 1 in 5 US physicians spend 8+ hours/week on after-hours EHR work; 20.9% in 2023, 22.5% in 2024 (AMA).
> - Family physicians averaged 86 minutes of after-hours administrative EHR work a night (Annals of Family Medicine).
> - Across the EHR day, roughly 44% is clerical/admin, 33% medical care, 24% inbox. Documentation sits in the clerical slice.
> - An AI scribe targets the charting piece; a 2026 JAMA study found it did not significantly change total after-hours EHR time, because the inbox stays.

## What is pajama time, exactly?

It's the EHR work that doesn't fit the workday and moves into your evening. The AMA defines the after-hours window as roughly 5:30pm to 7am on weekdays, the hours you're not seeing patients but are still in the chart.

And it's stubborn. The AMA's Organizational Biopsy survey, drawn from nearly 18,000 physicians, found 22.5% of physicians spent more than eight hours a week on after-hours EHR work in 2024, up from 20.9% in 2023. Even as total physician hours have edged down, the EHR has followed people home at the same rate. One older study of family physicians using Epic event logs clocked the nightly load at 86 minutes of administrative work after hours. That's an hour and a half, most nights, after the last patient leaves.

This is the part of the job nobody trained for and nobody scheduled. It's also a documented driver of burnout, which is why it gets its own metric.

## Where do the after-hours minutes actually go?

Not all of pajama time is the same task, and that matters for what a scribe can fix.

Looking at the full EHR day, an Annals of Family Medicine study found the time split roughly into 44% clerical and administrative work, 33% medical-care tasks, and 24% inbox management. Documentation, the note-writing, sits inside that clerical slice, and it's the single biggest chunk. The inbox, the third of the day spent on messages, results, and refill requests, is a separate problem.

So when you think about beating pajama time, picture the load as two piles. One is documentation, the note you reconstruct from memory at night. The other holds everything else, inbox and prior auth and orders. An AI scribe is a documentation tool. It goes after the first pile hard and leaves the second one sitting there. Pretending otherwise is how vendors oversell.

## How much pajama time can an AI scribe take back?

The charting slice, mostly. The rest, no, and the studies don't pretend otherwise.

Here's the honest version. A 2026 JAMA study across five health systems found ambient AI saved about 16 minutes of documentation time per eight hours of patient care, and 13 fewer minutes in the EHR overall. It also found no significant change in after-hours EHR time. That second finding is the one to sit with. The scribe pulled documentation out of the workday, but total evening EHR work barely moved, because the inbox and the rest of the clerical load are still sitting there waiting for you.

So the realistic promise isn't "no more pajama time." It's narrower and truer: the charting reconstruction comes out of your evening. Instead of opening a blank note at 9pm and rebuilding a visit from memory, the note got drafted while the visit happened, and you reviewed it about two minutes after the patient left. If your after-hours load is mostly documentation, that's a large win. If you're drowning in inbox, it's a smaller one. Know which you are before you buy.

## Does cutting pajama time reduce burnout?

For the charting-heavy clinician, the evidence says it helps, and meaningfully.

After-hours charting is one of the most resented parts of the job, and removing it tends to move burnout more than the raw minutes would suggest. We laid out the full evidence, including the gap between modest measured time savings and larger felt improvements, in [the 2026 evidence on AI scribes and burnout](../ai-scribe-burnout-evidence/) and the question-and-answer companion, [do AI scribes reduce burnout](../do-ai-scribes-reduce-burnout/).

What a scribe won't fix: the inbox, prior authorization, staffing, the workload sources of burnout. If documentation is your biggest evening burden, an AI scribe targets it directly. If your nights are mostly messages, temper the expectation.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The note is drafted during the visit, so the reconstruction that used to wait for your evening doesn't.

## Find out how much of your evening is charting

The honest way to know what an AI scribe would do for your pajama time is to measure how much of it is documentation versus inbox, then test the documentation piece on real visits.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to see a note appear about two minutes after a sample visit, then run the 7-day free trial on a real clinic week and notice how many evenings you don't reopen a chart. If most of your after-hours load is note-writing, that's the load an ambient scribe is built to lift. For the per-note dollar math, see [the real ROI of an AI scribe](../ai-scribe-roi-calculator-guide/); for where this fits in the bigger documentation-burden picture, start at the [pillar on cutting charting time](../reduce-charting-time-clinicians/). The denials angle, a separate revenue story, is in [can better notes cut claim denials](../ai-scribe-claim-denials-documentation/).

---

## HPR and HFR Registration: A Doctor's Step-by-Step (2026)
https://patientsquare.com/in/blog/hpr-registration-guide-doctors/
Published 2026-05-21 · Updated 2026-09-08 · Tags: abdm, hpr, hfr, india, registration

A clear step-by-step guide to HPR and HFR registration for Indian doctors in 2026: what each registry does, what you need, and how the DHIS payoff connects.

HPR (Healthcare Professionals Registry) is for individual doctors and health workers. HFR (Health Facility Registry) is for clinics, hospitals, and diagnostic labs. You register yourself on HPR; you register your clinic on HFR. Both are run by the National Health Authority and are the entry point to ABDM workflows.

To register on HPR (Healthcare Professionals Registry), go to hpr.abdm.gov.in, log in with Aadhaar OTP, enter your state council registration number, upload your degree certificate, and confirm your profile. Your HFR (Health Facility Registry) registration at facility.abdm.gov.in follows the same Aadhaar-based flow but asks for clinic address and facility type. Both are free, both run by the National Health Authority, and together they put your clinic on the ABDM map. That needs to happen before any ABHA-linked record or DHIS incentive is possible. This guide walks each step in plain language.

> **Key takeaways**
>
> - HPR and HFR are two separate registries: HPR is for you as a practitioner; HFR is for your clinic as a facility. Both need Aadhaar-linked verification.
> - Registration is free and self-service; self-declaration-based HPR typically completes in 20 to 30 minutes.
> - HFR registration is the practical prerequisite for ABHA-linked records, DHIS incentive eligibility, and AB PM-JAY facility verification.
> - HFR and DHIS registration are prerequisites for facility incentives, not proof that a record is eligible or that NHA will pay it. Check the current policy before forecasting.
> - ABDM integration (linking records from inside your software) is a separate step that depends on your software vendor being ABDM-certified. AI Medical Scribe by Patient Square has this on the roadmap, not shipped yet.

_Source: NHA, ABDM portals (hpr.abdm.gov.in, facility.abdm.gov.in) and the current DHIS FAQ._

## HPR: what it is and why a solo clinic needs it

The Healthcare Professionals Registry is the NHA's national database of verified doctors, nurses, pharmacists, and other health workers. Every practitioner gets an HPR ID, which functions as a verified professional identity within the ABDM ecosystem. It is what lets the system know that the person generating a clinical record is a credentialed health professional, not an anonymous data source.

For a solo GP or a specialist, HPR matters for three practical reasons. First, it is the professional anchor for ABHA-linked records. When you generate a record and link it to a patient's ABHA, the system traces that record back to a verified practitioner on HPR. A record without an HPR-linked practitioner sits outside the ABDM chain. Second, AB PM-JAY facility empanelment increasingly checks HPR-linked practitioners at the facility. If empanelment or scheme-based billing is on your roadmap, being on HPR makes the paperwork simpler later. Third, it puts you on record as part of India's digital health infrastructure, which matters if the government eventually makes ABDM participation a condition for public-sector billing or insurance tie-ups.

Registration is not a bureaucratic end in itself. It is the professional half of a two-part handshake. The facility half is HFR. Both have to be in place before ABHA-linked workflows run.

## HFR: the facility half of the same handshake

The Health Facility Registry is the NHA's database of clinics, hospitals, diagnostic labs, pharmacies, and other health facilities. HFR gives your clinic a facility ID, which is what allows ABHA records to be tagged to a specific physical location in the network.

HPR identifies who treated the patient. HFR identifies where. ABHA links the patient record to both. All three are needed before you have a functioning ABDM-linked record in the NHA's sense.

The registration flows are similar (both use Aadhaar-based identity verification and self-service portals) but the data they collect is different. HPR collects professional credentials: council registration number, degree, specialisation. HFR collects facility attributes: address, type (clinic/hospital/lab/pharmacy), bed count, services. For a solo clinic, you will typically register on HPR as a practitioner first, then register the clinic on HFR, then link your HPR profile to the HFR facility. The linkage is the step most guides skip, and it is the one that actually activates the two-part handshake.

## What you need before you start

Gather these before opening either portal. Both HPR and HFR registrations stall at document upload if you don't have them ready.

**For HPR:**
- Aadhaar-linked mobile number (OTP-based verification, your registered Aadhaar mobile is required)
- Valid email address
- Medical registration certificate from your state medical council
- Degree certificate (MBBS, MD, MS, or equivalent)
- Your state council registration number (the alphanumeric on your council registration card)
- A photograph (passport size, clear, recent)

**For HFR:**
- Aadhaar-linked mobile number (same Aadhaar basis as HPR)
- Clinic address proof (rent agreement, utility bill, or property document)
- Facility registration proof where applicable (trade licence, shop establishment certificate, or society/trust registration for hospitals)
- Number of beds (including zero for a bedless clinic; the field exists and is required)
- Services offered (OPD, IPD, emergency, diagnostic, pharmacy; check what applies)

Nothing here is unusual. Most of it sits in a drawer or a folder on your computer already. The Aadhaar mobile number is the one place people get stuck. If your registered Aadhaar mobile is a number you no longer use, fix that at your nearest Aadhaar Seva Kendra before you start the portal process.

## Step-by-step: HPR registration

The HPR portal is at hpr.abdm.gov.in. Walk through it in this order.

**Step 1 — Create an account or log in**

Go to hpr.abdm.gov.in and click "Register" if this is your first time. You will be prompted to enter your Aadhaar number. An OTP will arrive on your Aadhaar-linked mobile. Enter it. This creates your NHA account and ties it to your verified identity. (The portal also supports DigiLocker-based verification for doctors who prefer that path; check the NHA login page for current options.)

If you already have an ABHA account (the patient-facing ABHA ID is different from a practitioner HPR ID), you can log in using those credentials instead.

**Step 2 — Fill in basic professional details**

After verification, the portal asks for name, date of birth, gender, and contact details. These pre-populate from your Aadhaar where available. Correct anything that looks wrong before proceeding; Aadhaar-sourced data cannot be edited mid-flow.

**Step 3 — Enter your medical registration**

This is the core step. Select your state medical council from the dropdown, enter your registration number, and upload your registration certificate as a PDF or image. The portal validates the format; a JPG under 1 MB works reliably.

You have two paths here: **self-declaration** (you attest your credentials and registration completes immediately, pending future council verification) or **verification-based** (NHA cross-checks directly with your council, which can take days to weeks depending on council response time). For most GPs not in a time-bound empanelment process, self-declaration is the practical choice. Council verification gets triggered in the background.

**Step 4 — Add qualification details**

Enter your primary degree (MBBS, MD, MS, BDS, BHMS, BAMS, or other), the year of passing, and the university. Upload your degree certificate. For a specialist, add the postgraduate qualification separately in the qualification section; there is an "add another" option.

**Step 5 — Set your specialisation and work experience**

Choose your primary specialisation from the NHA's list. Add your current place of practice. You can add multiple practice locations if you work at more than one clinic, and you can link each location to an HFR facility once that registration is done.

**Step 6 — Submit and get your HPR ID**

Review the summary page carefully. Once you submit, the NHA generates your HPR ID: a 14-digit identifier formatted `98XXXXXXXXXXXX`. Save it. You'll need this number when linking your HPR profile to HFR and when your software eventually connects to ABDM.

## Step-by-step: HFR registration

The HFR portal is at facility.abdm.gov.in. The flow is similar to HPR but asks about the place, not the person.

**Step 1 — Go to facility.abdm.gov.in and log in**

Use the same Aadhaar-based credentials you set up for HPR. If you registered for HPR first, these carry over. Click "Register a New Facility" from your dashboard.

**Step 2 — Enter facility type and basic details**

Choose the facility type (clinic, hospital, nursing home, diagnostic lab, pharmacy, health and wellness centre, or other). Enter the facility name exactly as it appears on your registration or signage. Enter the address, including pincode. The portal cross-references pincodes against state and district codes; mismatches flag immediately.

**Step 3 — Upload facility documents**

Upload proof of address (utility bill or rent agreement works) and, where applicable, your registration certificate (trade licence or establishment certificate). For a clinic running from a residence, a utility bill in your name at that address is usually sufficient.

Enter the facility details the HFR form asks for, including bed count where applicable, and keep them accurate. Do not use an older bed-based DHIS illustration to forecast a current claim; NHA has revised the transaction model through later corrigenda.

**Step 4 — Add services and operating hours**

Check the services your clinic actually provides: OPD consultation, preventive care, family medicine, and any specialist consultations. Do not check services you don't offer; ABDM workflows may route patients based on listed services. Add your typical operating hours.

**Step 5 — Link your HPR profile**

This step is the one most guides miss. Before submitting HFR registration, use the "Add Practitioners" section to associate your HPR ID with the facility. Enter your 14-digit HPR ID and confirm. This creates the professional-facility link in the ABDM ecosystem.

If you have associates or consultants working at the facility, you can add their HPR IDs here too, provided they have completed their own HPR registration.

**Step 6 — Submit and get your facility ID**

Review the facility details and submit. The portal generates a facility ID. For verified facilities, a QR code is issued too, which can be displayed in the clinic and scanned by patients to confirm they are at an ABDM-registered facility. Note the facility ID and keep it with your clinic records.

## The DHIS connection: what registration actually unlocks

Completing HPR and HFR registration is not the finish line. It is the on-ramp. Here's what becomes possible once both are done.

First, ABHA-linked records become possible. Your software (or the NHA's own apps) can create and link patient records to ABHA IDs, tag them to your HPR practitioner profile, and associate them with your HFR facility. This is the record-linkage that DHIS measures and rewards.

Second, the facility can enter the DHIS workflow—but eligibility does not arise from HFR registration alone. The effective corrigendum controls which KYC-verified ABHA-linked records count, how the monthly baseline is deducted, the per-patient limits, the required software milestone and version, and the claim window. The [ABDM incentives guide](../abdm-incentives-for-doctors/) is the maintained home for those volatile rules and shows when its NHA sources were last checked and when they are due for review.

Third, consent-based record exchange opens up. With M2 certification (for your software vendor, not you personally), patients can consent to share records from your clinic with other providers. Your records become portable on the patient's terms.

Registration unlocks the ABDM workflow for your clinic. Software certification (the M1/M2/M3 milestones) is the vendor's job, not yours. You can be on both registries and still need your software vendor to clear ABDM certification before records flow digitally inside the system. These are separate questions. Worth asking separately.

## What changes after registration is live

The practical difference is gradual, not overnight. A few things happen immediately.

Your HPR ID is live and searchable in the NHA's public registry. Patients with ABHA accounts can add you as a provider. Government-scheme portals that cross-reference HPR will see your registration.

For record linkage to work, your software needs the relevant ABDM capability in production, not merely in a sandbox or roadmap. The NHA's path has three milestones: M1 covers identity and registration flows, M2 covers record linking and sharing as a Health Information Provider, and M3 adds consented record requests as a Health Information User. The effective DHIS rules can impose role-specific milestones plus a current API-version requirement, so ask for the vendor's production evidence and check it against the current NHA policy rather than assuming one old milestone label settles eligibility.

That's why the honest framing here is: registration is necessary but not sufficient. You do your part on the registries; your software vendor does theirs on the milestone certification.

## A note on where the AI Medical Scribe by Patient Square sits in this

Patient Square is an AI clinical platform, and its AI Medical Scribe is the ambient scribe module: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The documentation it produces, clean, structured, retrievable, is exactly the kind of record that feeds an ABHA-linked workflow when ABDM integration is in place.

What we don't do yet: we are not ABDM-certified. We do not link records to ABHA inside the tool. We are not a DHIS-registered digital solution company. ABDM integration is on our roadmap, and we will not call ourselves ABDM-compliant before we clear the milestones. If you need ABHA record linkage from inside your documentation software today, eka.care ships that integration and is the honest recommendation. That's the line.

What we do now is make the documentation accurate enough and fast enough that it's ready to feed whatever ABDM workflow you run. The note is drafted in about two minutes. Audio is processed in memory and discarded once the note is complete. No recording sits on a server, which is the cleaner answer under the [DPDP Act 2023](../dpdp-act-clinics-guide/) and its consent-first, purpose-limitation logic. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256). Notes belong to your practice; you can export or delete any visit anytime. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing is published ex-GST, per clinician a month. Assist starts at ₹1,599 on annual billing for the documentation essentials; Copilot at ₹2,399 adds a bundled AI EHR and WhatsApp; Autopilot at ₹3,999 adds an AI receptionist and follow-ups. Add 18% GST, so the Assist entry works out to about ₹1,887 a month all-in. There is a 7-day free trial through the India signup page.

If you're walking the ABDM onboarding path, HPR done, HFR done, now wondering what digital documentation setup makes the record-keeping part manageable: <a href="/in/how-it-works/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and ask specifically how the note structure maps to what ABHA-linked records need. Or start the 7-day trial and see how a 20-patient OPD day looks when the note drafts itself.

---

## AI Medical Scribe for Emergency Medicine: MDM & E&M Documentation
https://patientsquare.com/us/blog/ai-scribe-for-emergency-medicine/
Published 2026-05-20 · Updated 2026-09-29 · Tags: ai-scribe, emergency-medicine, mdm, specialty

How an AI scribe handles MDM complexity, critical-care time, and parallel-patient documentation in the ED, for ER physicians evaluating a scribe.

Yes, but with an important caveat: the scribe drafts the note and surfaces ICD-10 suggestions; you still confirm the MDM level and sign. Starting in 2023, ED E/M codes 99281-99285 are selected on MDM alone, so the note has to capture the number and complexity of problems addressed, the data reviewed, and the management risk. A well-trained ambient scribe captures enough clinical detail during the encounter that your MDM reasoning is already reflected in the draft when you sit down to review it.

An AI scribe in the ED has to clear a higher bar than in primary care. The documentation can't just be a readable summary. It has to support your MDM-based E/M code selection, hold up under audit, and capture critical-care time precisely when it applies. And you have to get all of that done across a shift where you are managing several patients at once and getting interrupted roughly every six minutes.

An ambient scribe handles the capture part. The review and attestation stay with you. Here is what that looks like in a real ED shift.

> **Key takeaways**
>
> - A 2024 Yale study (JAMA Network Open) found ED attending physicians spend a median of 3.72 minutes per encounter on documentation. Modest on any single note, but the EHR time compounds across 15 to 20 patients in a shift.
> - Since 2023, ED E/M codes 99281-99285 are selected on MDM alone. The note has to reflect the number and complexity of problems addressed, data reviewed, and management risk, not a time-counted exam.
> - Critical-care time (CPT 99291/99292) requires an exact minute count and clear justification. Ambient capture at the bedside gives you the narrative to back that number.
> - About two-thirds of ED attending time involves managing three or more patients simultaneously (observational workflow data). That parallel-patient model favors per-patient ambient sessions over push-to-talk dictation.

## What changed in 2023 for ED E/M documentation

Before 2023, ED E/M coding could go through either the history and physical exam route or the MDM route. Starting in 2023, the AMA CPT guidelines for ED E/M codes 99281 through 99285 removed the history-and-physical counting method entirely. Code selection is now based solely on medical decision making.

MDM in the ED still rests on three familiar axes: the number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications or patient management decisions. The highest two of those three determine the code level.

What this means for your notes: you do not need to count examination elements anymore, but you do need your note to clearly support the MDM complexity level you are selecting. A note that describes a straightforward complaint in generic terms will not support a 99284 or 99285 when an auditor is looking at it. A note that captures the acuity, the clinical reasoning, and the data you actually reviewed will.

An ambient scribe running during the encounter captures all of that in real time. You described the problem to the patient. You talked through the differentials with the resident. You reviewed the CT findings out loud. When the draft comes back two minutes after you close the session, the clinical reasoning you expressed during the visit is already in it. Not reconstructed from memory after five more patients.

## How the MDM documentation fits together in a busy shift

Take a typical adult medicine ED shift: 15 to 20 patients, a mix of complaint types, some who bounce to observation, one or two critical cases. For most encounters the MDM documentation is the note. You need the history, the physical findings, what you ordered and why, and your impression and plan.

With push-to-talk dictation, the usual pattern is: see patient, return to the workstation between other patients, dictate from memory. In a fast department with interruptions coming in at about 10 times per hour, that memory gap is where documentation slips. The note ends up vaguer than the actual encounter was.

With ambient capture: open a session at the bedside, see the patient, close it when you leave. The note drafts while you are in the next room. By the time you have a free moment, the draft reflects what you actually said and did.

That is the practical difference. Not whether the scribe understands MDM theory. Whether the note it produces has enough specificity to support the code you are assigning. Your review of the draft is where you make that call.

If you are still working out which scribe features matter most for your setting, the [9-question evaluation scorecard at how-to-evaluate-ai-medical-scribe](/us/blog/how-to-evaluate-ai-medical-scribe/) covers audio handling, coding honesty, export rights, and pricing transparency in detail.

## Critical-care time: what the scribe gives you and what it doesn't

CPT 99291 covers the first 30 to 74 minutes of critical care; 99292 covers each additional 30-minute block. To bill either, you need an exact time documented, the time has to exceed 30 minutes, and the documentation needs to make the case for why that time was critical-care time.

Critical-care time includes: evaluating the patient, reviewing labs and imaging, speaking with EMS or transport teams, family discussions, consultant calls, documenting the visit, and retrieving outside records. It excludes time spent on separately billed procedures.

An ambient scribe does not count your time for you. What it does is give you a complete narrative: the EMS handoff discussion, the family conversation about goals of care, the attending-to-attending call to the ICU. That story exists when you sit down to document the time count. An auditor looking at a 99291 needs it. Without it, the minute number in the chart floats unsupported.

You still enter the exact count. You still attest. But you are doing that with a full draft already in front of you, not pulling a resus together from memory at the end of a twelve-hour shift.

## The parallel-patient problem

Primary care has a sequential model: one patient at a time, a defined visit slot, a chart that waits. The ED does not work that way.

An observational study of ED attending workflow found that about two-thirds of attending time is spent managing three or more patients simultaneously. Interruptions come in at roughly 10 per hour; when a physician gets pulled away, the task they were on doesn't always get picked back up. That fragmentation is what pushes documentation out of the clinical window and into after-shift charting.

Ambient capture maps onto this model better than dictation does. You start a session when you walk into a room, you interact with the patient normally, and you close it when you leave. The capture is tied to that specific encounter. You do not need to reconstruct the visit from notes or memory later, and you do not need a quiet moment to dictate that may or may not come before end of shift.

The per-patient session structure also means you can run captures for different patients without mixing them up. Each encounter has its own draft. When you have a moment to review between patients, you work through the queue rather than rebuilding one long narrative from a fragmented shift.

## What the note actually looks like after the scribe drafts it

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Move up the plans and you also get a bundled AI EHR, scheduling, and messaging, but the scribe is the piece that changes your shift.

For an ED context, the SOAP format maps onto what an ED note needs: the subjective presenting complaint and history, the objective findings and data, the assessment including your differential reasoning, and the plan including disposition. ICD-10 suggestions give you a starting point for diagnosis coding. You confirm what is right, adjust what is not, and assign the final codes. The Rx draft covers medications you are ordering at discharge; yours to review before anything is finalized.

The note also includes enough clinical detail to support the MDM level because it captured your actual clinical reasoning during the visit, not a post-hoc summary. That is the difference from a template or a generic note.

To be direct about one thing: the scribe does not level your E/M code for you. It surfaces ICD-10 suggestions, not an MDM score or an automatic code assignment. The code selection, the critical-care time count, the attestation: all yours. What the scribe does is make the note that supports all of those things faster to produce and more complete when it arrives.

## The audio question for an ED setting

Emergency departments are loud in a particular way: multiple conversations happening at once, other patients audible through curtains, staff talking behind you while you examine someone in front of you. That is the environment where some ambient tools quietly fall apart. Transcription accuracy drops, or the recording captures too much of the wrong room.

AI Medical Scribe by Patient Square processes audio in memory and discards it the moment the note is drafted. No recording is kept. Nothing to retain, subpoena, or accidentally expose. In a shared clinical space where ambient sound includes half the department, that is not a minor implementation detail. It is what makes the tool viable in an ED at all.

Patient Square is HIPAA compliant, with BAAs available for every customer and a SOC 2 Type II audit currently underway. If you want the technical detail on how we handle PHI in clinical environments, [the security page](/us/security/) covers it.

## The cost math for an ED physician

An ED physician covering 15 to 20 patients a shift, working 12 shifts a month, is generating 180 to 240 encounters a month. From $79 per clinician per month on the annual Assist plan, you are paying well under 50 cents per encounter for the time-recovery. The math clears fast.

The harder-to-price return is the after-shift charting you stop doing at home. Per ongoing AMA tracking, EHR time continues bleeding into evenings for most physicians even as overall burnout rates inch down. The time compounds in the direction you probably care about most: finishing at the end of shift instead of at midnight.

The full pricing structure with no asterisks is on our [pricing page](/us/pricing/).

## Evaluating a scribe for ED work: the questions that are different

Most scribe evaluations center on note quality and price. That is correct, but the ED adds a couple of wrinkles worth pressing on.

The complexity test matters more here than in primary care. Ask a vendor for a trial on a real, representative case: an MDM 4 encounter, a chest pain workup, a resuscitation note. Grade the draft against what you would have written for that patient. If the note comes back generic when the encounter was complex, that is your answer before you spend a dime.

The audio question is also sharper in an ED context. When you ask a vendor what happens to the recording, the answer should be one sentence. "Processed in memory, discarded on note creation" is fine. "Retained for quality review" is not, full stop. You do not get to explain that one to a patient whose room shared walls with three others.

The trial design matters too. A seven-day trial on real ED shifts, with your actual patient mix, is the only credible data point. A scripted demo in a quiet exam room does not tell you anything about a Tuesday overnight.

On pricing: some scribes charge per note or per minute, which adds friction for shift-based practice. Know what you are paying per encounter at your volume before you commit. The full pricing structure for AI Medical Scribe by Patient Square is on our [pricing page](/us/pricing/), no asterisks.

Book a demo to run note quality against your specific visit types, then score the MDM specificity yourself on a real shift week.

---

## AI Medical Scribe That Works Offline in a Low-Signal Clinic
https://patientsquare.com/in/blog/ai-scribe-offline-low-connectivity/
Published 2026-05-20 · Updated 2026-07-22 · Tags: offline, low-connectivity, tier-2-3, india

How an offline AI scribe captures the visit with on-device encryption when the signal drops mid-OPD, then syncs later. Built for tier-2 and tier-3 clinics.

Most cloud scribes stall when the signal drops. AI Medical Scribe by Patient Square captures the visit offline on the device, encrypted with AES-256-GCM, and syncs the note when the connection returns. You keep seeing patients during a power cut or a dead tower; the record catches up on its own. The capture step does not wait for bandwidth.

Most AI scribes assume a clinic that never loses signal. A lot of Indian clinics don't have that luxury. AI Medical Scribe by Patient Square captures the visit offline on the device, encrypted with AES-256-GCM, and syncs the note once the connection comes back. So a dropped tower or a power cut at 11am in a tier-2 OPD doesn't cost you the record. You keep working; the note catches up.

> **Key takeaways**
>
> - Offline capture runs on the device, encrypted with AES-256-GCM. The note syncs when the connection returns.
> - Visit audio is processed and discarded once the note is drafted, so no audio archive piles up on the phone. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - Built for tier-2 and tier-3 clinics where signal drops mid-OPD and a cloud-only scribe would simply stop.
> - Languages don't change offline: English, Hindi, and 20+ Indian languages in, clean clinical English out.

## Why does a cloud-only AI scribe fail in a low-signal clinic?

Because the capture step is waiting on bandwidth it doesn't have.

A pure cloud scribe streams the visit to a server in real time. That's fine in a metro hospital on fibre. It's a problem in a town where the tower drops for an hour at midday, the power flickers, and the 4G icon turns into an E. When the stream breaks, a cloud-only tool either errors out, loses the segment, or makes you start over. None of those are acceptable when there are forty patients in the corridor and you can't stop to debug a network.

This isn't a rare edge case in India. Connectivity outside the big metros is genuinely present but genuinely unreliable, and a clinic can't predict which fifteen minutes of the day the signal will vanish. So the question for any scribe you evaluate isn't "does it support offline?" as a checkbox. It's "what exactly happens to this visit if the connection dies in the middle of it?"

## How does offline capture actually work?

One design principle holds the whole thing up: capture should never depend on the network. Only sync should.

So capture happens on the device. When you start a session, the visit is captured locally on the phone or laptop, signal or no signal. The scribe doesn't phone home to begin. It just works. That local capture is encrypted with AES-256-GCM on the device, so it isn't sitting there in plain form waiting for a connection. Lose the phone, or have it seized, and the buffer still isn't readable.

Audio gets discarded, not hoarded. Visit audio is processed and then discarded the moment the note is drafted, so the offline buffer never grows into a library of recordings on your phone. What stays is the structured note. And the sync step is only for that note, encrypted in transit. When the device reconnects, the note syncs over TLS 1.2 or newer, and the structured SOAP note, ICD-10 suggestions, and prescription draft become available to review and sign, in clean clinical English. You review it a little later than usual. You don't lose it. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Offline-first capture is what keeps that promise true when the clinic's connection won't cooperate.

## A real scene: the signal drops at 11:40am

Picture a single-doctor clinic in a tier-3 town. Forty-eight patients booked, a busy Saturday OPD. At 11:40 the local tower goes down, the way it does most weeks. A cloud-only scribe would stall on the next patient, and the doctor would be back to scribbling on paper for an hour, then retyping it that night.

Here, capture keeps running on the device. Patients twenty-two through thirty-one are seen and captured offline, each buffer encrypted on the phone. At 12:50 the signal returns. Those ten visits sync, and ten clean English notes are waiting to review and sign over the lunch break. The doctor lost nothing but a slightly delayed review. That hour of dead signal didn't become an hour of pajama-time charting at 9pm.

That's the moat. Not that we "support offline," but that the worst hour of the clinic's network day is a non-event.

## Is offline capture secure, or is it a soft spot?

Fair question, and the honest answer is that offline is only safe if it's encrypted offline.

The risk people imagine is a phone full of unencrypted patient recordings. That's a real risk with a badly built offline mode. Ours avoids it two ways. First, the on-device buffer is encrypted with AES-256-GCM, so what's stored locally isn't readable without the key. Second, audio is processed and discarded once the note is drafted, so there's no growing audio archive on the device to begin with. Notes are encrypted at rest with AES-256 and belong to your practice; you can export or delete any visit at any time. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

This also matters under the DPDP Act 2023. The principle is purpose limitation and reasonable security: keep only what you need, protect what you keep. An offline buffer that's encrypted and short-lived fits that far better than a scribe that streams and stores. The full posture is on our [security page](../../security/), and the [data residency post](../ai-scribe-data-residency-india/) covers where the synced data lives.

## Does offline mode cost more, and how does the price compare?

No. Offline capture ships on every plan, from the entry Assist tier up; it's part of the baseline, not a premium add-on. The higher tiers add other capabilities (a bundled AI EHR and WhatsApp messaging at Copilot, an AI Receptionist and follow-ups at Autopilot), but the offline capture you're reading about here is in the plan you start on.

Practice Copilot starts at ₹1,599 per clinician per month ex-GST on the annual Assist plan, about ₹1,887 once you add 18% GST, with a 7-day free trial. The published India-native anchor, EkaScribe Pro, is ₹1,499 per doctor per month. The full ladder, with the with-GST math, is on the [India rate card](../ai-medical-scribe-price-india/) and the [pricing page](../../pricing/). For a tier-2 or tier-3 clinic, the offline behaviour is worth more than the price gap, because the alternative is losing notes on the days the network has a bad afternoon.

If you run a solo practice and want to see whether the monthly cost pays back against your patient volume, the [solo-doctor payback post](../ai-scribe-for-solo-doctors-india/) works the math against a 40-to-60-patient OPD day.

## How do you test offline capture before you commit?

Don't take our word for it. Break the connection on purpose.

During the 7-day free trial, run a real OPD morning, and at some point put the phone in airplane mode mid-visit. Keep seeing patients. Then turn the signal back on and watch the notes sync. That's the test that matters for a low-connectivity clinic, and it takes ten minutes to run. If a vendor's offline mode loses the visit, you'll know on day one instead of on the worst Saturday of the year.

When you want to see it on your own clinic's network conditions, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we'll show the airplane-mode test live. If the multilingual side is your bigger question, the [Hindi and Hinglish post](../ai-scribe-hindi-indian-languages/) shows a code-mixed consult becoming an English note, online or off.

---

## Hinglish In, English Notes Out: How Code-Mixing Is Handled
https://patientsquare.com/in/blog/ai-scribe-hindi-english-code-mixing/
Published 2026-05-19 · Tags: hinglish, code-mixing, multilingual, india

A worked example of a code-mixed Hinglish consult becoming a clean English SOAP note, and the plain rule behind it: input is multilingual, output is English.

Code-mixing, or Hinglish in north India, is switching languages within a single sentence: a Hindi clause, an English drug name, a Hindi clause again. It is how a huge share of Indian consults are actually conducted. AI Medical Scribe by Patient Square captures the mixed speech and writes the note in clean clinical English, so the record is usable even though the conversation was not in one language.

A lot of Indian consults aren't in Hindi or in English. They're in both, mid-sentence, with the drug name in English and the rest in Hindi. That's code-mixing, and it breaks ordinary transcription tools. AI Medical Scribe by Patient Square captures the mixed speech and hands back a clean clinical English note. The rule underneath is simple: the input can be Hinglish, the output is always English. Here's a worked example of that happening, on a different case than our [Hindi and languages post](../ai-scribe-hindi-indian-languages/) walks through.

> **Key takeaways**
>
> - The rule, stated plainly: input is multilingual (Hindi, Hinglish, regional), output is clean clinical English. Every note, no exceptions.
> - Code-switching mid-sentence is a known weak point for tools trained on one language. The English drug name inside a Hindi sentence is where they fail.
> - The note is the record; the audio isn't. Visit audio is processed in memory and discarded once the note is drafted. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - This post uses a fresh case (a monsoon fever consult), distinct from the diabetes example in the main languages post.

## What does a code-mixed consult sound like, really?

Here's a different scene from the one in our main languages post. A monsoon-season fever case, the kind every Indian OPD sees by the dozen from July. The exchange below is an illustration, not a real patient:

> **Doctor:** "Kitne din se fever hai? Aur body pain ke saath?"
> **Patient:** "Teen din se, doctor. Tez bukhar aata hai, phir thoda kam ho jaata hai. Body pain bahut hai, aur aankhon ke peeche dard hota hai. Platelet ka kuch problem to nahi?"
> **Doctor:** "Dengue ka season hai, isliye main ek CBC aur NS1 antigen test likh raha hoon. Abhi sirf paracetamol lijiye fever ke liye, koi aspirin ya ibuprofen nahi. Fluids zyada rakhiye. Agar platelet count kam aaya ya bleeding dikhe to turant aana."

Three turns, half a dozen language switches, and a clinical decision braided through it: a duration, a symptom cluster, two named investigations, a drug to take, two drugs to avoid, a red-flag safety net. A general Hindi transcriber would garble "CBC", "NS1 antigen", "paracetamol", "aspirin", "ibuprofen", and "platelet". A general English transcriber would drop the Hindi entirely and lose the history. Neither leaves you with a record you could sign.

## What does the note look like afterward?

Clean clinical English, structured, ready to review:

> **S:** Three days of intermittent high-grade fever with severe body ache and retro-orbital pain. Patient anxious about platelet count. Monsoon season.
> **O:** Febrile illness, clinical assessment pending labs.
> **A:** Acute febrile illness, dengue fever to be ruled out.
> **P:** Order CBC and NS1 antigen. Paracetamol for fever; avoid aspirin and ibuprofen. Advise increased oral fluids. Return immediately if platelet count falls or bleeding appears.

The patient asked about platelets in Hindi. The chart records "retro-orbital pain," "NS1 antigen," and "avoid aspirin and ibuprofen" in English. That inversion, Hinglish conversation in, English record out, is the whole job. It's what makes the note useful to a pathologist running the CBC, a TPA processing a claim, or a court that won't read Hinglish.

## What's the rule, stated plainly?

Input multilingual, output English. That's it, and it's worth saying without hedging.

You and your patient can speak Hindi, Hinglish, Tamil, Bengali, Marathi, whatever puts the consultation at ease. The scribe captures that. But the note it produces, the SOAP note, the ICD-10 suggestions, and the prescription draft, is always generated in clean clinical English. We don't produce a Hindi-language note, and we're explicit about that, because the record has a different audience than the conversation. The conversation belongs to the patient. The record goes to the referral specialist, the insurer, the medico-legal file, all of which run in English.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The structuring and the language conversion happen in the same step. You don't get a Hinglish transcript to clean up afterward. You get an English note to read and sign.

## Why do ordinary tools choke on Hinglish?

Because they were trained to listen in one language, and a real consult doesn't cooperate.

Code-switching, changing language within a single utterance, is a recognised hard problem in speech recognition. Models trained predominantly on one language lose accuracy on the "other" language the moment a speaker flips, and that's exactly where the clinically load-bearing words live: the English drug name in the Hindi sentence, the lab abbreviation, the dose. Research on Hindi-English code-switched speech, including efforts to build dedicated code-switched corpora, exists precisely because off-the-shelf monolingual models handle this so poorly.

So "supports Hindi" on a vendor's feature page is not the same claim as "handles a real Hinglish consult." Capturing clean Hindi audio and correctly transcribing "platelet count kam aaya to turant aana" are different engineering problems. The second one is the one that matters in your OPD, and it's the one we built for. If a vendor only advertises the first, test the second on day one of a trial.

## Does this work when the room is noisy or the signal drops?

Both are the real Indian OPD. Both have to work.

A crowded room with a relative answering half the questions is the hard case for any scribe, and it's where transcription quality separates products. And in tier-2 and tier-3 clinics, the connection itself isn't reliable. [Capture works offline](../ai-scribe-offline-low-connectivity/) with on-device encryption and syncs when the signal returns, so a dead tower during a monsoon-fever rush doesn't cost you the note. The language handling is identical offline; connectivity changes when the note is ready, not what it understands.

And the audio doesn't linger. Visit audio is processed in memory and discarded the moment the note is drafted, which is also the right answer under the DPDP Act 2023. There's no Hindi transcript and no recording archived anywhere. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## How do you test the Hinglish handling before you trust it?

On your own patients, with your own accents. A demo on a scripted sentence proves nothing.

Start your 7-day free trial, and run it on a real OPD session, the messier the better: a relative interrupting, a regional accent, a sentence that starts in Hindi and ends with a drug name in English. Then read the English notes and ask whether they're clean enough to sign without a rewrite, and whether the drug names and lab values survived the language switch intact. That's the only test that tells you anything. If the [India rate card](../ai-medical-scribe-price-india/) is your starting question instead, every number there is in rupees with GST shown.

When you want to see the Hinglish handling on your own consults, book a demo and bring your hardest code-mixed case.

---

## Ambient Clinical Documentation: What It Is and How It Works
https://patientsquare.com/us/blog/ambient-clinical-documentation/
Published 2026-05-19 · Updated 2026-07-22 · Tags: ambient, clinical-documentation, category

Ambient clinical documentation listens during the visit and writes the note for you. Here is how the technology works, where it fits, and what to ask.

Ambient clinical documentation is software that captures the conversation between clinician and patient during a visit and automatically drafts the clinical note, without any dictation, typing, or transcription step from the clinician. The draft appears for review shortly after the visit ends.

Ambient clinical documentation is software that listens to a patient visit and drafts the clinical note from what it heard. You see the patient normally, start a session, and get a structured note ready to review about two minutes after the visit ends. No dictating, no typing, no reconstructing the encounter from memory at 9pm.

The terminology is a mess right now. "Ambient" gets used to mean everything from passive voice capture to automated coding to AI clinical decision tools. This page covers what the technology actually does, how it works at the layer level, and what questions separate real tools from marketing language.

> **Key takeaways**
>
> - Ambient clinical documentation captures the visit conversation and drafts a structured note automatically; the clinician reviews and signs.
> - Primary-care physicians log a median 36.2 minutes of EHR time per 30-minute visit, per a 2023 JAMA Network Open study. The note now outlasts the appointment.
> - A 2026 JAMA study across five health systems found ambient tools saved about 16 minutes of documentation time per 8-hour shift.
> - Audio handling and language coverage are the two gaps that separate credible tools from underpowered ones.
> - "Ambient AI" as a category term collides with a security company's brand name; the precise healthcare term is ambient clinical documentation.

## How the technology works, layer by layer

Any ambient documentation tool runs through four layers. Knowing them makes vendor comparisons much faster.

First, audio capture. You start a session on a phone or laptop, get the patient's consent, and see the patient normally. The software captures the conversation with a microphone. No push-to-talk button, no dictation trigger, no workflow change between patients.

Second, speech recognition. The audio stream is transcribed, usually in near-real-time. The easy version of this problem is a quiet US exam room with one accent and clear audio. The hard version — the one that actually reflects most clinic days — is two people talking over each other, a relative answering half the questions, clinical terms dropped into everyday sentences, and the patient switching languages mid-thought.

Third, clinical structure. A language model takes the transcript and extracts what matters clinically, then formats it into a structured note. This is where products diverge most. Some stop at a basic SOAP note. Others draft downstream artifacts too: ICD-10 suggestions, a prescription draft, a follow-up plan. The quality of this layer is what you are actually testing during a trial.

Fourth, review and sign. The draft arrives for you to read. Nothing enters the chart automatically. You fix what's wrong, confirm what's right, and sign. This step is load-bearing. AI language models make plausible mistakes — a note that says "patient denies fever" when the transcript says "does she have a fever" is exactly the kind of structural error that slips past a quick read.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

## Where ambient clinical documentation fits in the documentation stack

Clinicians come to ambient documentation from three different starting points, and the value proposition looks different depending on where you're coming from.

If you're still typing during or after visits, a 2016 Annals of Internal Medicine time-motion study found nearly two hours of EHR and desk work for every hour of direct patient care. Ambient documentation is the biggest single lever available here, because it removes the typing step entirely, not just trims it.

If you're dictating, you've already moved from typing to talking, but you still reconstruct the encounter from memory after it ends. That narration step — usually five to ten minutes of speaking plus cleanup — is what ambient documentation removes. The note gets drafted from the actual conversation, not your recollection of it. Our [comparison of ambient documentation and dictation](../ambient-ai-vs-dictation/) goes deeper on the tradeoffs.

If you're using a human scribe, you already know the result is good documentation. The tension is cost and scheduling: a salary, hiring, and a third person in every room. Ambient documentation delivers a comparable note without the staffing dependency.

In all three cases, the shift is the same. The visit and the note happen at the same time instead of sequentially. That's the core change, and everything else follows from it.

## The evidence, honestly stated

This category has picked up peer-reviewed data in the last two years, and the picture is worth summarizing accurately.

A 2026 JAMA study tracked more than 1,800 clinicians using ambient tools across five academic health systems. It found about 16 minutes of documentation time saved per 8-hour shift and about 13 fewer minutes spent in the EHR, compared to matched controls. There was also a modest increase in patient visits seen per week, roughly half a visit more per clinician. The paper's framing was "modest reductions," which is the honest read.

A 2025 UCLA randomized trial measured about 41 fewer seconds per note for one tool. Across a 20-patient day that works out to roughly 14 minutes, or about 4.6 hours a month. The per-note number is small; the cumulative effect of 20 visits a day is not.

A 2025 JAMA Network Open study at Mass General Brigham tracked 1,400-plus physicians over 84 days and found burnout scores dropped from 52.6% to 30.7% — a 21.2 percentage point absolute reduction. The objective time savings are modest; the subjective wellbeing gains are notably larger. Researchers have flagged this gap as worth studying further. We covered the burnout evidence in more depth in our [charting time post](../reduce-charting-time-clinicians/).

Time and mood are only half the evidence, though. The other half is whether the draft is right, and here the data is sobering enough to keep you reading every note. A 2025 study in npj Digital Medicine (Asgari et al.) had clinicians annotate 12,999 sentences from AI-generated clinical notes and measured a 1.47% hallucination rate, where the model states something the visit didn't contain, and a 3.45% omission rate, where it drops something that mattered. Small percentages, but at 30 to 40 sentences a note across a full clinic day, they add up to real content you have to catch. The authors' point isn't that the tools are unsafe; it's that a fluent, confident draft can still be wrong in ways a fast read misses. That's exactly why the review step below is not a formality.

The fair summary: real time savings, modest in the objective data, larger in the wellbeing data, and a small but nonzero error rate that makes the physician's read non-negotiable. Run a trial on your own patient mix before taking any of these numbers at face value.

## The two things that vary most across products

After the core capture-and-draft pipeline, two capabilities differentiate tools in ways that matter clinically.

### Audio handling after the visit

What happens to the recording once the note is drafted? The answer varies by vendor, and the visit recording is among the most sensitive artifacts in healthcare. It contains everything that did not make the note.

Some vendors retain audio for days or weeks for model improvement, quality review, or dispute resolution. Some let practices opt out. Others are deliberately vague. For a visit that includes a mental health disclosure, a substance use conversation, or something a patient said off the record, "we keep it for 28 days" is not a neutral answer.

AI Medical Scribe by Patient Square processes visit audio in memory and discards it once the note is drafted. No audio archive exists on our side or the practice's. What survives is the note you reviewed and signed. Full posture is on the [security page](../../security/).

Ask every vendor this question before anything else: what happens to the audio, and when is it gone? Accept only a one-sentence answer with a specific timeline.

### Language coverage

Several popular US ambient documentation tools publish language support lists that name no Indian language. For the United States alone, that is a gap across tens of millions of patients whose primary language is not English. Across a global clinical base, it is a much larger one.

The technical difficulty scales with the complexity of the language environment. A quiet bilingual visit with consistent switching patterns is workable. A visit where the patient speaks Kannada to a family member, Hindi to the doctor, and English for drug names, all in the same sentence, is a genuinely hard transcription problem.

This is where testing on your actual patient mix in your actual clinic setting is the only honest evaluation. Runs with generic demo patients do not tell you what an ambient tool does with your 8am Thursday clinic.

## What ambient clinical documentation does not do

The category pillar should also say what the technology isn't, because several vendor pitches blur these lines.

Ambient documentation is not autonomous coding. The ICD-10 suggestions some tools produce are exactly that — suggestions for you to review. No ambient tool today submits codes to a payer without physician sign-off, and any pitch implying otherwise is either mistaken or dishonest.

It doesn't write orders. Lab orders, referrals, imaging requests — those aren't drafted by the ambient layer in most tools. Some vendors are experimenting with this. It's not the baseline product today.

It doesn't replace your EHR. Ambient tools sit alongside whatever EHR you already use. The note lands in a review interface, you approve it, you move it into your chart. That's not a complaint about ambient tools — EHR-agnostic is usually better than locked-in. But "EHR replacement" is a different pitch entirely.

And it doesn't take the clinical judgment off your plate. The scribe drafts. You're still the author of the record, legally and clinically. The two minutes of review aren't optional. What the product should do is make those two minutes count — give you a solid draft so you're confirming and correcting, not building from scratch.

## A term you'll see misused: "ambient AI"

One naming collision is worth flagging before you start shopping.

"Ambient AI" is a registered company name in the security industry, unrelated to healthcare documentation. When clinicians search "ambient AI for documentation" they sometimes land on content about physical-space security sensors. This is why the precise healthcare term is ambient clinical documentation or, less formally, ambient documentation or ambient scribing.

"Ambient clinical intelligence" is a phrase trademarked by one specific clinical documentation vendor. It is their brand, not a generic category name, though it sometimes gets used that way in press coverage.

For search purposes and for vendor conversations, ambient clinical documentation is the term to use. It describes the technology accurately and does not collide with unrelated product categories.

## How to run a real evaluation

Every demo runs on ideal conditions. Your clinic is not ideal conditions.

Pull your five hardest visit types from last week: the patient who talks in circles, the one with three complaints, the one whose family member does most of the answering, the one with an accent your autocomplete already gets wrong, the one whose visit went somewhere unexpected. Run those with the ambient tool. Read every draft carefully.

A few specific things to check. Does the note capture what happened, or what typically happens in this kind of visit? Does the assessment match your clinical reasoning, or does it reflect the most likely diagnosis given the chief complaint? Are medication names, dosages, and frequencies right? Is anything in the note that wasn't actually said?

Pricing is secondary to this. A tool that costs twice as much and lets you sign in 90 seconds is cheaper than one that takes five minutes to fix per note. Do the arithmetic on your actual volume.

AI Medical Scribe by Patient Square includes an assisted 7-day trial after workspace setup. That's enough time for a real clinic week with real patients. The [pricing page](../../pricing/) has the full rate structure; no sales call is needed to read it.

## Five questions to ask any vendor before you sign

Before the demo, before the contract.

One: what happens to the visit audio, and when is it deleted? Accept only a one-sentence answer with a specific timeline. "We process it and discard it when the note is drafted" is an answer. "We have robust security practices" is not.

Two: which languages does the tool actually handle? Test with your patient mix, not a demo patient. The sales deck answer and the 8am Thursday OPD answer are often different.

Three: what's in the draft — SOAP note only, or also ICD-10 suggestions and a prescription draft? If there's an Rx draft, does it include a safety check, or just text? Those are different products.

Four: does it work with any EHR? EHR-agnostic tools take a day to set up. Tools that require specific integrations take months and often cost more. Get clear on this before procurement.

Five: what's the price after year one? Launch rates and renewal rates frequently diverge. Get the full rate ladder in writing. Ours is published on the [pricing page](../../pricing/).

A tool that answers all five clearly may be worth a controlled evaluation. Review the [published product scope](/us/products/practice-copilot/) first, then read every draft closely during any approved evaluation.

---

## AI Medical Scribe for a Solo Doctor in India: Does ₹1,599 Pay Off?
https://patientsquare.com/in/blog/ai-scribe-for-solo-doctors-india/
Published 2026-05-18 · Updated 2026-07-22 · Tags: solo-doctor, pricing, india, roi

The honest payback math for a solo doctor in India: what ₹1,599 a month buys against a 40 to 60-patient OPD day, with ex-GST and with-GST figures.

For a busy solo OPD, usually yes. The AI Medical Scribe module of Practice Copilot starts from ₹1,599 per month ex-GST on the annual Assist plan, about ₹53 a calendar day. Against a 40 to 60-patient day, even saving two to three minutes of charting per patient returns far more clinician time than the daily cost. The catch is honest: it pays off when your volume is high enough that documentation is genuinely eating your evenings.

Short answer for a solo doctor: from ₹1,599 a month ex-GST works out to about ₹53 a calendar day. Against a 40 to 60-patient OPD day, that's a small line item to recover an hour of evening charting. It pays off when your volume is high. It doesn't do much for you if you see eight relaxed patients a day. Below is the actual arithmetic, ex-GST and with GST, so you can decide on your numbers instead of ours.

> **Key takeaways**
>
> - From ₹1,599/month ex-GST is about ₹53 per calendar day, or roughly ₹61 across 26 working days; about ₹1,887 and ₹73/working day once you add 18% GST.
> - EkaScribe Pro, the published India-native anchor, is ₹1,499/month, about ₹50 a calendar day.
> - The payback is volume-driven: at a 40 to 60-patient day, saving two to three minutes of charting per patient dwarfs the daily cost.
> - The scribe is the entry Assist plan; a bundled AI EHR, WhatsApp, and receptionist and follow-up automation arrive on the Copilot and Autopilot tiers. A 7-day trial with no daily cap lets you check the math yourself.

## What does ₹1,599 actually come to per day?

Do the division. That's where the decision really gets made.

From ₹1,599 per month ex-GST is about ₹53 per calendar day across a 30-day month. Count only the days you run OPD, say 26, and it's about ₹61 a working day. Add 18% GST and the month comes to about ₹1,887, roughly ₹63 per calendar day or ₹73 per working day. EkaScribe Pro at ₹1,499 a month sits near ₹50 a calendar day.

So you're weighing a tool worth somewhere between ₹53 and ₹73 on a day you work. Less than one consultation fee in most practices. Price isn't the question. What matters is whether the time it hands back is worth more than that, and for a solo doctor that comes down to volume, full stop.

## Does the payback work on a 40 to 60-patient OPD day?

Here's where the real numbers are. Take a solo physician running a 50-patient day. A BMJ Open review of 28.5 million consultations across 67 countries put India's average primary-care consult at about two minutes, among the shortest measured anywhere. At that pace you cannot also type a complete, structured English note per patient during the visit. So the notes get deferred, and they pile up. A stack of fifty charts waiting to be reconstructed from memory after the last patient leaves.

Say an ambient scribe saves you a conservative two minutes per patient: the deferred typing and the cleanup that comes after. Across 50 patients that's 100 minutes a day. Call it an hour and forty minutes of your evening, recovered for about ₹61 ex-GST on a working day. You don't have to value your time aggressively for that trade to come out lopsided. Even on the three patients a day whose note would otherwise have been skipped or scrawled, the defensible-record value alone covers the line item.

Now run it the other way. See twelve patients a day at a leisurely pace, caught up on charting by the time you lock the clinic, and the savings shrink. The case gets weaker. We'd rather you know that going in. A scribe is a volume tool. The busier your OPD, the harder the math tips in its favour.

## What does a solo doctor get for the ₹1,599, exactly?

On the entry Assist plan you get the scribe, the piece that solves the documentation problem. The plans step up from there: Copilot adds a bundled AI EHR and WhatsApp messaging, and Autopilot layers on an AI receptionist plus follow-up automation. A solo doctor who only needs the notes handled can stay on Assist.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription draft reflects what you said in the visit; it does not screen for interactions or dosing. You are the safety check, reviewing the draft against the chart, adjusting the dose, and signing, exactly as you do today. Capture works in English, Hindi, Hinglish, and 20-plus Indian languages, with the note always returned in clean clinical English. If your clinic's signal drops mid-OPD, [capture keeps working offline](../ai-scribe-offline-low-connectivity/) with on-device encryption and syncs later.

For a solo doctor, the no-gating part is the bit that matters. You get the same prescription drafting and the same language handling a large clinic gets, at the solo seat price. The full rate ladder, with the with-GST math, is on the [India rate card](../ai-medical-scribe-price-india/) and the [pricing page](../../pricing/).

## How does the solo price compare to the alternatives?

Price is only half the decision, so keep this part short.

EkaScribe Pro is ₹1,499 per doctor per month, with an annual plan near ₹12,492 a year and a free tier capped at five consultations a day. It's India-native and, the honest concession, it has live ABDM integration that we don't yet; ABDM is on our roadmap. Augnito is sales-led and doesn't publish a transparent self-serve rupee price, so a solo doctor can't even see a number without a call. Our Assist plan starts from ₹1,599 ex-GST with a published ladder and a 7-day trial that runs the real product without a daily cap.

If live ABDM linking is a today requirement, EkaScribe is the honest pick, and the [EkaScribe alternatives post](../ekascribe-alternatives-india/) walks through that trade-off. If what you want is a published ladder you can read without a sales call, a prescription draft you review and sign, and audio that's never stored, the Assist seat is a strong daily driver, with a clear upgrade path once you want an EHR or messaging bundled in. The [India comparison](../india-ai-scribe-comparison/) lines all three up. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## How should a solo doctor test the payback?

Don't trust a worked example, including this one. Run your own.

Start your 7-day free trial, with no daily cap, and use it on a normal OPD day. Count roughly how many minutes of charting you save per patient. Then check whether the English notes are clean enough to sign without a rewrite. Multiply the minutes by your real patient count. If the time you get back across a 40 to 60-patient day isn't worth about ₹53 ex-GST, don't subscribe. We mean that. The trial exists so the math is yours, run on your clinic and not ours.

When you want to see it on your own consults before deciding, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we'll run it on the kind of OPD day you actually have.

---

## Is ChatGPT HIPAA-Compliant for Doctors? (2026)
https://patientsquare.com/us/blog/is-chatgpt-hipaa-compliant-for-doctors/
Published 2026-05-18 · Updated 2026-08-31 · Tags: hipaa, chatgpt, security

Standard ChatGPT accounts are not HIPAA eligible. See which OpenAI products can get a BAA, what functionality it covers, and what clinicians should verify.

Not by default. Standard consumer ChatGPT accounts are not HIPAA eligible. ChatGPT for Healthcare and other HIPAA-eligible OpenAI products can support HIPAA-compliant use only under an applicable BAA and within covered functionality; ChatGPT Business is not eligible for a BAA, while qualifying Enterprise and Edu customers must contact OpenAI.

A standard ChatGPT account, the one a colleague might use for emails, is not a HIPAA-eligible workspace for PHI. ChatGPT Business is not eligible for a BAA. If you need to enter patient information, use an eligible OpenAI product only after the applicable BAA and covered functionality are confirmed.

OpenAI has built healthcare-specific products in 2026, and the picture is more nuanced than "ChatGPT bad." But the nuances do not change the situation for most individual physicians. Here is what is actually true.

> **Key takeaways**
>
> - Standard consumer accounts and ChatGPT Business are not HIPAA eligible for PHI use.
> - OpenAI's eligible list includes ChatGPT for Healthcare, Enterprise with Regulated Workspace, FedRAMP, Clinicians, and modified-retention API products.
> - Eligible individual clinicians use a separate in-product BAA flow for ChatGPT for Clinicians.
> - A signed BAA is necessary but not sufficient: data residency, audit logs, and access controls are also part of a HIPAA-compliant implementation.
> - Purpose-built AI scribes can provide a narrower documentation workflow with explicit retention controls and a BAA.

## What OpenAI actually offers by tier

OpenAI's current HIPAA-eligible list spans several products. The account name alone is not enough; eligibility, the BAA, and covered functionality all matter.

**Standard consumer accounts and ChatGPT Business:** These are not HIPAA eligible for PHI use. OpenAI's BAA guidance explicitly excludes ChatGPT Business.

**ChatGPT for Healthcare (enterprise, launched January 8, 2026):** OpenAI's hospital-grade product. Includes a BAA, customer-managed encryption keys, data residency options, and audit logs. Deployed at Stanford Medicine Children's Health, UCSF, HCA Healthcare, Cedars-Sinai, Memorial Sloan Kettering, and others. Getting access means going through enterprise sales. It is not available via standard account signup.

**ChatGPT for Clinicians (individual, launched April 2026):** Free for verified US physicians, NPs, PAs, and pharmacists. It supports clinical literature search, prior authorization drafts, CME tracking, and documentation support. OpenAI lists it as HIPAA eligible and directs eligible individual clinicians to a separate in-product BAA flow.

**Enterprise, Edu, and FedRAMP:** OpenAI's current eligible-product list includes Enterprise with Regulated Workspace and ChatGPT FedRAMP. Sales-managed Enterprise and Edu customers contact OpenAI about a BAA. Administrators must keep PHI within covered functionality.

**OpenAI API:** Developers can request a BAA at baa@openai.com. HIPAA eligibility generally requires the organization to be provisioned with Modified Retention, and only covered endpoints and services may process PHI.

| Product or account | HIPAA eligibility | BAA path |
|---|---|---|
| Standard consumer account | No | None |
| ChatGPT Business | No | None |
| ChatGPT for Clinicians | Yes, for eligible clinicians | Separate in-product flow |
| ChatGPT for Healthcare | Yes | Enterprise agreement |
| Enterprise / Edu | Qualifying sales-managed customers | Contact OpenAI sales |
| API with Modified Retention | Yes, for covered services | Request at baa@openai.com |

## ChatGPT for Clinicians: what it is, what it is not

OpenAI announced ChatGPT for Clinicians on April 22–23, 2026. The clinical validation involved physician advisors testing the system across nearly 7,000 conversations on clinical care, documentation, and research. The advisors rated 99.6% of responses as safe and accurate. That figure comes from OpenAI's own testing process, not an independent clinical trial.

It covers research queries against peer-reviewed literature with real-time citations, prior authorization drafts, patient instruction suggestions, and documentation assistance. Eligible individual clinicians can use the separate in-product BAA flow. That does not turn every feature into a PHI workflow: the account must be eligible, the BAA must apply, and the functionality must be covered.

That distinction matters. A tool can be designed for clinicians and still not be ready to handle patient records in the way a HIPAA audit would require.

## Why a BAA alone is not enough

Even on the tiers where OpenAI does offer a BAA, the agreement covers OpenAI's handling of the data. It does not automatically make your implementation compliant. A ReframePractice analysis of the enterprise tier put it clearly: a compliant setup also requires the right account configuration, audit logging, documented workflows that limit PHI exposure, and workforce training.

The audit question is not just "did you sign a BAA?" It is: Where does the data physically sit? Who can access the conversation logs? How do you prove no PHI leaves your environment? These are engineering and governance questions that a signed agreement does not answer by itself.

## What makes a documentation tool actually HIPAA-appropriate

Clinicians who tried ChatGPT for notes usually landed there because they needed a faster way to document, not because they needed a general-purpose AI assistant. Those are different problems.

A purpose-built AI scribe handles PHI differently by design. Audio is processed in memory, never written to disk, and discarded once the note is generated. There is nothing stored to breach after the visit ends. A BAA is standard for every customer, regardless of practice size, not something you have to negotiate your way into. The workflow is closed: the scribe runs during the visit, the draft appears about two minutes after the patient leaves, and you review and sign. Nothing passes through a general-purpose chat interface.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. Audio is processed in memory and never stored. Safeguards are HIPAA compliant, and a BAA is available for every customer. SOC 2 Type II audit is underway. You can read the specifics at [our security page](../../security/).

## When ChatGPT for Healthcare actually makes sense

This is the honest part. OpenAI's enterprise product is not a toy.

If you work inside a hospital system that has signed an enterprise agreement with OpenAI, that institution has already done the governance work: BAA, data residency, audit logs, workforce policy. In that context, ChatGPT for Healthcare is a real tool with real compliance scaffolding. Stanford Medicine and UCSF are not naive about data security.

If you are a physician at one of those institutions, using ChatGPT through the institutional deployment with PHI can be appropriate. The institutional IT and compliance teams have made that call.

If you are an independent practitioner in a small or mid-size practice, a standard ChatGPT login is still the wrong place for PHI. Eligible clinicians can evaluate ChatGPT for Clinicians and its in-product BAA flow, then verify that the specific functionality they plan to use is covered.

## The practical question

The physician who tried ChatGPT for notes usually did it late on a Tuesday, with a stack of charts and no documentation tool that actually helped. That impulse is understandable. The gap is real.

You can close that gap with a general-purpose chat interface or with a tool built for the specific problem. The risk profiles, workflows, and HIPAA postures are different.

If you want to see what a purpose-built documentation workflow looks like against your specific visit type, our [HIPAA BAA and consent guide](../ai-scribe-hipaa-baa-consent/) walks through what a compliant AI scribe relationship requires, and our [security checklist for AI scribes](../ai-scribe-security-checklist/) gives you the twelve questions to ask any vendor before signing. We offer a 7-day trial — run it on a real clinic week, look at the note quality, and check it against what you were doing before.

---

## Can Better Notes Cut Claim Denials? The Documentation Angle
https://patientsquare.com/us/blog/ai-scribe-claim-denials-documentation/
Published 2026-05-15 · Tags: claim-denials, documentation, revenue-cycle, ai-scribe

Initial claim denials hit 11.81% in 2024, and weak documentation is a driver. How note quality affects denials, and the honest limit of what a scribe fixes.

Initial denials hit 11.81% of claims in 2024, up 2.4% from the prior year, according to Kodiak Solutions' analysis of more than 2,100 hospitals and 300,000 physicians. Roughly one in eight claims now bounces on first submission, and the categories tied to medical necessity and requests for more information are rising.

Better notes can cut the denials that turn on documentation. Only those. Initial claim denials hit 11.81% in 2024, and two of the fastest-growing categories, medical necessity and requests for more information, trace straight back to whether the record supports the claim. A complete, legible note gives your biller what a payer asks for. We'll be precise here about what a scribe touches and what it doesn't, because overclaiming on revenue is where this topic usually goes wrong.

One thing to settle up front: an AI scribe is not a billing tool. It doesn't submit claims, it doesn't adjudicate them, and it never sees your clearinghouse. What it does is improve the note that every one of those downstream steps depends on. Real lever, narrow one.

> **Key takeaways**
>
> - Initial denials hit 11.81% of claims in 2024, up 2.4%, per Kodiak Solutions (2,100+ hospitals, 300,000 physicians). About 1 in 8 claims bounces first time.
> - Two rising denial categories, medical necessity and requests for more information, are documentation-dependent.
> - A better note helps the documentation-driven denials only; it does nothing for eligibility, authorization, or timely-filing denials.
> - An AI scribe improves the note, not the billing workflow. It does not submit, code, or integrate with claims systems.

## How big is the claim-denial problem in 2024?

Worse, and the numbers come first-party from a large dataset.

Kodiak Solutions, analyzing claims from more than 2,100 hospitals and 300,000 physicians, reported that the initial denial rate rose to 11.81% of claims in 2024, an increase of 2.4% over the prior year. Roughly one in eight claims now gets denied on first submission. That's not the final write-off rate. Plenty of denials get overturned. But each one is rework, delay, and cost before the money ever lands.

What's driving the increase matters for our question. Kodiak found that even as providers cut authorization-related denials by 7.7%, denials tied to medical necessity and requests for more information rose by 5% and 5.4% respectively, more than making up the difference. Those two categories are the documentation-sensitive ones. A payer questioning medical necessity or asking for more information is, in effect, saying the record didn't make the case on its own.

## Which denials does documentation actually affect?

Not all of them. This is the distinction that keeps the claim honest.

| Denial type | Documentation-driven? | Can a better note help? |
|---|---|---|
| Medical necessity | Yes | Yes, a note that captures clinical justification |
| Request for more information | Yes | Yes, a complete note answers the question upfront |
| Insufficient documentation | Yes | Yes, directly |
| Eligibility / coverage | No | No, that's a front-desk/verification issue |
| Prior authorization | No | No, that's a process step before the visit |
| Timely filing | No | No, that's a submission-deadline failure |

The pattern is simple: documentation helps where the note is the evidence, and does nothing where the failure happened somewhere else in the process. If your denials are mostly eligibility and authorization, a better note won't move your numbers, fix the front-desk and pre-auth workflow instead. If they're medical necessity and information requests, the note is squarely in play.

## How does a better note reduce documentation-driven denials?

By handing the biller and the payer the clinical story, complete and legible, the first time.

A denial for medical necessity or a request for more information is usually a gap. The claim asserted something the record didn't fully support, or the documentation was too thin to stand on its own. The fix sits upstream: a note that captures the clinical reasoning, the relevant findings, and the plan clearly enough that the justification is visible without an appeal. When the note is complete, the coder has what they need to bill it cleanly. And if a payer does push back, the record is there to defend it.

This is where an ambient scribe earns its keep, and the mechanism is worth stating exactly. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. A note written at consultation pace, while the details are still fresh, tends to be more complete than one reconstructed from memory at 9pm. Completeness is exactly what the documentation-driven denial turns on. And the ICD-10 suggestions are just that, suggestions for your coder to confirm, not a coding engine. The note quality that makes this work is something you can grade yourself with our [SOAP-note rubric](../ai-scribe-soap-note-quality/), and the buyer's view is in [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/).

## What a scribe does not do for your denials

This is the part vendors blur, so here's the boundary drawn plainly.

It doesn't submit or adjudicate claims. AI Medical Scribe by Patient Square has no connection to your billing system, clearinghouse, or payer. It drafts notes, and your existing revenue-cycle process does the rest.

Coding isn't its job either. The ICD-10 suggestions speed your coder up; they don't replace one. A scribe that claims to "code your bills" is overselling, and we make that distinction at length in [how accurate are AI medical scribes](../ai-scribe-accuracy-what-to-expect/).

Then there are the process denials, which it can't touch. Eligibility, authorization, and timely-filing denials are workflow failures upstream or downstream of the note. A better note won't move them, and we won't pretend it can.

So the honest framing is narrow. An AI scribe improves documentation, documentation is a growing driver of denials, and a more complete note is easier to bill and to defend. That's the lever. It's not a revenue-cycle platform, so don't buy it as one.

## See the note quality before you bank on the billing benefit

The denials benefit is downstream of one thing: whether the note is actually more complete on your visits. That's testable.

<a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">Compare the options</a> to see a structured note appear about two minutes after a sample visit, then run the 7-day free trial and check whether your notes come out more complete than your current end-of-day reconstructions. If they do, the documentation-driven denials are the ones that benefit. For the time-and-money side, see [the real ROI of an AI scribe](../ai-scribe-roi-calculator-guide/); for the after-hours angle that ties into note completeness, [beating pajama time](../ai-scribe-pajama-time/); and for the full documentation-burden picture, the [pillar on cutting charting time](../reduce-charting-time-clinicians/). The receipts on security and data handling are on our [security page](../../security/).

---

## Prescription Software for Doctors in India: 2026 Landscape
https://patientsquare.com/in/blog/prescription-software-for-doctors-india/
Published 2026-05-15 · Updated 2026-10-04 · Tags: prescription, rx, india, software, solo-gp

A doctor-facing look at India's e-prescription software in 2026: what each tool does, where the safety gaps are, and when an Rx draft layer fits.

Electronic prescription software lets a doctor generate a typed or AI-drafted prescription instead of handwriting it. At the basic end it is a template that populates drug name, dose, and instructions. More sophisticated tools attach a safety screen that checks interactions and flags renal or pregnancy concerns before you sign. None of the Indian tools currently route prescriptions directly to a pharmacy.

India's prescription software market in 2026 is not one category. It's three distinct things wearing the same label. There are full clinic-management suites that include a prescription module. There are dictation tools that transcribe what you say into a drug list. And there are ambient scribes that draft the prescription from the conversation for you to review and sign. Buying the wrong category means paying for features you don't need while the actual problem, handwritten prescriptions that are slow, illegible, and slow to write, stays unsolved.

> **Key takeaways**
>
> - India's "prescription software" market splits into three types: full EMR with Rx modules, dictation tools, and ambient scribes. They solve different problems.
> - No Indian tool currently sends prescriptions to a pharmacy; digital Rx here means a typed or printed prescription the patient takes to a chemist.
> - Drafting a prescription and screening it for interactions are two different things. Most tools draft; almost none screen. The interaction, dose, and contraindication check stays with the prescriber.
> - DPDP Act 2023 makes prescription data a Data Fiduciary obligation. Ask every vendor whether audio is stored and where prescription text lives.
> - AI Medical Scribe by Patient Square drafts the Rx during the visit for you to review and sign; it doesn't run an automated interaction check, and the clinical call stays yours. From ₹1,599/month ex-GST on annual billing (plus GST), bundling scribe plus practice tools, 7-day free trial.

_Sources: Irving et al., BMJ Open 2017; AI Medical Scribe by Patient Square product facts._

## What "prescription software" actually means in India

The label covers a wide range. At the lowest end, it is a fillable template on a tablet: you type the drug and dose and print it. One step up is a dictation tool that transcribes your voice into a prescription. A level above that is an ambient scribe that drafts the prescription, mid-consult, from the conversation you are already having, then hands you the draft to review and sign.

The terminology also drifts. "E-prescription," "digital prescription," "Rx software," and "online prescription software" are used interchangeably by vendors even when the products are doing fundamentally different things. What they all share is that no Indian tool in 2026 routes the prescription electronically to a pharmacy. That is an important distinction from how e-prescribing works in the US or UK. Here, digital prescription software generates a typed or printed document the patient carries to the chemist. The value is legibility and time, not transmission.

This matters practically. If you are comparing products and a vendor says "e-prescribing," ask what that means. In the Indian context it almost certainly means "we generate a digital Rx" not "we send it to a pharmacy." If they do claim pharmacy transmission, get the specifics.

## The three types of tools and when each fits

### Full clinic-management system with Rx module

Tools like HealthPlix and Practo Ray include prescription management as one feature inside a larger clinic suite. You get billing, pharmacy inventory, appointments, and the prescription in one place. The prescription module is form-driven: you search for a drug, fill the fields, and print.

This is the right choice when your practice needs billing and dispensing to live in the same system as the clinical record. HealthPlix, which publishes its prices first-party at ₹11,999 per year (Pro) and ₹17,999 per year (Elite), includes drug-drug interaction (DDI) alerts as a named feature. [Practo Ray's published plans](https://www.practo.com/providers/clinics/ray/plans) list CM Atom at ₹999 per month and Clinic Management at ₹1,499 per month on a one-year plan; confirm which prescription, billing, and support features each quote includes.

Where these tools fall short for documentation: you do the typing. The prescription module does not listen to your consult and draft from it. In a 2-minute OPD, every second spent on a keyboard matters.

### Dictation and voice-to-text tools

Augnito Spectra is the main standalone dictation product in India. You dictate your prescription; the tool transcribes and structures it. It is useful if you are faster speaking than typing, particularly for doctors comfortable dictating in a specific clinical format. Augnito does not publish a website price (sales-gated); the App Store India listing shows in-app purchases at ₹1,199, ₹3,299, and ₹11,900 with billing periods not labeled. It offers a 7-day trial.

The limitation is that dictation is transcription, not drafting. You say the drug name; it writes what you said. There is no ambient listening that extracts a drug plan from a natural conversation, no safety screen running on the output, and no SOAP note wrapped around it.

### Ambient scribes with integrated Rx drafting

This is where the category gets interesting for a solo GP managing a heavy daily schedule. An ambient scribe listens during the consultation and, when the visit ends, hands back a full SOAP note, ICD-10 suggestions, and a prescription draft. You did not dictate; you just had the consult the way you always do. EkaScribe (by eka.care) and AI Medical Scribe by Patient Square both sit in this category.

EkaScribe is ₹1,499 per doctor per month (Pro), with a free tier capped at 5 consultations per day. It names 20+ Indian languages for input, including Hindi, Bengali, Tamil, and Telugu, and integrates with the eka.care platform, which has live ABDM/ABHA workflows. On prescription safety, EkaScribe does not headline a specific drug safety screener on its pricing page.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, builds a live transcript as you speak and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft the moment the visit ends, ready to review and sign.

## How the tool handles your two-minute consult

Think through the actual mechanics of a busy Tuesday. You see 40 patients. The consult itself is maybe 90 to 120 seconds. The handwriting, or the typing, happens on top of that. In a clinic running that density, any step that interrupts the consult to demand keyboard attention is a step that compounds into 40 extra minutes by evening.

An ambient scribe removes the keyboard from the loop. You speak with the patient; the draft appears after they leave. You review it, make any adjustments, sign it. The prescription text was drafted from what you actually said in the visit, not from a form you filled.

That architecture also has a data-handling implication under the [DPDP Act 2023](../dpdp-act-clinics-guide/). Prescription data is personal health data under DPDP. If a tool stores audio of your consultation on a remote server, that audio contains the prescription discussion plus everything else the patient said. Processing it with consent-first, purpose-limited handling is now a legal obligation, not a product nicety. Ask every vendor: is audio retained, and if so, where and for how long?

## Where the safety question lives

This is the part of the prescription-software conversation that most vendor pages skip.

A language model can draft a prescription. It can also draft one with a dangerous drug combination, an inappropriate renal dose, or a drug contraindicated in pregnancy. The AI does not inherently know your patient's creatinine or whether she is 8 weeks pregnant. A scribe that drafts an Rx is not making a safety judgment; it's turning what you said into a draft. The system is assuming you will catch a problem, because you are the one who should.

That's the honest posture, and it's the one our tool takes. The prescription is a draft, and the safety check is the clinician reviewing it, the same review you already do before signing a paper script. We don't run an automated interaction, renal, or pregnancy screen on the draft, and we'd be wary of any scribe that implies a language model has made those calls for you. What the draft saves you is the writing, not the thinking.

So the question worth asking a vendor isn't "does it use AI?" It's "what does the tool actually decide, and what stays with me?" A good answer keeps the prescribing judgment with the doctor.

## Comparison: what each type actually does

| | Full EMR + Rx module (e.g. HealthPlix) | Dictation (e.g. Augnito Spectra) | Ambient scribe (AI Medical Scribe by Patient Square) |
|---|---|---|---|
| **How Rx is generated** | You type into a form | You dictate the drug list | Drafted from the consult conversation |
| **Listens during visit** | No | You speak directly to tool | Yes, ambient |
| **SOAP note alongside Rx** | EMR notes (you type) | No | Yes, same pass |
| **Rx safety check** | DDI alerts (HealthPlix) | Not headlined | None automated; you review and sign the draft |
| **ICD-10 suggestions** | Not headlined as scribe feature | No | Yes (suggestions, not a coding engine) |
| **Audio stored?** | n/a | Per vendor policy | Live consultation audio is processed in memory and discarded at note draft; uploaded recordings use a separate retention mode with explicit consent |
| **ABDM** | HealthPlix: yes (live) | Dictation-focused | Roadmap (not shipped) |
| **Published India price** | ₹11,999–17,999/yr (HealthPlix) | App Store IAPs, period unlabeled | From ₹1,599/mo annual, ex-GST; scribe + practice tools bundled |
| **Trial** | Demo-led | 7-day | Assisted 7-day |

The table uses first-party vendor pages, with pricing rechecked in October 2026. HealthPlix and EkaScribe figures come from their published pricing. Augnito prices come from the App Store India listing. Practo Ray publishes [CM Atom and Clinic Management plan prices](https://www.practo.com/providers/clinics/ray/plans), but its plans are outside this three-column category comparison.

When should you pick the full EMR over a scribe? When billing, pharmacy, inventory, or live ABDM linking is the actual problem. A scribe that drafts a better prescription does not fix a broken billing workflow. Those are different fires. When your evenings are going to handwriting, not collections, the documentation layer is the right lever.

## Our Rx draft: what it does and what it deliberately doesn't

We think the most useful thing a prescription tool can do is take the writing off your plate: draft the Rx from the consult you already had, so you're editing a starting point instead of typing one from scratch. That is the job AI Medical Scribe by Patient Square is built for. What it deliberately doesn't do is decide anything clinical for you.

You run the visit the way you normally would. The scribe listens. After the patient leaves, you get a SOAP note with ICD-10 suggestions and a prescription draft built from what you said. You review the drugs, doses, and instructions, adjust anything off, and sign. That review is the safety check, the same one you already run on a handwritten script. The scribe doesn't run an automated interaction, renal, or pregnancy screen on the draft, and it doesn't hold the prescription up or wave it through. The prescribing call is yours, start to finish.

What it does not do is transmit the prescription anywhere. You review it, adjust it, and sign it. How it reaches the chemist is your call, paper or print. We draft; we do not dispense.

Visit audio is processed in memory and discarded when the note is created. No recording on a server. The prescription text stays in the note record, which belongs to your practice: you can export or delete any visit at any time. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On pricing: the Assist plan starts from ₹1,599 per clinician per month on annual billing, ex-GST, bundling the scribe with practice tools rather than billing an EMR separately. Add 18% GST on top, so about ₹1,887 a month all-in. The Rx drafting and the ICD-10 suggestions are in from that entry plan; moving up to Copilot (₹2,399 ex-GST) adds the bundled AI Copilot EHR and WhatsApp messaging, so the higher tiers do add features rather than just volume. There is a 7-day free trial through the India signup page.

On ABDM: we have it on the roadmap; it is not shipped. We won't mark a roadmap feature as available. If live ABDM linking is something your practice needs today, EkaScribe's broader eka.care platform has it, and the [best AI medical scribes comparison for India](../india-ai-scribe-comparison/) gives a fuller picture of where each tool sits.

The next step is to run the scribe on an actual clinic day before you decide. If you want to see where your own consults land as notes and prescriptions, book a short demo or <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>; the seven days begin after your workspace is ready.

A prescription tool you trust is one you have watched handle your patients, your drug choices, your accents. No scorecard replaces that Tuesday.

---

## The 2026 Evidence on AI Medical Scribes and Burnout
https://patientsquare.com/us/blog/ai-scribe-burnout-evidence/
Published 2026-05-14 · Tags: burnout, evidence, ambient-ai, studies

A digest of the latest AI-scribe burnout studies, including the April 2026 five-system trial, and the gap between modest time saved and large well-being gains.

It says the well-being effect is real but the time-saved effect is modest, and the two don't fully match. An April 2026 JAMA study across five health systems found only about 16 minutes saved per 8 hours of care, yet other 2025 studies found large drops in burnout. The subjective benefit outruns the objective minutes.

The 2026 evidence on AI scribes and burnout points to a genuine puzzle: the time saved is modest, but the well-being gains are large. An April 2026 JAMA study across five health systems measured only about 16 minutes saved per eight hours of care, yet a 2025 study found a 21.2% absolute drop in burnout at one site. The minutes don't fully explain the mood. That gap is the most interesting finding in the field right now, and it changes how you should read every burnout claim.

This is the evidence digest. Want the straight yes-or-no? Our companion post, [do AI scribes reduce burnout](../do-ai-scribes-reduce-burnout/), handles that. Here we go deeper into the specific 2025-2026 studies, what each one actually measured, and why the objective and subjective numbers disagree.

> **Key takeaways**
>
> - An April 2026 JAMA study across five health systems found ~16 minutes of documentation time saved per 8 hours of care, and called it "modest."
> - A 2025 JAMA Network Open study reported a 21.2% absolute burnout reduction over 84 days at Mass General Brigham, with Emory seeing a sharp well-being rise.
> - The puzzle: well-being improved more than the modest time savings would predict. The subjective benefit outruns the objective minutes.
> - The honest read: strong on time saved, promising on burnout, not yet conclusive on durable cause.

1,800 clinicians studied' },
]} />

## What did the April 2026 study actually measure?

The newest and largest read is a reality check, not a hype piece.

Published in JAMA on April 1, 2026, the study tracked more than 1,800 clinicians using ambient AI scribes against nearly 6,800 controls across five academic health systems from 2023 to 2025. The objective result was deliberately modest: about 16 minutes of documentation time saved and 13 fewer minutes in the EHR per eight hours of patient care, with no significant change in after-hours EHR work. The recovered time amounted to roughly half an extra patient visit a week. The researchers, and STAT's coverage, used the word "modest."

Most marketing, by contrast, implies hours reclaimed nightly. The best-powered 2026 evidence says the objective time savings are real but measured in minutes per shift, larger for primary care and high-note-volume clinicians, smaller for others. Anchor your expectations to the marketing and you'll be disappointed. Anchor them to this study and you'll be calibrated.

## What did the burnout-specific studies find?

Bigger effects show up on how clinicians feel, which is where the picture gets interesting.

A 2025 JAMA Network Open study across Mass General Brigham and Emory, surveying more than 1,400 clinicians, found a 21.2% absolute reduction in burnout prevalence at Mass General Brigham over 84 days, with prevalence falling from 52.6% to 30.7%. At Emory, the share of clinicians reporting that documentation positively affected their well-being rose from 1.6% before adoption to 32.3% after 60 days. A separate UCLA randomized trial in NEJM AI found roughly a 7% improvement in burnout scores even with its smaller measured time savings.

Real, published, encouraging. They also come with the caveats a careful reader applies. Survey response rates were low, so respondents may self-select toward people the tool helped. The designs show association, not proof of cause. And these are pilots and trials at academic systems, not the whole profession. The companion post, [do AI scribes reduce burnout](../do-ai-scribes-reduce-burnout/), walks through those caveats in detail, so we won't repeat them all here. What this digest cares about is the contrast between the burnout numbers and the time numbers.

## Why does well-being improve more than the minutes saved?

Because the minutes that get saved come off the task clinicians hate most.

Here's the disconnect the 2026 researchers flagged: objective time savings were modest, but subjective well-being gains were substantial. The explanation isn't mysterious. After-hours documentation, reconstructing a visit from memory at 9pm, is a disproportionate source of frustration. Strip even a modest number of minutes off that specific task and it moves how a clinician feels far more than the same minutes pulled from a neutral task would. Which time you save matters more than how much.

This has a practical implication. If your clinicians' biggest pain is after-hours charting, the evidence suggests an ambient scribe will help their well-being more than the modest minute count implies. If their pain is inbox or workload, expect less, because the scribe doesn't touch those. We mapped where the after-hours minutes actually go in [beating pajama time](../ai-scribe-pajama-time/).

## What this means for buying a scribe

Read the evidence as calibration, not as a sales pitch, ours included.

The honest summary for 2026: ambient AI scribes save a modest but real amount of documentation time, and they improve clinician well-being by more than that time alone would predict, because they target the most resented work. The durable, causal burnout claim is still being established. Any vendor stating it flatly is ahead of the evidence.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. We'd rather tell you the evidence is promising-but-early than oversell it, because the well-being effect is real enough that it doesn't need exaggerating, and a calibrated buyer is a happier customer.

## Test the well-being effect on your own clinicians

The studies tell you the direction. Your own clinic tells you the size, for your clinicians, on your visits.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to see how a finished note appears about two minutes after a sample visit, then run the 7-day free trial across a real clinic week and ask your clinicians the simplest question: did you get an evening back? That subjective answer is the one the evidence says matters most. For the time-and-money side, see [the real ROI of an AI scribe](../ai-scribe-roi-calculator-guide/); for the full documentation-burden picture, the [pillar on cutting charting time](../reduce-charting-time-clinicians/); and for the short yes-or-no, the companion [do AI scribes reduce burnout](../do-ai-scribes-reduce-burnout/).

---

## Electronic Patient Records in India: What EPR Means
https://patientsquare.com/in/blog/electronic-patient-record-india/
Published 2026-05-14 · Updated 2026-09-08 · Tags: epr, india, definitional, emr, patient-records

EPR, EMR, EHR — the full forms, the real differences, and what an Indian clinic actually needs from a patient record system in 2026.

An electronic patient record is the digital version of everything a clinic documents about a patient — visit notes, diagnoses, prescriptions, and test results — held in software rather than a paper file. In India the term is used interchangeably with EMR (Electronic Medical Record). Both describe the same thing: a digital chart that belongs to one clinic or facility.

An electronic patient record (EPR) is a digital record of everything a clinic documents about a patient. Visit notes, diagnoses, prescriptions, lab results: all of it in software instead of a paper file. In India, EPR and EMR (Electronic Medical Record) are used for the same thing. The distinction between them and EHR (Electronic Health Record) is real but matters more for hospitals and networks than for most clinics.

> **Key takeaways**
>
> - EPR (Electronic Patient Record) and EMR (Electronic Medical Record) mean the same thing in everyday India clinic use: a digital chart that lives in your practice.
> - EHR (Electronic Health Record) is the interoperable version, designed to follow the patient across providers. India's EHR Standards 2016 (MoHFW) define this formally.
> - No law forces a private clinic to use a specific EPR system. The operative 2002 medical ethics code sets a three-year minimum for indoor records, without prescribing a specific EPR system.
> - ABDM's DHIS can pay facilities for eligible KYC-verified ABHA-linked records, but rates, periods, software conditions, and transaction limits change by corrigendum.
> - For most OPDs, the bottleneck isn't which record system you run. It's whether the note gets written at all in a 2-minute consultation.

## What EPR means, and why the terminology is confusing

The term Electronic Patient Record arrived in India from UK NHS usage, where "EPR" is the standard shorthand for a hospital's clinical information system. The US equivalent is EMR. Indian vendors picked up both, which is why you'll see both on brochures for what is, under the hood, identical software: a digital record system for one facility.

EHR (Electronic Health Record) is the third variant, and this one does mean something different. India's Ministry of Health and Family Welfare published the EHR Standards for India in 2013, revised in 2016. Those standards define an EHR as a record meant to be shared across providers, built around common vocabularies like SNOMED CT, ICD, and LOINC so the record means the same thing everywhere it travels. The difference between an EPR/EMR and an EHR is whether the record is designed to stay in your clinic or follow the patient to a specialist, a lab, or another hospital.

For a solo GP or a small group clinic, this distinction is mostly theoretical. You're not routing records to another facility as a routine part of care. What you need is a digital chart that keeps your notes findable and your prescriptions retrievable. That's an EPR or EMR, whatever the software calls itself.

## What Indian law actually says about patient records

No central law currently mandates a particular EPR system for private clinics. What exists is an expectation of record-keeping, not a technology prescription.

The operative Indian Medical Council 2002 medical ethics code requires indoor records to be kept for three years from the start of treatment and requested records to be issued within 72 hours. It does not set a blanket three-year outpatient retention period or prescribe a specific EPR vendor. State medical council rules vary, and none prescribe a specific EPR vendor, so there's no legal force driving your software choice.

The actual case for going digital is practical, not regulatory: digital records are far easier to retrieve three years later than a physical file in a cupboard, and a well-structured SOAP note holds up better in a medico-legal situation than a line or two in a register. There are roughly 65,000 medical negligence cases filed annually in India (based on estimates from healthcare legal analysts citing NMC and consumer court data), and documentation quality is a recurring factor in how those cases resolve.

## ABDM and the financial case for digital records

ABDM is the government's national health-data infrastructure. The mission connects patient records across providers through ABHA (Ayushman Bharat Health Account), which is a health ID for Indian patients.

For a clinic, the entry point is registering on HFR (Health Facility Registry). Once registered and running qualifying ABDM-integrated software, you can link patient records to ABHA addresses. The Digital Health Incentive Scheme can pay facilities for eligible transactions, but HFR registration and a digital record alone do not make a transaction payable.

The volatile scheme details now live in one maintained place: our [current DHIS guide](../abdm-incentives-for-doctors/), which shows its NHA source-check and next-review dates. Check that guide and the NHA page before making a business case. Your software's production milestone and version, KYC status, transaction mix and frequency, filing date, and the currently effective corrigendum can all change the result.

ABDM is worth understanding. It's also not the reason most clinics start looking at EPR software. The reason is usually throughput.

## The real clinic problem: records don't get written

Most EPR vendors don't mention this part. The average primary-care consultation in India runs about two minutes. A 2017 BMJ Open systematic review of 67 countries by Irving and colleagues clocked India near the short end of a global range from 48 seconds (Bangladesh) to 22.5 minutes (Sweden). Two minutes to listen, examine, decide, and prescribe. There's no time left to write a proper note.

So what gets written? A line. Or the diagnosis gets coded from memory at the end of the queue. Or the prescription gets printed and the note never appears in the system at all.

A better EPR database doesn't fix this. It gives the thin note a neater home. The problem sits upstream of the database: the gap between a two-minute consult and a complete, defensible record. A documentation layer that drafts the note during the visit, not after the queue clears, is a different thing from the record system itself.

## Where an AI documentation layer fits

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. The scribe is the module that solves the documentation problem here.

You don't have to switch record systems to use it. The scribe drafts a complete note during the consultation and exports it as PDF, HL7, or FHIR, so it sits alongside whatever EPR or EMR you already run. Or, if you want the record system too, the bundled AI EHR ships from the Copilot tier. Either way you review the draft, make any edits, sign it, and it lands wherever you keep your records.

A few specifics that matter for India. The scribe is record-system-agnostic, so there's no ripping out your existing software. Visit audio is processed in memory and discarded the moment the note is drafted; no audio archive, no recording sitting around. It captures English, Hindi, and 20-plus Indian languages, including the code-mixed Hindi-English of a real OPD, and the note always comes back in clean clinical English. Patient data is handled to DPDP Act 2023 standards: consent-first, purpose-limited. ABDM integration is on our roadmap, not a current feature. Any vendor telling you otherwise deserves a follow-up question. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing runs on three plans, per clinician per month, ex-GST. Assist starts at ₹1,599 on annual billing (₹1,999 month-to-month) and covers the documentation essentials. Copilot at ₹2,399 annual adds the bundled AI EHR and WhatsApp messaging. Autopilot at ₹3,999 annual adds an AI receptionist and follow-ups. Add 18% GST, so the Assist entry works out to about ₹1,887 a month all-in. There's a 7-day free trial, so you can run it on a real clinic day before committing.

## Choosing a patient record system: the questions that actually matter

Most EPR buying decisions chase the wrong things: feature lists, cloud vs. local, whether there's a mobile app. Those matter, but none of them determine whether your clinic's records actually improve.

The questions that do: What happens to your notes when you're seeing patient forty? By that point in a morning OPD, the documentation from the first hour is whatever you could type between patients. If the system requires you to type at speed just to keep up, the database quality doesn't matter. The bottleneck is the writing.

Second: does your software have production ABDM integration at the milestone and v3 version your workflow requires, or just "ABDM-ready" marketing language? Those are different. Technical integration is one DHIS condition; it does not make every record eligible or guarantee a payout. Ask for the production milestone, v3 status, valid security assessment, and the transaction types the vendor can actually submit.

Third: where does the vendor stand on DPDP? India's Digital Personal Data Protection Act 2023 applies to health data. Any software holding patient records needs a clear answer on consent capture, data retention, and what happens to patient data if you switch systems. A vague answer there tells you most of what you need to know about the vendor.

If the missing piece in your clinic is the note rather than the database, read the full breakdown of [EMR vs EHR in India](../emr-vs-ehr-india/) to sort the acronyms first. Once you know which layer is actually broken, [our pricing](../../pricing/) is a one-page read. There's no demo required to see the numbers.

---

## How Accurate Are AI Medical Scribes? What to Expect
https://patientsquare.com/us/blog/ai-scribe-accuracy-what-to-expect/
Published 2026-05-13 · Updated 2026-07-22 · Tags: accuracy, note-quality, ai-scribe

Why no responsible AI scribe vendor publishes a clean accuracy percentage, what that number hides, and the tests that actually tell you if a scribe is good.

Accurate enough to draft a usable note that you edit, not accurate enough to sign unread. The honest answer is that accuracy varies by specialty, accent, room noise, and visit type, so a single percentage is misleading. The 2025 trials found generated notes occasionally contained clinically significant errors, which is why review is mandatory.

We won't quote you an accuracy number, and here's why: a single percentage hides everything that matters. AI scribe accuracy depends on what you measure, transcription or clinical correctness, on whose voice, in what room, for which kind of visit. A vendor advertising "99% accurate" has chosen a flattering definition and a clean test set. The honest answer is that a good scribe drafts a strong note you still have to read, and the only accuracy figure worth trusting is the one you measure on your own visits.

This is the post where we argue ourselves out of a marketing claim. It would be easy to put a big number on a banner. We don't, because the number would be misleading, and because you'd be right not to trust it. Instead, here's what accuracy actually means for an AI scribe and how to test it for real.

> **Key takeaways**
>
> - No responsible vendor, us included, should publish a single ASR accuracy percentage; it hides definition, population, and visit type.
> - 2025-2026 trials found AI notes "occasionally" contained clinically significant errors, which is why clinician review is non-negotiable.
> - Accuracy varies most on the hard cases: heavy accents, more than one language in the room, noisy multi-speaker rooms, unusual presentations.
> - The only trustworthy accuracy figure is the one you measure on your own real visits during a trial.

## Why won't you give me an accuracy number?

Because the number is a magic trick, and we'd rather show you how it's done.

"99.5% accurate" sounds precise and means almost nothing without three answers the banner never gives. Accurate at what, transcribing the words, or getting the clinical content right? Those are different problems with different error rates. Accurate for whom, the clean American-accented dictation in the vendor's test lab, or your patient with a heavy accent switching between languages in a crowded waiting room? Accurate on which visits, the simple follow-up, or the complex presentation with three complaints and an interrupting relative? Change any one of those and the number moves.

So a single percentage is a choice of the most flattering definition, the easiest dataset, and the simplest visit. It's not a lie exactly. It's a number engineered to impress and built to be useless to you. We think a vendor that leads with it is telling you how they'd like to be evaluated, not how the tool performs on your Tuesday.

We'd rather be the vendor that says: here's what actually varies, here's how to test it, and here's why you review every note regardless.

## What the studies actually found about accuracy

The honest literature is more useful than any banner figure.

A 2025 UCLA randomized trial published in NEJM AI, covering 72,000 encounters across 238 physicians and 14 specialties, found that AI-generated notes "occasionally" contained clinically significant inaccuracies, and that physicians had to actively review the output rather than passively accept it. That's the finding that matters more than any accuracy percentage: not "how often is it right" but "it's wrong often enough, and seriously enough, that you must check." A larger 2026 JAMA study across five health systems reached a similarly grounded conclusion, real but modest benefits, and inconsistent performance, which is the opposite of a clean number.

The takeaway isn't that AI scribes are inaccurate. It's that accuracy is multi-dimensional and context-dependent, which is exactly what a single number can't capture. We graded these dimensions individually in our [SOAP-note quality rubric](../ai-scribe-soap-note-quality/), because grading six axes tells you more than one percentage ever could.

## Where does accuracy actually break down?

On the hard cases, predictably, and these are the ones to test deliberately.

Accents and multiple languages come first. A model trained mostly on one accent struggles with others. A patient with a strong accent, or one moving between languages mid-sentence, is the genuine stress test. AI Medical Scribe by Patient Square works in English plus more languages and returns the note in clean clinical English either way, but you should still test it on your own patients, not take our word for it.

Then noisy, multi-speaker rooms. A quiet exam room is easy. A cramped room with a family member answering half the questions, and the clinic's noise leaking through the door, is where transcription quality separates products.

And unusual presentations. Routine visits draft well almost everywhere. The complex, atypical case is where a weaker model fills gaps with plausible-sounding content that didn't happen.

This is also why prescription safety can't lean on the language model. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The Rx draft reflects what the visit called for; it is a draft only, never sent to a pharmacy. The scribe does not screen for interactions, dosing, or pregnancy, so the clinician stays the safety check, reading the draft and adjusting the medicines before signing. A draft a model wrote is still a draft a model wrote, and the review that follows is where the safety lives, not in the model.

## How should I actually test accuracy?

Run it on your real visits, and stack the test against the cases you worry about.

1. Use a trial, not a demo. A scripted demo flatters every scribe. Your real patient mix sorts them out.
2. Test transcription and clinical accuracy separately. Did it hear the words? Did it get the meaning, the assessment, the plan?
3. Hunt for invented findings. The dangerous error is the confident hallucination, a symptom or result the patient never gave. Look for it specifically.
4. Throw your hard cases at it. Your heaviest accent, your noisiest room, your most mixed-language visit, your most complex presentation. Easy visits don't discriminate.
5. Time the cleanup. If editing the draft takes longer than writing from scratch on your hard visits, the accuracy isn't there for you, whatever the brochure says.

That gives you a real accuracy read, specific to your practice, which is the only kind worth having. The full buyer's version is in [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/).

## Test it on the visits you actually worry about

A published accuracy number can't tell you what a scribe does on your patients. A week of real visits can.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to see a draft note appear about two minutes after a sample visit, then run the 7-day free trial and deliberately test your hardest cases, the accents, the noise, the complex presentations. Read every draft closely for the first week and time the cleanup. That's your accuracy figure, and it's the only one we'd trust on your behalf. For how note quality ties back to the time you're trying to save, start at the [pillar on cutting charting time](../reduce-charting-time-clinicians/); for the per-note dollars, [the real ROI of an AI scribe](../ai-scribe-roi-calculator-guide/).

---

## Switching AI Medical Scribes Without Losing a Clinic Day
https://patientsquare.com/us/blog/switch-ai-scribe-migration-checklist/
Published 2026-05-12 · Updated 2026-07-22 · Tags: ai-scribe, switching, migration, checklist

A 12-step cutover checklist and a parallel-trial protocol to switch AI scribes without losing a single note, a clinic day, or your old data.

In the self-serve band, not really. There's no integration project to unwind, so switching is mostly two jobs: secure your old notes before you lose access, and run the new tool on real visits before you commit. The risk isn't technical difficulty; it's switching on faith instead of testing on a real clinic day first.

Switching AI scribes is mostly two jobs, not a project: get your old notes out before you lose access, and prove the new tool on real visits before you cancel anything. Do those in the right order and you never lose a clinic day, because your current scribe keeps working while you test the next one in parallel. This page is the cutover checklist, 12 steps, plus a parallel-trial protocol that grades both tools on the same real clinic day. You don't need faith. You need a week of evidence.

In the self-serve band there's no integration to unwind, so the danger isn't difficulty. It's switching blind: canceling on a demo's promise, losing notes you didn't export, or signing up for a launch price that resets in year two. The checklist below removes each of those.

> **Key takeaways**
>
> - Switching self-serve scribes is low-risk if you do it in order: export old notes first, trial the new tool in parallel, cancel last.
> - The parallel trial runs both scribes on the same real clinic day, so there's never a gap and you grade notes on your own visits, not a demo.
> - Export before you cancel: access usually ends with billing, and if you enabled an optional note auto-delete window, older notes may already be gone.
> - Confirm year-two pricing in writing, a signed BAA, and a one-sentence audio answer before you commit.

## Why do clinicians switch AI scribes?

Rarely on a whim. Three patterns drive it. The price changed, a launch or promo rate reset higher at renewal, or a feature you use moved up a tier. The tool missed your reality, it stumbled on your accents, your languages, your noisy clinic, or the multi-speaker room you actually work in. Or the gaps showed, no prescription draft, no ICD-10 suggestions, audio retained longer than you're comfortable with, a support queue that went quiet.

Whatever the trigger, the switch itself is the same shape. You're trading a known tool for a better-fitting one, and the only real risk is doing it carelessly. If any of those triggers sound like your week, you can <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and see the alternative before you plan the move.

## The 12-step cutover checklist

Do these in order. The order is the point: export before you cancel, test before you commit, cancel last.

1. Write down why you're switching. One sentence. It becomes your grading criterion later, so be specific: "ICD-10 is behind a tier I won't pay for," not "it's annoying."
2. List the clinical output you need. Note only, or note plus ICD-10 suggestions plus a prescription draft? Write the must-haves so you compare like for like, not feature-sheet against feature-sheet.
3. Check your current tool's note auto-delete setting. Some scribes offer an optional auto-delete window for notes. If it's on, older notes may already be gone, so check before you assume they're waiting for you.
4. Export every note you want to keep. Pull them into your EHR or local storage now, while you still have access. Access usually ends the day billing does.
5. Confirm what your current tool does with audio, and when it deletes it. You want this on record before you leave, especially if a patient or court ever asks.
6. Shortlist the replacement on the things that matter: published year-two pricing, a signed BAA, the clinical output from step 2, and a one-sentence audio answer.
7. Start the new tool's free trial, but don't cancel anything yet. The old scribe stays live.
8. Run the parallel trial (the protocol is in the next section). Both tools, same real visits, one clinic day minimum, a week is better.
9. Grade the notes side by side against your sentence from step 1 and your list from step 2. Use your own visits, not the demo's.
10. Get year-two pricing in writing. Launch and promo rates reset; a published ladder you can read beats a number you have to ask for.
11. Only now, cancel the old subscription, after the new tool has proven itself on real visits and your old notes are safely exported.
12. Keep your export for the record. Even after you switch, your old notes are part of the chart history. Store them where your retention policy lives.

Notice that nothing in that list is technical. That's the self-serve advantage: no integration project, no data-migration vendor, no downtime. The work is discipline, not engineering.

## The parallel-trial protocol: run both on one real clinic day

Demos flatter every scribe equally. The only test that tells you anything is your own clinic day, run through both tools at once. Here's the protocol.

Pick one normal clinic day. Not your easiest, not your hardest, a representative Tuesday with your usual mix of visit types, accents, and languages.

Run your current scribe as your live tool. Nothing changes in your workflow; it's still your real documentation, and that's what guarantees you don't lose the day.

Now run the new scribe in parallel on the same visits, using its trial. Patient Square's assisted trial runs for seven days after the workspace is ready, so agree the start date before the parallel capture begins. You're capturing the same conversations twice.

When the day ends, put the two notes side by side for each visit and grade them on what actually matters to you:

| Grade each note on | What you're checking |
|---|---|
| **Accuracy** | Did it get the drugs, doses, and history right? Any invented detail? |
| **Structure** | Is the SOAP clean, or did it dump a transcript? |
| **Your languages** | If a visit ran in more than one language, does the note still come back in clean clinical English? |
| **Edit load** | How many minutes to make each note sign-ready? |
| **The extras** | Did you get ICD-10 suggestions and a prescription draft, or just a note? |

The tool that wins your grading wins, full stop. A scripted demo can't show you this because it doesn't have your patients in it.

Run this for a single day and you'll know more than any feature comparison can tell you. Run it for a week and you've removed the risk from the switch entirely. Start by [reviewing Practice Copilot's scope](/us/products/practice-copilot/), agree on a date, and run it on a real clinic week in parallel with whatever you use now.

## What to check before you commit to the new tool

The trial proves note quality. These four checks prove you won't regret the switch in six months.

Get year-two pricing in writing. Launch rates and promo rates reset. Ask for the full ladder, what you pay now, what you pay at renewal, what each tier includes. We publish ours with no asterisks on the [pricing page](../../pricing/), which is the standard to hold every vendor to.

Then the legal floor: a signed BAA. It's the floor for any vendor that touches PHI, so don't switch to a tool that won't sign one for your practice size. Confirm, too, that the BAA reaches the subprocessors handling your audio, not just the vendor's own systems.

You also want a one-sentence audio answer. "Where does the audio live, and for how long?" A vendor who can't answer that in one sentence has answered it. Ours: the AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice; it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit, and visit audio is processed in memory and discarded the moment the note drafts, so there's no recording retained. The full posture is on the [security page](../../security/).

Last, the clinical output you actually use. If you need ICD-10 suggestions and a prescription draft, confirm which plan includes them so you don't discover the gap after you've switched. With Patient Square the scribe, ICD-10 suggestions, and prescription drafts are in every plan from Assist up; the bundled AI EHR and messaging come in at the Copilot tier, so you can see exactly where each feature sits before you move.

## Which alternative should you switch to?

That depends on what you're leaving and why. We've written the honest fit pages for the tools clinicians most often compare:

- Coming from the established self-serve incumbent? [Freed alternatives](../freed-ai-alternatives/) covers what Core includes, what sits a tier up, and the switch checklist for that specific move.
- Weighing an enterprise platform you've outgrown the need for? [Abridge alternatives](../abridge-alternatives/) is the enterprise-versus-independent fit call, and [Dragon Copilot alternatives](../nuance-dax-dragon-copilot-alternatives/) covers the EHR-embedded, Epic-native end.
- Leaving a voice-command tool? [Suki alternatives](../suki-ai-alternatives/) lays out voice-command versus ambient-first.
- Want the whole field at once? Our [best AI medical scribes comparison](../best-ai-medical-scribes/) is the honest roundup, with when-each-fits-better verdicts.

Each of those pages says, by name, when the tool you're leaving is actually the better fit, because pretending otherwise would make the rest untrustworthy.

## When you should not switch (said plainly)

Here's the verdict, no hedging. The honest version is the useful one.

Stay put if your current tool already does the job at a fair price. If you're on a scribe that drafts clean notes, signs a BAA, handles your languages, and isn't about to reprice you, switching for a marginal feature is churn you don't need. Chasing a slightly greener field costs you a week of parallel trialing for little gain.

Switch when the parallel trial proves a real difference on your visits. Maybe the new tool grades clearly better on your own accents, languages, and visit types. Maybe it includes output your current one gates, or publishes a price your current one hides. Then the switch pays for itself fast. The trial is how you tell the two situations apart.

The rule is short: never switch on a demo. Switch on a graded clinic day.

## How to switch in a week

1. Day 1: export your old notes, check the auto-delete setting, write your one-sentence reason.
2. Day 2: start the new tool's trial; keep the old one live.
3. Days 2 to 6: run the parallel trial on real visits; grade notes side by side daily.
4. Day 6: get year-two pricing in writing; confirm the BAA and the audio answer.
5. Day 7: if the new tool won your grading, cancel the old one, keep your export.

The price ladder with no asterisks is on the [pricing page](../../pricing/), and the security receipts are on the [security page](../../security/). <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to see the alternative against your own visit type, then compare the [product options](/us/compare/) with whatever you use now. Done in this order, you switch without losing a note, a clinic day, or your old data.

---

## SOAP Notes: Full Form, Format, and How a Scribe Drafts One
https://patientsquare.com/in/blog/soap-note-full-form-format-india/
Published 2026-05-11 · Updated 2026-07-22 · Tags: soap-note, india, definitional

SOAP full form in medical: Subjective, Objective, Assessment, Plan. How the format works in an Indian OPD, and how an ambient scribe drafts one in two minutes.

SOAP stands for Subjective, Objective, Assessment, Plan. The subjective is what the patient reports. The objective is what you observe and measure. The assessment is your clinical judgment on what is happening. The plan is what happens next — investigations ordered, treatment started, follow-up scheduled. Together the four sections form the standard structure for a clinical encounter note.

SOAP stands for Subjective, Objective, Assessment, Plan. Those four words are the entire skeleton of a clinical encounter note. The Subjective is what the patient tells you. The Objective is what you find. The Assessment is what you conclude. The Plan is what you do next. Every teaching hospital in India uses this structure; most ambulatory practice collapses it into shorthand. This post covers what each section actually contains, why the Indian OPD context makes writing them hard, and how an ambient scribe produces one in the two minutes after a visit.

> **Key takeaways**
>
> - SOAP = Subjective, Objective, Assessment, Plan. The full form is the same in India as internationally; the execution pressure is not.
> - The Assessment is the section most commonly skipped or thinned. "Chest pain, query cardiac" is not an Assessment; it is a restated complaint.
> - Indian primary-care consultations average about two minutes (BMJ Open, 2017 systematic review of 67 countries). At that pace, handwriting a full SOAP note is not realistic.
> - An ambient AI scribe captures the visit and returns a draft SOAP note roughly two minutes after it ends. You review and sign; the audio is discarded. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
> - The legal expectation under the IMC 2002 regulations is a complete, retrievable clinical note per patient. SOAP is the clearest way to produce one.

## What SOAP stands for, section by section

### Subjective

The Subjective is the patient's story. Chief complaint first, ideally in their own words or close to it: "pain in the chest since yesterday evening, worse on breathing." Then the history of present illness — onset, character, severity, what makes it better or worse, associated symptoms. Relevant past history lives here too if it frames the complaint: "previous TB treatment completed 2019."

What the Subjective is not: a recital of the patient's entire past medical history, a list of every current medication, or a demographic summary. Those belong in the record but they clutter the encounter note if pasted in wholesale.

The failure mode in Indian OPD practice is a Subjective that says only the chief complaint. "Pain chest" is not a Subjective. It is a chief complaint. The history (duration, character, severity, associated symptoms) is what makes the Subjective useful when someone reads the note six months later.

### Objective

The Objective is what you find on examination and measurement. Vitals: blood pressure, pulse, respiratory rate, temperature, SpO2 if measured. Examination findings: general appearance, the relevant system examination, anything you specifically look for given the complaint. Existing investigation results if available and relevant to today's visit.

One rule worth following: only put findings you actually checked. "Abdomen soft, non-tender" when you did not examine the abdomen is the kind of auto-populated boilerplate that turns a note into a liability rather than a record.

### Assessment

The Assessment is where most notes fall apart. This is your clinical reasoning stated plainly: what you think is happening and what you are ruling in or out. "Pleuritic chest pain, likely musculoskeletal. Viral pleuritis less likely given short duration. Cardiac cause needs to be excluded."

Not "chest pain, query cardiac." That is the Subjective restated. The Assessment should show your differential, your working diagnosis, and your clinical reasoning. It is the section a consulting specialist reads first, and the one a medico-legal case turns on.

### Plan

The Plan is what happens next, itemised. Investigations ordered. Medications prescribed. Referrals. Follow-up interval. In Indian practice, this often runs to a prescription printout attached to the note, which is fine — the Plan section should still spell out the key decisions in prose, not just point to the script.

The Plan section is also where errors of omission are most dangerous. A patient sent home with analgesics but no instruction on when to return or what symptoms to watch for has an incomplete Plan, regardless of whether the prescription was correct.

## Why writing SOAP notes is genuinely hard in Indian OPD

The structure is simple. Writing it during a real OPD is not.

A 2017 BMJ Open systematic review by Irving and colleagues looked at primary-care consultation length across 67 countries. India sat at roughly two minutes on average. At that pace, you are taking a history, examining the patient, deciding, prescribing, and explaining — in the time it takes to write a paragraph. Something gives. Most often it is the documentation.

The result is clinical notes that look like billing codes: a diagnosis, a drug, a dose. That note is technically present. It does not tell a story. It does not satisfy a complaint review. It does not help the next doctor who sees this patient, or the one who sees them in an emergency when you are not there.

The Indian Medical Council (Professional Conduct) Regulations 2002 require indoor records to be maintained for at least three years from the commencement of treatment and produced within 72 hours of a written request. The NMC 2023 successor regulations are currently in abeyance and do not alter this baseline. The operative expectation is clear: a complete, retrievable note exists per patient. What "complete" means in a contested case leans on what a SOAP note would have contained. A diagnosis and a drug do not meet that bar.

## What an Indian SOAP note actually looks like

Here is a realistic OPD note for a 38-year-old with chest pain, in the format most Indian hospital EMRs accept:

---

**Subjective:** 38M presenting with right-sided chest pain since yesterday evening, sharp, worse on deep breathing and coughing, no radiation. No fever, cough, or breathlessness. No cardiac or respiratory history. No recent travel or prolonged immobility.

**Objective:** BP 118/76, HR 82 regular, RR 16, T 98.4F, SpO2 99% on room air. Comfortable at rest. Chest: decreased breath sounds at right base, no crepitations. Abdomen soft, non-tender.

**Assessment:** Pleuritic chest pain, right-sided. Differential: musculoskeletal, viral pleuritis. Pulmonary embolism low probability (Wells score 0), but needs to be excluded given pleuritic character and decreased air entry.

**Plan:** CXR PA view today. D-dimer if CXR unremarkable and clinical concern persists. Ibuprofen 400mg TDS with food for 5 days. Return if breathlessness, haemoptysis, or worsening pain. Review in 5 days or earlier.

---

That is about 170 words. A competent clinician writes it in under three minutes. The problem is that in a 100-patient day, three minutes per note is five hours of documentation after the queue clears. Or a note that gets dropped entirely.

## How an ambient scribe drafts the SOAP note

The typical US search for SOAP note templates is aimed at students building their first note from a textbook case. The Indian clinic problem is not "I do not know how to write a SOAP note." It is "I know exactly what to write and I have no time to write it."

An ambient AI scribe addresses the second problem. The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

Here is what the scribe actually does with each section.

The Subjective comes from the patient's history as it unfolds in the room. The scribe picks up the chief complaint, duration, character, and associated symptoms from the conversation. You do not narrate this separately or dictate into a separate window; it captures what the patient says and what you ask.

The Objective draws from what you say aloud. When you call out "BP one-eighteen over seventy-six" or say "breath sounds reduced at the right base, abdomen soft," those go in. Vitals from a monitor you read out get captured the same way.

The Assessment is where the most happens, and also where you should spend the most time on review. Your verbal reasoning during the visit ("I want to rule out PE here," "this feels musculoskeletal to me") feeds the model. It structures that reasoning into a diagnosis and differential. Your job is to verify that what it wrote matches what you actually concluded, not just what you said.

The Plan captures medications you mention, investigations you order, follow-up timing you give the patient. The prescription draft comes separately, formatted for your review and sign-off.

The visit audio is processed in memory and discarded the moment the draft is ready. Nothing is stored. The note comes out in clean clinical English regardless of whether the consultation was in Hindi, Tamil, or the Hindi-English mixing that is standard in most Indian OPDs. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

| Without a scribe | With an ambient scribe |
|---|---|
| 2-minute consult → note written from memory after the queue | 2-minute consult → draft SOAP note ready 2 minutes later |
| Subjective: "chest pain" (chief complaint only) | Subjective: full history drawn from the conversation |
| Assessment: blank or "query cardiac" | Assessment: your stated reasoning, structured and reviewable |
| Plan: prescription attached, no follow-up instruction | Plan: medications, investigations, follow-up interval all captured |

## How this post relates to the note-quality guide

If your question is "what makes a good AI-generated SOAP note and how do I grade one," the [AI-generated SOAP note quality guide](/us/blog/ai-scribe-soap-note-quality/) covers that in a six-point rubric. That post owns the evaluation question. This one owns the upstream question: what SOAP means, how the four sections work in an Indian context, and how an ambient scribe handles the drafting so you are not writing notes by hand at the end of a 100-patient day.

For a ground-level view of what the scribe does across a full working day (the throughput math, the language handling, how it fits alongside an EMR), the [scribe-for-doctors post](/in/blog/scribe-for-doctors-india/) goes through that hour by hour.

## Pricing and where to start

Pricing starts from ₹1,599 per clinician per month ex-GST on annual billing (the Assist plan), which works out to about ₹1,887 with 18% GST added. Copilot (₹2,399 ex-GST) bundles an AI EHR and WhatsApp messaging, and Autopilot (₹3,999 ex-GST) adds an AI receptionist and follow-ups. There is a 7-day free trial through the India signup page. Full pricing is at [/in/pricing/](/in/pricing/).

SOAP is not going anywhere as a format. An ambient scribe just makes it possible to complete one on every patient in a busy OPD, not only on the ones where you happened to have time.

---

## Suki AI Alternatives: A Scribe With a Bundled EHR
https://patientsquare.com/us/blog/suki-ai-alternatives/
Published 2026-05-11 · Updated 2026-07-14 · Tags: ai-scribe, suki, alternatives, ehr

Suki AI is a voice assistant and scribe. Patient Square adds a bundled EHR and front-office automation at a published price from $79/mo. Honest comparison.

Voice interaction. Suki started as a clinical voice assistant you talk to ("add to the assessment," "show me the last note") and later added ambient capture. If you like driving the chart by speaking commands mid-visit, that dual workflow is Suki's signature and it has built it for years.

If you're comparing Suki AI, you're comparing a voice-led assistant that grew into a scribe: you talk to it, it acts on the chart, and it also listens ambiently. It's sold through a sales motion, so the price comes as a quote, not a number on a page. Patient Square answers the same job differently. It's an ambient scribe too, but the Copilot plan bundles a real EHR and front-office automation, and every tier's price is published. The scribe starts from $79/mo, the EHR is bundled from $119/mo on annual billing, and you can read the whole ladder right now on our [pricing page](../../pricing/).

We make one of the alternatives here, so read this with the sources open. Suki doesn't publish a per-clinician price, so we won't guess one, and where Suki is the better fit, there's a section that says so by name.

> **Key takeaways**
>
> - Suki is voice-command-led: you talk to it as well as let it listen. It sells through a sales motion with no published per-clinician price as of 2026.
> - Patient Square is an ambient scribe plus a bundled EHR (AI Copilot EHR) plus front-office automation, with every tier's price published.
> - Patient Square US pricing: Assist $99/mo ($79 annual, no EHR), Copilot $149/mo ($119 annual, EHR bundled), Autopilot $249/mo ($199 annual).
> - Two real differences: published price versus quote-on-request, and a bundled EHR versus a voice layer on top of your existing chart.
> - When voice commands are core to your workflow, Suki is the better fit. That's a verdict, not a hedge.

## What Suki AI is good at

Give Suki its due. It's been in clinical voice longer than most, and it shows. Suki began as an assistant you address out loud (add hypertension to the problem list, pull the last A1c) and layered ambient capture on top, so it now both listens to the visit and takes spoken commands. That dual mode is the product's identity. For a clinician who likes steering the chart by talking to it, the muscle memory is real and worth paying for.

It's also built for scale. Suki markets deep EHR integration and an enterprise sales motion, the kind of deployment a large system with an IT team expects. That's a legitimate strength for the right buyer.

So this isn't a takedown. It's a fit question. Some clinicians think in voice commands and want an assistant wired into a big EHR. If that's you, book a demo with Suki on your list and ours, and compare the two workflows on the same visit before deciding.

## Where Patient Square is different

Two honest differences, and neither is note quality.

First, the price is public. Suki sells through a sales motion, so learning your per-seat number takes a call and a contract. Patient Square publishes all three US tiers on the [pricing page](../../pricing/): $79 to $199 per clinician per month on annual billing. You can size a budget before you talk to anyone. One opinion, stated as one: a vendor that hides a per-seat subscription price is telling you something about the renewal conversation later.

Second, the EHR is bundled, not integrated. Suki sits on top of the EHR you already run and integrates with it. Patient Square, on the Copilot plan, *is* the EHR: it bundles AI Copilot EHR, so the ambient note lands in a chart it owns, and the front office (intake, scheduling, follow-ups) is automated on the same subscription. The scribe still drafts a structured SOAP note with ICD-10 suggestions and a prescription draft you review and sign. It just has somewhere to put them.

If you want a voice layer over a big existing EHR, that's Suki's world and we say so below. If you want one tool that is the scribe, the chart, and the front office, book a demo and see whether the bundle fits your practice.

## What Patient Square costs

We publish the price. No quote required.

Three US tiers, per clinician:

| Tier | Monthly | Annual (per mo) | What you get |
|---|---|---|---|
| Assist | $99 | $79 | Documentation essentials, no EHR |
| Copilot | $149 | $119 | Scribe plus AI Copilot EHR bundled, front-office automation |
| Autopilot | $249 | $199 | Everything, deepest automation |

The scribe starts from $79 a month on annual billing. The bundled EHR starts from $119 a month on annual billing, the Copilot tier. A 7-day free trial runs on the scribe, so you can test note quality on a real clinic week.

We can't run a head-to-head price table against Suki, because Suki doesn't publish a number and we won't invent one. What we can say is that our whole ladder is readable without a sales call, and the Copilot tier folds the EHR into the same $119-a-month line rather than a separate bill. The full ladder with no asterisks is on the [pricing page](../../pricing/).

## When Suki is the better choice

Here's the verdict, no hedging.

Choose Suki if voice commands are central to how you work. If you like talking to the chart, issuing spoken instructions mid-visit, and you want one assistant that handles dictation, ambient capture, and chart queries with enterprise EHR integration behind it, Suki has built exactly that. An ambient-only tool like ours will feel like it took away a control you used every visit. That's a genuine reason to stay, and we won't pretend otherwise. Same goes for a large system that needs a scribe wired deep into an existing enterprise EHR: that's Suki's deployment, not ours.

Choose Patient Square if you'd rather the software be invisible and the price be public. If your ideal is saying nothing to the tool, talking only to the patient, and reading a finished note that's already in a bundled chart, the voice-command layer is overhead you won't use. You'd rather have a clean note plus ICD-10 suggestions and a checked prescription draft, at a published price, on an assisted trial that begins after the workspace is ready.

The split is workflow and buying model, not note quality. Both draft good notes. One wants you to talk to it; the other wants you to forget it's there.

If your shortlist is wider, [Heidi Health alternatives](../heidi-health-alternatives/) and [Freed alternatives](../freed-ai-alternatives/) cover the EHR-agnostic scribe end of the market.

## How to decide in a week

Skip the spec sheet and run the real test:

1. Ask whether you'll actually use voice commands. If talking to the chart sounds great in a demo but you'd never do it on a 14-patient Tuesday, that feature isn't for you.
2. Get Suki's real quote in writing, then compare it to a list price you can read without a call.
3. Match the output. Note plus ICD-10 suggestions plus a checked prescription draft, so you're comparing like for like.
4. Settle the audio question with both vendors: stored or not, and for how long. Ours is never stored.
5. Trial on real visits. A scripted demo flatters every scribe equally; your own accents and interruptions don't.

The receipts behind our claims are on the [security page](../../security/), and the full price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the ambient workflow against your own visit type, then run the 7-day trial on a real clinic week. If you reach for voice commands, Suki is your tool. If you'd rather the software vanish and the price be public, the bundle is what you're shopping for.

---

## Medical Transcription vs AI Medical Scribe in India: Per-Note Math
https://patientsquare.com/in/blog/medical-transcription-vs-ai-scribe-india/
Published 2026-05-08 · Updated 2026-07-22 · Tags: transcription, ai-scribe, india

Medical transcription bills per note or per minute, delivers in hours. An AI scribe drafts in two minutes for a flat monthly fee. Honest India price comparison.

Indian medical transcription services typically bill per page (roughly ₹30–80 per A4 page of typed notes, depending on turnaround and specialty complexity) or per audio minute. A busy OPD doctor generating 40 typed pages of notes a month could pay ₹1,200–3,200 at those rates, before any rush-turnaround premium. The bill climbs every busy day.

Indian medical transcription services bill per page or per audio minute and return your notes in 12–24 hours. An AI scribe listens to the consultation itself and drafts a structured note in about two minutes, from ₹1,599 per clinician per month on annual billing (ex-GST, Assist plan). This is the India-specific comparison: the math is in rupees, the turnaround numbers come from real-world service rates, and the OPD economics are the ones where 40 patients happen before lunch. The US-facing version, with dollar rates, is at [ai-scribe-vs-medical-transcription-service](/us/blog/ai-scribe-vs-medical-transcription-service/).

> **Key takeaways**
>
> - Indian transcription services typically bill ₹30–80 per typed page or per audio minute. A practice generating 30+ pages of notes a month already crosses the ₹1,599 Assist-plan breakeven.
> - Standard turnaround in India is 12–24 hours; STAT delivery runs 4–6 hours for a premium. An AI scribe drafts in about two minutes.
> - Patient Square's Assist plan is ₹1,599/clinician/month ex-GST on annual billing (₹1,887 on the invoice after 18% GST), unlimited notes, no per-note metering.
> - Audio handling differs: a transcription service receives and stores your audio file. The AI scribe processes audio in memory and discards it the moment the note drafts.
> - A transcription service still fits if you dictate complex specialist narration and want a human in the loop.

## How medical transcription billing works in India

Indian medical transcription services charge in one of two ways. Most bill per page of typed output, with one "page" meaning a standard A4 page of text at normal medical-record density. The common range for routine dictation is around ₹30–80 per page at standard 12–24 hour delivery. Faster turnaround carries a surcharge: same-day or STAT delivery (4–6 hours) can run 50% higher than the base rate.

Some services bill per audio minute of dictation instead, which makes the cost depend on how long you talk rather than how dense the notes are. A five-minute dictation note might run a single A4 page, or two pages if the case is complex.

The ceiling problem with per-unit billing is straightforward. A general physician running a 40-patient OPD generates notes. If the average note is two-thirds of a page and they document all 40 visits, that's about 27 pages a day. At ₹50 per page, one busy day costs ₹1,350. The monthly bill from a high-volume OPD, in a city where a 67-country BMJ Open review put India's average consult at roughly two minutes, can exceed ₹20,000. The meter doesn't know you had a full day.

## The per-note math: where the breakeven sits

Here's the arithmetic a clinic owner needs to run once.

Take your transcription rate per page and divide ₹1,599 by it. That number is how many pages per month it takes before the Assist plan costs less.

| Rate per page | Breakeven (pages/month) | OPD equivalent (at 1 page per 2 consultations) |
|---|---|---|
| ₹30 | 53 pages | 106 consultations/month |
| ₹50 | 32 pages | 64 consultations/month |
| ₹70 | 23 pages | 46 consultations/month |
| ₹80 | 20 pages | 40 consultations/month |

A clinic seeing 60+ patients a month, a couple of busy OPD mornings, has almost certainly crossed the ₹50-per-page breakeven. The subscription wins past that point, and it stays fixed every day after.

At the ₹1,599 annual-billing base with 18% GST, the invoice is ₹1,887 per clinician per month. The with-GST breakeven at ₹50 per page is 38 pages (about 76 consultations a month). Worth knowing: most clinics can't claim back the 18% GST as input tax credit, since healthcare services are GST-exempt. Budget ₹1,887, not ₹1,599.

## The full comparison table

| | Medical transcription service | AI Medical Scribe by Patient Square |
|---|---|---|
| **What you do** | Dictate after the visit | Nothing; it listens during the consultation |
| **Who writes the note** | A human transcriptionist | The software drafts it |
| **Billing structure** | Per page (₹30–80) or per audio minute | From ₹1,599/clinician/month ex-GST (Assist, annual) |
| **Turnaround** | 12–24 hrs standard; 4–6 hrs STAT (premium) | About 2 minutes after the visit |
| **Languages** | Depends on service; Hindi dictation available at many vendors | English, Hindi, and 20+ Indian languages including Hinglish; note always in clean clinical English |
| **What you receive** | Typed text from your dictation | Structured SOAP note, ICD-10 suggestions, prescription draft |
| **Audio handling** | Sent to and stored by the service | Live consultation audio discarded after drafting; uploads use a separate mode with explicit consent |
| **Cost as volume grows** | Scales with every patient | Flat; unlimited notes |

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

## Turnaround: what 12–24 hours actually costs a clinic

Turnaround time sounds like a convenience issue. It is, but it has a clinical dimension too.

A note returned the next day means your chart stays incomplete overnight. For a medico-legal record, an incomplete chart is a liability. For a patient who comes back, or calls with a question, or whose insurer requests records, a 24-hour lag is a gap at exactly the moment you need continuity. The NMC's 2002 regulations (the operative record-keeping framework in India as of mid-2026) expect medical records to be producible within 72 hours of a request. A note in your queue overnight doesn't violate that, but it narrows your window.

STAT delivery at 4–6 hours costs more. Same-day turnaround costs more. Every time you need your notes faster, the per-unit model charges you for the urgency.

An AI scribe hands the note back before the patient reaches the exit. There is no queue, no incomplete chart at the end of the day, no overnight gap. That is not a minor feature for a busy OPD.

## Language: the Hinglish OPD problem

Medical transcription in India typically handles Hindi dictation, and many services accept vernacular languages with a specialist typist. The limitation is that code-mixed speech — the Hinglish that runs through every metro OPD, where a doctor says "patient ko thoda shortness of breath hai aur chest tight feel ho raha" without switching registers — tends to trip up a transcriptionist working from audio. You end up either slowing your dictation to stay in one language or accepting a transcript that needs editing.

AI Medical Scribe by Patient Square was built for exactly that conversational mix. It captures consultations in English, Hindi, and 20+ other Indian languages, handles code-switching mid-sentence, and the note always comes back in clean clinical English. You don't adjust for the microphone. The [India language handling page](../ai-scribe-hindi-indian-languages/) covers the full scope.

Transcription services can handle complex specialist narration that ambient models might compress. That is a real trade-off and worth naming plainly. If your documentation depends on verbatim clinical narration for medico-legal or specialty reasons, a human who listens carefully is doing something the AI draft might not match.

## Audio: where the two models differ most

A transcription service works because a human listens to your audio. That means the audio file gets transmitted to the service, listened to by staff, and retained somewhere on their infrastructure until delivery is complete and their retention clock runs out. For most consultations, this is fine. For some, the patient's words in your clinic being stored on a third-party server feels like a real risk, one worth weighing under the DPDP Act 2023, which places data-handling duties on every clinic that processes patient information digitally.

AI Medical Scribe by Patient Square processes audio in memory, on-device, and discards it the moment the note drafts. No audio file is sent anywhere. No audio file is stored. The encryption posture (TLS 1.2+ in transit, AES-256 at rest) and the full data-handling framework are on the [security page](../../security/). The note belongs to your practice, exportable or deletable any time, and neither the audio nor the note is ever sold or shared.

## When a transcription service is the better fit (stated directly)

Keep a transcription service if:

You dictate long complex specialist narration and you want a human who listens carefully. A consultant cardiologist writing detailed catheterisation notes, or a surgeon dictating complex operative findings, is producing a kind of narration where human judgment about nuance still adds real value. If you prefer to dictate and have someone else do the typing, that is a legitimate workflow.

Your monthly note count is genuinely low. Under 20–25 pages a month, the per-page rate can win on price. A part-time practice, a second-opinion clinic, or a new practice still filling its schedule is in this zone.

Your medico-legal workflow depends on verbatim records from a named transcriptionist. Some medicolegal teams want the chain of custody a human typist provides. That is a specific requirement, and it is the right reason to keep a transcription service.

Everywhere else, the flat fee and the two-minute turnaround are the better deal.

## The India pricing picture

The [India price guide](../ai-medical-scribe-price-india/) covers the full rate card for AI scribes in rupees, including EkaScribe, Augnito, and the US imports that convert to ₹7,500–14,200 a month. The [US comparison post](/us/blog/ai-scribe-vs-medical-transcription-service/) covers the dollar-priced side.

For this post's purposes: Patient Square's Assist plan starts at ₹1,599 per clinician per month on annual billing (ex-GST), ₹1,887 on the invoice with 18% GST. Copilot (₹2,399 ex-GST annual) adds the bundled AI Copilot EHR and WhatsApp messaging, and Autopilot (₹3,999) adds the higher-tier modules. No per-note metering at any level. The [pricing page](../../pricing/) has the full ladder, GST disclosures included.

Work out your current monthly transcription bill, or estimate it at your note volume. Most busy Indian clinics cross the breakeven in under a week of full OPDs. Past that point, the meter is just overhead.

## How to decide before you pay anything

1. Count last month's note pages (or estimate at 0.5 pages per consultation). Multiply by your per-page rate. That is your current transcription cost.
2. Compare to ₹1,887 (Assist with GST, on annual billing). The crossover is usually around 35–40 pages a month.
3. Ask the transcription service where your audio goes and how long they keep it. Put the answer next to the [security page](../../security/).
4. Decide whether you want to keep dictating. If you'd drop it gladly, the AI scribe removes the step entirely.
5. Run one clinic day on a trial. The only honest test is your own OPD, your own patients, your own speed.

Book a short demo to see a note draft itself two minutes after a visit, then run the 7-day trial on a real clinic week. If your transcription bill grows with every full day and the notes still land tomorrow morning, the flat, two-minute alternative is the one you'll keep.

---

## Dragon Copilot Alternatives for Practices Not on Epic
https://patientsquare.com/us/blog/nuance-dax-dragon-copilot-alternatives/
Published 2026-05-08 · Updated 2026-07-22 · Tags: ai-scribe, comparison, dragon-copilot, dax

Dragon Copilot is built to live inside the EHR. When an EHR-agnostic scribe fits a practice better, when Dragon fits better, and the real cost gap.

Dragon Copilot is Microsoft's ambient clinical documentation tool, the product that grew out of Nuance DAX Copilot after Microsoft acquired Nuance. It pairs Dragon dictation with ambient note generation and is designed to embed deep inside the EHR, with the strongest fit on systems already running Microsoft and Nuance infrastructure.

Dragon Copilot lives inside the EHR. That's the whole question. Run a large, Epic-native or Microsoft-heavy system with an IT team and that deep integration is the point; no self-serve scribe matches it. But if you're a small practice with no integration project, you'd be paying enterprise prices for the one feature you're least equipped to use, EHR write-back. So this page is a fit call. What Dragon Copilot is genuinely best at, what it actually costs (Microsoft doesn't publish it, so we'll be careful), and when leaving it for an EHR-agnostic tool is the right move.

Fair warning: we make one of the alternatives. Read this with the sources open. Dragon Copilot's price isn't published, so every number below is attributed and bounded.

> **Key takeaways**
>
> - Dragon Copilot is the Microsoft/Nuance ambient tool that grew out of DAX Copilot. Its strength is deep EHR integration, strongest on enterprise systems.
> - Microsoft publishes no per-provider price. Third-party aggregation and KLAS 2026 put real deployments roughly $150 to $600 per provider per month plus implementation fees; KLAS reported about $215 across large-system deployments. Small groups pay near the top of that band.
> - Patient Square publishes a US ladder from $79 per clinician per month on annual billing (Assist), no integration project, no procurement cycle, with a bundled AI EHR from the Copilot plan.
> - For an independent practice, the EHR-embedded workflow is mostly unused. For a large Epic-native system, it's the reason to stay. The verdict says so by name.

## What is Dragon Copilot actually good at?

Credit where it's due. The fit argument only works if it's honest. Dragon Copilot is Microsoft's ambient clinical documentation product, the descendant of Nuance DAX Copilot after Microsoft bought Nuance. It marries decades of Dragon dictation with ambient note generation, and it's engineered to embed deep inside the EHR. On a large system already running Microsoft and Nuance infrastructure, that integration is genuinely hard to beat. The note lands in the chart. The dictation history and the enterprise support are already there, wired in.

A CMIO rolling out ambient documentation across a health system should keep Dragon Copilot on the shortlist, and nothing below argues otherwise. The real question is whether that's you. If you're a small practice weighing a practice-sized route, you can book a demo to see a finished note in about two minutes, then request an assisted trial if the workflow fits.

## What does Dragon Copilot cost, and why can't you find the number?

Here's the friction a small practice hits first. Microsoft publishes no per-provider price for Dragon Copilot. It's negotiated, scoped to system size, integration depth, and the enterprise contract you sign. Third-party aggregation, including KLAS 2026 data, puts real-world deployments roughly between $150 and $600 per provider per month, plus implementation fees. KLAS reported about $215 per provider per month across a set of large-system deployments. The pattern holds: large systems negotiate down toward the low end, while small groups sit near the top and usually pay list, with little room to bargain.

Be precise about what those figures are. Third-party estimates and survey data, not Microsoft-published prices. And the dollar amount isn't really the point. You can't know your number without a procurement conversation, and a good chunk of whatever you pay is EHR integration a small practice won't use.

Compare that to a published ladder. We price transparently: three US tiers per clinician per month, from $79 on annual billing (Assist), then $119 (Copilot, which adds a bundled AI EHR and WhatsApp messaging) and $199 (Autopilot), the full ladder on our [pricing page](../../pricing/). Want the wider self-serve field? Our [best AI medical scribes comparison](../best-ai-medical-scribes/) is the honest roundup, and if you're coming from the established self-serve incumbent, [Freed alternatives](../freed-ai-alternatives/) covers that end.

## Epic-embedded versus EHR-agnostic: the decision table

The cleanest way to choose? Ask what your EHR setup actually is.

| | Epic-embedded (Dragon Copilot's home turf) | EHR-agnostic (AI Medical Scribe by Patient Square) |
|---|---|---|
| **Best fit** | Large system on Epic / Microsoft / Nuance stack | Independent practice or small group on any EHR |
| **EHR write-back** | Yes, deep, part of the deployment | No; you copy the finished note into your chart |
| **Who installs it** | Enterprise IT + integration project | Short assisted workspace setup before the trial |
| **Pricing** | Quote on request (est. $150-600/provider/mo, plus implementation) | Published ladder from $79/mo annual (Assist) |
| **Buying path** | Sales cycle, contract, scoping | Published pricing, assisted setup |
| **Audio handling** | Per Microsoft's terms; verify directly | Processed in memory, never stored |

Neither column is wrong. They're sized for different buyers. The enterprise column buys you the note arriving in the chart automatically across hundreds of clinicians. The agnostic column buys you a clean note you paste in yourself, at less than half the small-group estimate, with no project to run.

## The DAX-escape math for a practice not on Epic

Run the arithmetic an enterprise buyer never sees. Say a small group gets quoted near the bottom of the small-group band, $399 per provider per month, against our published $79 Assist entry price.

| | Dragon Copilot (small-group est.) | Patient Square Assist (published) |
|---|---|---|
| Per provider per month | ~$399 (estimate) | $79 (annual billing) |
| Annual per provider | ~$4,788 | $948 |
| Plus implementation fee | Often yes | None |
| What the premium buys | EHR integration, enterprise support | A clean note you paste in |

The gap isn't the headline. What the gap pays for is. At the enterprise tier a large share of the price is EHR integration and system-scale support, and a practice not on Epic, without an integration team, uses little of that. So you'd be carrying enterprise overhead for a note you could get from an agnostic tool at a fraction of the cost. If that table describes you, book a demo and check the note quality against your own visits before assuming cheaper means worse.

## What you give up by leaving Dragon Copilot

Be clear-eyed about the trade. Pretending there isn't one is how you end up disappointed.

First, you lose automatic EHR write-back. Dragon Copilot pushes the note into the EHR as part of the deployment; we don't integrate with EHRs, so you copy the finished note into your chart. For a solo practice that's a few seconds per visit. For a 400-clinician system it's a workflow decision. Know which you are.

You also lose enterprise-stack depth. The Dragon dictation history, the Microsoft support apparatus, the system-wide rollout tooling, all of that is real value if you're operating at enterprise scale.

What you keep is what a small practice actually uses. The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription is a draft that reflects what you said in the room; you review it, adjust the drug, dose, and instructions, and sign. There's no automated interaction check between you and the signature. The safety check is you, the same as it is when you write a script by hand. Audio is processed in memory and discarded the moment the note drafts, so there's no recording retained, and a BAA is available for every customer, solo practices included. The full posture is on the [security page](../../security/).

## When Dragon Copilot is the better choice (said plainly)

Here's the verdict, no hedging. The honest version is the useful one.

Keep Dragon Copilot if you're a large, Epic-native or Microsoft-heavy enterprise that wants the scribe wired into the EHR, tied into your existing Microsoft and Nuance stack, deployed across hundreds of clinicians with enterprise support and a procurement process that expects all of it. At that scale a self-serve tool isn't a competitor. It's the wrong category. Dragon Copilot is built for exactly this, and switching away to save on a per-seat price would cost you far more in lost integration than you'd ever save.

Go EHR-agnostic if you're a practice not on Epic, or on any EHR without an integration team, and you want a clean note in two minutes, published pricing, a BAA without an enterprise contract, and an assisted trial after workspace setup. You'll paste the note into the chart without minding the extra few seconds. That describes most independent practices reading this page.

The split is about EHR depth and scale, not note quality. Both draft good notes. One assumes you have an integration team; the other assumes you don't want one.

## How to decide in a week

Skip the spec-sheet comparison and run the real test:

1. Count your EHR-integration need honestly. If "the scribe writes into my EHR automatically" is a hard requirement, you're in enterprise territory, and Dragon Copilot belongs on your list.
2. If it isn't, shortlist EHR-agnostic tools with published prices and clearly documented trial setup and start terms.
3. Get the real quote in writing. The Dragon Copilot estimates are third-party and implementation fees are extra, so compare it to a list price you can read without a call.
4. Settle the audio question with every vendor. Stored or not, and for how long. Ours: never stored.
5. Trial on real visits. A scripted demo flatters every scribe equally.

The receipts behind our claims are on the [security page](../../security/), and the price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the note quality against your own visit type, then run the 7-day trial on a real clinic week. If you're not on a system that uses the deep EHR integration, the enterprise tool is probably more than you need.

---

## AI Medical Scribe for Dermatology: Lesion & Procedure Notes
https://patientsquare.com/us/blog/ai-scribe-for-dermatology/
Published 2026-05-07 · Tags: ai-scribe, dermatology, specialty

How an AI scribe handles dermatology documentation: lesion morphology, body-site mapping, procedure notes for biopsies, cryotherapy, and more.

A well-designed ambient scribe captures what you say in the room: macule vs. papule vs. plaque, Fitzpatrick phototype, dermoscopy descriptors. The note comes back with the terms you used, not a generic complaint field. Whether it does this accurately is the test to run before you commit. Trial it on your Monday skin-check clinic.

Dermatology documentation is harder to shortcut than most specialties. A lesion note needs morphology, distribution, body site, and size. If you did a shave biopsy in room 3 and cryotherapy in room 4 before lunch, you also need separate, complete procedure records for both. An AI scribe cuts the time to get those notes done. Whether it works for derm specifically comes down to how it handles the language your specialty actually uses.

> **Key takeaways**
>
> - Dermatologists spend roughly 36% of their work time on documentation, per a 2020 J Am Acad Dermatol study, higher than most specialties because each note carries morphology, site, and often procedure detail.
> - An AI scribe captures spoken exam findings in real time and returns a structured draft note about two minutes after the visit. You read it, correct anything, and sign.
> - The test that matters: does the draft come back with "3mm hyperpigmented macule, left forearm" or "patient presented with a skin concern"? Generic output fails derm.
> - ICD-10 suggestions come with the draft. You confirm or change them. They are suggestions, not auto-coded charges.
> - The biggest workflow gain for high-volume derm is the procedure note: narrate as you work, get the draft two minutes later, no reconstruction from memory at end of day.

## What makes derm documentation harder than a primary care note

A primary care SOAP note can sometimes get away with a short HPI and a problem list. A derm note usually can't. The exam section carries real work: morphology (macule, papule, plaque, nodule, pustule, vesicle, bulla), surface characteristics (smooth, verrucous, scaling, crusted), distribution (localized, generalized, dermatomal, photodistributed), and body site precise enough to find the lesion again at the follow-up.

Add color, size in millimeters, borders, any dermoscopic findings, and a Fitzpatrick phototype when it affects treatment. You've just built a note that takes real time to type, even for someone who knows the vocabulary cold.

Then there's the procedure side. A shave biopsy note needs consent documented, site marked, anesthesia administered, technique used, specimen labeled, pathology submission details, and post-care instructions given. A cryotherapy note needs the lesion description, site, number of freeze-thaw cycles, and expected healing discussed. Do three procedures in a morning and you're writing three separate procedure records on top of the visit notes.

A 2020 Journal of the American Academy of Dermatology study found dermatologists spend about 36% of their work time on documentation. That figure reflects exactly this reality: derm documentation is content-heavy by specialty design, not by inefficiency.

## How a derm visit runs with an ambient scribe

You start an AI Medical Scribe session when the patient walks in, then run the visit normally. You speak to the patient, describe your findings aloud as you examine: "left medial calf, 8 by 6 millimeter hyperpigmented plaque, irregular border, no scaling." The scribe captures it.

After the visit, you stop the session. Two minutes later you have a draft note with that finding in the HPI or exam section, not a generic "skin lesion" placeholder. You review it, fix anything the scribe got wrong or missed, and sign.

For a procedure visit, the same pattern holds. Leave the session running while you work and narrate what you're doing: "shave biopsy, left forearm lesion, one percent lidocaine local, specimen to pathology labeled left forearm shave." The scribe builds the procedure note from what you said. When done, the draft covers both the visit and the procedure. You review the whole thing and sign.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

## What the draft note should look like

This is the test that actually separates a scribe that works for dermatology from one that doesn't. Generic ambient scribes built for primary care often flatten exam findings into vague descriptors. The draft should come back with your clinical language, not a paraphrase of it.

A note from a well-designed scribe after a skin-check visit should look something like this:

| Section | What it should contain |
|---|---|
| HPI | Chief concern, duration, any prior treatment, change over time |
| Exam — skin | Morphology (type: macule, papule, plaque, etc.), color, size in mm, borders, distribution, body site precise enough to relocate |
| Dermoscopy | Structures noted if you described them aloud |
| Assessment | Differential or working diagnosis |
| ICD-10 suggestions | Codes mapped to your working diagnoses, for you to confirm |
| Plan | Treatment, biopsy ordered, follow-up |

If the scribe hands you "lesion on leg, see doctor" for an exam you described in clinical terms, it's not built for derm. The trial period exists for exactly this reason. Run it on your real skin-check clinic before you commit.

## Procedure notes: where documentation time stacks up

Biopsies, cryotherapy, electrodesiccation and curettage, intralesional injections, excisions. You might do several in a session, and each needs its own complete record.

The spoken narration approach fits this work well. You describe the procedure as you do it, or immediately after while the patient is still in the room, and the scribe drafts the note from what you said. The alternative is circling back at end of day to reconstruct what happened in room 3 at 10:15am. That's where errors creep in and time disappears.

Here's a rough framework for what a spoken narration covers per procedure:

| Procedure element | What to say aloud |
|---|---|
| Patient and consent | "Patient consents to shave biopsy of left forearm lesion" |
| Site preparation | "Site prepped with alcohol, sterile field" |
| Anesthesia | "One percent lidocaine with epinephrine, injected local" |
| Technique | "Shave biopsy, razor technique, lesion fully excised" |
| Specimen | "Specimen labeled left forearm, sent to pathology" |
| Post-procedure | "Hemostasis achieved with aluminum chloride, wound care discussed" |

The scribe captures that and structures it into the procedure note. You read it before signing. Nothing is submitted automatically.

## The body-site mapping problem

One specific derm challenge: documenting body site precisely enough that you, or someone covering for you, can find the exact lesion at follow-up. "Right arm" isn't enough. "Right medial forearm, proximal third, 3cm distal to the antecubital fossa" is the kind of note that has clinical value.

An AI scribe captures what you say. Say "right arm" and that's what the note says. Say "right medial forearm, proximal third" and the note says that. Precise spoken description is on you. The scribe doesn't add anatomical specificity you didn't verbalize.

There's actually a useful practice effect here. Verbalizing the body site during the exam tends to make the description more precise than typing it later from memory, because you're doing it while looking at the patient.

## Fitzpatrick phototype, dermoscopy, and specialty vocabulary

One test worth running during the trial period: say "Fitzpatrick phototype III, mild actinic damage" and see what comes back. Or "dermoscopy shows irregular pigment network with regression structures, no blue-white veil." If the scribe outputs those phrases correctly, the underlying speech recognition handles your vocabulary. If it transliterates into something unrecognizable, it'll frustrate you on every complex note.

Most modern ambient scribes handle medical terminology better than consumer speech recognition. But derm vocabulary is a specific mix of Latin morphology terms, measurement conventions, and dermoscopy descriptors. Worth verifying before committing.

The 7-day trial is how you run that test on actual patients, not a synthetic demo note.

## Volume math for a 30-patient derm day

Dermatology practices vary a lot. A general derm running 30 to 35 patients a day has a very different rhythm from a procedural derm seeing 15 patients with multiple procedures each. The time-back math shifts accordingly.

| Scenario | Time per note without scribe | With scribe | Daily savings |
|---|---|---|---|
| 30-patient skin check, 3-4 min notes | ~100 min | ~75 min | ~25 min |
| 15-patient procedural day, 6-8 min notes | ~110 min | ~80 min | ~30 min |
| Mixed: 20 visits + 5 procedures | ~115 min | ~82 min | ~33 min |

These are conservative estimates, not a trial study. Your actual time depends on how long your notes run, how much correction the drafts need, and how fast you read and sign. The only way to know your number is to run it on a real week.

The harder-to-quantify shift is the one primary care talks about too: notes that finish during clinic instead of after. For a dermatologist seeing 30 patients, even half the documentation clearing before 6pm changes the day in ways a time table doesn't capture.

## Where the scribe can't replace your judgment

The scribe drafts what you said. It doesn't interpret what you meant, add clinical reasoning you didn't verbalize, or catch an inconsistency between your verbal exam description and your assessment. If you call something a macule and your assessment says melanoma workup, the scribe won't flag that tension. That's the review step where your clinical judgment runs.

ICD-10 suggestions in the draft are suggestions. You confirm them, modify them, or reject them. They're not auto-coded charges. The scribe has no connection to your billing system. Nothing moves without you reviewing and signing the note.

This is also why the review matters, especially early. In the first few weeks of using a scribe, you'll find the patterns where the draft needs correction: specific terms it mishears, structure it doesn't handle the way you want. Adjusting your verbal habits to produce better first drafts takes a week or two and then stabilizes.

## Evaluating a scribe for your derm practice

The [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) covers the questions that apply across specialties: audio handling, data ownership, pricing transparency, ICD-10 claims honesty, and what happens to the audio after the visit. For derm, add three specific tests to that scorecard.

First, run a morphology output test. Dictate a complex lesion description and check whether the draft matches your clinical language or flattens it. Second, run a procedure note test: narrate a simple biopsy and check whether the structured note covers consent, site, technique, specimen, and post-care. Third, run a volume test on your busiest half-day, the one where you're going room to room with no gaps. Does the scribe handle back-to-back sessions cleanly, or do notes bleed into each other?

A trial period is non-negotiable for specialty evaluation. A demo on a single note tells you almost nothing about how the scribe performs across a full skin-check day.

The US Assist plan starts at $79 per clinician per month on annual billing ($99 month-to-month). Copilot ($119/mo annual) adds a bundled AI EHR and WhatsApp, and Autopilot ($199/mo annual) adds an AI receptionist and follow-ups. An assisted 7-day trial begins after workspace setup, with no subscription commitment. Full pricing is on the [pricing page](../../pricing/).

If you want to see note quality against your actual lesion descriptions and procedure vocabulary before committing, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical complex case. That's the right test for dermatology.

---

## NMC Record-Keeping for Doctors: Where an AI Medical Scribe Helps
https://patientsquare.com/in/blog/nmc-record-keeping-ai-scribe/
Published 2026-05-07 · Updated 2026-10-04 · Tags: nmc, record-keeping, compliance, india, medico-legal

What India's operative record-keeping rules require (three-year indoor retention, 72-hour production), why the 2023 NMC regs are in abeyance, and where an AI scribe fits.

The rules in force are the Indian Medical Council 2002 conduct regulations. Regulation 1.3.1 says keep indoor (admitted) patient records for three years from the start of treatment. Regulation 1.3.2 says produce records within 72 hours when a patient, attendant, or legal authority asks. Failure on either is professional misconduct.

India's operative record-keeping rule for doctors is the 2002 medical-council code, not the 2023 one. It asks two concrete things: keep indoor patient records for three years from the start of treatment, and produce any record within 72 hours of a request. The 2023 NMC regulations that tried to tighten this were held in abeyance, so they don't apply. Here is what the rule actually demands, and where an AI scribe earns its keep.

> **Key takeaways**
>
> - The rules in force are the 2002 MCI conduct regulations. Keep indoor records 3 years; produce on request within 72 hours.
> - The NMC's 2023 conduct regulations were notified, then put in abeyance on 23 August 2023. They are not operative.
> - Failure to maintain records for 3 years, or to produce them inside 72 hours, is professional misconduct.
> - A complete, retrievable note written at consultation pace is the whole game. A scribe helps you write it; the duty to sign and keep it stays yours.

_Sources: NMC / MCI Code of Medical Ethics 2002; Medical Dialogues (NMC 2023 abeyance)._

## Which record-keeping rules actually apply to Indian doctors right now?

The 2002 ones. The Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002 are the operative law for how doctors keep and hand over records. Two clauses do the heavy lifting.

Regulation 1.3.1 says every physician keeps the medical records of indoor (admitted) patients for three years from the date treatment commenced, in the standard proforma the regulations lay down. Regulation 1.3.2 says that when a patient, an authorised attendant, or a legal authority asks for records, you acknowledge the request and issue the documents within 72 hours.

Both clauses sit inside the conduct code. So a breach isn't just bad practice. It's professional misconduct a medical council can act on. That's the part doctors underweight. The retention rule and the production rule both have teeth.

## Why are the NMC 2023 regulations in abeyance, and what does that mean for me?

This is where a lot of online guidance is plain wrong, so read it twice. In 2023 the National Medical Commission notified a new set of conduct regulations for Registered Medical Practitioners. They restated and in places tightened record-keeping. Then, on 23 August 2023, the NMC held those 2023 regulations in abeyance. "In abeyance" means suspended, not in force, pending a fresh notification.

So if a blog tells you the 2023 rules require something specific of your clinic today, it's citing a text that isn't operative. Until the NMC revives them by gazette, the 2002 regulations govern. Practically, you plan to the 2002 standard: three years, 72 hours, indoor records, standard proforma. If the 2023 framework ever comes back, you'll have built the habit that matters anyway, which is a complete, retrievable record for every visit.

We'll say the obvious thing once: this is reporting, not legal advice. For your own exposure, confirm specifics with counsel. But the framing above is the one to confirm, not the abeyed-2023 one.

## How do the 2002 record rules sit alongside the DPDP Act?

They stack, and they pull in the same direction. The medical-council code governs *what* records you keep and for how long. The Digital Personal Data Protection Act 2023 governs *how* you handle the data inside them: consent, purpose limitation, security, deletion when the purpose ends.

| | MCI 2002 conduct code | DPDP Act 2023 |
|---|---|---|
| **Governs** | Which records, how long, production duty | How patient data is collected, secured, deleted |
| **Retention** | 3 years, indoor records (Reg 1.3.1) | Keep only as long as the stated purpose needs |
| **Production / rights** | Produce within 72 hours (Reg 1.3.2) | Honour access, correction, erasure requests |
| **Penalty for failure** | Professional misconduct | Financial penalties via the Data Protection Board |

The overlap is the point: a system that writes a complete note, stores it securely, and lets you retrieve or delete any visit serves both regimes at once. Thin, missing, or unretrievable notes fail both. For the data-handling side in detail, our [DPDP Act for clinics guide](../dpdp-act-clinics-guide/) walks the obligations, and the [DPDP Rules 2025 timeline](../dpdp-rules-2025-clinic-timeline/) dates when each one bites.

## An AI scribe doesn't satisfy the rule. It makes the record exist.

Not by satisfying the rule for you. By making the record-keeping easy enough that you actually do it, on every visit, including the busy ones.

Picture a Pune OPD at 8pm. You've seen 40-odd patients. Keeping an OPD note for each encounter makes a later records request easier to answer; the 2002 code sets a 72-hour window for issuing requested records, while its three-year retention clause names indoor records. Done by hand at consultation pace, the note that survives is often a line and a drug name. That's the note a court later reads as "absent."

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The record-keeping win is mechanical.

The note is complete at pace, captured while you're still in the room, so the three-year-old chart actually has content to retrieve. Input can be Hindi, English, or code-mixed; the note comes back in clean clinical English. It's retrievable on demand too: stored, structured, searchable. When a 1.3.2 request lands, producing the file is a lookup, not an archaeology dig. And the notes are yours. They belong to your practice, you can export or delete any visit, and that maps cleanly onto DPDP's deletion duty without fighting the 2002 retention floor.

One honest limit: the scribe drafts; you sign. It doesn't move the duty off you, and it shouldn't. What it removes is the reason records go thin, which is the time you don't have at 8pm.

| The record three years later | Handwritten at 8pm | AI scribe draft, reviewed and signed |
|---|---|---|
| **What's in it** | One line plus a drug name | Structured SOAP note, written in ~2 min |
| **Legibility** | Often illegible or missing | Stored, searchable, time-stamped |
| **On a 1.3.2 request** | Reconstructed from memory | Produced as a lookup, not rebuilt |

## Is the three-year rule about indoor records, OPD records, or both?

The 2002 regulation names indoor (admitted) patient records and the three-year clock specifically. It doesn't set a separate OPD retention figure. That gap is where doctors get caught out, because a consumer complaint about an OPD consultation can still land years later, and "the rule only named indoor records" is a weak place to stand.

The defensible default: keep OPD records to the same three-year horizon, and longer where a dispute is foreseeable. The operational cost of retaining digital OPD notes may be modest, but retention still needs a justified purpose and safeguards. The cost of not having it when a notice arrives is the whole case. Treat three years as a practical OPD retention policy to review with counsel, while recognising that the 2002 three-year legal minimum expressly covers indoor records.

## What should I have in place before the next records request lands?

You don't get warning before a 1.3.2 request. Check that you can retrieve and provide requested records within 72 hours. Separately, retain indoor patient records for the three years required by Regulation 1.3.1. Build your record process around both duties.

1. Every visit leaves a record. No exceptions for the busy days. A tool that writes the note at consultation pace is how you hold that line at a 40-patient OPD.
2. Records are stored, not scattered. One retrievable store beats notes split across paper, WhatsApp, and memory.
3. Retention is deliberate. Apply the three-year legal minimum to indoor records; set an OPD retention policy with counsel that accounts for other applicable duties and DPDP purpose limitation.
4. You can prove the chain. Who wrote it, when, and that it hasn't been quietly rewritten after a complaint. Legible, time-stamped records carry far more weight than a tidy note nobody can date.

Check whether your record process produces a complete, retrievable chart even on a busy day. Test retrieval and export with synthetic records, and document the retention policy that applies to your setting. The [records-as-defence guide](../ai-scribe-medico-legal-documentation-india/) explains why the content of that record matters.

---

## Discharge Summary Format India: Cleaner, Faster Cashless
https://patientsquare.com/in/blog/discharge-summary-format-india/
Published 2026-05-06 · Updated 2026-07-22 · Tags: discharge-summary, india, cashless, documentation

What a complete discharge summary contains in India, and how a cleaner, well-structured summary speeds final-discharge authorisation at the cashless desk.

A discharge summary closes an admission by recording who the patient is, why they were admitted, what was found and done, and what happens next. It should include patient and admission identifiers, diagnoses, the course of stay, dated procedures, discharge medicines and doses, follow-up instructions, and the treating doctor's name and signature.

A discharge summary is the one document everyone reads after the patient goes home. The next doctor reads it to continue care. The patient reads it to know what changed. And the cashless desk reads it to close the claim. When it is clear and complete, all three of those happen fast. When it is thin, contradictory, or copied from the last patient, every one of them stalls.

This guide covers what a complete discharge summary actually contains in India, the format that holds up under a TPA's eye, and the part most people get wrong about what a good summary can and can't do for a cashless claim.

> **Key takeaways**
>
> - A complete discharge summary carries identifiers, admitting and final diagnoses, course of stay, procedures with dates, discharge medications, and follow-up. Completeness beats any particular template.
> - The IRDAI Master Circular (29 May 2024) sets a three-hour clock for final discharge authorisation. The summary is the document that request rides on.
> - A clean summary does not stop a claim being rejected for paperwork, because IRDAI bars rejecting claims for "want of documents." The real benefit is speed: an approvable-on-first-read request that clears the clock without queries.
> - The summary is only as good as what got written during the stay. Capturing the encounter well is upstream of writing the summary well.

_Sources: IRDAI Master Circular on Health Insurance Business, 29 May 2024 (IRDAI/HLT/CIR/MISC/77/05/2024); MoHFW EHR Standards for India, 2016._

## What a complete discharge summary contains

Strip away the house style and every good discharge summary answers the same five questions: who, why, what was found, what was done, and what next. The fields below are the ones that make those answers verifiable. NABH accreditation guidance, the MoHFW EHR Standards 2016, and day-to-day TPA practice all converge on roughly this set.

- **Patient and admission identifiers.** Name, age, sex, hospital number, admission and discharge dates, treating consultant. This is what ties the summary to the rest of the record and to the pre-auth already on file.
- **Diagnoses.** Both the admitting diagnosis and the final diagnosis at discharge. If they differ, the summary should make sense of why; a final diagnosis that appears from nowhere is the kind of gap that triggers a query.
- **Course of stay.** A short, honest narrative of what happened between admission and discharge. Key events, the response to treatment, any complications. Not a transcript, a clinical story.
- **Procedures and investigations.** What was done, with dates, and the findings that mattered. A procedure billed but absent from the summary is a classic diagnosis-treatment mismatch.
- **Discharge medications.** Drug, dose, route, frequency, and duration. This is the part the patient and the next prescriber actually act on, so vagueness here has real downstream cost.
- **Condition at discharge and follow-up.** How the patient is leaving, what to watch for, when and where to come back. The instruction that closes the loop on care.
- **Authentication.** The treating doctor's name and signature. An unsigned summary is, for medico-legal purposes, an unfinished one.

The order can vary. The completeness cannot. A summary missing the indication or the final diagnosis is not a formatting problem, it is a hole in the clinical record, and it reads as one to anyone who has to rely on it later.

## Is there a standard discharge summary template in India?

People search for a blank template, paste it in, and assume the job is done. The template is the easy part. There is no single statutory discharge summary format mandated nationally, but the expected fields are remarkably stable across NABH guidance, the EHR Standards 2016, and what TPAs actually look for. The hard part is what goes inside the fields.

A template gives you headings. It does not give you a final diagnosis that matches the procedure, or a course of stay that explains the findings, or discharge medications that line up with what was prescribed during the admission. Those come from the clinical record being complete in the first place. A beautiful template wrapped around a thin record is still a thin summary. So treat the format as table stakes and put the effort where it counts: making sure the content is complete and internally consistent before the patient walks out.

## Why the discharge summary decides how fast cashless clears

Here is the chain, because it is worth seeing literally. At discharge, the hospital's insurance or TPA desk requests final authorisation. That request is built from the discharge summary: the final diagnosis, the procedures done, the course of stay. The insurer or TPA reads it and decides. Approve, query, or hold.

The IRDAI Master Circular on Health Insurance Business, dated 29 May 2024, put a hard clock on that decision. Final discharge authorisation has to be granted within three hours of the hospital's request, and if the insurer drags past three hours, it bears any extra hospital charges from the delay. Three hours sounds generous until a query lands in it. A summary that prompts "please clarify the indication" or "diagnosis does not match the procedure billed" spends that window in back-and-forth, and the patient sits in the bed waiting to leave.

The summary that clears the clock is the one that was complete and consistent the first time. Speed rewards clean summaries and punishes muddled ones. That is the whole mechanism, and the next section is about being exact on what it does and does not mean.

## The part everyone gets wrong about documents and denials

This is where vendors oversell and clinic staff get a rule backwards, so read it carefully. A clean discharge summary does **not** stop your cashless claim from being rejected for paperwork. It cannot, because the rule does not allow rejection for paperwork in the first place.

The IRDAI Master Circular bars insurers from rejecting a claim for "want of documents." Required documents are meant to be sorted at the proposal stage, and where something is missing for a claim, the insurer or TPA is expected to collect it from the hospital, not bounce the claim back at the patient. So "complete your discharge summary and your claims stop getting rejected for missing papers" describes a problem the rules already forbid. It is not the benefit on offer.

The real, narrow, honest benefit is speed. Because a complete and internally consistent summary gives the pre-auth desk a request that is approvable on first read, it is what lets that request clear the three-hour clock without a round of queries. Faster discharge authorisation. Fewer documentation back-and-forths at the bedside. That is the mechanism, and it is worth being precise about, because the loose version of the claim is both wrong and easy to disprove.

For the wider picture of how clinical notes feed cashless approvals and where they break, see [how notes affect cashless approvals](/in/blog/ai-scribe-cashless-claim-documentation/). For who actually sits at the cashless desk and why a TPA cannot reject a claim on its own, see [the TPA full form explained](/in/blog/tpa-full-form-cashless-explained/).

## The summary is only as good as what got written during the stay

Here is the upstream truth a template will never fix. A discharge summary is assembled from the clinical record of the admission. If the daily notes were thin, if the indication was never clearly documented, if the procedure findings live only in someone's memory, then the summary gets reconstructed at discharge from fragments. That reconstruction is where mismatches and gaps creep in, and it usually happens under time pressure with the next patient already waiting.

So the best place to improve discharge summaries is not the discharge desk. It is the encounter itself. A record that was captured completely and consistently during the stay produces a summary that practically writes itself, and one that holds together when the TPA reads it. A record that was captured in scraps produces a summary held together with assumptions.

| | Summary built from a thin record | Summary built from a complete record |
|---|---|---|
| **Final diagnosis** | Reconstructed from memory at discharge | Captured at the point of care during the stay |
| **Procedures and dates** | Pieced together from scattered notes | Already in the record, ready to carry over |
| **Discharge medications** | Copied forward, doses unchecked against the stay | Consistent with what was prescribed |
| **At the cashless desk** | Pre-auth desk queries the indication; the three-hour clock burns | Request approvable on first read; the clock clears clean |

## Where ambient documentation fits

The AI Medical Scribe is one module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It does not write the discharge summary for you, and it does not touch any TPA, insurer, or claims system. There is no claims integration, on the roadmap or off it. What it does is make the clinical record underneath the summary more complete, because the diagnoses, findings, and plan get captured while the encounter is happening instead of being reconstructed afterward.

It works alongside your existing EHR. The record still lives where it already lives; the scribe fills the gap between what was said in the room and what ends up written down. A few things matter for an Indian setting specifically. The scribe captures English, Hindi, and 20+ Indian languages, including the mid-sentence Hindi-English mixing of a real consult, and the note always comes back in clean clinical English. The prescription comes back as a draft that reflects what was decided in the room; you review it, adjust the dose, and sign. The scribe does not screen for drug interactions, dosing, or contraindications, and it sends nothing to a pharmacy. That safety call stays with you, the prescriber. Visit audio is processed in memory and discarded the moment the note drafts; there is no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On pricing, the entry Assist plan is ₹1,599 per clinician per month on annual billing, ex-GST; add 18% GST and the invoice lands at about ₹1,887 a month. Moving up, the Copilot plan (₹2,399 annual) adds a bundled AI EHR and WhatsApp messaging, and Autopilot (₹3,999 annual) adds an AI receptionist and follow-ups, so features do step up with the tier. A 7-day free trial is available after workspace setup. The full breakdown is on the [pricing page](../../pricing/).

## In short

A discharge summary does three jobs at once. It carries care forward to the next doctor, it tells the patient what changed, and it closes the cashless claim. The format is the easy part. Completeness and internal consistency are what actually carry it. The IRDAI clock rewards a summary that is approvable on first read and punishes one that prompts a query. Be precise about why, though. The benefit is speed, not protection from a paperwork rejection that the rules already forbid.

And the real fix sits upstream. A summary is only as good as the record it is built from, and the record is only as good as what got captured during the encounter. If your summaries arrive thin because there was no time to write them properly during the stay, the fix is better capture at the point of care, not a nicer template. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a real consult turn into a structured note, or read the [pricing](../../pricing/) first. Either way, fix the layer that actually feeds the summary.

---

## Free EHR AI Medical Scribe vs Standalone: Is athenaAmbient Enough?
https://patientsquare.com/us/blog/free-ehr-ai-scribe-vs-standalone/
Published 2026-05-06 · Updated 2026-07-22 · Tags: ai-scribe, comparison, athenahealth, pricing

Your EHR now bundles a free ambient scribe. When that is enough, when a standalone tool earns its price, and the honest workflow-coverage comparison.

Yes, for athenaOne customers. athenahealth announced athenaAmbient in November 2025, with its CEO saying ambient documentation is "embedded in the core athenaOne fee and not at any incremental charge." User testing was set for the first half of 2026. The catch is that it only exists inside athenaOne, so it is free only if you already pay for that EHR.

If your EHR now includes a free ambient scribe, the honest answer is: it might be all you need. In November 2025 athenahealth said its athenaAmbient scribe is bundled into the athenaOne fee at no extra charge. Free, and already inside the system you use, is a strong combination. A standalone scribe only earns its price when you need something the embedded one doesn't do: a checked prescription draft, ICD-10 suggestions, multilingual capture, or independence from any single EHR.

So this is a real fork, not a sales setup. Below: what the free embedded scribe actually covers, what a standalone adds, the workflow-coverage matrix that decides it, and a plain verdict on when free wins.

> **Key takeaways**
>
> - athenahealth announced athenaAmbient in November 2025, free for athenaOne users, with testing set for the first half of 2026.
> - It's embedded in athenaOne, so "free" applies only if you already pay for that EHR. Not an athenahealth customer, not an option.
> - A free embedded scribe is strong for note generation in straightforward visits. That's a real category, and for many users it's enough.
> - A standalone tool adds a prescription draft you review and sign, ICD-10 suggestions, multilingual capture, and EHR independence.
> - The deciding question: is note generation all you want automated, or do you need the rest?

## What does a free embedded EHR scribe actually do?

Start with what athenahealth said, because the announcement is the source of truth here. In November 2025, athenahealth's CEO described athenaAmbient as embedded in the core athenaOne fee, at no incremental charge, framing ambient documentation as "a feature, not a business." User testing was set for the first half of 2026; a general-availability date wasn't specified in the announcement, so we won't invent one. The core capability is ambient note generation, with a paired copilot (Sage) announced to add chart-summary and clinical-nudge features.

That's a genuinely good deal for the right user. If you're an athenaOne customer, the scribe lives where you already work, there's no second login, no copy-paste, no separate invoice. For a clinician whose main pain is "the note takes too long," a free, in-EHR note generator solves the actual problem. We're not going to pretend otherwise. The interesting question is the boundary: what does note generation leave out? If you're not on that EHR, or you suspect the boundary matters for your visits, book a demo and see where a standalone picks up where the free tool stops.

## What a standalone scribe adds, and why it costs something

A standalone tool charges money, so it has to do more than draft a note. Here's where the price goes.

Start with the prescription draft. A note describes the visit; a prescription draft starts the next action. The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The draft reflects what was said in the room. It never goes to a pharmacy on its own, and the scribe doesn't screen it for interactions or dosing. You do that when you read and sign, the same check you make on every script today. A note-only scribe stops before drafting the script at all.

Then ICD-10 suggestions. Not a coding engine. Suggestions, surfaced as you finish the note, to speed the coding you'd be doing anyway.

Multilingual capture comes next. A standalone built for it handles visits in more than English. A free embedded scribe tuned for a US EHR's typical patient base often can't, and for a practice with a multilingual patient mix that's a daily gap.

The big one is EHR independence. A free embedded scribe ties you to that vendor's ecosystem. Switch EHRs, change practices, or run on no EHR to begin with, and the free scribe doesn't follow you. A standalone works whichever EHR you use, or none. You copy the finished note in by hand. That's the trade: give up automatic write-back, get independence.

Be honest about that last trade, because it cuts against us too. We don't integrate with EHRs. The embedded scribe writes into athenaOne automatically; with a standalone, you paste. For a solo practice that's seconds. For someone who prizes automatic chart write-back above everything else, the embedded option wins on that axis, and we'll say so.

## The workflow-coverage matrix

Lay the two models side by side on what each covers, not on marketing adjectives.

| Capability | Free embedded EHR scribe | Standalone scribe (ours) |
|---|---|---|
| Ambient note generation | Yes | Yes |
| Writes into the EHR automatically | Yes, within that EHR | No, you copy the note in |
| Works with any EHR, or none | No, EHR-locked | Yes, EHR-agnostic |
| Available without that EHR subscription | No | Yes |
| Prescription draft | Not in the core scribe scope | Yes, you review and sign |
| ICD-10 suggestions | Varies / paired features | Yes |
| Multilingual capture | Limited / not the design case | Yes (English plus more) |
| Published price and BAA terms | Bundled, EHR-tied | Published, any practice size |
| Audio retention you can verify | Per the EHR vendor's policy | Never stored, in-memory only |

Read that matrix the right way. The embedded scribe isn't bad at the things it skips; it just isn't built for them. If those rows are blank for your needs too, the free tool is the rational pick. If three or four of them are must-haves, the standalone's price buys real capability, not just a different logo. The fastest way to know which describes you is to book a demo and watch a standalone handle one of your real visit types end to end, prescription draft included.

## When the free EHR scribe is the better fit

Here's the verdict, no hedging.

Use the free embedded scribe if you're an athenaOne customer, your visits are mostly straightforward, and note generation is the main thing you want off your plate. Free, in your EHR, with automatic write-back is genuinely hard to beat for that profile. Paying for a standalone on top would be paying twice for the note, to get features you've just told yourself you don't need. Don't do that.

Use a standalone if you're not on that EHR (then the free option doesn't exist for you), or you need the prescription draft, ICD-10 suggestions, or multilingual capture, or you want a tool that doesn't chain you to one vendor's ecosystem. For a practice with a multilingual patient mix, a heavy prescribing load, or a non-athenahealth EHR, the standalone isn't a luxury. It's the only one of the two that fits.

The mistake cuts both ways: buying a standalone on reflex when the free tool already covers you, or assuming the free tool covers you when half your visits run in another language and end in a prescription. Match the tool to the work.

## How to decide without overthinking it

1. Are you on athenaOne, or another EHR adding a free scribe? If no, the standalone question answers itself. You need an EHR-agnostic tool.
2. List what you want automated. If it's "just the note," lean free. If it includes prescriptions, coding, or languages, lean standalone.
3. Check the audio policy on both. Free doesn't mean private. Ask the EHR vendor what happens to your visit audio and for how long. Ours: never stored, processed in memory and discarded at note draft.
4. If you're leaning standalone, trial it on real visits, so you're comparing your actual workflow, not a demo.

If you want the wider field, our [best AI medical scribes comparison](../best-ai-medical-scribes/) covers the self-serve market, and [Abridge alternatives](../abridge-alternatives/) covers the opposite end, when an enterprise tool is more than you need. The full price ladder, no asterisks, is on the [pricing page](../../pricing/).

We'll make the cheap recommendation when it's the right one: if a free embedded scribe covers your workflow, take it. If it doesn't, book a short demo and run the 7-day trial on a real clinic week, then let the gap, or the absence of one, make the call for you.

---

## DPDP Rules 2025: The Clinic Compliance Timeline
https://patientsquare.com/in/blog/dpdp-rules-2025-clinic-timeline/
Published 2026-05-05 · Updated 2026-09-29 · Tags: dpdp, compliance, india, privacy

When each DPDP obligation hits your clinic, from the Nov 2025 notification to the May 2027 deadline, plus the questions to ask any AI tool handling patient PHI.

No, not broadly. The Act uses a negative-list model: cross-border transfer is allowed except to jurisdictions the central government specifically restricts. There is no blanket data-localization mandate in DPDP itself. Sector regulators may impose their own localization rules, but those do not come from the DPDP Act.

Your clinic has until 13 May 2027 for most of what the DPDP Rules 2025 ask, and a couple of milestones land sooner. The Rules were notified on 13 November 2025, but they switch on in stages, not all at once. So you don't need panic. You need a calendar. This page is that calendar: what hits when, what a clinic actually has to do, and how to vet any AI tool that touches patient data before the deadline arrives.

One honesty note before the dates. This is reporting, not legal advice, and the Data Protection Board is still standing up its machinery. Treat the schedule below as the published one and confirm specifics for your practice with counsel. Want the broader obligation primer instead of a dated timeline? Our [DPDP Act for clinics guide](../dpdp-act-clinics-guide/) walks the obligations themselves. This page is purely about timing.

> **Key takeaways**
>
> - The DPDP Rules 2025 were notified 13 November 2025 and commence in phases, not on day one.
> - Definitions and the Data Protection Board provisions are already live. The Consent Manager rule follows on 13 November 2026.
> - The bulk clinic obligations, notice, consent, breach, retention, and patient rights, take effect on 13 May 2027.
> - Breach rule: notify patients and the Board without delay, then file a detailed report to the Board within 72 hours.
> - The operative 2002 medical ethics code requires three-year retention for indoor patient records; it does not set a blanket three-year outpatient period. The NMC 2023 regulations remain in abeyance.

## The phased timeline, with real dates

The thing most coverage gets wrong is treating "DPDP is here" as a single switch. It isn't. The DPDP Act 2023 got Presidential assent on 11 August 2023; the Rules that make it operational were notified on 13 November 2025 (through Gazette notifications G.S.R. 843 to 846(E)). And the Rules themselves commence in three waves.

| Phase | Date | What switches on | What a clinic does |
|---|---|---|---|
| On notification | 13 Nov 2025 | Definitions (Rules 1, 2) and Data Protection Board constitution and functioning (Rules 17–21) | Nothing operational yet; the enforcement body is being built |
| One year out | 13 Nov 2026 | Consent Manager framework (Rule 4): registration, eligibility, obligations | Understand how Consent Managers will mediate consent; plan for it |
| Eighteen months out | 13 May 2027 | The bulk: notice, consent, security safeguards, breach reporting, retention and erasure, children's data, data-principal rights, cross-border (Rules 3, 5–16, 22, 23) | This is your real deadline; the consent-and-rights build must be done |

The main deadline is 13 May 2027. Before then, clinics need time to build and review their consent workflow, breach process, and vendor due diligence. Tools selected today should support those processes.

## What a clinic has to do, in plain terms

When the bulk obligations land, a clinic, as a Data Fiduciary, owes its patients (the Data Principals) a specific set of things. None of it is exotic. Most of it is good practice you could start tomorrow.

Consent has to be done properly. That means consent that's free, specific, informed, unconditional, and unambiguous, with an itemised notice telling the patient what you collect and why, purpose by purpose. A bundled, take-it-or-leave-it checkbox doesn't clear the bar.

Then purpose limitation. Use the data for the purpose you stated, and not for whatever else later turns out to be convenient.

Breach reporting is the one to get exactly right, because it's so widely misquoted. Under Rule 7 you notify affected patients without delay, and you notify the Data Protection Board without delay, and then you file a detailed report to the Board within 72 hours (or longer if the Board allows). So the "72 hours" floating around is the detailed-report clock. The first alarm, to patients and to the Board, is immediate.

Patient rights come next. A patient can ask for a summary of their data and how it's processed, request correction or completion, request erasure, nominate someone, and use a grievance-redress route you're required to publish.

And children's data. Processing a child's data (under 18) needs verifiable parental or guardian consent, and you can't run tracking or targeted advertising to children.

Here's one thing you don't have to do. The time-bound three-year retention written into the Rules applies to large platforms, big social media, e-commerce, online gaming, not to a clinic. Your retention is governed by purpose limitation plus your sector's record-keeping rules. Which brings us to the question every doctor asks next.

## How long must you keep records, and which rule governs?

The Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations 2002 are the operative rules. Regulation 1.3.1 requires indoor patient records to be maintained for three years from the start of treatment; it does not set the same period for all outpatient records. Regulation 1.3.2 requires requested records to be issued within 72 hours. The NMC Registered Medical Practitioner (Professional Conduct) Regulations 2023 were held in abeyance. Set an outpatient retention schedule using the applicable legal, specialty, contractual, and operational requirements.

DPDP and the record-keeping rules pull in the same direction. Keep what you need for as long as the purpose (and the medical-council expectation) requires, then erase it. A tool that lets you export or delete any patient record on demand makes both obligations easier to honour.

## And no, DPDP doesn't force your data to stay in India

Worth clearing up, because it drives a lot of nervous procurement. The DPDP Act uses a negative-list model for cross-border transfer (Section 16): data may be transferred to any jurisdiction except those the central government specifically restricts by notification. No blanket data-localization mandate sits in the Act itself. Individual sector regulators may impose their own localization rules, and those still apply, but they don't flow from DPDP. So "DPDP requires my patient data to live in India" is an overstatement. Where your data lives is a fair buying question. It just isn't one the statute decided for you.

## The DPDP question set for any AI tool

If anything touches patient data, a scribe, an EMR, a billing add-on, run it through these before May 2027 quietly arrives:

| Ask the vendor | A DPDP-aligned answer |
|---|---|
| How do you handle consent and purpose limitation? | Consent-first, purpose-bound, with a clear notice; not buried in a ToS |
| What happens to visit audio, and when is it deleted? | A one-sentence answer with a timeline; ideally "never stored" |
| How would a breach be reported to me? | A defined process matching Rule 7's without-delay and 72-hour structure |
| Can I export or delete any patient record? | Yes, anytime, no ticket; the data belongs to the practice |
| Where does the data live, and who can access it? | A clear location, role-scoped and logged access |

Here's how we answer, on the record. The AI Medical Scribe is one module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Data is handled to DPDP Act 2023 standards, consent-first and purpose-limited. Visit audio is processed in memory and discarded the moment the note drafts, so there's no audio archive to breach or produce. Notes are encrypted (TLS 1.2+ in transit, AES-256 at rest), access is role-scoped and logged, and the notes belong to your practice, export or delete any visit anytime. A SOC 2 Type II audit is underway, that phrase exactly. The full posture is on our [security page](../../security/). One honest line we won't blur: ABDM integration is on our roadmap, not live; we never claim to be ABDM-compliant, because we're not yet. If you want to walk the five questions against a live tool, [review the current Practice Copilot scope](../../products/practice-copilot/) and ask each one out loud. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## What to do this quarter

You have until 2027 for the big obligations, so spend the runway building instead of bracing for it:

1. Map your patient-data flows. What you collect, why, where it goes, who can see it. You can't write a consent notice for data you haven't mapped.
2. Draft the consent notice and patient-rights process before the 13 May 2027 deadline. Review them with your team and counsel before using them with patients.
3. Vet every data-touching vendor with the five questions above, and get the audio-retention answer in writing.
4. Apply the operative 2002 rules’ three-year retention requirement to indoor patient records. Set an outpatient retention policy with counsel, accounting for other applicable duties, and make sure requested records can be produced within 72 hours.
5. Plan for the Consent Manager framework arriving 13 November 2026, ahead of the bulk deadline.

The companion [India AI scribe buyer's guide](../ai-medical-scribe-cost-india-buyers-guide/) covers price, language, and data-handling questions. Ask each vendor the five DPDP questions directly and evaluate with synthetic scenarios. Review consent, retention, and privacy terms before using patient data.

---

## How to Write a Mental-Health SOAP Note (with a Rubric)
https://patientsquare.com/us/blog/how-to-write-a-mental-health-soap-note/
Published 2026-05-05 · Tags: soap-note, mental-health, behavioral

A field guide to writing behavioral-health SOAP notes: what each section carries, a worked therapy example, and a 6-point rubric to grade your drafts.

A mental-health SOAP note is a structured progress note organized into four sections: Subjective (what the client reports), Objective (what you observe), Assessment (your clinical formulation), and Plan (next steps). It documents a therapy session in a format payers and clinical supervisors can read quickly, and it applies to psychiatry, counseling, social work, and psychology.

A mental-health SOAP note has four sections: Subjective (what the client reports), Objective (what you observe), Assessment (your clinical formulation), and Plan (next steps). The format comes from medicine. In behavioral health, though, the Assessment section carries more weight than it does in a primary-care visit. Getting that section right is the difference between a note that defends your work and one that just records a conversation.

Below is how each section works in a therapy context, a worked example you can grade, and a rubric for evaluating any AI draft against your own sessions.

> **Key takeaways**
>
> - SOAP = Subjective, Objective, Assessment, Plan. In behavioral health, Assessment is where your clinical reasoning goes, not just a diagnosis code.
> - No law specifies the SOAP format. What matters is that your note supports the diagnosis, treatment goal, and client progress.
> - The worked example below shows a 50-minute CBT session for depression. Grade it against the rubric to see what a clean draft looks like.
> - A 2023 National Council survey of 750 behavioral-health workers found 93% had experienced burnout; 68% of those in direct care said paperwork takes time from clients.
> - When grading an AI-generated SOAP note, test the Assessment hardest. Any scribe can transcribe Subjective; Assessment is where they separate.

## What each SOAP section carries in a behavioral-health context

The four-section structure comes from medicine, but what you put in each bucket shifts when the visit is a therapy session rather than a physical exam.

**Subjective** is the client's voice. Chief complaint, mood in their words, recent stressors, sleep, whether homework was completed, and anything else they bring to the room. Include direct quotes when the quote carries clinical weight. "I can't stop thinking about it" tells a supervising clinician something a paraphrase can blur. Interpretation stays out of here; that belongs in Assessment.

**Objective** is what you observe and measure. Appearance, behavior, affect as it presents, and formal measurement when you ran it: PHQ-9 score, GAD-7, Columbia severity rating, MMSE. If a family member was present and said something relevant, it goes here. Objective is the section you could describe to a colleague who wasn't in the room. Risk indicators like eye contact, psychomotor activity, and speech pattern live here too, not in Subjective.

**Assessment** is your clinical reasoning. In medicine, Assessment is usually a differential or a diagnosis. In behavioral health it goes further: the working diagnosis, your formulation of what's driving the presentation, where the client sits in the treatment arc, and the risk picture. This section takes the most clinical skill to write and the most discipline to write clearly. A vague Assessment undermines everything else in the note.

**Plan** is concrete. Homework assigned, techniques agreed on, medications continued or adjusted, referrals made, next appointment scheduled, and what you'll focus on next session. A dropped plan item is a missed action. Not a style issue. If you decided something in session, it belongs in Plan.

Per StatPearls, SOAP was developed for medical settings but carries over to therapy because the four sections map to what happens in any clinical encounter. That said, know what a SOAP progress note is NOT. Under 45 CFR § 164.501, "psychotherapy notes" in HIPAA's technical sense are a clinician's separate private notes kept for their own use, distinct from the treatment record. A SOAP progress note goes in the chart. It is NOT a psychotherapy note under HIPAA. It's still protected health information, just without the heightened disclosure restrictions. Our [psychotherapy notes examples guide](../psychotherapy-notes-examples/) covers that distinction in full.

## A worked mental-health SOAP example (depression, CBT session)

Below is a SOAP note for a routine 50-minute individual session. This is an illustrative example we wrote to show the shape, not a real client record. Read it, then grade it against the rubric that follows.

---

**Subjective:** Client presented on time. Reports mood has been "pretty low" most of the week, rating it 5/10 compared to 6/10 at the last session. Describes continued difficulty getting out of bed before 10 a.m. and two instances of crying "for no real reason." States she completed the thought record from last session on one occasion but skipped it twice when she was "too tired to care." Denies suicidal ideation or self-harm. Reports no changes to medication adherence (sertraline 100 mg daily). Notes a conflict with her manager at work that she found "humiliating," which she identifies as a trigger.

**Objective:** Client was well-groomed and appropriately dressed. Affect was dysthymic but reactive: she smiled twice during the session, including a brief laugh when recounting an exchange with a co-worker. Speech was normal in rate and volume. Psychomotor activity appeared within normal limits. PHQ-9 completed at session start: score 13 (moderate depression), unchanged from two weeks ago. No signs of formal thought disorder. Eye contact maintained throughout.

**Assessment:** Client continues to meet criteria for major depressive disorder, moderate (F32.1). Presentation is consistent with the cognitive-behavioral model; she is identifying automatic thoughts and beginning to challenge them, though avoidance behaviors (particularly the incomplete thought-record homework) are still active. The workplace conflict serves as an activating event that appears to reinforce the core belief "I am incompetent." Risk level is low: no suicidal ideation, no self-harm, stable support system. Functional impairment is primarily occupational and sleep-related. Treatment progress is slow but directional; avoidance remains the primary target.

**Plan:** Continue sertraline 100 mg daily as prescribed by prescribing physician; no medication adjustments this session. Completed thought-record exercise in session using the workplace incident as the activating event; client to complete one thought record independently before next session. Discussed behavioral activation for morning routine; agreed on a graduated approach starting with a 9 a.m. alarm for the next week. Next session to focus on the workplace belief pattern and behavioral activation review. Follow-up individual session in one week. Risk safety plan reviewed and confirmed in place.

---

That Assessment is doing the work a good behavioral-health note should do. It names the diagnosis, formulates the presentation using the treatment model, states a risk level, and describes where the client is in treatment. The Plan ties directly back to what happened in session: the thought record reviewed is the same one assigned as homework. A weak note pastes a generic diagnosis into Assessment and ends Plan with "continue therapy."

## A 6-point rubric to grade any behavioral-health SOAP note

Use this on a real session you ran. Grade 0 to 2 on each point: 0 fails, 1 is acceptable, 2 is good.

| # | What to check | What 2 points looks like |
|---|---|---|
| 1 | **Faithfulness** | Every clinical fact in the note was actually said or observed in session. Nothing invented; no finding the client never reported. |
| 2 | **Section discipline** | Subjective, Objective, Assessment, Plan stay separated. The client's words don't drift into Objective; your reasoning doesn't land in Subjective. |
| 3 | **Assessment depth** | The Assessment has a diagnosis, a formulation, and a risk statement. It connects the session to the treatment arc, not just the day's complaint. |
| 4 | **Plan-session alignment** | Every assignment and decision from session appears in Plan. Nothing dropped. The homework in Plan matches the homework discussed in session. |
| 5 | **Uncertainty handling** | When something was ambiguous in session, the note says so rather than guessing a confident wrong answer. |
| 6 | **Edit load** | You can correct the draft in under a minute. If cleanup takes longer than writing it fresh would have, it scores 0. |

A perfect score is 12. Below about 9 on your real sessions and you're buying editing work instead of time. Point 1 catches the most drafts because a confident hallucinated detail is harder to catch than a blank field; you have to already know it's wrong to delete it. Point 3 is the hardest. Getting the Assessment to reflect clinical reasoning, not just session content, requires the model to understand the treatment context, not transcribe the conversation.

## How SOAP compares to DAP and BIRP in behavioral health

SOAP is the cross-discipline default, but behavioral health uses two other formats you'll see in the field. Knowing the difference matters when you're evaluating whether a scribe can produce what your practice needs.

| Format | Sections | What it emphasizes | Where it fits |
|---|---|---|---|
| **SOAP** | Subjective, Objective, Assessment, Plan | Keeps client-report, clinician-observations, and clinical-reasoning in separate buckets | Cross-discipline default; the only one with a standalone Assessment section |
| **DAP** | Data, Assessment, Plan | Folds report and observation into one Data block; faster to write | Solo and private practice prioritizing speed |
| **BIRP** | Behavior, Intervention, Response, Plan | Separates what you did from how the client reacted | Medicaid, substance-use treatment, group and community behavioral health |

The practical difference: SOAP forces you to separate your observations from your reasoning, which matters when clinical judgment is being reviewed. DAP is faster but collapses that distinction. BIRP is the format payers in managed behavioral health often want because the Intervention and Response sections make medical necessity plain to a reviewer. Our full breakdown of BIRP is in the [BIRP note guide](../birp-note/), and if DAP is your format, the [DAP note guide](../dap-note/) goes the same depth.

## Why documentation pressure is higher in behavioral health

Because the note is the only record of a relationship. A primary-care visit has vitals, labs, and an exam. A therapy session has what was said, what you observed, and what you decided to do about it. A note that doesn't capture the formulation and plan accurately affects continuity of care when a colleague covers, and it can unravel a treatment-plan review or a managed-care audit.

A 2023 survey by the National Council for Mental Wellbeing, conducted by The Harris Poll across 750 behavioral-health workers, found 93% had experienced burnout and a third said they spend most of their time on administrative tasks rather than direct care. Sixty-eight percent of those providing direct care said paperwork takes time away from clients. That's the real cost of a broken documentation workflow, and it's the case for anything that actually fixes it.

The catch is that the solution has to match the setting. Progress notes in a standard outpatient practice have a fairly clean workflow. Notes that carry the psychotherapy-notes status under HIPAA need careful handling. Our [psychotherapy notes examples guide](../psychotherapy-notes-examples/) covers where that line falls.

## Where an AI scribe fits with behavioral-health SOAP notes

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. The ICD-10 codes are suggestions, not automated coding. The Rx draft is a draft only.

For behavioral health, two things matter more than the feature list. First: the audio. Visit audio is processed in memory and discarded the moment the note is drafted. There's no recording archived, nothing to retain or subpoena. Second: the Assessment section. Our default draft gives you a clinical Assessment, but on a complex therapy session with an evolving formulation, plan to edit it. The scribe captures what was said and what it can infer; your clinical judgment about where a client is in treatment is yours to add.

Security posture: notes are encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice. Export or delete any visit at any time. We maintain HIPAA compliant safeguards and offer a BAA to every customer. Our SOC 2 Type II audit is underway. Details are on our [security page](../../security/).

Run the six-point rubric above on your own sessions. Assessment is the hardest dimension. It's the one that separates a note you sign in 90 seconds from one you're rewriting. If a draft clears about 9 out of 12 on your real caseload, it's saving time. For the rubric applied across medical specialties, the [SOAP note quality guide](../ai-scribe-soap-note-quality/) covers the same six dimensions.

## Grade a real session this week

A worked example and a rubric are only useful with actual notes in front of you. A vendor demo makes every scribe look competent. Your Thursday caseload with a resistant client and a rushed session is the test that counts.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to see a structured SOAP note appear about two minutes after a sample visit. Then run the 7-day free trial on three real sessions and score each against the six rubric points above. Assessment hardest. If the notes clear about 9 out of 12, the tool is earning its place.

---

## Do AI Medical Scribes Reduce Burnout? The 2026 Evidence
https://patientsquare.com/us/blog/do-ai-scribes-reduce-burnout/
Published 2026-05-04 · Tags: burnout, ambient-ai, evidence, clinical-informatics

A clinical informatics read on whether ambient AI scribes actually cut physician burnout, what the 2024-2026 studies show, and where the evidence stops.

The early evidence is encouraging but not conclusive. A 2025 JAMA Network Open pilot found burnout among surveyed ambient-AI users fell from 52.6% to 30.7% over twelve weeks, but response rates were low and respondents self-selected. Documentation time saved is well measured; a durable, causal cut in burnout is still being established.

Short answer: probably yes for the documentation slice of burnout, and the early numbers are good, but the evidence is younger and softer than the marketing suggests. Ambient AI scribes clearly save documentation time at scale. Whether that translates into a durable drop in burnout, for your clinicians specifically, is a question the studies are still answering. Here is what the 2024 to 2026 evidence actually supports, and what it does not.

> **Key takeaways**
>
> - Time saved is the strongest claim: one large medical group logged an estimated 16,000 hours saved across 2.5 million ambient-AI visits.
> - Burnout reduction is promising but early: a 2025 pilot saw 52.6% to 30.7% among surveyed users, with caveats that matter.
> - Burnout was already falling before AI scribes went mainstream, so the trends overlap.
> - An AI scribe treats the documentation slice of burnout, not the whole disease.

## Where is the burnout actually coming from?

Size the problem first. That sets the ceiling on what any tool can fix. In a 2023 JAMA Network Open study of 307 primary care physicians, the median 30-minute visit generated 36.2 minutes of electronic health record time. The note now outlasts the appointment it describes. Go back to the 2016 Annals of Internal Medicine time-and-motion study and the pattern is older than the AI hype: for every hour of direct patient face time, physicians spent nearly two more hours on EHR and desk work, plus one to two hours of after-hours work most nights.

That after-hours work is the part clinicians feel as burnout, and it has a price. A 2019 Annals of Internal Medicine model estimated the cost of physician burnout at roughly $4.6 billion a year nationally, about $7,600 per employed physician, driven by turnover and reduced clinical hours. So the documentation burden is real, and it shows up on a balance sheet. The open question is whether moving the typing to an AI moves the burnout with it.

## What does the time-saved evidence show?

This is the part with the firmest ground under it. When Kaiser Permanente's Permanente Medical Group turned on ambient AI scribes for 10,000 physicians and staff in late 2023, physicians used the tool in 303,266 patient encounters within the first ten weeks (NEJM Catalyst, 2024). The one-year follow-up reported more than 2.5 million ambient-AI-assisted encounters in roughly 14 months and an estimated 16,000 hours of documentation time saved (NEJM Catalyst, 2025).

Read those numbers the way a reviewer would. The encounter counts are hard operational data, and they are large. The 16,000 hours is an estimate at deployment scale, summed across thousands of physicians. That makes it a credible aggregate. It does not promise any single clinician a fixed number of minutes back. How much a physician edits the draft moves the figure, and so does specialty and baseline charting habit. The honest framing: ambient AI demonstrably reduces documentation time across a large population, and the magnitude is meaningful.

## What does the burnout evidence show?

The ground gets softer here. That is what you would expect for an outcome this new. A 2025 JAMA Network Open pilot across Mass General Brigham and Emory found that burnout prevalence among surveyed ambient-AI users fell from 52.6% to 30.7% at 84 days at one site. A large swing in twelve weeks. It is also the most direct burnout-specific result published so far.

The caveats are where a subject-matter read earns its keep. The pilot enrolled 1,430 clinicians, but survey response rates were low, around 22% at the Mass General Brigham 84-day mark and lower at Emory. When that few people answer, the ones who do may be the ones the tool worked for, which biases the result upward. The study measures association, not cause. And it ran at two academic systems, not as a multi-site randomized trial. None of that makes the 52.6% to 30.7% figure fake. It makes it a promising early signal you should quote with its caveats attached, rather than as a flat "ambient AI cuts burnout by 21 points."

A second reason for caution: physician burnout was already declining before AI scribes went mainstream. The AMA reported 41.9% of physicians had at least one symptom of burnout in 2025, down from 43.2% in 2024 and 48.2% in 2023. The national trend and the AI-adoption trend are rising and falling in the same window, which makes clean attribution hard. Adoption itself is real. A 2025 AMA survey found two in three physicians used health AI in 2024, up 78% in a year, with documentation the leading use case. Two overlapping trends still are not proof that one drives the other.

## So what is actually proven, and what is not?

| Claim | Evidence status |
|---|---|
| Ambient AI reduces documentation time at scale | Well supported (large operational deployments) |
| Time saved varies by specialty and clinician | Well supported (and a reason to pilot, not assume) |
| Burnout falls among users in early studies | Promising, with low-response-rate and association caveats |
| AI scribes are the cause of falling national burnout | Not established (overlapping trends) |
| AI scribes fix burnout broadly | Not claimed by serious evidence |

The pattern is consistent. The closer a claim sits to "minutes of documentation," the stronger the evidence behind it; push it toward "cured burnout" and the caveats pile up. So a vendor that tells you ambient AI eliminates burnout is ahead of the data. The one telling you it reliably cuts documentation time, and that less charting tends to help the clinicians most buried in it, is roughly where the evidence actually sits.

## What an AI scribe does not fix

Burnout is not one thing, and documentation is only one of its drivers. An ambient scribe does nothing for inbox volume, prior authorization, understaffing, moral injury, or the workload that comes from seeing too many patients in too little time. If after-hours charting is the largest stone in a clinician's shoe, removing it helps a lot. When the real load is a 2,000-message inbox or a chronic staffing gap, an AI scribe is the wrong tool for that part, and pretending otherwise just sets up a disappointed pilot.

This is also why the clinician stays in the loop. Generated notes contain errors, so every note is reviewed and signed by the physician. The time savings come from editing a near-complete draft instead of typing from a blank screen. The human is not removed from the work. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. That review step is a feature, and any product implying you can skip it is selling past the evidence.

## How to evaluate the claim for your own clinic

You can test the burnout question. Treat it as an experiment, not a brochure line. Three steps:

1. Measure your baseline first. Pull your after-hours EHR time and your charting backlog before you switch anything on. You cannot detect an improvement you never quantified.
2. Pilot on your real patient mix. Time saved swings with specialty and case complexity, so run the tool on your own visits for a few weeks rather than judging from a demo. Ask every vendor to document the trial setup, start, cancellation, and data-handling terms before you begin.
3. Watch documentation time and after-hours charting. Those are the metrics the evidence actually supports. If they drop and your clinicians feel the difference, that is your signal. A promised burnout-score miracle is a hypothesis to verify, not a result to expect.

The fair read in 2026: ambient AI scribes are a strong, evidence-backed tool for the documentation half of burnout, with early and promising signals on the well-being half that deserve a few more years of harder studies. For a young technology, that is a genuinely good place to be, and a more honest thing to tell a clinician than a slogan. To assess the workflow, review the [published product scope](/us/products/practice-copilot/); the [breakdown of how an AI scribe works](../what-is-an-ai-medical-scribe/) covers the mechanics.

---

## IRDAI Cashless Rules: The 1-Hour and 3-Hour Timelines
https://patientsquare.com/in/blog/irdai-cashless-rules-doctors/
Published 2026-05-04 · Tags: irdai, cashless, claims, documentation, india

IRDAI full form, the cashless 1-hour and 3-hour timelines from the 2024 Master Circular, and where a clinic's notes fit on that clock.

IRDAI is the Insurance Regulatory and Development Authority of India, the statutory regulator under the Ministry of Finance constituted by the IRDA Act of 1999. It licenses insurers and Third Party Administrators and writes the cashless rules a hospital works against, including the Master Circular on Health Insurance Business dated 29 May 2024.

If you run the front desk at a clinic or hospital, IRDAI is the name behind every cashless clock you work against. The full form is the Insurance Regulatory and Development Authority of India, the statutory regulator that sets the rules insurers and TPAs follow. Its 29 May 2024 Master Circular put hard timelines on cashless: roughly one hour for an authorisation decision, three hours for discharge approval. Most people searching this are patients checking their own claim. This page is the clinician's slice: the timelines, and the one place your team actually touches the chain, the note.

> **Key takeaways**
>
> - IRDAI full form: Insurance Regulatory and Development Authority of India, the statutory regulator behind the cashless rules.
> - The IRDAI Master Circular of 29 May 2024 sets a one-hour cashless authorisation clock and a three-hour discharge authorisation clock.
> - Miss the three-hour discharge clock and the insurer bears the extra hospital charges from its shareholder's fund.
> - Insurers are told to strive toward 100% cashless, a stated direction, not an absolute guarantee.
> - Claims cannot be rejected for want of documents. Good notes buy speed on the clock, not protection from a paperwork rejection that the rules already forbid.

_Source: IRDAI Master Circular on Health Insurance Business, 29 May 2024 (IRDAI/HLT/CIR/MISC/77/05/2024)._

## What is IRDAI, and why does it set your cashless clock?

IRDAI is the Insurance Regulatory and Development Authority of India. It is the autonomous statutory body under the Ministry of Finance, set up by the IRDA Act of 1999, that regulates the whole insurance industry. Insurers answer to it. TPAs are licensed by it. And the cashless timelines your discharge desk runs against are written by it.

One document carries most of the weight right now. The IRDAI Master Circular on Health Insurance Business, dated 29 May 2024 (reference IRDAI/HLT/CIR/MISC/77/05/2024), pulled 55 earlier circulars into a single rulebook and reset how cashless is meant to run. When someone at your clinic argues about a cashless deadline or a document demand, that circular is the document to point at.

For the rest of the vocabulary on a pre-auth form, the [plain-English TPA and IRDAI glossary](../tpa-full-form-cashless-explained/) covers what each term means and who it is to your clinic. This page stays on the timelines and the documentation role.

## The two cashless clocks the circular put in place

The 29 May 2024 circular set deadlines on two stages of a cashless claim. Both decide how long a patient sits on a bed waiting for an approval, so both land on your desk.

| Stage | IRDAI deadline | What the circular says happens on a delay |
|---|---|---|
| Cashless authorisation request | Decision immediately, not more than **one hour** of receipt | The pre-auth, built from your note, has to be approvable on first read |
| Final discharge authorisation | Within **three hours** of the hospital's request | Extra hospital charges from the delay are borne by the insurer from its shareholder's fund |

The wording on the discharge clock matters, so here it is plainly. The insurer grants final authorisation within three hours of the discharge authorisation request from the hospital. If there is any delay beyond three hours, the additional amount charged by the hospital is borne by the insurer from its shareholder's fund. That last part is the teeth. The cost of a slow approval moves to the insurer, not the patient and not the hospital.

There is a third date worth knowing, though it is not a cashless clock and should not be confused with one. The circular told insurers to put the necessary systems and procedures in place immediately and not later than 31 July 2024. That was a one-time setup deadline for insurers, already long past. The one-hour and three-hour rules are the live, recurring clocks your desk works against every day.

## Does IRDAI require 100% cashless? Read it carefully

This is where a pricing-page summary tends to overreach, so be exact. The circular says every insurer shall strive to achieve 100% cashless claim settlement in a time-bound manner, and that claims settled through reimbursement should be the exception rather than the norm. To back that, each insurer must have a board-approved policy on quality standards and benchmarks for empanelment of hospitals and health care providers.

Notice the verb. It is "strive to achieve," not "must achieve." This is a stated direction the regulator is pushing insurers toward, not a guarantee that every claim clears cashless. A patient who quotes "100% cashless" at your desk is half-right: it is the goal IRDAI set, but coverage, empanelment, and policy terms still decide the individual case. So when a cashless request is declined, the answer is rarely "the rule was broken." Usually it is a policy term doing exactly what it was written to do.

## Where your documentation sits on the clock

Walk a cashless claim backwards and you land on the note. The insurer decides on a pre-authorisation. The pre-auth is assembled by the hospital's insurance or TPA desk. And that desk builds it from what the treating doctor wrote: the diagnosis, the clinical indication for the treatment, and the plan. The note is the source document for the entire request.

So here is the honest, narrow benefit, and it is about speed, not rejection. Because IRDAI bars rejecting a claim for want of documents, a clean note does not "stop your claims from being rejected for paperwork." The rules already forbid that bounce. What a complete, internally consistent note does is hand the pre-auth desk a request that is approvable on first read, with the indication and findings already on the page. That is what lets a request clear the one-hour and three-hour clocks without a round of queries. Faster, cleaner cashless. Fewer documentation back-and-forths. That is the real mechanism, and it is worth being precise about it.

The difference shows up at the desk, not in whether a covered claim eventually pays.

| | Thin or inconsistent note | Complete, consistent note |
|---|---|---|
| What the pre-auth desk receives | Missing indication, diagnosis that does not match the plan | Indication, findings, and plan already on the page |
| Effect on the one-hour clock | Query first, decision later | Approvable on first read |
| At discharge | Summary that invites a last-minute hold | Summary that holds together under the three-hour clock |
| What it cannot do | A thin note never makes an excluded treatment covered | A clean note never lifts a sub-limit or waiting period either |

That last row is the line no honest tool crosses. A complete note does not lift a sub-limit, waive a waiting period, or cover an excluded treatment. Those are insurance terms, decided by the insurer against the policy, and no note quality moves them. The note affects how fast and how cleanly a covered, admissible claim gets processed. It does not decide admissibility. The same honest line on the revenue side is drawn in [can better notes cut claim denials](/us/blog/ai-scribe-claim-denials-documentation/), and the full pre-auth chain is walked step by step in [how notes affect cashless approvals](../ai-scribe-cashless-claim-documentation/).

## Where an AI scribe fits, and where it does not

Let's be plain about the product behind this site and draw the boundary hard. Patient Square is an AI clinical platform; the AI Medical Scribe by Patient Square is its ambient scribe module, and that module is what does the work here. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit.

Now read what is not in that sentence. It does not submit claims. It does not file pre-authorisations. It does not connect to any TPA, insurer, or hospital claims system. There is no claims rail here, on the roadmap or off it. The scribe writes the clinical note, full stop. The benefit to cashless is upstream and indirect: a complete, consistent note is better raw material for whoever prepares the pre-auth, so the request is cleaner and clears the IRDAI clock with fewer queries. The ICD-10 outputs are suggestions for your coder or billing desk to confirm, not a coding engine and not a billing submission.

For an Indian OPD, a few things matter in practice. The scribe captures English, Hindi, and 20+ Indian languages, including the Hindi-English mixing of a real consult, and the note always comes back in clean clinical English. Visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. That is the whole claim, and it is deliberately small: better notes in, faster and cleaner pre-auth out. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## The short version, and where to look next

IRDAI is the Insurance Regulatory and Development Authority of India, the regulator behind your cashless rules. Its 29 May 2024 Master Circular puts a one-hour clock on cashless authorisation and a three-hour clock on discharge authorisation, with the insurer bearing the extra charges from its shareholder's fund if it overruns the three hours. Insurers are told to strive toward 100% cashless, and claims cannot be rejected for want of documents. The one place your clinic touches all of it is the note, where a complete record means a faster, cleaner pre-auth, not a magically approved one.

If cashless queries cluster on missing indications or inconsistent summaries, audit a sample of queried records for the indication, findings, and treatment plan. Compare the insurer's request with what the clinical record actually contains. Use synthetic examples when discussing documentation tools with vendors; the [security page](../../security/) describes Patient Square's data handling.

---

## AI Medical Scribe vs Human Scribe: The 2026 Cost and Turnover Math
https://patientsquare.com/us/blog/ai-scribe-vs-human-scribe-cost/
Published 2026-05-01 · Updated 2026-07-22 · Tags: ai-scribe, human-scribe, pricing, comparison

A human scribe runs $33k-$49k a year before training and turnover. An AI scribe runs about $79 a month. Here is the honest staffing-economics comparison.

Per Salary.com (June 2026), the average US medical scribe salary is about $41,000 a year, with most landing between roughly $33,000 and $49,000 before payroll taxes, benefits, recruiting, and training. That's the line item. The hidden cost is re-hiring, because scribing is overwhelmingly a temporary, pre-med job people leave within a year or two.

A human medical scribe costs about $41,000 a year in salary alone, most of them landing between roughly $33,000 and $49,000 before benefits, recruiting, and training. An AI scribe costs about $79 a month, near $948 a year. So the AI runs roughly a fortieth of the salary. That's the headline gap. But salary is only part of it. Turnover is the bigger bill, because most human scribes are pre-med students who leave for school within a year or two, and you pay to recruit and train the next one every time.

This is a fit-and-cost page, not a "humans are obsolete" pitch. A good scribe does things software won't. Below: the salary numbers (sourced), the turnover problem nobody puts on the invoice, the per-note math, and when a human scribe is genuinely the better call.

> **Key takeaways**
>
> - A US medical scribe averages about $41,000 a year in salary (Salary.com, June 2026), with most between roughly $33,000 and $49,000, before payroll taxes, benefits, recruiting, and training.
> - Practice Copilot starts at $79 per clinician per month (annual Assist), about $948 a year, roughly a fortieth of the salary line.
> - Scribing is largely a pre-med stepping-stone job, so practices re-hire and re-train often. That recurring cost never shows on the salary slip.
> - A human scribe still wins when you need a person who does more than document. For the note alone, the AI is far cheaper and doesn't quit.

## What does a human medical scribe actually cost?

Start with the number you can see. Per Salary.com's June 2026 benchmark, the average US medical scribe earns about $41,000 a year, with the middle of the range running roughly $37,000 to $45,000 and the wider band landing between about $33,000 and $49,000. That's salary. On top of it sit payroll taxes, benefits, workspace, scheduling, and the cost of recruiting in the first place.

Then there's the part the salary line hides. For most people who do it, scribing is a temporary job, clinical hours on the way to medical or PA school. Scribe-company reviews say so plainly: turnover reads high because the workforce is college students passing through. So you don't hire a scribe once. You hire, train for weeks while they shadow, get a few productive months, and start over when they leave for school. That training time is real money. It eats your clinician's attention, drags productivity during ramp, and the recruiting cycle comes around again next year.

We're not going to put a precise turnover percentage on the page, because the figures floating around aren't from a source we'd stake a claim on. What we'll say is verifiable: the workforce is transient by design, and a tool that doesn't quit removes the re-hiring cycle entirely. If that cycle is wearing on your practice, book a demo and see what the note-only job looks like without it.

## AI scribe versus human scribe: the per-clinician cost gap

Put the two side by side for one clinician for one year.

| | Human scribe | AI Medical Scribe by Patient Square |
|---|---|---|
| **Annual cost** | ~$41,000 salary (range ~$33k-$49k), plus benefits and taxes | ~$948 ($79/mo, annual Assist) |
| **Recruiting and training** | Recurring, every time one leaves | None |
| **Turnover risk** | High; mostly transient pre-med staff | None; software doesn't quit |
| **Ramp time** | Weeks of shadowing | Short assisted setup; test during the 7-day trial |
| **What it produces** | Notes, plus flexible in-room help | A structured note, ICD-10 suggestions, a prescription draft |
| **Scales to a group** | Linearly; you hire one per clinician | Per seat, flat, no hiring |

The salary alone is about forty times the AI subscription, and even that undercounts the human cost. It leaves out benefits, taxes, and the re-hiring loop. None of this says the human does nothing. It's a question of what you're paying for. If your scribe's whole job is writing the note, you're paying $41,000 for documentation you can get for $1,068.

## The per-note math, both ways

Cost per visit makes the gap concrete. Say a clinician sees 20 patients a day, 20 days a month, 400 visits.

| | Human scribe (~$41k/yr) | AI scribe ($79/mo) |
|---|---|---|
| Annual cost | ~$41,000 (salary only) | ~$948 |
| Visits per year | ~4,800 | ~4,800 |
| Cost per visit | ~$8.54 | ~$0.20 |

Roughly $8.54 a visit against about 20 cents. Both look small next to the value of a clinician's evening, which is the comparison that actually matters. Nobody's saying a human scribe is expensive in the abstract. But for the narrow job of turning a visit into a note, you're paying about forty times more, and carrying turnover risk for the privilege.

## What an AI scribe gives you that a human doesn't

The cost case is one-sided. Capability isn't, so let's be fair about it.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription draft mirrors the plan you discussed in the visit; it's a starting point you review and sign, not a decision the software makes. Screening it for interactions and dosing stays your job, same as it is with a human scribe typing at the keyboard. The scribe saves the writing, not the clinical judgment.

It also doesn't have an off day or call in sick, and it won't leave for medical school in August. Audio is processed in memory and discarded the moment the note drafts, so there's no recording sitting in a file. The notes belong to your practice, exportable or deletable anytime. The full posture is on the [security page](../../security/). For the wider field of AI tools, our [best AI medical scribes comparison](../best-ai-medical-scribes/) is the honest roundup, and the [AI scribe versus transcription service](../ai-scribe-vs-medical-transcription-service/) page covers the other human-labor option.

## When a human scribe is the better choice (said plainly)

Here's the verdict, no hedging.

Keep a human scribe if you need a person who does more than document. A scribe who can take a verbal order to staff, chase a pending result, prep a room, or handle the unscripted parts of a visit is doing a job an AI won't. If "scribe" in your practice means "flexible clinical assistant," the documentation tool replaces one slice of that. Not the whole role. And a teaching practice that wants to give pre-med students real clinical hours has a second, legitimate reason to keep humans: the turnover you'd otherwise complain about is the point.

Go with the AI if the job is the note. When your scribe's day is mostly typing the visit into the chart, you're paying roughly forty times more than you need to, plus a recruiting cycle, for documentation a tool now does in two minutes. That's a lot of practices, honestly. They hired scribes purely to escape pajama time.

So it comes down to scope. A human can do more. An AI does the one thing far cheaper and never leaves.

## How to decide in a week

1. Write down what your scribe actually does all day. If it's 90% documentation, the math above is your math.
2. Add the hidden costs to the salary before you compare: benefits, taxes, and the re-hiring cycle. The $41k line is the floor, not the total.
3. Match the output. Note plus ICD-10 suggestions plus a checked prescription draft, so you're comparing the documentation job like for like.
4. Settle the audio question. A human scribe keeps no recording, so ask any AI vendor the same. Ours is never stored.
5. Trial on real visits. The only honest test is your own clinic day, not a demo.

The price ladder with no asterisks is on the [pricing page](../../pricing/), and the security receipts are on the [security page](../../security/). Book a short demo to see a note draft itself against your own visit type, then run the 7-day trial on a real clinic week. If your scribe's job is the note, the AI does it for a fortieth of the cost and doesn't quit in August.

---

## AI Medical Scribe vs Transcription Service: The 2026 Cost Gap
https://patientsquare.com/us/blog/ai-scribe-vs-medical-transcription-service/
Published 2026-04-30 · Updated 2026-08-29 · Tags: ai-scribe, transcription, pricing, comparison

A transcription service bills per line or per minute and turns notes around in hours. An AI scribe drafts in two minutes. The honest cost and speed comparison.

US services bill per 65-character line or per minute of audio. Published 2025-26 rate cards run roughly $0.07 to $0.16 per line (about $0.10 average) or $1.10 to $3.25 per audio minute. A busy clinic's monthly bill scales with volume, so heavy documentation days cost more, every time.

A medical transcription service bills you per line or per audio minute and sends the typed note back hours later. An AI scribe listens to the visit, no dictation, and drafts a structured note in about two minutes. The cost gap: US transcription runs roughly $0.07 to $0.16 a line or $1.10 to $3.25 a minute, while an AI scribe is a fixed monthly seat, from $79 a month. The speed gap is hours versus minutes. This page is the honest cost-and-turnaround comparison, plus when a transcription service is still the right call.

Both tools get you a clean note. They just go about it in completely different ways. Transcription keeps a human in the loop. An ambient scribe takes the loop out. Below: the real rate-card math, the turnaround gap, and the fit question.

> **Key takeaways**
>
> - US transcription services bill per 65-character line ($0.07-$0.16, about $0.10 average) or per audio minute ($1.10-$3.25), per published 2025-26 rate cards. The bill scales with your volume.
> - An AI scribe is a fixed monthly seat: from $79/clinician/month (annual Assist), unlimited notes. Past a modest volume the fixed fee wins.
> - Turnaround is the sharper gap: transcription is typically 24 hours (4-hour STAT for a premium); an AI scribe drafts in about two minutes.
> - Transcription still fits when you already dictate and want a human to clean up complex narration. For most clinics, the flat-fee, two-minute tool is faster and cheaper.

## How does a transcription service bill, and what does it add up to?

By the line or by the minute, and the bill moves with your volume. US medical transcription services publish rates on a 65-character line, the industry's standard unit, running roughly $0.07 to $0.16 per line, with about $0.10 a common average. Others bill per audio minute, roughly $1.10 to $3.25, with specialty complexity, audio quality, and turnaround speed pushing the rate up. Faster delivery costs more: a same-day STAT carries a premium over standard.

Here's what that means for a real clinic. The cost is variable, so a heavy documentation week costs more than a light one, and you're effectively renting typing by the unit. There's no point where the meter stops. A practice that documents a lot pays for documenting a lot, which is exactly backward from the practices that most need help, the busy ones. If your transcription bill creeps up with every busy Tuesday, Request your 7-day trial and see what a flat fee does to that line item.

## Transcription service versus AI scribe: the comparison that matters

Billing is one piece. The workflow is the piece that actually changes your day.

| | Medical transcription service | AI Medical Scribe by Patient Square |
|---|---|---|
| **You do** | Dictate the note after the visit | Nothing; it listens to the visit |
| **Who types** | A human transcriptionist | The software drafts it |
| **Billing** | Per line ($0.07-0.16) or per minute ($1.10-3.25) | Fixed seat: from $79/mo, unlimited notes |
| **Turnaround** | ~24 hours (4-hr STAT for a premium) | ~2 minutes after the visit |
| **What you get** | A typed note from your dictation | A structured SOAP note, ICD-10 suggestions, a prescription draft |
| **Cost shape** | Variable; scales with volume | Fixed monthly seat; unlimited notes |
| **Audio handling** | Sent to a service; retention varies by vendor and contract | Processed in memory, never stored |

It comes down to who does the typing and whether you dictate at all. Transcription keeps a person on the job, someone who can catch nuance in complex narration, and you keep dictating. An ambient AI scribe drops the dictation step. You talk to the patient, the note drafts itself, you review and sign. Transcription is a typing service you feed. The scribe is a documentation step that runs on its own.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. There's no audio file sent anywhere: visit audio is processed in memory and discarded the moment the note drafts. The note belongs to your practice, encrypted at rest (AES-256) and in transit (TLS 1.2+), exportable or deletable anytime. The full posture is on the [security page](../../security/).

## The turnaround gap: hours versus minutes

This is where the two tools aren't close. A transcription service typically promises 24-hour turnaround, with rush or STAT options pulling it down toward 4 hours for a premium rate. That means you dictate today and review tomorrow, and your chart sits open in the meantime. For a busy clinic, the queue of un-returned notes is its own quiet stress.

An AI scribe drafts the structured note about two minutes after the visit ends. The note is ready before the patient has left the parking lot. Your chart closes the same hour the visit happened, not the next day. Two minutes versus a day changes how you live with your own backlog.

## What about accuracy and control?

Let's be fair. A transcription service isn't worse, just different, and the trade isn't all in our favor.

A human transcriptionist can catch nuance an ambient model might compress: an unusual drug name in a thick accent, a complex specialty narrative, a verbatim phrasing you need preserved exactly. If your workflow depends on word-for-word human transcription, that's a real reason to keep one. The honest caveat on our side: any AI draft can mishear or compress, which is why review-and-sign is load-bearing. Our prescription drafts are drafts only. They reflect the plan you discussed, and you screen them for interactions and dosing before you sign, the same check you run on any prescription.

The control difference cuts the other way too. With transcription, you can't change the note until it comes back; with an ambient scribe, you read and edit the draft yourself in the same two minutes, so the note is final when you sign it, not a day later. For the wider field, our [best AI medical scribes comparison](../best-ai-medical-scribes/) is the honest roundup, and the [AI scribe versus human scribe](../ai-scribe-vs-human-scribe-cost/) page covers the staffing version of this same labor question.

## When a transcription service is the better choice (said plainly)

We'll give the verdict without hedging, because the honest version is the useful one.

Keep a transcription service if you already dictate and want a human in the loop. Say your workflow is built on dictation, you value a person cleaning up complex or specialty-heavy narration, or your medico-legal process depends on verbatim human transcription. A transcription service does that job, and an ambient scribe doesn't replace the human judgment in it. If you like dictating, you'll feel the loss of it.

Choose an AI scribe if you want the documentation step to disappear. If you'd rather not dictate at all, want the note in two minutes instead of a day, and want a flat fee instead of a meter, the ambient tool is the upgrade. Most clinics that dictate-and-wait today want that trade once they see it.

So: dictation plus a human, or no dictation at all. One returns your words typed up. The other writes the note while you work.

## How to decide in a week

1. Add up last month's transcription bill and divide by your note count. That's your real per-note cost to beat.
2. Time your turnaround. If notes come back the next day and that delay costs you, the two-minute tool is the fix.
3. Decide if you actually want to keep dictating. If yes, transcription fits. If you'd drop it gladly, ambient is the move.
4. Settle the audio question. Transcription sends audio to a service, and retention varies by vendor and contract. Ask any vendor where the audio goes and how long it remains available. Ours is never stored.
5. Trial on real visits. The only honest test is your own clinic day, against your own accents and pace.

The price ladder with no asterisks is on the [pricing page](../../pricing/), and the security receipts are on the [security page](../../security/). Request your 7-day trial to see a note draft itself two minutes after a visit on a real clinic week. If your transcription bill grows with every busy day and the notes still come back tomorrow, the flat, two-minute tool is the one you'll keep.

---

## The AI Medical Scribe Security Checklist Every Buyer Should Run
https://patientsquare.com/us/blog/ai-scribe-security-checklist/
Published 2026-04-29 · Tags: security, privacy, compliance, buyer-guide, trust

A 10-point checklist for vetting an AI medical scribe: audio handling, encryption, access logging, BAA coverage, and honest certification status.

The most important question is what happens to the visit audio and when it is deleted. The recording is more sensitive than the note because it holds everything the patient said before you filtered it into documentation. A vendor that processes audio in memory and discards it at note draft keeps no archive to breach or subpoena. A vendor that retains it for days or weeks keeps that surface open.

Vet an AI scribe's security the same way you'd vet anything that holds your patients' words: by what it does with the audio, what it encrypts, who can see the notes, and what it will put in writing. Run the ten checks below in order. The first one that gets a vague answer tells you most of what you need to know.

That's the whole method. The rest of this page is the checklist itself, what a good answer sounds like, and where the honest weak spots are, including ours. We sell a scribe, so read this with appropriate suspicion and test every claim during a trial.

> **Key takeaways**
>
> - The audio question decides more than any other. A scribe that keeps no recording has nothing to breach or subpoena.
> - Encryption is non-negotiable: TLS 1.2 or newer in transit, AES-256 at rest. Demand both in plain words.
> - "SOC 2 certified" is not a real claim. SOC 2 produces a CPA report, not a certificate.
> - The BAA is the legal floor. No business associate agreement, no deal, on any plan.
> - Of the ten checks, three are about audio, encryption, and access. Those three filter out most weak vendors.

## The 10-point AI scribe security checklist

Run these in order, with the vendor on the call. Write down the answers. The point isn't to collect a perfect score, it's to catch the one bad answer that ends the evaluation.

| # | Check | A good answer | A weak answer |
|---|---|---|---|
| 1 | What happens to the visit audio, and when is it deleted? | Processed in memory, discarded at note draft. No archive. | "We retain it for model improvement" with no deletion timeline. |
| 2 | Is traffic encrypted in transit? | TLS 1.2 or newer, every connection. | "Bank-grade security," no version named. |
| 3 | Are notes encrypted at rest? | AES-256 on notes and account data. | Hand-waving, or "in our cloud provider." |
| 4 | Is access role-scoped and logged? | Yes, every access logged, logs reviewable. | "Our team accesses data as needed." |
| 5 | Will you sign a BAA for a practice my size? | Yes, every customer, before any real visit. | Tier-gated, or "enterprise only." |
| 6 | Does BAA coverage reach the subprocessors that touch audio? | Yes, the speech-to-text vendors are named and covered. | "Our cloud is compliant," no subprocessor answer. |
| 7 | What's your SOC 2 status, honestly? | Type II underway / report on request, stated plainly. | "SOC 2 certified" (no such thing). |
| 8 | Is my audio or note text used to train models? | A written answer, separate for audio and text. | "We follow applicable law." |
| 9 | Can I export and delete any visit myself? | Yes, anytime, and you can test it in a trial. | Export by support request, delete unclear. |
| 10 | What happens to my data if I cancel? | Return or destruction, with a timeline, in the contract. | Buried in a ToS, or silence. |

Notice what's missing: accuracy percentages, "military-grade" anything, per-specialty templates, certification logos. Those decorate a slide and decide nothing about whether your patients' data is safe. Checks 1 through 4 do most of the filtering.

## Why the audio question comes first

A visit recording is the most revealing artifact an AI scribe ever touches. It holds the digressions, the names, the thing the patient immediately walked back, all the stuff that never made it into the structured note you signed. The note is the curated record. The audio is the unedited version of the same hour.

So the retention answer is the whole ballgame. If a vendor stores audio, that recording is protected health information, reachable in litigation and exposed in a breach. A vendor that processes audio in memory and discards it the moment the note is drafted has nothing to hand over. No clever encryption story beats simply not keeping the file.

Our position, stated as ours: visit audio is processed in memory and discarded once the note is drafted. There's no audio archive anywhere, not on our side and not on the practice's. If you want the cross-vendor version of this question, [what happens to your visit audio across major scribes](../ai-scribe-audio-retention/) walks through how different products answer it. Ask every vendor for a one-sentence answer with a timeline, and <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> where the audio question goes first.

## What encryption and access logging should actually look like

Checks 2 through 4 are where "trust us" meets the facts. None of these three is optional.

In transit, every connection between the capture device, the service, and your browser should run TLS 1.2 or newer. Table stakes in 2026. A vendor that won't name the version is either hiding something or doesn't know it.

At rest, notes and account data stored on disk should be encrypted with a strong, current standard. AES-256 is the common one. Ours uses AES-256 at rest, and for low-connectivity clinics, offline capture is encrypted on the device with AES-256-GCM before anything syncs.

Then access. Encryption stops outsiders; access controls stop the wrong insiders. Every read of a note should be role-scoped, every access logged, the logs reviewable. "Our team has access as needed" is the answer you don't want to hear.

The full version of our answer, what's encrypted, who can access what, what's logged, lives on the [security page](../../security/), written to be read with this checklist in hand.

## How to read a vendor's compliance claims without getting played

Check 7 is where marketing language gets loosest, so be precise here.

SOC 2 is a report, not a certificate. It's a voluntary framework from the American Institute of CPAs, and the output is a report from an independent CPA firm, not a badge. A Type II report covers how controls operated over a period, typically 3 to 12 months. So "SOC 2 certified" is a phrase the framework doesn't support. The honest claims are "Type II underway" (the audit is in progress) or "Type II report available on request" (it's done). Ours is underway with an independent assessor. We'll say that plainly and not a word more.

HIPAA isn't a certification either. No software is "HIPAA certified," because no such certificate exists. What's real is narrower: the vendor maintains HIPAA compliant safeguards, signs a BAA, encrypts PHI, and limits access. We maintain those safeguards and offer a BAA to every customer. If you want the BAA and consent mechanics in depth, our HIPAA and AI scribes guide goes there.

Then push on check 6, the one most decks skip. A BAA that covers the vendor but not the speech-to-text service their audio passes through is a half-answer. The subprocessors that touch the recording need the same coverage, named in writing. Ask which vendors are in that chain and whether each one is under the BAA. "Our cloud is compliant" is not the same sentence.

A vendor that says "we're fully compliant" and stops there has told you nothing. The ones worth trusting name the standard, name the status, and put it in writing.

## Who owns the data, and can you actually leave?

The last three checks are about exit, and they matter more than most buyers expect. A scribe holds your clinical record. If leaving is hard, the security story isn't finished, because lock-in is its own kind of risk.

So, three plain questions. Can you export any visit yourself, anytime? Can you delete any visit yourself, anytime? And when you cancel, does the contract actually spell out return or destruction with a timeline? "Your notes belong to your practice" should be a sentence the vendor will put their name on, not a vibe. We hold that notes belong to the practice, exportable and deletable any time, and we never sell or share clinical data. The full version of the exit question, with the lock-in red flags to watch, is in [who owns your AI scribe notes](../ai-scribe-data-ownership-export/).

## Where we'd tell you to look elsewhere

Honesty cuts both ways, so here's the part of the security story we don't cover. If your security model depends on the scribe writing directly into your EHR through a certified integration, on a vendor-managed audit trail living inside that EHR, or on enterprise features like SSO and SCIM provisioning across a large health system, a deeply EHR-embedded enterprise platform will fit that requirement better than we will. We don't integrate with EHRs, and we don't manage identity at health-system scale. That's a real gap for some buyers, and you should weigh it against the audio-retention advantage rather than pretend it away.

For a solo clinician or a small-to-mid practice, the calculus is simpler: the controls that actually protect your patients are the ones on this list, and the audio policy at the top of it is the one most vendors get wrong.

## How to run the checklist in practice

It's an afternoon of work, and worth doing precisely.

1. Send the ten questions before the demo. A vendor who answers in writing, in advance, is a vendor with answers. One who needs a call to "walk you through it" is buying time.
2. Make the audio answer a single sentence with a timeline. Everything else is secondary to that one.
3. Get the encryption versions in writing, TLS 1.2 or newer and AES-256 at rest, not a slogan.
4. Pin the training-data policy separately for audio and for note text. Two questions, two answers.
5. Test export and delete yourself during the trial. A function you can't exercise in a week is a function to doubt.

The line to keep in view, so you know exactly what you're vetting: the AI Medical Scribe is one module inside Practice Copilot, and it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The security posture behind that is on the [security page](../../security/), and the cleanest way to test all ten checks is a quiet week of real visits. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, put the audio question first, then use the [product page](/us/products/practice-copilot/) to review the published scope against every claim on this list.

---

## AI Medical Scribe Patient Consent: A State-by-State Map (2026)
https://patientsquare.com/us/blog/ai-scribe-patient-consent-by-state/
Published 2026-04-28 · Tags: consent, compliance, privacy, state-law, trust

Which states require all-party consent before an AI scribe records a visit, a verbal consent script you can use today, and the Sharp HealthCare lawsuit lesson.

Usually yes, and the duty comes from state recording law, not HIPAA. HIPAA lets you use patient information for treatment without a signed authorization. But an ambient scribe records the room, and eleven states require every party to a conversation to consent before it is recorded. The safe policy is to ask everywhere.

In eleven states you need every person in the room to consent before an AI scribe records the visit. Everywhere else the federal floor is one-party consent, and you are a party. The catch: that duty comes from state wiretap law, not HIPAA, and a few states flip the rule depending on whether you're in the exam room or on a video call. Get consent everywhere and the map stops mattering.

That's the answer. The reason it's worth reading the rest is that a real lawsuit just made this concrete. In late 2025 a patient sued a San Diego health system over an ambient scribe that allegedly recorded him without asking. Below: the eleven states, the exam-room-versus-telehealth wrinkle, a consent script you can say out loud tomorrow, and where the no-stored-audio question fits in.

> **Key takeaways**
>
> - Eleven states require all-party consent to record: California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington.
> - The consent duty comes from state recording law, not HIPAA. HIPAA lets you use patient information for treatment without a signed authorization.
> - A proposed class action alleges Sharp HealthCare recorded 100,000+ patients with an Abridge scribe without consent. Allegations, not findings, but the playbook is the lesson.
> - Florida treats illegal recording as a third-degree felony. The stakes aren't theoretical in all-party states.
> - A scribe that never stores audio still needs consent. Statutes regulate the act of recording, not the archive.

## Why state law, not HIPAA, decides the consent question

This trips up careful people, so start here. HIPAA permits using protected health information for treatment without a signed authorization (45 CFR 164.506). So HIPAA is not where "ask before you record" comes from. The duty to ask lives in state wiretap and eavesdropping statutes, the same laws that govern recording any conversation.

Federal law sets the floor at one-party consent under 18 U.S.C. § 2511(2)(d): a recording is lawful if one party to the conversation agrees, and the clinician in the room is a party. Eleven states raise that floor and require everyone. An ambient scribe records the visit, so in those eleven states the patient's consent isn't optional courtesy. It's the statute.

One honest caveat before the table: this is reporting, not legal advice. Statutes get amended, case law moves, and your malpractice carrier may want more than the law's minimum. Verify your state's current rule with counsel before you write a policy.

## Which states require all-party consent for an AI scribe?

Per the 50-state survey of recording statutes by the law firm Matthiesen, Wickert & Lehrer (chart dated February 2022; we fetched and read it in June 2026), eleven states require all-party consent: California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington.

You'll see "12," "13," even "15" in other guides. Nobody's wrong, exactly. The spread comes from four states with split or unsettled rules, Connecticut, Oregon, Michigan, and Vermont, and from a wrinkle that matters specifically in medicine: several statutes treat an in-person conversation differently from a phone or video one. An ambient scribe in an exam room records an in-person conversation. The same scribe on a telehealth call records an electronic one. Same tool, different statute.

| State | Exam-room visit | Phone / telehealth | Watch for |
|---|---|---|---|
| California | All parties | All parties | Strictest-state rule reaches cross-state calls (*Kearney*) |
| Delaware | All parties | All parties | Older statutes conflict; treat as all-party |
| Florida | All parties | All parties | Illegal recording is a third-degree felony (Fla. Stat. 934.03) |
| Illinois | All parties | Contested | 2014 amendment may permit participant recording of calls; treat as all-party |
| Maryland | All parties | All parties | Clear all-party statute |
| Massachusetts | All parties | All parties | Bars secret recording outright |
| Montana | All parties | All parties | Notice of recording can satisfy the statute |
| Nevada | One party | All parties | Flips by mode (*Lane v. Allstate* on calls) |
| New Hampshire | All parties | All parties | Knowing participation can count as consent |
| Pennsylvania | All parties | All parties | Clear all-party statute |
| Washington | All parties | All parties | Announcement at start of recording has a statutory path |
| Connecticut | One party | All parties (civil) | Phone recording without consent risks civil liability |
| Oregon | All parties informed | One party | Reverse flip: in-person requires informing everyone |
| Michigan | Participant may record | Participant may record | Reads all-party; case law says otherwise |
| Vermont | No statute | No statute | Unsettled, so default to consent |

Count the exam-room column and you get eleven all-party-or-informed states. Count the telehealth column and you also get eleven, but not the same eleven. Nevada swaps out, Oregon swaps in. That's the trap in every "thirteen two-party states" listicle: the number depends on which conversation you're having.

For telehealth across state lines, assume the stricter state's law applies. That's what the California Supreme Court held in *Kearney v. Salomon Smith Barney*, when a Georgia firm recorded calls with California clients and California's all-party rule reached it anyway. If you're a Portland clinic seeing a patient who's in Sacramento that morning, California is the law you plan around.

If you want the broader compliance frame around all this, the BAA, the Security Rule safeguards, the twelve questions to ask a vendor, our [HIPAA and AI scribes guide](../ai-scribe-hipaa-baa-consent/) sits one level up from this consent map.

## What the Sharp HealthCare lawsuit actually alleges

Here's why this stopped being abstract. In late 2025, a patient filed a proposed class action against Sharp HealthCare in San Diego. The complaint alleges that during a July 2025 physical exam at a Sharp Rees-Stealy clinic, an Abridge ambient AI scribe recorded the visit through a clinician's microphone-enabled device, sent the audio to a third-party cloud, and used it to draft the note, all without informing him or asking consent.

Two details make it a teaching case. First, the complaint alleges the patient later found documentation in his portal stating he had been "advised" the visit was recorded and had "consented," language the suit calls false, alleging the providers had no reliable workflow to actually obtain consent before recording. Second, it estimates more than 100,000 Sharp patients may have been recorded the same way. The suit cites California's Confidentiality of Medical Information Act and the state's wiretap statutes, and seeks class certification.

These are allegations, not proven facts, and Abridge is the named technology, not a defendant in the framing most outlets reported. But the lesson doesn't depend on the verdict. The risk wasn't the tool. It was the workflow: recording first, documenting a consent that may not have happened, at scale, in an all-party state. A scribe is only as compliant as the sentence the clinician says before pressing record.

## A consent script you can use this week

The fix is almost embarrassingly small. The consent conversation is one breath:

> "I use a tool that listens and drafts my note so I can focus on you instead of the keyboard. OK with you?"

Then one line in the chart: *"Verbal consent to ambient documentation obtained."* That's the whole workflow in a one-party state.

In an all-party state, layer documentation on top so the consent is provable, not just spoken:

1. Waiting-room and intake signage that names ambient documentation and the patient's right to decline.
2. A line on the intake form the patient acknowledges, so consent is captured before the clinician even walks in.
3. The verbal ask at the start of the visit. Every visit, no exceptions for the busy ones.
4. The chart line documenting that you asked and they agreed.

MGMA publishes a sample patient consent form for AI dictation and transcription as a member tool, if you'd rather adopt a template with a committee's fingerprints on it than draft your own. Whatever you use, the Sharp complaint is the argument for making it real: a portal note that says "consented" is worth nothing if the workflow behind it didn't ask.

## Does "we never store the audio" remove the consent requirement?

No, and we'll say it plainly because no-stored-audio is our own architecture. Recording statutes regulate the act of capturing a conversation, not the archive you keep afterward. A scribe that processes audio in memory and discards it the moment the note drafts is still recording while it listens. Consent still applies. All eleven states, every visit.

What the architecture does change is your exposure after the fact. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The visit audio is processed in memory and discarded once the note is drafted, so there's no recording to subpoena, breach, or leak later. In a case shaped like Sharp's, the thing plaintiffs reach for first, the retained audio sitting in a vendor's cloud, simply doesn't exist.

That's a smaller risk surface, not a smaller duty. You still ask. You still document. The difference shows up the day someone files. If you want to see how vendors actually differ on this, our [audio-retention comparison across major scribes](../ai-scribe-audio-retention/) puts the retention windows side by side, because almost nobody else does. And if you want to see what "audio never stored" looks like in the workflow, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and ask exactly what happens to the recording after the note is written.

## What a small practice should do before turning on a scribe

For a three-clinician practice this is an afternoon, not a project:

1. Check your state. All-party? Build signage plus an intake-form line plus the verbal ask. One-party? The verbal ask and a chart line are enough.
2. Check your telehealth footprint. If you see patients across state lines, the stricter state's law is your safe assumption. Confirm it with counsel.
3. Write the consent into the workflow, not into the portal after the fact. The Sharp complaint is what "after the fact" looks like when it goes wrong.
4. Ask your vendor what happens to the audio, and get a one-sentence answer with a timeline. Vague retention language means indefinite retention.
5. Document that you asked. Producible-on-request is the standard every recording-consent dispute eventually turns on.

We think the vendors worth your time make consent easier and the audio question boring. Ours: audio never stored, a BAA for every customer including solo practices, TLS 1.2+ in transit and AES-256 at rest, SOC 2 Type II underway, notes owned by your practice and exportable or deletable anytime. The receipts are on our [security page](../../security/), written to be read skeptically.

The honest evaluation is a week of real visits with the consent script running on every one. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and ask exactly what the audio does after the note is written, then compare the [product options](/us/compare/) against your Tuesday clinic consent workflow. Consent is your obligation in all fifty states; the right tool just makes asking the easy part.

---

## Best EMR Software in India (2026): An Honest Roundup
https://patientsquare.com/in/blog/best-emr-software-india-roundup/
Published 2026-04-28 · Updated 2026-08-29 · Tags: emr, best-emr, comparison, abdm, india

A named EMR shortlist for Indian clinics, with separate choices for a bundled EHR, an incumbent EHR, and hospital HIS/EHR procurement.

There is no universal best EMR. Compare HealthPlix, Practo Ray, and eka.care against the clinic's record, billing, pharmacy, and scheduling needs. A hospital needs a separate HIS/EHR evaluation.

The best EMR software in India is the one that handles the clinic's actual work. A clinic that runs its own billing and pharmacy has a different need from a solo OPD whose notes are late every evening. A hospital needs an HIS/EHR procurement process, not a clinic EMR shortlist.

Google Ads Keyword Planner recorded approximate 12-month India averages of 50 for "best emr software in india" and 70 for "best ehr software" in the repository's 2026-07-01 export. Those numbers indicate a small but specific buying query. The export's competition field measures advertiser competition, not organic difficulty.

## Start with the operating boundary

Use this as the first decision, before comparing features.

| Setting | Starting point | Decision to prove |
|---|---|---|
| Solo or small clinic | EMR plus documentation workflow | Can the clinician create, retrieve, amend, and review a record without extra after-hours work? |
| Clinic with billing or pharmacy operations | Clinic-management suite | Does the quoted plan cover the clinic's required operational workflows? |
| Hospital or multispecialty facility | HIS/EHR procurement | Does the candidate support the departments, continuity plan, and implementation evidence the hospital requires? |

This distinction prevents a common bad purchase. A clinic can overbuy a hospital suite because it has a long module list. A hospital can underbuy a clinic tool because a clean OPD demo hides the work of wards, diagnostics, pharmacy, billing, and recovery. Write down the care setting, the people using the system, and the handoffs that fail today before opening vendor tabs.

## The named clinic shortlist

HealthPlix, Practo Ray, and eka.care are three named options for a clinic shortlist. They are not interchangeable, and this is not a winner table. Their own published material gives different starting points for a buyer's demo.

| Candidate | Published starting signal | Good first demo question | What not to infer |
|---|---|---|---|
| HealthPlix | Its pricing page lists Pro and Elite prices and names specialty OPD EMR, billing, pharmacy, IPD, lab, and queue-related scope. | Which listed items are in the selected plan for this specialty and site? | A page label is not proof that the workflow fits the clinic or that every module is configured. |
| Practo Ray | Its subscription agreement describes calendar management, billing, EMR, and communication functions, and says some features vary by subscription plan. | Show a booking change, an invoice or payment entry, a clinical note, and the selected plan's limits. | Do not assume a feature is included before the written plan and account terms confirm it. |
| eka.care | Its doctor product page groups digital prescription, clinic management, patient engagement, and practice analytics under the product. | Show the exact record, queue, billing, reminder, and staff-permission workflow the clinic needs. | Product-category labels do not state the clinic's price, implementation effort, or every workflow detail. |
| Practice Copilot by Patient Square | The Assist plan is scribe-only. Patient Square EHR begins at Copilot. | Do you need the scribe beside the incumbent EHR, or the bundled EHR from Copilot? | Use the ₹2,399 Copilot tier when comparing EHR scope. |

The table is deliberately practical. It uses what each first-party source says, then turns it into a test. A vendor website can tell you what to ask for. It cannot establish how a particular specialty, receptionist, or clinic day will behave after rollout.

## HealthPlix: useful when published plan scope matters

HealthPlix's pricing page makes it a sensible first call for a buyer who wants a visible plan comparison before a demo. The page displays Pro at ₹11,999 and Elite at ₹17,999, and its plan columns name specialty OPD EMR, billing, pharmacy, IPD, laboratory management, and queue-related functions. Treat those as the vendor's published labels, not an endorsement or a complete implementation specification.

That gives a clinic a concrete way to structure the conversation:

| HealthPlix check | Why the answer changes the shortlist | Evidence to keep |
|---|---|---|
| Specialty OPD EMR | A generic clinical-record demonstration may omit the templates and review process a specialty uses. | A demo note and correction in the clinic's specialty. |
| Billing and pharmacy | A clinic that uses these workflows should see them in the exact quoted scope, not merely in a plan grid. | The plan name, module list, tax, and exclusions in writing. |
| IPD and laboratory management | These labels matter only if the facility actually needs them. | A real referral, order, result, or inpatient handoff where applicable. |
| Queue-related workflow | The page's label does not prove token display, routing rules, or a hospital-wide queue engine. | The clinic's own arrival-to-consult handoff in a sandbox or pilot. |

The limitation is important. The public page supplies prices and module names, but it is not a site-specific statement of setup, data migration, integrations, or fit. Ask which price applies to the clinic, what the term includes, how GST is handled, and what happens to records at exit. If the clinic does not run pharmacy, lab, or IPD operations, do not pay for them merely because they appear in a comparison column.

## Practo Ray: useful when front-desk and clinical work must be checked together

Practo Ray's subscription agreement describes several clinic functions: calendar management for appointment scheduling and changes, billing for invoices and payments, EMR for clinical notes and prescriptions, and a communication centre. The agreement also says that particular features can vary by subscription plan. That makes Ray a reasonable candidate for a clinic whose selection committee includes both a clinician and the person running the front desk.

Run a single patient through the demo rather than watching four separate feature tours:

1. Create or find the patient, then book, cancel, and reschedule an appointment.
2. Record the visit in the clinical note and check the prescription-draft or prescription workflow required by the clinic.
3. Create the required invoice or payment record.
4. Ask the vendor to identify which of these steps belongs to the plan in the written quote.
5. Ask how the clinic retrieves the same patient's record on the next visit and what permissions the receptionist has.

This is selection detail, not a claim that Ray will solve every handoff. The subscription agreement is especially useful because it points out a limitation buyers can miss: a named function on a product does not mean that it is present in every subscription. Obtain price, included feature list, renewal terms, tax, support, and export process directly in the proposed agreement. The public agreement directs users to account-level terms for details, so this page does not state a general Ray price.

## eka.care: useful when the clinic wants one product conversation across operations

eka.care's doctor product page presents digital prescription, clinic management, patient engagement, and practice analytics as product areas. Its clinic-management material also describes a single queue for walk-ins and appointments, reminders, bills and due payments, and staff restrictions. Those are useful prompts for a clinic that wants to test operational steps alongside the clinical record.

| eka.care test | What the source supports | Procurement question |
|---|---|---|
| Digital prescription | The vendor uses this product label. | Does the selected plan produce the draft or prescription workflow the clinician requires, with review steps understood? |
| Clinic management and queue | The vendor describes handling walk-ins and appointments in one queue. | Can staff route the clinic's real walk-in, booked visit, cancellation, and delayed-doctor scenario? |
| Patient engagement | The product page lists patient engagement and reminders. | Which reminder route, consent process, and limits are in the written plan? |
| Billing and payments | The vendor describes bills and due payments. | Can the team demonstrate the clinic's payment and correction sequence? |
| Staff restrictions | The vendor describes staff restrictions. | Which roles can see, create, amend, export, or delete each record type? |

The correct limit to write into the buying file is simple: verify the current plan price, scope, onboarding work, and exit terms with eka.care. A product page describes categories and example workflows. It does not establish a quoted cost or guarantee that a configuration is suitable for every clinic.

## Make the vendors prove the same day of work

A named roundup becomes useful only when every candidate is judged by the same scenario. Use a synthetic patient and a script that matches the clinic's busiest routine. Do not use live patient data in an early vendor evaluation unless the clinic has completed its own privacy and access review.

| Moment in the test | What to ask every candidate to show | Pass evidence |
|---|---|---|
| Arrival and appointment | Create a walk-in, book an appointment, cancel it, and reschedule it. | Screens or a recording, plus the selected plan name. |
| Consultation | Create a note, correct it, and retrieve it for the same patient. | A reviewed note and the role that may amend it. |
| Billing or pharmacy | Run only the workflow the clinic really uses. | The exact scope and exception handling in the quote. |
| Handoff | Let the clinician, receptionist, and biller each perform their part. | A list of roles, permissions, and unresolved steps. |
| Exit and support | Ask for readable export, retrieval timeline, support route, and contract end process. | Written answer attached to the procurement file. |

A feature grid is not proof. A recorded or observed test gives better evidence than a long generic checklist, especially when the clinic will need corrections, duplicate-patient handling, role control, and record retrieval on its first difficult week.

## Price the EHR tier honestly

Do not compare a scribe tier with an EHR tier.

| Patient Square plan | Annual monthly equivalent, per clinician, ex-GST | Scope |
|---|---:|---|
| Assist | ₹1,599 | AI Medical Scribe and scheduling. This is scribe-only. |
| Copilot | ₹2,399 | Adds the bundled AI EHR and WhatsApp messaging. |
| Autopilot | ₹3,999 | Adds AI Receptionist, AI Follow-ups, priority support, and adoption and ROI analytics. |

GST is added at the prevailing rate. Use ₹2,399 when comparing Patient Square's bundled EHR with another EMR. A vendor quote can only be compared after its scope, term, and tax treatment are known. The ₹1,599 Assist figure is relevant when the clinic wants the standalone scribe alongside an incumbent EHR, not when it is pricing a replacement EHR.

## ABDM is a separate proof request

ABDM is federated and consent based. It does not choose a local record system for the clinic. If an ABDM workflow matters, ask a vendor to demonstrate its current production evidence for that workflow and retain the evidence with the procurement record.

Patient Square does not claim live ABDM integration. It is on the roadmap. That may rule it out for a clinic whose immediate requirement is a specific live ABDM workflow.

## Where Patient Square fits

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.

A practice can keep its existing EHR and use Practice Copilot alongside it, with EHR-ready export (PDF · HL7 · FHIR), or use Patient Square EHR from the Copilot tier. The product does not claim named-vendor integration or automatic filing.

For a clinic, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> and use a real week of visits to review the drafts after setup. For a hospital, bring the incumbent HIS/EHR, facility size, department mix, and one difficult workflow to Book a demo.

---

## AI Medical Scribes and Medico-Legal Defence: Records as Your Shield
https://patientsquare.com/in/blog/ai-scribe-medico-legal-documentation-india/
Published 2026-04-27 · Tags: medico-legal, record-keeping, india, documentation

Why "no records, no defence" is the rule that decides Indian negligence cases, what the data shows about deficient records, and how an AI scribe closes the gap.

Records are the primary evidence of what you did and why. In a consumer or civil dispute the onus is on the complainant, but courts repeatedly hold that poor records mean poor defence and no records mean no defence. A contemporaneous, legible, retrievable note is often what separates a dismissed complaint from a finding against you.

In an Indian medical-negligence case, your record is your defence. The complainant carries the burden of proof, but courts decide these disputes largely on the documentation, and the recurring line is blunt: poor records mean poor defence, no records mean no defence. A 2023 review of 253 NCDRC cases found "deficient medical records" among the most common error categories. So the cheapest legal protection a doctor can buy is a complete note for every visit.

> **Key takeaways**
>
> - Indian courts treat documentation as primary evidence; "no records, no defence" is the operative reality.
> - A 2023 IJME review of 253 NCDRC cases (2015–2019) found negligence proved in 53%, with deficient records about 22% of error categories.
> - The 2002 conduct rules require records produced within 72 hours and indoor records kept 3 years; failing either is professional misconduct.
> - A contemporaneous, legible, time-stamped note is the precondition for any defence. A missing one removes the option before the case starts.

_Source: Indian Journal of Medical Ethics, NCDRC five-year retrospective review, 2023._

## Why do records decide Indian negligence cases?

Because they're the evidence, and usually the only contemporaneous evidence. A negligence dispute lands months or years after the visit. Memories have moved on. Witnesses are unreliable. What survives is the chart, and the chart speaks for what happened in the room.

The doctrine that runs through these judgments is the one every medico-legal trainer repeats: poor records mean poor defence, no records mean no defence. It isn't a slogan; it's how the evidence actually weighs. When a complainant alleges you missed something, a complete note that shows what you checked, what you found, and why you decided as you did is your account of events. A thin note leaves the court with the complainant's version and your memory, and memory loses to paper every time.

There's a structural point underneath this. Under the Consumer Protection framework, the onus of proving negligence is on the complainant. That sounds protective. In practice, a missing or deficient record can shift the practical burden onto you, because the court is entitled to read an absent record as evidence the care wasn't given. The asymmetry is brutal: good records help you a little when you're right, and missing records sink you completely when you're challenged.

## What does the evidence actually show about documentation?

This isn't a vibe. There's data. A 2023 Indian Journal of Medical Ethics retrospective reviewed 253 medical-negligence cases decided by the National Consumer Disputes Redressal Commission between 2015 and 2019. Two findings matter here:

- Negligence was proved in 135 of the 253 cases, about 53%.
- Among the error categories the reviewers identified, "deficient medical records" was one of the most common, at 38 instances, roughly 22% of the errors logged. Add deficient preoperative and treatment-care documentation and the documentation-related share climbs further.

The reviewers' own framing echoed the doctrine: poor records mean poor defence. So when a doctor treats charting as the afterthought of a busy day, the afterthought is the thing the case turns on.

One honest caveat, because the gate demands it: these are consumer-forum cases that reached the NCDRC, not a random sample of all care. They over-represent disputes that escalated. But that's exactly the population a doctor worries about, and the documentation signal in it is loud.

## How does the 72-hour production rule turn a record into a shield?

The shield only works if you can hand it over fast. The operative 2002 medical-council conduct rules give you two duties that bear directly on defence:

- Retention. Keep indoor (admitted) patient records for three years from when treatment began. (The NMC's 2023 conduct regulations, which restated this, were held in abeyance, so the 2002 rules govern.)
- Production. When a patient, attendant, or legal authority requests records, produce them within 72 hours. Failing to do so is professional misconduct in its own right.

Read those together. A negligence complaint usually arrives with, or triggers, a records request. If you can produce a complete, contemporaneous file inside 72 hours, you've met the duty and put your account on the table early. If you can't, you've committed a second breach on top of the underlying allegation, and you've signalled, before any merits are argued, that the record isn't there. For the full mechanics of the retention and production rules, the [NMC record-keeping explainer](../nmc-record-keeping-ai-scribe/) is the companion read.

## An AI scribe fixes the failure point: the note that never got written

It fixes the failure point, which is not your intent to document well. It's the time you have to do it at a 50-patient OPD. The record that sinks a case is rarely one a doctor chose to write badly; it's the one written in eight seconds between patients, or never written at all.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For a defence workflow, three properties do the work.

It's contemporaneous: the note is drafted while the visit is happening, not reconstructed at 9pm. Contemporaneous records carry the most evidential weight, because they're written before anyone knows there's a dispute. It's complete and legible: a structured SOAP note records what you assessed and planned, in clean clinical English, even when the consult ran in Hindi or code-mixed Hinglish. Legibility alone has decided cases. And it's retrievable and time-stamped: stored, searchable, dated. A three-year-old visit becomes a lookup rather than an excavation, and you can prove when the note was written.

A word on that last point, because it cuts both ways. The medico-legal value of a record is highest when it's clearly contemporaneous and not quietly edited after a complaint lands. Don't rewrite history. A time-stamped note you reviewed and signed at the visit is a shield; a note that looks back-dated is a liability. Keep the audit trail honest.

We'll state the limit plainly, as an opinion: a scribe doesn't make you defensible. You make yourself defensible by reviewing and signing accurate notes. The scribe just removes the reason that step gets skipped.

## What about consent, audio, and the privacy side of the record?

A fair worry: if a tool is listening, does the recording itself become discoverable evidence that cuts against you? It's the right question to ask any vendor, and the answer should reassure you here. Our position is that visit audio is processed in memory and discarded the moment the note is drafted. There is no audio archive, so there's no recording sitting in storage to be subpoenaed later. What survives is the note you reviewed and signed, which is the record you want to stand behind anyway. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That also keeps you clean under the DPDP Act 2023, which expects consent-first, purpose-limited handling of patient data and the ability to delete when the purpose ends. Notes belong to your practice; you can export or delete any visit. The detail is on our [security page](../../security/), and the broader data-handling duties are in the [DPDP Act for clinics guide](../dpdp-act-clinics-guide/).

## How do I build documentation that actually defends me?

Five habits, in order of how much they protect you:

1. Every visit leaves a note. No exceptions on busy days. A tool that writes at consultation pace is how you hold this, because intention fails at patient 45, not patient 5.
2. Write it now, not tonight. Contemporaneous beats reconstructed, evidentially and in court.
3. Make it complete: history, exam, assessment, plan, and the reasoning. The "why you decided" is what answers the negligence allegation.
4. Keep it retrievable and time-stamped. Three years minimum, producible inside 72 hours, with an honest audit trail.
5. Never edit silently after a complaint. Correct with a dated addendum, not a rewrite.

The honest test of whether your documentation would hold up isn't a checklist; it's your own clinic on its worst day. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a complete note land about two minutes after a real consultation, or run a <a href={CTA_URLS.in.trial}>7-day free trial</a> across a full OPD and check whether every visit ends with a record you'd be glad to produce in front of a forum. If cleaner notes also matter for your insurance paperwork, the [cashless-claim documentation read](../ai-scribe-cashless-claim-documentation/) covers that angle.

---

## Counseling Notes Templates for Private Practice
https://patientsquare.com/us/blog/counseling-notes-template/
Published 2026-04-27 · Tags: counseling, template, behavioral

Copy-paste DAP, BIRP, and SOAP counseling note templates built for private practice — what each section must carry to satisfy payers, and when to stop.

A counseling note template is a structured form — usually DAP, BIRP, or SOAP — that organizes each session into labeled sections so the progress note carries diagnosis, interventions, client response, and goal progress. The template defines the shape; the clinician fills the content from the session.

A counseling note template gives your progress note a consistent shape: DAP, BIRP, or SOAP. Below are copy-paste templates for each, a plain-language breakdown of what payers actually need to see regardless of format, and the honest argument for why the blank box is only half the problem.

> **Key takeaways**
>
> - DAP, BIRP, and SOAP all document the same session; they just label the sections differently. For most private-practice counselors, DAP is the practical default.
> - A payer's medical-necessity audit looks for five things in any format: a covered diagnosis, the specific interventions you used, the client's response, progress toward each treatment-plan goal, and a signed credential.
> - A progress note from a template is not the same as a HIPAA psychotherapy note. The two belong in different places.
> - A 2023 National Council for Mental Wellbeing survey of 750 behavioral health workers found 93% reported burnout; a third said they spend most of their time on administrative tasks rather than direct client care.
> - A template standardizes the shape of the note. It does nothing about reconstructing what happened in session three when you sit down to chart at seven in the evening.

## Which counseling note format fits private practice?

The format argument is smaller than the blog-post industry around it suggests. DAP, BIRP, and SOAP carry the same clinical content. What differs is which section holds it.

DAP (Data, Assessment, Plan) is the leanest. Data holds what the client reported plus what you observed. Assessment is your clinical reasoning. Plan is what happens next. SimplePractice lists it as one of the current standard approaches for psychotherapy documentation, and in most private practices it fits without forcing anything. You get two narrative sections and a plan. That covers the majority of counseling sessions.

BIRP (Behavior, Intervention, Response, Plan) exists because payers want to see a paper trail connecting what you did in the room to how the client responded. ICANotes describes it as purpose-built for medical necessity and audit readiness. Behavior covers presenting symptoms. Intervention names the specific techniques you used. Response documents what the client did with those techniques. The I-then-R pairing is the thread an auditor looks for, which is why BIRP earns its extra section if you're reviewed often or carry a high-risk caseload.

SOAP (Subjective, Objective, Assessment, Plan) keeps the client's account separate from what you measured or observed. The Objective section, per StatPearls, is for screener scores, vital signs, medication notes. In a pure talk-therapy session with nothing to measure, that box stays thin. SOAP is worth the overhead when you have actual objective data; skip it otherwise.

Pick one format. Use it every session of the same type. The debate about which is "best" is mostly not useful.

| Format | Sections | Best fit | The honest tradeoff |
|---|---|---|---|
| **DAP** | Data, Assessment, Plan | Talk therapy, private practice | Merges reported and observed; a strict auditor may push for more separation |
| **BIRP** | Behavior, Intervention, Response, Plan | High-review practices, insurance-heavy caseloads | More sections to fill on a quiet, low-intervention session |
| **SOAP** | Subjective, Objective, Assessment, Plan | Sessions with a measurable Objective (screeners, meds) | Objective section is thin in pure talk therapy |

## The DAP counseling note template (copy-paste)

Copy this into your EHR's note field. Brackets are prompts, not text to keep in the note.

```
DATE: [date]   START: [time]   END: [time]   CPT: [code]   DX: [ICD-10 + condition]

D — DATA
[Reason for today's session and presenting concern.]
[Client report: symptoms, mood, sleep, significant events since last session — in their words.]
[What you observed: appearance, affect, engagement, mental status, anything notable.]
[Screener results if administered (e.g., PHQ-9: 11, down from 14).]
[Interventions used during the session and the client's in-session response.]

A — ASSESSMENT
[Your clinical interpretation of the Data above.]
[Progress toward each treatment-plan goal — name the goal, state the direction of movement.]
[Any change in diagnosis, risk, or functioning level. Risk assessment if clinically indicated.]

P — PLAN
[Next session date and frequency.]
[Homework or between-session tasks assigned.]
[Referrals. Treatment-plan updates. Anything to follow up on next time.]

[Credential, signature]
```

The Assessment section carries the most weight in a payer review. "Client appeared sad" is data. "Depressive symptoms have decreased over the past four weeks in response to behavioral activation work, consistent with progress toward goal 1" is assessment, and that sentence is what holds medical necessity together. Every clinical conclusion in Assessment needs visible support in Data, or a reviewer will flag the gap.

## The BIRP counseling note template (copy-paste)

Use BIRP when you need the intervention-response pair on the page.

```
DATE: [date]   START: [time]   END: [time]   CPT: [code]   DX: [ICD-10 + condition]

B — BEHAVIOR
[Presenting symptoms and affect at the start of session.]
[Subjective: what the client reported. Observed: what you noted.]
[Risk factors, if any.]

I — INTERVENTION
[The specific techniques and therapeutic approaches you used this session.]
[Psychoeducation delivered. Skill practiced. Treatment strategy applied.]

R — RESPONSE
[How the client responded to each intervention — engagement, what shifted, what didn't.]
[Progress toward each treatment-plan goal. Client feedback or direct quotes if relevant.]

P — PLAN
[Next session date. Homework or between-session tasks.]
[Treatment-plan updates. Risk-management plan. Focus for next session.]

[Credential, signature]
```

The Intervention and Response sections are doing the medical-necessity work. A note that documents a technique but never records whether it landed is the kind of gap that becomes a clawback on audit. BIRP forces you to answer both sides of that question, which is why payers tend to like it.

## The SOAP counseling note template (copy-paste)

Use SOAP when the session includes something measurable in the Objective section.

```
DATE: [date]   START: [time]   END: [time]   CPT: [code]   DX: [ICD-10 + condition]

S — SUBJECTIVE
[Chief concern for today. Client's account of symptoms, mood, and events — in their words.]

O — OBJECTIVE
[What you observed and measured: mental status exam, affect, screener scores.]
[Medication adherence and side effects, if applicable.]

A — ASSESSMENT
[Diagnosis and clinical reasoning. Progress toward treatment-plan goals. Risk if clinically indicated.]

P — PLAN
[Next session date. Medication changes if applicable. Referrals, homework, follow-up.]

[Credential, signature]
```

If the Objective section is going to say "client appeared appropriately dressed and engaged," SOAP is adding structure without adding value. DAP handles that session better. Save SOAP for visits where you have actual objective data to separate out.

## What every counseling note must carry to get paid

The format is cosmetic to a payer. The medical-necessity content is what gets a claim paid.

For Medicare, the Local Coverage Determinations governing psychotherapy (L33252 and L34616) require the service date and session times, the diagnosis tied to a covered condition, the CPT code, a mental status finding, the specific interventions used, the client's response and any symptom change, measurable progress toward each treatment-plan goal, and a signed credential. Commercial payers track the same thread. The format you use to organize all that does not appear in any payer policy.

If you're picking a template hoping it will fix a documentation gap, it will fix the shape of the gap. Not the content. The reviewer hunting for medical necessity doesn't care whether you called the section "Response" or folded it into your Data. They want the same five things either way.

| What the payer is looking for | Where it lives in DAP | In BIRP | In SOAP |
|---|---|---|---|
| Covered diagnosis | Header + Assessment | Header + Behavior | Header + Assessment |
| Interventions used | Data | Intervention | Plan |
| Client response to intervention | Data | Response | Subjective + Objective |
| Progress toward each goal | Assessment | Response | Assessment |
| Signed credential | Footer | Footer | Footer |

## Progress notes versus psychotherapy notes: one distinction that matters

One thing to sort out before you put anything sensitive into a template. The note these templates produce is the progress note: the billable chart entry with diagnosis, interventions, and progress. Under HIPAA, that is explicitly not a "psychotherapy note."

HIPAA psychotherapy notes are your separate private notes analyzing the session, kept apart from the chart, with heightened legal protection. CMS confirms they are not required for reimbursement and should not be submitted to payers at all. The progress note is what a template (or a scribe) produces. The psychotherapy note stays with you.

The distinction matters for subpoenas, insurance audits, and any case where a third party requests records. Progress notes can be disclosed in many circumstances where psychotherapy notes cannot. Keep them in different places. If you store both in the same EHR note, you have likely collapsed a distinction that HIPAA went to some trouble to create.

Our [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/) goes into 42 CFR Part 2, audio retention, and what these distinctions mean when a third party touches your session data.

## When to stop filling a blank box and start generating the note

Here is our take, stated plainly: for a full private-practice caseload, the blank template is a half-measure.

Think about a Wednesday with six clients. Session four was a quiet, low-intervention hour. Session six had a crisis call that ran thirty minutes over. By the time you sit down to chart, session four is a blur and session six is the only one you can reconstruct in any detail. The template tells you to write Data, Assessment, Plan. It does not tell you what the client said about the homework from three weeks ago or which CBT technique you actually used in session four. You have to remember that, and on a full day the memory is unreliable by the time you get to it.

The 2023 National Council for Mental Wellbeing survey, conducted by Harris Poll across 750 behavioral health workers between February 3 and 19, put the burnout number at 93%, with 62% rating it moderate or severe. A third said they spend most of their time on administrative work rather than direct care. Sixty-eight percent of those in direct care said admin time takes away from time with clients. A blank template is not the answer to those numbers.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Instead of filling a blank DAP box from memory at eight in the evening, you read a draft built from what was actually said and edit it down. The template defines the format you want; the scribe fills it from the session, not from what you can still recall two hours later.

This tool is not right for every situation, and two things are worth saying clearly before you try it. In behavioral health, the audio question comes before the note-quality question. Visit audio is processed in memory and discarded once the note is drafted; there is no archive. We built the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/) around that question because it's the one that matters most in this specialty. Separately, some sessions should not have a microphone running at all: a trauma disclosure, a crisis escalation, a fragile therapeutic alliance. That's a clinical judgment call, and no software should make it for you.

For the rest of the caseload, the templates above are worth saving and a solid place to start. For the busiest days, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to see a note generated from a sample session, then run the 7-day free trial on a real week. Compare the edit time to filling a blank template after hours. If the draft clears most of the note with a light touch, you have stopped templating. That is the point.

The related guides worth reading from here: [therapy notes templates](../therapy-notes-template/) for the broader DAP/BIRP/SOAP comparison, [DAP note format and examples](../dap-note/), [BIRP notes explained](../birp-note/), and the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/) for the audio and HIPAA questions before anything else.

---

## HIPAA vs DPDP for AI Medical Scribes: What Each Demands
https://patientsquare.com/in/blog/ai-scribe-hipaa-vs-dpdp/
Published 2026-04-24 · Updated 2026-09-29 · Tags: hipaa, dpdp, compliance, privacy

What India's DPDP Act demands of an AI scribe: consent, breach windows, data residency, and how those duties compare with HIPAA requirements.

HIPAA (US) runs on the covered-entity and business-associate model: the vendor signs a BAA and follows the Security and Breach Notification Rules. DPDP (India) runs on a consent-and-fiduciary model: the clinic is a Data Fiduciary that must process patient data on consent and purpose limitation. One is contract-and-safeguards led; the other is consent led.

India's DPDP Act and the US HIPAA rules both govern how an AI scribe may handle patient data, but they run on different machinery. DPDP turns on patient consent and your duties as a Data Fiduciary. HIPAA turns on a signed Business Associate Agreement and the Security Rule. If you run a clinic in India and you're weighing a scribe, and many were built US-first for HIPAA, this is the obligation map: what DPDP actually demands of you, where HIPAA sets a baseline a serious vendor already meets, and what to verify before you sign.

> **Key takeaways**
>
> - HIPAA runs on the BAA-plus-Security-Rule model; DPDP runs on the consent-plus-Data-Fiduciary model.
> - HIPAA breach: notify individuals within 60 days; notify HHS within 60 days for 500+ affected, annually for smaller breaches.
> - DPDP breach: intimate people and the Data Protection Board without delay, then a detailed report to the Board within 72 hours.
> - DPDP has no blanket data-localisation rule. HIPAA has none either. Residency is a contract question, not a statutory mandate in either law.
> - The engineering that satisfies both, encryption, access control, minimal retention, is largely the same. The paperwork differs.

_Sources: HHS HIPAA Breach Notification Rule (45 CFR 164.404, 164.408); PIB / MeitY DPDP Rules 2025._

## HIPAA vs DPDP: the obligation map for an AI-scribe buyer

Here's the side-by-side. Each row is a real obligation that bears on the scribe you buy, not a generic legal summary.

| Obligation | HIPAA (US) | DPDP (India) |
|---|---|---|
| **Who carries the duty** | Covered entity + business associate (the vendor) | The clinic, as Data Fiduciary; vendor is a processor on your behalf |
| **Core legal instrument** | Written BAA (45 CFR 164.502(e), 164.504(e)) | Patient consent: free, specific, informed, unambiguous |
| **Lawful-basis model** | Permitted uses for treatment, payment, operations | Consent-first, with limited statutory exceptions |
| **Security duty** | HIPAA Security Rule: administrative, physical, technical safeguards | Reasonable security safeguards (the duty with the largest penalty) |
| **Breach: people** | Without unreasonable delay, no later than 60 days (164.404) | Without delay (2025 Rules) |
| **Breach: regulator** | HHS within 60 days for 500+; annual log for under 500 (164.408) | Data Protection Board: without delay, detailed report within 72 hours |
| **Patient rights** | Access, amendment, accounting of disclosures | Access, correction, erasure; grievance redressal |
| **Data residency** | No statutory localisation; governed by the BAA | No blanket localisation; negative-list transfer (Section 16) |
| **Penalty ceiling** | Tiered civil penalties per violation category | Up to ₹250 crore for security-safeguard failure leading to a breach |

The shape of the difference: HIPAA hands you a contract (the BAA) and a rulebook (the Security Rule), and compliance flows from honouring both. DPDP hands you a relationship with the patient (consent) and a role (Data Fiduciary), and compliance flows from respecting purpose limitation and securing the data. A scribe that's built right satisfies both with the same underlying engineering.

If you operate in both regions, the practical move is to ask one vendor the BAA question and the consent question side by side. You can do that on a call: <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and put both regimes to the same tool.

## What does HIPAA actually require from an AI scribe?

Three things, in order of how often buyers get them wrong.

Start with the signed BAA. It's non-negotiable and it's the first thing to verify. Under 45 CFR 164.502(e) and 164.504(e), a covered entity must have a written contract with any business associate that creates, receives, maintains, or transmits PHI on its behalf. An ambient scribe processing visit audio and notes is squarely a business associate. The BAA has to carry the required safeguard and breach-notification terms, and an oral assurance doesn't count. If a vendor won't sign one, the conversation is over.

Then the Security Rule safeguards. The vendor has to implement administrative, physical, and technical safeguards for the PHI it holds: access controls, encryption, audit logging, the standard set. HIPAA deliberately doesn't certify software, so "HIPAA certified" is a phrase to distrust, because no such certificate exists. What exists is a vendor with HIPAA compliant safeguards that can show you how those controls work. Our full take on this is in the [HIPAA and AI scribes guide](/us/blog/ai-scribe-hipaa-baa-consent/).

Last, breach notification. If unsecured PHI is breached, the clock starts at discovery. Affected individuals get notice without unreasonable delay and no later than 60 calendar days (45 CFR 164.404). HHS gets notice within 60 days when 500 or more people are affected, or on an annual log for smaller breaches (45 CFR 164.408). When the breach is at the vendor, the business associate notifies you, the covered entity, and you remain responsible for individual notice.

## What does DPDP actually require from an AI scribe?

A different starting point: the patient's consent, and your role as the one accountable for the data.

Consent and purpose limitation come first. Under DPDP, you process patient data on consent that's free, specific, informed, and unambiguous, and you use it only for the purpose you stated. A scribe that quietly repurposed patient data for model training would break this, so ask every vendor directly whether your patients' data trains anything.

Then there's Data Fiduciary accountability. You're the Data Fiduciary. When you hand data to a processor like a scribe, their handling becomes your exposure. Which is why vendor diligence under DPDP isn't optional. It's the law making your procurement decision a compliance decision.

And the breach timelines. The DPDP Rules 2025 were notified on 13 November 2025 and commence in phases, with the bulk operational obligations landing by 13 May 2027. On breach, the duty is to intimate affected people and the Data Protection Board without delay, then file a detailed report to the Board within 72 hours. The phased calendar, and what your clinic must do by when, is laid out in the [DPDP Rules 2025 timeline](../dpdp-rules-2025-clinic-timeline/).

## Does either law force patient data to stay in-country?

This is the most over-claimed point in the whole area, so here's the clean version. Neither HIPAA nor DPDP imposes a blanket data-residency mandate on a health-tech vendor.

- HIPAA has no localisation rule. Where PHI is stored is governed by your BAA and your own risk decisions, not a statute that says "US-only."
- DPDP uses a negative-list model under Section 16 of the Act: cross-border transfer is permitted except to jurisdictions the central government specifically restricts. There's no general "data must stay in India" command in the Act itself. Sector regulators (for example in banking) can impose their own localisation, but those rules come from elsewhere, not DPDP.

So "where does the data live" is a real question, but it's a contract-and-risk question you settle with the vendor, not a box a law ticks for you. A vendor who answers it in one sentence has told you they've thought about it. For the India residency angle in detail, see [where your patient data lives](../ai-scribe-data-residency-india/).

## How can one AI scribe satisfy both regimes?

By building to the stricter technical floor and handling the paperwork per region. The thing that jumps out, once you map both laws, is how much they agree on at the engineering level: encrypt the data, control and log access, don't keep what you don't need, let the customer export or delete. HIPAA gets there through the Security Rule and the BAA. DPDP gets there through reasonable-security-safeguards and purpose-limitation. Different routes to the same place.

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The compliance posture is built to clear both floors:

- For the US: HIPAA-compliant safeguards, and a BAA available to every customer. We don't say "HIPAA certified," because that certificate doesn't exist.
- For India: patient data handled to DPDP Act 2023 standards, consent-first and purpose-limited. We describe this as handling-to-standards, not certification, because DPDP vendor certification isn't a thing that exists either. (Our ABDM integration is on our roadmap, not live, and we won't claim otherwise.)
- And for both: live consultation audio is processed in memory and discarded once the note is drafted. This reduces retained audio; it does not remove obligations for processing or other retained data. Notes are encrypted in transit (TLS 1.2+) and at rest (AES-256), access is role-scoped and logged, and the notes belong to your practice, exportable or deletable any time. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

One opinion, held firmly: the cleanest compliance answer in both countries is to hold less data, not to paper over holding a lot of it. Discarding live consultation audio reduces retained data. Notes and uploaded recordings still need their own access, retention, and disclosure controls.

The full technical posture, in the same plain terms for both regimes, is on our [security page](../../security/). If you want to put it to the test, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and ask the consent-and-purpose question directly, or the BAA question too if you also run a US practice, then take a <a href={CTA_URLS.in.trial}>7-day free trial</a> and check the recording mode: live consultation audio is processed in memory and discarded, while uploaded recordings use a separate retention mode with explicit consent.

---

## AI Medical Scribe for Psychiatry: The Privacy Questions First
https://patientsquare.com/us/blog/ai-scribe-for-psychiatry-privacy/
Published 2026-04-23 · Updated 2026-07-22 · Tags: psychiatry, behavioral-health, privacy, compliance, trust

Which privacy rules actually apply to a psychiatry AI scribe, why retained audio is the real risk, and a decision tree for behavioral-health buyers.

Only if your practice is a federally-assisted substance use disorder program. Part 2 protects SUD-treatment records held by programs that hold themselves out as providing SUD diagnosis, treatment, or referral. A general psychiatry or therapy practice that is not such a program is usually governed by HIPAA, not Part 2. If you do SUD work, Part 2 layers on top.

Before you pick a psychiatry AI scribe, ask one question: what happens to the audio? In behavioral health the recording is more revealing than the note, and a vendor that retains it has created something a court can later reach. The privacy rules that apply are narrower than most vendor pages imply, but the discoverability risk of stored audio is real. A scribe that never keeps the recording sidesteps the worst of it.

The rest of this sorts out which rules actually govern your practice, which ones are marketing fog, and gives you a short decision tree to run any vendor through. Us included.

> **Key takeaways**
>
> - 42 CFR Part 2 protects substance use disorder records held by federally-assisted SUD programs. It does not, by itself, cover general psychiatry.
> - The scribe's SOAP note is the regular clinical record, not a HIPAA "psychotherapy note." Different rules, lower disclosure bar.
> - Retained audio is protected health information and is discoverable in litigation. Audio that's never stored can't be subpoenaed.
> - 93% of behavioral health workers reported burnout in a 2023 survey of 750 workers; 62% called it moderate or severe.
> - The deciding question isn't a feature. It's the retention policy. Get a one-sentence answer with a timeline.

## Which privacy rules actually apply to a psychiatry scribe?

This is where careful clinicians get talked into the wrong fear. Three regimes get name-dropped on vendor pages. Only some of them apply to you.

HIPAA is the floor. It governs your practice's protected health information, including the note the scribe drafts, and it almost always applies.

42 CFR Part 2 is the one vendors get wrong most often. It protects records of substance use disorder treatment created or held by a federally-assisted Part 2 "program," meaning a person or unit that holds itself out as providing SUD diagnosis, treatment, or referral (42 CFR 2.11, 2.12). If a patient's SUD treatment is not provided by such a program, that record is not covered by Part 2. So a general psychiatry or therapy practice that isn't an SUD program is usually governed by HIPAA, not Part 2. Run SUD treatment and Part 2 layers on top, with stricter consent and disclosure rules. The 2024 final rule brought much of Part 2 consent closer to HIPAA, letting a single patient consent cover future treatment, payment, and operations uses, while still requiring separate consent for SUD counseling notes.

Psychotherapy notes are a HIPAA category, not a Part 2 one. They're the clinician's process notes analyzing a session, kept separate from the rest of the record, and they need a specific authorization to disclose (45 CFR 164.501, 164.508(a)(2)). Here's the part that matters for a scribe. The structured note a scribe produces, the SOAP, the meds, the plan, is the regular clinical record. It is not a psychotherapy note. So it doesn't get the heightened protection, and you shouldn't assume it does.

One honest line before we go further: this is reporting, not legal advice. The interaction of HIPAA, Part 2, and state mental-health law is exactly the kind of thing to confirm with counsel for your specific practice type. If you want the general HIPAA framework, our [HIPAA and AI scribes guide](../ai-scribe-hipaa-baa-consent/) covers the BAA and the vendor checklist that apply to every practice.

## Why retained audio is the real risk in behavioral health

Strip away the regime alphabet soup and the practical risk is concrete. If a vendor stores the visit audio, that recording is protected health information, and PHI is discoverable in litigation. Under 45 CFR 164.512(e), a covered entity can be compelled to produce PHI in response to a subpoena or court order when the conditions are met. For SUD records under Part 2, the bar is higher, a qualifying court order rather than a plain subpoena, but the point holds: a stored recording is a thing that can be reached.

In behavioral health that's a sharper edge than in most of medicine. The audio captures what the patient said before any of it was filtered into a note. The digressions. The names dropped in passing. The thing they said and immediately walked back. Your signed note is the curated version, scrubbed of all that. The raw recording isn't. A clinician who would never paste a verbatim transcript into the chart should think hard about a vendor keeping that same transcript on a server for weeks.

One caveat, stated plainly: this is editorial synthesis, not a statute. The legal mechanism is 164.512(e). The conclusion that a scribe's stored audio is a discovery target is our read of how that mechanism meets this technology, and we think it's the right read. Test it by asking the vendor directly. If you keep my patients' audio, and a court asks for it, what happens? A vendor that stores nothing has a one-word answer. If that's the answer you want, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and put the audio question first, before anyone talks features.

## The behavioral-health scribe decision tree

Run any vendor through this, in order. The first question that gets a bad answer ends the evaluation.

| Step | Ask | A good answer | A bad answer |
|---|---|---|---|
| 1 | Do you store the visit audio, and for how long? | Processed in memory, discarded at note draft. No archive. | "We retain it for model improvement" with no deletion timeline. |
| 2 | Will you sign a BAA for a practice my size? | Yes, every customer, before any real visit. | Tier-gated or "for enterprise only." |
| 3 | If I run an SUD program, do you support Part 2 consent requirements? | A straight yes-or-no, in writing. If no, they say so. | Confident hand-waving about "full compliance." |
| 4 | Is patient audio or note text used to train your models? | A written answer, separately for audio and text. | "We follow applicable law." |
| 5 | Who can access my notes, and is access logged? | Role-scoped, every access logged, logs reviewable. | "Our team has access as needed." |
| 6 | What happens to my data if I cancel? | Return or destruction, with a timeline, in the contract. | Silence, or buried in a ToS. |

Notice what's not on the list: per-specialty "psychiatry templates," accuracy percentages, EHR write-back. Those make good slides and decide nothing about your privacy exposure. The retention answer in step one decides almost everything.

## Where we fit, and where we don't

So here's where we land. AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For behavioral health, the part that matters is what we do with the audio. It's processed in memory and discarded the moment the note is drafted. There is no recording to retain, train on, subpoena, or breach. The prescription draft reflects what you said in the visit; it does not screen for interactions or dosing. In psychiatry, where polypharmacy and interaction risk are routine, that interaction check is exactly the read you already run on every prescription, and it stays yours: you review the draft against the chart, adjust what needs adjusting, and sign.

Now the honest part. If you run a federally-assisted SUD program that needs Part 2-specific consent tracking wired into an enterprise EHR, a health-system platform embedded in that EHR will likely fit your compliance workflow better than we will. We don't integrate with EHRs. We don't manage Part 2 consent flows for you. That's a real gap for a subset of behavioral-health practices, and you should weigh it honestly against the audio-retention advantage. Match the tool to your regulatory footprint.

For everyone else, the calculus is simpler. A solo psychiatrist, a group therapy practice, a behavioral-health clinic that isn't a Part 2 program: the documentation burden is brutal (93% of the workforce reported burnout in 2023), and a scribe that never keeps your audio answers the privacy fear at its root. If that's your practice, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run the audio policy past your own compliance instincts before you commit.

## What to verify before you sign

The work is small, and it's worth doing precisely:

1. Settle the audio question first. One sentence, with a deletion timeline. Everything else is secondary.
2. Confirm your regime. Are you a Part 2 program or a HIPAA-only practice? It changes the consent and disclosure rules, and it changes which vendor claims are even relevant to you.
3. Get the BAA before the first real session, and confirm it covers the trial period, since you'll feed it real visits from day one.
4. Pin the training-data policy in writing, separately for audio and note text.
5. Test on your own patients during a trial. A demo with a scripted SUD intake tells you nothing about how the tool handles your actual sessions.

Our security posture, what's encrypted, who can access what, what's audited and what isn't yet, is on our [security page](../../security/), written to be read with this checklist in hand. And the cross-vendor audio question is its own buying decision: see [what happens to your visit audio across major scribes](../ai-scribe-audio-retention/) before you take anyone's word, ours included.

The right evaluation for a behavioral-health practice is a quiet week of real sessions with the audio policy verified in writing first. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and make the audio question the first thing you ask, then compare the [product options](/us/compare/) against your own caseload and consent workflow. In this specialty, the recording is the risk. A tool that keeps none of it is the cleanest answer to the hardest question.

---

## OPD Software for a Clinic: The 200-Patient-Day Buyer Guide
https://patientsquare.com/in/blog/opd-software-for-clinic-india/
Published 2026-04-23 · Updated 2026-09-29 · Tags: opd-software, india, buyer-guide

A buyer guide to OPD software for an Indian clinic, built around a 200-patient OPD day: what to look for, the documentation burden, and pricing.

OPD (outpatient department) software runs the front-of-house of a clinic: patient registration, the OPD queue and token system, appointment scheduling, the consultation note, the prescription, and usually billing. It is the system that turns a walk-in into a registered visit, gets the patient in front of the doctor, captures what happened, and produces the bill. Larger products add pharmacy, lab orders, and ABDM record linking on top.

OPD software is the system that runs the busy front of an Indian clinic: registration, the queue, the consultation note, the prescription, the bill. Pick it for the day that actually tests it, not the quiet Tuesday. Pick it for the 200-patient OPD day, when the waiting room is full by ten and the doctor is three patients behind by noon. On that day the thing that breaks is almost never a missing feature. It is the documentation, because there is no time to type a note when the next patient is already at the door.

This guide walks the high-throughput reality: what to look for in OPD software, where the documentation burden bites hardest, what the main options cost, and how a documentation layer fits on top of whatever you run.

> **Key takeaways**
>
> - On a 200-patient OPD day, the constraint is seconds per step times 200. Test queue speed, registration speed, and clicks-to-finish-a-note on a live demo, not a feature list.
> - India-native clinic software prices cluster around ₹1,000–1,500 per doctor per month plus 18% GST. HealthPlix publishes ₹11,999–17,999/year. Practo Ray publishes nothing first-party.
> - The note module exists in almost every OPD product. Whether it gets filled properly in a two-minute consult is the real question, and that is a documentation problem, not a storage one.
> - A documentation layer (ambient AI scribe) works alongside your existing OPD software. It fixes the note without replacing registration, queue, or billing.

_Sources: Irving et al., BMJ Open 2017; Indian Medical Council medical ethics code, 2002._

## Why the 200-patient day is the right test

Most OPD software demos run on a clinic with five patients in the waiting room and all the time in the world. That demo tells you almost nothing. The system you should buy is the one that holds up when the OPD is packed.

Run the numbers. At a two-minute average consult, a doctor working a long OPD session can clear well past a hundred patients in a day, and high-volume clinics regularly cross 200. Now add three extra clicks to every note, or two extra screens to register a returning patient. Three clicks does not sound like much. Multiply it by 200 and you have added real minutes to the queue and stolen attention from the patient in the chair. At high throughput, friction does not stay small. It compounds.

So the test is not "does it have a billing module." Almost everything does. The test is speed per patient and where the slow steps hide. The three that decide a packed OPD: how fast a repeat patient gets registered and into the queue, how few taps it takes to finish a note and print a prescription, and whether the doctor can actually keep up without skipping the documentation entirely.

That last one is where most OPD software quietly fails. The note field is there. Nobody fills it, because typing a real note in a two-minute consult with twelve patients waiting is not possible.

## What to look for in OPD software

Strip the feature list back to what a high-volume OPD actually leans on every day.

The **queue and token system** is the spine of the OPD. It should let the front desk register a walk-in in seconds, assign a token, and show the doctor who is next without anyone shouting names down a corridor. Test it with a returning patient, not a fresh one. Repeat-patient lookup is where slow systems lose the most time.

**Registration and patient lookup** has to be fast and forgiving. Phone-number search, partial-name search, and a clean way to handle the same patient arriving under a slightly different spelling. On a busy day the front desk is the first bottleneck, and a clumsy registration screen backs the whole OPD up before the doctor even starts.

The **consultation note and prescription writer** is where the clinical work lands. Look at how long it takes to go from "patient sits down" to "prescription printed." If that flow needs heavy typing, it will not survive a packed OPD, and the note will get compressed to a single line or skipped.

**Billing and GST invoicing** should sit in the same flow as the visit, so the bill is generated without re-entering anything. If billing lives in a separate system, someone reconciles two records every month.

Beyond those, decide honestly whether you need **pharmacy and inventory**, **lab order management**, and **ABDM record linking**. Each is genuinely useful for the clinic that runs that function in-house, and dead weight for the clinic that does not. We come back to ABDM below, because "ABDM compliant" hides more than it says.

Our [India clinic software scorecard](/in/blog/best-clinic-management-software-india/) scores the main OPD and clinic-management options on exactly these lines, and the [EMR software buyer guide](/in/blog/emr-software-india-guide/) covers the cloud-versus-on-premise and DPDP Act 2023 decisions that sit underneath the OPD layer.

## Where the documentation burden bites

Here is the part the feature lists skip. The Indian OPD moves fast. Average primary-care consultation time in India is about two minutes, per Irving et al.'s 67-country BMJ Open review, which put India near the short end of an enormous global range, from 48 seconds in Bangladesh to 22.5 minutes in Sweden. Two minutes to listen, examine, decide, and prescribe. The documentation loses that race every single time.

So one of three things happens. The note gets compressed to a one-line scribble that says nothing useful later. Or it gets written from memory after the queue finally clears, two hours and forty patients later, by which point the details have blurred. Or it gets skipped, and the OPD register has a token number and a fee but no clinical record behind it.

Better OPD software does not fix this. A faster registration screen and a slicker billing module do not make the note appear. The constraint is upstream of the software entirely: there is no spare time in a two-minute consult to type. A nicer note field is still a note field nobody has the seconds to fill.

And thin notes are not a cosmetic problem. The operative 2002 medical ethics code requires three-year retention for indoor records and production of requested records within 72 hours. A register full of one-line entries is a medico-legal exposure that sits squarely with the clinician, not the software vendor.

The split below is documentation only, on a 200-patient OPD day. The note burden is the part that breaks at volume, not the queue or the bill.

| On a packed OPD day | Type the note yourself, mid-OPD | Ambient layer drafts the note |
|---|---|---|
| **The note** | Compressed to one line, or skipped, to keep the queue moving | Structured SOAP note ready to review about two minutes after the visit |
| **After the last patient** | Charting backlog cleared from memory, hours later | Nothing to catch up on; the notes are already written |
| **Medico-legal exposure** | Thin or missing clinical records | Complete, retrievable records without slowing the queue |
| **Attention in the room** | Split between the screen and the patient | On the patient, not the keyboard |

_Source: Irving et al., BMJ Open 2017; Indian Medical Council medical ethics code, 2002; clinic workflow estimate._

## What OPD software actually costs in India

Most vendors gate pricing behind a demo call. Here is what is actually published, as of June 2026.

| Vendor | Type | Published price | Price source |
|---|---|---|---|
| **HealthPlix** | Specialty EMR / OPD suite (billing, pharmacy, ABDM, DDI) | ₹11,999/yr Pro; ₹17,999/yr Elite (≈₹1,000–1,500/mo, computed) | First-party (healthplix blog) |
| **Practo Ray** | Clinic-management / OPD suite | No first-party price; third-party listings ≈₹1,000–6,000/doctor/mo | Third-party (sales-gated) |
| **EkaScribe** | Ambient scribe (eka.care platform) | ₹1,499/mo Pro; free tier 5 consults/day; ~17% off annual | First-party (ekascribe.ai) |
| **Patient Square Assist** | Ambient AI medical scribe + workflow automation | From ₹1,599/mo annual, ex-GST; + 18% GST ≈ ₹1,887/mo | First-party |

All figures from each vendor's own pages in June 2026. Confirm before you buy.

A couple of honest notes. HealthPlix annual fees compute to ₹1,000–1,500 a month, which is the same band a standalone documentation layer occupies. Practo Ray is genuinely sales-gated; its website shows no prices, so any figure you see is a third-party estimate. The [full India clinic software comparison](/in/blog/best-clinic-management-software-india/) goes deeper on per-feature scoring if the table leaves a gap.

## ABDM, plainly stated

If your OPD software brochure says "ABDM compliant," slow down. That phrase can mean almost anything.

The National Health Authority's sandbox-to-production process certifies software against three separate milestones, and each does a different job. M1 makes the software an identity provider: it can create and verify an ABHA number and register the clinic on the Health Facility Registry (HFR) and Health Professional Registry (HPR). M2 makes it a Health Information Provider: it can share a patient's records as FHIR bundles when the patient consents. M3 makes it a Health Information User: it can pull records from other providers into your view.

Certification is per-software, not per-clinic. The vendor clears the sandbox once; each facility registers itself separately. A product that can create ABHAs (M1) but has not reached record-sharing (M2) is "ABDM-ready" in marketing and half-built in practice.

We will be straight here: AI Medical Scribe by Patient Square has ABDM integration on its roadmap, not shipped. We will not claim a milestone we do not hold. If you need live ABDM record linking from your OPD today, your shortlist is software that has cleared at least M1 and M2 in production. Ask for the NHA certification reference, not just the badge on the pricing page.

## Where a documentation layer fits alongside your OPD software

You do not have to choose between good OPD software and a complete note. The two solve different problems, and they work together.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It sits alongside your existing OPD software. The OPD system keeps doing registration, the queue, billing, and storage. The scribe handles the one thing the packed OPD never had time for: writing the note.

A few things that matter specifically for an Indian OPD. The scribe captures English, Hindi, and 20+ Indian languages, including the mid-sentence Hindi-English mixing of a real consult, and the note always comes back in clean clinical English. The prescription comes back as a draft built from the plan you dictated; you review the drugs, doses, and instructions and sign. It doesn't run an automated interaction or dosing check, and it never goes to a pharmacy on its own. The clinical judgment stays yours, the way it already is on a paper script. Visit audio is processed in memory and discarded the moment the note drafts; there is no recording sitting on a server anywhere, which is the cleaner answer under DPDP Act 2023 and the one we would want if the roles were reversed. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That is the part that scales with the 200-patient day. The queue does not slow down, because the doctor is reviewing a draft instead of typing from scratch. The note does not get skipped, because it is already written. The after-OPD charting backlog disappears, because there is nothing left to catch up on.

On pricing, the documentation layer lands inside the same band as the OPD software it sits next to. Assist starts at ₹1,599 per clinician per month on annual billing, ex-GST. Add 18% GST and the invoice is about ₹1,887 a month. Move up to Copilot (₹2,399 ex-GST) and the bundled AI Copilot EHR and WhatsApp messaging come with it, so the tiers do gate features rather than just volume. There is a 7-day free trial through the India signup page. So it reads as one more clinic tool priced for the Indian market, not an import.

If you are comparing the India-facing ambient scribes head to head, EkaScribe, Augnito, and AI Medical Scribe by Patient Square are compared in the [India clinic software scorecard](/in/blog/best-clinic-management-software-india/).

## Deciding in one pass

Three questions get most clinics to a decision without spending a month on vendor demos.

What breaks on your busiest OPD day? If it is registration, queue management, or billing, you need OPD software that is fast at exactly those, and you should test it on a live high-volume demo. If it is the note that never gets written, no amount of OPD software fixes that, and a documentation layer does.

Does the vendor publish a first-party price, and what is the year-two renewal? Sales-gated pricing flexes with how hard you negotiate. A rupee figure on the page signals something real about how the vendor operates. Get the renewal number in writing before you sign.

Does the vendor answer "where does the visit audio go" in one clean sentence? If a product listens to the consultation, that question should have a short, specific answer. Vague answers on data handling tend to predict vague practices on data handling.

Sort those out and the choice mostly makes itself. If your OPD software is fine but the notes are thin because there is no time to write them, the missing piece is documentation, not a new system. Book a short demo and watch a real consult turn into a signed note, or read through the [pricing](../../pricing/) first. Either way, fix the layer that the busy day actually breaks.

---

## Where Does Your Patient Data Live? Data Residency, India
https://patientsquare.com/in/blog/ai-scribe-data-residency-india/
Published 2026-04-22 · Updated 2026-10-04 · Tags: data-residency, dpdp, india, privacy, compliance

What India's DPDP Act requires on data residency for an AI scribe, why localization is not the real test, and a data-location and deletion checklist.

No, not as a blanket rule. The DPDP Act 2023 provides a negative-list model for cross-border transfers when Section 16 commences on 13 May 2027. No restricted-country list has been notified. So there is no general data-localization mandate for clinical data today. Sector-specific rules can still impose higher bars.

India's DPDP Act does not, today, force patient data to live inside India. Section 16 will use a negative-list model when it commences on 13 May 2027. No restricted-country list has been notified; assess transfers under current applicable law and contracts. So when a vendor sells you on a Mumbai data centre, they're answering a question DPDP doesn't really ask. The questions that matter: is the data stored at all, who can reach it, can you delete it.

Most "data residency" pitches answer the geography question because geography is easy to demo. The rest of this page is what DPDP actually demands, why purpose limitation beats location, and a checklist you can run any vendor through in about ten minutes.

> **Key takeaways**
>
> - DPDP 2023 uses a negative-list, not mandatory localization: data may leave India unless the government restricts the destination. That restricted list isn't notified yet.
> - The forthcoming Section 8(7) erasure duty takes effect on 13 May 2027; plan purpose-limited use and retention now.
> - The DPDP Rules 2025 (notified 13 November 2025) phase in; cross-border and general security obligations land around 13 May 2027.
> - For an AI scribe, the audio is the residency problem. A tool that never stores it removes the question for the most sensitive artifact.
> - ABDM data rules and DPDP data rules are different things. Don't let a vendor blur them.

## Does DPDP require patient data to be stored in India?

Short answer: no general localization mandate, as of October 2026.

Section 16 of the DPDP Act 2023 provides a negative-list approach to cross-border transfers when it commences on 13 May 2027: a Data Fiduciary may transfer personal data outside India except to a country or territory the central government specifically restricts. ITIF and several Indian law firms have made the same point: that restricted list has not been notified, but Section 16 is not yet in force. Assess transfers under current applicable law and contracts. There's no blanket rule that clinical data must sit on Indian soil.

Two things keep that from being the whole story. Where another Indian law sets a higher bar for a particular sector, the higher bar still applies. DPDP doesn't dilute it. And the government has reserved the power to restrict specific categories or destinations later, public health among the sensitive sectors named. So "no localization mandate" is the position now, not a permanent guarantee. A vendor that tells you "DPDP requires Indian storage, and we provide it" is overstating the law to sell you a feature.

## If location isn't the test, what is?

Purpose limitation and deletion. These DPDP duties are scheduled to govern an AI scribe from 13 May 2027.

When it commences on 13 May 2027, Section 8(7) of the DPDP Act will require a Data Fiduciary to erase personal data "upon the Data Principal withdrawing her consent or as soon as it is reasonable to assume that the specified purpose is no longer being served, whichever is earlier," unless a law requires keeping it. Prepare for it as an operating instruction. Collect the visit data for one stated purpose, drafting your note. Use it only for that. Plan to delete it when the purpose is done or the patient pulls consent, unless another law requires retention.

So the geography question is a distraction. A recording that sits in an Indian data centre for six months while someone uses it to "improve the model" is a bigger DPDP problem than a note processed under a clear purpose and deletable on request. Where the data lives matters far less than how long it lives and what it's used for. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## The audio is the real residency problem

For a scribe, one artifact decides almost everything. The visit audio. That's the raw recording of what your patient said before any of it became a note, and it's the most sensitive thing the tool ever touches. Store that file anywhere, in India or not, and it becomes what a breach exposes and a court can reach.

So the cleanest answer to "where does my patient data live" is that the most sensitive part of it doesn't live anywhere. Here's our position, stated as ours. Visit audio is processed in memory and discarded the moment the note is drafted. Nothing to localize, breach, or subpoena. What survives is the note you reviewed and signed, encrypted at rest with AES-256, in transit with TLS 1.2 or newer, behind role-scoped, logged access. And for tier-2 and tier-3 clinics where the signal drops mid-OPD, capture works offline with on-device AES-256-GCM encryption and syncs later. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Worth doing before you sign anyone: the cross-vendor version of the audio question, [what happens to your visit audio across major scribes](/us/blog/ai-scribe-audio-retention/). The broader vetting routine lives in [the AI scribe security checklist](/us/blog/ai-scribe-security-checklist/), which puts the audio question first for exactly this reason. Want a clean audio answer? <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and ask it before anyone talks features.

## The clinic data-location and deletion checklist

Run any India scribe vendor through this. Every question here prepares you for two DPDP duties scheduled for 13 May 2027: whether you keep control of the data, and whether you can walk away with it.

| Check | Ask | A good answer | A red-flag answer |
|---|---|---|---|
| Audio | Do you store the visit recording? | Live consultation audio is processed in memory and discarded at note draft; uploaded recordings use a separate retention mode with explicit consent. | "Retained for model improvement," no timeline. |
| Storage | Where are notes stored, and is that disclosed? | Named region and provider, in writing. | "Securely in the cloud," no specifics. |
| Purpose | Is my data used for anything beyond drafting my notes? | No, or a written, separate answer for any other use. | "To improve our service" with no limit. |
| Deletion | Can I delete any visit myself, anytime? | Yes, self-serve, testable in a trial. | Delete only by support request. |
| Export | Can I export my notes and leave? | Yes, full export, any time. | Export gated or undefined. |
| Retention | What's your default retention, and can I set it? | Stated default, deletable on demand. | Indefinite, or unstated. |
| Consent | How do you handle DPDP consent and withdrawal? | Consent-first capture, erase on withdrawal. | "We're DPDP compliant," no mechanics. |
| ABDM | Are you ABDM-integrated, or is that on a roadmap? | A straight answer that doesn't conflate ABDM with DPDP. | Implies ABDM-certified when it isn't. |

That last row needs an honest concession from us. ABDM integration is on our roadmap, not live. Some India-native platforms do have live ABDM integration today, and if ABDM connectivity is a hard requirement for your practice right now, that's a genuine reason to look at them. We won't pretend otherwise. The point we will make plainly: DPDP-aligned handling and ABDM integration are two different claims. We meet the first and we're honest about the second.

## How DPDP's timeline changes what you should ask in 2026

The DPDP Rules 2025 were notified on 13 November 2025, and they don't all switch on at once. Consent-manager provisions come into force around 13 November 2026. The heavier set, general obligations covering security safeguards, breach reporting, and the cross-border transfer framework, comes into force around 13 May 2027. Clinics get a transition window.

For a buyer today that means you're choosing a vendor in the run-up to those obligations. Pick one whose posture already matches where the law is going (consent-first, purpose-limited, deletable) instead of one that'll be scrambling to retrofit it in early 2027. The phased calendar in plain language is in our [DPDP for clinics guide](../dpdp-act-clinics-guide/). The ownership half of this question, who actually owns the notes and how you exit, is in [who owns your AI scribe notes](/us/blog/ai-scribe-data-ownership-export/).

## What it costs, and the honest GST line

Pricing earns a spot in a residency conversation for one reason: lock-in and surprise costs are their own kind of risk. So, plainly. Practice Copilot starts in India at ₹1,599 per clinician per month on the annual Assist plan, ex-GST. Add 18% GST and that's ₹1,887 per clinician per month all-in. The plan you pick decides what's bundled: Copilot (₹2,399/mo annual) adds an AI EHR and WhatsApp, Autopilot (₹3,999/mo annual) adds the receptionist and follow-ups, and there's a 7-day free trial on all of them. The full ladder, month-to-month and annual, sits on the [pricing page](../../pricing/), and the India-specific rate-card breakdown is in [AI medical scribe price in India](../ai-medical-scribe-price-india/).

And the canonical line, so you know exactly what's being handled to DPDP standards: Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR.

## The short version for a clinic deciding this week

Five things, in order:

1. Stop asking only where the data lives. DPDP doesn't mandate Indian storage today. Its purpose limitation and erasure duties commence on 13 May 2027.
2. Ask whether the audio is stored at all. The recording is the residency problem, and a no-storage scribe removes it.
3. Confirm you can delete and export any visit yourself, without filing a support ticket to do it.
4. Keep DPDP and ABDM separate. They're different claims, so make the vendor answer both honestly.
5. Pick a posture, not a promise. Consent-first and purpose-limited is where the law lands in 2027, so choose a vendor already there.

The cleanest way to test all of it is a quiet week of real OPD visits with you working the deletion and export functions yourself. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, ask where the audio goes first, then run a <a href={CTA_URLS.in.trial}>7-day free trial</a> on your own clinic days and check every answer against what they told you.

---

## Dragon Medical One Cost in 2026 vs an Ambient Scribe
https://patientsquare.com/us/blog/dragon-medical-one-cost/
Published 2026-04-22 · Updated 2026-07-22 · Tags: pricing, dragon-medical-one, comparison

Dragon Medical One runs $79 to $99 per provider per month plus a $525 setup fee on a multi-year contract. Here is the full cost versus a published-rate ambient scribe.

Resellers publish Dragon Medical One at $99 per provider per month on a 1-year contract, $89 on a 2-year contract, and $79 on a 3-year contract, plus a one-time setup fee of about $525 per user. Microsoft does not post a single list price, so the figure you pay depends on your contract length and reseller. Returning customers are sometimes quoted $79 on a 1-year term.

Dragon Medical One costs $79 to $99 per provider per month, plus a one-time setup fee of about $525 per user, and the lower monthly numbers only apply if you sign a two- or three-year contract. There is no public checkout page. You get a quote from Microsoft or a reseller, and the number moves with your term length.

If you are pricing Dragon right now, that is the headline. The rest of this page is the part the quote does not show you: the setup fee, the contract lock-in, and the cost of the dictation workflow itself, which is the line item nobody puts on an invoice.

> **Key takeaways**
>
> - Dragon Medical One list pricing from resellers in 2026: $99/provider/month (1-year), $89 (2-year), $79 (3-year), plus a ~$525 one-time setup fee per user.
> - Microsoft does not publish a single list price; you buy through a rep or reseller, so the real number depends on your contract length.
> - Dragon Medical One is the dictation engine. Dragon Copilot (formerly DAX) is the separate ambient product, and it does not publish monthly list prices at all.
> - The subscription is close to a published-rate ambient scribe on the monthly number. The gap is the setup fee, the multi-year commitment, and the workflow.
> - Dictation still makes you narrate the note from memory after the visit. Ambient capture drafts it from the conversation, which is the cost most pricing pages ignore.

## What Dragon Medical One actually costs in 2026

The number depends entirely on how long you are willing to commit. Reseller pages in 2026 quote three tiers for Dragon Medical One, the cloud dictation product:

- $99 per provider per month on a 1-year contract, about $1,188 a year.
- $89 per provider per month on a 2-year contract, about $1,068 a year.
- $79 per provider per month on a 3-year contract, about $948 a year.

On top of that, expect a one-time setup fee of about $525 per user. One reseller notes this can run higher for "complicated installs such as certain VDI configurations," which is common in hospital and large-group environments. Returning customers are sometimes quoted the $79 rate on a 1-year term, so the exact figure you see will vary by reseller and history.

Two things to sit with before you sign anything.

First, the cheapest monthly rate is a three-year decision. To get $79 a month you are committing to 36 months. That is not a software subscription you can cancel next quarter if the workflow does not stick; it is a contract. Across three years at $79, the subscription alone is roughly $2,844 per provider, and the setup fee pushes the all-in to about $3,369 before microphones or VDI work.

Second, there is no list price you can just look up. Dragon Medical One is sold through Microsoft sales reps and certified resellers. The published numbers come from those resellers, not a checkout page, which means your quote is a negotiation, not a posted rate.

## Dragon Medical One is not Dragon Copilot, and the difference matters for cost

This trips up a lot of people pricing Dragon in 2026, so it is worth being precise.

**Dragon Medical One** is the dictation engine. You speak, it transcribes in real time, and you assemble the note yourself, by voice instead of by keyboard. That is the product with the $79 to $99 reseller pricing above.

**Dragon Copilot** is the newer ambient product, which absorbed DAX. It captures the patient conversation and generates a draft note, rather than transcribing your spoken narration. It is sold separately from Dragon Medical One. And if you are trying to budget, this is the part that complicates things: Dragon Copilot does not publish monthly subscription list prices at all. It is quoted per organization, often with consumption-based components, so a solo clinician or small group cannot easily price it without a sales conversation.

So when you compare "Dragon" to an ambient scribe, you are usually comparing the wrong two things. Dragon Medical One has a price you can find but a dictation workflow. Dragon Copilot has the ambient workflow but no price you can find. An ambient scribe with a published flat rate gives you both: the ambient workflow and a number you can see before you talk to anyone.

## The line item nobody invoices: the dictation workflow

Here is the cost that does not appear on any Dragon quote.

Dictation moved clinicians off the keyboard, which was a real improvement over typing. But the structure of the work did not change. With dictation, you still finish the visit, then reconstruct the encounter from memory and narrate it. The note happens after the visit, in a separate block of time, built from your recollection of what was said.

That narration step is usually five to ten minutes of speaking per note, plus cleanup of misrecognized terms and restructuring into a proper note. Multiply that across a full clinic day and it is the documentation tail that follows clinicians home. A 2023 JAMA Network Open study found primary-care physicians log a median 36.2 minutes of EHR time per 30-minute visit; a 2016 Annals of Internal Medicine time-motion study found nearly two hours of EHR and desk work for every hour of direct patient care. Dictation trims the typing inside that work. It does not remove the after-visit reconstruction.

Ambient capture changes the structure, not just the input method. The conversation is captured during the visit, and the draft note is built from what was actually said. There is nothing to narrate afterward, because the encounter already happened on the record. You review a draft instead of producing one from memory. We go deeper on this in our breakdown of [ambient documentation versus dictation](../ambient-ai-vs-dictation/).

That is the cost the pricing page hides. Two products can land at nearly the same monthly number and have completely different daily realities: one where you still build the note after every visit, and one where you confirm a draft that was already written.

## The real cost comparison: Dragon Medical One vs an ambient scribe

Put the two side by side on the things that actually hit your budget and your evening. The Dragon column reflects the dictation product with published reseller pricing; figures marked as ranges or estimates are clearly labeled because Microsoft does not post a single list price.

A few notes on reading this honestly.

On the raw monthly number, the two land in the same place. Dragon's three-year rate is $79. The Assist plan from Patient Square is $79 per clinician per month on annual billing ($99 month to month). So if your only question is "which is the smaller monthly line item," this is a tie, not a win for either side.

The total cost of ownership is where it separates. Dragon's $79 is a three-year decision with a roughly $525 setup fee bolted onto year one, which pushes the first-year cost well above the ambient annual rate. The Assist annual plan is the same $79 with no setup fee and no multi-year lock-in, and a 7-day free trial lets you find out in a week, on your own patients, before any money changes hands. Same headline number, very different commitment.

And the column that does not have a dollar sign is the one that compounds. Dictation keeps the note as after-visit work. Ambient capture moves the note into the visit. Over a year of clinic days, that structural difference outweighs anything happening in the monthly-price cell.

## What you give up, and what you gain, switching from Dragon

Switching costs are real, so name them plainly.

Dragon Medical One has been around a long time, and that maturity counts. The dictation accuracy on medical vocabulary is well established, the integration story with Epic is deep, and if your whole organization already runs on it, there is real switching friction. If you are a heavy dictation user who genuinely prefers narrating notes by voice, the workflow is one you know.

What you gain by moving to an ambient scribe is the removal of the after-visit step entirely, plus a few things Dragon Medical One does not produce. The AI Medical Scribe is one module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The Rx is a draft: it reflects what was decided in the visit, and you review, adjust, and sign it. The scribe doesn't screen for drug interactions or dosing; that safety call stays with you, the prescriber. Dragon Medical One, as a dictation tool, does not draft codes or prescriptions; it transcribes what you say.

There is also the audio question, which matters more in healthcare than almost any other software category. Ask any vendor what happens to the visit recording and when it is deleted. AI Medical Scribe by Patient Square processes visit audio in memory and discards it once the note is drafted, so no audio archive exists. For a deeper look at the dictation-versus-transcription distinction, see our post on [AI scribes versus medical transcription services](../ai-scribe-vs-medical-transcription-service/).

## If you are specifically pricing Dragon Copilot

Some people land here because they were quoted Dragon Copilot, the ambient product, and want to sanity-check the number.

The honest answer is that Dragon Copilot does not publish monthly subscription list prices, so there is no public figure to check it against. It is sold per organization, often with consumption-based components where usage maps to billable units. For a solo clinician or a small group, that usually means a sales process and a custom quote, rather than a rate you can read on a page and decide on the same day. If you want the wider set of ambient alternatives in this lineage, we cover it in our guide to [Nuance DAX and Dragon Copilot alternatives](../nuance-dax-dragon-copilot-alternatives/).

The contrast with a flat published rate is the point. When pricing is opaque, the cost of evaluation goes up: you spend time in sales conversations before you know if the product is even right for you. When pricing is flat and posted, you can model the cost first, request an assisted trial, and evaluate the real workflow after setup.

## The bottom line on cost

Dragon Medical One is a known quantity with a known dictation workflow, priced at $79 to $99 per provider per month through resellers, plus a setup fee, on a contract that gets cheaper the longer you commit. That is a fair deal if dictation is the workflow you want and you are ready to sign for multiple years.

If what you actually want is to stop building the note after every visit, the monthly number is not the deciding factor. The deciding factor is whether the note gets written during the visit or after it. Run the math on your own volume, then run a real clinic week and see which workflow you would rather keep.

Practice Copilot from Patient Square, with the AI Medical Scribe at its core, starts at $79 per clinician per month on the annual Assist plan ($99 month to month), with no setup fee and an assisted 7-day trial after workspace setup. The [pricing page](../../pricing/) has the full tier structure, including the Copilot plan that bundles an AI EHR, with no sales call needed to see it. Try it on a real week of patients before you commit to anything, here or anywhere else.

---

## Who Owns Your AI Medical Scribe Notes? Ownership and Exit Rights
https://patientsquare.com/us/blog/ai-scribe-data-ownership-export/
Published 2026-04-21 · Updated 2026-08-27 · Tags: data-ownership, export, lock-in, privacy, buyer-guide

Who owns the notes an AI scribe drafts, the export and delete rights to demand, and the lock-in red flags that signal a vendor you can't leave cleanly.

Your practice does, or it should. The clinical record belongs to the practice that created it, and an AI scribe is a tool that drafts it, not a party that owns it. A trustworthy vendor states in the contract that notes belong to you and acts as a processor of your data, not an owner of it. If a vendor's terms claim rights over your clinical content, that is a deal-breaker.

Your practice owns the notes an AI scribe drafts, not the vendor. The scribe is a tool that types the record; the record belongs to you. So the questions that actually protect you are practical ones: can you export every visit yourself, can you delete any visit yourself, and what happens to your data the day you cancel. If a vendor can't answer all three cleanly, you don't fully own your data, whatever the marketing says.

That's the thesis. The rest of this walks through what ownership means in law, the export and delete rights worth demanding, the five lock-in red flags, and the one case where a little lock-in is actually a fair trade. We sell a scribe, so test every claim here during a trial.

> **Key takeaways**
>
> - The clinical record belongs to the practice. A trustworthy AI scribe processes your data; it doesn't own it.
> - Demand self-serve export of every visit and self-serve delete of any visit. Both, testable in a trial.
> - HIPAA gives patients an access right and expects your practice to manage its own records. Build that into the vendor test.
> - Five lock-in red flags: no self-serve export, closed-format export, ownership claims in the terms, unclear deletion, silent cancellation terms.
> - Accept lock-in only when you can name the concrete benefit you're buying with it.

## Who actually owns the notes an AI scribe drafts?

You do. The clinical record is the practice's record, created by the clinician, and a scribe, silicon or human, doesn't change who authored it. The vendor's correct role is a processor: it handles your data to draft your notes, under your instruction, and acquires no ownership of the clinical content.

The place this gets tested is the contract. Read the terms for two things. First, does the vendor explicitly state that your notes belong to you? It should be a sentence they'll sign, not a vibe on a landing page. Second, what rights does the vendor claim over your content, for "service improvement," model training, or anything else? Any claim of ownership, or a broad license over your clinical notes, is a deal-breaker. A processor needs permission to do its job and nothing beyond it.

Our position, stated plainly: notes belong to your practice, not to us. We act as a processor of your data, we don't sell or share clinical data, and you can take it with you whenever you want. The full posture, what's stored, who can access it, what's logged, is on our [security page](../../security/), and the broader vetting routine is in [the AI scribe security checklist](../ai-scribe-security-checklist/).

## What export and delete rights should you demand?

Ownership without export is ownership on paper. Two functional rights make it real.

Start with export. You should be able to pull every visit yourself, any time, in a format you can actually use outside the tool. Not a screenshot. Not a PDF dump that loses the structure of the note. And not an export you have to open a support ticket for and wait on. The test is simple. During the trial, export a week of notes and see if they come out complete and readable somewhere else. Can't run the export yourself? Then you don't control your data. The vendor does.

Delete is the other half. You should be able to remove any single visit yourself, any time, without "contact support to request deletion." Granular self-serve deletion is the clearest signal a vendor treats the data as yours. It's also a legal expectation. HIPAA frames patients' access rights and expects practices to manage their own records, which you can't do if removing a single visit means filing a ticket and waiting.

There's a deeper version of this for the most sensitive artifact, the audio. The cleanest delete is the one that already happened. A scribe that never stores the visit audio has nothing to delete, because it processed the recording in memory and discarded it at note draft. Ours works that way. The cross-vendor audio question is its own decision, walked through in [what happens to your visit audio across major scribes](../ai-scribe-audio-retention/).

## The five lock-in red flags

Run any vendor's terms and product through this. Each one is a way a vendor makes leaving harder than joining.

| # | Red flag | Why it traps you | What to ask instead |
|---|---|---|---|
| 1 | No self-serve export | You can only leave on the vendor's timeline and goodwill. | "Can I export every visit myself, today, without asking you?" |
| 2 | Closed or lossy export format | Your data comes out unusable, so it might as well stay in. | "What format is the export, and does it keep note structure?" |
| 3 | Ownership or broad-license terms | The vendor claims rights over your clinical content. | "Does the contract say my notes belong to my practice?" |
| 4 | Unclear deletion | You can't remove a visit without asking, or at all. | "Can I delete any single visit myself, any time?" |
| 5 | Silent cancellation terms | At exit, the vendor has the least reason to help. | "What happens to my data if I cancel, and on what timeline?" |

The pattern across all five: a vendor confident in its product makes leaving easy, because it expects you to stay because the product is good. When leaving has been made deliberately hard, ask why the product needs the friction to keep you.

## What happens to your data when you cancel?

This is the red flag buyers check last and regret first. Cancellation day is exactly when the vendor has the least reason to be helpful. So the protections have to be in the contract before you sign, not negotiated after.

A good cancellation clause is specific: your notes are returned or destroyed on your instruction, within a stated window, and the vendor confirms when it's done. A bad one is silence, or a sentence buried in a terms page that says the vendor "may retain data as required." Get the exit terms in writing up front. Our stance is that your data leaves with you, exportable any time, deletable any time, and we don't hold clinical content hostage to a renewal conversation. The technical side of the same trust question, what's encrypted, who can access notes, and how the audio is handled, sits alongside this one in [the AI scribe security checklist](../ai-scribe-security-checklist/).

## When is some lock-in a fair trade?

Honestly, sometimes it is. Not all friction is a trap, and pretending otherwise would be its own kind of dishonesty.

If a scribe is wired deep into your EHR, with a certified integration that writes notes straight into the chart and pulls patient context automatically, pure portability gets harder. But that integration can save real time and cut double-entry, and for a large health system that workflow benefit can outweigh the lower portability. That's a legitimate trade. The honest rule: accept lock-in only when you can name the concrete benefit you're buying with it. Write-back into the chart, a managed audit trail inside the EHR, enterprise identity at scale, some practices should pay portability for those.

And here's the truth about us. We don't integrate with EHRs. So if that deep-integration benefit is what you need, a health-system platform embedded in your EHR will serve you better than we will, and you'll accept more lock-in to get it. What we offer is the other side of that trade. Low lock-in. Notes exportable and deletable any time. Audio never stored. A product you stay on because it works, not because leaving hurts. Pick the side your practice actually needs.

The canonical line, so you know what you'd be staying with or leaving: Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot: an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan. Hospitals get Hospital Copilot, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. The bundled AI EHR is Patient Square's own, so a Copilot-tier practice keeps its notes in a record it owns and can export or delete anytime, not one wired into a third-party chart.

## How to verify ownership and exit before you sign

Twenty minutes of contract reading saves a painful migration later.

1. Find the ownership sentence. The terms should say your notes belong to your practice. If they don't, ask for it in writing.
2. Run the export yourself during the trial. A week of notes, exported by you, complete and readable elsewhere.
3. Delete a test visit yourself. Confirm it's granular and self-serve, not a support ticket.
4. Read the cancellation clause. Return or destruction, on your instruction, within a stated window.
5. Price the lock-in. If there's friction, name the benefit you're buying with it. No benefit, no friction worth accepting.

The cleanest test of all of this is a real week with the product, exercising export and delete with your own hands. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, ask who owns the notes and how you'd leave before you ask anything about features, then verify the export and deletion steps during an approved evaluation. A vendor that makes that easy is showing you something the sales deck can't.

---

## Cleaner Claims: How Notes Affect Cashless Approvals in India
https://patientsquare.com/in/blog/ai-scribe-cashless-claim-documentation/
Published 2026-04-20 · Tags: cashless, claims, documentation, india, irdai

How clinical documentation gaps drive cashless claim denials, what the IRDAI 1-hour and 3-hour timelines demand, and where a complete note helps pre-auth.

The pre-authorisation a hospital sends a TPA or insurer is built from the doctor's clinical notes: diagnosis, indication, planned treatment, and supporting findings. If the note is thin, contradictory, or missing the indication, the insurer queries or rejects it. Cleaner, complete documentation gives the pre-auth desk a stronger, faster case to submit.

A cashless claim lives or dies on the clinical note behind it. The pre-authorisation a hospital sends the insurer is assembled from what the doctor wrote: the diagnosis, the indication, the plan. When that note is thin or inconsistent, the insurer queries it, and queries burn the IRDAI clock. A complete note doesn't submit the claim for you, but it gives the pre-auth desk a stronger case and removes the documentation gaps that stall approvals.

> **Key takeaways**
>
> - Cashless pre-auth is built from clinical notes; a weak note is a weak claim before the insurer ever sees it.
> - The IRDAI Master Circular (29 May 2024) sets a 1-hour cashless authorisation and 3-hour discharge authorisation clock.
> - The biggest documentation cause of denials is insufficient or inconsistent notes, not coverage terms.
> - An AI scribe does not submit claims or touch TPA systems. It improves the note, which is the raw material the pre-auth is built from.

_Source: IRDAI Master Circular on Health Insurance Business, 29 May 2024 (IRDAI/HLT/CIR/MISC/77/05/2024)._

## How does a clinical note become a cashless approval or a denial?

Walk the chain. A patient presents for a planned procedure. The treating doctor documents the diagnosis, the clinical indication, the proposed treatment, and the supporting findings. The hospital's insurance or TPA desk takes that documentation and builds a pre-authorisation request. The insurer or TPA reads the request and decides: approve, query, or reject.

Notice where the doctor sits in that chain. Right at the top. Everything downstream, the pre-auth, the approval, the eventual settlement, is constructed from the clinical note. If the note doesn't state the indication for the procedure, the pre-auth can't either, and the insurer has grounds to query. If the diagnosis in the note doesn't line up with the treatment requested, that mismatch is exactly what a claims reviewer is trained to catch.

So "documentation drives claims" isn't a slogan from the billing department. It's the literal data flow. The note is the source document. A clean source produces a clean claim; a muddled one produces a query, and a query at minimum costs you time against the IRDAI clock.

## What do the IRDAI timelines actually require?

The IRDAI Master Circular on Health Insurance Business, dated 29 May 2024, rewrote the cashless rules of engagement. Two timelines matter for documentation pressure:

| Stage | IRDAI deadline | What it means at the bedside |
|---|---|---|
| Cashless authorisation request | Decision within **1 hour** | The pre-auth, built from your note, has to be approvable on first read |
| Final discharge authorisation | Within **3 hours** of the hospital's request | A discharge summary and supporting notes that hold together avoid a last-minute query |

The circular also puts teeth on the discharge clock: if the insurer delays final authorisation beyond three hours, it bears the additional hospital charges arising from that delay. The intent is to stop patients waiting on a bed for paperwork.

Here's the documentation angle the circular makes sharper. Faster mandated decisions mean less time for back-and-forth. A query that once got resolved over a leisurely afternoon now eats into a one-hour or three-hour window. The documentation that survives that pressure is the documentation that was complete and consistent the first time. Speed rewards clean notes and punishes thin ones. If your queries cluster on missing indications and inconsistent summaries, that's a note-quality problem worth seeing fixed live; <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> with a recently queried case in hand.

## Where do cashless claims actually break on documentation?

Not usually on coverage. On the note. The recurring documentation failure modes:

- Missing indication. The procedure is requested, but the note doesn't say why it's clinically necessary. The single most common query trigger.
- Diagnosis–treatment mismatch. The recorded diagnosis doesn't support the treatment or the length of stay. Reviewers flag this fast.
- Incomplete clinical picture. History or examination findings that would justify the decision aren't written down, so the decision looks unsupported.
- Inconsistency across documents. The admission note, progress notes, and discharge summary tell slightly different stories. Any gap between them is an opening for a query.

Each of these is a documentation-quality problem, and that's the good news, because documentation quality is fixable at the point of care. None of them is a coverage problem. A complete, internally consistent record doesn't make an excluded treatment covered. What it does is remove the avoidable reasons a covered treatment gets stalled or denied.

## How does an AI scribe help, and what it absolutely does not do

Let's be exact about the boundary, because this is where vendors oversell. AI Medical Scribe by Patient Square does not submit claims. It does not file pre-authorisations. It does not connect to any TPA, insurer, or hospital claims system. There is no claims integration, on our roadmap or off it. If a tool tells you it "automates your cashless approvals," ask hard questions, because the claims rail is not where an ambient scribe lives.

What it does is upstream and honest. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For the claims chain, that buys you three things.

A complete clinical note, with the indication, the findings, and the plan actually written down, is better raw material for whoever prepares the pre-auth. The ICD-10 suggestions give the diagnosis a coded anchor for the documentation, which the coder or billing desk still confirms; they are suggestions, not a coding engine, and not a billing submission. And a structured note is harder to leave half-empty than a free-text scrawl at the end of a long shift, so the encounter stays consistent with itself.

The mechanism is simple and modest: better notes in, fewer documentation-driven queries out. The pre-auth desk still does its job, the coder still codes, the insurer still decides on the policy terms. The scribe just stops the claim from starting life with a documentation gap. That's the only benefit we'll claim here, and it's a real one.

## So what can cleaner notes change, and what can't they?

Worth drawing the line clearly, because overpromising on claims is how trust dies.

Cleaner notes can reduce the documentation-driven slice of denials and queries. They support a faster first-pass approval against the IRDAI clock, and they give the discharge summary the consistency that avoids a last-minute hold.

What they can't do is override a policy exclusion, shrink a waiting period, lift a sub-limit, or approve a treatment the policy doesn't cover. Those are insurance terms. No note quality touches them, and any tool that implies otherwise is selling you something it can't deliver.

That narrow, real benefit is the one to test on your own documentation. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a recent case that got queried on documentation; watch what a complete structured note for that encounter would have looked like. Or run a <a href={CTA_URLS.in.trial}>7-day free trial</a> across a clinic day and check whether the notes coming out carry the indication and findings your pre-auth desk keeps asking for. If the medico-legal side of complete records is also on your mind, the [records-as-defence read](../ai-scribe-medico-legal-documentation-india/) and the [NMC record-keeping explainer](../nmc-record-keeping-ai-scribe/) cover that, and the [security page](../../security/) shows how the underlying data is handled.

---

## Medical Dictation & Transcription Software Compared (2026)
https://patientsquare.com/us/blog/medical-dictation-software-compared/
Published 2026-04-20 · Updated 2026-07-22 · Tags: dictation, transcription, comparison, pricing

An honest comparison of medical dictation and transcription software, Dragon Copilot, Freed, Sunoh, and the ambient alternative, on strengths and pricing.

There is no single best medical dictation tool; the right choice depends on whether you want to keep dictating or have an ambient system draft from the visit. Dragon Copilot is the deep Epic-oriented option, while Freed and Sunoh suit smaller practices. Compare workflow and verified current pricing before choosing.

If you are shopping for medical dictation or transcription software, the honest answer is that the best tool depends on one decision you probably have not made yet: do you want to keep dictating, or do you want the note to write itself from the visit. This page compares the named products clinicians actually evaluate, Dragon Copilot, Freed, Sunoh, Suki, and Nabla, with their real strengths, their published prices where they have one, and the workflow tradeoff underneath all of them.

A quick orientation, because the category is muddy. "Dictation software" used to mean push-to-talk: you speak, it types, you still build the note. Most of these tools have since bolted on ambient capture, where the software listens to the whole visit and drafts the note with no dictation at all. So the real choice is not Dragon versus Freed. It is dictation versus ambient. Get that right and the shortlist sorts itself out.

> **Key takeaways**
>
> - The market splits into two workflows: front-end dictation, where you still narrate the note, and ambient capture, where the visit conversation becomes the note.
> - Dragon Copilot is the deepest enterprise pick (Epic-native, dictation plus ambient) but publishes no list price; you buy through Microsoft or partners.
> - Freed ($39 to $119/mo) and Sunoh ($149/mo promo) are the transparent value picks for solo and small practices; Suki and Nabla publish no pricing at all.
> - A 2023 JAMA Network Open study found primary-care physicians log a median 36.2 minutes of EHR time per 30-minute visit, the burden any of these tools is trying to cut.
> - Patient Square competes on the ambient workflow plus a published ladder from $79/clinician/month annual, unlimited notes on every tier, with a bundled AI EHR from the Copilot plan.

## Dictation versus ambient: the choice underneath the shopping

Start here, because it changes which column of the comparison you should care about.

Front-end dictation is the older model. You speak the note out loud and the software transcribes it in real time. The work is faster than typing, but you are still the author composing from memory after the patient leaves. Dragon Medical One built its reputation on doing this well, and the engine is now part of Dragon Copilot.

Ambient capture is the newer model. The software listens to the actual conversation during the visit and drafts a structured note from what was said. There is no dictation step. You see the patient normally and review a draft a couple of minutes later. The narration work disappears instead of getting faster.

Here is the part that trips up evaluations: nearly every tool in this comparison now offers both modes. Dragon Copilot does. Nabla does. Suki does. So comparing them feature-by-feature on a spreadsheet misses the real question, which is which mode you actually want to live in. We break that tradeoff down in detail in our [ambient documentation versus dictation guide](../ambient-ai-vs-dictation/). If you already know you want a human-in-the-loop typing service rather than software, our [AI scribe versus transcription service comparison](../ai-scribe-vs-medical-transcription-service/) covers that fork instead.

The rest of this page assumes you are weighing software, and it concedes upfront that several of these products are genuinely good at what they do.

## The named products, and what each one is actually good at

No strawmen here. Each of these has a real reason clinicians pick it.

**Dragon Copilot (Microsoft / Nuance).** The most established name in clinical voice, full stop. It unifies the Dragon Medical One dictation engine with DAX ambient capture in one product, and it is built around Epic: physician documentation in Hyperdrive, nurse flowsheets, radiology via PowerScribe One, write-back through Epic FHIR APIs and the orders module. If your organization runs Epic and wants both dictation and ambient from one vendor with deep EHR write-back, nothing else matches its reach. The catch: there is no published subscription price. You buy through Microsoft reps or certified partners, and consumption runs around $0.01 per unit with an AI-assisted session costing roughly $0.25, per Microsoft's May 2026 licensing guidance. Our [Dragon Medical One cost breakdown](../dragon-medical-one-cost/) digs into that pricing model. {/* deep-link dragon-medical-one-cost once live */}

**Freed.** The clearest value play for solo and small practices. Pricing is published and honest: Starter at $39/month (capped at 40 notes), Core at $79/month unlimited, Premier at $119/month adding EHR push and ICD-10 coding. It pushes notes into browser-based EHRs through a Chrome extension and has real scale behind it. If you want a transparent price and a fast setup, Freed earns its shortlist spot.

**Sunoh.ai.** Distributed by eClinicalWorks, which matters if you are an eCW practice, because the integration is native via healow. Published price is $149 per user per month, promotional, marked down from $199. Ambient capture, draft SOAP, edit before EHR import. A solid pick if you are inside the eCW ecosystem.

**Suki.** Strong enterprise reach and a polished assistant that does ambient documentation plus dictation and voice commands, with deep bidirectional integrations into Epic, Oracle Health, athenahealth, and MEDITECH. The tradeoff for a shopper: no public pricing, sales-led only. You will be talking to a rep before you see a number.

**Nabla.** A credible ambient product with both conversation capture and a dedicated dictation mode, real published evidence behind it, and wide EHR coverage. Like Suki, it is sales-led: the pricing page returns a 404, and the fee scales with user count by undisclosed amount. Good tool, opaque price.

The honest summary: if you want depth and you live in Epic, Dragon Copilot. If you want a transparent self-serve price, Freed or Sunoh. If you are fine with a sales call, Suki and Nabla are real. What none of them lead with is a flat, published price for an ambient-first workflow, which is the gap the next section is about.

## Medical dictation and transcription software compared

This table is scoped to the things that actually differ across tools and that a clinician can verify. Pricing is per clinician per month, US, as published by each vendor or marked as sales-led where no price exists.

Two rows on that table are worth pausing on, because they are where the products diverge most and where the marketing language gets vaguest.

### What happens to the audio

The visit recording is the most sensitive artifact in the whole workflow. It holds everything that did not make the note, the aside about a mental health struggle, the substance use mention, the thing said off the record. So "what happens to the audio, and when is it gone" is the first question to ask any vendor, not the last.

Most tools answer this in their terms rather than on the homepage, and the answers vary: some retain audio for days or weeks for model improvement or quality review, some let you opt out, some are deliberately vague. None of those is automatically disqualifying, but you should get a one-sentence answer with a specific timeline before you sign.

AI Medical Scribe by Patient Square processes visit audio in memory and discards it once the note is drafted. No audio archive exists on our side or the practice's. What survives is the note you reviewed and signed. The full posture is on the [security page](../../security/).

### Published price versus "talk to sales"

Of the named ambient tools, only Freed and Sunoh put a real self-serve number in front of you. Dragon Copilot routes you through Microsoft or a partner. Suki and Nabla publish nothing; Nabla actively removed its pricing page. That is a legitimate enterprise sales motion, but for a clinician sizing a single-provider or small-group decision, an opaque price is a cost in itself, the cost of a sales cycle and the uncertainty of where you will land.

Patient Square publishes its US ladder openly on the [pricing page](../../pricing/), starting at $79 per clinician per month on annual billing (Assist), with unlimited notes on every tier. No call required to see the number.

## What AI Medical Scribe by Patient Square adds, honestly stated

This is the part where a comparison page is supposed to claim a clean sweep. It will not, because two of these competitors are genuinely deeper than us in specific ways: Dragon Copilot's Epic write-back is unmatched, and Suki's enterprise integration breadth is real. If deep bidirectional EHR integration is your hard requirement, those tools are built for it and we are not.

What we are built for is the ambient workflow at a flat, honest price, with things bundled in that the dictation-first tools do not lead with.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription draft and the ICD-10 suggestions come with the note, not as an upsell tier.

The prescription is a draft, and it stays one. The scribe doesn't screen it for interactions, dosing, or contraindications, and it never goes to a pharmacy on its own. You are the safety check: you read the draft, adjust it, and sign it, exactly as you check every script today. Be wary of any tool that implies software will catch a bad prescription for you. We go deeper on how the draft works in our [prescription draft post](../ai-scribe-prescription-draft-safety/).

And it works alongside whatever EHR you already use rather than integrating with it. You review the note and move it into your chart. That keeps setup to about a day. The tradeoff is honest: you do not get one-click write-back into Epic the way Dragon does. For an EHR-agnostic practice, that is usually the better deal; for a deep-Epic shop, it may not be. Pick accordingly.

## Does the time savings justify any of this

Worth grounding in the evidence, because the category oversells and the data is more measured than the pitches.

A 2023 JAMA Network Open study found primary-care physicians log a median 36.2 minutes of EHR time per 30-minute visit. The documentation now outlasts the appointment, which is the burden every tool here is trying to cut.

A 2026 JAMA study across five health systems and more than 1,800 clinicians found ambient tools saved about 16 minutes of documentation time per 8-hour shift and about 13 fewer EHR minutes, versus matched controls. The paper's own framing was "modest reductions," which is the honest read. The objective time savings are real but moderate; some studies find the wellbeing gains larger than the raw minutes.

So do not buy on a vendor's "save two hours a day" headline. Buy on what the tool does to your actual note quality and your actual review time, measured on your actual patients. A draft you sign in 90 seconds beats one you spend five minutes fixing, regardless of the sticker.

## How to run the evaluation that actually decides it

Every demo runs on a clean exam room and a cooperative patient. Your Thursday clinic is neither.

Pull your five hardest visit types from last week: the patient who talks in circles, the one with three complaints, the one whose family member answers most questions, the one with an accent your autocomplete already mangles, the one whose visit went somewhere unexpected. Run those through any tool on your shortlist and read every draft closely.

Check the things that separate a real note from a plausible one. Does the assessment match your clinical reasoning, or the most likely diagnosis given the chief complaint? Are medication names, doses, and frequencies right? Is anything in the note that was not actually said? A tool that invents a denial of symptoms is worse than no tool.

Then do the price arithmetic on your real volume, not a vendor's example. A flat fee is predictable; a per-session or per-line model moves with your busiest days, which are exactly the days you most need help.

AI Medical Scribe by Patient Square includes an assisted 7-day trial after workspace setup, enough for one real clinic week. The [pricing page](../../pricing/) shows the full ladder, from $79/month annual, with no sales call needed to read it. Run it against whatever else is on your shortlist and judge the drafts before you commit.

---

## India AI Medical Scribe Buyer's Guide: What ₹1,599 Should Buy
https://patientsquare.com/in/blog/ai-medical-scribe-cost-india-buyers-guide/
Published 2026-04-17 · Tags: india, pricing, buyers-guide, ai-scribe

A scorecard for buying an AI medical scribe in India: what to demand on price, language, DPDP, prescriptions, and offline capture, with the GST math shown.

The published India-native scribe-only anchor is EkaScribe Pro at ₹1,499 per doctor per month. AI Medical Scribe by Patient Square is ₹1,599 per clinician per month on annual billing (Assist tier), ex-GST, so ₹1,887 on the invoice with 18% GST, and that one price bundles the scribe with practice tools rather than billing an EMR separately. Pair EkaScribe with an EMR and the eka stack runs ₹2,600 to 3,000. US-built tools bought from India run roughly ₹6,500 to ₹12,500.

For ₹1,499 to ₹1,599 a month, an AI scribe in India should capture a Hindi or code-mixed consult, build a live transcript as you speak and hand back a clean English note the moment the visit ends, draft a checked prescription, hold a clear DPDP and audio-retention posture, and keep working when the OPD signal drops. That's the bar. Anything priced like a US tool, ₹6,500 to ₹12,500, is asking you to pay several times the native rate for the same job. This guide is the scorecard. Not a rate card.

Want the ₹ table instead? Our [India AI scribe price comparison](../ai-medical-scribe-price-india/) lays the numbers out vendor by vendor. This page is the other half: the criteria behind the numbers, so you know what each rupee is supposed to buy.

> **Key takeaways**
>
> - The published India-native scribe-only anchor is EkaScribe Pro at ₹1,499/month. Our Assist plan is ₹1,599/month ex-GST on annual billing, so ₹1,887 with 18% GST, and that price bundles scribe plus practice tools. Add an EMR to EkaScribe and the eka stack runs ₹2,600 to 3,000/month.
> - US-built scribes convert to ₹6,500 to ₹12,500/month for no India-specific advantage.
> - Price is the entry ticket. Language, DPDP posture, prescription drafting, and offline capture are what decide a real OPD day.
> - On ABDM, eka.care is live today; ours is on the roadmap. If you need ABHA linking now, that's a genuine mark for eka.care.
> - A scribe and a full EMR solve different problems. Don't buy a ₹18,000-a-year EMR if your pain is just the note; our bundle covers scribe plus practice tools, not the full clinic stack.

## What ₹1,499 to ₹1,599 actually buys in 2026

Set the price floor honestly. EkaScribe Pro, the published India-native scribe, is ₹1,499 per doctor per month billed monthly for the scribe alone, with a free tier capped at five consultations a day and roughly 17% off on annual billing; its EMR is a separate eka plan. Augnito publishes no website price, its pricing page routes to sales, though its India App Store listing shows a "Standard" in-app tier at ₹1,199 (the billing period isn't labeled, so monthly is an inference, not a published fact). AI Medical Scribe by Patient Square (Assist tier) is ₹1,599 per clinician per month on annual billing, ex-GST, and that one price bundles the scribe with practice tools. Add 18% GST and the invoice reads ₹1,887.

Now the contrast that should shape the whole decision. A US-built scribe priced at $89 to $149 converts to roughly ₹6,500 to ₹12,500 a month when you buy it from India (per third-party 2026 roundups; Sunoh's $149 matches its own published rate). Four to eight times the native anchor, for a tool that wasn't built for a Hindi OPD. The reason matters. Those tools price in dollars for a market where clinic software costs more. India's established clinic-software budget sits around ₹1,000 to ₹1,500 per doctor per month, the band where Practo Ray and HealthPlix's tiers land. A scribe priced inside that band reads as another clinic tool. One priced at ₹10,000 reads as an imported luxury.

So price screens out the imports. Everything below is how you choose among the tools that pass that screen. If you'd rather see the difference than read about it, book a demo and watch a Hinglish consult turn into an English note on your own phone.

## The five-axis India buyer's scorecard

Score every vendor on these, weighted for an Indian practice. Price is one row, not the whole sheet.

| Axis | What to demand | Why it matters in India |
|---|---|---|
| **Price (₹, with GST shown)** | A ₹ figure, ex-GST stated, "+ 18% GST" disclosed, no USD conversion | Imported pricing is the single biggest overpay risk |
| **Language** | Hindi and code-mixed (Hinglish) capture on input; clean English note out | Consults run in Hindi/regional/mixed; records and claims need English |
| **DPDP and audio** | DPDP Act 2023 posture; a one-sentence audio-retention answer with a timeline | Consent-first handling is the new baseline; retained audio is exposure |
| **Prescription** | A drafted prescription, ideally with a safety check, that you review and sign | The Rx is the next action after the note; a note-only tool stops short |
| **Offline capture** | Encrypted capture that works when the signal drops mid-OPD | Tier-2 and tier-3 clinics lose connectivity; the tool can't stall with it |

Here's how we score on our own card, stated as claims you can verify, not adjectives. AI Medical Scribe by Patient Square is an ambient AI medical scribe that builds a live transcript as you speak and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft the moment the visit ends, ready to review and sign. Language: English, Hindi, and 20+ Indian languages on input, code-mixing included, with the note always returned in clean clinical English, the longer worked example is in our [Hindi and Indian-languages explainer](../ai-scribe-hindi-indian-languages/). DPDP and audio: handled to DPDP Act 2023 standards, and visit audio is processed in memory and discarded the moment the note drafts, so there's no archive, the full posture is on our [security page](../../security/). Prescription: a draft only, one you review, adjust, and sign, and it never goes to a pharmacy. The scribe writes down what the visit called for; you stay the safety check, the way you already are with a handwritten script. Offline: encrypted capture (AES-256-GCM on the device) for low-signal clinics, syncing when the connection returns. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Run the same five rows on every shortlisted vendor and the differences stop being about logos. When you want to score us on the card yourself, book a demo and bring your hardest OPD scenario to it.

## The GST math, shown once so you stop guessing

Indian B2B software is quoted ex-GST. So a "₹1,599" headline isn't your invoice. Here's the arithmetic, once, so you can do it for any vendor:

₹1,599 ex-GST × 1.18 (18% GST) = **₹1,887 on the invoice.**

Do the same for the others: EkaScribe's ₹1,499 becomes about ₹1,769 with GST; our Copilot annual rate at ₹2,399 becomes about ₹2,831. The rule for the whole shortlist: make every vendor show the ex-GST figure and confirm the GST treatment in writing before you compare. A vendor that quotes a with-GST number against a competitor's ex-GST number is comparing apples to a heavier apple.

## Where eka.care and a full EMR fit better than we do

The honest part. A buyer's guide that only flatters its author isn't a guide.

Start with ABDM, where eka.care wins today. eka.care has live ABDM integration; you can link records to ABHA inside the tool now. Ours is on the roadmap, not live. If ABHA linking from inside the scribe is a present requirement, maybe because you're chasing AB-PMJAY empanelment or DHIS incentives, that's a real and current advantage for eka.care, and we'd point you there for it. We're building toward it. We're not there. Our full three-way breakdown, concessions included, is in the [EkaScribe vs Augnito comparison](../india-ai-scribe-comparison/).

A full EMR wins on a different axis: when you need the whole clinic stack. A scribe writes the note. An EMR like HealthPlix manages billing, pharmacy, IPD, lab, and the rest of the practice, which is why its tiers run ₹11,999 to ₹17,999 a year. If your pain is "I need to run the whole clinic on one system," buy the EMR; a scribe won't do it. But if the pain is narrower, with documentation eating your OPD day, paying ₹18,000 a year for an EMR to solve a note problem is overbuying. A focused scribe at ₹1,499 to ₹1,599 is the sharper fix, and our Assist bundle at ₹1,599 adds scheduling and practice tools without the full-EMR price.

Match the tool to the problem you actually have, not the one with the longest feature list.

## How to run the purchase in a week

1. Screen out the imports on price. If a vendor only quotes dollars or converts to ₹6,500-plus, it isn't built for your market.
2. Score the survivors on all five axes, not just price. A cheap tool that mangles a Hinglish consult costs you more in edits than it saves.
3. Get the ₹ figure ex-GST in writing, GST treatment confirmed, for every vendor.
4. Decide your ABDM timeline. Need it now, eka.care is on your list. Need it later, weigh language, prescriptions, and offline first.
5. Trial on a real OPD day. Not a scripted demo. A genuine 40-to-60-patient morning with the languages and interruptions your clinic actually has.

The rate card with every ₹ figure and the GST note beside each is in our [India price comparison](../ai-medical-scribe-price-india/); the security posture is on the [security page](../../security/). When you've scored the shortlist, book a demo and make each vendor put their ₹ number and GST treatment in writing, then <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, then run it on a real Tuesday OPD before anyone signs. The scorecard tells you what to demand. Your own patients tell you who delivers.

---

## HIPAA-Compliant Transcription Software: The Audio Pipeline
https://patientsquare.com/us/blog/hipaa-compliant-ai-transcription/
Published 2026-04-17 · Tags: hipaa, transcription, compliance, security

What HIPAA-compliant transcription software does to your audio. The pipeline stage by stage, why in-memory beats stored recordings, and how to vet a vendor.

There is no HIPAA certification, so "HIPAA-compliant transcription software" describes how the software handles protected health information, not a badge it holds. The real markers are a signed Business Associate Agreement, encryption in transit and at rest, role-scoped and logged access, and a clear answer to what happens to the visit audio. The strongest version of that last answer is audio that is processed in memory and discarded once the note is drafted, so no recording is ever stored.

If you are vetting HIPAA-compliant transcription software, the question that actually matters is not what badge a vendor claims. It is what the software does to your audio. A recording of a patient visit is one of the most sensitive files a practice ever creates, and where that file goes after it is captured is the difference between a tool that protects you and one that quietly builds a liability you will never see until it leaks.

This page walks the audio pipeline one stage at a time. Capture, transcribe, draft, discard. By the end you can tell a tool that holds onto recordings from one that never keeps them at all. Then it covers the paperwork (the Business Associate Agreement), the encryption, and the exact questions to put to a vendor before you let it near a real visit.

> **Key takeaways**
>
> - "HIPAA-compliant transcription software" is not a certificate. HHS does not certify any product as HIPAA compliant, so the phrase describes how the software handles protected health information.
> - The strongest privacy posture is audio that is processed in memory and discarded once the note is drafted. No stored recording means nothing to leak, subpoena, or breach.
> - Some vendors retain visit audio for days or weeks; some keep it indefinitely; some never store it. This is the single most important thing to nail down before you sign.
> - A Business Associate Agreement is required, not optional. A transcription vendor that handles patient audio is a business associate under HIPAA.
> - The cleanest evaluation is to follow your audio through the pipeline and confirm what survives at each step.

## What "HIPAA-compliant transcription software" actually means

There is no such thing as HIPAA-certified software. The Department of Health and Human Services has stated plainly that it does not certify businesses or products as HIPAA compliant, and the Office for Civil Rights does not issue any kind of HIPAA certificate. So when a vendor's marketing page says "HIPAA certified," it is describing something that does not exist.

What does exist is a set of obligations the software and the vendor have to meet, and proof that they meet them. Compliant transcription software handles protected health information under the HIPAA Security Rule, with encryption, access controls, and audit logging, and the vendor signs a Business Associate Agreement that puts those obligations in writing. The phrase "HIPAA-compliant transcription software" is shorthand for all of that. It is a description of behavior, not a label.

That distinction matters for how you shop. You cannot ask to see a certificate, because there isn't one. You can, and should, ask to see the BAA and ask precisely what the software does with the audio at each step. Our companion piece on [HIPAA, BAAs, and consent for AI scribes](../ai-scribe-hipaa-baa-consent/) goes deep on the agreement itself and on the state recording-consent laws that sit alongside it.

## The audio pipeline: what happens to a visit recording, stage by stage

Every transcription tool moves your audio through the same four stages. The differences that matter for HIPAA are about what each tool keeps at each stage, and for how long. Walk the pipeline and the vendor differences stop being abstract.

### Stage one: capture

The software turns on a microphone and captures the conversation in the room. At this point the audio is the most complete and most sensitive it will ever be. It contains everything: the small talk, the off-the-record aside, the disclosure the patient asked you not to write down.

The question to ask at this stage is whether capture happens on the device or streams immediately to a server, and whether anything is written to disk. Tools built for low-connectivity settings sometimes buffer audio locally; if they do, that buffer should be encrypted. AI Medical Scribe by Patient Square uses offline encrypted capture (AES-256-GCM on-device) so that even a buffered segment in a clinic with patchy wifi is protected before it moves anywhere.

### Stage two: transcribe

The captured audio is converted to text. This is the speech-recognition layer, where the audio is actively in use, being read by a model and turned into a transcript. Some architectures stream the audio to a transcription service and process it as it arrives. Others upload the whole file first.

The HIPAA-relevant question here is not accuracy. It is location and persistence. Is the audio held in memory while it is transcribed, or is it written to a file on a server that then has to be secured, logged, and eventually deleted? A file that exists, even briefly, is a file that can be backed up, copied, or forgotten. Audio that lives only in memory during processing never becomes that kind of artifact.

### Stage three: draft

A language model takes the transcript and writes the structured note: the SOAP note, plus whatever else the tool produces. By this stage the clinically relevant content has been extracted into text. The original audio has done its job.

This is the decision point that separates tools. Some keep the audio around after the draft exists, on the theory that it is useful for model training, quality review, or settling a later dispute about what was said. Others treat the moment the note is drafted as the moment the audio is no longer needed.

### Stage four: discard (or retain)

Here is where "HIPAA-compliant transcription software" splits into two genuinely different products.

One kind of tool retains the recording. It might keep it for 30 days, or 90, or indefinitely, and it might or might not let you opt out. Every day that recording exists, it is something that has to be encrypted, access-controlled, included in your risk analysis, and produced if a court asks for it. The retention is a feature for the vendor and a standing exposure for the practice.

The other kind of tool discards the audio the instant the note is drafted. AI Medical Scribe by Patient Square processes visit audio in memory and discards it once the note is drafted, so no audio archive exists, not on our side and not on the practice's. What survives the pipeline is the note you reviewed and signed. Nothing else. There is no recording to leak in a breach, to hand over under subpoena, or to find years later in a backup nobody remembered. The full posture is documented on the [security page](../../security/).

## What each tool does with your audio: a side-by-side

The four-stage pipeline turns into a buyer's checklist. Instead of comparing marketing claims, compare what survives at each stage. The table below contrasts the two architectures you will actually encounter, a tool that stores recordings versus one that processes audio in memory and discards it, with AI Medical Scribe by Patient Square as the in-memory reference.

The pattern is the point. The fewer rows where an audio file survives, the smaller the surface where protected health information can be exposed. A tool that never writes the recording to a server, and discards it in memory the moment the note exists, has the shortest pipeline and the least to go wrong. If you want to turn this into a full procurement pass, our [AI scribe security checklist](../ai-scribe-security-checklist/) lays out the line items to verify before you buy.

## Why the stored recording is the real risk

It is tempting to treat audio retention as a minor setting. It is not. The recording is more sensitive than the note it produces, because the note is curated and the recording is raw.

A clinical note is what you decided to write down. The audio is everything that was said: the comment about a spouse, the question the patient walked back, the mention of a medication they take but did not want in the chart. A breach of stored notes is bad. A breach of stored audio is worse, because it exposes the unedited encounter.

Stored recordings also pull a practice into obligations that have nothing to do with documentation. Every retained audio file is in scope for your HIPAA risk analysis. It can be discoverable in litigation. It has to be deleted on a schedule someone has to own and audit. None of that work exists if the audio was never stored. The cleanest way to handle a sensitive artifact is to not keep it, a principle that lines up with the data-minimization spirit of the Security Rule's risk-analysis guidance. Our deeper look at [where visit audio goes across vendors](../ai-scribe-audio-retention/) compares published retention windows if you want to see how far apart vendors actually are.

## The paperwork: Business Associate Agreement

The pipeline is the technical half. The Business Associate Agreement is the legal half, and you need both.

A transcription vendor that receives or processes patient audio on your behalf is, by definition, a business associate under HIPAA. The Privacy Rule requires a written agreement before any protected health information flows to them. This is true whether you are a 200-provider group or a solo clinician. Practice size does not change the requirement.

A BAA is available for every AI Medical Scribe by Patient Square customer. When you read any vendor's agreement, confirm it does the basics: defines permitted uses of the data, requires safeguards, obligates breach notification, and addresses what happens to data when the relationship ends. If a vendor cannot produce a BAA, the conversation is over. No agreement, no PHI, full stop. The mechanics of what a strong BAA contains are covered in detail in our [BAA and consent guide](../ai-scribe-hipaa-baa-consent/).

## Encryption and access, briefly

Two more technical markers round out a compliant posture, and they are quick to verify.

Encryption should cover data both in transit and at rest. AI Medical Scribe by Patient Square uses TLS 1.2+ for data in transit and AES-256 at rest. In a pipeline where audio is discarded after drafting, "at rest" mainly applies to the notes that survive, which is exactly as it should be. The thing you keep is the thing you protect.

Access should be role-scoped and logged. Not everyone at a vendor should be able to open a practice's notes, and every access should leave an audit trail. You also want to own your data outright: notes belong to the practice, you can export or delete any visit on demand, and the vendor never sells or shares clinical data. Those are the answers a compliant vendor gives without hedging.

## How AI transcription changed the risk math

It is worth saying why this pipeline conversation is different from the one practices had a decade ago.

Old-style medical transcription worked like this: you dictated, the audio file was recorded and sent off (often to an offshore typing service), and a document came back hours or days later. That model has two built-in exposures. It creates a stored audio file, and it puts an extra human in the loop who handles the recording. Both are surfaces where protected health information can slip.

AI transcription that drafts in memory removes both. There is no file sent away, because the audio is processed and discarded in the pipeline. There is no third-party typist, because the draft is generated by the model and reviewed by you. The work that used to take a day and pass through two extra hands now happens during the visit and leaves nothing behind but the note. That is not a small efficiency gain. It is a smaller attack surface. For the broader picture of how this software category works, see our explainer on [ambient clinical documentation](../ambient-clinical-documentation/).

A note of caution that has nothing to do with privacy: the model can still make plausible errors in the draft, so review is not optional. The pipeline protects the audio; you protect the accuracy of the record. Both jobs are real.

{/* deep-link once live */}
If you are specifically weighing dictation-style tools, our comparison of medical dictation software covers that lane and will link here once it is published.

## Questions to ask before you let any tool record a visit

Bring these to the demo, in this order. The answers separate compliant transcription software from marketing language fast.

One: what happens to the visit audio, and when is it deleted? You want a one-sentence answer with a specific moment. "It is processed in memory and discarded when the note is drafted" is an answer. "We retain it for 90 days for quality purposes" is a different answer with different consequences. "We have robust security" is not an answer at all.

Two: is there a Business Associate Agreement, and what does it cover? A vendor handling patient audio must offer one. Read it before procurement, not after.

Three: how is data encrypted, in transit and at rest, and who can access it? Expect TLS 1.2+ in transit, strong encryption at rest, role-scoped access, and audit logs. Vague answers here are a flag.

Four: who owns the notes, and can you export or delete them on demand? The notes are your record. You should be able to take them with you and remove them at will, and the vendor should never sell or share clinical data.

A tool that answers all four in plain, specific sentences is one you can actually evaluate. The AI Medical Scribe by Patient Square, the ambient scribe module inside Practice Copilot, listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. It processes audio in memory and never stores the recording, a BAA is available for every customer, and the full security posture is published on the [security page](../../security/). There is a 7-day free trial, which is enough real clinic time to run your own audio through the pipeline and see what survives.

---

## Abridge Alternatives: A Practical Buying Guide
https://patientsquare.com/us/blog/abridge-alternatives/
Published 2026-04-16 · Updated 2026-08-29 · Tags: ai-scribe, comparison, buying, pricing

Compare an enterprise ambient AI platform with a published-price clinical scribe using contract, workflow, security, and exit questions.

Compare the buying path, total contract, clinical output, review workflow, security terms, implementation work, support, renewal terms, and exit rights. Abridge describes its platform for enterprise healthcare organizations and directs prospective buyers to contact its team. Patient Square publishes per-clinician plans. Those are different buying paths, so compare written terms rather than a third-party price estimate.

Abridge and Patient Square sit on different buying paths. Abridge describes an enterprise ambient AI platform for healthcare organizations and asks prospective buyers to contact its team. Patient Square publishes per-clinician Practice Copilot plans for practices that want an ambient scribe, with Patient Square EHR included from the Copilot tier or an alongside path for an existing EHR.

That does not make either route automatically better. It changes the questions you should ask. A health system may care most about deployment governance and a negotiated agreement. An independent practice may care more about seeing the price, running a short clinical test, and knowing how to leave with its records.

This guide does not use third-party Abridge price estimates or rankings. It gives you a comparison method you can take into both sales conversations.

> **Key takeaways**
>
> - Ask Abridge for a current written quote. Its reviewed public pages do not display a per-clinician list price.
> - Compare the unit, contract term, included modules, implementation, support, taxes, renewal, and exit terms.
> - Patient Square publishes its current per-clinician plans. Check the pricing page before relying on any number here.
> - Patient Square does not promise a named-EHR integration, write-back, or automatic filing.
> - Test both products with the same visit types and the same scoring sheet.

## Start with the buying path

Abridge's current site leads with an enterprise platform and a Contact Us route. That tells a buyer to expect a conversation and a tailored proposal. It does not tell you what your quote will contain.

Get the commercial terms in one document. At minimum, ask for:

| Quote item | Question to put in writing |
|---|---|
| Price unit | Is the fee per clinician, user, encounter, location, or organization? |
| Term | Is the commitment monthly, annual, or multi-year? |
| Modules | Which documentation, coding, revenue-cycle, or other modules are included? |
| Implementation | What work is required from the vendor, the EHR vendor, and your team? |
| Support | Which support hours and response targets are included? |
| Taxes and fees | What can appear beyond the subscription or contract price? |
| Renewal | Does the price change at renewal, and how much notice is required? |
| Exit | How do you export data, and what happens after termination? |

This worksheet is more useful than a market estimate. A number without its unit, scope, and term is not a comparable price.

## Check what the public price includes

Patient Square currently publishes three US tiers. Assist is a $79 per-clinician monthly equivalent on annual billing or $99 month to month. Copilot is $119 on the same annual-billing basis or $149 month to month. Autopilot is $199 on the annual-billing basis or $249 month to month. Each price is per clinician. The [pricing page](/us/pricing/) controls if those figures change.

Do not stop at the headline number. Confirm which tier contains the workflow you intend to test. Ask the same implementation, support, renewal, and exit questions you ask any other vendor.

The clinical output from AI Medical Scribe by Patient Square is a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The prescription is not sent to a pharmacy. The clinician remains responsible for reviewing and approving the note, codes, and prescription draft.

## Be precise about the EHR boundary

Patient Square offers two routes. A practice can use Patient Square EHR from the Copilot tier, or it can keep its existing EHR alongside Patient Square.

The public portability claim is **EHR-ready export (PDF · HL7 · FHIR)**. That phrase describes available export formats. It does not claim automatic filing, bidirectional sync, a named-EHR connector, or guaranteed import into a receiving product. If your workflow depends on a particular destination, test the exact format and fields with that vendor before signing.

Ask Abridge the corresponding question for your proposed deployment: which work happens inside your current system, what has to be configured, who maintains it, and what happens if the EHR or interface changes. Capture the answer in the order form or statement of work.

## Run one fair clinical comparison

Pick representative visits, not polished demo cases. Include a routine follow-up, a medication-heavy encounter, a patient who changes topics, and a visit with the note structure your practice finds hardest.

Use a simple scorecard:

1. Was the history complete and correctly attributed?
2. Did the assessment reflect what the clinician actually concluded?
3. How many material edits were needed?
4. Were suggested diagnoses and prescription details safe after review?
5. How long did final review take?
6. What exact step moved the approved note into the system of record?
7. Could the practice export and delete the test record as promised?

Record corrections, not impressions. A product can sound convincing in a demo and still miss the details that matter in your visits.

## Put privacy answers beside workflow answers

Abridge publishes security material through its Trust Center. Patient Square publishes its security posture and makes a BAA available to US customers. For either vendor, have your privacy or security lead review the actual agreement, not this article.

Ask where audio is processed, whether it is retained, which records persist, who can access them, and how deletion works. Patient Square's current claim is that visit audio is processed in memory and discarded when the note is drafted. Notes are encrypted in transit and at rest, and the practice can export or delete visits. The [security page](/us/security/) has the current details.

## Decide from written evidence

Choose Abridge if its proposal, deployment plan, and enterprise controls fit the requirements your organization has documented. Choose Patient Square if its published scope and clinical test fit your practice, with either the bundled EHR route or an existing EHR kept alongside it.

Do not choose from a ranking, an uncited price, or a promise that uses "integration" without explaining the workflow. A signed quote, a completed security review, and results from your own visits are the evidence that counts.

If you want to test the Patient Square route, Request your 7-day trial. Use the scorecard above and keep the final decision with your clinical, privacy, and operational reviewers.

---

## Cloud EMR vs On-Premise in India: A DPDP-Aware Decision
https://patientsquare.com/in/blog/cloud-emr-vs-on-premise-india/
Published 2026-04-16 · Tags: emr, cloud, on-premise, dpdp, india

Cloud EMR vs on-premise for an India clinic: the real trade-offs on cost, maintenance, uptime, and data control, plus what DPDP data residency actually changes.

For most small and mid-sized clinics, cloud wins on the things that actually go wrong: no server to patch, automatic backups, access from any device, and updates you do not have to schedule. On-premise earns its place when a clinic has a specific data-control requirement, a genuine reason to keep records on-site, and real local IT to maintain the box. The honest test is not cloud versus on-premise in the abstract. It is which one your clinic can actually secure, back up, and recover.

For a clinic deciding between a cloud EMR and an on-premise one in India, the answer is usually cloud, but not for the reason most vendors lead with. The deciding factor is not where the server physically sits. It is who keeps the thing patched, backed up, and recoverable when something breaks. A cloud system hands that job to a vendor whose only business is running it. An on-premise box hands it to whoever in the clinic happens to be free, which is often nobody. India's DPDP Act 2023 doesn't overturn that. It raises the bar for the vendor you pick, and it makes data residency a contract question rather than a server-room one.

What follows is the trade-off laid out plainly: cost, maintenance, uptime, and data control, and then the part everyone gets wrong, what DPDP data residency actually asks of an India clinic.

> **Key takeaways**
>
> - Cloud wins for most clinics on the failures that actually happen: patching, backups, device access, and disaster recovery. On-premise fits clinics with a real data-control need and real local IT.
> - DPDP Act 2023 does not mandate on-premise storage or blanket data localization. Cloud hosting is allowed; the vendor just carries Data Fiduciary obligations.
> - Data residency in India is a contract question, not a geography pitch: where the data sits, who can reach it, and whether you can delete it.
> - The sharpest residency question for any listening tool is the visit audio. A scribe that never stores the recording removes that question entirely.
> - Your EMR and a documentation layer are separate decisions. The cloud-vs-on-prem call is about the records system; the scribe sits alongside whichever you choose.

_Sources: ITIF, June 2025; MeitY DPDP Rules 2025; Indian Medical Council Conduct Regulations 2002._

## The trade-offs, without the sales gloss

Strip out the marketing and the cloud-versus-on-premise decision comes down to four lines: what it costs over time, who maintains it, what happens when the internet or the hardware fails, and who controls the data. Here is how they actually play out in an India clinic.

**Cost.** On-premise looks cheaper because the cost is mostly upfront: a server, a one-time licence, maybe a local install fee. Cloud looks more expensive because it is a recurring per-doctor fee. But the on-premise sticker price hides the parts nobody quotes, the server refresh every few years, the backup drive, the someone who patches it, the downtime when it dies on a Saturday. Cloud folds all of that into the subscription. Over a three to five year window, the gap narrows or flips, and the cloud number is at least predictable.

**Maintenance.** This is where most on-premise deployments quietly fail. Patching, backups, security updates, and recovery testing are real jobs, and in a clinic running on a five-year-old Windows PC they usually fall to no one. A cloud vendor does this as their core function, because their whole business breaks if they don't. If your clinic does not have someone whose actual job is keeping a server healthy, cloud is not just easier. It is safer.

**Uptime.** On-premise keeps working when the internet drops, which is a genuine point in its favour in areas with patchy connectivity. But it goes fully dark when the local hardware fails, and a single clinic almost never has the redundancy a hosted platform does. Cloud needs a working connection, which is a real dependency worth checking against your clinic's reality, and a good one survives a single server dying without you ever noticing.

**Data control.** On-premise feels like more control because the box is in the room. But control is not proximity, it is the ability to secure, back up, recover, and delete on demand. A locked, unpatched, un-backed-up server in a clinic is less in your control than a professionally hosted system with audit logs and exportable data. Real control is about what you can do with the data, not how far away it lives.

## Cloud vs on-premise, side by side

The trade-offs above, in one decision table. Read it against your own clinic, not against a generic "best practice".

The pattern is hard to miss. Cloud takes the operational load off the clinic; on-premise keeps it. The one column where on-premise wins outright is offline operation, which matters in low-connectivity settings and almost nowhere else.

## Where DPDP data residency actually bites

Here is the part vendors muddle. When an India clinic hears "data residency", the pitch is usually a Mumbai data centre and a reassuring map. That answers a question the DPDP Act does not really ask.

The DPDP Act 2023 uses a negative-list model for cross-border transfers. Personal data may move outside India except to destinations the central government specifically restricts, and that restricted list has not been notified yet. So there is no blanket localization mandate for clinical data today. A cloud EMR with servers abroad is not automatically out of bounds, and a Mumbai data centre is not automatically compliant. Geography is the easy thing to demo, not the thing the law turns on.

What DPDP actually demands is closer to home. A cloud vendor holding patient records is a Data Fiduciary, which means consent, purpose limitation, security safeguards, and deletion on request. Purpose limitation is the sharp one: data should be used only for what the patient consented to, then erased when that purpose ends. That is a "use it for what you said, then delete it" rule, and it has nothing to do with where the server sits.

For a clinic choosing cloud over on-premise, that translates into four contract questions worth more than any data-centre map. Where are the data centres, and is the data stored in India, which sidesteps the cross-border questions cleanly even though it is not strictly required. What happens to patient deletion requests if you stop being a customer. What the breach-notification process looks like. And, if the product listens to consultations, where the visit audio goes and whether it is stored at all. We go deeper on the residency-versus-localization distinction in our [India data residency explainer](../ai-scribe-data-residency-india/); the short version is that what the vendor stores and whether you can delete it matters more than the pin on the map.

That last question, about audio, is worth dwelling on. For any tool that records a consultation, the recording is the most sensitive artifact in the whole system, and it is the one most likely to be quietly retained on a server somewhere. The cleanest answer under DPDP is not a well-guarded archive. It is no archive. A tool that processes audio in memory and discards it the moment the note drafts removes the residency question for that artifact entirely, because there is nothing left to reside anywhere.

## When on-premise still makes sense

Cloud is the default recommendation for most clinics, but not all. On-premise is the right call in a few specific situations, and it is worth being honest about them.

If the clinic has a genuine reason to keep records strictly on-site, a contractual data-control requirement, an institutional policy, a setting where that is non-negotiable, on-premise meets that need directly. If the clinic runs in an area where the internet is unreliable enough that browser-based access would stall care, the offline operation of a local system is a real advantage rather than a theoretical one. And if the clinic already has competent local IT, someone who actually patches, backs up, and tests recovery, then the maintenance argument against on-premise weakens considerably.

The trap is choosing on-premise for the feeling of control while having none of the infrastructure to back it up. A local server that nobody patches and nobody backs up is not data sovereignty. It is a single point of failure with a clinic's entire record history on it. If you are going on-premise, go in with the IT to run it properly, or the choice works against you.

## The decision in one pass

Most clinics can settle this in three questions, without a month of vendor demos.

Does someone in the clinic actually own server health, patching, backups, and recovery? If not, cloud is both easier and safer, and the maintenance argument decides it on its own. Is the internet reliable enough that browser-based access won't stall a consult on a bad day? If yes, the main point in on-premise's favour drops away. And can the vendor answer the four residency questions, data-centre location, deletion-on-exit, breach process, and audio handling, in one clear sentence each? Vague answers tell you more than any compliance badge.

One thing to keep separate while you decide: your EMR and your documentation layer are different choices. The cloud-versus-on-premise call is about the records system. It does not settle the question of getting the note written in a two-minute OPD, which is a different gap with a different fix. For the wider buyer's decision on EMR type, ABDM milestones, and honest pricing, our [India EMR buyer's guide](../emr-software-india-guide/) covers the full shortlist.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It sits alongside whatever EMR you choose, cloud or on-premise. Visit audio is processed in memory and discarded the moment the note drafts, with no recording archived anywhere, which is the cleaner answer under DPDP Act 2023. The platform is handled to DPDP Act 2023 standards, consent-first and purpose-limited, and the full technical detail on how patient data is stored, accessed, and deleted lives on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If your clinic is weighing where patient data should live, sort the records system out with the three questions above, then <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a real consult turn into a signed note. Or read through [pricing](../../pricing/) first. Either way, fix the layer that's actually broken.

---

## Best AI Medical Scribes in 2026: An Honest Comparison
https://patientsquare.com/us/blog/best-ai-medical-scribes/
Published 2026-04-15 · Updated 2026-08-29 · Tags: comparison, ai-scribe, buying

A fair, situation-by-situation comparison of the leading AI medical scribes (Freed, Abridge, Suki, Heidi, Twofold), including where each one beats us.

There isn't one best. There's a best for your situation. Freed and Heidi suit low-volume or budget clinicians; Abridge, Suki, and DeepScribe fit large EHR-integrated health systems; Twofold bundles coding; AI Medical Scribe by Patient Square fits prescription-heavy primary care that wants an Rx draft you review and sign. Match the tool to the clinic.

There is no best AI medical scribe in 2026. There's a best for your clinic. A low-volume solo practice wants something different from a large EHR-integrated health system, and a prescription-heavy primary care clinic wants something different again. What follows is a fair read on the leading scribes, sorted by which clinic each one actually fits, including the cases where a competitor beats us.

> **Key takeaways**
>
> - Two in three US physicians used health AI in 2024, and documentation is the number-one use case (AMA).
> - On a tight budget or low volume? Freed Starter and Heidi's free tier are genuinely the cheapest credible choices.
> - Large health systems wanting deep EHR integration should be talking to the sales-led vendors: Abridge, Suki, DeepScribe.
> - Prescription-heavy primary care is where we fit: an Rx draft you review and sign, plus ICD-10 suggestions you confirm.

## How we picked, and why we'll name our own gaps

Most "best AI scribe" lists are written by a vendor that conveniently ranks itself first. This one is too. So here's the deal: we'll tell you exactly where each competitor wins, us included. Call it self-interest if you like. A roundup nobody can trust is a roundup nobody cites. AI Medical Scribe by Patient Square is one module of Practice Copilot: it captures the visit and returns a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review about two minutes after the visit. A practice can keep its existing EHR and use Practice Copilot alongside it, or use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back to a third-party EHR. Every plan includes EHR-ready export (PDF · HL7 · FHIR). Test the requirements that matter to your clinic before you buy.

Adoption is no longer the question. A 2025 AMA survey found two in three US physicians used health AI in 2024, up 78% in a single year, with documentation the leading use case. Fit is.

If this shortlist has narrowed your choices, request your 7-day trial with Practice Copilot and run the same difficult visit through the finalists before you commit.

And the field is crowded, which is the real reason "best" is the wrong question. The Peterson Health Technology Institute counted roughly 60 ambient AI scribe products being rolled out across healthcare in its March 2025 review, and called the pace of adoption one of the fastest in recent healthcare history. It also found that once a scribe is widely available inside an organization, uptake typically lands between 20% and 50% of eligible clinicians, with the outliers hitting 75% to 80% only where the rollout paired hands-on training with note customization. Sixty products and adoption that swings that widely tell you the same thing: the differentiator isn't a leaderboard, it's how well a specific tool fits a specific clinic and how it's introduced. So the list below sorts by fit, not by rank.

## Best AI scribe by situation

| Your situation | Best fit | Why |
|---|---|---|
| Low volume / tight budget | **Freed Starter** or **Heidi free tier** | ~$39/mo annual (40-note cap) or genuinely free with limited actions, so you don't pay for unlimited you won't use |
| Coding included, no EHR push needed | **Twofold** | CPT + ICD coding bundled into the $49–69 Personal plan |
| Large health system, deep EHR integration | **Abridge / Suki / DeepScribe class** | Enterprise integration depth and EHR partnerships; expect sales-led pricing |
| Prescription-heavy primary care | **AI Medical Scribe by Patient Square** | Rx draft that mirrors the visit; you review, screen, and sign it |
| Transparent published pricing | **Freed / Commure / Twofold / us** | All publish real numbers you can compare before a call |

## The leading AI scribes, honestly

**Freed** is the self-serve benchmark. It publishes clear pricing ($39–119 across tiers and billing), runs a 7-day no-card trial, and has a large clinician base. Where it beats us: the specialty-template catalogue is broad, and for a low-volume clinician the $39 Starter tier undercuts almost everyone. The catch is that ICD-10 coding and EHR push sit behind the Premier tier, so if those matter to you, price the plan you'd actually buy, not the headline $39.

**Abridge, Suki, and DeepScribe** are the enterprise tier. Deep EHR integrations, large health-system deployments, mature workflows. None publishes self-serve pricing, so you'll get a quote, not a list price. They beat us cleanly on one thing: if you're a hospital that needs the scribe wired into Epic or Oracle Health with an enterprise contract and dedicated support, that's their home turf, not ours. The solo clinician or two-doctor clinic who wants a published price and a short assisted trial is not who they are built for.

**Heidi Health** offers a genuinely useful free tier (unlimited transcription, limited actions) and a Pro plan around $99 by its own blog. The free tier is real, and it's generous for a clinician testing the water. That's the edge over us. Coding and EHR integration move you up to the paid and enterprise tiers.

**Commure Scribe and Twofold** round out the transparent self-serve field. Commure runs $59–89 (write-back and coding in custom group tiers), and Twofold runs $49–69 with coding included. Both are credible; Twofold's bundled coding is a real edge if that's your priority.

**Doximity** is a different buying case because its scribe sits inside a clinician network rather than a standalone shortlist. The [Doximity Scribe review](../doximity-scribe-review/) owns that product-specific decision, including eligibility, workflow, privacy questions, and what to verify before treating access as a reason to switch.

## Where AI Medical Scribe by Patient Square fits

Prescription-heavy primary care, specifically. Picture a clinic running a steady stream of polypharmacy follow-ups, where an Rx draft that mirrors the visit and saves the typing is worth more than another specialty template. The draft stays a draft. You screen it for interactions and dosing and sign it, the same review you run on every prescription. The note, ICD-10 suggestions, and the Rx draft all land about two minutes after the visit, and you stay the author of every one.

Our pricing is public: Assist starts at $79 per clinician a month on annual billing. Copilot is $119 per clinician a month on annual billing and includes Patient Square EHR and WhatsApp messaging. Autopilot is $199 per clinician a month on annual billing and adds AI Receptionist, AI Follow-ups, priority support, and adoption and ROI analytics. The full ladder is on the [pricing page](../../pricing/), and our security posture, including the audio-never-stored design, is on the [security page](../../security/).

## A one-week scorecard beats a leaderboard

Use the same ten real visits for every finalist. CMS says a record should be complete and legible, identify the encounter, assessment, plan, date, and author, and support the codes reported on the claim ([CMS E/M guidance](https://www.cms.gov/training-education/medicare-learning-networkr-mln/compliance/medicare-provider-compliance-tips/evaluation-management-services)). That gives you a better test than counting features.

| Test | Weight | What passes | What goes in the failure log |
|---|---:|---|---|
| Missing or invented facts | 30 | No unsupported problem, medication, finding, or plan survives review | Record the exact sentence and visit type |
| Editing burden | 20 | The clinician can sign after a short, predictable review | Minutes to sign and the section that needed repair |
| Note completeness | 15 | Reason, relevant findings, assessment, and plan are easy to find | Any clinically important omission |
| Workflow handoff | 15 | The reviewed note reaches the chart in a repeatable way | Copy, export, or write-back step that failed |
| Consent and privacy | 10 | Staff can explain capture and honor a patient's refusal | Refusal, pause, or deletion path that wasn't clear |
| Price at real volume | 10 | The rate, limits, add-ons, and renewal term are written down | Any cost you learned only after the trial |

Score each tool out of 100, but keep the failure log beside the number. A single invented medication matters more than a polished template. We think a finalist that needs a clinician to rediscover the same error three times is out, even if its average score looks fine.

## How to actually choose

Stop comparing feature grids. Run two or three tools on the same week of real visits. Bring your messiest case, the polypharmacy follow-up or the noisy room with a caregiver answering half the questions, and read every draft closely. The honest comparison isn't on anyone's marketing page. It's in your own clinic on a Tuesday.

If you're early in the decision, the [clinic software category map](../medical-scribe-software-for-clinics/) explains the handoff choices, while the [current pricing comparison](../ai-medical-scribe-pricing/) normalizes the public rates. Then run the same one-week test through the 7-day free trial and let your own failure log pick the winner.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot supports documentation and shipped practice workflows. A new practice can instead use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## Freed AI Alternatives: When You Want More Than a Note
https://patientsquare.com/us/blog/freed-ai-alternatives/
Published 2026-04-14 · Updated 2026-07-14 · Tags: ai-scribe, freed, alternatives, ehr

Freed AI drafts notes for solo clinicians. Patient Square adds a bundled EHR and front-office automation at a published price from $79/mo. Honest comparison.

Solo-clinician documentation. Freed is a well-established ambient scribe built around the individual doctor: it listens, drafts a note, and you paste it into whatever chart you use. It has a large clinician base and a low entry price. If you want a note drafter and nothing more, Freed is a strong, proven pick.

If you're weighing Freed AI alternatives, start by naming what you actually want. Freed is a solid, proven ambient scribe for solo clinicians: it listens, drafts the note, and you paste it into your chart. If a note drafter is the whole job, Freed is a good tool and you may not need to switch. Patient Square is the alternative for people who want more than a note. It's a scribe too, but the Copilot plan bundles a real EHR and front-office automation, so the note lands in a chart and the front desk runs itself a little. Pricing is published: from $79/mo for the scribe, with the EHR bundled from $119/mo on annual billing. See the whole ladder on our [pricing page](../../pricing/).

We make one of the alternatives here, so read this the way you'd read any vendor's comparison, with the sources open. Where Freed is the better fit, and for many clinicians it clearly is, there's a section that says so by name.

> **Key takeaways**
>
> - Freed is a focused ambient scribe for solo clinicians: low entry price, large user base, EHR-agnostic. It ends at the note.
> - Patient Square is a scribe plus a bundled EHR (AI Copilot EHR) plus front-office automation, so the note has somewhere to go.
> - Patient Square US pricing: Assist $99/mo ($79 annual, no EHR), Copilot $149/mo ($119 annual, EHR bundled), Autopilot $249/mo ($199 annual).
> - The trade is scope, not note quality. If the note is your only pain, Freed wins. If your front office and chart are also a mess, the bundle earns its price.

## What Freed AI is good at

Credit where it's due. Freed is one of the established names in ambient scribing, and it earned that the boring way: a note drafter that works, priced low enough for a solo clinician to say yes without a meeting. It listens during the visit, hands back a structured note, and doesn't ask you to change the EHR you already run. Its published pricing and no-card trial mean a doctor can test it this afternoon.

That's a real product with a clear audience. A solo physician drowning in after-hours charting can pick Freed up and feel lighter the same week. Nothing below is a takedown.

The question is scope. Freed is built to solve one problem: the note. If that's your only pain, it's a fine answer. If your front desk is also underwater and your EHR fights you daily, a scribe alone leaves most of the mess untouched. That's where a wider tool comes in. Book a demo and see the note quality against your own visits before you decide.

## Where Patient Square is different

Here's the honest split. Freed ends at the note. Patient Square keeps going.

Patient Square is an ambient AI clinical platform, live now, built around Practice Copilot. The scribe layer does what Freed's does: it listens during the visit and drafts a structured SOAP note with ICD-10 suggestions and a prescription draft you review and sign. But the Copilot plan bundles AI Copilot EHR, a real electronic health record, so the note isn't something you paste anywhere. It's already in the chart. On the same plan, the front office gets automated: intake, scheduling, and the follow-up busywork a scribe never touches.

One line: a scribe hands you a note and a clipboard. Patient Square hands you a note, a chart it lives in, and a front desk that runs a little on its own.

If you already love your EHR and won't leave it, that bundle is more than you need, and we say so below. But if you went looking for a scribe *because* the whole workflow is broken, the wider tool is the point. Book a demo and check whether the EHR and front-office pieces solve problems you actually have.

## What Patient Square costs

We publish the price. No call required to learn what you'll pay.

Three US tiers, per clinician:

| Tier | Monthly | Annual (per mo) | What you get |
|---|---|---|---|
| Assist | $99 | $79 | Documentation essentials, no EHR |
| Copilot | $149 | $119 | Scribe plus AI Copilot EHR bundled, front-office automation |
| Autopilot | $249 | $199 | Everything, deepest automation |

The scribe starts from $79 a month on annual billing. The bundled EHR starts from $119 a month on annual billing, which is the Copilot tier. A 7-day free trial runs on the scribe, so you test note quality on a real clinic week before committing.

Be honest about the money: for a solo clinician who only wants documentation, Freed's entry tier can come in under our Assist price, and we won't pretend otherwise. The comparison isn't scribe-versus-scribe on price. It's whether you'd otherwise be paying for a scribe *and* a separate EHR *and* separate front-office tools. Add those up, and one bundled Copilot subscription at $119 a month starts to look like the cheaper stack, not the pricier one. The full ladder with no asterisks sits on the [pricing page](../../pricing/).

## What happens to your visit audio when you switch

Ask this of every vendor before you ask about anything else. Freed's own compliance FAQ says visit audio is temporarily saved, then automatically deleted once the note generates, per its published wording as of July 2026. Notes are separate: they persist until you delete them or turn on an optional auto-delete. Confirm the current terms yourself before you sign, because policies change.

Patient Square's approach: visit audio is processed in memory and discarded the moment the note drafts, so there's no recording retained. What survives is the note you reviewed and signed. The full posture, encryption, access, and audit status, lives on our [security page](../../security/). Whichever tool you pick, get the audio answer in one sentence with a timeline.

## When Freed is the better choice

There's a clean case for staying with Freed, and it deserves to be said plainly.

Choose Freed if the note is the entire job. If you're a solo clinician happy with your current EHR, with a front desk that runs fine, and you just want charting off your plate, a focused scribe is the right tool and Freed is a proven one. Its low entry price and large user base are real advantages. Buying a bundled EHR and front-office automation you'll leave idle is spending on features you won't touch.

Choose Patient Square if the note is only part of the problem. If your charting *and* your front office both eat hours, and you'd rather buy one tool than wire a scribe to a separate EHR and a separate scheduling system, the bundle earns its price.

The split is scope, not quality. Both draft good notes. Freed assumes the rest of your stack is sorted. We assume it might not be.

If your shortlist is wider, [Heidi Health alternatives](../heidi-health-alternatives/) covers another EHR-agnostic scribe, and [Suki alternatives](../suki-ai-alternatives/) looks at the voice-assistant angle.

## How to decide in a week

Skip the spec sheet and run the real test:

1. Name your actual problem. Just charting? A scribe alone fits, and Freed is easy to try. Charting plus front-office chaos plus an EHR you hate? Weigh the bundle.
2. Count the separate bills. If a Freed-style scribe means also paying for an EHR and scheduling tools, add those in before you compare on price.
3. Trial on real visits. Run Patient Square's 7-day scribe trial across your busiest clinic days and judge note quality against your own edits.
4. Settle the audio question with every vendor: stored or not, and for how long.
5. Check EHR fit. Keeping your chart? Confirm the scribe drops in cleanly. Fed up with your chart? Look hard at the bundled EHR on the demo.

The price ladder with no fine print is on the [pricing page](../../pricing/). Book a short demo to see the note against your own visit type, then run the trial on a real week. If a note drafter is the whole job, keep Freed. If the note is only part of the mess, the bundle is what you're actually shopping for.

---

## What Happens to Visit Audio? AI Medical Scribe Retention Compared
https://patientsquare.com/us/blog/ai-scribe-audio-retention/
Published 2026-04-13 · Tags: ai-scribe, audio-retention, privacy

Eight AI scribe vendors’ audio-retention policies, quoted and access-dated: who deletes recordings, who keeps them 30 days, and what to ask.

Some do, some don’t, and the difference is large. Published policies range from never stored (Doximity, Patient Square) to deleted at note generation (Freed, Jane by default) to 30-day windows (Suki) to clinic-configurable indefinite retention (Jane). Always read the vendor’s own retention page, not their homepage.

Does an AI scribe store recordings of your patients? It depends entirely on the vendor. Published policies run the full spectrum: never stored, deleted at note generation, kept 30 days, or kept indefinitely on a setting your front desk might not know exists. Below is each major vendor's policy, quoted from their own pages, with the date we checked.

Nobody else publishes this table. Vendors describe their own policy (sometimes carefully, sometimes not) and stay quiet about everyone else's. So we fetched the pages ourselves.

> **Key takeaways**
>
> - Of 8 vendors we checked on June 12, 2026: 4 say audio is never stored or deleted at note generation, 1 keeps audio 30 days, 1 lets clinics keep it indefinitely, and 1 publishes no number at all.
> - Audio and transcripts are separate artifacts. Two vendors that don't store audio keep transcripts for 2 years, or forever by default.
> - Two policies hinge on the word "successful." Ask every vendor what happens to audio when note generation fails.
> - Deleting audio fast does not remove the consent requirement; it still applies in every US state.

## Does your AI scribe store recordings? Eight vendors, quoted

Every quote below comes from the vendor's own public page, fetched on June 12, 2026. Policies change, which is why each row carries its source. Check the link before you rely on the row.

| Vendor | What their public docs say about audio | Retention window | Source (fetched June 12, 2026) |
|---|---|---|---|
| Abridge | Privacy policy sets no window for clinical audio. Visit content is "Customer Data," governed by the health system's own agreement. Deployments publish their own rules: UChicago Medicine says recordings are "never kept for more than one week," deleted "often on the same day." | Set by your health system, not published by the vendor | [Abridge privacy policy](https://www.abridge.com/privacy); [UChicago Medicine](https://www.uchicagomedicine.org/forefront/patient-care-articles/2025/january/ai-ambient-clinical-documentation-what-to-know) |
| AI Medical Scribe by Patient Square | Audio is processed in memory and discarded once the note is drafted. There is no audio archive, not for us, not for the practice, not for anyone. Notes are encrypted, owned by the practice, exportable and deletable anytime. | None; no recording survives the note draft | [Security page](../../security/) |
| Doximity Scribe | "We do not store or retain any audio. Recordings are processed securely in real time and immediately discarded once the note is generated." | None claimed | [Doximity Scribe announcement](https://blog.doximity.com/articles/meet-doximity-scribe) |
| Freed | "Once the note is successfully generated, the audio recording is automatically deleted," within 60 seconds of the encounter ending, per their FAQ. "Freed does not retain audio by default." Notes: delete manually anytime, or enable a 30-day auto-delete policy. | Deleted on successful note generation; notes persist until deleted | [Freed HIPAA FAQ](https://www.getfreed.ai/resources/hipaa-compliance-in-ai-scribes) |
| Healthie | "Raw audio is not stored by Healthie… audio is processed and discarded." But: "Transcripts are stored for 2 years from the date of the appointment," then auto-deleted. | Audio: none. Transcripts: 2 years | [Healthie AI Medical Scribe FAQs](https://help.gethealthie.com/article/1272-faqs-healthie-ai-scribe) |
| Heidi | "No, Heidi does not store audio recordings of patient consultations." Transcript retention is customizable from 1 day to "never delete," and "by default, accounts are set to 'never delete.'" | Audio: none. Transcripts: indefinite unless you change the setting | [Heidi compliance FAQs](https://www.heidihealth.com/en-us/blog/heidi-compliance-lightning-faqs) |
| Jane | A clinic-wide Recording Deletion Policy with three options: keep "indefinitely," delete "immediately after successfully generating a chart entry," or delete after a set number of days. Default for new users: delete immediately after successful generation. Deleted files persist on secure backups about a week. | Configurable: immediate to indefinite (default: at note generation) | [Jane recordings guide](https://jane.app/guide/ai-scribe-working-with-recordings) |
| Suki | "The original audio recording is permanently deleted after 30 days." The transcript is also deleted at 30 days; the final note is retained for the duration of the service contract. | Audio and transcript: 30 days | [Suki security FAQ](https://developer.suki.ai/documentation/faqs/security) |

Four patterns hide in that table, and they're worth naming.

Start with never-stored versus deleted-after. "We don't store audio" (Doximity, Patient Square) and "we delete audio after the note generates" (Freed, Jane's default) sound identical and aren't. In the first model there's no stored artifact at any point, because audio is processed in memory and gone. In the second, a recording exists as a file until a pipeline step succeeds. Usually a distinction without much practical difference. Until the pipeline has a bad day.

Then watch the word "successfully," which is doing quiet work. Freed deletes audio "upon successful note generation." Jane's default deletes "immediately after successfully generating a chart entry." Neither page says what happens to the recording when generation fails. Maybe nothing interesting. But a policy that only describes the happy path has only answered half the question. Ask the other half.

Third, transcripts outlive audio. Healthie discards audio and keeps transcripts for 2 years. Heidi doesn't store audio and defaults to keeping transcripts forever. A transcript is the same conversation in a different format. If your privacy question was "does a record of everything said in my exam room persist," the audio answer alone hasn't answered it.

Last, enterprise vendors delegate the answer. Abridge publishes no retention number; the health system deploying it sets one. A defensible model for a hospital with an information-governance office. If you're a 3-physician practice, it means the policy is whatever your contract says, so read the contract, not the website.

One honest concession: stored audio is sometimes what you want. Jane's configurable retention is the better fit if your clinic deliberately keeps recordings. Some practitioners re-listen while finalizing charts, and Jane lets a Full Access user set the window the clinic actually intends. Heidi's never-delete transcript default is the better fit if you want a permanent searchable record of every consultation beyond the note. Those are legitimate choices. Our argument is only that they should be choices someone made on purpose, not defaults nobody read.

If you'd rather the answer be "there is nothing to configure because nothing is kept," that's our model. Read the [security page](../../security/), then use the [pricing page](../../pricing/) to plan a trial that tests the failure path.

## Why is visit audio more sensitive than the note?

The note is a summary you reviewed and signed. The audio is everything else.

A recording of a 20-minute visit contains the depression screen the patient answered honestly, the "while I'm here" question about an STI, the daughter in the room arguing about her father's drinking, your own thinking out loud before you settled on an assessment. The note you signed contains none of that phrasing. The recording contains all of it, verbatim, in the patient's own voice.

That asymmetry has teeth:

- It's a second record you didn't author. You control what enters the chart. You don't control what a microphone heard. If a stored recording and your signed note ever diverge, you'll be asked about the gap.
- It's a bigger breach surface. A leaked note is a clinical summary. A leaked recording is a patient's voice describing their lowest moment. Same incident-response process, very different patient harm.
- It can be requested. Anything retained can, in principle, be sought in a dispute by either side. Penn Medicine's patient FAQ is blunt about who controls this: recordings are kept (de-identified) "for a short time," and patients cannot request that previous recordings be deleted. Even careful health systems end up with retention rules the person in the room can't override.

None of this means stored audio is reckless. It means audio deserves its own line of questioning, separate from "is the note secure," and most vendor security pages answer the second question while hoping it covers the first.

## What should you ask a vendor before the first recorded visit?

Six questions. A good vendor answers each in one sentence, in writing.

1. Where does audio live during processing? In memory, or written to disk and queued? Either can be done securely; you want to know which it is.
2. What exactly triggers deletion, and what's the window? "When the note generates" and "within 30 days" are both real answers. "We take privacy seriously" is not.
3. What happens to audio when note generation fails? The happy-path question every published policy answers; this is the one some don't. Our answer: there is no audio archive for a failed draft to land in, full stop.
4. How long do transcripts persist, separately from audio? You now know why. Ask about each artifact by name: audio, transcript, note.
5. Do backups keep copies after deletion? Jane discloses about a week on secure backups, and that's the honest shape of a real answer. A vendor who says "deleted means deleted, instantly, everywhere" either built something unusual or hasn't checked.
6. Who in my clinic can change the retention setting? Jane's policy is clinic-wide and editable by any Full Access user. That's fine, if you know it. A privacy posture that one staff account can quietly flip is a process risk, not just a setting.

Vendors who handle these six without flinching will probably also survive the [evaluation questions that go beyond audio](../what-is-an-ai-medical-scribe/).

## What does US law actually require before you record?

Two separate obligations, often blurred together. This is orientation, not legal advice, so confirm specifics with your counsel or malpractice carrier.

Start with HIPAA. Visit audio is PHI the moment it's captured. Any vendor processing it for you must sign a business associate agreement. No BAA, no deal, even if the audio is deleted in seconds. Patient Square signs a BAA for every customer, on every plan, including the trial week. Ask any vendor whether BAA coverage extends to the subprocessors that touch audio (speech-to-text APIs included), and at which pricing tier the BAA actually becomes available.

The consent side is separate. State law governs recording a conversation, and it doesn't care how briefly the file existed. Most states require one party's consent; roughly a dozen (California, Florida, Illinois, Pennsylvania, and Washington among them) expect every party in the room to consent. Fast deletion makes the disclosure easier to say; it does not make the disclosure optional. The line that works in practice is one sentence: "I use a tool that listens and drafts my note so I can pay attention to you, and the audio is deleted once the note is written. OK?" When retention is genuinely zero, that sentence has the advantage of being true.

## Where does AI Medical Scribe by Patient Square sit on this table?

In the row with the least to say. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The audio that produced the note is processed in memory and discarded once the note is drafted. No archive, no configurable window, no retention setting a staff account can flip. The [security page](../../security/) states the full posture: TLS 1.2+ in transit, AES-256 at rest, role-scoped and logged access, BAAs for every customer, SOC 2 Type II audit underway.

We think zero retention is the right default for a tool that sits in an exam room, and we're saying that as the vendor whose table row it is. Weigh it accordingly, then check our claim the same way you check everyone else's: read the page, ask the questions, and make us answer the failure-path one.

What does persist is yours. Notes belong to the practice; export or delete any visit, anytime; we never sell or share clinical data. If a vendor's retention answer ever stops satisfying you, your exit shouldn't be held hostage by your own charts.

The fastest way to assess this is with a controlled evaluation. Bring this post's six questions into a review of the [product workflow](/us/products/practice-copilot/) and verify where the audio goes. (Nowhere. That's the point.) For how retention fits into the wider buying decision, the [honest comparison of the leading scribes](../best-ai-medical-scribes/) is the next read.

*7-day free trial · month-to-month available · audio never stored.*

---

## AI Medical Scribe Pricing: What You'll Pay in 2026
https://patientsquare.com/us/blog/ai-medical-scribe-pricing/
Published 2026-04-10 · Updated 2026-08-29 · Tags: pricing, ai-scribe, buying

A dated AI medical scribe price table, cost-per-reviewed-note worksheet, and renewal questions for US clinics comparing 2026 plans.

Current public options span free access for eligible verified Doximity clinicians, capped or paid self-serve tiers, and custom enterprise quotes. Freed lists $39 to $104 monthly equivalents on annual billing, Sunoh lists a limited-time $149 rate, and Patient Square starts at $79 per clinician per month annually. Recheck the dated rate card before signing.

AI medical scribe pricing ranges from free access for eligible clinicians to public per-clinician subscriptions and custom enterprise quotes. The real comparison is dated price plus volume limit, required tier, EHR handoff, contract, and renewal. The rate card below was rechecked on August 11, 2026. It separates verified public numbers from unavailable ones instead of turning old screenshots into facts.

> **Key takeaways**
>
> - Doximity is free for eligible verified US clinicians. Freed's annual equivalents run $39, $59, and $104 by tier. Sunoh shows $149 as a limited-time rate.
> - A public price is not enough. Record caps, coding, EHR handoff, implementation, contract, and renewal beside it.
> - Cost per note uses your completed reviewed-note count. Don't treat a busy-clinic example as a guaranteed return.
> - Patient Square's annual plans are about 20% below month to month; prove workflow fit before taking the term discount.

## What do AI medical scribes actually cost in 2026?

These are the public US numbers we could verify from first-party pages on August 11, 2026. A promotion is labelled as a promotion. An inaccessible or ambiguous price stays out.

| Vendor | Current public price | Annualized amount | Limit or tier fact that changes the comparison | Verification |
|---|---:|---:|---|---|
| **Doximity Scribe** | $0 for eligible verified US physicians, NPs, PAs, CRNAs, and listed students | $0 | Requires a verified account; notes and transcripts are available for 29 days; vendor says review every note | Doximity Help Center, rechecked Aug 11 |
| **Freed Starter** | $59 monthly or $39 monthly equivalent annually | $468 on annual billing | 40 notes per month | Freed pricing, rechecked Aug 11 |
| **Freed Core** | $79 monthly or $59 monthly equivalent annually | $708 on annual billing | Unlimited note generation | Freed pricing, rechecked Aug 11 |
| **Freed Premier** | $119 monthly or $104 monthly equivalent annually | $1,248 on annual billing | Adds EHR push and ICD-10/CPT coding | Freed pricing, rechecked Aug 11 |
| **Twofold Personal** | $69 list price; page also shows a limited first-month promotion | Use the written renewal quote, not the promotion, before annualizing | Page names unlimited notes, templates, and CPT/ICD coding; group price is custom | Twofold first-party page, rechecked Aug 11 |
| **Sunoh** | $149 per user per month, labelled limited time; $199 crossed out | $1,788 if the $149 rate lasts 12 months | Ask when the promotion ends and what renewal costs | Sunoh pricing, rechecked Aug 11 |
| **Patient Square Assist** | $99 monthly or $79 monthly equivalent annually | $948 on annual billing | Unlimited visits and notes; documentation tier | Live Patient Square pricing, rechecked Aug 11 |
| **Patient Square Copilot** | $149 monthly or $119 monthly equivalent annually | $1,428 on annual billing | Adds bundled AI Copilot EHR and WhatsApp messaging | Live Patient Square pricing, rechecked Aug 11 |
| **Patient Square Autopilot** | $249 monthly or $199 monthly equivalent annually | $2,388 on annual billing | Adds named receptionist, follow-up, support, and analytics modules | Live Patient Square pricing, rechecked Aug 11 |

This isn't the whole market. It is a dated, reproducible set of public rates. Quote-only products belong in the same table only after you have a written quote with term, seats, implementation, limits, add-ons, and renewal.

Patient Square publishes both billing paths in the table. If the Assist scope fits your work, Request your 7-day trial before choosing the annual commitment. Review the same real visits you would use to compare any other finalist.

## Why is the cheapest tier rarely the real price?

Because the cheap tier may have a volume, eligibility, term, or feature condition. Freed Starter is $39 a month on annual billing but caps use at 40 notes per month. Doximity is free only for the eligible roles it lists and requires a verified account. A limited-time promotion may renew at another number. The price that matters is the one for your role, completed-note volume, required handoff, and contract.

The second condition is scope. Freed's page places EHR push and ICD-10/CPT coding in Premier. Patient Square includes ICD-10 suggestions and EHR-ready export (PDF · HL7 · FHIR) on every plan, while the bundled AI Copilot EHR begins on Copilot. Export isn't native write-back into every EHR. Two products with the same headline can therefore buy different handoffs.

Twofold's current page names CPT and ICD coding in Personal but also shows a first-month promotion. Ask for the post-promotion and renewal price in writing before calling it cheaper. Doximity's free tier may be the honest better fit for an eligible clinician who only needs a portable note. We'd rather say that plainly than make a paid tier win every row.

## What should you do with a quote-only price?

Don't call it hidden and stop there. A custom quote can price integration, implementation, governance, support, and scale that self-serve software does not include. The mistake is comparing that quote with a monthly sticker before normalizing scope.

Ask for a line-item quote with billable unit, clinician count, usage limit, required tier, interfaces, implementation, training, support, contract length, renewal rule, overage, seat reduction, cancellation, export, and taxes. Annualize it. Then compare it with the same rows for public plans. Our opinion: a blank renewal rule is a bigger warning than a missing website price.

## What does an AI scribe cost per completed reviewed note?

Use completed, reviewed notes as the denominator, not booked visits. As a worked example only, take a clinician who finishes 440 reviewed notes in a month. At the $79 annual Assist rate:

**$79 ÷ 440 completed reviewed notes ≈ $0.18 per note.**

At that volume, the subscription works out to about 18 cents per completed note on annual Assist or 23 cents month to month. Patient Square's output is a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The arithmetic says nothing about note quality, review time, consent, or EHR handoff. Those are separate trial measures.

Now run your own denominator. A therapist with 80 reviewed notes and an urgent-care clinician with 500 have different unit costs. Add any mandatory implementation, interface, support, or add-on amount before dividing. A free product also has a workflow cost if its handoff or corrections consume staff time.

One more honest caveat, because it changes how you should read every ROI pitch in this category, ours included. When the Peterson Health Technology Institute reviewed early scribe deployments in March 2025, it reported that health systems had not yet established a clear financial impact on measures such as visit capacity or billing-code accuracy. The independent case for a universal dollars-in, dollars-out return is still thin. That is an argument for a published price you can reason about, not against it. If the returns are not established, the last thing you want is a subscription whose cost you cannot see until a sales call and a renewal number you learn later. A number on the page lets you size the bet honestly.

## What changes your bill after year one?

Four things, and you should get all four in writing during the trial:

1. The month-to-month versus annual gap. Ask what the price becomes at renewal and what the annual commitment saves. Patient Square publishes both: $79 versus $99 for Assist, $119 versus $149 for Copilot, and $199 versus $249 for Autopilot.
2. Per-seat creep in a group. A solo price times ten is not a group price, and a "custom" group quote can drift up at renewal if it was never anchored. Get the per-seat number and the renewal terms together.
3. Feature upsell once you're dependent. The cheap tier that gets you hooked may not include the coding or integration you'll want by month three. Price the tier you'll actually live on, not the one in the ad.
4. Promotion expiry. A crossed-out rate or first-month offer needs a written start date, end date, renewal rate, and eligibility rule.

## Which AI scribe is the best value?

It depends on your volume and what you need the note to do. For some clinicians, the honest answer is not us:

- Eligible clinician who needs a portable note at $0: Doximity may be the better narrow fit. Verify its role eligibility, 29-day note retention, and copy-to-EHR workflow.
- Low volume with predictable limits: Freed Starter is $39 monthly equivalent on annual billing with a 40-note cap.
- Coding-first: Twofold names CPT and ICD coding in Personal, but confirm the post-promotion and renewal price before comparing.
- Busy primary care or specialty, wants codes plus an Rx draft: every plan includes ICD-10 suggestions and a prescription draft you review and sign, from $79/mo on the annual Assist plan. Move up to Copilot for a bundled AI EHR and WhatsApp, or Autopilot for an AI receptionist and follow-ups. The draft never goes to a pharmacy, and the sign-off stays yours, the way it is today.
- Large health system needing deep EHR integration: a sales-led enterprise vendor may be the right conversation. Expect a scoped quote, not a self-serve rate.

The cheapest way to find your answer is to stop reading price tables and run the same real-workflow test on two finalists. Request your 7-day trial and read every draft, measure review time, test the handoff, and keep a failure log. The [honest roundup of the leading scribes](../best-ai-medical-scribes/) supplies the trial scorecard; the [EMR cost guide](/us/blog/emr-system-cost-guide/) shows how to annualize implementation and staff work beside the subscription.

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot works alongside it. A new practice can instead use the bundled Patient Square EHR, available from the Copilot tier, as its system of record. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## HIPAA and AI Medical Scribes: BAAs, Consent, and What to Verify
https://patientsquare.com/us/blog/ai-scribe-hipaa-baa-consent/
Published 2026-04-09 · Updated 2026-08-27 · Tags: hipaa, compliance, baa, consent, trust

No software is HIPAA certified. What a BAA must contain, which states require all-party consent to record visits, and a 12-question vendor checklist.

No. HHS states there is no standard that requires certifying compliance, and the Office for Civil Rights does not certify any person or product as HIPAA compliant. A vendor can operate in a compliant way and prove it with a BAA and documented safeguards, but a certificate does not exist.

Can an AI scribe be HIPAA compliant? It can be used in a HIPAA-compliant way. No software product is "HIPAA certified," though. HHS certifies nothing and recognizes nobody else's certificate. Compliance lives in the arrangement, not the badge: a signed BAA before patient information flows, Security Rule safeguards you can verify, and patient consent that satisfies your state's recording law.

So that's the framework. The rest of this guide is the verification work behind it. What the BAA must actually say. The twelve questions that separate a compliant vendor from a merely confident one. And the state-by-state consent table for the part HIPAA doesn't touch at all: recording the room.

> **Key takeaways**
>
> - "HIPAA-certified software" doesn't exist. HHS says no standard requires certifying compliance, and OCR does not certify any person or product as HIPAA compliant.
> - A missing BAA is a violation by itself. OCR settled with one Illinois practice for $31,000 after it shared 10,728 patients' records with a vendor. No signed agreement, and that was the whole case.
> - Eleven states require all-party consent to record a conversation. Which eleven depends on whether you mean the exam room or the telehealth call.
> - 45 CFR 164.504(e) dictates what your vendor's BAA must contain, down to subcontractors and what happens to PHI when you cancel.
> - Audio that's never stored still requires consent. The statutes regulate the act of recording, not the archive.

## Why "HIPAA-certified" software doesn't exist

Start with the words of the agency that enforces HIPAA. HHS's own FAQ on the Security Rule is blunt: there is no standard or implementation specification that requires a covered entity to "certify" compliance, and HHS does not endorse or otherwise recognize private organizations' certifications. OCR's guidance on misleading marketing goes further. It does not certify any persons or products as "HIPAA compliant," and a private seal does not shrink your legal obligations by one clause.

So when a vendor's homepage wears a "HIPAA Certified" badge, one of two things happened. Either someone paid a third party for an assessment and over-labeled it, or marketing wrote the compliance page without asking anyone who knew. That badge is the single most useful tell in this market, honestly. Vendors who understand the rule say "compliant-ready" or "aligned." The best of them skip the adjectives and just show you the artifacts. A BAA they'll sign. Named encryption standards. An audit status stated honestly.

Honest phrasing sounds like ours, and we'd hold any vendor to the same bar: HIPAA-compliant safeguards, a BAA available for every customer, SOC 2 Type II audit underway. Underway means underway. If a vendor's badge claims more than its contract will, believe the contract.

## What makes AI scribe use HIPAA-compliant in practice?

Three legs hold it up, and you control two of them.

The first is a signed BAA, in place before the first real visit. The vendor handles protected health information on your behalf, which makes it a business associate, and the Privacy Rule requires the written agreement first. Details in the next section.

Second, Security Rule safeguards, verified rather than assumed. Administrative, physical, technical. Encryption in transit and at rest, access limited by role, activity logged, a breach process that exists on paper before anyone needs it. You can't audit a vendor's data center. You can demand specific answers, and the checklist below is built to get them.

The third leg is consent that satisfies your state's recording law, and HIPAA itself never says "ask the patient before using a scribe." Treatment use of PHI needs no signed authorization, a point MGMA's guidance on AI consent forms makes too. The duty to ask comes from somewhere else: state wiretap and eavesdropping statutes, plus the simple fact of running a practice where patients are told who's listening.

For orientation: the AI Medical Scribe is one module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, all ready to review and sign about two minutes after the visit. If you're still mapping the category itself, start with our [plain-English explainer on how AI scribes work](../what-is-an-ai-medical-scribe/), then come back for the paperwork.

## Do you need a BAA with an AI scribe vendor?

Yes. Not as a best practice, but as the precondition for the disclosure being legal at all.

The cautionary case is small-practice-sized. In 2017, OCR settled with the Center for Children's Digestive Health, an Illinois pediatric group, for $31,000. The practice had shared 10,728 patients' records with a storage vendor; when OCR asked for the signed business associate agreement, neither side could produce one. The missing contract was enough. HHS's own headline for the resolution: "No Business Associate Agreement? $31K Mistake."

And a real BAA has a specific shape. 45 CFR 164.504(e)(2) spells out what the contract must establish:

- Permitted uses and disclosures: exactly what the vendor may do with PHI, and nothing that would violate the Privacy Rule if you did it yourself. (e)(2)(i)
- Safeguards: the vendor must use appropriate safeguards and comply with the Security Rule for electronic PHI. (e)(2)(ii)(B)
- Reporting: any use or disclosure outside the contract, including breaches, gets reported to you. (e)(2)(ii)(C)
- Subcontractor flow-down: anyone the vendor hands your PHI to agrees to the same restrictions. (e)(2)(ii)(D)
- Patient-rights support: the vendor makes PHI available for access, amendment, and accounting of disclosures. (e)(2)(ii)(E)–(G)
- Return or destruction at termination: when you leave, PHI comes back or is destroyed, or the protections follow it. (e)(2)(ii)(J)
- Termination for cause: you can end the contract if the vendor materially violates it. (e)(2)(iii)

Two traps worth naming. First, a clause buried in a SaaS terms-of-service is not a BAA. You need a contract that satisfies 164.504(e), signed, and producible on request, because "producible on request" is precisely what the $31,000 settlement was about. Second, the subcontractor clause matters more for AI scribes than for almost any other practice software: your audio may pass through a speech-recognition engine, a language-model API, and a cloud host. Flow-down means each of them is bound, not just the brand on the invoice.

And one ask the regulation doesn't require but you should make anyway: a written commitment on whether PHI is used to train models. Get it in the BAA or an attached data-processing addendum, not in a sales email.

## The 12-question vendor checklist

Run every vendor through these, including us. The regulation or reason sits behind each one.

| # | Ask the vendor | A good answer looks like |
|---|---|---|
| 1 | Will you sign a BAA for a practice my size, and when? | Yes, for every customer including solo, signed before any real patient visit. Tier-gated BAAs are a red flag. |
| 2 | Is the BAA a standalone signed contract or a ToS clause? | A standalone agreement meeting 45 CFR 164.504(e), countersigned, copy in your files. |
| 3 | Do your subcontractors (ASR, LLM APIs, cloud) have their own BAAs? | Yes, named or described, with flow-down per (e)(2)(ii)(D). "We can't discuss our stack" is not an answer. |
| 4 | What happens to visit audio, and when is it deleted? | One sentence with a timeline. Vague retention language means indefinite retention. |
| 5 | How is PHI encrypted in transit and at rest? | Named standards: TLS 1.2+ in transit, AES-256 at rest, or equivalent. |
| 6 | Who at your company can access my notes, and is access logged? | Role-scoped access, every access logged, logs reviewable. |
| 7 | Is my patients' data used to train your models? | A written yes-or-no, separately for audio and note text, attached to the BAA. |
| 8 | What is your breach-notification commitment and timeline? | Contractual reporting per (e)(2)(ii)(C), with a stated clock, not "we follow applicable law." |
| 9 | Which third-party audits are complete, and which are in progress? | Honest status. "SOC 2 Type II underway" is a real answer; "HIPAA certified" is a tell (see above). |
| 10 | Who owns the notes, and can I export or delete them? | The practice owns them; export or delete any visit, anytime, no ticket required. |
| 11 | What happens to PHI if I cancel? | Return or destruction per (e)(2)(ii)(J), with a timeline, in the contract. |
| 12 | Can I see the consent workflow you recommend for patients? | A script and documentation pattern, plus a straight acknowledgment that consent is your obligation and they'll make it easy. |

How we answer the same twelve, on the record: a BAA for every customer, solo practices included. TLS 1.2+ in transit, AES-256 at rest. Visit audio is processed in memory and discarded once the note is drafted, so there is no audio archive to retain, train on, or breach. Access is role-scoped and logged. Notes belong to your practice; export or delete any visit anytime, and we never sell or share clinical data. SOC 2 Type II audit underway, that phrase exactly, nothing grander. On training and note text, ask us in the demo and you'll get the answer in writing, which is the standard you should hold everyone to.

The fastest way to run the checklist is against a live system. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and ask for our BAA in the same call. Then ask whether the BAA covers the trial period, a question worth putting to every vendor on your shortlist, us included. 7-day free trial · month-to-month available · audio never stored.

## Which states require all-party consent to record a visit?

Federal law sets the floor: one party's consent is enough (18 U.S.C. § 2511(2)(d)), and the clinician is a party. Eleven states raise it and require everyone's consent. Per the 50-state survey of recording statutes by law firm Matthiesen, Wickert & Lehrer (chart dated February 2022; we fetched and read it in June 2026), those eleven are California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington.

You'll see "12," "13," even "15" in other guides. Nobody's lying. The spread comes from four states with split or unsettled rules, and from a wrinkle that matters specifically to medicine: several statutes treat an in-person conversation differently from a phone or video call. An ambient scribe in an exam room is recording an in-person conversation. The same scribe on a telehealth visit is recording an electronic one, and that can land it under a different statute entirely.

| State | Exam-room visit | Phone / telehealth | Watch for |
|---|---|---|---|
| California | All parties | All parties | Strictest-state rule for cross-state calls (*Kearney*) |
| Delaware | All parties | All parties | Older statutes conflict; treat as all-party |
| Florida | All parties | All parties | Exception only where no privacy expectation |
| Illinois | All parties | Contested | 2014 amendment may permit participant recording of calls; treat as all-party |
| Maryland | All parties | All parties | Clear all-party statute |
| Massachusetts | All parties | All parties | Bars secret recording outright |
| Montana | All parties | All parties | Notice of recording can satisfy the statute |
| Nevada | One party | All parties | Flips by mode (*Lane v. Allstate* on calls) |
| New Hampshire | All parties | All parties | Knowing participation can count as consent (*Locke*) |
| Pennsylvania | All parties | All parties | Clear all-party statute |
| Washington | All parties | All parties | Announcement at start of recording has a statutory path |
| Connecticut | One party | All parties (civil) | Phone recording without consent risks civil liability |
| Oregon | All parties informed | One party | Reverse mode-flip: in-person requires informing everyone |
| Michigan | Participant may record | Participant may record | Reads all-party; case law says otherwise (*Sullivan v. Gray*) |
| Vermont | No statute | No statute | Unsettled, so default to consent |

Count the exam-room column and you get eleven all-party-or-informed states; count the telehealth column and you also get eleven, but not the same eleven. Nevada swaps out, Oregon swaps in. That's the trap in every "13 two-party states" listicle: the number depends on which conversation you're having.

Two practical rules fall out. For telehealth across state lines, assume the stricter state's law applies. That's what the California Supreme Court held in *Kearney v. Salomon Smith Barney* when a Georgia firm recorded calls with California clients. And for everything else: a consent sentence takes five seconds. A practice in Tampa needs it by statute; a practice in Houston needs it because patients talk, and "my doctor records me secretly" is a sentence no practice survives. Get consent everywhere and the map becomes trivia.

One more thing, said plainly: this section is reporting, not legal advice. Statutes get amended and case law moves, so verify your state's current rule with counsel before you write your policy.

## Does "we never store audio" remove the consent requirement?

No, and we're the right vendor to say so, because no-stored-audio is our own architecture. Recording statutes regulate the act of capturing a conversation, not the archive you keep afterward. A scribe that processes audio in memory and discards it at note draft is still recording while it listens. Consent still applies. All states.

What the architecture does change is your risk surface. There's no recording to breach, subpoena, or leak, and the consent conversation gets easier to have honestly. The script we suggest is one breath long: *"I use a tool that listens and drafts my note so I can focus on you instead of the keyboard. The audio is deleted as soon as the note is written. OK with you?"* Then one line in the chart: "Verbal consent to ambient documentation obtained." In all-party states, add a notice in the waiting room and intake forms; MGMA publishes a sample AI consent form for members if you want a template with a committee's fingerprints on it.

What other vendors do with audio is its own buying question. Retention windows range from seconds to indefinite, and almost nobody puts the policies side by side. We did: see the [audio-retention comparison across major scribes](../ai-scribe-audio-retention/) before you take any vendor's word for it, including ours.

## What should a small practice do this week?

The compliance work for an AI scribe is real but small. For a three-clinician practice, it's an afternoon:

1. Shortlist vendors that answer the twelve questions in writing. A vendor that stalls on questions 1, 4, or 7 has answered them.
2. Get the BAA signed before the first real patient, and confirm whether it covers the trial period, since you'll be feeding the system real visits from day one.
3. Adopt the consent script and the one-line chart documentation. Add signage if you're in an all-party state or just want the trust dividend.
4. Check your telehealth footprint with counsel if you see patients across state lines. The stricter state's recording law is the safe assumption.
5. File the artifacts (the BAA, the vendor's written answers, your consent policy) where you can produce them on request. Producible-on-request is the lesson of the $31,000 settlement.

Your notes stay yours through all of it: export or delete any visit, anytime, whichever vendor's logo is on the screen. And if a vendor won't promise that in writing, return to step one.

The receipts behind everything we've claimed here live on our [security page](../../security/), stated in the same plain terms: what's encrypted, who can access what, what's audited, and what isn't done yet. Read it the way you'd read any vendor's: skeptically, checklist in hand, and then [test the product on a week of real visits](../../pricing/) before anyone signs anything long.

HIPAA-compliant · No audio stored · SOC 2 in progress

---

## AI SOAP Note Generators Compared (2026)
https://patientsquare.com/us/blog/ai-soap-note-generators-compared/
Published 2026-04-08 · Updated 2026-07-22 · Tags: ai-scribe, soap-note, comparison

An honest comparison of AI SOAP note generators: Freed, Heidi, paste-text tools, and ambient scribes. What each does, what it costs, and how to pick.

It is software that turns a clinical encounter into a structured SOAP note: subjective, objective, assessment, plan. Two kinds exist. Paste-text tools take notes you type or dictate and reformat them into SOAP structure. Ambient scribes listen to the visit itself and draft the note from the conversation, so there is no typing step at all.

Most AI SOAP note generators fall into two camps, and picking the right tool starts with knowing which camp you're shopping in. One camp takes notes you type or dictate and reformats them into clean SOAP structure. The other listens to the visit and writes the note from the conversation, so there's no typing step left to format. The first is cheaper and the second saves more time, and that single split decides most of the call.

This is an honest roundup of the field as it stands in 2026: Freed, Heidi, the paste-text generators, and where AI Medical Scribe by Patient Square fits. Real strengths on each side, real tradeoffs, and the questions that actually separate them.

> **Key takeaways**
>
> - "AI SOAP note generator" covers two different products: paste-text reformatters and ambient scribes that draft the note from the visit audio.
> - Paste-text tools are cheap and often free, but you're still typing the input. The time saved is in formatting, not in the encounter.
> - Ambient scribes (Freed, Heidi, AI Medical Scribe by Patient Square) remove the typing step entirely. Primary-care physicians log a median 36.2 minutes of EHR time per 30-minute visit, per a 2023 JAMA Network Open study. That's the time these tools target.
> - Audio handling is the question most buyers skip and most regret skipping. Ask what happens to the recording, and when.
> - Free tiers almost always cap notes per day or strip the features worth paying for. Read the limit, not the headline.

## The two kinds of "SOAP note generator"

Search "AI SOAP note generator" and you'll get two product categories on the same results page. They feel similar and they are not.

The first kind is the paste-text generator. You write or dictate a rough account of the visit (a few bullet points, a dictated paragraph, your shorthand) and the tool reshapes it into a structured SOAP note. Some let you answer a short form instead. These are fast to try, frequently free, and genuinely useful if you already capture notes and just hate formatting them. The catch is the input. You're still reconstructing the encounter from memory and typing it out. The tool saves the formatting minutes, not the documentation minutes.

The second kind is the ambient scribe. You see the patient normally and the tool captures the conversation through a microphone. It transcribes, then drafts a SOAP note from what was actually said. No typing, no dictation, no reconstructing the visit afterward. You read a draft and sign. This is the camp that targets the real documentation burden: the after-hours charting, the note that now outlasts the appointment.

The price gap follows the value gap. Paste-text tools cluster at free-to-cheap. Ambient scribes run roughly $79 to $149 per clinician per month at the transparent end of the market. If your problem is "I don't mind typing notes, I just want them formatted," the cheap tool is the right answer. If your problem is "I'm charting at 9pm," the ambient tool is the one that moves the needle.

## The roundup, side by side

Here's the field across the dimensions that decide a purchase. Patient Square's column is highlighted; the comparison is honest, not stacked.

A note on reading this table: a check mark isn't a winner and a cross isn't a loser. "Works from typed input" is a cross for Patient Square because it's ambient by design, and for a clinician who wants to keep dictating, that's a reason to pick a different tool. The point is fit, not score.

## Freed: the ambient incumbent for solo and small practice

Freed is the name most clinicians have heard, and for good reason. It's a polished ambient scribe aimed squarely at independent practitioners, and it does the core job well: capture the visit, draft a structured SOAP note, push it into a browser-based EHR through a Chrome extension. It supports dictation as a secondary input and handles code-switching within a visit.

Where Freed is strong: a large, customizable template library across specialties; ICD-10 coding on the Premier plan (CPT flagged as beta); patient instructions, letters, and referrals on the top tier; a wide set of EHR-push targets for web-based systems. For a solo clinician on a common outpatient EHR, it's a credible default.

Where to look closely: the features that make it feel complete (EHR push, ICD-10 coding, visit summaries, patient instructions) live on the Premier plan at $119/mo, or $104/mo billed annually, per Freed's pricing page. The Core plan at $79/mo gives you unlimited notes and AI editing but holds those back. So the real comparison isn't "$79 Freed vs the field." It's Premier, once you want coding and EHR push. On languages, Freed's help center names 15 (the marketing claim is 90+, not enumerated); Hindi is not among the named ones on the pages we checked, and the final SOAP note is generated in English. On audio, Freed deletes recordings once notes and quality checks complete and can hold paused-visit audio up to 28 days.

## Heidi: the multilingual generalist

Heidi is the other ambient scribe clinicians weigh seriously, and its strength is breadth. Its developer docs list 81 language codes for transcription and document generation, including Hindi and romanized Hindi, which is a genuinely wider net than most US-focused tools cast. It pairs the note with a natural-language assistant ("Ask Heidi") that edits the note and spins up downstream documents from the session.

Where Heidi is strong: language coverage, a deep template library across specialties, downstream document generation, and EHR integrations as a paid add-on. If your patient mix spans languages, Heidi belongs on your shortlist.

Where to look closely: pricing renders dynamically and the exact current numbers are best confirmed on Heidi's own page. Secondary sources put a clinician tier around $150/user/mo with a limited free plan beneath it, and EHR integration is a paid add-on rather than included. On audio, Heidi deletes recordings right after transcription and keeps transcripts and notes, which is a reasonable posture worth confirming for your compliance needs.

## Paste-text and "free" SOAP note generators

This is the camp people mean when they search "free AI SOAP note generator." Tools in this band, the paste-a-paragraph and fill-a-form generators, take input you provide and return a structured note. They're handy for a specific job: you've got rough notes and you want clean SOAP formatting in a few seconds.

Be clear-eyed about what they do and don't do. The free tier is real but usually capped: a handful of notes a day, or a watermark, or the structured-export feature held behind a paid plan. More importantly, the input is still on you. If you're typing or dictating the substance of the visit, you've saved the formatting time, not the documentation time. For a clinician whose pain is the after-hours charting, that's the smaller half of the problem.

There's also a quieter consideration: where does the text go? A free web tool that processes clinical content should have a clear data-handling and HIPAA posture before any patient detail touches it. Some do; some are general-purpose writing tools wearing a medical label. Check before you paste.

If your honest answer is "I don't mind providing the input, I just want it formatted," a paste-text generator is a fine, cheap tool. If your answer is "I want the note written for me," you're shopping in the ambient camp, and the free generators won't get you there.

## Where AI Medical Scribe by Patient Square fits

The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

Three things shape where it fits against the field above.

It's ambient, not paste-text. The note is drafted from the visit conversation, so there's no typing step. That puts it in the same camp as Freed and Heidi, not the free reformatters, which is the right comparison if your goal is to stop charting after hours.

The audio is never stored. Visit audio is processed in memory and discarded once the note is drafted. No audio archive exists, on our side or the practice's. What survives is the note you reviewed and signed. For a visit that includes a mental-health disclosure or anything said off the record, that's a different answer than "we keep it for 28 days," and it's the question worth asking every vendor first. The full posture is on the [security page](../../security/).

The price is published, with no sales call to see it. It's from $79 per clinician per month in the US on annual billing (the Assist plan), and every tier carries unlimited visits and notes with no per-note metering. Higher tiers add capabilities as you go up, a bundled AI EHR and WhatsApp messaging at Copilot, an AI Receptionist and follow-ups at Autopilot, so you pick the tier that matches how much you want the platform to do. The full ladder is on the [pricing page](../../pricing/). The note itself comes with ICD-10 suggestions and a prescription draft included on every plan. The draft mirrors the plan you discussed and stays a draft you review and sign; screening it for interactions and dosing is your call, as it is on any prescription. No sales call required to see what you'll pay.

Where it's not the fit: if you want to keep dictating rough notes and just reformat them, a paste-text tool is cheaper. If your must-have is deep two-way write-back into a specific EHR, the integration-heavy incumbents go further on that axis today. Honest is honest.

For the wider head-to-head across the self-serve scribe field, our [roundup of the best AI medical scribes](../best-ai-medical-scribes/) ranks the field by who fits which clinic, and the [deep dive on SOAP note quality](../ai-scribe-soap-note-quality/) covers what actually makes a drafted note good enough to sign.

{/* deep-link soap-note-generator product page once it ships */}

## How to actually pick one

Skip the feature-table paralysis. Three steps get you to an answer faster than a month of reading comparison pages.

First, decide which camp you're in. Are you willing to keep typing or dictating the input? If yes, start with a paste-text generator and a free tier; you'll know within a day whether the formatting saves enough to matter. If no, you want an ambient scribe, and the rest of this applies.

Second, run two ambient tools on the same real week. Pull your five hardest visit types: the patient who talks in circles, the one with three complaints, the one whose family member answers, the accented visit your autocomplete already mangles, the one that went somewhere unexpected. Run them through two tools side by side. Read every draft closely. Does the note capture what happened, or what usually happens in this kind of visit? Are the medications, dosages, and frequencies right? Is anything in the note that wasn't actually said?

Third, do the arithmetic on your volume, not the sticker. A tool that costs $40 more a month and lets you sign in 90 seconds is cheaper than one that takes five minutes to fix per note across 20 visits a day. And check the renewal price, not just the launch rate. The two diverge more often than they should.

AI Medical Scribe by Patient Square includes an assisted 7-day trial, which is enough for a real clinic week with real patients. Read the drafts closely for the first few days. By Friday you'll know whether the note holds up in your workflow, which is the only test that settles it.

---

## EkaScribe vs Augnito vs Patient Square (2026)
https://patientsquare.com/in/blog/india-ai-scribe-comparison/
Published 2026-04-08 · Updated 2026-07-22 · Tags: comparison, ekascribe, augnito, india

An honest comparison of three AI documentation tools for Indian doctors: EkaScribe, Augnito, and AI Medical Scribe by Patient Square, on price, languages, Rx, and ABDM.

Augnito is primarily medical dictation. The doctor speaks the note aloud and it's transcribed, command-driven. An ambient AI scribe like EkaScribe or AI Medical Scribe by Patient Square listens to the actual doctor-patient consultation and drafts the note from the conversation, so you don't dictate anything.

EkaScribe, Augnito, and AI Medical Scribe by Patient Square overlap, but they're not solving the same problem. EkaScribe is an India-native ambient scribe wired into ABDM. Augnito is medical dictation, the kind where you speak the note. AI Medical Scribe by Patient Square is an ambient scribe built around code-mixed consults and prescription safety. Nobody has published an independent comparison of the three. So here's an honest one, built only on what each vendor publishes.

> **Key takeaways**
>
> - Augnito is dictation (you speak the note); EkaScribe and Patient Square are ambient (they listen to the consult).
> - EkaScribe publishes ₹1,499/month scribe-only (EMR separate); Patient Square starts at ₹1,599/month annual ex-GST, with the ₹2,399 Copilot plan bundling a full AI EHR alongside the scribe; Augnito publishes no price at all. Pair EkaScribe with an EMR and the eka stack runs ₹2,600–3,000/month.
> - For live ABDM/ABHA linking today, EkaScribe is the better fit. Our ABDM integration is roadmap, not shipped.
> - All three deserve a trial on your own patient mix before you commit; that's the only fair accuracy test.

## Dictation or ambient: which problem are you solving?

This is the first fork, and it matters more than price. Augnito's core product is medical dictation: the doctor speaks the note aloud, something like "new paragraph, assessment, type 2 diabetes, comma, suboptimal control," and it's transcribed with voice commands, in the lineage of Dragon-style tools. It's fast and accurate for clinicians who already narrate, and Augnito's marketing cites a large hospital footprint and high accuracy (claims we'll attribute to them rather than test ourselves).

EkaScribe and AI Medical Scribe by Patient Square are ambient. They listen to the actual conversation between you and the patient and draft the note from it, so you don't dictate. The AI Medical Scribe by Patient Square, the scribe module inside its clinical platform, builds a live transcript as you speak and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft the moment the visit ends, ready to review and sign. If you want to stop narrating notes entirely, you want ambient. If you like dictating and just want it faster, Augnito's category is the one to shortlist.

## How do they compare, line by line?

| | EkaScribe (eka.care) | Augnito | AI Medical Scribe by Patient Square |
|---|---|---|---|
| **Type** | Ambient scribe | Medical dictation | Ambient scribe |
| **Published price** | ₹1,499/mo Pro scribe-only; free tier 5 consults/day; EMR separate | None published (sales-gated) | From ₹1,599/mo (Assist annual), ex-GST; ₹2,399 (Copilot annual) bundles scribe + AI EHR |
| **App-store price signal** | App listings | App Store India IAPs ₹1,199 / ₹3,299 / ₹11,900 (periods unlabeled) | n/a |
| **Indian languages** | 20+ named (Hindi, Bengali, Telugu, Tamil, Marathi, Gujarati, Kannada, Malayalam, Punjabi, Urdu and more) | Multiple Indian languages (per Augnito) | English + Hindi + 20+ Indian languages, code-mixing auto-detected |
| **Note language** | English / structured | As dictated | Clean clinical English |
| **What's drafted** | Note + clinical summary | Transcribed dictation | Note + ICD-10 suggestions + Rx draft |
| **Prescription** | Voice-to-prescription | Not applicable | Draft from the consult; you review and sign |
| **Audio handling** | Cloud servers (India), per eka framing | Per Augnito policy | Live consultation audio discarded; uploads use a separate mode with explicit consent |
| **ABDM** | Live ABDM/ABHA ecosystem | Dictation-focused | On the roadmap (not yet integrated) |
| **Trial** | Free tier (5/day) | 7-day | Assisted 7-day |

All figures from each vendor's own pages and listings in June 2026; confirm before buying. Two cells deserve plain talk.

## Where EkaScribe is the better choice

If linking records to ABHA under ABDM is something you need today, EkaScribe wins. It's in the ABDM ecosystem now, and we are not. Our ABDM integration is on the roadmap; we won't dress that up. eka.care is also India-native, publishes its price openly, and names a deep list of Indian languages. For a clinic whose buying decision turns on ABDM readiness, that's the honest recommendation. Before choosing, use the broader [India scribe roundup](/in/blog/best-ai-scribe-for-india-2026/) to check the distinction between company-level ABDM evidence and the exact product workflow.

One thing the SERP won't tell you, because eka's review results are all self-published: user reviews on the app stores report friction around renewal sales calls and post-payment activation. Worth reading the store reviews yourself before you commit, and that's true of any vendor, us included.

## Where Augnito is the better choice

Already speak your notes? If you're a dictation loyalist who wants a fast, accurate Dragon-style tool and isn't after ambient listening, Augnito is built for exactly that, with a substantial Indian hospital footprint. The catch is price discovery. There's no public number, so you'll go through sales. The only verifiable figures are the App Store India in-app purchases (₹1,199, ₹3,299, ₹11,900), and even those don't label their billing periods. If transparent pricing matters to you, that's real friction.

## Augnito Spectra vs ambient scribe: what the distinction actually means

Augnito has two separate products and people mix them up constantly.

**Augnito Spectra** is push-to-talk dictation. Press a button, speak your note aloud, the words appear in whatever clinical system is on your screen. It runs as a floating widget on Windows, Web, Chrome, iOS, and Android, and it works directly inside any RIS, LIS, HIS, or EMR — Epic, Cerner, Intersystems — without native integration. You don't install anything on the hospital server. That EMR-agnostic posture is the real pitch for larger Indian hospital deployments with legacy software no vendor will build an API for.

**Augnito Omni** is their ambient AI scribe: it listens to the consultation and drafts the note, the same category as EkaScribe and AI Medical Scribe by Patient Square. Omni and Spectra are sold separately.

Most of the Augnito comparisons circulating online don't make this split. They compare a dictation product (Spectra) against ambient scribes. Those are different tools solving different workflow problems.

### Spectra vs ambient: the honest comparison

| | Augnito Spectra | AI Medical Scribe by Patient Square |
|---|---|---|
| **Mode** | Push-to-talk dictation | Ambient (listens to consultation) |
| **What you do during consult** | Speak the note aloud | Consult normally; don't narrate |
| **EMR placement** | Dictates directly into any EMR / RIS / LIS via floating widget, no integration needed | Works alongside your EMR; exports PDF / DOCX |
| **Indian language support** | Accent-agnostic dictation; named-language list not published on vendor site | English + Hindi + 20+ Indian languages; code-mixed Hinglish input, English note output |
| **Rx / prescription** | Not a documented feature of Spectra | Prescription draft you review and sign |
| **Audio handling** | Per Augnito data-retention policy (uses de-identified data for model training by default; customers can opt out) | Live consultation audio discarded; uploads use a separate mode with explicit consent |
| **ABDM / ABHA** | Dictation-focused; ABDM not documented | On our roadmap; not live yet |
| **Trial** | 7-day free trial, no card, no implementation fee (Spectra) | Assisted 7-day |
| **Published price** | No public price; App Store India IAPs ₹1,199 / ₹3,299 / ₹11,900 (billing periods unlabeled) | From ₹1,599/mo (Assist annual), ex-GST; ₹2,399 (Copilot annual, + 18% GST = ~₹2,831/mo) bundles scribe + AI EHR |

A few cells need a direct call-out.

**Audio and training data:** Augnito's privacy policy states they use de-identified user data to train their AI by default; customers can opt out. AI Medical Scribe by Patient Square doesn't store audio at all — the recording is processed in memory and discarded once the note is drafted. Under India's DPDP Act, purpose limitation and data minimisation are key obligations. Not storing audio is the cleaner answer to both. That said, Spectra is a dictation overlay, not a conversation recorder, so the data-handling surface area is different. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

**EkaScribe and ABDM:** Worth restating because it changes the recommendation. eka.care is live in the ABDM ecosystem today — ABHA linking, ABDM-wired workflows. If a clinic's buying decision hinges on ABDM readiness right now, EkaScribe is the honest recommendation and we'll say so. Our ABDM integration is roadmap. We don't call it live, and we won't until it ships.

### Who should pick Spectra

Spectra is the right shortlist for a doctor or registrar who already dictates and just wants a faster, more accurate recognition engine that drops text wherever the cursor is, with no EHR-side setup. Radiologists dictating reports into a PACS or RIS are the clearest fit — Spectra supports Discharge Summary and Imaging Report templates natively. For outpatient clinics where the doctor wants to finish the consult without narrating it, Spectra is the wrong category. That's ambient territory.

If you're comparing the Augnito stack broadly, the [EkaScribe alternatives roundup](../ekascribe-alternatives-india/) covers how both Augnito products sit against the wider India market. And if you're deciding on price, the [India AI scribe rate card](../ai-medical-scribe-price-india/) has the full GST-inclusive breakdown.

## Where AI Medical Scribe by Patient Square fits

The code-mixed, prescription-heavy clinic. If your consults are Hinglish, with Hindi and English braided together, and you need the note in clean English plus a prescription draft you review and sign, that's what we built. The scribe doesn't screen the draft for interactions or dosing; you stay the safety check, the same as you are today. We publish every number in rupees: Assist starts at ₹1,599 annual ex-GST for the scribe essentials, and the Copilot plan at ₹2,399 (about ₹2,831 with 18% GST) bundles the scribe with a full AI EHR and WhatsApp. The tiers gate features, so you pay up only for what you use, and there is a 7-day free trial through the India signup page. The audio is never stored, which is also the cleaner answer under the [DPDP Act](../dpdp-act-clinics-guide/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The deciding move is the same for all three. Run them on your own OPD. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>, alongside EkaScribe's free tier and an Augnito demo, and let your actual patients, accents, and prescriptions pick the winner. Want the full price picture first? The [India rate card](../ai-medical-scribe-price-india/) lays out every figure with GST; for the language question, [Hindi and Hinglish handling](../ai-scribe-hindi-indian-languages/) has a worked example.

---

## AI Medical Scribe Price in India: 2026 Rate Card
https://patientsquare.com/in/blog/ai-medical-scribe-price-india/
Published 2026-04-07 · Updated 2026-08-30 · Tags: ai-scribe, pricing, india

Compare Patient Square AI medical scribe pricing in India: plan cadence, ex-GST and with-GST maths, and questions for a like-for-like quote.

Patient Square lists AI Medical Scribe from ₹1,599 per clinician monthly-equivalent on annual billing for Assist, ex-GST, or ₹1,887 with 18% GST. Assist is ₹1,999 month-to-month; Copilot and Autopilot have their own monthly and annual-equivalent prices. Ask every other vendor for a current written quote that states the product scope, billing cadence, tax treatment, limits, and record-system path before comparing it.

Price comparisons break when they mix a scribe-only plan, a record-system plan, different billing cadences, and different tax treatment. [AI Medical Scribe by Patient Square](../../pricing/) starts at ₹1,599 per clinician monthly-equivalent on annual billing for Assist, ex-GST, or ₹1,887 once 18% GST is added. Assist is ₹1,999 month-to-month. Copilot, the tier with the bundled AI Copilot EHR, starts at ₹2,399 monthly-equivalent on annual billing. Ask competitors for a current written quote before placing them beside those figures.

This is a retained repository research snapshot, not a fresh live price pull. The underlying comparison captures first-party material reviewed in June 2026; computed conversions are labelled as computed, and the GST arithmetic is shown in the open. The retained Google Ads Keyword Planner export dated 2026-07-29 records `ai medical scribe` at 390 India average monthly searches. Its LOW competition field refers to paid-advertiser competition, not organic ranking difficulty.

> **Key takeaways**
>
> - Assist is ₹1,599 per clinician monthly-equivalent on annual billing, ex-GST (₹1,887 with 18% GST); it includes the AI Medical Scribe and Scheduling.
> - Copilot starts at ₹2,399 per clinician monthly-equivalent on annual billing, ex-GST, and adds the bundled AI Copilot EHR.
> - Compare a competitor's written quote on the same product scope, billing cadence, per-user unit, tax basis, trial limit, and record-system path.
> - Patient Square's displayed ex-GST price plus 18% GST is an invoice example. Ask an appropriate tax adviser how tax applies to your clinic and any competitor quote.

## Patient Square's India rate card

The rate card below gives the published Patient Square ladder. For any competitor, obtain a written quote and compare scope, billing cadence, user unit, tax treatment, limits, and the record-system path before treating two figures as comparable.

| Tool | ₹ / doctor / month | What that number is | Free tier / trial |
|---|---|---|---|
| **AI Medical Scribe by Patient Square: Assist** | **₹1,599** monthly-equivalent on annual billing · ₹1,999 month-to-month | AI Medical Scribe and Scheduling; per clinician, published ex-GST with 18% GST added | 7-day free trial |
| **AI Medical Scribe by Patient Square: Copilot** | **₹2,399** monthly-equivalent on annual billing · ₹2,999 month-to-month | Adds WhatsApp messaging and AI Copilot EHR; per clinician, published ex-GST with 18% GST added | 7-day free trial |
| **AI Medical Scribe by Patient Square: Autopilot** | **₹3,999** monthly-equivalent on annual billing · ₹4,999 month-to-month | Adds the named AI Receptionist and AI Follow-ups modules, priority support, and adoption and ROI analytics; per clinician, published ex-GST with 18% GST added | 7-day free trial |

Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot. Assist is ₹1,599 per clinician monthly-equivalent on annual billing and includes Scheduling. Copilot adds WhatsApp messaging and AI Copilot EHR. Autopilot adds the named AI Receptionist and AI Follow-ups modules, priority support, and adoption and ROI analytics. No plan has per-note metering.

The [India pricing page](../../pricing/) shows the whole ladder with the + 18% GST note beside every number. A 7-day free trial is available at each tier after workspace setup. Run it against a real clinic week, not a demo script.

## What does 18% GST mean when a clinic buys software?

Patient Square's India prices are ex-GST, so the number on the pricing page is not the number on the invoice. Here is an invoice arithmetic example, not tax advice: Assist at ₹1,599 per clinician monthly-equivalent on annual billing + 18% = **₹1,887**; Copilot at ₹2,399 per clinician monthly-equivalent on annual billing + 18% = ₹2,831. Same product family, GST on top, no per-note meter underneath.

Tax recoverability depends on the clinic's supplies, registration, and current law. Treat the displayed calculation as an invoice example and ask an appropriate tax adviser how it applies to your clinic.

For Patient Square, check the published rate card and invoice. For another vendor, ask whether its quote is ex- or inclusive of tax, then have your adviser assess the treatment.

On a 30-day basis, the Assist monthly-equivalent on annual billing lands at about ₹53 a day ex-GST, or ₹63 a day with GST counted (₹1,887 ÷ 30).

## What will you pay in year two?

Every intro price implies a regular price somewhere; the year-two question is whether you can read it. Patient Square prints its ladder per clinician: Assist ₹1,999 month-to-month or ₹1,599 monthly-equivalent on annual billing; Copilot ₹2,999 month-to-month or ₹2,399 monthly-equivalent on annual billing; Autopilot ₹4,999 month-to-month or ₹3,999 monthly-equivalent on annual billing. All are ex-GST, with 18% GST added. Budget against the published number and treat any promotion as the bonus, not the baseline.

Three questions worth putting to any scribe vendor in writing, before the first invoice:

1. "What is the renewal price after the intro period?" If the regular ladder isn't published, this answer IS the price.
2. "Is the discount conditional on an annual lock-in?" Month-to-month exists on our ladder (₹1,999 Assist, ₹2,999 Copilot). Paying a bit more to stay free to leave is a legitimate choice, and a vendor with no monthly option is telling you something about renewals.
3. "What happens to my notes if I stop paying?" Ours belong to the practice. Export or delete any visit, any time, and we never sell or share clinical data. That's the real lock-in answer. Everything else is contract language.

## How should you compare another scribe quote?

Ask for the exact product, per-user unit, billing cadence, trial limit, tax treatment, language support, data terms, and record-system path in writing. If you need a bundled record system, compare that path directly with Copilot, not with Assist. For Patient Square, the scribe accepts [English, Hindi, and 20+ Indian languages, code-mixing included](../ai-scribe-hindi-indian-languages/), returns a clean clinical-English note, and provides a prescription draft for clinician review. Visit audio is processed in memory and discarded once the note drafts; the full posture is on the [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

The rate card above is the decision aid. Whatever you shortlist, get the GST treatment in writing, then run a real clinic day through it and read every draft before signing. <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a>.

---

## AI Medical Scribe for Hindi, Hinglish & 20+ Indian Languages
https://patientsquare.com/in/blog/ai-scribe-hindi-indian-languages/
Published 2026-04-06 · Tags: hindi, hinglish, multilingual, india

How an AI medical scribe handles Hindi, code-mixed Hinglish, and regional-language consults, then returns the note in clean clinical English, every time.

Some can, most only partially. AI Medical Scribe by Patient Square captures consults in English, Hindi, and 20+ Indian languages, including mid-sentence Hindi-English code-mixing (Hinglish), and returns a structured note in clean clinical English. Several popular global scribes publish language lists that name no Indian language at all.

An AI medical scribe built for India has to do something most global scribes don't even attempt. It has to understand a sentence that starts in Hindi, switches to English for the drug name, and finishes in Hindi again, then write the note in clean clinical English. AI Medical Scribe by Patient Square captures English, Hindi, and 20+ Indian languages, code-mixing and all, and returns a structured note you can put straight into a referral. Here's how that works, and why it matters.

> **Key takeaways**
>
> - You and your patient speak Hindi, Hinglish, or a regional language. The note always comes out in clean clinical English.
> - Code-switching mid-sentence is a known weak point for ordinary transcription tools, which are trained on one language at a time.
> - Several global scribes publish language lists that name no Indian language. The gap is real.
> - Capture works offline with on-device encryption for low-connectivity clinics. Live consultation audio is discarded after drafting; uploaded recordings use a separate retention mode with explicit consent.

## What does a real Indian consult actually sound like?

Not textbook Hindi, and not textbook English. It sounds like this. The exchange below is an illustration, not a real patient:

> **Doctor:** "Toh sugar ka kya scene hai? Last HbA1c kitna tha?"
> **Patient:** "Doctor sahab, woh 8.2 tha. Lekin ab thoda better feel ho raha hai. Metformin le raha hoon regularly."
> **Doctor:** "Theek hai. BP bhi check karte hain. Aap evening walk kar rahe ho? Diet mein sugar control rakhna hai. Main metformin continue rakhta hoon, aur ek SGLT2 inhibitor add karte hain."

Three sentences, four language switches, two drug classes, a lab value, and a plan, all braided together the way medicine is actually practiced in a Gurgaon or Pune OPD. A general Hindi transcriber would garble "HbA1c", "metformin", and "SGLT2 inhibitor." A general English transcriber would drop the Hindi entirely. Neither gives you a usable record.

## What does the note look like afterward?

Clean clinical English, structured, ready to sign:

> **S:** Type 2 diabetes follow-up. Reports feeling better. Adherent to metformin. Previous HbA1c 8.2%.
> **O:** BP to be recorded. Lifestyle: advised evening walks, dietary sugar control.
> **A:** Type 2 diabetes mellitus, suboptimal glycemic control on metformin monotherapy.
> **P:** Continue metformin. Add SGLT2 inhibitor. Reinforce diet and exercise. Review with repeat HbA1c.

The patient spoke Hindi. The chart speaks English. That inversion is the whole point, and it's the part that makes the record useful to a referral specialist, an insurer, or a court that won't read Hinglish.

## Why is the note in English when the visit was in Hindi?

Because the record has a different audience than the conversation. The conversation belongs to you and your patient, in whatever language puts them at ease. The record goes to people and systems that work in English: the cardiologist you refer to, the TPA processing the cashless claim, the medico-legal file if a case is ever raised. A Hindi *transcript*, which is all most speech tools produce, is not a medical record. A clean English *note* is.

This is also where ordinary transcription tools and an ambient scribe part ways. Tools like generic speech-to-text give you a wall of text in one language. The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The structuring and the translation happen together.

## Why is Hinglish so hard for ordinary tools?

Code-switching, the act of changing languages within a single utterance, is a recognized hard problem in speech recognition. Most models are trained predominantly on one language, so when a speaker flips mid-sentence, accuracy on the "other" language drops sharply. Research on Hindi-English code-switched speech, including efforts to build dedicated code-switched corpora, exists precisely because off-the-shelf monolingual models handle it poorly. The failure lands exactly where medicine can't afford it: the English drug name embedded in a Hindi sentence, the lab abbreviation, the dose.

So "supports Hindi" on a vendor's page isn't the same as "handles a real Hinglish consult." Supporting Hindi audio is one thing. Supporting a doctor who says "BP thoda high hai, metformin continue rakhiye" is another problem entirely. We built for the second one.

## How do the global scribes compare on language?

| Scribe | Languages claimed | Indian languages named on public list | Note output language |
|---|---|---|---|
| **Freed** | "90+" on its multilingual page | None named (as of June 2026) | English |
| **eka.care (EkaScribe)** | 20+, India-native | Hindi + 10+ named (Bengali, Telugu, Tamil, Marathi, Gujarati, Kannada, Malayalam, Punjabi, Urdu and more) | English / structured |
| **AI Medical Scribe by Patient Square** | English + Hindi + 20+ Indian languages | Hindi, Tamil, Telugu, Bengali, Marathi, Gujarati, Kannada, Malayalam, Punjabi and more, with code-mixing auto-detected | Clean clinical English |

A fair word on the others: eka.care genuinely names a deep list of Indian languages. It's India-native and credible on this axis, and if you want a closer look the [India scribe comparison](../india-ai-scribe-comparison/) lays us side by side. The global vendors are the real mismatch. A page claiming "90+ languages" that names not one Indian language is borrowing authority it hasn't earned for an Indian consult.

## Why this matters in a two-minute OPD

A BMJ Open review covering 28.5 million consultations across 67 countries put India's average primary-care consultation at about two minutes, among the shortest measured anywhere. At one government super-speciality hospital, several OPDs each saw more than 200 patients a day. There is no version of that day where you also type a structured English note from a Hindi conversation. Either the record gets written by something that listens while you work, or it doesn't get written well.

For clinics where the internet is unreliable, capture works offline with on-device encryption and syncs later, so a power cut or a dead connection doesn't cost you the note. Live consultation audio is processed in memory and discarded once the note is drafted, which is also the right answer under the [DPDP Act](../dpdp-act-clinics-guide/). Uploaded recordings use a separate retention mode with explicit consent. The full posture is on our [security page](../../security/).

Evaluate language handling with representative accents and code-mixed phrases, then read the English notes for meaning and prescription accuracy. The [India rate card](../ai-medical-scribe-price-india/) distinguishes ex-GST and with-GST amounts when you compare costs.

---

## What Is an AI Medical Scribe? How It Works in 2026
https://patientsquare.com/us/blog/what-is-an-ai-medical-scribe/
Published 2026-04-02 · Updated 2026-07-22 · Tags: ai-scribe, ambient-documentation, basics

How AI medical scribes turn visit audio into a structured note, what they cost, and the questions to ask before you trust one with your charts.

No. A human scribe is a person in the room (or on a call) typing while you work, at a salary. An AI medical scribe is software that listens to the visit, transcribes it, and drafts the structured note itself. You pay a monthly subscription, typically a tenth of the cost.

An AI medical scribe is software that listens to a clinical visit and writes the note for you. It transcribes the conversation, pulls out the clinically relevant parts, and drafts structured documentation, usually a SOAP note, that you review and sign. No keyboard during the visit, no chart waiting for you at 9pm.

That's the short answer. The longer answer is worth ten minutes, because the products sold under this label differ in ways that matter clinically: what they do with your audio, which languages they understand, what they draft beyond the note, and what "review" actually means when you're 14 patients deep on a Tuesday.

> **Key takeaways**
>
> - An AI scribe converts visit audio into a draft note. You stay the author; it does the typing.
> - Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit. The note now outlasts the appointment it describes.
> - Published US pricing runs roughly $39–$199 per clinician per month, and several big vendors publish nothing at all.
> - The two questions that separate vendors fastest: what happens to the audio, and how honest the vendor is about what the tool can't do.

## How does an AI medical scribe actually work?

Four steps, all of them during or right after the visit.

First it listens. You start a session on your phone or laptop, get the patient's consent, and see the patient like normal. The scribe captures the conversation ambiently. Nobody dictates anything.

Then it transcribes. Speech becomes text. The good systems handle two speakers, interruptions, and the way real consultations loop back on themselves. The genuinely hard version of this problem is a crowded room with a relative answering half the questions and a thick accent the model has never heard. More on that below.

Next it structures the transcript. A language model turns it into clinical documentation: subjective, objective, assessment, plan. This is the step where products diverge. Some stop at the note. Others draft the downstream artifacts too, and AI Medical Scribe by Patient Square also returns ICD-10 suggestions and a prescription draft with the SOAP note.

Then you review and sign. The draft appears about two minutes after the visit ends. You read it, fix what needs fixing, and sign. Nothing enters the record without you.

The honest framing: this is a very fast, very patient junior scribe with perfect recall of the last conversation, not a colleague. It drafts. You decide.

Does the four-step loop hold up outside a demo? The largest real-world read so far says yes. The Permanente Medical Group ran ambient AI scribes across 7,260 physicians and 2,576,627 patient encounters over 63 weeks (October 2023 to December 2024), and reported an estimated 15,791 hours of documentation time recovered, roughly 1,794 eight-hour workdays, in results published in NEJM Catalyst and summarized by the AMA. Eighty-four percent of those physicians said the tool improved how they communicated with patients, and 47% of patients noticed their doctor spending less time on the computer. That's not a pilot with 30 friendly users. It's a deployment at the scale of a large medical group, and it's the kind of evidence worth weighing before you trust any product with your charts.

## What does an AI scribe hand back after the visit?

Baseline, every credible product: a structured note. Beyond that, read the feature list carefully, because the word "scribe" covers a wide range.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription is a draft built from the plan you stated in the room; you review the drugs, doses, and instructions and sign. It doesn't run an automated interaction or dosing check, and it never goes to a pharmacy on its own. We're deliberate about that boundary: a draft an LLM wrote is still a draft an LLM wrote, so the clinician stays the safety check, exactly as with a script written by hand.

Things some vendors include that we currently don't: after-visit patient summaries, referral letters, per-specialty note templates, and direct EHR write-back. If those are must-haves for your workflow today, weigh that honestly. Our [pricing page](../../pricing/) lists exactly what ships now.

## AI scribe vs human scribe vs dictation: what's the difference?

| | Human scribe | Dictation software | Ambient AI scribe |
|---|---|---|---|
| **Who does the work** | A person, in the room or remote | You, after the visit | Software, during the visit |
| **Your time per note** | Review only | 5–10 min of speaking + cleanup | ~2 min review |
| **Cost shape** | A salary (plus hiring, training, turnover) | Low subscription | $39–$199/mo, flat per clinician |
| **Captures the visit itself** | Yes | No, you reconstruct it from memory | Yes |
| **Patient in the room** | A third person present | Just you | Just you and a phone |
| **Scales to a group practice** | Linearly, painfully | Per clinician | Per clinician, flat |

Dictation was the first wave: it moved typing to talking, but you still spent evenings narrating visits you'd already done once. Human scribes solve the time problem and create a staffing one. Ambient AI is the first version where the documentation happens while the medicine happens.

## What happens to the visit audio?

Ask this before you ask about price. Seriously.

A visit recording is among the most sensitive artifacts in healthcare. It's more revealing than the note, because it contains everything that didn't make the note. Vendors handle it very differently. Some retain audio for days or weeks for model improvement or dispute resolution. Some let you opt out. Some are vague.

Our position: visit audio is processed in memory and discarded the moment the note is drafted. There is no audio archive, not for us, not for the practice, not for anyone. What survives is the note you reviewed and signed. Notes are encrypted in transit (TLS 1.2+) and at rest (AES-256), they belong to your practice, and you can export or delete any visit at any time. The full posture is on our [security page](../../security/).

The floor for any vendor is a signed BAA, plus encryption in transit and at rest and access you can audit. A vendor who can't answer "where does the audio live and for how long" in one sentence has answered the question.

## How much does an AI medical scribe cost in 2026?

From published pricing pages (fetched June 2026):

- Self-serve band: Freed runs $39–$119 per month across its tiers depending on billing; Commure Scribe lists $59–$89; Twofold $49–$69; Sunoh lists $149 promotional ($199 regular).
- The opaque tier: several large vendors (Suki, DeepScribe, Nabla) publish no pricing at all and route you to sales. You get a quote, not a list price.
- Patient Square's Practice Copilot starts from $79/clinician/month on annual billing (the Assist plan); Copilot ($119) adds a bundled AI EHR and messaging, and Autopilot ($199) adds an AI receptionist and follow-ups. Month-to-month and committed-annual rates are on the [pricing page](../../pricing/). An assisted 7-day trial is available at each tier after workspace setup.

One opinion, stated as one: we think pricing pages that say "talk to sales" for a per-clinician software subscription tell you something about how the renewal conversation will go. Transparent list pricing keeps vendors honest, including us.

Does the subscription pay for itself? The arithmetic is short. Primary-care physicians in a 2023 JAMA Network Open study logged a median of 36.2 minutes of EHR time per 30-minute visit, and an earlier time-motion study in Annals of Internal Medicine found nearly two hours of EHR and desk work for every hour of direct patient care, plus another one to two hours of after-hours "pajama time" most nights. Recovering even a fraction of that against a $79 monthly line item isn't a close call. Still, run the numbers for your own visit volume, not ours.

## Where do AI scribes still fall short?

Anyone selling you perfection is selling. The failure modes worth knowing:

Noisy, multi-speaker rooms. A quiet consult room is the easy case. A crowded clinic with a caregiver answering half the questions, or a pediatric visit with a parent in the room, is the real test, and transcription quality varies sharply across products there.

Language is the other big one. "Multilingual" without a named list is marketing. Read any vendor's language list literally and test it on your own patients during a trial, because accents and code-switching are where models quietly break. We capture English and more languages, with notes always returned in clean clinical English, and in low-connectivity settings capture works offline with on-device encryption and syncs later.

Drafts contain errors, too. Models mishear drug names, compress two complaints into one, occasionally write something plausible that didn't happen. This is why the review-and-sign step is load-bearing, why we treat the clinician as the safety check on every Rx draft rather than an automated screen, and why you should distrust any vendor whose pitch implies you can skip reading the note.

And the chart is yours, legally. No scribe, silicon or human, moves the documentation responsibility off the signing clinician. A tool that writes a complete record at the pace of the visit is the difference between signing at 6pm and signing in bed, and between a defensible chart and a backlog you'll be answering for later.

## Five questions to ask before you sign with any vendor

1. "What happens to the visit audio, and when is it deleted?" Accept only a one-sentence answer with a timeline. Ours: processed in memory, discarded at note draft.
2. "Will you sign a BAA?" Vague answers here are disqualifying. So is anyone implying they're "HIPAA certified," because no such certificate exists.
3. "What exactly is in the draft: note only, or codes and prescriptions too? What checks them?" Make the demo show a wrong drug pairing and watch what happens.
4. "What does my actual patient mix sound like to your model?" Test with your accents, your languages, your interruptions, during a free trial, on day one, not after procurement.
5. "What's the price after year one?" Launch rates, annual commitments, and month-to-month rates differ. Get the whole ladder in writing. Ours is published.

A scribe that survives those five questions will probably survive your Tuesday clinic. Review the [product workflow](/us/products/practice-copilot/) and read every draft closely during any approved evaluation. That's the evaluation that matters, and it costs you nothing but the week.

---

## DPDP Act for Doctors: What It Means for Your Clinic
https://patientsquare.com/in/blog/dpdp-act-explained-doctors/
Published 2026-04-01 · Updated 2026-10-04 · Tags: dpdp, compliance, india, privacy

A doctor-readable DPDP Act checklist: what the law asks of your clinic, the May 2027 deadline, the penalty tiers, and the questions to put to any AI vendor.

It makes your clinic a Data Fiduciary the moment patient data goes digital. You owe patients consent, purpose limitation, security, breach reporting, and the right to see, correct, or erase their data. Practice size does not exempt you. The duties are operational, not just paperwork, and most take effect by 13 May 2027.

For a practising doctor, the DPDP Act means one thing above all: the moment your patient records go digital, your clinic becomes a "Data Fiduciary" with real legal duties, and most of them take effect by 13 May 2027. You owe patients proper consent, tight purpose limits, security, breach reporting, and the right to see or delete their data. This is the doctor's version, not the law firm's. What you have to do, what a slip costs, and the questions to ask any software you buy.

> **Key takeaways**
>
> - DPDP makes your clinic a Data Fiduciary the instant patient data is digital. No size exemption, no lighter tier for a two-doctor practice.
> - The deadline that matters is 13 May 2027, when the bulk obligations switch on. The Consent Manager framework lands earlier, on 13 November 2026.
> - Penalties are statutory ceilings, not automatic fines, and reach up to ₹250 crore for failure to take reasonable safeguards to prevent a breach.
> - Your record-retention floor is unchanged: three years for inpatient records, from the operative 2002 medical-council rules, not from DPDP.
> - Every software purchase is now a compliance decision. The right vendor questions are four, and they are short.

_Sources: PIB / MeitY DPDP Rules 2025; PRS India on the DPDP Act 2023 Schedule; NMC Code of Medical Ethics 2002._

This is reporting, not legal advice, and the Data Protection Board is still building its machinery. Treat the list below as the shortlist worth confirming with your counsel, not a substitute for them. Want the full obligation primer, written for clinic owners? Our [DPDP Act for clinics guide](../dpdp-act-clinics-guide/) walks each duty in detail. This page is the doctor-facing version: shorter, organised by what you actually do.

## Is my clinic really covered by the DPDP Act?

Yes, and the size of your practice has nothing to do with it. The Act applies to any "Data Fiduciary," which it defines as any person who, alone or with others, decides the purpose and means of processing personal data. A solo GP keeping digital records is making exactly those decisions. So is a two-doctor clinic on a shared EMR. There is no carve-out for small practices, and if anything the sensitivity of health data raises the stakes rather than lowering them.

What flips the switch is digitisation. Paper-only files sit outside the Act's core machinery. The moment patient data goes digital, the duties attach, and "digital" is broad here: an EMR, a billing tool, the clinic WhatsApp number, an AI scribe. If it holds patient data and runs on a screen, it counts.

## What does the DPDP Act actually ask a doctor to do?

Here is the checklist, organised by the action, not the legal clause. None of it is exotic. Most of it is good clinical record-keeping with a consent layer on top.

| Obligation | What it means at the front desk | Who it falls on |
|---|---|---|
| **Take consent properly** | Collect data on free, specific, informed, unambiguous consent, after a plain notice saying what you collect and why. No bundled, take-it-or-leave-it checkbox. | The clinic |
| **Stick to the stated purpose** | Data gathered for treatment is not a marketing list or a referral-selling list. | The clinic |
| **Keep reasonable security** | Encryption, access control, logging. This duty carries the biggest penalty, which tells you what the law cares about most. | The clinic + every vendor |
| **Report a breach** | Tell affected patients and the Data Protection Board without delay, then file a detailed report to the Board within 72 hours. | The clinic |
| **Honour patient rights** | A patient can ask what you hold, fix it, or have it erased. Publish a grievance route and answer within 90 days. | The clinic |
| **Vet your vendors** | Hand data to a processor and their handling becomes your liability. Diligence is not optional. | The clinic |

The one that catches doctors off guard is the last. Buying software used to be an IT decision. Under DPDP it is a fiduciary one, because whatever your scribe or your billing host does with patient data, the exposure lands on you. We come back to that below, because it is where a good buying decision saves you the most work. If you are already vetting a scribe, <a href="/in/security/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">review the security details</a> and put your data-handling questions to it directly.

## The deadline that matters is 13 May 2027

The date to circle is 13 May 2027. That is when the obligations that reshape how a clinic handles data actually bite. The runway started on 13 November 2025, when the DPDP Rules were notified, but the Rules switch on in waves rather than all at once.

_Source: SCC Online and PIB / MeitY on the DPDP Rules 2025 phased commencement._

The remaining time before 13 May 2027 is for building a consent notice your front desk can use, rehearsing a breach process, and checking vendor contracts. Clinics that use 2026 to get consent, security, and procurement in order will have a clearer path into 2027. If you want the obligation-by-obligation calendar with the exact rule numbers, our [DPDP Rules 2025 timeline](../dpdp-rules-2025-clinic-timeline/) lays out which provision lands when.

## What are the DPDP penalties for a clinic?

Large, tiered, and discretionary. The Act's Schedule sets statutory ceilings that the Data Protection Board applies case by case. There is no minimum, no automatic fine, and the Board weighs the conduct before it lands on a number.

Read the chart for its shape, not its top number. No clinic should expect a ₹250 crore demand. What the figures tell you is priority. The biggest ceiling sits on the security-safeguards duty, which is the law signalling, in the bluntest way it can, that protecting the data is the obligation it takes most seriously. The breach-reporting and children's-data duties share the next tier. Everything else falls under the residual ceiling. Spend your attention where the law spends its biggest number: on holding the data safely.

## DPDP doesn't change how long you keep records

No, it doesn't, and this is the point most coverage gets muddled, so here it is straight. Your retention floor still comes from the medical-council rules, not from DPDP. The Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations 2002 are the live rules. Under Regulation 1.3 you keep inpatient records three years from the start of treatment and produce any record within 72 hours of a request.

The catch is the regulation people quote. The NMC's 2023 conduct regulations restated this and proposed tighter timelines, but they were held in abeyance in August 2023 and never commenced. So when you cite "three years," cite the 2002 rules, the ones actually in force, not the 2023 ones a lot of blog posts treat as law.

_Sources: NMC Code of Medical Ethics 2002, Regulation 1.3; SCC Online on the DPDP Rules 2025 grievance window._

The two regimes pull the same way. MCI 2002 sets your retention floor and your duty to produce a record on request. On top of that, DPDP wants consent, purpose limitation, security, and deletion once the treatment purpose has run its course. So a complete, retrievable note satisfies both at once, which is also why a thin or missing one is a liability under either. One thing you do not carry: the time-bound deletion clock in the DPDP Rules targets large platforms like e-commerce and social media above set user thresholds, not a clinic. Your retention is governed by purpose plus the medical-council rule. The retention question deserves its own sitting with counsel; this is the short version.

## What should I ask an AI scribe or any health-tech vendor?

Since every software purchase is now a fiduciary decision, the vendor's data handling becomes your exposure. Four questions do most of the filtering. Ask them out loud and listen for whether the answer comes back in a sentence or a fog.

- **"What patient data do you collect, and where is it stored?"** Without the data map you cannot honour purpose limitation or answer a patient request.
- **"How long do you keep it, and can I delete any record on demand?"** Deletion once the purpose ends is a DPDP duty, so the vendor has to support it, not resist it.
- **"Is visit audio stored, and for how long?"** Stored audio is about the most sensitive thing a clinic can hold. A vendor that processes audio in memory and never keeps it takes a whole risk category off your books.
- **"Is my patients' data used for anything beyond my care, like model training, analytics, or resale?"** This is where purpose limitation lives or dies.

The AI Medical Scribe is one module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. We built it so those four answers come back short. Visit audio is processed in memory and discarded the moment the note is drafted, so there is no audio archive to breach or to produce. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256), access is role-scoped and logged, and you can export or delete any visit at any time. We never sell or share clinical data. We describe this as handling data to DPDP Act 2023 standards, consent-first and purpose-limited, and we deliberately do not call it a certification, because a DPDP certification for vendors does not exist. A SOC 2 Type II audit is underway, that phrase exactly, and ABDM integration is on our roadmap, not live, so we never claim otherwise. The full posture, in the same plain terms, sits on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Two more things doctors ask us. The scribe hands you an EHR-ready export (PDF, HL7, FHIR), so it does not lock you into one records system, and Practice Copilot also bundles its own AI EHR from the Copilot plan up if you want the record inside the same tool. And the price is published per clinician: in India, the entry Assist plan is ₹1,599 per clinician a month on annual billing, ex-GST, plus 18% GST, so a seat lands at about ₹1,887 a month all in. The Copilot plan at ₹2,399 adds the bundled AI EHR and WhatsApp messaging, and Autopilot at ₹3,999 adds an AI receptionist and follow-ups. You read the number before you talk to anyone.

If you operate across borders, our [HIPAA vs DPDP guide for AI scribes](../ai-scribe-hipaa-vs-dpdp/) puts both regimes side by side. Read the [security details](/in/security/) and ask the four questions above. Live consultation audio is processed in memory and discarded; uploaded recordings use a separate retention mode with explicit consent. Confirm which mode you are using and how notes and other retained patient data are protected.

---

## Using an AI Medical Scribe With Epic: Export and Limits
https://patientsquare.com/us/blog/ai-scribe-for-epic/
Published 2026-03-31 · Updated 2026-07-22 · Tags: ai-scribe, epic, ehr, workflow

How a standalone ambient AI scribe works alongside Epic: you paste or import the finished note, the honest limits, and when Epic's own AI Charting fits better.

A standalone ambient scribe works alongside Epic without connecting to it. It captures the visit on your phone or laptop, drafts the note, and you paste or import the finished text into the Epic chart. It does not file into Epic by itself. There is no live Epic API connection on our side, by design.

Yes, a standalone AI scribe works with Epic, but not the way the word "integration" implies. It captures the visit on its own, drafts the note, and you paste or import the finished text into the Epic chart. It does not write into Epic by itself. There's no Epic API on our side, and that's a deliberate design choice, not a missing feature.

If you came here hoping for a tool that files notes straight into Epic, read the next two paragraphs carefully, because that's not what a standalone scribe is. What it is, and why some practices on Epic prefer it anyway, is the rest of this page.

> **Key takeaways**
>
> - A standalone scribe works *alongside* Epic. You copy the finished note in, or export it. It does not auto-file into the chart.
> - There is no Epic API, no HL7 or FHIR write-back, no bidirectional sync on our side. We say so plainly because the alternative is a lie you'd catch in week one.
> - Epic shipped its own built-in scribe, AI Charting, in February 2026. For an all-Epic practice, that's the obvious first thing to try.
> - A standalone earns its place when you also work off Epic, see patients in more than one language, or want a checked prescription draft and ICD-10 suggestions.
> - The trade is exact: you give up automatic write-back, you get a tool that isn't chained to one EHR.

## Does an AI scribe actually work with Epic?

Short version: it works *near* Epic, not *inside* it.

A standalone ambient scribe is software that listens to the visit and writes the note. It runs on your phone or laptop, separate from the EHR. When the note is ready, you move it into Epic the same way you'd move any text: select, copy, paste into the encounter. Some teams export the note as a file and import it instead. Either way, the scribe never touches Epic directly.

This is a real, common category. In the ambient-scribe market, the tools that do exactly this have a name: paste-window vendors. The app generates the note in a sidebar or its own window, and the clinician pastes it into the open chart. It's the standard pattern for EHR-agnostic scribes that aren't wired into a hospital's IT stack. AI Medical Scribe by Patient Square is one of them, and we're not going to dress that up as something fancier.

The thing it buys you is independence. The scribe doesn't care whether you're in Epic, in another EHR, or writing into a flowsheet you keep yourself. It captures the visit and hands back the note regardless. For a clinician who works across more than one system, or who might switch EHRs someday, that matters more than it sounds like it should.

## What the scribe hands back, and what you do with it

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. That's the output. Here's the Epic part.

The note arrives as clean, structured text: subjective, objective, assessment, plan. You read it, fix what needs fixing, and paste the finished version into the Epic encounter. The ICD-10 suggestions come alongside, so the codes you'd be hunting for are already in front of you. They're suggestions, not a coding engine, and not anything that touches your E/M level. You stay the one who decides.

The prescription draft reflects what you said in the visit, the drug, the dose, the instructions, written out so you don't retype it. It doesn't screen for interactions or dosing, and it doesn't decide anything. You are the safety check, exactly as you are today: you read the draft against the patient's chart, adjust what needs adjusting, and sign. A draft an LLM wrote is still a draft an LLM wrote. None of it files into Epic on its own, and none of it reaches a pharmacy. You review, you sign, you act.

One more thing that happens away from Epic: the visit audio. It's processed in memory and discarded the moment the note is drafted. No archive, not for us, not for the practice. What survives is the note you reviewed and pasted in. The full posture is on our [security page](../../security/).

## Why isn't there an Epic integration? The honest answer

Because we don't have one, and building a fake one into the marketing copy is how you lose a clinic in the first week.

Here's what a deeper Epic integration actually involves. A vendor that pushes notes straight into the chart has to register its app through Epic's own app-integration program and build an API connection that Epic vets. That's the difference between "the note appears in the chart automatically" and "you paste the note in." The first one is real engineering and a real Epic relationship. We don't do it. We do the second one.

So when another scribe advertises "Epic integration," ask which kind. Push-into-the-chart via an Epic-vetted API connection is a genuine capability. A paste window is a different thing wearing the same word. Both are legitimate; they're just not the same product, and the price and the lock-in differ.

We chose the standalone path on purpose. The cost is the copy-paste step. The benefit is that the scribe works with any EHR or none, your notes belong to your practice, and you can export or delete any visit at any time without asking a vendor's integration team for help. For an independent practice, that trade usually comes out in favor of independence. For a large health system that wants the note in the chart with zero clicks, it doesn't, and we'll get to that.

## Standalone scribe with Epic vs. Epic's own AI Charting

In February 2026, Epic released its own built-in ambient scribe, AI Charting. That changed the question for anyone on Epic, so let's put the two side by side honestly.

| | Standalone scribe with Epic (ours) | Epic AI Charting (built-in) |
|---|---|---|
| **How the note reaches the chart** | You paste or import it | Written into the chart automatically |
| **Works off Epic too** | Yes, EHR-agnostic | No, lives inside Epic |
| **Available without Epic** | Yes | No, Epic customers only |
| **Cost shape** | Published per-clinician price | Part of what you already pay Epic |
| **Prescription draft you review and sign** | Yes | Not the same scope |
| **ICD-10 suggestions** | Yes | Within Epic's own tooling |
| **Multilingual capture** | Yes, English plus more | Tuned for the US Epic base |
| **Audio retention** | Never stored, in-memory only | Per Epic's policy |

The native tool has one enormous advantage: the note lands in the chart with no copy-paste, and it's bundled into a system you already pay for. That's hard to beat on convenience and on price, because the marginal cost is close to zero. We're not going to argue otherwise.

What it doesn't do is leave Epic. If half your documentation happens somewhere else, a tool that only works inside Epic covers half your day. And the prescription draft you review and the multilingual capture aren't the native tool's job. That's the boundary.

If you want the full head-to-head, including when the free built-in tool is simply enough and you should stop reading vendor blogs, we wrote a dedicated comparison: [AI Medical Scribe vs Epic AI Charting](../ai-scribe-vs-epic-ai-charting/). This page is about working alongside Epic; that one is about choosing between the two.

## When Epic's built-in tool is the better fit

Here's the verdict, no hedging, because the honest version is the useful one.

Use Epic AI Charting if your practice lives entirely inside Epic, every visit you document happens in Epic, you don't need a prescription draft from the scribe, and your patients speak the language your Epic build is tuned for. For a deep all-Epic enterprise with no off-Epic work, no telehealth documentation outside the system, and no multilingual case mix, the native tool's automatic write-back and near-zero marginal cost are exactly right. Paying a second vendor to also draft the note, then pasting that note in by hand, would be paying twice for less convenience. Don't do that.

Use a standalone scribe with Epic if any of these is true: you document visits outside Epic too, you want a prescription draft you review and sign, you see patients in more than one language, or you simply don't want your notes locked to one EHR's roadmap. Epic's 42% of the acute-hospital market, per STAT's February 2026 reporting, means most hospital beds run on it, but plenty of clinicians split their week across Epic and something else. For them, "works only inside Epic" is a real gap, and a standalone that travels is the tool that fits.

The mistake runs both ways. Buying a standalone when the native tool already covers your whole day is waste. Assuming the native tool covers you when a third of your visits happen off Epic, or end in a prescription you'd like checked, is a different kind of waste. Match the tool to how you actually work.

## How to decide in five minutes

1. Is every visit you document inside Epic? If yes, try Epic AI Charting first. It's already there and it's bundled. If no, you need a tool that works off Epic, which the native one doesn't.
2. Do you want the scribe to draft and safety-check prescriptions, or just write the note? Note-only leans native. Note-plus-prescription leans standalone.
3. What languages do your visits actually happen in? A US-tuned native tool may not cover a multilingual clinic. A standalone built for it does, with notes always returned in clinical English.
4. Where does the visit audio go, on whichever tool you pick? Ask both. Ours: processed in memory, discarded at note draft, no archive.
5. Can you live with a paste step in exchange for EHR independence? For most independent practices that's a fair trade. For a zero-click enterprise workflow, it isn't.

If you're leaning standalone, the way to settle it is to run one on your real visits, not on a demo script. Compare against your own Tuesday: your patients, your prescriptions, your languages, your copy-paste tolerance. For a wider look at how a tool fits any chart system, our [any-EHR export guide](../ai-scribe-any-ehr-export/) walks through the workflow across Epic, athenahealth, and the rest, and the [free-EHR-scribe versus standalone breakdown](../free-ehr-ai-scribe-vs-standalone/) covers the same fork for clinics on other systems. The full price ladder, no asterisks, is on the [pricing page](../../pricing/).

We'll make the cheap recommendation when it's right: if you're all-in on Epic and the built-in scribe covers your day, use it. If your work spills outside Epic, or your notes need more than a transcript, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and run the 7-day trial on a real clinic week. Then let the paste step, or the absence of one anywhere else, decide it for you.

---

## AI Medical Scribe vs Epic AI Charting: Is Built-In Enough?
https://patientsquare.com/us/blog/ai-scribe-vs-epic-ai-charting/
Published 2026-03-30 · Updated 2026-07-22 · Tags: ai-scribe, comparison, epic, ehr

Epic now drafts your note in-EHR. When the built-in tool is enough, when a standalone scribe earns its price, and an honest side-by-side fit guide.

For an Epic shop, it is a strong fit. Epic released AI Charting in early February 2026 as a built-in feature that drafts the note and queues orders from the visit conversation, inside the chart you already use. There is no second login and no copy-paste. The honest limit is that it lives in Epic, so it helps you only where your work runs in Epic.

If you run on Epic, Epic AI Charting is probably enough. Epic released it in early February 2026 as a built-in feature that listens during the visit, drafts the note, and queues orders, all inside the chart you already use. A standalone scribe only beats that when some of your work happens outside Epic: telehealth visits, a second EHR, a practice that is not on Epic, visits in another language, or a checked prescription draft you want alongside the note.

So this is a genuine fork, not a setup. Below: what the built-in Epic tool actually does, where a standalone picks up, and a plain fit guide that tells you which one you are.

> **Key takeaways**
>
> - Epic released AI Charting in early February 2026: a built-in feature that drafts the note and queues orders from the visit, inside Epic.
> - It lives in Epic. Roughly two-thirds of hospitals on Epic have adopted ambient AI, so the built-in tool is already the default for in-Epic work.
> - Epic has published no list price for it. Do not assume it is free; confirm bundled-versus-extra with your Epic rep in writing.
> - A standalone scribe trades automatic chart write-back for working off-Epic, on telehealth, and in more languages, plus a prescription draft you review and sign.
> - The deciding question: does all your work happen inside Epic, or does part of it happen somewhere Epic cannot reach?

## What does Epic AI Charting actually do?

Start with Epic's own words, because the vendor announcement is the source of truth here. Epic describes AI Charting as "a built-in feature that listens during patient visits, drafts the clinician's note, and queues up orders based on the conversation." It is part of Art, Epic's AI for clinicians, and it is built directly into Epic's software. Epic released it in early February 2026, and reporting at launch put adoption of ambient AI among Epic hospitals at roughly two-thirds.

The direction is bigger than a note. Epic's chief medical officer, Jackie Gerhart, told STAT News that a plain scribe "is passive. We really want this to be active," adding, "we're just going to keep adding more besides just notes. So it's going to be orders, it's going to be diagnoses." There is a real guardrail under that ambition: per Healthcare Dive, clinicians must review and approve every drafted note and order before it is placed, and Epic watches how often clinicians edit the draft to catch mistakes.

For an Epic clinician, that is a strong deal. The tool lives where you already work. No second login, no copy-paste, no separate invoice to chase. If your whole day runs inside Epic and your main pain is that the note takes too long, a built-in note-and-orders drafter solves the actual problem. We are not going to pretend it doesn't. The interesting question is the edge of it: what happens when part of your work isn't in Epic? If that edge is where you live, book a demo and watch a standalone pick up exactly where the built-in tool stops.

## Is Epic AI Charting free? What the pricing actually is

Short answer: nobody outside an Epic contract knows, so don't budget around "free."

Epic has not published a list price for AI Charting. Coverage at launch carried no dollar figure, and Epic's own post stays quiet on cost. In practice that means whether the tool is bundled into your existing agreement or carries an added line depends on your specific Epic contract and your account team. That is normal for enterprise EHR features, and it is the opposite of how self-serve scribes price.

The practical move: ask your Epic representative whether AI Charting is included or extra, at what scope, and get it in writing before you treat it as a zero on the budget. "Built-in" and "no added cost" are not the same sentence, and only your contract settles which one applies to you.

## Where does a standalone AI scribe pick up?

A standalone scribe charges money, so it has to earn the line. Here is where the price goes, and every one of these is something a built-in Epic tool can't reach by design, because it only runs inside Epic.

It works with any EHR, or none. This is the whole point of "standalone." The AI Medical Scribe is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. You copy the finished note into whatever chart you keep. If you run two EHRs, switch systems, or aren't on Epic at all, that independence is the difference between having a scribe and not.

It documents telehealth the same way. A built-in EHR scribe is tuned for the in-person, in-chart encounter. A standalone captures the visit from the device near you, so a video consult gets documented like any other. The consent rule changes for telehealth, and that's worth getting right, but the capture doesn't care which room you're in.

It handles more than one language. A US-tuned EHR scribe is built for a US-English patient base. A standalone built for multilingual work captures visits in English, Hindi, and more than twenty Indian languages, including the mid-sentence code-mixing real patients use, and returns the note in clean clinical English. For a practice whose patients don't all speak English, that is a daily gap, not an edge case.

It drafts the prescription. A note describes the visit; the prescription draft starts the next action, mirroring the plan you dictated so you review a filled-in Rx instead of a blank field. It stays a draft you check and sign, and the interaction, dosing, and contraindication screen is yours to run, exactly as you run it today. A note-only tool stops before any prescription draft at all.

And the audio is gone the moment the note exists. Visit audio is processed in memory and discarded once the note is drafted. There is no audio archive, not for us, not for the practice. What survives is the note you reviewed and signed.

## The honest trade: what a standalone gives up

This cuts against us too, so let's say it plainly. We export; we do not integrate. A built-in Epic tool writes the draft straight into the Epic chart. With a standalone, you paste the finished note in by hand. For a solo clinic that's a few seconds per visit. For a clinician who values automatic write-back above everything else, the built-in option wins on that one axis, and we'll say so.

ICD-10 is suggestions, not a coding engine. We surface likely codes to speed the work you'd do anyway; we don't auto-set your E/M level or run a billing engine. The prescription is a draft, not e-prescribing, no pharmacy gateway. On our compliance posture: we maintain HIPAA compliant safeguards, sign a BAA with every US customer, and have a SOC 2 Type II audit underway, not finished. We're not going to round any of that up.

If your honest answer is "everything I do happens inside Epic, and write-back is the feature I care about most," the built-in tool is the rational pick. Keep reading only if part of your day lives somewhere Epic doesn't.

## Epic AI Charting vs a standalone scribe: a side-by-side

Lay them next to each other on what each can actually do, not on adjectives.

| Capability | Epic AI Charting (built-in) | Standalone scribe (ours) |
|---|---|---|
| Drafts the visit note | Yes | Yes |
| Writes the draft into the chart automatically | Yes, inside Epic | No, you copy the note in |
| Works with any EHR, or none | No, Epic only | Yes, EHR-agnostic |
| Available without an Epic contract | No | Yes |
| Documents a telehealth visit | Built for the in-Epic encounter | Yes, captures from the device near you |
| Multilingual and code-mixed capture | Tuned for a US-English base | Yes, English plus 20+ Indian languages, English note out |
| Prescription draft you review and sign | Queues orders inside Epic | Yes, draft mirrors the visit; clinician screens and signs |
| Published price you can read up front | Not disclosed; ask your Epic rep | Published, any practice size |
| Visit audio you can account for | Per Epic's terms | Never stored, in-memory only |

Read that table the right way. Epic AI Charting isn't weak at the rows it skips; it isn't built for them, because it's built into Epic. If those rows are blank for your work too, the built-in tool is the right call and a standalone on top would be paying twice for the note. If three or four of them are must-haves, the standalone's price buys reach a native tool structurally can't offer. The fastest way to know which describes you is to book a demo and watch a standalone document one of your real visit types, prescription draft included.

## When is Epic AI Charting the better fit?

Here's the verdict, no hedging, because being straight about this is the point.

Use Epic AI Charting if you're an all-Epic shop, your visits run inside Epic start to finish, you don't take telehealth on a separate platform, your patients are mostly English-speaking, and note-and-orders drafting is the thing you want off your plate. Native, in-chart, with automatic write-back is hard to beat for that profile. A standalone would be a second tool solving a problem you've just told yourself you don't have. Don't buy it.

Use a standalone if part of your work happens where Epic can't follow. You're not on Epic, or you run more than one EHR. You see patients on telehealth. Your patients don't all speak English. You want the prescription draft you review and sign, not just a note. Or you simply don't want your documentation chained to one vendor's ecosystem. For an independent practice, a multi-EHR group, a telehealth-heavy clinic, or a multilingual patient mix, a standalone isn't a luxury on top of Epic. It's the tool that fits the work Epic's built-in one was never going to reach.

The mistake runs both ways: bolting a standalone onto Epic when the built-in tool already covers you, or assuming the built-in tool covers you when a third of your visits are on video, in another language, or in a chart that isn't Epic. Match the tool to where the work actually happens.

## The arithmetic, briefly

Either way, the documentation burden is real. In a 2023 JAMA Network Open study, primary-care physicians logged a median of about 36 minutes of EHR time per 30-minute visit. The note now outlasts the appointment it describes. That's the burden the whole ambient-scribe category, Epic's tool and ours alike, exists to cut.

So the question isn't whether ambient documentation is worth it. It is. The question is which shape fits your practice: the one welded into Epic, or the one that travels with you across every EHR, every telehealth call, and every language your patients bring. Run the numbers for your own visit volume, not ours.

## How to decide without overthinking it

1. Map where your visits happen. All inside Epic? Lean built-in. Some on telehealth, another EHR, or no EHR? You need a standalone, and the question answers itself.
2. List what you want automated. Just the note? The built-in tool is strong. Note plus a checked prescription, ICD-10 suggestions, or multilingual capture? That's standalone territory.
3. Get Epic's price in writing. "Built-in" isn't "free." Ask your Epic rep whether AI Charting is bundled or extra before you compare line items.
4. Check the audio policy on both. Ask where the visit audio lives and for how long. Ours: never stored, processed in memory and discarded at note draft.
5. If you're leaning standalone, trial it on real visits, so you're comparing your actual workflow, not a demo.

If you want the wider field, our [best AI medical scribes comparison](../best-ai-medical-scribes/) covers the self-serve market, and if your EHR is athenahealth rather than Epic, [the free-EHR-scribe versus standalone breakdown](../free-ehr-ai-scribe-vs-standalone/) runs the same fork for athenaAmbient. The two pages that pair with this one: [an AI scribe that works with any EHR](../ai-scribe-any-ehr-export/), and [using a standalone scribe alongside Epic by export](../ai-scribe-for-epic/). The full price ladder, no asterisks, is on the [pricing page](../../pricing/).

We'll make the cheap recommendation when it's the right one: if your work lives entirely in Epic and the built-in tool covers it, use it. If it doesn't, book a short demo and run the 7-day trial on a real clinic week, then let the gap, or the absence of one, decide for you.

---

## DPDP Act for Clinics: What Doctors Must Do in 2026
https://patientsquare.com/in/blog/dpdp-act-clinics-guide/
Published 2026-03-30 · Tags: dpdp, compliance, privacy, india

A practical guide to the DPDP Act 2023 for Indian clinics: consent, retention, breach duties, penalties, and what to ask any health-tech vendor.

Yes. The DPDP Act 2023 applies to anyone who decides how and why personal data is processed. That includes a two-doctor clinic handling patient records digitally. Size doesn't exempt you; you are a Data Fiduciary with obligations around consent, purpose limitation, security, and breach notification.

The DPDP Act 2023 turns every Indian clinic that handles patient data into a Data Fiduciary with real legal duties, and with the DPDP Rules notified in November 2025, the compliance clock is now running. This is written for clinic owners and doctors, not lawyers. It covers what the law asks of you, what a slip can cost, and the questions to put to any software you buy. Not legal advice. Confirm the specifics with counsel. What it gives you is the shortlist of things worth confirming.

> **Key takeaways**
>
> - The DPDP Act applies to clinics of any size; you are a "Data Fiduciary" the moment you decide how patient data is used.
> - The DPDP Rules were notified on 14 November 2025, with most obligations phasing in over roughly 18 months. The window is open now.
> - Penalties reach up to ₹250 crore for security-safeguard failures that lead to a breach.
> - Every software purchase is now a fiduciary decision; the right vendor questions are short and specific.

_Source: PIB / MeitY, DPDP Rules 2025 backgrounder, November 2025._

## Does the DPDP Act actually apply to my clinic?

Yes. Practice size has nothing to do with it. The Digital Personal Data Protection Act, enacted on 11 August 2023, applies to any "Data Fiduciary": the person or organization that determines the purpose and means of processing personal data. A two-doctor clinic keeping digital patient records is deciding why and how that data gets handled, and that makes it a Data Fiduciary with obligations. There's no lighter tier for health data. If anything the sensitivity of it raises the stakes.

What flips the switch is digitization. Paper-only records sit outside the Act's core machinery. But the moment patient data goes digital, DPDP duties attach, and "digital" is a broad word here: an EMR, a billing system, a WhatsApp number, an AI scribe.

## When do I actually have to comply?

Now. The DPDP Rules, 2025 were notified on 14 November 2025, and most substantive obligations phase in over roughly an 18-month window from notification. Enforcement isn't retrospective to 2023, so nobody's coming after old records. But the runway is finite and it has already started ticking. Clinics that use 2026 to get consent, security, and vendor contracts in order are the ones who won't be scrambling when the obligations actually bite.

Don't wait for a notice from the Data Protection Board. Compliance is cheapest when you build it before anyone asks for it.

## What does DPDP actually require a clinic to do?

Six duties, in plain terms:

1. Take consent properly. Collect patient data on the basis of consent that is free, specific, informed, and unambiguous, with a clear notice of what you're collecting and why. A handful of medical situations carry carve-outs. Consent is the default footing otherwise.
2. Stick to the purpose you stated. Patient data gathered for treatment isn't a marketing list.
3. Keep reasonable security safeguards: encryption, access control, logging, the appropriate technical and organizational measures. This is the duty with the largest penalty attached, which tells you how seriously the law takes it.
4. Report breaches. If a personal-data breach occurs, notify the Data Protection Board and affected individuals, in plain language, without delay.
5. Honor data-principal rights. Patients can ask what you hold, request correction, and request erasure, and you answer within the timelines the Rules set (within 90 days for certain requests).
6. Do your vendor diligence. Hand data to a processor, whether an EMR host, a scribe, or a billing service, and you stay responsible. Their handling is your liability.

## What are the penalties?

They are large and tiered. The DPDP Act's schedule sets statutory ceilings applied by the Data Protection Board:

| Failure | Penalty up to |
|---|---|
| Failure to maintain reasonable security safeguards leading to a breach | **₹250 crore** |
| Failure to notify a breach; breach of children's-data obligations | **₹200 crore** |
| Other violations | **₹50 crore** |

These are ceilings, not automatic fines, and the Board applies them case by case. No clinic should read this as "you will be fined ₹250 crore." Read it instead as a signal of priorities. The biggest number sits on the security-safeguards duty, which is the law's way of telling you that protecting the data is the obligation it cares about most.

## How does DPDP sit alongside medical record-keeping rules?

They stack rather than collide. DPDP governs how you handle data; the medical-council ethics rules govern what records you keep and for how long. There's a retention nuance a lot of guides get wrong, so here it is. The NMC's 2023 conduct regulations, which proposed three-year retention for all patients and records supplied within five working days, were held in abeyance shortly after notification. So they don't bind you. The rules actually in force are the older MCI 2002 ethics regulations: keep inpatient records three years from the start of treatment, produce records within 72 hours of a request, and treat a failure as professional misconduct.

Put together, MCI 2002 sets your retention floor and your production duty, and DPDP layers purpose-limitation, security, consent, and the duty to delete once the purpose ends on top. A complete, retrievable record serves both at once. It's also why thin or missing notes are a liability under either regime. (The retention rules deserve their own read with counsel; this is the short version.)

_Sources: NMC / MCI Code of Medical Ethics 2002; PIB / MeitY DPDP Rules 2025 backgrounder._

## What should I ask an AI scribe or health-tech vendor?

Every software purchase is now a fiduciary decision, because the vendor's handling becomes your exposure. Four questions settle most of it.

- "What patient data do you collect, and where is it stored?" Without the data map you can't honor purpose-limitation or answer a patient request.
- "How long do you retain it, and can I delete any record on demand?" Deletion once the purpose is done is a DPDP duty, so the vendor has to support it.
- "Is visit audio stored, and if so for how long?" Stored audio is about the most sensitive thing a clinic can hold. A vendor that processes audio in memory and never stores it takes a whole category of risk off your books.
- "Is my patients' data used for anything beyond my care, like model training, analytics, or resale?" This is where purpose-limitation lives or dies.

The AI Medical Scribe is one module of Practice Copilot from Patient Square: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. It's built so those four answers come out short. Visit audio is processed in memory and discarded the moment the note is drafted, so there is no audio archive. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256), access is role-scoped and logged, and you can export or delete any visit at any time. We call this handling data to DPDP Act 2023 standards, consent-first and purpose-limited, and we don't call it a certification, because a DPDP certification for vendors doesn't exist. The full posture, in the same plain terms, is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Procurement is one part of DPDP preparation; clinics also need consent, access, retention, and incident procedures. The [India scribe comparison](../india-ai-scribe-comparison/) provides a starting point for vendor questions. Check the [security details](/in/security/) against the workflow you intend to use: live consultation audio is processed in memory and discarded, while uploaded recordings use a separate retention mode with explicit consent. Notes and other retained patient data still need protection.

---

## AI Medical Scribe for Behavioral Health: Privacy First
https://patientsquare.com/us/blog/ai-scribe-for-behavioral-health/
Published 2026-03-27 · Tags: behavioral-health, therapy, counseling, privacy, compliance, 42-cfr-part-2

What 42 CFR Part 2 and HIPAA psychotherapy-notes rules mean for a therapy AI scribe, why stored audio is the risk, and when an ambient scribe is the wrong tool.

Only if your practice is a federally-assisted substance use disorder program. Part 2 covers records held by programs, including private practitioners, who hold themselves out as providing SUD diagnosis, treatment, or referral. A general therapy, counseling, or LCSW practice that is not such a program is governed by HIPAA, not Part 2. If you do SUD work, Part 2 layers on top.

Ask one question before you pick a behavioral-health scribe: what happens to the audio? In therapy the recording holds more than the note ever will, and a vendor that keeps it has made something a court can later reach. A scribe that never stores the recording removes that risk at the root. The compliance rules people worry about, 42 CFR Part 2 and HIPAA's psychotherapy-notes category, are narrower than most vendor pages let on. Stored audio is the part that's actually sharp.

This post is for the talk-therapy side of behavioral health: counselors, LCSWs, group practices, clinics. If you're an MD running medication management, the [psychiatry privacy guide](../ai-scribe-for-psychiatry-privacy/) covers your case more directly. Here we sort the rules that govern a therapy practice from the ones that don't, and we give you a decision tree to run any vendor through. Us included.

> **Key takeaways**
>
> - 42 CFR Part 2 covers substance use disorder records held by federally-assisted SUD programs. A general therapy or counseling practice that isn't one is governed by HIPAA.
> - HIPAA "psychotherapy notes" are your separate session-analysis notes. The progress note a scribe drafts is explicitly the excluded content, not a psychotherapy note.
> - Stored audio is protected health information and discoverable in litigation. Audio that's never kept can't be subpoenaed.
> - 93% of behavioral health workers reported burnout in a 2023 survey of 750; 68% of those in direct care said paperwork takes time from clients.
> - The deciding factor isn't a feature. It's the retention policy. Get a one-sentence answer with a deletion timeline.

## Which privacy rules actually govern a therapy practice?

Careful clinicians get talked into the wrong fear here. Vendor pages name-drop three regimes. Only some touch your practice.

HIPAA is the floor. It governs your protected health information, including the progress note the scribe writes, and it almost always applies to a licensed therapy or counseling practice.

42 CFR Part 2 is the one that gets misapplied most. It protects records of substance use disorder treatment held by a federally-assisted Part 2 "program." Under 42 CFR 2.12, that includes treatment programs, hospital units, and "private practitioners who hold themselves out as providing... substance use disorder diagnosis, treatment, or referral for treatment." Read that carefully. If you don't hold yourself out as an SUD program, Part 2 generally doesn't attach to your records, even when a client talks about drinking or drug use in session. So a counseling or LCSW practice that isn't an SUD program is usually a HIPAA practice, not a Part 2 one. Run an addiction program and Part 2 layers on, with stricter consent and disclosure rules. The 2024 Part 2 Final Rule, with a compliance date of February 16, 2026, brought much of Part 2 consent closer to HIPAA, so a single client consent can now cover future treatment, payment, and operations uses. It kept the hard protections: SUD records still can't be used to start or back a criminal charge against the patient, and disclosure in a legal proceeding needs patient consent or a court order plus a subpoena, not a plain subpoena alone.

Psychotherapy notes are a HIPAA category, and this is where the scribe question actually turns. HIPAA defines them as "notes recorded (in any medium) by a health care provider who is a mental health professional documenting or analyzing the contents of conversation during a private counseling session," kept separate from the rest of the record (45 CFR 164.501). Those get heightened protection: you need a specific authorization to disclose them (45 CFR 164.508(a)(2)). But the same definition spells out what is not a psychotherapy note, and the list is long: the medication record, session start and stop times, treatment modalities and frequencies, clinical test results, and any summary of diagnosis, functional status, treatment plan, symptoms, prognosis, and progress. That list is the progress note. It's the thing a scribe drafts. So the scribe's output is protected by HIPAA, but it is not a psychotherapy note, and it doesn't get the heightened authorization shield. Don't assume it does, and don't let a vendor imply their note carries protection it doesn't.

One honest line before we go on: this is reporting, not legal advice. How HIPAA, Part 2, and your state's mental-health confidentiality law stack for your specific license and practice type is a question for your own counsel. For the framework that applies to every practice, our [HIPAA and AI scribes guide](../ai-scribe-hipaa-baa-consent/) walks through the BAA and the vendor checklist.

## Why stored audio is the real risk in behavioral health

Strip away the regime alphabet soup and the practical risk gets concrete fast. If a vendor stores the session audio, that recording is protected health information, and PHI is reachable in litigation. Under 45 CFR 164.512(e), a covered entity can be compelled to hand over PHI in response to a subpoena or court order when the conditions are met. For SUD records under Part 2 the bar is higher, a court order with a subpoena rather than a plain subpoena, but the shape holds: a stored recording is a thing someone can come for.

In therapy that edge is sharper than almost anywhere in medicine. The recording captures what the client said before any of it became documentation. The thing they blurted and took back. The name dropped in passing. The detail about a third party who never consented to anything. Your progress note is the curated version, filtered down to what's clinically necessary. The raw audio is not filtered at all. A clinician who would never paste a verbatim transcript into the chart should think just as hard about a vendor keeping that transcript on a server for weeks.

There's a quieter cost too, and it's worth naming. Some clients freeze when they know a recording is running. The chilling effect is real, and in trauma work or early sessions it can change what gets said at all. A scribe that keeps nothing still records during the visit, so this isn't a magic fix. But "the audio is gone the second your note is drafted" is a sentence you can say to a wary client and mean. "We retain it for a while for quality purposes" is not.

So here's our position, stated plainly, and you should pressure-test it. Visit audio is processed in memory and discarded the moment the note is drafted. There is no audio archive, not for us, not for the practice, not for anyone. What survives is the note you reviewed and signed. The conclusion that a vendor's stored audio is a live discovery target is our read of how 164.512(e) meets this technology, and we think it's the right read. Test it on any vendor with one question: if you keep my clients' audio and a court asks for it, what happens? A vendor that stores nothing has a one-word answer.

## The behavioral-health scribe decision tree

Run any vendor through this in order. The first question that gets a bad answer ends the evaluation.

| Step | Ask | A good answer | A bad answer |
|---|---|---|---|
| 1 | Do you store the session audio, and for how long? | Processed in memory, discarded at note draft. No archive. | "We keep it for quality or model work" with no deletion date. |
| 2 | Will you sign a BAA for a practice my size? | Yes, every customer, before any real session. | Tier-gated, or "enterprise only." |
| 3 | If I run an SUD program, do you support Part 2 consent and disclosure rules? | A straight yes or no, in writing. If no, they say no. | Confident hand-waving about "full compliance." |
| 4 | Is client audio or note text used to train your models? | A written answer, separately for audio and text. | "We follow applicable law." |
| 5 | Who can open my notes, and is every access logged? | Role-scoped, every access logged, logs reviewable. | "Our team has access as needed." |
| 6 | What happens to my data if I cancel? | Return or destruction, on a timeline, in the contract. | Silence, or buried in the terms. |

Notice what isn't on that list. Per-specialty "therapy templates," accuracy percentages, EHR write-back. They make good slides and decide nothing about your privacy exposure. Step one decides most of it. The cross-vendor version of that question is its own buying decision, and we wrote it up: see [what happens to your visit audio across major scribes](../ai-scribe-audio-retention/) before you take anyone's word, ours included.

## Does the documentation math even work for therapy?

It does, and the burden is well documented. A 2023 National Council for Mental Wellbeing survey, run by Harris Poll across 750 mental health and substance use professionals, found 93% had experienced burnout and 62% rated it moderate or severe, an 8, 9, or 10 on a ten-point scale. Paperwork is named directly: a third of the workforce said they spend most of their time on administrative tasks, 68% of those providing direct care said that admin time takes away from time with clients, and 38% said less paperwork would help them serve clients better.

That's the case for a scribe in one paragraph. A 50-minute hour followed by ten or fifteen minutes of notes, session after session, is how a full caseload turns into evening charting. A tool that drafts the progress note while the session is fresh gives that time back. The honest framing, though: in this specialty you're buying that time back against higher privacy stakes than a primary-care clinic faces. The retention answer is what makes the trade worth it or not.

## Where we fit, and where we don't

Here's where we land. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For behavioral health, the part that matters is the audio: processed in memory, discarded the moment the note is drafted. There's no recording to retain, train on, subpoena, or breach. Notes are encrypted in transit (TLS 1.2+) and at rest (AES-256), access is role-scoped and logged, and the notes belong to your practice, which can export or delete any visit at any time and never has its clinical data sold or shared. We maintain HIPAA compliant safeguards and offer a BAA to every customer; our SOC 2 Type II audit is underway. The full posture is on our [security page](../../security/). For practices that prescribe, the Rx draft reflects the visit and stays a draft only, never sent to a pharmacy; the prescriber reviews and signs it, and that review is the safety check, not an automated screen.

Now the honest part, because fairness is the point of writing this. An ambient scribe is the wrong tool for some of this work, and we'll say so plainly.

If the recording itself would change the room, skip it. Some modalities lean on a client speaking without a device running, and some clinicians write their notes reflectively, as part of how they think through a session, not by editing a transcript a model produced. Neither of those is a documentation problem a scribe solves. It's a different way of working, and it's a legitimate one. If that's you, a scribe is a poor fit no matter whose it is.

And if you run a federally-assisted SUD program that needs Part 2 consent tracking and disclosure logging wired into an enterprise EHR, a platform embedded in that EHR will fit your compliance workflow better than we will. We don't integrate with EHRs. We don't manage Part 2 consent flows for you. That's a real gap for a slice of behavioral-health practices, and you should weigh it against the audio-retention advantage rather than wave it off.

For everyone else, the calculus is simpler. A solo counselor, a group therapy practice, an LCSW clinic that isn't a Part 2 program: the documentation load is heavy, the privacy fear is legitimate, and a scribe that keeps none of your audio answers that fear at its root. If that's your practice, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and put the audio question first, before anyone talks features.

## What to verify before you sign

The work is small, and worth doing precisely:

1. Settle the audio question first. One sentence, with a deletion timeline. Everything else is secondary.
2. Confirm your regime. Are you a Part 2 program or a HIPAA-only practice? It changes the consent and disclosure rules, and it changes which vendor claims are even relevant to you.
3. Get the BAA before the first real session, and confirm it covers the trial, since you'll feed it live visits from day one.
4. Pin the training-data policy in writing, separately for audio and note text.
5. Think through consent with your own clients. State recording-consent rules vary, and a wary client is a clinical consideration, not just a legal one. Our [consent-by-state guide](../ai-scribe-patient-consent-by-state/) is the starting point.

We think a transparent retention policy should be the price of entry for any vendor handling therapy audio, and most of the market isn't there yet. Our security posture, what's encrypted, who can access what, what's audited and what isn't yet, is on our [security page](../../security/), written to be read with this checklist in hand.

The right evaluation for a behavioral-health practice is a quiet week of real sessions with the audio policy verified in writing first. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a>, make the audio question the first thing you ask, then compare the [product options](/us/compare/) against your caseload and consent workflow. In this specialty the recording is the risk. A tool that keeps none of it is the cleanest answer to the hardest question.

---

## EMR vs EHR in India: The Difference, and What You Need
https://patientsquare.com/in/blog/emr-vs-ehr-india/
Published 2026-03-27 · Updated 2026-07-22 · Tags: emr, ehr, india, basics

EMR and EHR are not the same thing. The full forms, the real difference per ONC and India’s EHR Standards, and what an Indian clinic actually needs.

EMR is Electronic Medical Record. EHR is Electronic Health Record. An EMR is the digital version of a single practice’s paper charts. An EHR is built to share a patient’s record across many providers and care settings, so the record follows the patient instead of staying inside one clinic.

EMR is Electronic Medical Record. EHR is Electronic Health Record. They sound like the same thing, and most clinics use the words interchangeably, but they aren't the same. An EMR is the digital version of one practice's paper charts. An EHR is built to share a patient's record across many clinicians and care settings. EMR stays inside the clinic; EHR follows the patient.

That's the full forms and the one-line difference. The rest of this is for the clinic owner deciding what to actually buy, because the EMR-vs-EHR label tells you less about what your clinic needs than the vendors selling either one would like.

> **Key takeaways**
>
> - EMR = Electronic Medical Record (one practice). EHR = Electronic Health Record (shared across providers). The difference is scope, per the US ONC.
> - India's EHR Standards 2016 (MoHFW) define an EHR as a shareable, standards-based record and recommend SNOMED CT, ICD, and LOINC.
> - Most "EHR" software sold to Indian clinics is, strictly, an EMR. That's usually fine for a single clinic.
> - The real clinic bottleneck isn't EMR vs EHR. It's that notes don't get written well when the average consult runs about two minutes.

## What is the full form of EMR and EHR?

EMR stands for **Electronic Medical Record**. EHR stands for **Electronic Health Record**. You'll also see "EMR full form in medical" searched as if it's a different question; it isn't. Same words, same expansion. The "M" is medical, the "H" is health, and that one-letter swap is the whole argument.

The terms came up in that order. EMR arrived first, describing software that did one job: take the paper chart in a clinician's office and make it digital. EHR came later as the more ambitious idea, a record meant to span a patient's care, not just one doctor's view of it. So when you see both terms on a brochure, they're not synonyms a marketer chose at random. They point at two different scopes.

## What is the actual difference between EMR and EHR?

Scope, and where the record can go. The clearest statement of this comes from the US Office of the National Coordinator for Health IT (ONC), and it travels well to India because the underlying distinction is about software design, not jurisdiction.

ONC's definition of an EMR: "a digital version of the paper charts in the clinician's office." It "contains the medical and treatment history of the patients in one practice." And the catch: "the information in EMRs doesn't travel easily out of the practice." In ONC's own example, a patient's EMR record "might even have to be printed out and delivered by mail to specialists." Digital, but stuck.

An EHR does more. ONC says EHRs "focus on the total health of the patient" and are "built to share information with other health care providers, such as laboratories and specialists, so they contain information from all the clinicians involved in the patient's care." The line that captures it: with an EHR, "the information moves with the patient, to the specialist, the hospital, the nursing home, the next state or even across the country." ONC adds that it uses "electronic health record or EHR almost exclusively," because despite looking "a little picky," the distinction is "actually quite significant."

| | EMR (Electronic Medical Record) | EHR (Electronic Health Record) |
|---|---|---|
| **Who it serves** | One practice or clinician | The patient, across many providers |
| **Where the record lives** | Inside the clinic that made it | Shared across clinics, labs, hospitals |
| **Designed to be shared** | Not really; export is manual | Yes, interoperability is the point |
| **Patient access** | Usually none | Designed for patient access too |
| **What it's best at** | Clean records for daily clinic work | Continuity of care across settings |
| **The honest summary** | Digital chart that stays put | A record that follows the patient |

## What do India's EHR Standards say?

India has its own answer, and it lines up with ONC. The Ministry of Health and Family Welfare published the **Electronic Health Record (EHR) Standards for India** in 2013 and revised them on 31 December 2016. The intent is plain in the title: a uniform basis for creating and maintaining health records that can be shared across providers, not just stored in one place.

The 2016 standards define an EHR as a collection of the medical records generated during clinical encounters, and they recommend specific coding systems so those records mean the same thing everywhere they travel: SNOMED CT for clinical terms, ICD for diagnoses, and LOINC for lab and observation data. That recommendation is the tell. You only need shared vocabularies if the record is meant to move. A chart that never leaves your clinic doesn't need to speak SNOMED to anyone.

And the plumbing to move it is further along than most clinic owners assume. For a record to travel, the system needs a verified directory of who the sending and receiving providers actually are. India built two: the Health Facility Registry and the Healthcare Professionals Registry, both run under ABDM. As on 16 December 2024, per the health ministry's own year-end achievements document, the facility registry held 3,55,072 registered health facilities and the professionals registry held 5,42,132 verified clinicians, and both kept climbing into 2025.

Read those numbers carefully, though. Being listed on a registry means a clinic can be addressed when a record needs to reach it. It is not the same as actively sending records yet. But the addressing layer, the thing that turns a stored chart into a shareable one, is no longer hypothetical. The directory exists; what's uneven is how many clinics have started using it to actually move a record.

For a clinic owner, that reframes the buying question. The interoperability the EHR label promises is not a distant maybe anymore; the national scaffolding for it is being registered facility by facility. What is still optional, for now, is whether your own software is built to use it.

So formally, India draws the same line ONC does. An EHR is the interoperable, standards-based record. What most Indian clinics run day to day, whatever the login screen calls it, is closer to an EMR: a solid digital chart for that clinic. There's nothing wrong with that. It's worth knowing which one you actually bought.

## Does the EMR-vs-EHR label matter for my clinic?

Less than the brochure implies. Here's the uncomfortable part: for a solo doctor or a small group practice, full EHR interoperability is often a feature you pay for and rarely use. You're not routing records to a nursing home in another state. You're trying to get through a Tuesday OPD and have a clean, findable note for each patient at the end of it.

Where the EHR distinction earns its keep is at scale: a hospital, a multi-site chain, a network that genuinely moves patients and their records between departments and facilities. There, interoperability isn't a nice-to-have; it's the job. For that setting, buy the EHR and make sure it actually implements the India EHR Standards rather than just claiming the acronym.

For most clinics, the more useful question isn't "EMR or EHR." It's "where do my records actually break?" And the answer is almost never the storage layer. It's the notes.

## So what does an Indian clinic actually need?

A record that gets written. That sounds obvious until you sit in a real OPD.

The average primary-care consultation in India runs about two minutes. That figure comes from a 2017 BMJ Open systematic review of 67 countries by Irving and colleagues, which clocked consultation length from 48 seconds in Bangladesh to 22.5 minutes in Sweden, and put India near the short end at roughly two minutes. Two minutes to listen, examine, decide, and prescribe. The documentation loses that race every time. So the note gets compressed to a line, or written from memory after the queue clears, or skipped.

No EMR or EHR fixes this on its own. A better storage system doesn't make the note appear; it just gives the thin note a nicer home. The constraint is upstream of the database. It's the gap between a two-minute consult and a complete record, and that gap is where charts go missing and where, under India's medical-record-keeping expectations, a clinic's defensibility quietly erodes.

This is the layer most clinics are actually missing, and it's a different layer from the EMR-vs-EHR question. You can have the right record system and still have bad records, because the bottleneck is the writing, not the storing.

## Where does an AI documentation layer fit?

Alongside whatever you already run, or as part of the platform if you want the record system too. The scribe module on its own is a documentation layer, not a replacement for your EMR, and it doesn't need to be one to earn its place.

Patient Square is an AI clinical platform, and the AI Medical Scribe is its ambient scribe module: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. Run the scribe alongside your EMR or EHR and it just solves the writing problem while your record system keeps doing the storing. Or move up to the Copilot plan, where a bundled AI EHR ships with it, and you get both under one login. Either way you review the draft, sign it, and it lives wherever your records already live.

A few things that matter for an Indian clinic specifically. It's record-system-agnostic, so you don't rip out what works to add it. Visit audio is processed in memory and discarded the moment the note is drafted, so there's no audio archive sitting around as a liability. It captures English, Hindi, and 20+ Indian languages, including the mid-sentence Hindi-English mixing of a real OPD, and the note always comes back in clean clinical English. Data is handled to DPDP Act 2023 standards, consent-first and purpose-limited. ABDM integration is on the roadmap, not a current claim, and any vendor telling you otherwise deserves a follow-up question. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

> We think the EMR-vs-EHR debate gets more clinic attention than it earns, while the thing that actually determines record quality, whether the note gets written at all, gets almost none.

Pricing is published, per clinician per month, ex-GST. Assist starts at ₹1,599 on annual billing for the documentation essentials. With 18% GST, Assist lands at about ₹1,887 a month all-in. Copilot at ₹2,399 annual adds the bundled AI EHR and WhatsApp; Autopilot at ₹3,999 adds an AI receptionist and follow-ups. The tiers gate features, so you pay up only when you want the record system or the automation. There's a 7-day free trial too, so you can run it on a real clinic day before you commit to anything.

If you're weighing the documentation tools rather than the storage systems, the [India AI scribe comparison](../india-ai-scribe-comparison/) breaks down how the main options handle audio, languages, and pricing. On the compliance side, our [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) and the [DPDP Rules 2025 timeline](../dpdp-rules-2025-clinic-timeline/) cover what the law now asks of any clinic holding patient data. And whatever record system you settle on, the documentation layer is the one most clinics skip and most need.

## How to decide, in one pass

You don't need to resolve the acronym to make a good call. Three questions get you there:

1. Does my clinic move patient records between sites, hospitals, or specialists as a routine part of care? If yes, you want a real EHR that implements the India EHR Standards. If no, a clean EMR is usually enough.
2. Are my notes actually complete and retrievable today, or are they thin because there's no time to write them? If thin, the fix is a documentation layer, not a new database.
3. Does my vendor answer "where does the visit audio go" and "what's the price after year one" in one sentence each? Vague answers there tell you how the rest of the relationship will go.

Sort those out and the EMR-vs-EHR question mostly answers itself. If the missing piece is the note rather than the storage, <a href="/in/how-it-works/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a real consult turn into a signed note, or read the [pricing in full](../../pricing/) first. Either way, fix the layer that's actually broken.

---

## A Scribe for Your OPD: What It Does on a 100-Patient Day
https://patientsquare.com/in/blog/scribe-for-doctors-india/
Published 2026-03-25 · Updated 2026-07-22 · Tags: scribe, medical-scribe, india, opd, workflow

What a scribe actually does across a busy 100-patient Indian OPD day, hour by hour, and what the AI version at ₹1,599 a month does that a human one cannot.

A scribe writes the clinical record while the doctor sees the patient, so the doctor talks and examines instead of typing. The scribe captures the history, findings, diagnosis, and plan into a structured note. A human scribe sits in the room and types; an AI scribe listens in the background and drafts the note itself, ready for the doctor to review and sign.

A scribe writes your clinical record while you see the patient. On a 100-patient OPD day that one job is the difference between leaving at closing and staying till 9pm to reconstruct notes from memory. A human scribe types in the room and costs about ₹22,000 a month. An ambient AI scribe listens in the background, drafts each note as the visit happens, and runs ₹1,599 a month ex-GST. Below is what that actually looks like across a real OPD day, hour by hour, and where each one helps or doesn't.

This is a workflow page, not a feature pitch. We walk a 100-patient day, show where the time goes, and put the cost of a human scribe next to the AI seat so you can see the trade for your own OPD.

> **Key takeaways**
>
> - A human medical scribe in India averages about ₹22,000/month (Indeed India, Dec 2025); a clinical documentation specialist runs near ₹33,750/month (Payscale, 2026).
> - AI Medical Scribe by Patient Square is ₹1,599/month ex-GST on annual billing, about ₹1,887 with 18% GST, roughly a twelfth to a twenty-first of a dedicated documentation hire.
> - India's average primary-care consult is near two minutes (BMJ Open, 28.5M consultations, 67 countries), so typing a full note per patient during the visit isn't realistic at OPD pace.
> - On a 100-patient day, the AI drafts notes as you work; you end with records to review, not a backlog to rebuild after the last patient leaves.

## What does a scribe actually do for a doctor?

Strip it to the job. A scribe turns a spoken visit into a written record so you don't have to do both at once.

In a busy Indian OPD that matters more than it sounds. You take the history in Hindi or Hinglish, examine, decide, explain the plan, and the record of all that has to land somewhere. Do it yourself and you're typing while a patient talks, or you're deferring it. A scribe takes that off your hands: history, examination findings, diagnosis, medications, follow-up, written down in a structure you can sign.

There are two ways to get one. A human scribe sits beside you and types as you go, which works but needs hiring, training, and a salary. An ambient AI scribe listens to the consult in the background and drafts the note itself, so nothing gets typed in the room at all. The output is the same kind of record. What differs is the cost, the keeping-up, and what happens when the OPD gets loud.

## A 100-patient OPD day, hour by hour

Picture a single-doctor clinic that opens at 9 and runs till the queue clears. A hundred patients is a heavy day, not a record one. The super-speciality OPDs in a 2019 Int J Community Med Public Health study saw more than 200 patients per working day at about two minutes a consult, so a hundred is squarely in real-OPD territory.

Here is the same day, the manual way and with an ambient scribe beside you.

| Time | Doing it yourself | With an ambient AI scribe |
|---|---|---|
| 9:00–11:00 | First 25 patients. You type a line or two each, or scribble to "finish later". Notes start thinning by patient 15. | First 25 patients. The note drafts itself in the background; you glance and move on. |
| 11:00–14:00 | Peak load. Typing falls away entirely; you're working from memory and a sticky note. | Peak load. Each consult still produces a full structured note while you focus on the patient. |
| 14:00–17:00 | Last 40 patients. The deferred pile is now huge and half-remembered. | Last 40 patients. Notes keep landing, ready to review, two minutes after each visit. |
| After clinic | 1.5 to 2 hours rebuilding the day's notes from fragments. Detail is already lost. | 15 to 30 minutes skimming drafts, fixing the odd line, signing. Then you leave. |

The manual column isn't an exaggeration. At a two-minute consult pace, measured across 28.5 million consultations in a BMJ Open review of 67 countries, India's average sits among the shortest anywhere. You physically cannot type a complete, structured English note inside two minutes and also look at the patient. So the notes slide to the evening, and the evening is when the detail has already faded.

## The cost: a human scribe versus the AI seat

This is the part doctors actually weigh, so here are the numbers with sources.

A human medical scribe in India averages about ₹22,187 a month, per Indeed India's December 2025 figure, with listings running from roughly ₹16,500 to ₹60,000 depending on city and experience. Want someone trained specifically on clinical documentation? Payscale's 2026 India data puts a clinical documentation specialist near ₹4,05,000 a year, about ₹33,750 a month. Even a non-clinical front-desk hire who only helps with typing sits near ₹13,500 a month.

Set that against the AI seat. AI Medical Scribe by Patient Square is ₹1,599 per doctor per month ex-GST on annual billing. Add 18% GST and it's about ₹1,887 a month, which works out to roughly ₹53 on a day you run OPD. So a dedicated documentation hire costs somewhere between twelve and twenty-one AI seats.

Now the honest part most cost pages skip. A dedicated in-room human scribe, common in US clinics, is rare in Indian OPDs. Indeed India lists the role from a tiny pool, only seven salaries on its career page when we checked. So for most Indian doctors the real comparison isn't "hire a scribe versus buy software". It's "keep typing notes after clinic yourself versus have something draft them as you go". The salary numbers matter mostly as a ceiling: that's what buying the human version of this job would cost you.

## What does the AI scribe hand back, and in what language?

The note, in English, ready to sign. That last bit trips people up, so let's be exact.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. You and the patient can speak English, Hindi, Hinglish, or any of 20-plus Indian languages, switching mid-sentence the way real consults do. The captured speech can be Hinglish; the note that comes out is always clean clinical English, because that's the language a medical record should be in. You don't dictate in a fixed language, and you don't get a half-Hindi note. You talk normally, you read an English note.

The prescription comes back as a draft off the plan you dictated. You review the drugs, doses, and instructions and sign, the same way you check a script before it leaves your desk. It doesn't run an automated interaction or dosing check, and it never routes to a pharmacy on its own; the prescribing judgment stays yours. If your clinic's signal drops mid-OPD, capture keeps working offline with on-device encryption and syncs when the connection returns. Audio is processed in memory and discarded once the note drafts, so there's no recording sitting in a file afterward. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

## When a human scribe is still the better call

Plainly, because the cost gap doesn't settle every case.

Keep a human if you want a person who does more than write the note. A human scribe can chase a pending report, prep the next patient, manage the queue, or handle the unscripted bits of a clinic an AI won't touch. If "scribe" in your practice means a clinical assistant who happens to document, the AI replaces one slice of that role, not the whole person. A teaching setup that wants to give a junior real clinic exposure has its own reason to keep humans.

Go with the AI when the job is the record. If your only reason to want a scribe is that notes are eating your evenings, you're weighing about ₹53 a working day against an hour or two of your own time, every day. For a solo doctor specifically, [we ran that payback math separately](../ai-scribe-for-solo-doctors-india/), and it tips fast once volume is high. The busier your OPD, the more lopsided the trade.

## How does the AI seat compare to other India options?

Short version, because this is a workflow page and not a shoot-out.

EkaScribe Pro is ₹1,499 per doctor per month, about ₹50 a day, with a free tier capped at five consultations a day. It's India-native and, the honest concession, it has live ABDM integration that we don't; ABDM is on our roadmap, not shipping today. Our Assist plan starts at ₹1,599 ex-GST on annual billing, with a published rate ladder, no per-note metering, and a 7-day full-featured trial with no daily cap. Where we differentiate is EHR-ready export instead of lock-in, discarding live consultation audio after processing, and published, transparent tiered pricing. Uploaded recordings use a separate retention mode with explicit consent. The full ladder with the GST math is on the [India rate card](../ai-medical-scribe-price-india/) and the [pricing page](../../pricing/). If you're weighing the human-scribe economics in detail, [our human-versus-AI cost breakdown](/us/blog/ai-scribe-vs-human-scribe-cost/) lays out the staffing side.

## Test it on your own OPD before you decide

Don't take the worked example above on faith. Run your own day.

Start your 7-day free trial, with no daily cap, and use it on a normal OPD. Count roughly how many minutes you'd otherwise spend documenting per patient, then check whether the English notes are clean enough to sign without a rewrite. Multiply by your real patient count. If having those minutes back across a 100-patient day isn't worth about ₹53 a day to you, don't subscribe. We mean that. The trial is built so the math is yours, run on your clinic and not ours.

When you want to watch it draft a note against the kind of OPD day you actually run, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we'll do exactly that.

---

## Best Clinic Management Software India: 2026 Scorecard
https://patientsquare.com/in/blog/best-clinic-management-software-india/
Published 2026-03-24 · Updated 2026-09-29 · Tags: clinic-management-software, comparison, abdm, india

A clinician-built scorecard of clinic management software in India for 2026: Practo Ray, HealthPlix, EkaScribe and more, on price, ABDM-readiness, and charting.

There is no single best one; it depends on what your clinic actually runs on. A full EMR like HealthPlix fits clinics that need billing, pharmacy, and ABDM in one place. A greenfield clinic can use Patient Square EHR through Practice Copilot, while an established clinic can keep its current EHR and add an ambient scribe. Score each on price, ABDM-readiness, and how much it cuts your charting, then trial the shortlist.

There's no single best clinic management software in India. A greenfield clinic has a real choice: buy a full suite for billing, pharmacy, and ABDM workflows, or start Practice Copilot with the bundled Patient Square EHR as its record system. An established clinic can keep its current EHR and add the documentation layer alongside it. This scorecard keeps those paths separate, then measures the work each product removes from a real clinic day.

Start with the category, not the logo. Practo Ray and HealthPlix are full EMRs; EkaScribe and Augnito focus on documentation; Practice Copilot combines an ambient scribe with a bundled EHR for greenfield clinics. The useful comparison is the work your clinic needs done, the published price, and the ABDM milestone a vendor can show.

_Sources: Irving et al., BMJ Open 2017; National Health Authority / DD News, May 2026._

Starting a new clinic and want the record system plus documentation in one place? <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> with Practice Copilot. If you already have an EHR, use the scorecard to decide whether an alongside documentation layer is the smaller, safer change.

## Two jobs clinic software gets asked to do

It's a loose label, and that's the first trap. Vendors use "clinic management software," "EMR," "HMS," and "practice management" almost interchangeably, but buyers are usually after one of two very different things.

One is the **system of record**: appointments, patient registration, billing and GST invoicing, pharmacy and inventory, lab orders, sometimes inpatient and teleconsult. That's a full EMR or clinic-management suite. Practo Ray and HealthPlix live here. Practice Copilot also gives a greenfield clinic a bundled AI EHR from the Copilot tier, but it is not a claim to run billing, pharmacy, or inpatient workflows.

The other is the **documentation layer**: the thing that turns a consultation into a written note. For a two-minute Indian OPD consult, India's primary-care average per the 67-country BMJ Open review, that note is where time and medico-legal risk both pile up. A scribe handles only this slice, and it sits on top of whatever record system you already use.

Conflating the two is how clinics overbuy. You don't need a new EMR because your notes are thin. You need something that fixes the notes.

## A scorecard for an ordinary clinic week

Forget feature checklists that run forty rows deep. Five criteria decide whether a tool earns its monthly fee, and we've weighted them for an independent doctor or a small clinic, not a 300-bed hospital.

1. **What problem does it solve, records or documentation?** Decide this first. Everything else is downstream. Buying a full suite to fix charting is like buying a car to charge your phone.
2. **Published, honest pricing.** Does the vendor put a number on the page, in rupees, ex-GST with the 18% disclosed? Sales-gated pricing isn't a dealbreaker, but it's friction, and it usually means the price flexes with how hard you negotiate.
3. **ABDM-readiness, with the milestone named.** If you want patient records linked to ABHA, the software has to be ABDM-certified, and "ABDM-ready" hides three different National Health Authority milestones (more on that below). Table stakes for a full EMR; not yet universal for scribes.
4. **Documentation burden lifted.** Does it actually shorten the note, or just store it? An ambient scribe that drafts the note from the conversation removes work. A form-heavy EMR can add it.
5. **Data discipline under DPDP.** Since the [DPDP Act 2023](../dpdp-act-clinics-guide/), every software purchase is a fiduciary decision. Where does the data sit, how long is it kept, and, for anything that listens, is the audio stored? We think this one is underweighted by most buyers and about to get a lot heavier.

## Named options, side by side

Here's the scorecard, built only on what each vendor publishes (or doesn't). Two products are full EMRs, two are ambient note tools, and Practice Copilot combines an ambient scribe with a bundled AI EHR. Read the "Type" row first; it tells you which problem each one is for.

| | Practo Ray | HealthPlix | EkaScribe (eka.care) | Augnito | Practice Copilot by Patient Square |
|---|---|---|---|---|---|
| **Type** | Clinic-management / practice suite | Specialty EMR | Ambient scribe | Medical dictation | AI Copilot: ambient scribe + bundled AI EHR |
| **Published price** | None first-party (sales-gated) | ₹11,999/yr Pro; ₹17,999/yr Elite | ₹1,499/mo Pro; free tier 5 consults/day | None published (sales-gated) | Assist ₹1,999/mo (₹1,599 annual); Copilot ₹2,999 (₹2,399); Autopilot ₹4,999 (₹3,999); ex-GST |
| **Price signal** | Third-party ~₹1,000–6,000/doctor/mo | First-party (HealthPlix blog) | First-party (ekascribe.ai) | App Store India IAPs ₹1,199 / ₹3,299 / ₹11,900 (periods unlabeled) | First-party |
| **Billing / pharmacy / IPD** | Yes (practice management) | Yes (billing, pharmacy) | No | No | No |
| **ABDM** | Per Practo (not first-party-verified here) | Listed as a feature | eka.care platform has live ABHA workflows | Dictation-focused | On the roadmap (not shipped) |
| **What's drafted** | Records you enter | Records you enter + EMR notes | Note + clinical summary | Transcribed dictation | Note + ICD-10 suggestions + Rx draft |
| **Rx safety check** | Not headlined | Drug-interaction (DDI) alerts | Not headlined | Not applicable | None; the draft goes to the clinician to review and sign |
| **Audio handling** | n/a (not a scribe) | n/a (not a scribe) | Cloud servers (India), per eka framing | Per Augnito policy | Live consultation audio discarded; uploads use a separate mode with explicit consent |
| **Languages** | n/a | EMR UI | 20+ named (Hindi, Bengali, Telugu, Tamil and more) | Multiple Indian languages (per Augnito) | English + Hindi + 20+ on input; note in clean English |
| **Trial** | Free trial (per third-party) | Demo-led | Free tier (5/day) | 7-day | assisted 7-day |

All figures come from each vendor's own pages and listings in June 2026, except where marked third-party; confirm before buying. A few cells need plain talk, which the next two sections give.

## ABDM: ask which milestone is live

This row trips up more buyers than any other, so it's worth slowing down. ABDM, the Ayushman Bharat Digital Mission run by the National Health Authority, crossed 100 crore ABHA-linked health records in May 2026, with more than 450 health-tech solutions integrated. It's real, it's large, and it's where India's interoperable patient record is heading.

The demand side is just as far along, which is the part a scorecard should weigh. The government's own eSanjeevani service had facilitated more than 43 crore cumulative teleconsultations by 23 November 2025, across all 28 states and 8 Union Territories, per a written reply the health ministry gave in the Rajya Sabha. That's teleconsultations since the 2019 launch, not unique patients, so read it as usage rather than headcount.

Still, it settles one question a buyer might otherwise argue about. The digital rails clinic software plugs into aren't a pilot anyone is waiting on. They already carry hundreds of millions of visits. So when you score a tool on ABDM-readiness, you're scoring it against live national infrastructure, not a roadmap slide. A suite that still can't talk to any of it in 2026 is a weaker buy than its feature list makes it look.

For the scorecard, that turns a vague checkbox into a sharp one. Don't score "has ABDM" as yes or no. Score whether the tool can plug into the rails your patients already use, and ask the vendor to show it, not say it.

But "ABDM-ready" on a pricing page can mean almost anything. Under the NHA's sandbox-to-production process, a piece of software certifies against milestones, and each one does a different job:

- **M1** makes the software an identity provider: it can create and verify an ABHA number and register on the facility and professional registries (HFR and HPR).
- **M2** makes it a Health Information Provider: it can share a patient's records, as FHIR, when the patient consents.
- **M3** makes it a Health Information User: it can pull records from other providers into your view.

Certification is per-software, not per-clinic, so the vendor clears the sandbox once and each facility then registers itself. The practical takeaway for a buyer is one question: *which milestones have you cleared, and are they live in production or still in sandbox?* A tool that can mint an ABHA (M1) but can't yet share records (M2) is "ABDM-ready" in marketing and half-built in practice.

To be straight about our own position: **AI Medical Scribe by Patient Square has ABDM integration on its roadmap, not shipped.** We won't put an ABDM badge on a scribe that doesn't yet hold the certification, and you shouldn't accept one from anyone who can't name the milestone. This section is here to make you a sharper buyer, not to claim a status we don't have.

## When a full clinic suite is the right buy

Plenty of clinics. If your evenings aren't lost to charting but to chasing payments, stock, and appointments, a scribe won't fix your actual problem, and a full EMR will. Be honest about which fire you're fighting.

A full suite or EMR is the better buy when you:

- **Bill in-house and need GST invoicing, receipts, and revenue reports** in the same system as the clinical note.
- **Run a pharmacy or hold inventory** and want dispensing tied to the prescription.
- **Manage inpatients, labs, or multiple satellite clinics** under one roof.
- **Want ABDM linking today** and your EMR vendor has cleared the milestones (HealthPlix, for instance, lists ABDM, with billing, pharmacy, and drug-interaction alerts built in).

If two or more of those are true, start your shortlist with a full EMR, not a scribe. The honest read is below.

## Where Practice Copilot fits

For a greenfield clinic, Practice Copilot can use the bundled Patient Square EHR as the record system from the Copilot tier. For a clinic that already has an EHR, Practice Copilot can work alongside it. We do not claim that it runs billing, pharmacy, or inpatient wards. When export matters, the supported claim is **EHR-ready export (PDF · HL7 · FHIR)**, not a named integration or automatic write-back.

Practice Copilot brings an ambient AI Medical Scribe, a bundled AI EHR, scheduling, and messaging as you move up the plan. The scribe hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft for the clinician to review and sign. For an Indian OPD, it accepts code-mixed Hinglish on input and returns the note in clean clinical English. The prescription remains a draft. It is not transmitted to a pharmacy, and the product does not screen it for interactions, dosing, or contraindications. Patient Square handles the patient data it processes to DPDP Act 2023 standards: consent-first and purpose-limited. Visit audio is processed in memory and discarded once the note is drafted. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

On price, we publish every number. There are three per-clinician tiers on annual billing, ex-GST: Assist at ₹1,599 a month for the scribe, Copilot at ₹2,399 which adds the bundled AI Copilot EHR and WhatsApp messaging, and Autopilot at ₹3,999. Add 18% GST and the Assist invoice is about ₹1,887. There is a 7-day free trial through the India signup page. Assist is just above the published ₹1,000–1,500 monthly range shown here for HealthPlix and EkaScribe. If you're comparing scribes specifically, the [India scribe comparison](../india-ai-scribe-comparison/) goes deeper on EkaScribe and Augnito, and the [India scribe roundup](/in/blog/best-ai-scribe-for-india-2026/) widens the field.

The deciding move is a real clinic day. Run the shortlist against your own patients, accents, and prescriptions. If you are a greenfield clinic, <a href={CTA_URLS.in.trial}>Start your 7-day free trial</a> with the bundled EHR path. If you are keeping an existing EHR, run the same trial alongside it and judge the note before changing anything else.

---

## DAP Notes: Format, an AI Example, and a Co-Sign Check
https://patientsquare.com/us/blog/dap-note/
Published 2026-03-23 · Tags: dap-note, progress-note, behavioral-health, therapy, documentation

What a DAP note is, how Data-Assessment-Plan differs from SOAP, a full AI-generated example for a therapy session, and a checklist to run before you sign.

DAP stands for Data, Assessment, Plan. It is a three-part progress note format used mostly in behavioral health. Data is what happened in the session, what the client said and what you observed. Assessment is your clinical read of it. Plan is what comes next. It collapses the subjective and objective parts of a SOAP note into one Data section, which makes it faster to write for talk therapy.

A DAP note is a three-part progress note: Data, Assessment, Plan. Data is what happened in the session, the client's words and your observations together. Assessment is your clinical read of it. Plan is what happens next. It's the format most therapists and counselors reach for, because it merges the two parts a SOAP note keeps separate and writes faster for talk work. Below is the format, a full AI-generated example, and a checklist to run before you sign one.

If you've used SOAP, DAP will feel like SOAP with the first two sections fused. That's basically what it is. The harder questions are what counts as Data versus Assessment, whether an insurer cares which format you use, and, if a scribe drafts the note for you, what you actually need to check before it becomes part of the record. We'll work through all three.

> **Key takeaways**
>
> - DAP = Data, Assessment, Plan. It collapses SOAP's Subjective and Objective into one Data section, leaving three parts instead of four.
> - Use DAP for therapy and counseling, where the line between reported and observed is blurry. Use SOAP when there are real exam findings and vitals to separate.
> - Payers don't reject a format. CMS guidance asks that a note be legible, signed, dated, and justify medical necessity, whether it's DAP or SOAP.
> - 93% of behavioral health workers reported burnout in a 2023 survey of 750, and paperwork is named directly. A faster note format is one lever.
> - If an AI scribe drafts your DAP note, check it against CMS's own warning: cloned-looking notes and a Data section that drifted from what was said.

## What is a DAP note, and what does each section carry?

DAP comes out of the same case-note tradition as SOAP. In their 2002 Journal of Counseling & Development paper on counseling case notes, Cameron and Turtle-Song laid out the SOAP format, Subjective, Objective, Assessment, Plan, as a way to document a client's care clearly and concisely. DAP is the behavioral-health adaptation: take SOAP's first two sections, the ones that split what the client says from what you measure, and merge them. In therapy that split is awkward. A client's tone, their affect, the thing they said and then walked back, all of it is both reported and observed at once. One Data section holds it without forcing an artificial line.

Here's what each part is for.

| Section | What it holds | Watch for |
|---|---|---|
| **Data** | What happened in the room: the client's reported mood and symptoms, quotes that matter, your behavioral observations, the interventions you used, and how the client responded. Subjective and objective, together. | Keep it factual. The moment you write what it *means*, you've crossed into Assessment. |
| **Assessment** | Your clinical judgment: progress toward treatment goals, your read on the client's current state, risk considerations, how this session connects to the arc of treatment. | This is the section a transcript can't write for you. It's reasoning, not recall. |
| **Plan** | What comes next: the next appointment, any homework or between-session task, referrals, planned consultations, and changes to the treatment plan based on today. | A dropped Plan item is a missed action. Completeness is the thing to check. |

The whole point of DAP is that it's lighter than SOAP for the work therapists actually do. Fewer headers, less time deciding which bucket a sentence goes in, more of the note reading like a clinical narrative. That's the appeal, and it's a real one when you're documenting six or eight sessions back to back.

## DAP vs SOAP: which one should you use?

Short version: SOAP when the visit has measurable findings to separate, DAP when it doesn't. A primary-care visit has vitals, an exam, lab values, things that belong cleanly in an Objective section apart from what the patient reports. A 50-minute therapy hour usually doesn't. Forcing a counseling session into Subjective-versus-Objective produces a stilted note where half the Objective section is empty and the other half is really subjective anyway.

| | SOAP | DAP |
|---|---|---|
| **Sections** | Subjective, Objective, Assessment, Plan (4) | Data, Assessment, Plan (3) |
| **Subjective vs objective** | Kept separate | Merged into Data |
| **Best fit** | Medical visits with exam findings, vitals, results | Talk therapy, counseling, case management |
| **Speed** | More structure to fill | Fewer sections, faster for narrative work |
| **Origin** | Documented for counseling by Cameron & Turtle-Song (2002) | Behavioral-health simplification of SOAP |

Neither is "better." They're tuned for different visits. Plenty of behavioral-health clinicians who also do medication management keep both in their head and pick per encounter. If you want the deeper version of what separates a good note from a mediocre one in either format, we built a six-point grading rubric in [what makes a good AI-generated SOAP note](../ai-scribe-soap-note-quality/), and every point on it applies to DAP too.

One thing worth saying plainly, because vendor pages blur it: the DAP note your scribe drafts is a progress note, and a progress note is not a HIPAA "psychotherapy note." Under 45 CFR 164.501, psychotherapy notes are your separate session-analysis notes, kept apart from the chart, and the definition specifically excludes the progress note, the treatment plan, and any summary of diagnosis and progress. DAP output is exactly that excluded content. So it's protected by HIPAA, but it doesn't carry the heightened authorization shield some vendors imply. We sorted that out in full in the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/).

## A real AI-generated DAP note example

This is the artifact. Below is a complete DAP note for a routine therapy session, written the way a competent ambient scribe should draft it from the audio. The case is invented, no real client, but the shape and level of detail are what you should expect on screen about two minutes after a visit ends.

**Session context:** 45-minute individual therapy session, established adult client, generalized anxiety, week 6 of treatment.

> **D (Data):**
> Client attended on time, alert and engaged, dressed appropriately. Reported anxiety "a bit better this week, maybe a 5 out of 10 instead of a 7." Described two nights of disrupted sleep tied to a work deadline, but said the breathing exercise from last session "actually helped, I used it twice." Made good eye contact, speech normal rate and volume, affect congruent and brighter than prior sessions. Discussed an upcoming presentation as the main current stressor. Practiced cognitive reframing of the thought "if I stumble, everyone will think I'm incompetent." Client was able to generate two balanced alternative thoughts with minimal prompting. No reported substance use. Denied suicidal or homicidal ideation when asked directly.
>
> **A (Assessment):**
> Client is making steady progress toward the treatment goal of reducing anticipatory anxiety. Independent use of the breathing technique between sessions suggests the coping skills are generalizing outside the room, which is the target. Cognitive reframing is landing; the client moved from catastrophic to balanced thinking faster than in week 3. Sleep disruption appears situational and tied to the deadline rather than a worsening of baseline symptoms. No acute risk indicators present this session.
>
> **P (Plan):**
> Continue weekly individual therapy. Homework: use the breathing exercise before the presentation and log one balanced alternative thought each day this week. Next session in one week; plan to review the presentation outcome and introduce graded exposure to public-speaking situations if the client is ready. No medication referral indicated at this time. Treatment plan unchanged.

Read it the way you'd read your own. Notice what the Data section does and doesn't do: it reports the "5 out of 10," the two quotes, the observations, the interventions, and it stops there. It doesn't say the client is improving. That judgment lives one section down, in Assessment, where it belongs. That separation is the single most common place an AI draft goes wrong, sliding an interpretation into Data, and it's the first thing to scan for. The Plan section is specific and actionable: not "continue treatment" but the actual homework, the actual next step, the actual decision on medication. A vague Plan is a Plan you'll have to rewrite.

A draft like this is a strong starting point. It is not a finished note until you've read it and signed it. Which brings us to the checklist.

## The pre-sign co-sign checklist for a DAP note

Whether you wrote the note or a scribe drafted it, the same elements have to be true before you sign. We've anchored this to CMS's own guidance for behavioral health documentation rather than to anybody's marketing, because the audit standard is what actually matters when a payer or reviewer pulls the chart.

CMS's "Documentation Matters" fact sheet for behavioral health practitioners says a documented service must reflect medical necessity, be complete, concise, and accurate, be legible, signed, and dated, and be coded correctly. Same fact sheet, on EHRs specifically: turn off auto-fill and watch for "cloned" notes, the ones that look identical across different visits, because they "may not reflect the uniqueness of the encounter." That warning was written about templates and copy-paste. It applies word for word to an AI draft.

| # | Check before you sign | Why it matters |
|---|---|---|
| 1 | **Data is factual, not interpretive.** Symptoms, quotes, observations, interventions. No clinical conclusions hiding in here. | Interpretation belongs in Assessment. A judgment in Data muddies both sections and reads sloppy on audit. |
| 2 | **Assessment is yours, and it's real.** It reflects your actual clinical reasoning about this session, not a paraphrase of the Data. | This is the section that justifies the visit. CMS wants medical necessity; a recycled Assessment doesn't show it. |
| 3 | **Plan is specific and complete.** Every decision you made, next appointment, homework, referral, med change, is captured. | A dropped Plan item is a missed action and a documentation gap. Completeness is non-negotiable. |
| 4 | **Nothing is invented.** No symptom, quote, or finding the client never reported. Scan the Data hardest. | A confident hallucinated detail is worse than a blank field; you have to already know it's wrong to catch it. |
| 5 | **It doesn't look cloned.** This note reflects *this* session, not last week's with the date changed. | CMS flags cloned notes by name. A scribe that reuses phrasing across visits trips the same wire a copy-paste habit does. |
| 6 | **It's signed and dated by you.** Your signature, the correct date, your edits attributed if you changed anything. | CMS lists legible, signed, and dated as a base requirement. The signature is you taking ownership of the content. |

Run a real note through this, not a demo note. The draft that matters is the one from your messiest session, the client who buried the real issue in the last five minutes, the one who switched topics four times. A scribe that produces a clean, sign-ready DAP note on that session is saving you time. One that needs a heavy rewrite isn't, no matter what the time-saved number on the marketing page says.

## Does a faster note format actually move the needle?

It does, and the documentation burden behind the question is well documented. A 2023 National Council for Mental Wellbeing survey, run with Harris Poll across 750 behavioral health workers, found 93% had experienced burnout and 62% rated it moderate or severe. Paperwork is named directly: a third of the workforce said they spend most of their time on administrative tasks, and 68% of those providing direct care said that admin time takes away from time with clients.

That's the case for a leaner note in one paragraph. A 50-minute session followed by ten or fifteen minutes of charting, repeated across a full day, is how a caseload turns into evening documentation. DAP helps a little by cutting a section. A scribe that drafts the DAP note while the session is fresh helps more, by moving the typing off your plate entirely. But the gain only holds if the draft is good enough to sign with light edits. A format change plus a bad draft is just a different way to spend the same evening.

## Where AI Medical Scribe by Patient Square fits

Here's where we land. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For behavioral health, the same engine drafts into a DAP structure, and the example above is the kind of output to expect. The note is yours to read, edit, and sign; the draft saves the typing, not the clinical judgment.

The part that matters most in therapy isn't the format, it's the audio. Visit audio is processed in memory and discarded the moment the note is drafted. There's no recording kept to retain, train on, or produce under a subpoena. Notes are encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice, which can export or delete any visit anytime. We maintain HIPAA compliant safeguards and offer a BAA to every customer, and our SOC 2 Type II audit is underway. We made the full privacy argument, including why stored audio is the real risk in behavioral health, in the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/).

And the honest limit, because pretending otherwise helps nobody. If you write notes reflectively as part of how you think through a session, rather than by editing a draft, a scribe is a poor fit no matter whose it is. If a recording in the room would change what your client says, that's a clinical reason to skip it. And we don't write back into an EHR, so if you need the note to land automatically inside an enterprise system, weigh that gap. For a solo counselor or a group practice that just wants the documentation load off their evenings, a scribe that drafts a clean DAP note and keeps none of your audio is a straight win.

The way to know is to grade a real note. <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to watch a DAP note appear about two minutes after a sample session, then run the 7-day free trial on your own caseload and put three real notes through the six-point checklist above. If a tool can't produce a sign-ready DAP note on your hardest session, no time-saved number will rescue it.

---

## BIRP Notes Explained: Format, Example, and What to Verify
https://patientsquare.com/us/blog/birp-note/
Published 2026-03-20 · Tags: birp-note, note-format, behavioral-health, documentation

What BIRP stands for, what each section carries, an AI-generated example you can grade, and what to verify before a scribe drafts your notes.

BIRP stands for Behavior, Intervention, Response, and Plan. It is a structured progress-note format used in behavioral health, substance-use counseling, and case management. Behavior is what the client presents, Intervention is what you did in session, Response is how they reacted, and Plan is what happens next. It is one optional format, not a legal requirement.

A BIRP note organizes a behavioral-health session into four sections: Behavior, Intervention, Response, and Plan. Behavior is what the client presents, Intervention is what you did about it, Response is how they reacted, and Plan is what comes next. It is one of several optional progress-note formats, not a rule HIPAA or your license board imposes. What sets it apart from SOAP and DAP is that it pulls your method and the client's reaction into their own named sections.

This is the part most write-ups skip: BIRP isn't a standard anyone hands down to you. It's a habit that stuck because the four sections make medical necessity easy for a reviewer to read. If you bill Medicaid or work in community behavioral health, you've probably been asked for it. Below is what each section carries, an AI-generated example you can actually grade, and the single thing worth checking before you let a scribe write these for you.

> **Key takeaways**
>
> - BIRP = Behavior, Intervention, Response, Plan. It separates what you did from how the client responded, which SOAP and DAP don't.
> - No law requires it. HIPAA mandates no note format; some payers and Medicaid programs prefer BIRP because medical necessity reads cleanly off the four sections.
> - The Intervention and Response sections are where an AI scribe most often drifts, because both need clinical judgment, not transcription.
> - 93% of behavioral-health workers reported burnout in a 2023 survey of 750, and 68% of those in direct care said paperwork takes time from clients.
> - Grade a scribe on a real session against a fixed checklist, not a scripted demo.

## What does each section of a BIRP note carry?

Before you can tell a good BIRP note from a padded one, get clear on what each letter is for. The structure, per clinician documentation guides like ICANotes, breaks a session into four parts that build on each other.

**Behavior** is what the client brings into the room. Presenting symptoms, mood, affect, appearance, risk factors, and your own observations, both what they say and what you see. This is the closest BIRP gets to a combined Subjective-plus-Objective view. A suicide-risk statement, a missed-medication admission, a flat affect: all Behavior.

**Intervention** is what you did about it. The specific technique, not a vague gesture at "supportive therapy." A cognitive restructuring exercise, a motivational-interviewing reflection, a grounding skill you taught, psychoeducation about the medication. This section is the heart of BIRP and the reason payers like it, because it shows you delivered a clinical service, not just a conversation.

**Response** is how the client reacted to that intervention. Engagement level, movement toward a treatment goal, a symptom that shifted, a direct quote. "Client was able to identify two cognitive distortions and appeared less tearful by the end of the session" is a Response. It's the section that proves the intervention landed, or didn't.

**Plan** is what happens next. Homework, the next appointment, a referral, a treatment-plan update, a risk-management step, what you'll focus on next time. A dropped Plan item is a missed action, so completeness here matters as much as it does in any note.

The thing to notice: Intervention and Response are a matched pair. One records your move, the other records the result. That pairing is BIRP's whole point, and it's also the part that's hardest to fake.

## How is BIRP different from DAP and SOAP?

All three are progress-note formats, and none is required. The difference is where each one draws its lines.

| Format | Sections | What it emphasizes | Where it fits |
|---|---|---|---|
| **SOAP** | Subjective, Objective, Assessment, Plan | Splits the client's report from your observations, then your judgment | The cross-discipline default; the only one with a standalone **Assessment** |
| **DAP** | Data, Assessment, Plan | Folds report and observation into one Data block; fastest to write | Solo and private practice that wants speed |
| **BIRP** | Behavior, Intervention, Response, Plan | Separates **what you did** from **how the client reacted** | Medicaid, substance-use treatment, group and community behavioral health |

SOAP is what most clinicians trained on and what most AI scribes draft into by default. Its Assessment section is the one piece BIRP doesn't carry as a separate heading; in BIRP your clinical reasoning tends to live inside Behavior and Response instead. DAP is the streamlined cousin, one Data section instead of two, and tends to win when speed matters more than showing your method.

BIRP earns its place when you have to show a reviewer that a billable intervention happened and worked. That's why it shows up in managed care and Medicaid documentation, per clinician references like ICANotes. If your payer mix or your agency leans that way, BIRP isn't busywork, it's the structure that gets the claim paid.

One honest note, because it matters for how you read every vendor page on this topic: the format you use is mostly your call or your employer's. ICANotes, a behavioral-health EHR vendor, is clear that BIRP is not universally required by payers; what's required is that your note support medical necessity, the treatment goal, the intervention, and client progress. SAMHSA's documentation guidance for substance-use counseling, the 2023 TIP 65, talks about documenting counseling approaches but does not hand down the BIRP acronym as a mandate. So don't let anyone sell you BIRP as a compliance rule. It's a good tool that happens to make compliance easier to demonstrate.

## What does a good AI-generated BIRP note look like?

Here's the part you can use today. Below is a BIRP note an ambient scribe might draft from a routine 50-minute individual session, the kind of output you should expect to review and lightly edit, not rewrite. It's an illustrative example we wrote to show the shape, not a real client.

> **Behavior:** Client presented on time, well-groomed, with constricted affect and a depressed mood she rated 6/10. Reported two nights of poor sleep this week and a conflict with her sister that "set everything off." Denied suicidal ideation when asked directly. Continued to take sertraline as prescribed with no reported side effects.
>
> **Intervention:** Used cognitive restructuring to examine the automatic thought "I always make things worse." Walked through a thought record identifying the evidence for and against the belief. Provided psychoeducation on the link between sleep disruption and mood reactivity.
>
> **Response:** Client engaged actively and was able to generate two pieces of disconfirming evidence with prompting. She identified the all-or-nothing pattern in the thought herself and appeared less tearful by session's end, re-rating her mood at 4/10. Stated the sleep-mood connection "actually makes sense."
>
> **Plan:** Client to complete one thought record before the next session and resume a 10 p.m. wind-down routine. Continue sertraline at the current dose. Follow-up individual session in one week. Next session will focus on sleep hygiene and the sibling relationship.

Read that and notice what makes it work. The Behavior section reports without interpreting. The Intervention names a specific, billable technique. The Response ties directly back to that intervention, the thought record, the mood re-rating, with a client quote. And the Plan is concrete enough to act on. A weak scribe blurs these lines: it puts your intervention in the Behavior section, or writes a Response that just restates symptoms without connecting them to what you did.

This is also where you should be skeptical. A scribe can produce four labeled sections that look right and still be wrong inside them. The structure is the easy part. Getting the Intervention to match the actual technique you used, and the Response to reflect what genuinely shifted, is the hard part, and it's the part worth grading.

## What should you verify before a scribe drafts your BIRP notes?

Grade these on a real session you ran, not a vendor's demo reel. A scripted demo flatters every scribe; your messy Thursday afternoon sorts them out. Each point scores 0 to 2, so 0 fails, 1 is acceptable, 2 is good.

| # | What to check | What "good" looks like |
|---|---|---|
| 1 | **Section discipline** | Behavior, Intervention, Response, and Plan stay in their lanes. Your technique doesn't leak into Behavior; symptoms don't get mislabeled as Response. |
| 2 | **Intervention accuracy** | The named technique matches what you actually did. If you used motivational interviewing, the note says so, not a generic "provided support." |
| 3 | **Response fidelity** | The Response ties back to the Intervention and reflects what genuinely changed, not a recycled symptom list. |
| 4 | **No invented content** | Nothing in the note was added that didn't happen. No risk statement the client never made, no homework you never assigned. |
| 5 | **Plan completeness** | Every next step you decided is captured: homework, referral, follow-up, med continuation, focus for next time. |
| 6 | **Edit load** | You can correct the draft in about a minute. If cleanup takes longer than writing from scratch, it scores 0. |

A perfect score is 12. Below about 9 on your own sessions and you're buying cleanup, not time. Point 4 catches the most scribes, because a confident invented detail is worse than a blank line; you have to already know it's wrong to delete it. Points 2 and 3 are what separate a scribe that understands a therapy session from one that just transcribes one. The same logic powers our six-point [SOAP note quality rubric](../ai-scribe-soap-note-quality/) if SOAP is your house format.

## Why does BIRP note quality matter more than the time saved?

Because a bad note erases the time saving and leaves you exposed. In behavioral health it also touches a real workload problem.

A 2023 National Council for Mental Wellbeing survey, run by The Harris Poll across 750 behavioral-health workers, found 93% had experienced burnout and 62% rated it moderate or severe. A third of the workforce said they spend most of their time on administrative tasks, and 68% of those in direct care said that admin time takes away from time with clients. That's the case for a scribe in one paragraph: a tool that drafts the progress note while the session is fresh gives that time back.

But the math only holds if the note holds. A BIRP note with a hallucinated risk statement or an intervention you never used isn't a time saver; it's a liability you signed. For a behavioral-health practice the bigger question is what happens to the session recording, which we treat as the deciding factor in our [behavioral-health scribe guide](../ai-scribe-for-behavioral-health/). Note quality and audio handling are the two things to settle before features.

## Where an AI scribe fits with BIRP, and where it doesn't

Here's where we land, plainly. The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The default structure is SOAP, the format most clinicians and payers expect; if BIRP is your house format, the draft is yours to review and reshape into those four sections, and it should already carry the underlying content, the behavior, the intervention, the response, the plan. The note is always yours to read and approve.

For behavioral health specifically, the part that matters most isn't the section labels. It's the audio. Visit audio is processed in memory and discarded the moment the note is drafted; there's no recording to retain, train on, or subpoena. Notes are encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice, which can export or delete any visit at any time. We maintain HIPAA compliant safeguards and offer a BAA to every customer, and our SOC 2 Type II audit is underway. The full posture is on our [security page](../../security/).

Now the honest part. An ambient scribe is the wrong tool for some behavioral-health work, and we'll say so. If the recording itself would change the room, in trauma work, in early sessions, with a client who freezes at a running mic, skip it. Some clinicians also document reflectively, as part of how they think a session through, rather than by editing a transcript. That's a legitimate way to work, and no scribe improves on it. And if you need BIRP because a managed-care contract demands it section by section, confirm the draft maps cleanly to your four headings before you commit, since the tool drafts SOAP first.

## Grade a BIRP draft on a real session this week

The checklist above is only useful with a real note in front of you. A demo makes every scribe look fluent; your own caseload is the test that counts.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to watch a structured note appear about two minutes after a sample visit, then run the 7-day free trial on a few real sessions and grade three notes against the six points above. Check the Intervention and Response sections hardest, because that's where a therapy note lives or dies. If a tool can't clear about 9 out of 12 on your own sessions, no time-saved number will rescue it. For the wider buyer's view, our [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) scorecard turns this note grade into a full demo agenda.

---

## Therapy Notes Templates (and When to Stop Templating)
https://patientsquare.com/us/blog/therapy-notes-template/
Published 2026-03-19 · Updated 2026-07-22 · Tags: therapy-notes, progress-note, dap-note, birp-note, soap-note

Copy-paste SOAP, DAP, and BIRP progress note templates for therapists, what each section must carry to bill, and when a template stops saving you time.

There is no single best one. Most therapists pick DAP, BIRP, or SOAP. DAP is the leanest and works for talk therapy. BIRP ties each intervention to a client response, which payers like for medical necessity. SOAP carries a separate objective section that fits medication management. Pick the format your documentation already leans toward and use it for every note.

Pick a therapy progress note template by matching it to how you already document: DAP for lean talk-therapy notes, BIRP when you need a tight intervention-and-response trail for payers, SOAP when a session involves meds and a real objective section. All three sort the same session into different headings. Below you get a copy-paste template for each, the content every note needs to bill, and the honest part most template posts skip: where a template stops helping.

A blank template is still a blank box you fill in after a full caseload. It standardizes the shape of the note. It does nothing about the part that actually eats your evening, which is reconstructing what happened in a 50-minute session three clients ago. So we'll give you templates that are genuinely worth saving, then make the case for skipping the blank box entirely.

> **Key takeaways**
>
> - The three formats therapists use are DAP (Data, Assessment, Plan), BIRP (Behavior, Intervention, Response, Plan), and SOAP (Subjective, Objective, Assessment, Plan). Same content, different headings.
> - For Medicare billing, the note needs diagnosis, interventions, client response, and progress toward each goal, per LCDs L33252 and L34616. The template you pick is irrelevant to that.
> - A progress note is not a HIPAA psychotherapy note. CMS reimburses against the progress note; psychotherapy notes stay private and unsubmitted.
> - A 2023 National Council survey of 750 behavioral health workers found 93% had experienced burnout and a third spend most of their time on admin.
> - A template fixes the format. It doesn't fix the after-hours reconstruction. That's the line where templating stops paying off.

## Which therapy note template should you use: DAP, BIRP, or SOAP?

Start here, because the format argument is smaller than it looks. The three common templates carry the same clinical facts. They just label the buckets differently, and one will fit how you already write.

DAP is the leanest. It merges what the client reports and what you observe into a single Data section, then Assessment for your clinical reasoning and Plan for next steps. SimplePractice describes it as one of the current standard ways to write a psychotherapy note. If your notes are already mostly narrative, DAP fits with the least friction.

BIRP splits the room differently: Behavior, Intervention, Response, Plan. Its whole point is the middle two. You document the specific intervention you used, then the client's response to it. ICANotes frames BIRP as built for medical necessity and audit readiness, because that intervention-then-response pairing is exactly the thread a payer wants to see. If your work is reviewed often, BIRP makes the case for itself on the page.

SOAP keeps Subjective and Objective apart. Per the StatPearls reference, Subjective is the client's account, Objective is what you measure or observe, Assessment is the diagnosis, Plan is what happens next. The separate Objective section earns its keep when there's something measurable in the visit, vitals, a screener score, a medication change, which is why it's the default for psychiatry and medication management more than for pure talk therapy.

Here's the part that saves you re-reading three blog posts: they're interchangeable for most sessions. Pick one, use it for every note, and stop relitigating the choice each week.

| Format | Sections | Best fit | The tradeoff |
|---|---|---|---|
| **DAP** | Data, Assessment, Plan | Talk therapy, narrative documenters | Merges said and observed, so a strict reviewer sees less separation |
| **BIRP** | Behavior, Intervention, Response, Plan | Practices reviewed often; strong medical-necessity trail | More structure to fill on a quiet, low-intervention session |
| **SOAP** | Subjective, Objective, Assessment, Plan | Med management, anything with a measurable Objective | The Objective section is thin in pure talk therapy |

## The DAP therapy note template (copy-paste)

This is the artifact. Copy it, drop it in your EHR's note field, and fill the three sections. Brackets are prompts, not text to keep.

```
DATE: [date]   START-END: [clock time]   CPT: [code]   DX: [ICD-10 code + condition]

D — DATA
[Reason for today's session / presenting concern.]
[Client report: symptoms, mood, sleep, events since last session, in their words.]
[Observed: appearance, affect, engagement, mental status notes.]
[Screener or measure results, if any (e.g., PHQ-9 score).]
[Interventions used in session and the client's in-session response.]

A — ASSESSMENT
[Your clinical interpretation of the data above.]
[Progress toward each treatment-plan goal — name the goal, state the movement.]
[Any change in diagnosis, risk, or functioning. Risk assessment if relevant.]

P — PLAN
[Next session date/frequency. Homework assigned. Referrals.]
[Treatment-plan updates. Anything to follow up on next time.]

[Clinician name, credential, signature]
```

The Assessment section is the one to write carefully. "Client appeared anxious" is data. "Anxiety symptoms are improving in response to weekly exposure work, consistent with goal 2" is assessment, and it's the line that carries medical necessity. Every conclusion in Assessment should be visibly supported by something in Data, or a reviewer will flag the gap.

## The BIRP therapy note template (copy-paste)

Same session, four sections. BIRP earns its structure when you need the intervention-response link on the page.

```
DATE: [date]   START-END: [clock time]   CPT: [code]   DX: [ICD-10 code + condition]

B — BEHAVIOR
[Presenting symptoms, mood, affect, appearance.]
[Subjective: what the client reported. Objective: what you observed.]
[Risk factors noted, if any.]

I — INTERVENTION
[The specific techniques and clinical interventions you used this session.]
[Psychoeducation delivered. Treatment strategy applied.]

R — RESPONSE
[How the client responded to each intervention: engagement, symptom change.]
[Progress toward goals. Direct client feedback or quotes that show the response.]

P — PLAN
[Next steps: homework, referrals, follow-up.]
[Treatment-plan updates, risk-management plan, focus of next session.]

[Clinician name, credential, signature]
```

Notice the Intervention and Response sections are doing the medical-necessity work. A note that says you used a technique but never records whether it landed is the kind of gap that turns into a clawback on audit. BIRP forces the pairing, which is the entire reason reviewers and payers tend to like it.

## The SOAP therapy note template (copy-paste)

If your sessions touch medication or a measurable objective, SOAP's separate Objective section is the reason to use it.

```
DATE: [date]   START-END: [clock time]   CPT: [code]   DX: [ICD-10 code + condition]

S — SUBJECTIVE
[Chief complaint / focus. Client's account of symptoms, mood, events, in their words.]

O — OBJECTIVE
[What you observed and measured: mental status exam, affect, screener scores.]
[Medication adherence and side effects, if applicable. Vitals if taken.]

A — ASSESSMENT
[Diagnosis and clinical reasoning. Progress toward goals. Risk if relevant.]

P — PLAN
[Medication changes. Next session. Referrals, labs, follow-up. Homework.]

[Clinician name, credential, signature]
```

In a pure talk-therapy session the Objective section gets thin, which is the honest knock on SOAP for counseling. Keep it for the visits where you actually have objective data, and use DAP or BIRP for the rest. You're allowed to use different formats for different visit types.

## What every therapy note needs to bill, whichever template you pick

The format is cosmetic to a payer. The medical-necessity content is what gets the claim paid, and it's the same across DAP, BIRP, and SOAP.

For Medicare, CMS reimburses against the progress note and the treatment plan, per the Local Coverage Determinations governing psychotherapy (L33252 and L34616). Each note has to carry the service date and start-and-end times, the diagnosis matched to a covered condition, the type of therapy with its CPT code, a mental status finding, the specific interventions used, the client's response and any symptom change, progress toward each treatment-plan goal, and a signed credential within a day or two. Commercial payers track the same thread, diagnosis to intervention to measurable progress.

So if you're choosing a template hoping it'll fix a documentation gap, it won't. A template arranges the content. It doesn't generate the content. Whether you write "Response" or fold the response into your Data section, the reviewer is hunting for the same five things: a covered diagnosis, what you did, how the client responded, movement toward goals, and a signature.

| Required in the note | Where it lives in DAP | In BIRP | In SOAP |
|---|---|---|---|
| Diagnosis (covered condition) | Header / Assessment | Header / Behavior | Header / Assessment |
| Interventions used | Data | Intervention | Plan / Objective |
| Client response to intervention | Data | Response | Subjective / Objective |
| Progress toward each goal | Assessment | Response | Assessment |
| Signature + credential | Footer | Footer | Footer |

## The progress note is not your psychotherapy note

One distinction that trips people up, and it matters before you put anything sensitive into a template. The note these templates produce is the progress note: the billable chart note with diagnosis, interventions, and progress. Under HIPAA, that is explicitly not a "psychotherapy note."

HIPAA psychotherapy notes are your separate, private notes analyzing the session, kept apart from the chart, and they get heightened protection. CMS confirms they're not required for reimbursement and shouldn't be submitted to payers at all. The progress note is the thing a template, or a scribe, drafts. The psychotherapy note stays with you. We unpack what that means for privacy, audio, and 42 CFR Part 2 in the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/), which is worth reading before any vendor touches your session content.

## When to stop templating and start generating

Here's the opinion, stated as one. We think the blank template is a half-measure, and for a busy caseload the better move is to stop filling one from memory.

Think about the actual Tuesday. Seven clients, a no-show you rebooked, a crisis call that ran long. By the time you sit down to chart, session three is a blur and you're rebuilding it from a few scribbled words. The template told you to write Data, Assessment, Plan. It didn't tell you what the client said about their sleep, because you have to remember that. That reconstruction, multiplied across a full day, is how a 50-minute hour quietly becomes a 65-minute one and your notes follow you home.

The burden is well documented. In the 2023 National Council for Mental Wellbeing survey, run by Harris Poll across 750 behavioral health professionals between February 3 and 19, 93% reported burnout and 62% rated it moderate or severe. A third said they spend most of their time on administrative work, and 68% of those in direct care said that admin time takes away from time with clients. A blank template is not the answer to that. A note drafted from the session you just had is closer.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Instead of opening a blank DAP box at 7pm, you read a draft built from the actual conversation and edit it down. The template defines the shape you want; the scribe fills it from what was said, not from what you can still recall. You stay the clinician: you read the note, fix what's wrong, and sign it. Nothing gets billed that you didn't approve.

Two honest caveats, because the tool isn't right for every minute of this work. First, the recording is the sensitive part in therapy, more than the note ever is, so the audio question comes before the note-format question. Visit audio is processed in memory and discarded the moment the note is drafted; there's no archive. We made that the center of the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/) for a reason. Second, some sessions shouldn't have a mic running at all, and some clinicians document reflectively as part of how they think, not by editing a transcript. If that's your modality, a template you fill by hand is the right tool and a scribe is the wrong one. Match the tool to the work.

For everyone else carrying a full caseload, the templates above are a fine place to start and a better place to stop. <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a structured note appear about two minutes after a sample session, then run the 7-day free trial on a few real visits and compare the edit time against filling a blank template after hours. If the draft clears most of your note with a light edit, you've stopped templating. That's the point.

---

## DAP Note Examples by Diagnosis (Depression, Anxiety, PTSD)
https://patientsquare.com/us/blog/dap-note-example/
Published 2026-03-18 · Tags: dap-note, progress-notes, behavioral-health, therapy, documentation

Worked DAP note examples for depression, anxiety, PTSD, and substance use disorder, plus a Data-Assessment-Plan structure you can copy. Illustrative samples.

DAP stands for Data, Assessment, Plan. It is a three-section progress-note format used widely in behavioral health. Data is what happened in the session, including what the client reported and what you observed. Assessment is your clinical interpretation. Plan is what happens next. It is the therapy world's leaner cousin to the four-section SOAP note.

A DAP note has three parts. Data is what happened in the session, both what the client said and what you observed. Assessment is your clinical read on it. Plan is what happens next. It is the behavioral-health field's leaner take on the four-section SOAP note, and below you'll find worked examples for depression, anxiety, PTSD, and substance use disorder that you can copy as templates. Every example here is illustrative, written to show structure. None of them is a real patient.

A blank format guide only gets you so far. What you actually want, sitting down after a session, is a note that looks like the one you're trying to write, for the kind of presentation you just saw. So this is built as a set of diagnosis-specific samples, not a definition you have to translate yourself. Read the structure once, then jump to the example that matches your caseload.

> **Key takeaways**
>
> - DAP = Data, Assessment, Plan. It merges SOAP's Subjective and Objective into one Data section, so a session reads as one narrative instead of two boxes.
> - Data is description; Assessment is judgment. The diagnosis and your reasoning live in Assessment, against the DSM-5-TR.
> - The 4 examples below (depression, anxiety, PTSD, SUD) are illustrative clinician-style samples, not real patient records.
> - Documentation load in behavioral health is heavy: a 2023 National Council survey of 750 workers found 93% reported burnout, and 68% of those in direct care said admin time eats into client time.

## What is a DAP note, and what goes in each section?

DAP stands for Data, Assessment, and Plan. It's a progress-note format used widely across therapy, counseling, and behavioral-health work, and the appeal is that it fits how a session actually goes.

Here's the split, section by section.

**Data** is everything observable from the session. What the client reported in their own words, their mood and affect, behaviors you watched, symptoms, screener results, and the interventions you used. It's description, not interpretation. The test is one line: if it's a fact about what happened, it's Data.

**Assessment** is your clinical judgment about that data. The working diagnosis, progress toward goals, changes in symptoms or risk, and the reasoning that connects what you saw to what you think. This is the section that carries the medical necessity of the visit, and it's the one a model finds hardest, because it's reasoning, not transcription.

**Plan** is what happens next. Interventions for the next session, homework, medication or referral steps, the follow-up interval, and any safety planning. A dropped Plan item is a missed action, so completeness matters here more than polish.

| Section | What it holds | What it is not |
|---|---|---|
| **Data** | Client's reported experience, observed mood and behavior, symptoms, screener scores, interventions used in session | Your opinion or diagnosis |
| **Assessment** | Working diagnosis, clinical reasoning, progress toward goals, risk changes | A re-listing of the raw session facts |
| **Plan** | Next interventions, homework, referrals, follow-up interval, safety planning | Vague intentions with no timeframe |

## How is a DAP note different from a SOAP note?

The short version: SOAP has four sections, DAP has three, and the missing one is a merge, not a cut.

SOAP, per the [StatPearls reference](https://www.ncbi.nlm.nih.gov/books/NBK482263/), uses four headings: Subjective, Objective, Assessment, and Plan. The Assessment there is described as "the synthesis of subjective and objective evidence to arrive at a diagnosis," and the Plan covers further testing and referrals. DAP keeps Assessment and Plan unchanged and folds Subjective and Objective together into a single Data section.

Why therapists tend to reach for DAP: a talk-therapy session isn't a physical exam. There's no clean line between what the client "subjectively" reported and what you "objectively" measured, the way there is between a chief complaint and a blood pressure reading. Most of a session is conversation, observed and described together. One Data section captures that as a single narrative instead of forcing you to split a sentence in half. If you want the full anatomy of the four-section format and a rubric for grading any note, our [SOAP note quality guide](../ai-scribe-soap-note-quality/) covers it.

That's the whole difference. Same clinical logic, one fewer box. Now the part you came for.

## DAP note example: depression

Illustrative sample. Not a real patient. A 30-minute follow-up for an adult with major depressive disorder, four sessions in.

> **Data:** Client attended on time, alert, mildly disheveled. Reported mood as "flat, maybe a 3 out of 10" over the past two weeks, with low energy, early-morning waking around 4 a.m., and reduced interest in activities she previously enjoyed. PHQ-9 administered in session, score 16 (down from 19 at intake). Denied current suicidal ideation, plan, or intent when asked directly; reported passive thoughts that "things would be easier if I weren't here" twice in the past week, without intent. Discussed behavioral activation; client completed two of five planned activities from last session. Affect constricted, congruent with reported mood. Speech normal rate and volume.
>
> **Assessment:** Major depressive disorder, recurrent, moderate (DSM-5-TR). Symptoms improving modestly, supported by a 3-point PHQ-9 decrease and partial completion of behavioral-activation tasks. Passive ideation present without active risk; safety reassessed and judged low-acute. Engagement is adequate. Primary barrier remains low activation energy rather than insight.
>
> **Plan:** Continue weekly individual therapy. Increase behavioral-activation targets to five activities, scaffolded smaller to improve completion. Re-administer PHQ-9 in two weeks. Reassess passive ideation at each session and reinforce the safety plan on file. Coordinate with prescriber re: current antidepressant response at the next joint check-in. Next session in one week.

Notice what the Assessment does that the Data doesn't. The PHQ-9 score sits in Data as a fact. The interpretation, "improving modestly," lives in Assessment with the evidence attached. That separation is what makes the note defensible.

## DAP note example: anxiety

Illustrative sample. Not a real patient. A weekly session for generalized anxiety disorder.

> **Data:** Client reported a "high anxiety week," rating worry as 7 out of 10 most days, with difficulty concentrating at work and two episodes of racing heart and shortness of breath he identified as panic. GAD-7 score 14, unchanged from last week. Reported sleep onset delayed by racing thoughts, averaging five to six hours nightly. Practiced diaphragmatic breathing in session; client was able to bring subjective distress from 6 to 3 over four minutes. Reviewed cognitive-restructuring worksheet; client completed three of seven daily entries. Affect anxious, fidgeting, good eye contact.
>
> **Assessment:** Generalized anxiety disorder (DSM-5-TR). Symptom burden stable rather than improving, with a flat GAD-7 and continued sleep disruption. Client demonstrates capacity to down-regulate acute distress in session, which is a strength to build on, but is not yet generalizing the skill between sessions, reflected in low worksheet completion. The two panic episodes warrant monitoring but do not currently meet a separate panic-disorder threshold.
>
> **Plan:** Continue weekly CBT. Shift focus from new content to between-session practice, since the skill exists but isn't transferring. Assign one daily breathing practice at a fixed time rather than as-needed. Continue cognitive-restructuring worksheet, reduced to three entries to match realistic adherence. Screen for panic-disorder criteria next session if episodes persist. Re-administer GAD-7 in two weeks. Next session in one week.

## DAP note example: PTSD

Illustrative sample. Not a real patient. A trauma-focused session for posttraumatic stress disorder. Note the heightened attention to risk and to what is, and is not, recorded.

> **Data:** Client attended, guarded initially, settling over the session. Reported increased nightmares (four this week, up from two) and one flashback triggered by a car backfiring, lasting "a few minutes." Described avoidance of driving past the location of the index event. PCL-5 score 48. Reported hypervigilance and startle response as "worse than last month." Denied suicidal or homicidal ideation when asked directly. Engaged in a grounding exercise during a moment of elevated distress mid-session and recovered to baseline. Did not pursue trauma-narrative work this session by mutual agreement, given symptom elevation.
>
> **Assessment:** Posttraumatic stress disorder (DSM-5-TR), with an increase in re-experiencing and arousal symptoms over the past month, supported by a rising PCL-5 and client report. Avoidance cluster active and currently reinforcing. Risk assessed and judged low-acute today, though symptom escalation warrants close monitoring. Client's ability to use grounding mid-session is a meaningful regulatory strength. Pacing trauma-processing work down is clinically appropriate given current arousal levels.
>
> **Plan:** Hold trauma-narrative exposure until arousal stabilizes; prioritize stabilization and grounding skills next session. Add a sleep-hygiene and nightmare-management component. Reassess PCL-5 in two weeks. Reassess risk at every session while symptoms are elevated. Consider prescriber consult re: symptom escalation if no improvement in three weeks. Next session in one week.

For practices doing this work, two operational realities sit on top of the clinical note: how privacy rules apply, and what happens to any recording of the session. We cover both in the [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/), and the deeper psychiatry case in the [psychiatry privacy post](../ai-scribe-for-psychiatry-privacy/). In trauma work the recording is more sensitive than the note, so the audio question is the one to settle first.

## DAP note example: substance use disorder (SUD)

Illustrative sample. Not a real patient. An individual session for alcohol use disorder, client in early recovery.

> **Data:** Client reported 11 days of continuous sobriety, attending two mutual-support meetings this week. Described one significant craving on day 8, triggered by a social event, which he managed by leaving early and calling his sponsor. Reported improved sleep and appetite. Denied withdrawal symptoms. Discussed high-risk situations for the coming week, including a family gathering. Completed a relapse-prevention worksheet identifying three coping strategies. Affect brighter than prior sessions, engaged, future-oriented.
>
> **Assessment:** Alcohol use disorder, moderate, in early remission (DSM-5-TR). Eleven days of sobriety with active use of recovery supports is clear early progress. The craving on day 8 was managed adaptively, which demonstrates emerging coping capacity. The upcoming family gathering is a foreseeable high-risk situation; planning for it is the priority. No current indication of withdrawal risk requiring medical escalation.
>
> **Plan:** Continue weekly individual therapy alongside mutual-support attendance. Develop a specific written plan for the family gathering, including an exit strategy and a support contact. Reinforce the three coping strategies the client identified. Continue monitoring craving frequency and intensity. Reassess remission status against DSM-5-TR criteria monthly. Next session in one week.

A note on SUD documentation specifically: if your practice is a federally-assisted substance use disorder program, a separate confidentiality rule, 42 CFR Part 2, layers on top of HIPAA and changes how these records can be disclosed. The note structure doesn't change, but the handling does. The [behavioral-health privacy guide](../ai-scribe-for-behavioral-health/) walks through who that rule actually covers, because it's narrower than most assume.

## What separates a strong DAP note from a weak one?

Four things. They apply the same way when you write the note by hand or when you review one a tool drafted.

First, the Data and Assessment stay separate. The most common documentation slip is smuggling judgment into Data ("client was manipulative") or restating raw facts in Assessment with no interpretation added. Keep the line clean: facts down here, reasoning up there.

Second, the Assessment names a diagnosis and justifies it. For a covered behavioral-health visit, the working diagnosis against the DSM-5-TR, the standard diagnostic reference published by the American Psychiatric Association, plus the reasoning, is what supports medical necessity. A note that describes a session beautifully but never lands a clinical judgment is incomplete.

Third, the Plan is specific and time-bound. "Continue therapy" is not a plan. "Weekly CBT, shift to between-session practice, re-administer GAD-7 in two weeks" is. Each item should be something a covering clinician could act on without calling you.

Fourth, risk is addressed when it's relevant. In depression, PTSD, and SUD work especially, the note should show that risk was assessed and what you concluded, not leave it to inference.

## Why does the format matter when documentation is already eating your evenings?

Because the structure is the part you can standardize, and standardizing it is what makes the note faster to write and faster to defend.

The documentation load in behavioral health is well documented. A 2023 survey run by Harris Poll for the National Council for Mental Wellbeing, across 750 behavioral health workers, found that 93% had experienced burnout and 62% rated it moderate or severe. A third of the workforce said they spend most of their time on administrative tasks, and 68% of those providing direct care said that admin time takes away from time with clients. A 50-minute session followed by ten minutes of notes, repeated across a full day, is how a caseload turns into evening charting.

A consistent DAP structure helps two ways. It speeds the writing, because you're filling known sections instead of staring at a blank page. And it's where an AI scribe can take the first pass, drafting the Data section from the conversation and proposing an Assessment and Plan you then correct, rather than typing from scratch. The format is what makes that hand-off clean: a tool that knows it's writing into Data, Assessment, and Plan produces something you can review section by section.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The note itself is still yours to read, correct, and sign; the diagnosis and the clinical reasoning are your call, not the model's. What it removes is the blank page.

## Use these examples, then grade a real note

The fastest way to judge whether a format or a tool works for you is to run it on your own caseload, not a sample.

Copy the example above that matches your next session as a starting template, write the note, and check it against the four marks: Data and Assessment separated, a named diagnosis with reasoning, a specific time-bound Plan, and risk addressed where it's relevant. If you're evaluating an AI scribe to take the first pass, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> to watch a structured note appear about two minutes after a sample visit, then run the 7-day free trial and grade three real notes the same way. For the full grading rubric that turns this into a buyer's scorecard, see our [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) guide, and the [SOAP note quality](../ai-scribe-soap-note-quality/) post if your setting uses the four-section format instead.

One more time, because it's the rule that keeps this page useful and safe: every DAP note above is an illustrative, clinician-style sample. None describes a real person. Write yours from the visit in front of you.

---

## BIRP Note Examples by Presenting Problem
https://patientsquare.com/us/blog/birp-notes-examples/
Published 2026-03-17 · Tags: birp-note, behavioral-health, progress-notes, documentation

Illustrative BIRP note examples for depression, panic, PTSD, alcohol use, and more, plus what a payer auditor checks before a behavioral-health note gets paid.

BIRP stands for Behavior, Intervention, Response, and Plan. Behavior is the client's presentation and symptoms for the session. Intervention is what you did and why. Response is how the client reacted to it. Plan is the next step. It is a standard behavioral-health progress-note format used by counselors, social workers, psychologists, and psychiatrists.

A BIRP note records four things in order: Behavior (what you observed and the client reported), Intervention (what you did and why), Response (how the client reacted), and Plan (the next step). Below are illustrative BIRP examples for the presenting problems clinicians actually chart, depression, panic, PTSD, alcohol use, and more, each written to show the format, not to be copied into a real chart.

These are teaching samples. They're composites, not real sessions, and every line is the kind of thing you'd write, not a record to paste. Read one in your own area, see how the four sections hang together, then write yours from the actual visit. The point of a worked example is the shape, not the words.

> **Key takeaways**
>
> - BIRP = Behavior, Intervention, Response, Plan. The Intervention and Response sit side by side, which is the whole reason behavioral-health clinicians use it.
> - The examples below cover 6 presenting problems. They're illustrative composites, written to show the format, not to be copied verbatim.
> - A payer auditor reads a BIRP note for one thing: medical necessity. Symptom, intervention, response, and the link to a treatment-plan goal.
> - CMS Medicare guidance flags copy-pasted notes that read identically across sessions. Each note has to be its own.
> - 93% of behavioral health workers reported burnout in a 2023 survey of 750; 68% in direct care said paperwork eats into client time. The format isn't the burden. The volume is.

## What goes in each BIRP section?

Before the examples, get the four buckets straight, because the most common mistake is letting them bleed into each other.

**Behavior** is the client's presentation for this session. Mood, affect, appearance, what they report, risk if any. It's both what you observe and what they tell you, written plainly. **Intervention** is what you did, and ideally why: the modality, the specific technique, the question you asked and your reason for asking it. This is the section a weak note skips, and it's the one an auditor reads first. **Response** is how the client reacted to that intervention. Engaged, resisted, had an insight, shut down. A direct quote earns its place here. **Plan** is the next step: homework, the focus for next time, a referral, a screening, a frequency change.

| Section | What it carries | The common mistake |
|---|---|---|
| **Behavior** | Presentation, mood, affect, reported symptoms, risk | Burying your interpretation in here instead of in Response |
| **Intervention** | What you did and why, the modality and technique | Writing "supportive therapy provided" and nothing else |
| **Response** | How the client reacted to the intervention | Leaving it out, so the note can't show the session worked |
| **Plan** | Next step, homework, frequency, referrals | A generic "continue treatment" with no goal link |

The format itself is standard across behavioral-health settings; counselors, LCSWs, psychologists, and psychiatrists all chart this way. A clean BIRP note and a thin one have the same four headings. What separates them is whether the Intervention and Response actually connect.

## BIRP note examples by presenting problem

Here's the artifact. Six illustrative notes, one per presenting problem, each a composite written to show the format. They are not real patient records, the names and details are invented, and they're deliberately short so the four sections stay visible. Use them as a model for shape and depth, then document your own session.

### Major depressive disorder

> **B:** Client presents with flat affect and slowed speech. Reports low mood "most days," early-morning waking, and loss of interest in running, which she previously did four times a week. Denies suicidal ideation when asked directly. PHQ-9 administered, score 16 (moderately severe).
>
> **I:** Behavioral activation introduced. Reviewed the link between activity and mood, and worked with client to schedule one valued activity before the next session. Explored barriers to resuming exercise.
>
> **R:** Client engaged with the rationale and identified a 15-minute morning walk as a realistic first step. Stated, "I can probably do that on the days I'm already up early." Affect brightened slightly when planning it.
>
> **P:** Client to attempt the scheduled walk at least three times before next session. Re-administer PHQ-9 in two weeks. Continue weekly individual therapy per treatment plan goal of restoring daily functioning.

### Panic disorder

> **B:** Client reports three panic attacks since the last session, two while driving. Describes chest tightness, derealization, and a fear of "losing control." Appeared anxious, fidgeting, speech pressured early in the session.
>
> **I:** Delivered psychoeducation on the panic cycle and the role of catastrophic interpretation. Practiced diaphragmatic breathing in session and introduced interoceptive exposure rationale.
>
> **R:** Client completed the breathing exercise and reported a drop in subjective anxiety from 8/10 to 4/10. Voiced doubt that exposure "would be safe," which we addressed directly.
>
> **P:** Client to practice breathing twice daily and log panic triggers. Begin graded interoceptive exposure next session. Goal: reduce attack frequency to fewer than one per week.

### Post-traumatic stress disorder

> **B:** Client reports intrusive memories and nightmares three to four nights this week, hypervigilance in crowded spaces, and avoidance of the route past the incident site. Affect constricted. Denies current suicidal ideation; safety reviewed.
>
> **I:** Continued trauma-focused CBT. Reviewed the avoidance hierarchy and supported the client through an imaginal exposure exercise focused on a previously avoided memory.
>
> **R:** Client tolerated the exposure with prompting and reported peak distress of 7/10, down from 9/10 two sessions ago. Tearful but able to ground and remain present. Said the memory "felt less stuck" afterward.
>
> **P:** Client to continue the in-vivo step of driving one block toward the avoided route. Next session: process the exposure and advance the hierarchy. Goal: reduce avoidance and re-engage daily routine.

### Alcohol use disorder

> **B:** Client reports drinking five to six days this week, down from daily, with two days fully abstinent. Identifies evenings alone as the highest-risk time. Appeared motivated, made good eye contact. CIWA not indicated; no acute withdrawal signs.
>
> **I:** Used motivational interviewing to reinforce change talk around the two abstinent days. Reviewed the decisional balance and collaborated on an evening-routine plan as a relapse-prevention strategy.
>
> **R:** Client elaborated on the abstinent days unprompted and said, "I felt better the next morning, that's the part I want." Receptive to building an alternative evening routine. Some ambivalence about social drinking remained.
>
> **P:** Client to plan two specific alternative evening activities and track drinks daily. Continue weekly sessions. Goal per treatment plan: reduce use and extend abstinent days.

### Borderline personality disorder

> **B:** Client arrived distressed after a conflict with a partner, describing fear of abandonment and an urge to text repeatedly. Reports one episode of urge to self-harm earlier in the week, no action taken. Affect labile, shifting within the session.
>
> **I:** Applied DBT skills coaching. Reviewed distress tolerance, specifically the TIPP skill, and validated the emotional intensity while distinguishing the urge from the action. Reinforced use of the existing safety plan.
>
> **R:** Client identified that she had used a paced-breathing skill during the self-harm urge and it "helped a little." Able to name the abandonment fear as a trigger rather than a fact. Calmer by the end of the session.
>
> **P:** Client to complete a diary card daily and practice TIPP at the next high-distress moment. Review the safety plan next session. Goal: increase skill use during crises, reduce self-harm urges.

### Generalized anxiety with ADHD

> **B:** Client reports persistent worry about work performance and trouble completing tasks, describing "starting ten things and finishing none." Restless, shifted topics frequently. Denies safety concerns. Notes worry is worst on unstructured days.
>
> **I:** Combined cognitive restructuring for the worry with practical executive-function support. Worked on breaking one work task into three steps and externalizing it to a written list. Examined the "if I don't worry, I'll fail" belief.
>
> **R:** Client found the task-breakdown "obvious but I never actually do it" and committed to trying it on one project. Could generate a more balanced thought about performance with coaching, less so independently.
>
> **P:** Client to use the three-step breakdown on one task daily and capture worries in a scheduled worry window. Next session: review and adjust. Goal: reduce functional impairment from worry and disorganization.

A note on these: every one pairs a specific Intervention with a specific Response, and every Plan points at a treatment-plan goal. That pairing is the part that holds up. A note that says "processed feelings, client felt better, continue treatment" has all four letters and documents nothing.

## What does a payer auditor actually check?

Medical necessity. That's the single lens. A behavioral-health note gets paid when it shows why this client needed this session, and BIRP is built to show exactly that.

Per CMS Medicare contractor guidance (Noridian's mental-health documentation requirements), a payable note carries the symptoms that justify care, the modality and intervention delivered, the client's response, the treatment plan with updates, and the session start and stop times. CMS guidance also prohibits cloned notes, the kind that read word-for-word identically across sessions or clients. Clinicians sometimes call the through-line a "golden thread": symptom to intervention to response to goal, traceable across every note. BIRP makes that thread easy to follow because the Intervention and Response are already adjacent.

The two sections people skimp on, Intervention specificity and a Response tied to a goal, are the two an auditor weighs most. A blank field is at least honest. A vague one ("client tolerated session well") just looks like documentation, and a reviewer can tell the difference.

## BIRP vs DAP vs SOAP: pick the format by setting

They're not interchangeable, and the choice usually comes down to the setting.

SOAP, per the StatPearls reference, separates Subjective from Objective before the Assessment and Plan. That split earns its keep in medical visits with exam findings and vitals, which is why our [SOAP-note quality rubric](../ai-scribe-soap-note-quality/) is framed for general clinical notes. DAP collapses Subjective and Objective into one Data section, then Assessment and Plan, which suits a talk-therapy session where there's no exam to separate out. BIRP goes further for behavioral health by pulling the Intervention and the client's Response into their own sections, side by side.

| Format | Sections | Fits best |
|---|---|---|
| **SOAP** | Subjective, Objective, Assessment, Plan | Medical visits with exam findings and measurements |
| **DAP** | Data, Assessment, Plan | Talk-therapy sessions; simpler, fewer sections |
| **BIRP** | Behavior, Intervention, Response, Plan | Behavioral health where you need to show the intervention worked |

Our honest take: if you're documenting psychotherapy and your payer cares about medical necessity, BIRP is the strongest default, because it forces the intervention-and-response pairing that a reviewer is hunting for. DAP is lighter and fine for lower-stakes notes. SOAP is the wrong tool for a therapy hour and the right one for a medical visit.

## How an AI scribe drafts a BIRP note

The format is the easy part. The volume is what burns people out. In a 2023 National Council for Mental Wellbeing survey of 750 behavioral health workers, 93% reported burnout and 68% of those in direct care said administrative time takes away from clients. Picture a Thursday with eight sessions back to back and the notes still unwritten at 7pm. That's the problem a scribe is actually solving, and it's not the four letters.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For behavioral health it can draft into a BIRP layout instead, sorting the session into Behavior, Intervention, Response, and Plan, with the ICD-10 codes offered as suggestions you confirm. You read and sign every note, because a model can mishear a medication, fold two issues into one, or miss the goal link that makes the note payable. It removes the typing, not the judgment.

One thing to settle before any therapy scribe, ours included: what happens to the audio. In a therapy room the recording holds far more than the note ever will, and a vendor that keeps it has created something a court can later reach. AI Medical Scribe by Patient Square processes audio in memory and never stores it; once the note is drafted, the recording is gone. We walk through the full set of behavioral-health privacy questions in the [behavioral-health scribe guide](../ai-scribe-for-behavioral-health/), and the [psychiatry privacy guide](../ai-scribe-for-psychiatry-privacy/) covers the medication-management side if that's your practice.

## Try it on a real session, not a sample

These examples show the shape. Your own caseload is the real test, the labile client, the one who buries the actual issue in the last five minutes, the session that ran long.

<a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">Explore the workflow</a> to watch a structured note appear about two minutes after a sample visit, then run the 7-day free trial and draft a few BIRP notes from your own sessions. Grade them the way an auditor would: is the intervention specific, is the response tied to a goal, could you sign it in about a minute? If a draft can't clear that on your hardest session, no time-saved number will fix it. For the wider buyer's view, our [behavioral-health scribe guide](../ai-scribe-for-behavioral-health/) starts with the privacy questions that matter most, and you can compare what we charge on the [pricing page](../../pricing/) before you commit.

---

## Psychotherapy Note Examples, Written by Clinicians
https://patientsquare.com/us/blog/psychotherapy-notes-examples/
Published 2026-03-16 · Updated 2026-07-22 · Tags: psychotherapy-notes, therapy-notes, progress-note, documentation, behavioral-health

Worked therapy progress note examples in SOAP, DAP, BIRP, intake, group, and risk formats, plus the HIPAA psychotherapy-notes distinction therapists get wrong.

Under HIPAA, a psychotherapy note is the clinician's separately-kept note documenting or analyzing the content of a counseling session. It must be kept apart from the rest of the record and gets heightened protection: releasing it almost always needs the patient's specific authorization. It is not the same thing as the progress note that goes in the chart.

A psychotherapy note has a precise meaning under HIPAA: it's the note you keep separate from the chart, documenting or analyzing what happened in a session, and it gets heightened legal protection. That's different from the progress note you sign and share. Below are worked examples of both, written the way a clinician actually writes them, across the formats you'll really use.

Most "psychotherapy note examples" you find online quietly blur that distinction, which matters more in this field than almost any other. So we'll fix the definition first, in two short paragraphs, then get to the notes. Every example here is illustrative. No real patient, no real session.

> **Key takeaways**
>
> - HIPAA defines a "psychotherapy note" narrowly: the clinician's separate process note about a session, with heightened protection. Releasing it almost always needs a specific authorization (45 CFR 164.508).
> - The note you sign and bill is the progress note. It can be shared with insurers and providers and follows ordinary disclosure rules.
> - 5 of the worked examples below are progress notes (SOAP, DAP, BIRP, intake, group). 2 are the rarer kinds: a risk note and a true HIPAA psychotherapy note.
> - The format barely matters to a reviewer. What matters is that risk, the intervention, the client's response, and the plan are all there.
> - An AI scribe drafts the progress note, not your private process notes. Ask what it does with the audio first.

## What HIPAA actually means by "psychotherapy notes"

Here's the distinction that trips up careful clinicians. Under the HIPAA Privacy Rule, a "psychotherapy note" is a specific thing: notes recorded by a mental health professional "documenting or analyzing the contents of conversation during a private counseling session" that are "separated from the rest of the individual's record" (45 CFR 164.501). Those notes get heightened protection. With few exceptions, you need the patient's specific written authorization to disclose them, even to another treating provider, and that authorization can't be bundled with a general one (45 CFR 164.508; HHS OCR FAQ 2088).

The regulation is just as specific about what is *not* a psychotherapy note. It expressly excludes medication prescription and monitoring, session start and stop times, the modalities and frequencies of treatment, results of clinical tests, and any summary of diagnosis, functional status, treatment plan, symptoms, prognosis, and progress to date (45 CFR 164.501). All of that lives in the regular record. The APA's Record Keeping Guidelines put it the same way: the clinical record holds the presenting complaint, diagnosis, treatment plan, and the nature of each intervention, while psychotherapy notes "are necessarily kept apart from other parts of the record." So the everyday note documenting a session, the one you bill from and might send to an insurer, is a *progress note*, not a HIPAA psychotherapy note. Two different documents, two different rule sets. Most of what people call a "psychotherapy note example" online is actually a progress note. We'll show you both, clearly labeled.

## Progress note vs. psychotherapy note: which rules apply

Before the examples, one table to anchor the difference. This is the thing to get right.

| | Progress note | Psychotherapy note (HIPAA) |
|---|---|---|
| **What it is** | The official session note in the chart | The clinician's separate process note |
| **Typical contents** | Presenting concern, MSE/risk, intervention, response, assessment, plan | Your analysis, hypotheses, reactions, raw session detail |
| **Where it's kept** | In the medical record | Physically/logically separate from the record |
| **Shared with insurers/providers?** | Yes, follows ordinary HIPAA disclosure rules | Almost never, without specific authorization |
| **Authorization to release** | General consent / TPO rules | A separate, standalone authorization (45 CFR 164.508) |
| **Does an AI scribe draft it?** | Yes, this is what a scribe produces | No, this stays yours to write or skip |

The practical upshot: if you keep separate process notes at all (many clinicians don't), keep them genuinely separate and don't paste protected content into the chart. The note that follows the patient through billing and referrals is the progress note. That's what the next five examples are.

## Example 1: SOAP progress note (anxiety, individual therapy)

SOAP, per the StatPearls reference, is a widely used documentation format: Subjective, Objective, Assessment, Plan. Plenty of therapists and psychiatric prescribers write progress notes in it. Illustrative note for a fictional 34-year-old client, fourth session for generalized anxiety:

> **S:** Client reports anxiety "a little more manageable" this week, sleeping 5–6 hrs (up from 4). Used the box-breathing practice twice before work meetings, found it "helped a bit." Still avoiding driving on the highway. Denies SI/HI. No new stressors reported.
>
> **O:** Alert, oriented x4. Mood "okay," affect mildly anxious, congruent. Speech normal rate/volume. No psychomotor agitation. Engaged, completed between-session homework. No evidence of thought disorder.
>
> **A:** GAD, ongoing, with modest symptom improvement. Sleep trending up; daytime avoidance of driving persists and remains the primary functional impairment. Good engagement with CBT skills.
>
> **P:** Continue weekly CBT. Introduce graded exposure hierarchy for highway driving next session. Reassign box-breathing daily. Continue sleep-hygiene plan. Return 1 week.

What makes this a competent note: risk is addressed explicitly (denies SI/HI), the intervention is named (CBT, box-breathing), the client's response is concrete (5–6 hrs of sleep, not "doing better"), and the plan has a specific next step. Notice it contains nothing that would qualify as a HIPAA psychotherapy note. It's shareable, billable, and clean.

## Example 2: DAP progress note (depression, telehealth)

DAP, Data-Assessment-Plan, emerged as a streamlined format for behavioral health, folding the patient report and your observations into a single Data section. Useful when the subjective/objective split feels forced for talk therapy. Illustrative note, fictional client, sixth telehealth session for major depressive disorder:

> **D:** Client joined on time, camera on, in their kitchen. Reported a "flat" week but completed two of three scheduled behavioral-activation tasks (walk, called a friend; skipped the gym). Described low motivation on weekend. PHQ-9 self-reported at 11, down from 14 two weeks ago. Denied SI, denied any active plan or intent. Discussed automatic thought "nothing I do matters" and identified evidence against it.
>
> **A:** MDD, moderate, improving. Behavioral activation producing measurable gains; PHQ-9 down 3 points. Cognitive distortions present but client now able to challenge them with prompting. No acute risk.
>
> **P:** Continue weekly telehealth. Add one pleasurable-activity task to BA schedule. Begin thought-record worksheet for the "nothing matters" belief. Re-administer PHQ-9 in 2 weeks. Confirmed crisis line and local ED instructions on file.

The DAP "Data" section carries both what the client said and what you observed, which is why many therapists prefer it. The risk check, the measured instrument (PHQ-9 with a real delta), and the safety-plan line are what a chart auditor or a payer wants to see.

## Example 3: BIRP progress note (PTSD, individual)

BIRP, Behavior-Intervention-Response-Plan, puts your intervention and the client's response front and center, which makes it a favorite in settings where demonstrating active treatment matters. Illustrative note, fictional veteran client, individual session for PTSD:

> **B:** Client presented anxious, reported two nightmares this week and one flashback triggered by a car backfiring. Hypervigilant in session, scanned the room twice. Reported avoiding crowded stores. "I'm functioning, but I'm exhausted."
>
> **I:** Conducted psychoeducation on trauma triggers and the fight/flight response. Practiced grounding (5-4-3-2-1 sensory) in session. Began constructing a graded in-vivo exposure list for avoided situations.
>
> **R:** Client engaged well with grounding, reported anxiety dropping from 8/10 to 5/10 during the exercise. Receptive to exposure rationale, expressed some apprehension about starting with grocery stores.
>
> **P:** Continue weekly trauma-focused work. Client to practice grounding daily and log triggers. Begin lowest-anxiety exposure item next session. Reassess PCL-5 in 3 weeks. No SI/HI; safety plan reviewed and current.

BIRP's strength is that the "Response" section forces you to document whether the intervention worked, the 8/10 to 5/10 detail here. That single line is often what distinguishes a defensible note from a vague one.

## Example 4: Intake / initial evaluation note

The first note is its own animal. It establishes the presenting problem, history, diagnosis, and the initial plan, the spine the APA guidelines say the clinical record should carry. Trimmed illustrative excerpt, fictional client:

> **Presenting concern:** 28-y/o self-referred for "panic attacks" over the past 3 months, escalating after a job change. 2–3 episodes/week, peak intensity ~10 min, with chest tightness, derealization, fear of "losing control."
>
> **Relevant history:** No prior psychiatric treatment. No current medications. Family hx of anxiety (mother). Denies substance use beyond occasional alcohol. No trauma history disclosed at intake.
>
> **Mental status:** Cooperative, anxious affect, linear thought, no perceptual disturbance, insight fair, judgment intact. Denies SI/HI at intake.
>
> **Assessment / diagnosis:** Panic disorder (provisional). Rule out GAD; screen for caffeine contribution.
>
> **Initial plan:** Weekly individual CBT, 8–12 sessions. Psychoeducation on panic cycle session 1. Coordinate re: possible PCP referral for medical workup of cardiac symptoms. Administer GAD-7 and PDSS at next visit.

An intake note is longer on purpose. It's the record's foundation, and a thin one creates problems later, for treatment planning, for the next clinician, and for any payer review. Note again: this is the progress/clinical record, not a psychotherapy note.

## Example 5: Group therapy progress note

Group notes have a wrinkle. You document the individual client's participation and response, not a transcript of the room, and you don't name other members. Illustrative note, fictional client, week 5 of an 8-week DBT skills group:

> **Group/session:** DBT skills group, week 5 (Emotion Regulation module). Client attended full 90 min.
>
> **Participation:** Client arrived on time, shared a homework example of using "opposite action" during a conflict with a roommate. Volunteered twice, listened actively, no disruptive behavior. Appeared more comfortable than in prior weeks.
>
> **Response/assessment:** Client demonstrating growing skill uptake; able to apply opposite action to a real situation with a reasonable outcome. Affect brighter than week 1. No acute concerns observed; denied SI when checked individually at close.
>
> **Plan:** Continue group through module completion. Client to complete distress-tolerance homework. Individual therapist to reinforce emotion-regulation skills in 1:1. Next group in 1 week.

The discipline here is confidentiality: one client's note never identifies another. A scribe drafting group notes has to respect that boundary too, which is a fair question to put to any vendor.

## Example 6: Risk / safety note (suicidal ideation)

When risk is present, the note changes shape. It becomes the most important document you write that day, and it should read like you took the risk seriously and acted on it. Illustrative note, fictional client presenting with passive SI:

> **Risk presentation:** Client reported passive suicidal ideation this week ("sometimes I think it'd be easier not to wake up"), denied active intent, denied plan, denied means. Ideation tied to acute relationship loss. No prior attempts. Protective factors: strong relationship with sister, religious belief against suicide, future-oriented (mentions a planned trip).
>
> **Assessment:** Passive SI without plan or intent in the context of acute grief. Risk judged low-to-moderate, primarily driven by recent loss. Protective factors substantial and credible.
>
> **Intervention:** Conducted collaborative safety planning. Identified warning signs, internal coping strategies, sister as a support contact, and crisis line (988). Means-restriction discussion: no firearms in home, confirmed. Client agreed to safety plan and to contact provider or 988 if ideation intensifies.
>
> **Plan:** Increase to twice-weekly sessions for 2 weeks. Provided 988 and local crisis resources in writing. Client verbalized understanding and willingness to use them. Follow-up call scheduled in 48 hrs to check in.

A risk note documents the assessment, the safety plan, the means-restriction conversation, and the follow-up. The format is secondary. Whether those elements are present is what gets reviewed, in quality audits and, in the worst case, in litigation. This is exactly the kind of note where an AI scribe earns trust or loses it: it has to capture the risk language faithfully and never soften or drop it.

## Example 7: A true HIPAA psychotherapy note (process note)

Finally, the rare one: an actual psychotherapy note as HIPAA defines it. This is your private analysis of the session, kept apart from the chart, never billed, and protected by the separate-authorization rule. It reads nothing like the progress notes above. Illustrative excerpt:

> Working hypothesis: the panic seems less about the job change itself and more about a re-activation of the early experience of being "the one who holds it together" at home. The somatic fear of losing control may be a stand-in for an old, unspoken fear of being needed and then abandoned. Countertransference note: I felt a pull to reassure quickly today, worth watching. Consider whether my reassurance is colluding with the avoidance. Explore the mother's anxiety and the client's role as caretaker next session, gently.

See the difference. There's no diagnosis summary, no plan in billable form, no MSE, none of the things HIPAA carves out of the definition. It's interpretation and the clinician's own reactions. *This* is the document that gets heightened protection. If you keep notes like this, the rule is simple: keep them separate, and never let them bleed into the shared record.

## Where an AI scribe fits, and where it doesn't

So where does an ambient scribe land in all this? On the progress note, not the process note. The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice; it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In a therapy or psychiatry context, that means it drafts the shareable record, the SOAP or progress note like the examples above, while your private psychotherapy notes stay yours to write or skip. For prescribers, the Rx comes back as a draft off what you said in session; you review the drugs, doses, and instructions and sign. It doesn't run an automated interaction or dosing check, so with psychiatric polypharmacy in play the prescribing judgment stays yours, exactly as it is today. You read and sign every note.

Now the honest part. A scribe drafts the note; it doesn't decide your documentation philosophy. If you write lean notes by conviction, or you keep detailed separate process notes by hand, that workflow is yours and a scribe shouldn't override it. And we don't write to EHR systems or manage release-of-information workflows for you. The more important caution is specific to this field: in behavioral health the *recording* is more revealing than the note it becomes, so the first question for any scribe is what happens to the audio. Ours is processed in memory and discarded the moment the note is drafted, with no archive. We argued that case in full in our [psychiatry AI scribe privacy guide](../ai-scribe-for-psychiatry-privacy/), and the cross-vendor version is in [what happens to your visit audio](../ai-scribe-audio-retention/). If you want the broader compliance frame, our [HIPAA and AI scribes guide](../ai-scribe-hipaa-baa-consent/) covers the BAA and consent questions.

## Write better notes faster, on your own sessions

The examples above are a template, but the only test that counts is your own caseload. A scripted demo note looks clean for everyone; your real Tuesday, with the client who buries the actual issue in the last five minutes, is what sorts the tools out.

If documentation is eating your evenings, <a href="/us/products/practice-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and watch a progress note draft about two minutes after a sample session, then run the 7-day free trial on a few real visits and grade the notes against what you'd have written yourself. For a structured way to score the output, our [6-point note-quality rubric](../ai-scribe-soap-note-quality/) turns this into a checklist, and our [how to evaluate an AI medical scribe](../how-to-evaluate-ai-medical-scribe/) guide turns it into a full demo agenda. The format of the note matters far less than this: does it capture the risk, the intervention, the response, and the plan, accurately, every time, with the audio question answered before you start.

---

## SLP SOAP Notes: Format, Goals, and What Ambient AI Misses
https://patientsquare.com/us/blog/slp-soap-notes/
Published 2026-01-26 · Updated 2026-07-22 · Tags: slp, clinical-documentation, soap-note

SLP SOAP note examples for clinic and school settings, measurable-goal language that holds up in a Medicare or IEP review, plus what an AI scribe can't do.

An SLP SOAP note keeps the four SOAP sections but fills them with speech-language data: Subjective is the client or caregiver report, Objective is the trial-by-trial accuracy and cueing you recorded, Assessment is your clinical judgment on progress toward the goal, and Plan is the next target or cue fade. The Objective section carries percentages, not impressions.

An SLP SOAP note uses the same four sections as any clinical note, but the Objective section is built from numbers you count: trial-by-trial accuracy, cueing level, and progress against a measurable goal. Below are three full worked examples for speech-language pathology, each section annotated, plus a blank template you can paste into your chart or IEP tool.

The part that trips up SLP notes isn't the format. It's the goal math. A note that says "articulation improving" tells a Medicare reviewer or an IEP team nothing. A note that says "produced /s/ in initial position at 80% accuracy, 8 of 10 trials, minimal verbal cues" tells them exactly where the client stands. That's the difference the rest of this page is about.

> **Key takeaways**
>
> 1. SLP SOAP = the standard four sections, but Objective carries percentages and cueing levels, not impressions.
> 2. ASHA requires plan-of-care goals to be measurable and functional; school IEPs require measurable annual goals under 34 CFR 300.320.
> 3. Three full worked examples below: an articulation session, an adult dysphagia session, and a school fluency session.
> 4. A blank copy-paste template sits at the end, built around goal-progress language.
> 5. The one thing an ambient scribe can't do for you: turn 8 of 10 trials into "80%, criterion met" and decide what happens next. You own that.

## What makes an SLP SOAP note different from a general one?

The buckets are the same. What goes in them is not. Per the StatPearls reference, the SOAP note is a widely used documentation method devised by Larry Weed almost 50 years ago. Speech-language pathology bends each section toward measurable communication and swallowing data.

**Subjective** is the client or caregiver report. How did carryover go at home this week? Is the parent hearing the target sound in conversation? For an adult, is swallowing feeling safer, or did coughing at meals come back? This is their account, and in pediatrics it's often the caregiver's, so note who reported it.

**Objective** is where SLP notes earn their keep. This is counted data: trial-by-trial or session accuracy for each target, the cueing hierarchy level you used, level of assistance, stimuli, and any measurable observation like an intelligibility rating or a swallow-trial result. If your goal has a percentage in it, the Objective section is where the matching percentage appears.

**Assessment** is your judgment about progress. Not "did fine today." Where does the number sit against the goal criterion, is the trend up or flat, and does the client still need your skilled service to keep moving? ASHA's health-care documentation guidance is explicit that notes should justify skilled care, meaning services that need an SLP's knowledge and judgment, not a less-skilled helper.

**Plan** is the next move. Advance the target, fade a cue, add a context, or hold and re-baseline. In medical settings this ties to the plan of care; in schools it ties to the IEP annual goal.

## Why measurable goals decide whether the note holds up

Here's the rule that governs both settings, stated plainly. ASHA's Documentation in Health Care guidance says a plan of care should include "short- and long-term measurable and functional goals," and treatment notes should include measurable statements plus the level of cueing or assistance provided. For school-based work, the federal IDEA regulation at 34 CFR 300.320(a)(2)(i) requires the IEP to contain "a statement of measurable annual goals." Two different authorities, one demand: the goal has to be countable.

A measurable SLP goal has three parts. The **behavior** (produce /r/ in the medial position of words). The **criterion** (at 80% accuracy across three consecutive sessions). The **condition**, usually the cueing level (with minimal verbal cues, given a visual model). Drop any of the three and the goal stops being measurable.

Compare these:

| Vague goal (fails the audit) | Measurable goal (holds up) |
|---|---|
| Improve articulation | Produce /s/ in initial position of words at 80% accuracy across 3 sessions with minimal verbal cues |
| Increase language skills | Use 3-word noun-verb-object utterances in structured play at 70% accuracy with a visual model |
| Improve fluency | Use easy onset in reading tasks with fewer than 3% disfluent syllables across 2 sessions, no clinician cue |
| Safer swallowing | Tolerate nectar-thick liquids with no overt signs of aspiration across a full meal trial |

The right column is what a Medicare progress note or an IEP team can act on. The left column is what gets a plan-of-care rejected or a goal flagged as non-measurable at the annual review. Write the goal in the right-hand form once, and every session's Objective section has a clear number to hit.

## Worked example 1: an articulation session (pediatric, medical or clinic)

A 6-year-old on your caseload for a residual /s/ and /z/ distortion. Third session of a block. Here's the illustrative note.

---

**Subjective:** Caregiver reports carryover practice completed 4 of 5 days this week using the home word list. Says she is starting to hear a "cleaner s" in single words but not yet in sentences. Client arrived cooperative, no illness or absence since last session.

**Objective:** Targeted /s/ in initial position of words across 40 trials. Accuracy 80% (32/40) with minimal verbal cues, up from 68% (27/40) last session. /s/ in medial position, 20 trials, 55% accuracy with moderate cues (verbal plus tactile placement cue). /z/ not targeted this session. Client maintained attention for full 30-minute session with two short breaks.

**Assessment:** Meeting the initial-position /s/ goal criterion (80% target) at the word level for the first time; needs one to two more sessions at criterion to confirm carryover before advancing. Medial position remains cue-dependent and is the logical next target. Progress is skilled-service dependent: accuracy drops without the placement cue, so continued SLP intervention is warranted.

**Plan:** Hold initial-position /s/ at word level one more session to confirm 80% across consecutive sessions, then advance to short phrases. Begin systematic work on medial /s/, fading from tactile to verbal cue. Send updated home list with 10 medial-position words. Reassess /z/ next session.

---

What to notice. The Objective section reports a raw count and a percentage for every target, plus the exact cueing level, so anyone reading knows what "80%" was measured under. The Assessment doesn't just say "good progress"; it states where the number sits against the criterion and why skilled service is still needed, which is the sentence a payer looks for. The Plan names the next target and the cue-fade step, so the following session's goal is already set.

## Worked example 2: an adult dysphagia session (medical, inpatient or SNF)

A 72-year-old post-stroke, seen for dysphagia in a skilled nursing facility. Notes for swallowing carry safety stakes the articulation note doesn't, so the Objective and Assessment lean harder on signs and diet tolerance.

---

**Subjective:** Client reports meals feel "easier" than last week and denies coughing at the last two breakfasts. Nursing staff report no witnessed coughing at meals over the weekend. Client motivated to advance from pureed diet.

**Objective:** Meal-observation trial with nectar-thick liquids and pureed solids. No overt signs of aspiration (no cough, no wet vocal quality, no throat clearing) across 15 sips and 10 spoonfuls. Delayed swallow initiation on 3 of 15 liquid trials, improved with chin-tuck cue. Oral residue minimal after pocketing check. Effortful swallow strategy used with 90% adherence when cued.

**Assessment:** Tolerating nectar-thick liquids and pureed solids without overt aspiration signs, meeting the current diet-tolerance goal at the meal-trial level. Delayed initiation persists but is responsive to the chin-tuck strategy, which supports continued skilled instruction. Not yet safe to trial thin liquids given the delay frequency. Progress supports advancing solids before liquids.

**Plan:** Continue nectar-thick liquids; trial mechanical-soft solids next session with pocketing checks. Reinforce chin-tuck and effortful swallow, targeting independent use without cue. Coordinate with nursing on diet order and mealtime supervision. Reassess for thin-liquid trial once delayed initiation drops below 10% of trials. Progress note due at or before the 10th session per Medicare, on track.

---

Two things this example teaches. First, in dysphagia the Objective section counts safety signs and strategy adherence the same way an articulation note counts sound accuracy: 3 of 15 delayed initiations, 90% strategy adherence. Numbers, not "did well." Second, the Assessment states what is and isn't safe to advance and ties it to the observed data, which is exactly the medical-necessity reasoning ASHA's guidance says skilled notes must show. The last Plan line flags the Medicare progress-note timing so it doesn't get missed.

## Worked example 3: a school fluency session (school-based)

A 9-year-old with childhood-onset fluency disorder, seen twice weekly in a school setting against an IEP annual goal. School notes tie every session to a measurable annual goal and report progress on the IEP cycle, not a payer's.

---

**Subjective:** Student reports using "easy speech" during a class presentation this week and felt "less stuck" than usual. Teacher note in the log mentions the student volunteered to read aloud, which is new. Student engaged and willing to practice reading tasks today.

**Objective:** Structured reading task, 200 syllables. Disfluent syllables 2.5% (5 of 200) using easy-onset and light-contact strategies, no clinician cue, down from 6% two sessions ago. Conversational sample, 150 syllables, 8% disfluency with self-cued strategy use on about half of disfluent moments. Self-rated tension 2 of 5.

**Assessment:** Reading-level fluency now meeting the IEP annual-goal criterion (under 3% disfluent syllables, no cue) for a single session; needs one more session at criterion to confirm. Conversational carryover lagging, as expected, and remains the harder context. Self-monitoring emerging (student self-cued in structured reading), which is a positive prognostic sign for generalization.

**Plan:** Confirm reading-level criterion next session, then shift primary target to structured conversation. Continue easy-onset and light-contact instruction, building self-cueing in conversation. Note progress toward the measurable annual goal for the next IEP progress report. Coordinate with classroom teacher on low-pressure speaking opportunities.

---

The school note ties directly to the measurable annual goal the IEP is required to carry under 34 CFR 300.320. The Objective section reports the disfluency percentage the goal criterion is written against, in two contexts (reading and conversation), so progress and its limits are both visible. The Assessment states criterion status and flags the next reporting point, which keeps the note aligned with the IEP cycle instead of a billing clock. Same SOAP shape as the medical notes above, different accountability chain.

## A blank SLP SOAP note template you can copy

Here's the reusable skeleton, built around goal-progress language. Paste it and fill each line. Brackets are reminders, not text to keep.

---

**Goal(s) targeted this session:** [State the measurable goal(s): behavior + criterion + cueing condition]

**Subjective:**
[Client and/or caregiver report; note who reported]
[Carryover / home practice completed since last session]
[Relevant status: illness, absences, motivation, teacher or nursing report]

**Objective:**
[Per target: trials attempted, accuracy count and percentage, cueing hierarchy level, level of assistance]
[Stimuli / task used]
[Measurable observations: intelligibility rating, disfluency percentage, swallow-trial signs, strategy adherence]
[Comparison to prior session where relevant]

**Assessment:**
[Where each number sits against the goal criterion: met, approaching, flat]
[Trend and clinical judgment on progress]
[Justification of continued skilled service — why an SLP is still needed]
[Risk or safety statement where relevant, e.g. dysphagia]

**Plan:**
[Advance, hold-to-confirm, fade cue, or add context per target]
[Next target(s)]
[Home program / carryover assigned]
[Coordination: caregiver, teacher, nursing, plan of care or IEP]
[Reporting checkpoint: Medicare progress note timing or IEP progress report]

---

Keep the "goal(s) targeted" line at the top. It's the anchor that forces the Objective section to report the matching number, and it's the first thing a reviewer or IEP team wants to see. For the plain-format version of the four sections with three general-medicine examples, the [SOAP note examples and template](/us/blog/soap-note-examples/) covers the base structure, and the [SOAPIE nursing note guide](/us/blog/soapie-note-nursing/) shows how nurses extend SOAP with Intervention and Evaluation steps.

## How an AI scribe drafts an SLP note, and where it stops

Filling that template by hand, session after session, is the part of the job that follows you home. A 2023 JAMA Network Open study found primary-care physicians logged a median of 36.2 minutes of EHR time per 30-minute visit. Different discipline, same squeeze: the note outlasts the session. That's the gap an ambient scribe is built to close.

The AI Medical Scribe by Patient Square is one module inside Practice Copilot, our AI platform for the whole practice. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

For an SLP, that flips the work from writing to editing the narrative parts. The scribe maps what you and the client said onto the four sections: the Subjective from the caregiver report you took, the Objective narrative from the tasks and observations you spoke aloud, the Assessment and Plan from the reasoning you said in the room. You read the draft, fix what's off, and sign. The ICD-10 entries are suggestions you confirm, not codes filed for you. The note comes out in clean clinical English.

Now the honest limit, and for SLPs it's a big one. The scribe can transcribe that you ran 40 trials and hit 32. It does not own the math that matters: 32 of 40 is 80%, 80% clears your criterion, criterion-met means advance to phrases next session. That chain from raw trials to accuracy percentage to goal-progress judgment is the skilled clinical decision, and it's yours. Say the count and the criterion out loud during the session and the draft has something to anchor to, but you check the number and you make the call. The Assessment is the section to grade hardest on your own notes, because that's where measurement, not transcription, decides quality.

Two more limits worth stating plainly. The visit audio is processed in memory and discarded once the draft is ready, so there's no session recording sitting in an archive. And the tool does not read percentages off your data sheet or your IEP tool; if the goal criterion lives on paper or in a separate system, you're the one reconciling the draft against it. For how much to trust any ambient draft before you sign, the [AI scribe accuracy guide](/us/blog/ai-scribe-accuracy-what-to-expect/) lays out what to expect and what to check, and if your caseload leans toward rehab and movement work, the [AI scribe for physical therapy](/us/blog/ai-scribe-for-physical-therapy/) post covers the adjacent allied-health documentation shape.

The examples above are the bar. A drafted SLP note should read like one of them after a quick edit, with the accuracy numbers you supply dropped cleanly into the Objective section, not a transcript you have to rebuild. The way to know is to run it on your own sessions, not a demo. Read the [pricing page](/us/pricing/), then try structured notes for a week on your real caseload and read every draft closely, Assessment section first.

---

## AI Patient Follow-Up: What AI Sends and Humans Still Own
https://patientsquare.com/us/blog/ai-patient-follow-up-automation/
Published 2026-01-23 · Tags: patient-follow-up, automation, no-show-recovery, practice-copilot

See which reminders, recall nudges, and no-show recovery texts can be automated, and where a licensed clinician must remain in the loop.

The routine, rule-based ones. Appointment and exam reminders, a nudge to a patient who is overdue for a recall or a preventive screening, a post-visit check-in that asks how someone is doing after a procedure, and a text to a no-show patient asking them to rebook. Each of these is a message the practice configures in advance. The system fires it on a schedule or a trigger you set. What does not automate is the clinical read on the reply.

A patient had a procedure on Monday. It's now Thursday, and nobody has checked whether the swelling went down like it should have. Another patient is four months overdue for a diabetes recall, sitting quietly in the panel with nobody to nudge them. A third no-showed yesterday and the slot is still empty because the front desk hasn't had a spare minute to call. None of that is complicated work. It's just the kind of work that slips, because it always loses to the phone that's ringing right now.

That slippage is what "follow-up automation" is supposed to catch. The pitch is easy to oversell, though, and the way most tools describe it blurs a line that matters a lot in healthcare: the line between a message that can safely send itself and a decision that needs a licensed person. So this page draws that line plainly, then says where the automation earns its keep and where it will get you in trouble if you let it run past its lane.

> **Key takeaways**
> - Routine follow-ups automate well: appointment reminders, recall and care-gap nudges, post-visit check-ins, and no-show recovery texts the practice writes in advance.
> - What never automates: interpreting a result, deciding on care, or telling a patient what an abnormal value means. Those are licensed clinical decisions and stay with a clinician.
> - HIPAA permits texting and emailing patients about their care with reasonable safeguards; the FCC's 2015 TCPA ruling exempts treatment messages but pins strict limits on them.
> - The biggest payoff is refilled no-show slots and closed care gaps, not faster typing.

_Sources: MGMA Stat no-show benchmark; Phreesia scheduling-preferences survey; Rotenstein et al., JAMA Network Open 2022._

## The four follow-ups that send themselves

Start with what the automation is genuinely good at. These are messages a practice writes once, then lets fire on a rule. A person doesn't compose each one, and a person doesn't need to.

Appointment reminders are the obvious floor. Confirm the visit, offer a reschedule link, cut the no-show. Most practices already run some version of this, and the value is well-worn.

Recall and care-gap nudges are where a lot of practices leave money and outcomes on the table. A patient overdue for an annual physical, a diabetic past due for an A1c, someone who never booked the colonoscopy their chart flags. The panel is full of these, and working the list by hand almost never happens. An automated nudge that texts the overdue patient with a booking link closes gaps the front desk would never get to.

Post-visit check-ins are the third. A short message a few days after a procedure asking how the patient is doing, with a clear line to call if something is wrong. It signals you're paying attention, and it surfaces the patient who's quietly worse before they wait until Monday to say so.

No-show recovery is the fourth, and it's the one with the fastest payback. When a patient misses a visit, a same-day text asking them to rebook, plus an offer of that freed slot to a waitlisted patient, turns a dead block into a filled one. No-shows sit around 7% by the MGMA benchmark, up from 5% the year before, and every one is a paid room producing nothing. Reminders trim the front end of that number. Recovery texts catch the back end.

One thread runs through all four: the practice decides the content and the trigger in advance. The system sends what you told it to, when you told it to. It isn't writing new clinical messages on the fly, and that constraint is exactly what makes it safe to run unattended.

## Where a human clinician has to stay in the loop

Here's the part the demos skip. There is a category of follow-up work that looks automatable and absolutely is not, and pretending otherwise is how a practice ends up with a compliance problem or a hurt patient.

The clearest line is the abnormal result. Automation can tell a patient their labs are back and ask them to call. It can drop the result into the clinician's queue so it doesn't get lost. What it cannot do is read the result, decide what it means, and tell the patient what to do about it. That is a licensed clinical decision, and it belongs to a person every time. A tool that claims it triages abnormal results without a clinician is one to close the tab on.

The same holds for anything that reads as clinical judgment in a patient's reply. A check-in text goes out; the patient answers that the pain is worse and they're running a fever. The automation's job ends at getting that reply in front of a clinician fast. Deciding whether that patient needs to be seen today, or sent to the ED, is not an automated call.

There's a quieter category too: the message that requires knowing this particular patient. The one who needs a phone call, not a text, because they're anxious and a canned message will make it worse. The one whose situation the rule didn't anticipate. Good automation escalates these instead of forcing a scripted message through.

| Sends itself (rule-based, pre-written) | Stays with a clinician (licensed judgment) |
| --- | --- |
| Appointment and recall reminders | Interpreting a lab, imaging, or pathology result |
| Care-gap nudges from chart flags | Deciding on a follow-up plan or a change in care |
| Post-visit "how are you doing" check-ins | Reading a worrying reply and deciding to see the patient |
| No-show rebooking and waitlist fill | Any message that assumes a diagnosis is understood |
| "Your result is ready, please call" | Telling a patient what an abnormal value means |

The pattern in the right column is consistent: it's a decision only a licensed person can make. Automation should carry information to and from those decisions. It should not make them.

## The compliance layer, stated straight

Two rulebooks govern automated patient messaging in the US, and they answer different questions. Getting them mixed up is where practices trip.

HIPAA governs the content. The HHS Privacy Rule permits a provider to communicate with patients by phone, email, or text about their care, reminders included, as long as you apply reasonable safeguards ([HHS Privacy Rule FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/570/does-hipaa-permit-health-care-providers-to-use-email-to-discuss-patients-health-issues/index.html)). In practice that means an automated message should carry only what the patient needs and shouldn't assume the wrong person is holding the phone. It also means any vendor touching those messages sits under a business associate agreement. Patient Square offers a BAA for every practice, solo included.

The TCPA governs the method, specifically automated calls and texts. The FCC's 2015 Declaratory Ruling recognized a healthcare exemption for treatment messages sent to wireless numbers, including "appointment and exam confirmations and reminders, wellness checkups, hospital pre-registration instructions, pre-operative instructions, lab results, post-discharge follow-up, prescription notifications, and home healthcare instructions" ([FCC 15-72](https://docs.fcc.gov/public/attachments/FCC-15-72A1_Rcd.pdf)). But the exemption is fenced. Under that ruling, the messages must be free to the patient, must state the provider's name and contact info, must carry no telemarketing or billing or debt-collection content, must stay short (160 characters or less for texts), are capped at one message a day and three a week from a given provider, and must give the patient an easy way to opt out. The exemption is a floor, not a green light to blast the panel.

The clean operational answer is to collect a phone number and a messaging preference at intake and honor opt-outs the moment they land. That keeps you on the right side of both rules without leaning on an exemption's fine print, and it's how most well-run practices handle it. Any follow-up tool you buy should make honoring an opt-out automatic, not a manual chore someone forgets.

## What the automation buys you, honestly

The value isn't typing faster or answering sooner. It's two boring, measurable things.

First, filled slots. A no-show at 10am that a recovery text turns into a rebooking, or a waitlisted patient dropped into a freed block, is revenue you were otherwise eating. A busy front desk rarely has the minutes to work that by hand, which is exactly why the automation matters: it does the tedious backfill you'd skip.

Second, closed care gaps. The overdue recalls sitting in your panel are both an outcome you're missing and a visit you're not booking. Nudging them shrinks that pile. Neither of these is a flashy claim. Both move numbers a front desk can't reach on a normal week.

There's a load argument too. Primary-care physicians already spend about 36 minutes in the EHR per visit, per a 2022 JAMA Network Open study, and the "did anyone follow up with that patient" churn spills onto that pile. Getting the routine follow-ups to run themselves keeps that mess off the clinician's afternoon, which is the same reason practices reach for the [ROI math behind these tools](../ai-scribe-roi-calculator-guide/) before they buy.

## Where follow-ups fit: a module, not a standalone app

Here's our bias, said plainly. We don't sell follow-up automation as a disconnected app. AI Follow-ups is a module inside [Practice Copilot](/us/products/practice-copilot/), in the Autopilot tier at $249 per clinician per month, or $199 on annual billing, alongside the [AI receptionist that handles the phone and scheduling](../ai-medical-receptionist-for-clinics/) and, for practices that want it, the [AI scribe that drafts the visit note](../ai-scribe-for-primary-care/).

The reason is the shared patient record. When a recall nudge goes out, it's reading the same chart flags the clinician saw. When a no-show recovery text rebooks a patient, the [scheduling engine](../ai-patient-scheduling-medical-office/) already knows the visit type and the rules. Run follow-ups as a bolt-on that doesn't see the chart, and you're re-entering the same patient across tools that don't talk, which is the exact daily tax a bundle removes.

For context on the visit itself: the AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The prescription is a draft the clinician signs, not something sent on its own, and the ICD-10 codes are suggestions, not filed automatically. Follow-ups work the same way: they carry information, and the licensed decision stays with a person.

## So, should you automate patient follow-ups?

For a practice losing slots to no-shows and letting recalls sit unworked, yes, with the line drawn clearly. Automate the routine, rule-based four: reminders, care-gap nudges, check-ins, no-show recovery. Keep every licensed decision, above all the read on an abnormal result, with a clinician. Set up your messaging so opt-outs are honored automatically and the content stays minimal.

The honest test before you buy: does the tool make the safe follow-ups send themselves, does it route the clinical judgment to a person instead of guessing, does it handle HIPAA safeguards and TCPA opt-outs without you babysitting them, and does it read the same chart the clinician does? A tool that automates the easy part and quietly overreaches on the clinical part is the one to avoid.

AI Follow-ups is a module in Practice Copilot. If you want to see how reminders, recall nudges, and no-show recovery behave against your own patient panel, [explore Practice Copilot](/us/products/practice-copilot/) and identify the follow-up scenario that's slipping through the cracks today.

_Sources: HHS HIPAA Privacy Rule FAQ on patient communication; FCC 15-72 TCPA Declaratory Ruling (2015); MGMA Stat no-show benchmark; Phreesia patient-preferences survey; Rotenstein et al., JAMA Network Open 2022._

---

## AI Discharge Summaries in India: What the Doctor Owns
https://patientsquare.com/in/blog/ai-discharge-summary-india/
Published 2026-01-22 · Tags: discharge-summary, india, ai-scribe, nabh, medico-legal

What AI can draft in an Indian discharge summary, what NABH expects, and the sections a treating doctor must verify and sign before it's a legal record.

AI can draft one. An ambient or generative AI tool assembles a structured draft from the encounter and the ward record, mapping the diagnosis, course of stay, and plan into the standard sections. It does not produce a legal record on its own. Under NABH accreditation guidance the discharge summary is authenticated by the treating doctor, so the draft is a starting point the clinician reviews, edits, and signs. The signed version is the record, not the draft.

AI can draft an Indian discharge summary. It cannot own one. A generative or ambient tool assembles a structured draft from the encounter and the ward record, but under NABH accreditation guidance the discharge summary is authenticated by the treating doctor, so the draft only becomes a legal record when a clinician reviews it, corrects it, and signs. This post is about that line: what the AI can safely draft, what NABH expects the summary to carry, and the sections you have to check yourself before your signature goes on it.

> **Key takeaways**
>
> - AI drafts the discharge summary; the treating doctor reviews, edits, signs, and owns it. The draft has no legal standing until authenticated (NABH 5th Edition; NMC conduct regulations).
> - NABH's Access, Assessment and Continuity of Care standards expect a discharge summary with identifiers, diagnoses, course of stay, procedures with dates, discharge medications, and follow-up.
> - Three sections carry the most risk in an AI draft: the final diagnosis, the discharge medication list, and the follow-up plan. Read those hardest.
> - Notes come back in clean clinical English, not Hindi. Visit audio is discarded after the draft. Ask any vendor how it handles data under the DPDP Act 2023. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

_Sources: NABH Accreditation Standards for Hospitals, 5th Edition; NMC (Professional Conduct) Regulations._

## What can AI actually draft in a discharge summary?

Most of the scaffolding, and none of the accountability. That's the honest split.

A generative or ambient AI tool works from two things: what was said and done during the encounter, and the structured ward record built up over the stay. From that, it can lay out the summary in the expected order, pull the admission and discharge dates, carry forward the procedures and their dates, and draft a course-of-stay narrative and a follow-up plan. It's fast at the assembly. A first pass that would take a tired resident twenty minutes at 9pm arrives in a fraction of that.

What it can't do is decide. It doesn't know that the final diagnosis shifted on day three because a culture came back. It doesn't know that a drug was stopped for a rash the ward noted but never coded. It drafts from what it was given, and if the ward record is thin or contradictory, the draft inherits the thinness. So think of the AI as a very fast typist who was in the room but isn't the doctor. The typing is done in seconds. The clinical judgment is still yours, and so is the signature.

This is a different job from getting the format right. If you want the field-by-field breakdown of what a complete Indian discharge summary contains and why it speeds a cashless claim, that's the [discharge summary format guide](/in/blog/discharge-summary-format-india/). This post assumes the format and asks the next question: when a machine drafts it, what do you still have to own?

## What does NABH expect a discharge summary to contain?

A defined set of elements, prepared for every discharged patient, and authenticated by the treating clinician. The tool that produces the first draft is not the point; the finished, signed summary is.

NABH's 5th Edition standards, under Access, Assessment and Continuity of Care, treat the discharge summary as a required part of closing an admission, and they expect it to carry the elements that let the next clinician continue care safely (NABH Accreditation Standards for Hospitals, 5th Edition). The MoHFW EHR Standards 2016 similarly name the discharge summary as part of the patient record (MoHFW EHR Standards for India, 2016). Neither prohibits a documentation aid. What they require is completeness and authentication. An AI draft that a doctor reviews and signs meets that bar the same way a resident's typed draft does.

Here is the section set, and next to each, the one thing to check when the draft came from a machine rather than a person.

| Section | What NABH expects it to carry | What to verify in an AI draft |
|---|---|---|
| Patient and admission identifiers | Name, age, sex, hospital number, admission and discharge dates, treating consultant | Correct patient and dates; a draft attached to the wrong record is the worst failure |
| Admitting and final diagnoses | Both diagnoses; the reasoning if they differ | The final diagnosis reflects what you concluded, not what was said early in the stay |
| Course of stay | A clinical narrative of key events and response to treatment | The narrative matches the record; no invented event, no dropped complication |
| Procedures and investigations | Procedures with dates and the findings that mattered | Every procedure billed is present; dates are right |
| Discharge medications | Drug, dose, route, frequency, duration | Every drug, dose, and stop instruction; this is the section the patient acts on |
| Condition at discharge and follow-up | How the patient is leaving, red flags, when and where to return | The follow-up interval and warning signs are correct and complete |
| Authentication | Treating doctor's name and signature | Your signature goes on only after the six sections above check out |

The order can vary between hospitals. The completeness cannot, and neither can the authentication. An unsigned summary is, for medico-legal purposes, an unfinished one, whether a person or a model produced the draft.

## Which sections must the doctor verify hardest?

Three, and they're not the ones that look longest. They're the ones where a wrong word carries the most weight: the final diagnosis, the discharge medications, and the follow-up plan.

The **final diagnosis** is a judgment, not a transcription. An AI draft tends to anchor on whatever diagnosis was stated most or earliest, which is often the admitting diagnosis, not the one you settled on. If the two differ, the summary has to reflect the final one and, ideally, make sense of the shift. A diagnosis-procedure mismatch here is both a clinical gap and the classic trigger for a cashless query. Read this line against your own conclusion, not against the ward's first guess.

The **discharge medication list** is what the patient and the next prescriber act on. A draft can drop a drug that was stopped mid-stay, carry forward a dose that changed, or miss a taper instruction that lived only in a verbal handover. Check each drug, each dose, and every start or stop against what actually happened during the admission. This is the section where an unchecked draft does direct harm.

The **follow-up plan** closes the loop on care. The interval, the department, the red flags that should bring the patient back sooner. A draft can leave these generic ("follow up as advised") when the visit had specifics. Make them specific, because a vague follow-up line is a safety gap that reads fine until something goes wrong.

## Who owns an AI discharge summary, medico-legally?

You do, the moment you sign. Not the vendor, not the model, not the resident who ran the tool.

An AI draft carries no legal standing until a registered medical practitioner reviews and authenticates it. Under the National Medical Commission (Professional Conduct) Regulations, indoor-patient records must be maintained and produced on request, and the accountability for the content sits with the treating clinician (NMC Professional Conduct Regulations). The tool is a documentation aid, in the same category as a dictation service or a typing pool. It changes who does the first draft. It does not change who answers for the finished record.

So the practical rule is simple. Treat the AI draft exactly as you'd treat a summary a junior handed you to sign: read it as if you're the one who'll defend it in a complaint or a claim, because you are. The speed is a real gift on a full ward. The accountability is unchanged, and any framing that implies the AI "produces the discharge summary" in a legal sense is wrong. It produces a draft. You produce the record. For the broader question of how the NMC's record-keeping expectations apply when an AI scribe is in the loop, the [NMC record-keeping guide](/in/blog/nmc-record-keeping-ai-scribe/) goes deeper.

The shift is worth seeing plainly. The typing shrinks. The clinical review doesn't. It becomes the whole job.

| Step | Without a draft | With an AI draft |
|---|---|---|
| Assemble | Reconstruct the summary from ward notes at discharge | Read the assembled draft against the record |
| Fill the fields | Type identifiers, diagnoses, procedures, medications by hand | Correct the final diagnosis, medications, and follow-up |
| Catch gaps | Write the course of stay and follow-up from memory | Fix any dropped complication or wrong date |
| Close it | Sign | Sign, and own it exactly as before |

## A worked AI-drafted summary, with the doctor-verify callouts

Here's what the review actually looks like. Below is an illustrative AI-drafted discharge summary for a routine admission, with the checks a treating doctor should run marked inline. The draft is plausible and mostly right, which is exactly why it needs reading, not rubber-stamping.

---

**Patient:** [Name], 58F, Hosp No. 4471. Admitted 14 Jan 2026, discharged 18 Jan 2026. Consultant: Dr. [Name].

`VERIFY: patient, hospital number, and both dates. A draft on the wrong record is the one error nothing downstream catches.`

**Admitting diagnosis:** Community-acquired pneumonia, right lower lobe.
**Final diagnosis:** Community-acquired pneumonia, right lower lobe, resolving.

`VERIFY: is this still your final diagnosis? If the stay revealed anything else (say, a new AF picked up on telemetry), the draft may have missed it because it anchored on the admitting label.`

**Course of stay:** Admitted with 4-day history of fever, productive cough, breathlessness. SpO2 92% on air at admission. Started on IV antibiotics per protocol. Clinical improvement by day 2, afebrile by day 3. Stepped down to oral antibiotics day 3. Chest clear on discharge, SpO2 97% on air.

`VERIFY: does the narrative match the record? Check nothing was dropped (a complication, a change of antibiotic) and nothing was invented. The AI summarises what it was given; it can smooth over a rough patch that mattered.`

**Procedures / investigations:** Chest X-ray (14 Jan): right lower lobe consolidation. Blood cultures (14 Jan): no growth. CBC, CRP trended down over stay.

`VERIFY: every investigation billed is listed, with correct dates.`

**Discharge medications:** Tab Amoxicillin-Clavulanate 625mg, one tablet three times daily, 5 days. Tab Paracetamol 500mg, as needed for fever. Continue home antihypertensive (Amlodipine 5mg once daily).

`VERIFY hardest. Check every drug, dose, and duration by hand. Did any inpatient drug get stopped that the draft carried forward? Did the home medication list survive the stay correctly? This is the section the patient acts on tonight.`

**Condition at discharge / follow-up:** Stable, ambulatory, afebrile. Follow up in chest OPD in 7 days with repeat chest X-ray. Return sooner for breathlessness, fever above 101F, or chest pain.

`VERIFY: is the interval right, is the department right, and are the red flags the ones you'd actually want this patient to watch for? Replace any generic "follow up as advised" with specifics.`

**Authentication:** _________________________ (Treating doctor's signature)

`This line goes last, and only after the six above check out. Your signature is what makes this a record.`

---

The draft above would pass a quick glance. That's the trap. The value of an AI draft is the twenty minutes of typing it saves; the risk is the two minutes of reading it tempts you to skip. Spend the two minutes. For the standards behind why each of these fields belongs in the record, see the [NABH documentation requirements](/in/blog/nabh-documentation-requirements/).

## What about patient data, under the DPDP Act?

Fair question, and one to ask any vendor before the tool touches a real patient. The DPDP Act 2023 treats health data as sensitive personal data and expects purpose limitation and security safeguards (Digital Personal Data Protection Act, 2023). An AI documentation tool sits right on top of that data, so its handling matters.

The questions worth asking are concrete. Where does the visit audio go, and is it kept? How long is the drafted text retained? Does the record stay inside your existing hospital systems, or does it leave them? A tool that processes visit audio in memory and discards it once the draft is ready, and that encrypts data in transit and at rest, reduces the surface you're accountable for. Vague answers to these questions are themselves the risk. Don't accept "it's secure" as an answer; ask for the specifics and match them against the DPDP expectations.

## Where an AI scribe fits, and what we won't claim

At the documentation layer, and we'll be exact about the line we don't cross.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In a busy Indian OPD or ward round running code-mixed Hindi and English, it captures the encounter, and the note comes back in clean clinical English. That structured note is upstream of the discharge summary: it's the well-captured record that a good summary is later assembled from, whether the summary is drafted by you, a resident, or a tool.

Here's what we won't say. We don't claim the scribe produces a legally final or diagnostically authoritative document. It drafts; you own. The ICD-10 entries are suggestions you confirm, not codes filed for you. The prescription is a draft the treating doctor verifies and signs, and the accountability is yours. The note comes out in English, not Hindi. Visit audio is processed in memory and discarded the moment the draft is ready, so there's no recording sitting in an archive; data is encrypted in transit and at rest. We handle data to DPDP Act 2023 standards, and a SOC 2 Type II audit is underway (not yet certified). We are not claiming ABDM integration, EHR/HL7/FHIR integration, or any accuracy percentage, because none of those would be true. The full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

For clinicians weighing the tool for Indian practice specifically, the [AI scribe for doctors in India guide](/in/blog/scribe-for-doctors-india/) lays out the fit, and the [pricing page](../../pricing/) has the numbers: from ₹1,599 per clinician per month on the annual Assist plan, ex-GST, plus 18% GST (about ₹1,887 all-in), with a 7-day full-featured trial and no card required. Or just <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and ask where the audio goes and how fast a structured note is ready. Then decide what a cleaner point-of-care record is worth to your discharge process, knowing the signature, and the ownership, stay exactly where they always were: with you.

---

## What Is a Practice Copilot? Bundled AI vs Scribe Add-Ons
https://patientsquare.com/us/blog/what-is-a-practice-copilot/
Published 2026-01-22 · Updated 2026-07-18 · Tags: practice-copilot, ai-scribe, comparison, pricing

See how a Practice Copilot combines scribing, ICD-10 suggestions, scheduling, and messaging, and when a standalone scribe fits better.

A Practice Copilot is a bundled AI platform for independent practices that puts the front-office tools in one product instead of several. Patient Square's Practice Copilot is six core modules plus the AI Copilot EHR: an AI Medical Scribe, ICD-10 suggestions, prescription drafts, scheduling, WhatsApp messaging, and, on higher tiers, an AI Receptionist and AI Follow-ups. The scribe is one module inside it, not the whole product.

Ask three vendors what they sell and you'll hear "AI scribe," "AI scribe," and "AI scribe," but the products aren't the same shape. Some are a single tool that drafts your note and stops there. Others are a bundle where the scribe is one part of a wider set of front-office modules that share the same visit. "Practice Copilot" is the name for that second shape. This page draws the line between the two so you buy the one that matches your actual gap.

> **Key takeaways**
>
> - A Practice Copilot is a bundled product: the AI scribe is one module, sitting alongside scheduling, messaging, ICD-10 suggestions, and prescription drafts under one login.
> - A standalone scribe fixes the note and leaves the rest of the front office to other vendors you buy and reconcile separately.
> - The bundle's payoff is one vendor, one bill, one support line, and modules that already share the same visit; the trade is less pick-and-choose than a best-of-breed stack.
> - Patient Square's US Practice Copilot publishes three tiers per clinician per month: Assist $99 / $79, Copilot $149 / $119, Autopilot $249 / $199, with a 7-day trial.
> - If the note is your only pain, a standalone scribe is enough. If the whole front office is the pain, the bundle removes the seams between tools.

## What a Practice Copilot actually bundles

Start with the parts, because "Copilot" is a category word and vendors use it loosely. Patient Square's Practice Copilot is built for solo doctors and independent clinics, and it packages six core modules plus a built-in record module called the AI Copilot EHR.

The six core modules are the AI Medical Scribe, ICD-10 suggestions, prescription drafts, scheduling, WhatsApp messaging, and, on the higher tiers, an AI Receptionist and AI Follow-ups. The scribe is the module most people arrive for, and it earns that. The AI Medical Scribe by Patient Square listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Notes come back in English, and the audio is never stored.

The point of the bundle is what surrounds that scribe. Scheduling and patient messaging live in the same product, so the appointment that got booked, the reminder that went out, and the note that got drafted all refer to the same visit without you copying anything between tools. The ICD-10 output is a set of suggestions to speed your coding, not automatic coding, and the prescription is a draft you review and sign, not something transmitted to a pharmacy on its own.

## How is a Practice Copilot different from bolting on a standalone scribe?

Here is the split that actually matters. A standalone scribe does one job: it drafts the note. Everything else stays where it was. Your scheduling lives in one tool, your patient messaging in another, your coding help somewhere else again, and your record in whatever EHR you already run. The scribe is a good tool that solves a real, specific pain, and if the note is your only gap, that's the honest fit.

A Practice Copilot answers a wider question. Instead of buying a scribe and then separately buying, learning, and paying for scheduling and messaging, you get them in one product where they already know about each other. The difference isn't that one drafts better notes. Both can draft good notes. The difference is the number of seams you maintain.

Those seams have a cost that doesn't show up on any single invoice. Four vendors means four contracts, four bills, four support queues, and four places a patient's visit lives in a slightly different form. When the scheduling tool doesn't know what the scribe wrote, and the messaging tool doesn't know what got scheduled, you become the integration layer. A bundle removes that job by making the modules parts of one product rather than neighbors that have to be introduced.

## Why the multi-vendor stack quietly gets expensive

The standalone route looks cheaper because you're pricing one tool at a time. The full bill arrives in pieces. A scribe subscription, then a scheduling subscription, then a messaging tool, then whatever you use for coding help. Each is defensible on its own. Together they're a bigger monthly number than a single tier that includes the lot, and the price is only half of it.

The other half is your time. Every vendor is a login to manage, a renewal to track, and a support thread to open when something breaks. When a patient's appointment, reminder, and note don't line up, the reconciliation lands on you or your front-desk staff. That admin drag is the same category of tax that documentation is: it's not clinical work, but it eats the day. Physician time studies have measured how much of a clinician's day already goes to desk and record work rather than patients (Sinsky et al., Annals of Internal Medicine, 2016). Stacking four disconnected tools on top of that adds coordination work, it doesn't remove it.

Independent practices feel this more than most, and a 2026 survey puts numbers on it. Veradigm surveyed 360 leaders of independent, physician-owned practices, and more than half described their administrative burden as highly challenging. Most physicians in that group still spend at least an hour a day on documentation outside patient visits, and roughly a quarter spend two hours or more. That's the baseline load a small practice is already carrying before anyone adds a scribe login, a scheduling login, and a messaging login on top of it. Each extra tool is one more thing that can fall out of sync with the others, and one more thing the practice has to reconcile by hand.

A bundle collapses that. One tier, one invoice, one place to look. You trade some pick-and-choose freedom for a lot less stitching. For a solo practice or a small group without an operations person to ride herd on vendors, that trade usually favors the bundle.

## What the AI Copilot EHR is, and what it is not

One module needs a plain-English caveat. The AI Copilot EHR is Patient Square's own built-in record system inside the Copilot. It is not an integration with an outside EHR, and it doesn't write back into Epic, Cerner, or any external system. There's no claim here that the Copilot plugs into the EHR you already run.

Why say so up front? Because buyers reasonably assume any tool with a record in it talks to their existing chart. It doesn't. The AI Copilot EHR is a built-in record that lives inside the Copilot for practices that want the visit in one place. If you already run your own EHR, you keep it. You copy the finished note into your chart, the same few seconds any standalone scribe would ask of you.

Being clear about this keeps the comparison honest. The bundle's advantage is that its own modules share a visit. It is not that it silently unifies with software from other vendors, because it doesn't.

## What Patient Square's Practice Copilot costs

The price is published, which is itself part of the pitch. US Practice Copilot has three tiers, all per clinician per month, with the annual rate in parentheses:

| Tier | Monthly | Billed annually | What it adds |
|---|---|---|---|
| Assist | $99 | $79 | AI Medical Scribe, ICD-10 suggestions, prescription drafts, scheduling |
| Copilot (most popular) | $149 | $119 | Adds WhatsApp messaging and the AI Copilot EHR |
| Autopilot | $249 | $199 | Adds AI Receptionist and AI Follow-ups |

There's a 7-day trial, and the full ladder sits on the [pricing page](../../pricing/) with no asterisks and no sales call to learn the number. Compare that with pricing a scribe, a scheduler, and a messaging tool one contract at a time. The published bundle is a single figure you can reason about before you commit. If you'd rather see the note quality against your own visit type first, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a finished note come back before you look at any tier.

## So which one do you actually need?

Match the tool to the gap, not the label on the box.

1. Name the gap honestly. If the only pain is that charting eats your evening, a standalone scribe is a clean, focused fix, and our [what is an AI medical scribe](../what-is-an-ai-medical-scribe/) explainer covers that layer on its own.
2. Count your other tools. If scheduling, patient messaging, and coding help are already handled by software you like, adding a bundle overlaps with what you have. If those are gaps too, or a pile of disconnected logins, the bundle is doing real work.
3. Weigh the seams. Every extra vendor is a bill, a login, and a reconciliation job. Decide whether best-of-breed freedom is worth that admin, or whether one product that shares a visit fits your practice better.
4. Check the trial on real visits. A scripted demo flatters every tool. Run the Copilot, or a standalone scribe, on a genuine clinic week before you decide.

If you're weighing specific bundled products, the [Nuance DAX and Dragon Copilot alternatives](../nuance-dax-dragon-copilot-alternatives/) piece covers the enterprise-copilot end of that market, and if you're the front-desk kind of buyer, the [AI medical receptionist for clinics](../ai-medical-receptionist-for-clinics/) page goes deeper on that single module. Already wondering whether a bundle competes with switching your whole record system, [AI scribe vs a new EHR](../ai-scribe-vs-new-ehr/) walks the cheaper-fix-first order.

When you want to see how the modules ride together on your own visit type, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and review the [product workflow](/us/products/practice-copilot/) against a real clinic week. The honest test isn't the feature list. It's whether one product covering the note, the schedule, and the message beats the stack you're stitching by hand.

---

## Clinic ERP in India: What It Means and Who Needs One
https://patientsquare.com/in/blog/clinic-erp-india/
Published 2026-01-21 · Updated 2026-08-27 · Tags: clinic-erp, buyer-guide, india, back-office

Learn what ERP for clinics means in India and when a clinic-management system plus an AI layer may fit better than a full ERP.

ERP stands for enterprise resource planning: one system that ties together finance and general-ledger accounting, procurement, inventory and pharmacy stock, HR and payroll, and multi-department operations. A clinic ERP applies that idea to a healthcare facility, sitting the clinical record alongside the money, the stores, and the staff. In practice the label is used loosely in India, and many products sold as clinic ERP are really clinic-management systems with a billing module.

The word ERP came out of factories, where one system had to track raw material, machines, money, and people at once. Bolt it onto a clinic and it promises the same: finance, stock, staff, and the patient record under a single roof. That promise is real for a large hospital group. For a two-doctor OPD clinic it is mostly weight you will pay for and never touch. This guide sorts what "clinic ERP" actually means from what an Indian practice needs to buy.

> **Key takeaways**
>
> - ERP means enterprise resource planning: general-ledger finance, procurement, inventory, HR and payroll, and multi-department operations tied together. A "clinic ERP" applies that back-office machinery to a healthcare facility.
> - Most small and mid OPD clinics do not need one. With no wards, no central stores, and no cross-department payroll, the ERP modules sit idle while you pay for them.
> - Clinic-management software, an HMS, and an ERP are three different sizes of tool. Read the modules a product ships, not the label.
> - ERP-grade weight earns its keep at large hospitals, multi-site groups, and chains, where finance, procurement, and stores genuinely span departments.
> - Patient Square is not an ERP. Practice Copilot can use Patient Square EHR or an existing EHR; Hospital Copilot can use the complete Patient Square HIS/EHR or an existing HIS/EHR. ERP accounting, procurement, payroll, and warehouse workflows remain separate.

## What "ERP for clinics" actually means

Enterprise resource planning is back-office software. In any industry, an ERP knits together the systems that run the organisation as a business: general-ledger accounting, accounts payable and receivable, procurement and purchase orders, warehouse-grade inventory, HR and payroll, and reporting that rolls all of it up across departments. It is the money-and-materials layer, and its whole point is that these pieces talk to each other instead of living in separate spreadsheets.

A clinic ERP takes that idea into a healthcare facility. Alongside the clinical record, it wants to run the pharmacy as inventory tied to procurement, post every charge to a ledger, cut payroll for the whole staff, and reconcile stores against purchases. On paper that is tidy. The catch is scale: an ERP only pays off when there is enough finance, stock, and staff to coordinate that a spreadsheet-plus-billing setup starts breaking down.

The Indian software market muddies this. Plenty of products sold as "clinic ERP" are clinic-management systems with a billing screen, no general ledger in sight. The label travels further than the modules. So before you weigh whether you need an ERP, it helps to see how the three tools that get sold to clinics actually differ in size.

## Clinic-management software vs HMS vs ERP

These three names get stacked on the same pricing page, which is how clinics end up overbuying. They are not synonyms. They are three sizes of tool for three sizes of problem.

Clinic-management software, often called a clinic EMR in India, is built around the OPD practice. Appointments, patient registration, the clinical record, prescriptions, and simple GST billing. It is sized for a walk-in practice with one or two billing counters. Products in this band are what most Indian clinics actually run, and our own [best clinic management software in India](../best-clinic-management-software-india/) scorecard lives here.

An HMS, a hospital management system, runs a facility. On top of a clinical module it adds IPD and OPD registration, bed and ward management, admission and discharge flows, a pharmacy with inventory, the lab, and billing that spans departments. A 100-bed hospital cannot run on a clinic EMR; it needs this operational backbone. We walk through it in [EHR vs HMS in India](../ehr-vs-hms-india/) and [hospital management system explained](../hospital-management-system-explained/).

An ERP is broader still, and it starts from the back office rather than the bedside. Where an HMS coordinates the clinical facility, an ERP coordinates the whole organisation as a business: consolidated finance and a real general ledger, procurement, warehouse inventory, and payroll across every unit. In healthcare, an ERP often sits under or beside an HMS at a large group, handling the money and materials while the HMS handles the wards.

## Why most Indian OPD clinics don't need an ERP

Line the ERP modules up against a real OPD clinic and most of them have nothing to do. There are no wards to manage, so bed and admission flows are dead weight. There is no central warehouse feeding several departments, so warehouse-grade inventory is overkill; a small drug cupboard is a stock list, not a supply chain. Payroll is a handful of people, not a multi-department run that needs its own engine. And the finance, for a practice whose core clinical services are usually GST-exempt, is a set of invoices and a receipts ledger, not a consolidated general ledger closing books across units (MoHFW EHR Standards for India, 2016, for what a compliant clinical record must hold; the financial machinery an ERP adds is separate from that).

That mismatch has three costs. You pay a bigger licence for capability you never use. You spend weeks configuring and training staff on modules that will stay empty. And the daily software gets more complex to operate, which in a small clinic means slower reception and more errors, not fewer.

There is a cleaner setup for this scale. A clinic-management system or EMR handles the record, prescriptions, and billing, and an accountant or a light accounting tool handles the books, which for a small practice is genuinely enough. The pharmacy, if there is one, runs on the clinic system's stock feature or a simple standalone. You add finance-grade ERP the day the money and the stores stop fitting that setup, and not before.

## Where ERP weight does earn its keep

None of this means ERP is a bad tool. It is the right tool at the right scale, and the tipping point is when the back office, not the clinical record, becomes the bottleneck.

A large hospital running procurement across many departments, holding real warehouse inventory, and closing consolidated finance every month has coordination problems a billing module cannot solve. A multi-site group or chain that needs one view of purchasing, stock, payroll, and revenue across locations is exactly what ERP was built for. At that scale the modules a small clinic would never touch become the reason to buy: the whole point is that finance, stores, and staff reconcile automatically instead of by hand across a dozen spreadsheets.

So the honest test is scale and back-office complexity, not the word "clinic" in the product name. Ask where your organisation actually hurts. If it is beds and departments, you are looking at an HMS. If it is procurement, consolidated finance, and warehouse stock across units, that is the ERP conversation. If it is the patient record and prescriptions in a walk-in OPD, you needed neither.

## Where Patient Square fits, and where it doesn't

Worth being blunt here, because the whole point of this guide is honesty about scope. Patient Square is not an ERP. It has no general-ledger accounting, no procurement, no HR-payroll, and no warehouse inventory. If your problem is coordinating money and materials across a hospital group, we are not the answer, and we would rather say so than sell you a badge.

Patient Square is a packaged clinical platform: Practice Copilot for clinics and Hospital Copilot for hospitals. Practice Copilot can use Patient Square EHR or work alongside an existing EHR. Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Neither path turns Patient Square into an ERP, so general-ledger accounting, procurement, HR-payroll, and warehouse inventory still need a suitable system.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. The ICD-10 codes are suggestions you confirm and the prescription is a draft you check and finalise; nothing is transmitted to a pharmacy on your behalf. The note comes back in clean clinical English, and the visit audio is processed in memory and never stored on a server, which is the cleaner posture under the Digital Personal Data Protection Act, 2023 (MeitY / PIB). We build to DPDP standards, and ABDM integration is on our roadmap rather than live today (National Health Authority, ABDM). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Here is the practical read for a clinic that thinks it needs "ERP". Nine times out of ten, the real need is a clinic-management system for the record and billing, plus an AI layer that takes the typing off the doctor's evening. The heavy finance-and-stores machinery is a problem you may grow into, not one you have at two doctors and a front desk.

## How to decide

Buy for the scale and the bottleneck you have now, not the org chart you might grow into.

1. Name the real pain. Is it the patient record, prescriptions, and OPD billing? Is it beds, wards, and department coordination? Or is it procurement, consolidated finance, and warehouse stock across sites? Those three answers point at clinic-management software, an HMS, and an ERP, in that order.
2. Read modules, not labels. Make each shortlisted vendor show you what it actually ships, since "clinic ERP" and "clinic management" get printed on the same product.
3. Right-size the finance layer. A small OPD clinic needs invoicing and a receipts ledger, which an accountant or a light tool handles. Reach for ERP-grade finance only when the money and the stores stop fitting that.
4. Then add the AI layer. Whatever record system you land on, the documentation time is the same pain on all of them, and an AI scribe layered on top removes it.

If you are an OPD-led practice and the daily grind is notes, prescriptions, and billing rather than back-office reconciliation, start with the focused options in our [best clinic management software in India](../best-clinic-management-software-india/) roundup and the [EMR software in India guide](../emr-software-india-guide/). If you keep tangling the record-system terms, [EHR vs HMS in India](../ehr-vs-hms-india/) draws that line, and [hospital management system explained](../hospital-management-system-explained/) covers the facility side in depth.

When you want to compare Patient Square EHR with the existing-EHR path, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> or start the 7-day trial. The India Practice Copilot publishes its pricing openly: Assist at ₹1,999 per clinician a month (₹1,599 on annual), Copilot at ₹2,999 (₹2,399 annual, the most popular tier), and Autopilot at ₹4,999 (₹3,999 annual), all plus 18% GST. No card to start the trial, and no ERP you didn't need.

_Reviewed by the Patient Square clinical team._

---

## Medical Practice Management Software: Honest Guide
https://patientsquare.com/us/blog/medical-practice-management-software-guide/
Published 2026-01-21 · Updated 2026-08-29 · Tags: practice-management, pms, billing, practice-copilot

What practice management software actually covers, how to weigh all-in-one vs best-of-breed, migration risk, and where an AI layer fits on top of your PMS.

The core five: scheduling, billing and revenue cycle, insurance eligibility checks, patient communication, and reporting. Some PMS products bolt on a patient portal or basic charting, but the heart of it is the money and the calendar, not the clinical note. If a vendor pitches a PMS as a full EHR, read the fine print. The two overlap but they are not the same product.

Picture the front office of a four-provider clinic at 4:30 on a Wednesday. One staffer is on hold with a payer to check eligibility. Another is keying an insurance denial back into a billing screen. A third is fielding the eleventh reschedule call of the day while a claim from last week sits unworked. Practice management software is the tool that's supposed to make that afternoon quieter. Whether it does depends entirely on which one you buy and how honestly the vendor drew the boundaries. This guide names the tradeoffs the sales deck skips.

> **Key takeaways**
>
> - A PMS covers five things: scheduling, billing and revenue cycle, insurance eligibility, patient communication, and reporting. Charting is the EHR's job, even when they share a login.
> - The real fork is all-in-one vs best-of-breed, and EHR-coupled vs standalone. There's no universal winner. A lean two-provider clinic and a billing-heavy specialty group want opposite things.
> - Migration is where deals go wrong. The demo is smooth; the go-live weeks are where claims stall and cash flow dips.
> - Practice Copilot can cover documentation, scheduling, and a bundled EHR by tier. It still does not run US claims, clearinghouse, eligibility, or full RCM work.

_Sources: CAQH 2023 Index; CAQH 2024 Index (via CAQH); MGMA._

## What a PMS actually covers (and what it doesn't)

Strip away the branding and a practice management system does five jobs. Get clear on these before you compare a single feature list.

**Scheduling.** The calendar: booking, rescheduling, cancellations, provider templates, and the waitlist. This is the operational spine. If the scheduling module is clumsy, your front desk pays for it every hour of every day.

**Billing and revenue cycle.** Charge capture, claim submission, denial management, payment posting, and patient statements. For most practices this is the reason a PMS exists. Weak billing is the single most common reason a clinic rips out a system two years in.

**Insurance eligibility.** Checking coverage before the visit so you're not chasing a denial after it. The savings here are real and measured: the CAQH found the medical industry saves roughly $10 per eligibility check by running it electronically instead of by phone or portal (2023 CAQH Index). Multiply that across a full schedule and it's not a rounding error.

**Patient communication.** Reminders, confirmations, recall for overdue visits, and increasingly two-way messaging. Reminders are the cheapest tool you have against no-shows, and no-shows aren't small. MGMA puts the median practice no-show rate around 5 to 7% (MGMA Stat, 2023). Every confirmed slot is revenue the reminder paid for.

**Reporting.** Days in accounts receivable, denial rates, collection ratios, provider productivity. Without it you're flying blind on the numbers that decide whether the practice is healthy.

Notice what's not on that list: the clinical note. Charting, orders, results review, the SOAP note, that's the EHR's territory. Plenty of ambulatory suites bundle PMS and EHR under one login, which blurs the line, but they're two different jobs. A PMS runs the business of the visit. An EHR runs the medicine of it. When a vendor sells you a "complete platform," your job is to figure out which half is strong and which half is along for the ride.

Security requirements cut across both halves. If HIPAA is a purchase condition, use the [HIPAA-compliant practice-management software checklist](../hipaa-compliant-practice-management-software/) to test contracts, access control, auditability, integrations, and breach responsibilities instead of accepting a compliance badge as the answer.

## The two decisions that actually matter

Feature grids are a trap. Every modern PMS checks the same boxes. The decisions that shape your next five years are structural, and there are only two of them.

**All-in-one vs best-of-breed.** An all-in-one suite gives you scheduling, billing, and comms from one vendor, on one bill, with one support line. Fewer integration seams, fewer finger-pointing matches when something breaks. Best-of-breed means picking the strongest tool for each job and wiring them together, which pays off when one function is critical enough to deserve a specialist. A high-volume billing operation might want a dedicated clearinghouse workflow that a generalist suite can't match. A three-provider family clinic almost never does.

**EHR-coupled vs standalone.** A coupled system shares a database with your charting, so a diagnosis flows to a claim without re-entry. Clean, until you want to switch one and not the other. A standalone PMS keeps billing independent, which is exactly right if your EHR's billing is weak, if you use an outside billing service, or if you just don't want your revenue cycle held hostage to a charting vendor's roadmap. The cost is a data bridge you own and maintain.

Here's the honest version most vendor pages won't print: for a small, lean practice, a standalone or all-in-one PMS with a tight, unshowy feature set often beats the sprawling enterprise suite. You don't need forty modules. You need scheduling that doesn't fight you, billing that gets claims paid, and reminders that fire. Buying a platform built for a 200-provider group to run a two-provider clinic is how software becomes the thing you resent.

| Function | PMS covers it | Lives elsewhere |
|---|---|---|
| Scheduling / calendar | Yes, core | – |
| Billing, claims, denials | Yes, core | Outside billing service (optional) |
| Insurance eligibility | Yes | – |
| Reminders / patient comms | Yes | – |
| Reporting on AR + productivity | Yes | – |
| Clinical notes / charting | Sometimes (coupled EHR) | The EHR |
| Ambient documentation, AI drafts | No | An AI layer (see below) |
| Interoperability / records exchange | Varies | EHR / HIE |

## Draw the buy, integrate, or retain boundary first

Before comparing vendors, put every operating job into one of three buckets. This prevents an attractive documentation demo from being mistaken for a revenue-cycle replacement.

| Practice job | What a buyer needs to prove | Patient Square's current boundary | Decision |
|---|---|---|---|
| Encounter documentation | Draft, clinician review, signature, export, and record ownership | Ambient scribe on every plan; structured SOAP note, ICD-10 suggestions, and prescription draft for review | Buy or trial if the note test passes |
| Clinical system of record | Migration, longitudinal chart, permissions, and exit export | Bundled AI Copilot EHR starts on Copilot; the public product surface doesn't enumerate deep EHR submodules | Verify before replacing an existing EHR |
| Scheduling | Booking rules, staff overrides, reminders, and failure handling | Scheduling starts on Assist | Buy only after a real calendar test |
| Phone and follow-up automation | Human takeover, emergency boundary, consent, and audit trail | AI Receptionist and AI Follow-ups start on Autopilot | Add after the escalation test |
| Claims and clearinghouse | Eligibility, claim submission, ERA, denial work, and payer connectivity | Not claimed as a Practice Copilot capability | Retain or buy a dedicated PMS/RCM stack |
| Billing history and open balances | Clean migration, reconciliation, parallel run, and ownership | No public claim that this migration is supplied | Retain until a written migration plan exists |

Our opinion: the claims row should be a hard stop. If the project is mainly a clearinghouse or denial-management replacement, this isn't the right product category. If the practice wants the documentation and record layer while keeping a billing service or PMS, the boundary can be sensible. The [integrated EMR and practice-management guide](/us/blog/emr-practice-management-software/) covers that architecture; [current pricing](/us/pricing/) shows which Patient Square tier owns each shipped module.

## Migration is where the money hides

Every PMS demos beautifully. The screens are clean, the sample data is tidy, the rep clicks through a claim in nine seconds. None of that tells you what the switch will cost you.

The risk sits in two places. First, data migration: moving patient records, open balances, scheduling history, and provider setups from the old system to the new one without losing or corrupting anything. Second, the go-live weeks, when your staff is slow on unfamiliar screens and claims can stall in the transition. A dip in cash flow during a botched go-live is the tax nobody quotes you.

So make the vendor earn it. Ask for a written migration plan, a data-mapping document that says exactly which fields go where, and a parallel-run period where the old system stays reachable while the new one takes over. Ask how open accounts receivable transfers, because half-migrated balances are a collections nightmare. And never, ever go live over a long weekend with no fallback. The clinics that migrate cleanly treat it as a project with a timeline, not a switch you flip.

## Where Practice Copilot fits, and where it stops

Here's where a lot of buyers get confused, so we'll be blunt about our own product. [Practice Copilot](/us/products/practice-copilot/) is not a full US PMS or revenue-cycle suite. It won't submit your claims, run a clearinghouse, check eligibility, or replace a billing engine.

What it does claim publicly is narrower. The ambient [AI Medical Scribe](../ai-scribe-for-primary-care/) produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Scheduling starts on Assist. The Copilot tier adds the bundled AI Copilot EHR and WhatsApp messaging; Autopilot adds modules named AI Receptionist and AI Follow-ups. The public pages don't describe deep behavior for those named modules, so a buyer should make the demo prove the exact calendar, call, message, and handoff behavior it needs.

The safe division is clear at the billing boundary. Your existing PMS or billing service keeps claims, eligibility, statements, balances, and denials. Practice Copilot can be tested for documentation and the tier-scoped record or front-office modules. Whether you keep the old EHR and calendar too depends on migration and workflow evidence, not the word bundle.

We think clinics should keep revenue-cycle ownership separate on purpose unless a vendor can prove every payer workflow. A specialist billing platform can run the money while the clinical layer changes. That cuts the migration blast radius and makes the limitation obvious.

## So how do you actually choose?

Boil it down to four questions and ignore the rest of the pitch.

1. **Is billing the strong half or the weak half?** Demo a real denial workflow, not a clean paid claim. If billing is weak, either pick a best-of-breed billing tool or plan to bolt on an outside service.
2. **Coupled or standalone?** Decide whether you want billing chained to your charting vendor. If your EHR's billing is fine and you like it, coupled is simpler. If it isn't, keep them independent.
3. **What's the migration plan in writing?** No plan, no data-mapping doc, no parallel run: no deal. The go-live is where the real cost lives.
4. **Which Patient Square modules have you actually proved?** Documentation, scheduling, a bundled EHR, messaging, receptionist, and follow-up labels don't prove your exact workflow. Run each claimed handoff before retiring an incumbent.

The verdict is unglamorous and it's the right one. Keep a PMS or billing partner that's genuinely strong at claims for your size of practice, insist on a written migration plan, and replace only the modules that pass a real workflow test. For a small clinic, a clear boundary beats a sweeping platform claim.

If you want to test that boundary, request your 7-day trial and bring your messiest Wednesday afternoon plus one billing workflow the product must not pretend to own. The [pricing page](/us/pricing/) shows which modules are named at each tier; the trial has to prove the rest.

_Sources: CAQH 2023 Index Report; CAQH 2024 Index (via CAQH); MGMA no-show benchmark; JAMA Network Open 2022 (via AMA)._

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot supports documentation and shipped practice workflows. A new practice can instead use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## AI Patient Scheduling: What Autonomous Booking Actually Requires
https://patientsquare.com/us/blog/ai-patient-scheduling-medical-office/
Published 2026-01-20 · Tags: scheduling, ai-scheduling, front-desk, practice-copilot

A clinic-built breakdown of what AI patient scheduling really needs to work: live calendar access, real booking rules, self-scheduling, and clean human escalation.

It answers the phone or a web request, checks your real calendar, and books, reschedules, or cancels an appointment against your rules. It sends reminders and fills a cancelled slot from a waitlist. What it does not do is invent availability or override a rule you set. If the request is outside what the rules cover, a good system hands the call to a person instead of guessing.

It's a Tuesday at a single-specialty office and the phone has been ringing since 8:02. Two patients stand at the window. The scheduler is on hold with a patient who wants to move a Thursday slot, a new patient is trying three clinics in a row to see who picks up first, and a cancellation from 20 minutes ago is still sitting empty because nobody has had a spare minute to call the waitlist. None of this is hard. It's just relentless, and it's the exact work people mean when they ask whether AI can "handle scheduling."

Most guides answer that question by listing standalone booking tools and ranking them. That's the wrong frame. The interesting question isn't which widget is prettiest. It's what a system actually has to do before it can book a patient without a human double-checking the result.

> **Key takeaways**
> - Autonomous booking needs four things to work: live calendar access, real scheduling rules, patient self-scheduling on the phone and the web, and clean escalation to a person.
> - About 65% of patients still prefer to book by phone, so a web-only scheduler misses most of your volume.
> - The payoff isn't answering faster. It's filling cancelled slots and cutting no-shows, which is where the money leaks.
> - A human front desk still wins on judgment calls: work-ins, favors, upset callers, odd edge cases the rules don't cover.

_Sources: Phreesia scheduling-preferences survey; MGMA Stat no-show benchmark; Rotenstein et al., JAMA Network Open 2024._

## What "autonomous booking" actually means

Vendors use "AI scheduling" to describe two very different things. One is a smart web form: it shows open slots and lets a patient click one. That's self-scheduling, and it's genuinely useful, but a human still built the availability and set the rules. The other is autonomous booking: a system that takes a request in plain language, on a call or a web chat, figures out what the patient needs, and commits the booking against a live calendar without a person in the loop.

The second one is what people picture when they imagine replacing phone work. It's also the one with real requirements. Four things have to be true before it can run unsupervised.

First, live calendar access, not a copy. If the AI books against a synced snapshot that updates every 15 minutes, it will double-book. Autonomous scheduling has to read and write the actual calendar in real time, so the slot it offers is the slot it takes.

Second, your rules, encoded. Every practice has them, mostly in someone's head. New patients get 40 minutes, follow-ups get 20. This provider doesn't do Fridays. Two procedures can't stack back to back. A physical needs a longer room. An AI that doesn't know any of this will book garbage, and you'll spend more time fixing its bookings than you saved.

Third, it has to work on the phone. This is the one most tools skip. Roughly 65% of patients prefer to book by phone, per Phreesia's survey of nearly 14,000 patients, and that number climbs with age. A scheduler that only lives on a web widget quietly ignores two-thirds of how your patients want to reach you.

Fourth, it has to know when to stop. The measure of a decent scheduling AI is how cleanly it escalates. When a request falls outside the rules, or the caller is upset, or something smells like an emergency, it should hand off to a person fast instead of forcing a booking.

## The part nobody puts on the sales page

Answering the phone quickly is nice. It's not where the money is. The money is in two boring places: cancelled slots that never get backfilled, and patients who don't show.

No-shows sit around 7% by the MGMA benchmark, up from 5% the year before. Every one is a paid room and a paid provider producing nothing for that block. Reminders help, but the bigger lever is the waitlist. When a Thursday-afternoon slot cancels at 11am, a busy front desk almost never has the minutes to work the list and refill it by hand. An autonomous scheduler does it in the background: text the eligible waitlisted patients, book whoever confirms first, done. That single behavior, filling gaps you'd otherwise eat, tends to move the numbers more than faster pickup ever will.

There's a quieter payoff on the clinical side too. Primary-care physicians already spend about 36.2 minutes in the EHR per visit, per a 2024 JAMA Network Open study. Scheduling churn that spills onto the clinician's desk, the "can you just fit them in" messages, adds to that load. Getting booking to run itself keeps that mess off the exam room.

## Where a human front desk still wins

We build this software, and we'll still tell you plainly: don't try to automate the whole desk. There's a band of scheduling work where a person is simply better, and a system that pretends otherwise creates problems.

The routine 70% is what you automate. The last 15% is where staff earn their keep. A patient who needs to be worked in today because they sound worse than they'll admit. The favor double-book a provider agrees to for a long-time patient. The caller who's frightened and wants a human voice, not an efficient one. The scheduling edge case your rules didn't anticipate. Force an AI through those and you get cold, wrong, or both.

Here's the honest line between the two.

| What autonomous scheduling handles | What stays human |
| --- | --- |
| Booking, rescheduling, cancelling routine visits | Working a patient in against a full schedule |
| Reminders and confirmations | An upset or frightened caller |
| Filling a cancelled slot from the waitlist | A favor double-book the provider will accept |
| Applying set rules (visit length, provider prefs) | An edge case the rules don't cover |
| Answering "what times do you have" on phone or web | Anything that smells like an emergency |

If your front desk is small and mostly handles complex, high-touch scheduling, an autonomous system will help less than the demo suggests. That's a fair reason to wait. We'd rather tell you that than sell you a mismatch.

## Where scheduling fits: a module, not a bolt-on

This is where our bias shows, so we'll be direct about it. We don't ship scheduling as a standalone tool. It's a module inside [Practice Copilot](/us/products/practice-copilot/), alongside the [AI receptionist that answers the phone](../ai-medical-receptionist-for-clinics/) and, for practices that want it, the [AI scribe that drafts the visit note](../ai-scribe-for-primary-care/).

The reason is plain: these things share a patient. When the receptionist books a follow-up, the scheduling rules already know the visit type; when the patient arrives, the scribe's draft note ties back to that same booking. Run scheduling as a disconnected widget and you re-enter the same patient three times across three tools that don't talk. That fragmentation is the actual daily tax, and it's what a bundle removes.

If you're weighing this alongside a broader front-office change, our notes on [rolling out an AI scribe in a small clinic](../ai-scribe-implementation-small-clinic/) and the [ROI math behind these tools](../ai-scribe-roi-calculator-guide/) cover the adjacent decisions.

## So, is AI patient scheduling worth it?

For a busy office drowning in routine calls and empty slots, yes, with eyes open. The value is real and measurable: fewer no-shows, backfilled cancellations, a front desk that isn't chained to the phone. But it's narrow. It handles the repetitive 70% and escalates the rest, and any vendor telling you it replaces your staff outright is overselling.

The honest test before you buy: does it read your live calendar, does it know your rules, does it work on the phone and not just the web, and does it hand off cleanly when it should? If a tool can't answer all four, it's a booking widget wearing an AI label.

Scheduling is a module in Practice Copilot. If you want to see how autonomous booking, reminders, and waitlist backfill behave against real rules, [explore Practice Copilot](/us/products/practice-copilot/) using your messiest scheduling scenario as a test case.

_Sources: Phreesia, Understanding Patients' Scheduling Preferences and Habits; MGMA Stat patient no-show benchmark; Rotenstein et al., JAMA Network Open 2024; CDC / NCHS National Ambulatory Medical Care Survey._

---

## Hospital CRM in India: Where It Sits Outside the HMS
https://patientsquare.com/in/blog/crm-for-hospitals-india/
Published 2026-01-20 · Updated 2026-08-29 · Tags: hospital-crm, patient-engagement, buyer-guide, india

A buyer guide to hospital CRM in India: what patient relationship management actually does, where it overlaps your HMS, and how to decide what you really need.

A hospital CRM (customer relationship management) is software built around the patient as a relationship, not just a clinical record. It handles engagement between visits: appointment reminders, recall and reactivation of lapsed patients, feedback collection, referral tracking, and outreach campaigns. It sits alongside the clinical and operational systems a hospital already runs, and its job is retaining and re-engaging patients rather than documenting the consult or running the wards.

Ask most Indian hospital administrators where the money leaks, and they will point at billing, stock, or empty OPD slots. Almost nobody points at the patient who came once and never came back. That gap is what a hospital CRM is built to close, and it is the most under-invested corner of the average Indian hospital's software stack. This guide explains what patient relationship management actually covers, where it quietly overlaps the HMS you already run, and how to decide whether you need a separate CRM at all.

> **Key takeaways**
>
> - A hospital CRM is organised around the patient relationship over time: reminders, recall of lapsed patients, feedback, referrals, and outreach. It is not an EMR and not an HMS.
> - Patient retention is chronically under-invested in Indian hospitals, so the CRM upside is real, but the overlap with your existing HMS is also real. Many HMS products already send reminders and WhatsApp messages.
> - In India, patient communication is WhatsApp-first, so any engagement tool has to respect DPDP Act 2023 consent and WhatsApp's opt-in and 24-hour-window rules.
> - Before buying a standalone CRM, list what your HMS engagement module already does so you do not pay twice for the same capability.
> - Hospital Copilot includes WhatsApp messaging, AI Follow-ups, and AI Receptionist. They are the CRM-adjacent slice, not a standalone hospital CRM suite.

## What a hospital CRM actually manages

A CRM is built around one question: how do you keep a patient coming back, and win the next one through them? Everything it does serves that. Appointment reminders so booked patients show up. Recall and reactivation lists so the diabetic who skipped his three-month review gets a nudge. Feedback capture after discharge so you hear about a bad experience before it becomes a Google review. Referral tracking so you know which GP or which happy patient is actually sending you business. Outreach campaigns for a health camp or a new cardiology service.

None of that is the clinical record, and none of it is running the wards. The CRM lives between visits, in the weeks when the patient is at home and your competitor's hoarding is at the bus stop. For a hospital that treats a first visit as the start of a relationship, this is the machinery that keeps the relationship alive.

The reason it matters more than most administrators think is arithmetic. A hospital that fills its OPD chairs by paying for the next new patient, over and over, is renting its demand. One that also reactivates the patients it already treated owns a cheaper, warmer source of visits. Indian hospitals spend heavily on acquisition and lightly on retention, which is exactly backwards from how the numbers usually work.

## Why retention is the under-invested half

So if the maths favours retention, why is the CRM the last thing most hospitals buy? Partly habit. The HMS gets bought because you cannot run a 150-bed hospital without registration, billing, and pharmacy. The EMR gets bought because you need the clinical record. The CRM has no such hard forcing function, so it slips down the list every budget cycle.

The result is a familiar pattern. The hospital has a rich database of patients it has already treated and almost no structured way to reach them again. Reminders, if they go out at all, are a manual SMS from the front desk. Feedback is a suggestion box nobody empties. Referral sources are a guess. The patient who would happily come back for a follow-up simply drifts, because nothing in the system remembered to ask.

That is the honest case for a hospital CRM. Not that it is glamorous, but that the retention work it does is real revenue that most hospitals leave on the table. The trap on the other side is buying a whole new platform for capabilities your existing software may already half-cover, which is where the overlap question comes in.

## Where a CRM overlaps your HMS, and where it does not

Here is the part vendors gloss over. A hospital CRM and a hospital management system are not cleanly separated. Most HMS products already ship an appointment-reminder feature and some form of SMS or WhatsApp messaging, because a facility that books patients needs to remind them. So the simplest slice of CRM work often already sits inside the HMS you paid for.

The line gets clearer when you look past reminders. A transactional HMS module is good at sending a message tied to a booking. It is usually weak at the relationship work: building a recall list of patients overdue for a review, running a structured feedback loop, attributing a new patient to the referrer who sent them, or managing a multi-message campaign. That relationship layer is where a dedicated CRM earns its keep, and where an HMS reminder feature runs out of road.

The practical move is to read your own HMS before you shop. List exactly what its engagement features do today: does it send reminders, does it use WhatsApp, can it build a recall list, does it capture feedback? Whatever it already does is capability you should not pay for twice. The gap between that list and the full CRM column above is your real requirement, and it is often smaller than a CRM sales deck implies.

## Why the WhatsApp and consent rules decide the shortlist

In India, none of this works unless it works on WhatsApp. Patients read WhatsApp; they ignore email and half-read SMS. So a hospital engagement tool that cannot message on WhatsApp is solving the problem in the wrong channel, and one that blasts WhatsApp without regard for the rules is a compliance risk waiting to surface.

Two sets of rules shape what a compliant tool looks like. The first is the DPDP Act 2023, enacted in August 2023, which makes a hospital a Data Fiduciary and requires consent that is free, specific, informed, unconditional and unambiguous, given for a stated purpose, before you process a patient's personal data (DPDP Act 2023, Section 6). Health data is personal data, so a recall message is a use you need the patient's consent for. The second is WhatsApp's own Business Platform policy: the patient must opt in, and outside a 24-hour window after the patient messages you first, a business can send only pre-approved message templates, not free-form text (Meta, WhatsApp Business Platform). India's TRAI commercial-communication rules add a further consent expectation for promotional messaging (TRAI, TCCCPR 2018).

The takeaway for a buyer is simple. A good engagement tool treats consent as a first-class feature, keeps a record of who opted in and for what, and works inside WhatsApp's template and window rules rather than around them. A tool that promises unlimited bulk WhatsApp blasts is promising you a problem.

## Where Patient Square's Copilot fits, and where it stops

Hospital Copilot is not a standalone hospital CRM. It can use the complete Patient Square HIS/EHR as the hospital record system or work alongside an existing HIS/EHR. Its CRM-adjacent module names are WhatsApp messaging, AI Follow-ups, and AI Receptionist. That is the published scope. The module names do not establish a campaign-management workflow, referral analytics, automatic outreach, or a named CRM integration.

If you need deep referral analytics, campaign management, or a marketing-automation console, evaluate a dedicated CRM. If you need to decide whether Hospital Copilot's named modules fit an existing patient-engagement workflow, use a demo to test that workflow with the hospital's consent and channel requirements in view.

The clinical side is separate from engagement. The AI Medical Scribe hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft for the clinician to review and sign. ICD-10 codes are suggestions and the prescription remains a draft. Visit audio is processed in memory and discarded once the note is drafted. ABDM integration is on the roadmap, not live or certified. Patient Square handles the patient data it processes to DPDP Act 2023 standards: consent-first and purpose-limited. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Hospital Copilot is a separate, demo-priced hospital product. Do not use Practice Copilot tiers to estimate a hospital deployment.

## How to decide

Buy for the gap you have, not the platform category a vendor sells.

1. Name the retention leak. Is it no-shows, lapsed patients who never get recalled, feedback you never hear, or referral sources you cannot see? Each points at a different slice of CRM work, and you may only need one or two.
2. Audit your HMS first. Write down what its engagement features already do. Reminders and WhatsApp messaging often already live there, so subtract those from your requirement.
3. Check the channel and the consent. Whatever you buy has to work on WhatsApp and has to handle DPDP Act 2023 consent and WhatsApp's opt-in and template rules. Treat a bulk-blast promise as a red flag.
4. Decide modules or a suite. If Hospital Copilot's named modules may fit your gap, test the workflow in a demo. If you need referral analytics and campaign management, evaluate a dedicated CRM.

If your OPD-led facility keeps tangling these categories, [EHR vs HMS in India](../ehr-vs-hms-india/) sorts the clinical-record and facility-management sides, and [hospital management system explained](../hospital-management-system-explained/) goes deep on the HMS. For the messaging channel itself, [WhatsApp for clinics in India](../whatsapp-for-clinics-india/) covers the consent and template rules in detail, and the [best clinic management software in India](../best-clinic-management-software-india/) roundup scores the wider field.

For a hospital deployment, <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring the patient-engagement workflow, consent process, and incumbent HIS/EHR you need to evaluate.

_Reviewed by the Patient Square clinical team._

---

## Hospital Inventory Management in India: Where HMS Modules Struggle
https://patientsquare.com/in/blog/hospital-inventory-management-india/
Published 2026-01-19 · Updated 2026-08-30 · Tags: inventory, pharmacy, hospital, hospital-copilot, india

What a hospital inventory system tracks, the India-specific mess (Schedule H1, GST, expiry write-offs), and when a dedicated pharmacy or ERP beats the bundled HMS module.

At minimum: pharmacy stock and consumables at the batch level, expiry dates, reorder points, GRN against purchase orders, department indents and issues, and a running valuation. In India it also has to hold the Schedule H1 register, batch-and-expiry for drug recalls, and GST-correct rates per item so billing and returns reconcile.

Inventory decisions should start with the hospital's own batch, expiry, issue, transfer, and valuation scenarios. A demo is useful only if the vendor can run those scenarios end to end in the quoted product.

Most buyers come to this looking for a "hospital inventory management system" and assume the module bundled into their HMS will handle it. Do not assume that either way. This guide sets out the workflow and regulatory questions to put through the exact product being quoted.

> **Key takeaways**
> - A real hospital inventory system tracks pharmacy stock and consumables at the batch level, with expiry, reorder points, GRN, and department issue all reconciling to one valuation.
> - India adds requirements to verify: the Schedule H1 register, GST-correct rates per item, and batch-and-expiry controls across the stores you operate.
> - Use the hospital's own purchasing, expiry, and adjustment data to measure the risk.
> - Compare the quoted HMS module and any pharmacy or ERP candidate on the same buyer-authored tests.

## What an inventory module is supposed to track

Strip away the marketing and a hospital inventory module has a short, non-negotiable job list. It tracks pharmacy stock and surgical consumables down to the batch and expiry date, not just "40 units of X." It holds reorder levels so a stockout on a vital drug triggers before you're dispensing your last strip. It records goods received (GRN) against the purchase order, so what you paid for matches what landed. It handles department indents and issues, so the ICU pulling gauze shows up as a real movement, not a mystery shrinkage. And it keeps a live valuation you can trust at month-end.

The batch-and-expiry layer should be part of the buyer test. Pharmacy inventory can contain batches with different expiry dates, so ask the vendor to demonstrate the hospital's required issue rule and the resulting audit trail.

_Sources: Devnani et al., J Young Pharm 2010; GST Council 56th meeting recommendations; CDSCO Drugs and Cosmetics Rules (Schedule H1)._

## The India-specific mess your module has to survive

These are workflow and regulatory questions to put to the vendor.

**Schedule H1 register.** Selling a Schedule H1 drug isn't just a sale. Under the Drugs and Cosmetics Rules, the supply has to be recorded in a separate register with the prescriber's name and address, the patient's name, the drug, and the quantity, and those records must be kept for three years and stay open for inspection ([CDSCO / NTEP knowledge base](https://ntep.in/node/938/CP-schedule-h-1-regulation)). If your inventory system can't produce that register on demand, your pharmacy is doing it in a paper ledger, which is exactly where audits go wrong.

**GST on medical supplies.** Every item needs the rate and tax treatment applicable to the hospital's transaction. The 56th GST Council material records medicine-rate changes effective 22 September 2025 ([GST Council](https://gstcouncil.gov.in/sites/default/files/2025-09/press_release_press_information_bureau_0.pdf)). Have finance and the vendor test item-master updates, purchase, sale, return, and credit-note scenarios against the hospital's current tax advice.

**Expiry and multi-store scenarios.** Ask the vendor to demonstrate stock held in every store the hospital operates, including transfer, near-expiry review, count discrepancy, adjustment, and audit reporting. Devnani et al. provides an ABC/VED expenditure analysis, not a benchmark for expiry loss, dead stock, or staff views ([Devnani et al.](https://pmc.ncbi.nlm.nih.gov/articles/PMC3021698/)).

## Compare the quoted inventory workflows

Run the same scenarios with every candidate.

Ask the vendor to show the batch logic, reorder rule, transfer flow, and exception handling in the quoted configuration. A product demo or a module name does not establish that these workflows meet the hospital's requirements.

A pharmacy-management system or ERP may be a relevant candidate when its demonstrated workflow fits the hospital's requirements. Compare it with the HMS module on the same batch, expiry, purchase, transfer, valuation, and register tests.

| Buyer test | Evidence to record |
| --- | --- |
| Batch and expiry | Exact issue rule, near-expiry review, adjustment, and audit output |
| Reorder | Trigger, approval, exception, and lead-time handling |
| Multi-store | Transfer, ward issue, count discrepancy, and reconciliation |
| GST | Item rate, return, credit note, and finance review |
| Schedule H1 | Required register fields, retention, inspection output, and pharmacy sign-off |

Select the product that passes the hospital's documented tests at an acceptable total cost. Do not assume that either a bundled module or a separate product is the right fit before the demonstration.

Devnani et al. is useful background for an ABC/VED review. Use the hospital's own purchasing data rather than treating one tertiary-care study as a universal spend pattern.

## Where Patient Square fits, and where it doesn't

Do not buy Hospital Copilot as an inventory or pharmacy product. The published Hospital Copilot scope does not establish batch control, FEFO, purchase, GRN, stock transfer, GST reconciliation, drug-register reporting, or any other inventory workflow. A hospital that needs those capabilities should choose and verify a dedicated pharmacy or ERP system first.

Hospital Copilot has two record-system paths: use the complete Patient Square HIS/EHR or keep an existing HIS/EHR and use Hospital Copilot alongside it. Neither path proves inventory coverage. During discovery, bring one batch-and-expiry scenario, a ward-indent scenario, and a recall or count discrepancy; ask the implementation team to state whether each is in scope before you sign. Inventory is one part of a larger hospital programme that also touches [revenue cycle](../hospital-revenue-cycle-management-india/) and [bed management](../bed-management-system-hospital-india/), but those product areas must be checked separately too.

The honest verdict: pick inventory software from a documented demonstration of the required controls, not from a broad HMS demo. If you are evaluating Hospital Copilot for its published hospital-record deployment paths, review the [Hospital Copilot page](/in/products/hospital-copilot/) and bring the required workflow list to any evaluation; do not assume inventory is included.

_Sources: [CDSCO Drugs and Cosmetics Rules, Schedule H1 register (NTEP)](https://ntep.in/node/938/CP-schedule-h-1-regulation); [GST Council, 56th meeting recommendations](https://gstcouncil.gov.in/sites/default/files/2025-09/press_release_press_information_bureau_0.pdf); [Devnani M, Gupta AK, Nigah R. ABC and VED Analysis of a Tertiary Care Pharmacy Store, J Young Pharm 2010](https://pmc.ncbi.nlm.nih.gov/articles/PMC3021698/)._

---

## Bed Management in Indian Hospitals: What an HMS Module Really Does
https://patientsquare.com/in/blog/bed-management-system-hospital-india/
Published 2026-01-16 · Updated 2026-08-27 · Tags: bed-management, ipd, hospital, hospital-copilot, india

What a hospital bed-management / IPD module actually tracks in an Indian hospital, what it can't fix, and where it sits inside a Hospital Copilot or HMS.

At its core it tracks the live state of every bed: occupied, vacant, reserved, under cleaning, or blocked. On top of that it records admission-discharge-transfer (ADT) events, the ward or ICU a patient sits in, housekeeping turnaround after a discharge, and a running census. The point is to replace the whiteboard and the phone calls with one screen everyone trusts.

It's 8:40pm in the casualty of a 200-bed hospital in Pune. A patient needs admission to the medical ward. The duty medical officer calls the third-floor nursing station, who says bed 312 is free. The ward clerk, when the patient arrives twenty minutes later, says 312 was given away an hour ago and the whiteboard just hadn't been wiped. So the trolley waits in the corridor while someone walks the floor counting empty beds by eye.

That scene runs on paper, memory, and phone calls in a lot of Indian hospitals. A bed management system is the software that's supposed to end it. Before you buy one, it's worth being clear about what it actually does, and what it quietly can't.

> **Key takeaways**
>
> - A bed-management or IPD module tracks live bed status, admission-discharge-transfer events, ward and ICU allocation, housekeeping turnaround, and a running census. That's the real job.
> - It makes bottlenecks visible. It doesn't fix them. Slow discharges, short-staffed housekeeping, and afternoon discharge dumps stay your problem to solve.
> - In India the module has to handle mixed bed tiers (general, private, deluxe) and scheme-linked beds for PMJAY or state insurance, or the census lies.
> - It belongs inside your HMS, sharing patient identity and billing. A disconnected bolt-on usually adds double-entry.

---

## What a bed management module actually tracks

Strip away the marketing and a bed-management module does five concrete things.

First, live bed status. Every bed carries a state: occupied, vacant, reserved, blocked, or under cleaning. Change one and everyone sees it, so nobody's counting beds by walking the ward.

Second, admission-discharge-transfer. Every time a patient is admitted, shifted between wards, moved to the ICU, or discharged, the module logs it. This is the same ADT backbone that NABH's Access, Assessment and Continuity of Care standard expects a hospital to document properly ([NABH Accreditation Standards for Hospitals, 5th edition](https://healthcarearchitecture.in/wp-content/uploads/2022/01/NABH-5-STD-April-2020.pdf)).

Third, allocation. A ward, a bed number, sometimes a specific consultant's beds, matched against the patient's category and clinical need.

Fourth, housekeeping turnaround. When a bed empties, it flags for cleaning, and it isn't offered to the next patient until it's marked ready. That one loop is where a lot of hidden delay hides.

Fifth, census. A live count of who's where, sliceable by ward, tier, or scheme, that feeds your morning report and your billing desk.

_Sources: [PIB / MoHFW, healthcare infrastructure status](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2080071); [IJPHRD, bed utilization study, 2024](https://medicopublication.com/index.php/ijphrd/article/view/21143)._

When beds are this scarce, how you move patients through the ones you have matters as much as how many you own.

## What it can't fix, and you should hear this before you sign

Here's the honest part. A bed-management module is a mirror, not a fix.

If your discharge summaries get written at 4pm because that's when the consultant does rounds, your beds free up at 4pm no matter how good the software is. If housekeeping has three people for six floors, the "under cleaning" state just shows you the queue you already had. If there's no culture of estimated-discharge-dating on admission, the system can't guess it for you.

We think a lot of buyers are sold on the idea that dashboards create throughput. They don't. Throughput comes from discharge planning, staffing, and the choices your ward teams make at 11am. The software's real gift is that it stops you arguing about *whether* a bottleneck exists, because it's on the screen with a timestamp. What you do next is a management decision, not a feature.

| What the bed module does | What stays a human / process job |
| --- | --- |
| Shows live bed status across wards and ICU | Deciding who gets the next ICU bed |
| Logs every admission, transfer, and discharge | Writing the discharge summary on time |
| Flags a bed as "under cleaning" and blocks reuse | Actually staffing housekeeping to turn it fast |
| Reports census by ward, tier, and scheme | Building an early-discharge culture on rounds |
| Reserves scheme-linked beds by category | Empanelment and payer negotiation |

## The India-specific parts vendors gloss over

A bed system built for a generic hospital breaks quietly in an Indian one, because the bed itself isn't a neutral unit here.

Bed tiers are the first trap. General ward, semi-private, private, deluxe: each has a different tariff, and a patient's insurance or scheme fixes which tier they're entitled to. If the module treats a bed as just a bed, your census can't tell billing what it needs, and you'll reconcile tiers by hand at discharge.

Scheme beds are the second. Hospitals empanelled for AB-PMJAY or a state scheme often reserve a share of beds for scheme patients. Your allocation logic has to respect that reservation, or you'll admit a private patient into a scheme-reserved bed and sort it out painfully later. Bed density makes this sharper: India sits at roughly 0.79 government hospital beds per 1,000 people against an [IPHS norm of one per 1,000](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2080071), and the [World Bank puts overall availability well below the levels of comparable economies](https://data.worldbank.org/indicator/SH.MED.BEDS.ZS?locations=IN). Every reserved-but-empty bed is expensive.

The third is the whiteboard reality. Plenty of well-run Indian hospitals still allocate beds on a physical board because it's fast and everyone can see it. A bed module only beats the whiteboard if it's *faster to update* than a marker. If the nurse has to log into a slow screen to free a bed, she won't, and your live data rots within a week. Adoption is the real project, not installation.

## Where bed management sits inside a Hospital Copilot

Bed management isn't a product you buy alone. It's a module, and it's only as useful as the records around it.

Admission pulls the patient's identity and category from registration. Transfer and discharge events need to reach billing so the tier is priced right. And the discharge summary, the document that actually frees the bed, comes out of clinical documentation. When those pieces live in separate systems, you rebuild the same patient three times and the census drifts.

Hospital Copilot can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Inside either deployment, bed and IPD tracking is one layer of the inpatient picture, sitting alongside the clinical record and the documentation tools. The scribe drafts the note; the note carries the discharge; the discharge frees the bed; the bed shows up in the census. To be plain about limits: our module doesn't submit claims, connect to any insurer or TPA, or file with ABDM. ABDM connectivity is on our roadmap, not shipped. The value we're honest about is upstream, in a cleaner, faster inpatient record that the bed count can trust.

If your delay is mostly the top two bars, no bed module fixes it alone. If it's the third bar, live status genuinely helps.

## So should you buy one?

If your beds are managed on a whiteboard and a phone, and you can't answer "how many free general-ward beds do we have right now" in under a minute, a bed-management module earns its place. It gives you one honest picture and a timestamped record NABH will expect anyway.

But go in clear-eyed. Buy it as part of your [HMS](../hospital-management-system-explained/), not as a disconnected island, so it shares identity with registration, feeds [billing](../hospital-billing-software-india/) the right tier, and connects to the documentation that drives [discharge and the revenue cycle](../hospital-revenue-cycle-management-india/). Sort out bed tiers and scheme reservations before go-live. And fix the human parts, discharge timing and housekeeping staffing, in parallel, because the software will show you those gaps but never close them. The same logic applies to your [supply and inventory side](../hospital-inventory-management-india/): visibility first, then the process work.

Our honest take: if you're a small clinic without an inpatient block, this isn't your priority and a good [clinic management system](../best-clinic-management-software-india/) matters more. If you run wards, book a short demo of [Hospital Copilot](/in/products/hospital-copilot/) and we'll show you the inpatient layer and where its edges are.

_Sources: [World Bank / WHO, hospital beds per 1,000, India](https://data.worldbank.org/indicator/SH.MED.BEDS.ZS?locations=IN); [PIB / MoHFW, healthcare infrastructure status](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2080071); [Indian Journal of Public Health Research & Development, bed utilization study, 2024](https://medicopublication.com/index.php/ijphrd/article/view/21143); [NABH Accreditation Standards for Hospitals, 5th edition](https://healthcarearchitecture.in/wp-content/uploads/2022/01/NABH-5-STD-April-2020.pdf)._

---

## Doximity Scribe Review: Free, but Is It Enough?
https://patientsquare.com/us/blog/doximity-scribe-review/
Published 2026-01-16 · Updated 2026-08-29 · Tags: ai-scribe, doximity, review, free

A dated Doximity Scribe review covering eligibility, 140-minute sessions, 29-day retention, EHR handoff, and when a paid workflow is worth it.

Yes, for the roles Doximity currently lists: verified US physicians, nurse practitioners, physician assistants, certified registered nurse anesthetists, and medical, NP, PA, and CRNA students. A verified Doximity account is required. Recheck eligibility before relying on it because this is a vendor policy.

Doximity Scribe has an unusually strong price: zero dollars for the eligible verified US clinicians it lists. The free offer is not the catch. The real decision is whether its 29-day note window, copy-to-EHR handoff, and note-focused scope fit your week.

Our verdict is simple. Start with Doximity if you qualify and need a portable clinical note. Pay for something broader only after a real visit exposes a missing job.

> **Key takeaways**
>
> - Doximity currently lists physicians, NPs, PAs, CRNAs, and students in those tracks as eligible, with a verified US account.
> - A session can run up to 140 minutes. Notes and transcripts remain available for 29 days.
> - Doximity documents a review, edit, and copy workflow into the EHR. That is useful, but it is not proof of native write-back into every chart.
> - Its announcement says audio is discarded after note generation. The saved note and transcript have a separate 29-day lifecycle.
> - Doximity can be the better choice. A paid tool needs to win on a workflow you will actually use.

## The dated Doximity Scribe facts

The table below uses Doximity's Help Center and product announcement as rechecked on August 11, 2026. It separates what is stated from what still needs a trial.

| Buying question | What Doximity currently states | What that means in practice |
|---|---|---|
| Price | Free for listed eligible roles | No subscription crossover calculation is needed |
| Eligibility | Verified US physicians, NPs, PAs, CRNAs, and listed students | Other roles and non-US users need another route |
| Session limit | 140 minutes per session | Test unusually long visits or groups |
| Note types | H&P, progress, consult, dictation, and custom templates | Verify specialty structure on your own notes |
| Language | Non-English or Other visit mode is available | The public page does not list every language pair |
| Audio | Product announcement says audio is discarded after generation | Confirm contractual terms for your organization |
| Note and transcript | Available for 29 days, then permanently deleted | Move the signed record before the deadline |
| EHR handoff | Review, edit, and copy into the EHR | Portable handoff, not universal native write-back |
| Accuracy | Doximity warns that AI can make mistakes | Clinician review is mandatory |

That is a good free product. It also has boundaries you can test.

## The 29-day rule matters more than the price

Doximity treats audio, notes, and transcripts differently. Its 2025 announcement says audio is processed and immediately discarded after the note is generated. The current Help Center says notes and transcripts remain accessible for 29 days and are then permanently deleted.

For a solo clinician who copies every reviewed note into the EHR on the same day, that may be ideal. The Doximity inbox is a temporary work queue, not a second record archive.

The risk appears when staff leave notes in that queue. A sick day, vacation, or unresolved correction can push work toward the deletion date. Put a control around it:

1. Generate and review the note.
2. Copy the approved version into the legal record.
3. Confirm the chart contains the correct author, date, and encounter.
4. Clear any failed handoff before the 29-day deadline.

Do not use the temporary inbox as your only record.

## The 140-minute and language limits need real visits

A 140-minute session ceiling is far above a routine office encounter. It can still matter for long assessments, group work, or a workflow that pauses and resumes for other tasks. Doximity also provides pause and resume controls, but your trial should reproduce the longest event you expect.

The language wording deserves the same care. Doximity's instructions offer a Non-English or Other mode and say it uses a specialized model. They do not publish an exhaustive language list on that page. Run the exact accent, code-switching pattern, medication names, and specialty vocabulary your patients use. "Supports non-English" is not the same claim as "passed this visit."

## The handoff is copy, not a universal integration promise

Doximity's Help Center explains how to open, edit, and copy a note into the EHR. That is a clear handoff. It can work with almost any chart that accepts text, and it avoids waiting for a custom interface.

It also leaves work with the clinician or staff member. Test whether headings survive, whether the correct patient is open, whether amendments remain attributable, and whether a copied note brings unwanted transcript text. If a vendor says "EHR-ready," ask them to show the exact action after you click Copy.

Native write-back can be worth paying for when it reliably chooses the right chart and section. It can also create a larger integration and support project. Judge the observed workflow, not the adjective.

## Doximity versus Patient Square on the jobs that differ

This is not a contest over who can draft a note. Both products can do that. The decision turns on eligibility, adjacent output, and whether you want a broader practice bundle.

| Decision row | Doximity Scribe | Patient Square Practice Copilot |
|---|---|---|
| Public entry price | Free for listed eligible verified US roles | Assist is $99 monthly or $79 monthly equivalent annually |
| Core output | Editable clinical note with listed and custom templates | Structured SOAP note |
| Coding support | Not established on the reviewed Help Center page | ICD-10 suggestions for clinician review |
| Prescription workflow | Not established on the reviewed Help Center page | Prescription draft for review; no pharmacy transmission |
| Session ceiling | 140 minutes per session | No public comparable ceiling stated |
| Saved-note window | 29 days in Doximity | Verify retention and deletion terms for your account |
| Handoff | Review, edit, and copy to EHR | EHR-ready export (PDF · HL7 · FHIR); not universal native write-back |
| Adjacent modules | Doximity ecosystem, including Dialer and Ask | Scheduling on Assist; AI Copilot EHR and WhatsApp on Copilot |

Patient Square's public price is per clinician. It includes unlimited visits and notes, but a paid plan still has to beat free on your actual workflow. ICD-10 suggestions and a prescription draft are not independent clinical decisions. The clinician remains responsible for review and sign-off.

For a paid comparison, use the complete public ladder. Assist is $99 month-to-month or $79 per clinician per month as an annual monthly equivalent. Copilot is $149 month-to-month or $119 annual monthly equivalent and adds the bundled AI Copilot EHR plus WhatsApp messaging. Autopilot is $249 month-to-month or $199 annual monthly equivalent. The tier names do not change the free-versus-paid test: only buy a paid path when its added work is work the clinic needs.

## The switch decision, without the false upgrade story

A paid scribe is not an upgrade merely because it has a price. Doximity is the better first choice when its eligibility, note types, 140-minute ceiling, 29-day work queue, and copy step fit the clinic. That covers a meaningful number of clinicians. There is no budget prize for replacing a free tool that already reaches a complete reviewed chart.

The case changes when a missing job is visible in the trial. That might be a clinician who needs ICD-10 suggestions beside a structured SOAP note, a prescription draft to review, practice scheduling, or the option to use a bundled AI Copilot EHR. It might also be a practice that cannot use Doximity because its users are outside the listed eligible roles. Those are reasons to compare a paid tool. They are not reasons to assume one is safer or more accurate without observed results.

Keep the comparison narrow. Doximity's documented copy step is a sensible portable handoff. Patient Square's EHR-ready export (PDF · HL7 · FHIR) is also a portability claim. Neither statement establishes automatic filing into a named external chart. If native write-back is the deciding requirement, ask the vendor that claims it to show the entire correction path with your own record system.

## The honest better-fit verdict

Choose Doximity first when all of these are true:

- your role is eligible and your account is verified;
- the note and custom-template workflow covers the job;
- copying reviewed text into the chart is acceptable;
- your team can close the loop well inside 29 days;
- you do not need a paid product's adjacent modules.

Patient Square becomes a credible finalist when the note needs ICD-10 suggestions or a prescription draft for review, when scheduling or the bundled EHR is part of the purchase, or when Doximity eligibility excludes the user. Even then, compare the drafts. A longer feature list cannot rescue a worse note.

Another vendor may win if native write-back into a named EHR is non-negotiable. Patient Square's export wording does not promise that, and Doximity's reviewed instructions describe copy-to-EHR.

## A five-visit test that settles the choice

Use one routine follow-up, one new patient, one medication-heavy visit, one non-English or code-switched visit, and the longest session you reasonably expect. For each tool, record:

| Measure | Doximity | Paid finalist |
|---|---:|---:|
| Minutes from visit end to signed chart |  |  |
| Material omissions |  |  |
| Wrong medications, doses, or negatives |  |  |
| Formatting repairs after handoff |  |  |
| Failed patient or section selection |  |  |
| Unresolved note at end of day |  |  |

Stop the trial if either product creates an unsafe draft pattern. Otherwise, choose the cheaper workflow that reaches a complete, reviewed chart with fewer corrections. For many eligible clinicians, that will be Doximity.

The exercise also prevents a common procurement error: comparing a paid tool's polished output to an imagined version of the free tool. Use the same clinicians, visit types, consent practice, correction standard, and handoff target for both. If a staff member normally completes the chart, include that person. The right choice may be free, paid, or a decision to keep the current workflow for now. The record of the test is more valuable than a generic feature score.

The [best AI medical scribes comparison](../best-ai-medical-scribes/) supplies a broader scorecard. The [any-EHR export guide](../ai-scribe-any-ehr-export/) explains why copy, files, extensions, and write-back should be evaluated separately. Request your 7-day trial if the paid workflow wins the same five visits.

## Patient Square and your existing record system

Practice Copilot can use the bundled AI Copilot EHR from the Copilot tier, or work alongside an existing EHR. Neither route promises automatic filing or write-back into a named third-party EHR.

---

## AI Medical Scribe for a Group Practice: Per-Seat Cost, Admin Controls
https://patientsquare.com/us/blog/ai-scribe-for-group-practice/
Published 2026-01-15 · Updated 2026-07-22 · Tags: ai-scribe, group-practice, pricing, admin, procurement

How to buy an ambient AI scribe for a group practice: per-seat cost maths, admin controls, staged rollout, and procurement questions.

Most scribes price per clinician per month, and a group buys N of those seats on one contract. The group rate is usually a little under the solo rate, and it should be flat per seat, no volume tiers that reset at renewal. The real number to model is total monthly spend across active seats, not the headline solo price.

When a group practice buys an ambient AI scribe, the product is the same one a solo clinician buys. The purchase is not. You are now modeling cost across N providers, standing up one admin dashboard, onboarding a dozen people instead of yourself, and negotiating a contract where the word "seat" quietly decides your bill. This page is about that buy, not the tool itself.

If you're a solo clinician, the [pricing breakdown](../ai-medical-scribe-pricing/) and the [9-question evaluation scorecard](../how-to-evaluate-ai-medical-scribe/) cover your decision. Everything below is the multi-provider version: the per-seat math, the dashboard, the pilot, and the four procurement questions a group should never sign without answering.

> **Key takeaways**
>
> - Scribes price per clinician per month. A group buys N seats on one contract, so your real number is total monthly spend across active seats, usually 10 to 20% under the solo rate.
> - The definition of an "active seat" decides your bill when a provider is on leave or leaves the group. Get it in writing before you sign.
> - One admin dashboard buys you centralized billing, staged onboarding, role controls, and usage visibility. Below roughly 5 providers you can skip it; above that you cannot.
> - Pilot with 3 to 5 providers on real visits for 2 to 4 weeks before you buy seats for everyone. The pilot finds the note-quality issues a demo hides.
> - Four questions to settle in the contract: seat definition, contract term and renewal, per-seat rate lock, and data export on exit.

## Why does group scribe buying differ from a solo purchase?

Because the documentation problem it solves is a group problem, and the buy has moving parts a solo clinician never touches.

Start with the pain. A 2016 time-and-motion study in Annals of Internal Medicine found physicians spent only about 27% of their office day on direct clinical face time, and nearly half on the EHR and desk work, with another one to two hours of after-hours documentation on top ([Sinsky et al., Annals of Internal Medicine, 2016](https://pubmed.ncbi.nlm.nih.gov/27595430/)). In a solo practice that's one person's evening lost. In a 12-provider group it's twelve people's evenings, and it shows up as turnover, reduced clinical hours, and the recruiting bill behind both.

Now the buy. A solo clinician picks a plan and enters a card. A group has to answer questions the solo buyer never sees: who administers the accounts, how billing rolls up, what happens when a provider joins or leaves mid-contract, whether every clinician documents the same way, and who can see usage across the group. Get those wrong and a good tool still lands badly. The rest of this page is those questions, in order.

## How do you model per-seat cost across a group?

Scribes are priced per clinician per month. That's the unit. A group multiplies it by active seats and applies whatever group discount the vendor offers, which is typically a modest cut off the solo rate, not a steep volume break.

Here's the worked example. Numbers below are illustrative round figures to show the method, not a quote; confirm live rates on any vendor's own page before you budget. Say you have 10 providers and a group rate of $80 per seat per month:

**10 seats × $80/seat/mo = $800/mo, or $9,600/yr.**

That looks like the whole cost. It isn't, because two things move it:

1. **Active seats, not headcount.** If two of your ten providers are part-time and document maybe 20 notes a month, you're still likely paying a full seat for each unless the contract says otherwise. Model your bill on seats you'll actually activate, and ask whether a low-volume provider can sit on a cheaper tier or a shared seat.
2. **The group discount is real but small.** Vendors that publish team rates tend to shave 10 to 20% off the solo price, not half. Freed, for instance, publishes team pricing alongside its solo tiers rather than a deep bulk discount ([Freed pricing](https://www.getfreed.ai/pricing)). Don't budget on a fantasy volume break.

Set that against what the status quo already costs. A 2019 Annals of Internal Medicine model estimated physician burnout at roughly $7,600 per employed physician per year, driven by turnover and lost clinical hours ([Han et al., Annals of Internal Medicine, 2019](https://pubmed.ncbi.nlm.nih.gov/31132791/)). Across ten providers that's a modeled $76,000 a year of burnout cost sitting on your P&L whether or not you ever buy a scribe. The scribe line item, at the example above, is a fraction of it. We're not promising the tool erases that number; time-savings vary by clinician and specialty, and you should measure your own. But the comparison reframes which cost is the big one. For the per-clinician version of this calculation, the [ROI math is worked out here](../ai-scribe-roi-calculator-guide/).

## What admin controls does a multi-provider practice actually need?

One dashboard, and it earns its place the moment you pass roughly five providers.

Below that, individual accounts are manageable. Above it, "everyone has their own login" quietly becomes a mess: you can't see who's using the tool, billing arrives as a pile of separate charges, and offboarding a departing clinician means hunting for a password nobody wrote down. A group admin surface fixes four specific things.

- **Centralized billing.** One invoice for all seats, one renewal date, one place to add or remove a seat. No reconciling a dozen personal subscriptions.
- **Provider onboarding and offboarding.** An admin adds a new clinician's seat in a couple of minutes and revokes a departing one the same day. That last part matters for compliance: when a provider leaves, their access to visit data should end cleanly, on your timeline.
- **Role and permission controls.** Not everyone should be an admin. A practice manager who handles billing and seats is a different role from a clinician who only drafts notes. Scope access to the job.
- **Usage visibility.** You can see which seats are active, which providers have adopted the tool, and which bought a seat and never logged in. That's how you catch a stalled rollout in week two instead of at renewal.

None of this changes what the scribe does in the exam room. It changes whether ten people using it feels like one system or ten headaches.

## How should a group standardize note templates across specialties?

Set one structure everyone shares, so any provider can read any chart, then let clinicians adjust how they review and edit within it.

The tension is real. Your family-medicine docs, your behavioral-health clinicians, and your urgent-care shift all document differently, and each will argue their way is right. The group interest is that a covering provider can open a colleague's note at 7pm and find the plan where they expect it. A shared SOAP structure, subjective-objective-assessment-plan in the same order across the group, is usually enough to get that.

One honest point here. AI Medical Scribe returns a structured SOAP note by default, with specialty-aware templates ready out of the box, so a family-medicine seat and a behavioral-health seat each start from a sensible shape. What it does not do is let you build a bespoke, locked-down form library that every provider is forced into. The standard you set across the group is the shared SOAP structure. For a lot of groups that's a feature, not a gap: it keeps a common format instead of letting every provider drift into a private one. If your group's whole value proposition is deep custom templating and coding depth, ask any vendor to show you exactly what that includes and price it, because those are the classic features vendors gate behind a top tier.

## What every seat gets, and what the tiers add

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Every seat in the group gets the scribe from the entry Assist plan. There's no watered-down group tier: the group buys the same plans a solo practice does, at a group rate. Where the plans differ is by capability, not by group size. Assist is the scribe. Copilot adds a bundled AI EHR and WhatsApp messaging. Autopilot layers on an AI receptionist, follow-up automation, priority support, and adoption analytics. A group can put every seat on the same plan or mix them by role.

A few boundaries a buying group should know up front, because they're the same for one seat or fifty. The ICD-10 output is suggestions, not a coding engine, and it doesn't touch anyone's E/M level. The prescription is a draft that reflects what the provider said in the visit; it does not screen for interactions or dosing, and it is not e-prescribing. Each provider is the safety check, reviewing the draft against the chart, adjusting the dose, and sending it themselves. Notes always come back in clean clinical English. And the visit audio is processed in memory and discarded once the note is drafted, with no archive kept, which is the answer you want when your compliance officer asks where a dozen providers' recordings live. The full posture is on our [security page](../../security/).

One thing the scribe deliberately does not do: file into your EHR. There's no HL7, no FHIR write-back, no schedule integration. A provider drafts the note in the scribe and pastes or exports it into your chart. For a group weighing whether it'll still be on the same EHR in three years, that portability is a point in favor, not against.

## How do you pilot an AI scribe before rolling it out to the group?

Run it with 3 to 5 providers on real visits for 2 to 4 weeks, then decide. Don't buy seats for everyone off a demo.

Pick pilot providers who cover your range: your busiest primary-care doc, one specialist, and one skeptic. The skeptic matters. If the tool wins them over on their own patients, you have an internal champion; if it doesn't, you've learned that cheaply, before you signed for twelve seats. Give them two to four weeks, because week one is learning the workflow and the honest signal shows up after that.

Measure four things. First, note quality on your real visits, not a scripted demo: have pilot providers grade a sample of notes for accuracy and how much editing each one needs. Second, time actually saved, self-reported per provider. It'll vary. A 30-patient urgent-care shift and a therapist seeing eight clients have different math, and that variance is the whole reason you pilot instead of guessing. Third, workflow friction, meaning the paste step into your EHR, how the Rx draft fits each provider's sign-off habit, and whether the SOAP structure holds up across specialties. Last, adoption, straight from the admin dashboard. A provider who logged in twice and stopped is telling you something the exit survey never will.

For a sub-10-provider practice, our [two-week rollout plan](../ai-scribe-implementation-small-clinic/) walks the day-by-day version of this. A larger group runs the same shape, just with a bigger pilot cohort and a phased rollout by department after.

## What should a group ask before signing the contract?

Four questions. Settle every one in writing, because each is a place where a fuzzy answer becomes your problem at renewal.

| Question | Why it decides your bill or your exit |
|---|---|
| **How is a "seat" defined?** | Named clinician, concurrent login, or any provider who drafted a note that month? This sets what you pay when someone's on leave or leaves the group. |
| **What's the contract term and renewal?** | Month-to-month protects you during rollout; annual saves money after you're sure. Know the auto-renewal window and the price at renewal, not just year one. |
| **Is the per-seat rate locked?** | A group quote that isn't anchored can drift up at renewal. Get the per-seat number and the renewal terms together, in the same sentence. |
| **How do we export and delete our data on exit?** | You want to export every note as a file and delete any visit on demand, without an integration team in the loop. A hard exit is a warning about the whole relationship. |

We think the seat definition and the exit terms are the two that groups underweight most. The rate is easy to compare on a spreadsheet. The seat definition is what turns a clean $800-a-month line into a surprise when a part-time provider goes on parental leave, and the exit terms are what decide whether switching vendors in year two is a paste-out or a hostage negotiation. On our side: seats are per clinician, pricing is published, and your notes belong to your practice, exportable or deletable anytime. The full ladder, group rate included, is on the [pricing page](../ai-medical-scribe-pricing/), with no "contact sales" wall in front of the number.

## How the group should decide, in five steps

1. Count your active seats, not your headcount. Part-timers and low-volume providers may not need a full seat; ask.
2. Model total monthly spend at the group rate, then set it against the burnout cost you're already carrying across those providers.
3. Confirm you get one admin dashboard: billing, onboarding, roles, usage. Above five providers this is non-negotiable.
4. Pilot with 3 to 5 providers on real visits for 2 to 4 weeks. Grade notes, measure time saved per provider, watch adoption.
5. Before signing, get the four answers in writing: seat definition, term and renewal, rate lock, data export on exit.

The cheapest way to settle it is to stop comparing tables and run the tool on a real clinic week across a few of your providers. A short pilot on your own patients tells you more than any vendor deck. If your group is ready to try that, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and we'll set up a pilot cohort; if you're still narrowing the field, the [honest roundup of the leading scribes](../best-ai-medical-scribes/) ranks them by who fits which practice.

---

## Hospital Billing Software in India: OPD, IPD, Cashless
https://patientsquare.com/in/blog/hospital-billing-software-india/
Published 2026-01-15 · Updated 2026-09-08 · Tags: hospital-billing-software, opd-billing, cashless-claims, india, buyers-guide

A buyer's guide to hospital billing software in India: OPD, IPD packages and discharge settlement, TPA cashless claims, and GST rules.

Three billing worlds, not one. OPD billing has to be fast and high-volume, taking cash and UPI at a counter that clears hundreds a day. IPD billing runs on bed charges, package rates, interim bills, and a discharge settlement that reconciles everything. Cashless insurance billing runs a whole separate track: TPA pre-authorisation, query replies, and final claim submission against IRDAI timelines. A tool that only does OPD counter billing will leave your IPD and insurance desks on spreadsheets.

Hospital billing in India is not one job. It's three, and they barely resemble each other. The OPD counter needs speed and UPI. The IPD ward needs a running account, package rates, and a discharge settlement that ties out to the rupee. And the insurance desk runs a separate track entirely: TPA pre-auth, queries, and a final claim that has to clear against IRDAI timelines. Buy software that only does one well and the other two end up on spreadsheets.

This guide sorts what hospital billing software actually has to handle across those three worlds, what GST really applies (most clinical services are exempt, room rent isn't always), what to look for in a package and TPA engine, and where clean clinical documentation quietly makes billing easier without pretending to be a billing engine.

> **Key takeaways**
>
> - Hospital billing spans three worlds: high-volume OPD (cash/UPI), IPD (bed charges, packages, interim bills, discharge settlement), and cashless claims (TPA pre-auth, IRDAI timelines, NHCX direction). One tool has to carry all three or your desks fragment.
> - Health care services by a clinical establishment are GST-exempt under CBIC Notification 12/2017, but room charges above ₹5,000/day carry 5% GST since July 2022. Your billing engine has to apply the split correctly.
> - The billing features that matter: a package and tariff master, an interim-bill and discharge-settlement flow, a TPA pre-auth and claims queue, and a tight audit trail.
> - Clean documentation feeds cleaner claims. A complete discharge summary means fewer TPA queries. That's where an ambient scribe helps, upstream of billing.
> - When IPD, packages, and cashless are daily work, a dedicated billing/HIS module usually beats bolting billing onto a clinical EMR.

_Sources: CBIC Notification 12/2017-CT(Rate); CBIC Notification 04/2022-CT(Rate); IRDAI Master Circular, 29 May 2024._

If your OPD billing already runs clean and the pain is IPD reconciliation or a TPA queue that never empties, jump to the sections on those. If you're buying fresh, start with the three worlds and be honest about which two you're weakest on today.

## OPD billing: fast, high-volume, cash and UPI

Picture the front desk at a mid-size Pune hospital at 8pm. The OPD has cleared two hundred patients since morning, the queue still has thirty, and the cashier is switching between a UPI QR, a card machine, and a cash drawer without missing a beat. OPD billing lives or dies on that speed.

What OPD billing actually needs is short:

- A bill that closes in seconds: consult fee, a lab line, a pharmacy line, done.
- Every payment mode at the counter: cash, UPI, card, and a running tab for corporate or credit patients.
- A queue and token flow so the counter isn't the bottleneck.
- GST applied right, which for most clinical services means nil (more on that below).

Most billing tools handle OPD counter billing competently. It's the simplest of the three. The mistake buyers make is judging a whole hospital system on a slick OPD demo, then discovering the IPD and cashless sides are thin. OPD is table stakes, not the deciding factor.

## IPD billing: bed charges, packages, interim bills, discharge

This is where billing software earns its price, and where a manual ledger leaks money. IPD billing is a running account, not a transaction. A patient admitted for a surgery accrues charges over days, and the bill has to hold all of it together.

The pieces that matter:

- **Daily accruals.** Bed and nursing charges by category, ICU rates, doctor visit charges, each posting automatically per day rather than being keyed in at discharge from memory.
- **A package and tariff master.** Surgeries are often billed as packages with defined inclusions and exclusions. The software has to hold the package rate, apply it, and flag what falls outside so the ward isn't arguing with the billing desk at discharge.
- **Interim bills.** For a long stay the family needs to pay against a running total. The system should generate an interim bill any day, net it against the advance deposit, and keep the account current.
- **Discharge settlement.** The hard part. At discharge the final bill nets deposits, package inclusions, any cashless approval, and the patient's own share. If this reconciliation isn't automatic, someone does it by hand under time pressure, and that's exactly where revenue slips.

A hospital running a real IPD load without proper package and settlement handling is doing arithmetic that should be automated. If your IPD desk keeps a parallel Excel sheet to "check" the software, the software isn't doing the job. Our wider [hospital revenue cycle guide](../hospital-revenue-cycle-management-india/) walks the same accrual-to-settlement flow end to end.

## Cashless insurance claims: TPA pre-auth to final settlement

The third world is the one that frustrates admin heads most, because part of it is outside your control. Cashless claims run on the insurer and the TPA, and your billing software has to speak their process fluently.

A [TPA (Third Party Administrator)](../tpa-full-form-cashless-explained/) processes claims on behalf of an insurer ([IRDAI policyholder portal](https://policyholder.gov.in/third-party-administrators)). The flow for a planned admission runs like this: the hospital sends a **pre-authorisation** request with the estimate, the TPA or insurer approves an amount, the desk manages **queries** and enhancement requests during the stay, and at discharge the hospital submits the **final claim** with the discharge summary and itemised bills. The approved amount settles with the insurer; the patient pays only the uncovered part.

IRDAI's Master Circular on Health Insurance Business, dated 29 May 2024, sets the clock the desk works against: cashless pre-authorisation within one hour of request, and final authorisation within three hours of the discharge request, with a stated direction toward 100% cashless ([IRDAI](https://irdai.gov.in/documents/37343/365525/Master+Circular++on+Health++Insurance+Business++29052024.pdf)). What your software has to do is give the cashless desk a queue: which pre-auths are pending, which have queries open, which claims are submitted and awaiting settlement, and which have been paid or short-paid. Without that queue, the desk tracks it in a notebook, and short-payments go unnoticed.

Worth knowing where this is heading: the **National Health Claims Exchange (NHCX)**, run by the National Health Authority, is the standard rail for claims between hospitals, TPAs, and insurers. The Ministry announced its national launch for 29 June 2026, and NHA described the NHCX–HMIS implementation as a pilot in its July review ([PIB, 17 July 2026](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2285825)). It will not replace your billing software. Ask vendors for a successful production transaction covering your claim type and payer; treat a launch announcement, sandbox demo, or vague answer as "not verified."

For the documentation side of a clean claim, [what a cashless claim actually needs from the note](../ai-scribe-cashless-claim-documentation/) is a useful companion read.

## GST on hospital billing: exempt, mostly

Here's a rule a surprising number of billing setups get wrong. **Health care services by a clinical establishment are exempt from GST** (nil-rated) under CBIC Notification No. 12/2017-Central Tax (Rate), Sl. No. 74 ([CBIC](https://cbic-gst.gov.in/hindi/pdf/central-tax-rate/Notification12-CGST.pdf)). Consultations, procedures, diagnostics tied to treatment: no GST on the clinical service.

But "mostly exempt" isn't "always exempt," and the room-rent carve-out is the one to get right. Since **18 July 2022, room charges above ₹5,000 per day attract 5% GST** (without input tax credit), and ICU, CCU, ICCU, and NICU are excluded from this, under CBIC Notification No. 04/2022-Central Tax (Rate) ([CBIC](https://cbic-gst.gov.in/pdf/central-tax-rate/04_2022-ctr-eng.pdf)). So a deluxe room at ₹8,000 a night carries 5% GST on the room charge; the ICU bed does not; the surgery itself stays exempt.

Your billing engine has to apply this split automatically: exemption on clinical services, 5% on eligible room rent, and the standard GST rates on any non-clinical retail lines like a cafeteria or a paid attendant meal. Confirm the tool handles the room-rent rule specifically, because it's the item most legacy setups miss. We're not tax advisers, and thresholds and rules do change, so run your exact billing categories past your CA before you finalise a setup.

## What to look for when you buy

Skip the feature count on the brochure. Five things separate a real hospital billing engine from a glorified OPD counter till.

| Capability | Why it matters | Question to ask the vendor |
|---|---|---|
| **Package / tariff master** | IPD surgeries bill as packages with inclusions and exclusions | "Show me a package bill with an exclusion applied at discharge" |
| **Interim bill + discharge settlement** | Long stays need running bills; discharge must reconcile automatically | "Run an interim bill, then a final settlement netting a deposit and a cashless approval" |
| **TPA pre-auth + claims queue** | Cashless is a workflow, not a document | "Show the queue: pending pre-auths, open queries, submitted claims, short-payments" |
| **GST split (exempt vs 5% room rent)** | Legal requirement; commonly misconfigured | "Bill a ₹6,000 room and an ICU night, show the GST on each" |
| **Audit trail** | Every bill edit, discount, and write-off must be traceable | "Who changed this bill, when, and can I lock it after settlement?" |

The audit trail deserves its own line. In a hospital, bills get edited, discounts get given, and write-offs happen. A billing system without a tamper-evident trail of who did what is a governance hole, and it's the first thing an auditor or a suspicious CFO asks about. Make the vendor show you the edit history, not just tell you it exists.

## When a dedicated billing module beats bolting billing onto an EMR

Here's our honest take, and it cuts against selling you anything. **If IPD, packages, and cashless are daily work, buy a dedicated hospital billing or HIS module, not billing bolted onto a clinical EMR.**

The reason is design intent. An EMR is built to document care: the note, the orders, the results. A billing engine is built to price care: a package master, a discharge settlement, a TPA queue, a GST split. A billing bolt-on inside an EMR usually handles OPD counter billing acceptably and then strains the moment an IPD interim bill or a pre-auth query shows up. You can force it, the way you can force any tool past its purpose, but the friction compounds across a busy ward.

There's a narrower case where a bolt-on is fine: a small clinic or day-care setup that's mostly OPD, with light or no IPD and little cashless volume. There, an [EMR with decent OPD billing](../hospital-revenue-cycle-management-india/) may be all you need, and running two systems would be overkill. The test is simple. Count your monthly IPD admissions and cashless claims. If both are meaningful, the billing engine is a separate, deliberate purchase. If both are near zero, the EMR bolt-on will do.

## Named systems to put through an IPD and cashless demo

Two public product pages are worth using as a starting shortlist. [MocDoc's India HMS page](https://mocdoc.com/india) describes outpatient, inpatient, billing, pharmacy, diagnostic, cashless-treatment, pre-authorisation, and paperless-claim workflows. [KareXpert's hospital page](https://www.karexpert.com/enterprise-digital-transformation/) lists IPD/OPD, pharmacy, billing, and insurance modules, including automated billing, real-time charge capture, and e-claims processing.

Those descriptions establish areas to inspect, not a promise that either system fits your tariff master, TPA contracts, or discharge process. Give each vendor the same sample: an IPD package with an excluded consumable, an interim bill against an advance, and a cashless discharge with a query. Ask to see the queue, the ledger, the final settlement, and the audit trail. That comparison is more useful than a feature list.

## Where Hospital Copilot may fit

Better clinical documentation gives a billing team better source material, but it does not decide whether a claim is accepted. A TPA query can involve a missing clinical detail, package terms, policy conditions, or something else outside the note. That distinction matters.

Hospital Copilot is the relevant Patient Square product for this hospital workflow. Its named hospital modules include Claims Management and AI Discharge Summary, and it can use the complete Patient Square HIS/EHR as the system of record or work alongside an existing HIS/EHR. Those module names are not a promise of TPA connectivity, claim submission, automatic filing, claim coding, a package master, GST calculation, or a full billing engine. Validate the exact workflow in a demo.

A few scope points, stated straight, because the market oversells this category:

- The AI Medical Scribe provides a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review and sign-off.
- ICD-10 suggestions are not automated claim coding and do not set claim coding.
- The scribe accepts code-mixed Indian-language input and returns the note in clean clinical English.
- Visit audio is processed in memory and discarded once the note is drafted. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.
- ABDM integration is on the roadmap, not shipped, and no Patient Square product is presented as ABDM-certified.

The right question for a Hospital Copilot demo is narrower: can its named modules fit the documentation and claims workflow beside the hospital's billing process? Keep the billing engine accountable for pricing, package rules, GST, cashless queues, and claim submission. Keep clinical review with the clinician.

## The buying advice we'd give a friend

Sort your three billing worlds by how much pain each causes you today. OPD billing is almost certainly solved. IPD reconciliation and the cashless queue are where the money and the frustration are, so weight your evaluation there, and make every vendor demo an IPD discharge settlement and a TPA queue on your own numbers, not a slide.

Buy the billing engine for the billing job. Then decide whether Hospital Copilot's named documentation and claims modules fit the hospital workflow alongside the existing HIS/EHR or on the complete Patient Square HIS/EHR path. Neither path removes the need to prove billing and TPA workflow details in the demo.

If documentation and claims are the upstream problem, book a Hospital Copilot demo. Bring an IPD discharge case, the cashless queue, your incumbent HIS/EHR, and the billing step that currently creates rework. The hospital team can then evaluate the complete HIS/EHR path and the alongside path without pretending either is a full billing-engine claim.

_Sources: CBIC Notification 12/2017-CT(Rate), Sl. No. 74; CBIC Notification 04/2022-CT(Rate); IRDAI Master Circular, 29 May 2024; PIB / NHA NHCX implementation review, 17 July 2026; IRDAI policyholder portal (TPA)._

---

## AI Medical Scribe for OB/GYN: Prenatal Notes, Two Patients, One Room
https://patientsquare.com/us/blog/ai-scribe-for-ob-gyn/
Published 2026-01-14 · Tags: ai-scribe, ob-gyn, specialty

How an ambient AI scribe handles OB/GYN visits: prenatal and postpartum notes, maternal-fetal records, consent, and clinician review.

It captures the maternal record you dictate and the fetal findings you say out loud, kept as your words in one note. Say the fundal height, the fetal heart rate, the position on Leopold's, and the scribe drafts those into the note. It doesn't measure the fundal height or hear the Doppler for you. You read those; the scribe writes down what you said.

An OB/GYN scribe has a wrinkle no other specialty scribe has. There are two patients in the room, and only one of them can talk. The mother's record and the fetal findings live in one note, and the tool has no idea which is which unless you say so out loud. Get the narration right and it drafts a clean prenatal note about two minutes after you finish. Get it fuzzy and the draft is fuzzy too.

> **Key takeaways**
>
> - ACOG has put ob-gyn burnout at an estimated 40 to 75 percent, with electronic medical record expectations named among the drivers.
> - The fetus and the mother share one record. The scribe won't split findings for you. Dictate maternal versus fetal clearly and the draft stays clean.
> - Consent to record a visit that covers pregnancy is sensitive. You ask, you honor a no, and you can run the visit without the scribe. Audio is processed in memory and never stored.
> - Fetal heart rate, fundal height, position, and cervical exam are captured as your words. The scribe doesn't measure or interpret anything. You do.
> - ICD-10 suggestions like Z34.90 or O24.410 show up next to the draft for you to confirm. They're suggestions, not posted charges.

## Why an OB/GYN visit is harder to document than it looks

A prenatal follow-up looks quick from the hallway. Ten minutes, maybe less for a healthy 28-week patient. But the note packs a lot in: interval history, maternal vitals and weight, fundal height, the fetal heart rate and how you found it, position on Leopold's, edema, urine dip, complaints, plus the counseling and the plan and the labs due. A first-trimester intake runs longer still, with dating, history, and risk stratification on top.

Stack that across a full clinic and the documentation load is real, even when each visit is short. That's part of why ob-gyn burnout runs high. ACOG has cited an estimate that 40 to 75 percent of ob-gyns experience some form of professional burnout, and it named electronic medical record expectations among the pressures. The AMA's 2023 Organizational Biopsy found 20.9 percent of physicians spend more than eight hours a week on the EHR outside normal hours, the charting that follows you home.

The recent evidence points at ambient scribes as one lever. A 2025 JAMA Network Open study of 263 clinicians across six health systems found burnout dropped from 51.9 percent to 38.8 percent after 30 days on an ambient scribe, and obstetrics and gynecology was one of the named subgroups with a statistically significant reduction. That's a burnout signal across a month, not a stopwatch on one note. But it's your specialty on the list.

## The thing that makes OB documentation different: two patients

In almost every other visit, an ambient scribe listens to a conversation between one clinician and one patient and drafts one record. In obstetrics there are two patients, the pregnant person and the fetus, and one of them produces findings you generate yourself, by hand and by Doppler and by ultrasound, that have to land in the same note.

The scribe does not know that a "148" you say is a fetal heart rate and not a maternal systolic. It has no anatomy. It writes down numbers and words in the context you give them. So the burden of separation is on your dictation. If you say "fetal heart tones 148, regular, found in the left lower quadrant," the note is clean. If you just say "148, sounds good," you'll be untangling it at review.

This is worth building into how you narrate an OB visit from day one. Label the finding. "Maternal blood pressure 118 over 72. Fundal height 30 centimeters. Fetal heart rate 150 by Doppler. Cephalic on Leopold's." Four labeled statements, four clean lines in the draft. The scribe is a stenographer for two patients who share a chart, and it can only separate them as well as you do out loud.

## How an ambient scribe fits a prenatal visit

Picture a Tuesday morning prenatal clinic. Your 32-week patient sits down. You start an AI Medical Scribe session and take the visit the way you always do. You ask how she's feeling, whether the baby's moving well, any contractions or leaking or bleeding. She answers. That interval history gets captured.

Then you do the exam and you narrate it. Weight, blood pressure, fundal height in centimeters, fetal heart rate and how you got it, position, edema, deep tendon reflexes if you're checking. You dictate the numbers as you find them. When you counsel her, about kick counts, about the glucose test result, about when to call, you say it plainly and the scribe keeps it.

You stop the session at the end. About two minutes later there's a draft: interval history, exam with the maternal and fetal findings you dictated, assessment, plan, and what's due at the next visit. You read it, fix anything the tool misheard, and sign.

AI Medical Scribe is one module inside Practice Copilot. It listens during the visit and hands back a structured note, ICD-10 suggestions, and a prescription draft to review, ready about two minutes after you finish. The note comes back in English, the audio is never stored, and any prescription output is a draft you review, never something sent to a pharmacy on its own. If you want the mechanics of consent and PHI handling, our [HIPAA, BAA, and consent guide](../ai-scribe-hipaa-baa-consent/) walks through it.

## Consent is different when the visit is about a pregnancy

Every ambient scribe raises a consent question: is it okay to have this visit recorded and drafted by a tool? In OB/GYN that question carries more weight, because the visits carry more weight. A visit that discusses a wanted pregnancy, a loss, options counseling, infertility, or a genetic-screening result is not a routine encounter. Some patients will not want a recording running while they talk about it, and that's a completely reasonable line to draw.

So treat consent as a conversation, not a checkbox the software owns. You tell the patient a tool is helping you write the note, you ask if that's okay, and if she says no, you turn it off and chart the old way. The point is that the clinician holds this decision at the bedside, in the moment, reading the room. The tool never overrides that.

Two things make this easier to honor. First, the audio is processed in memory and never stored, so a declined patient isn't leaving a recording anywhere. Second, recording-consent law varies by state, and a handful require all parties to agree before any recording. Our [state-by-state consent guide](../ai-scribe-patient-consent-by-state/) covers where that applies. The clinical sensitivity of an OB visit sits on top of the legal baseline, and both point the same way: ask first, and mean it.

I'll say plainly what I think here. The right default in a pregnancy-options or pregnancy-loss visit is to ask before you start the session, not after, and to make the no easy. A patient who feels she has to justify declining a recording is a patient you've already made uncomfortable in a visit that was hard enough.

## What the scribe captures versus what you own

This is the line that matters most, and OB/GYN makes it sharp. The scribe writes down what you say. It does not generate clinical findings, and in obstetrics that distinction is not abstract.

| Finding | What produces it | What the scribe does |
|---|---|---|
| Fetal heart rate | Your Doppler or the tracing you read | Records the number and rhythm you say aloud |
| Fundal height | Your tape measure | Writes the centimeters you dictate |
| Fetal position | Your hands on Leopold's | Notes cephalic or breech as you state it |
| Cervical exam | Your exam | Captures dilation, effacement, station you say |
| Ultrasound findings | The read you or the sonographer performed | Drafts the interpretation you dictate, not the images |
| Gestational age | Your dating | Writes the weeks and days you state |

Every left-hand item is yours. The Doppler is in your hand. The tape measure is yours. The dating is your call. The scribe never listens to the fetal heart, never measures a fundus, never reads a scan. It captures the spoken record of the clinical work you already did. If you don't say the fetal heart rate out loud, it isn't in the note. The tool has no other way to know it.

Same logic for ultrasound. If you or your sonographer read a growth scan, dictate it, biparietal diameter, estimated fetal weight, amniotic fluid index, placental location, and the scribe drafts that interpretation in your words. It is not looking at the images. The read is yours.

## Postpartum, gyn, and the mixed clinic day

OB/GYN isn't only prenatal. A single clinic session can swing from a new-OB intake to a postpartum check to an annual well-woman exam to a colposcopy follow-up. The vocabulary changes room to room, and a scribe built for one flow shouldn't fall apart in the next.

A postpartum visit has its own shape: mood screening, incision or perineal healing, bleeding, breastfeeding, contraception plan, and a note that reflects the delivery it follows. The narration approach carries across all of them. You say what you find and what you counsel, and the draft follows your words. What you can't do is assume the scribe knows this is a six-week postpartum and not a routine gyn visit. It knows what you say. Say it.

Back-to-back rooms with different visit types is exactly where notes can bleed into each other in a weaker tool. Read each draft closely for the first week or two, and you'll learn where this one holds a clean boundary between rooms.

## What the scribe suggests for coding, and what it won't do

OB/GYN coding is trimester-aware and detail-heavy. Supervision of a normal pregnancy splits by trimester and by whether it's the first pregnancy. Complications carry their own families: gestational diabetes, preeclampsia, hyperemesis, each with weeks-of-gestation specificity.

The scribe reads your dictated assessment and suggests codes to match: Z34.90 for supervision of a normal pregnancy, unspecified trimester, O24.410 for gestational diabetes in pregnancy, diet-controlled, and so on. They show up next to the draft as suggestions. You confirm the ones that fit, change the ones that don't, drop the rest. The scribe has no line into your billing and posts nothing. A code in the draft is a prompt for your judgment, not a claim.

The OB-specific catch: the specificity that drives correct coding is the same specificity that drives denials when it's missing. If your dictated assessment says "diabetes in pregnancy" without diet-controlled versus insulin-controlled, without the trimester, the suggestion will be vague because that's all you gave it. Dictate the full picture and the suggestion sharpens. For how the suggestions get generated and where they miss, see our [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/).

## Where an OB/GYN scribe stops, and where it's the wrong tool

Being straight about the limits matters more than a feature list. The scribe drafts what you dictate. It doesn't read your ultrasounds, doesn't interpret a fetal heart tracing, doesn't flag that your dictated fundal height is small for the dates you stated. If you call the position cephalic and then dictate a breech plan, the scribe won't catch the contradiction. That's your review, and in obstetrics the stakes on that review are high.

It also doesn't integrate with anything. Not your EHR, not your prenatal flowsheet, not an antepartum record or an L&D board. You get a draft, you review it, you copy or export it into wherever you chart. If your practice's real pain is data flowing between your OB module and your chart, an ambient scribe is the wrong purchase. That's interoperability, and a scribe doesn't touch it.

And if what you want is automated structured data pulled straight off the ultrasound machine or the fetal monitor into a coded report with no dictation, this isn't that either. It captures spoken clinical work. If you never plan to say the read out loud, this tool isn't for you.

## How to evaluate a scribe against your own OB/GYN clinic

A single demo note tells you almost nothing about a real prenatal day. Run it on your own clinic during a trial. A few tests are worth doing.

First, dictate a full prenatal exam with labeled maternal and fetal findings and check whether the draft keeps them separate and in your language. Second, narrate a growth-scan read and see whether the draft captures the measurements without pretending to have seen the images. Third, run it across a mixed half-day and see whether a new OB, a postpartum, and a well-woman stay distinct instead of blurring. Fourth, and this one's specific to you, run a visit where you'd normally handle consent carefully and confirm turning the session off is genuinely frictionless.

Accuracy across a real week, and how to read the first drafts, lives in [what to expect from scribe accuracy](../ai-scribe-accuracy-what-to-expect/). And because pediatrics shares the shape of documenting a patient who can't self-report, our [pediatrics scribe breakdown](../ai-scribe-for-pediatrics/) is a useful companion on narration discipline.

If you want to see draft quality against your own prenatal notes and OB vocabulary before committing anything, book a demo and bring a typical complex case. That's the right test for OB/GYN, and it's the one we'd run in your shoes.

---

## IVF Clinic Software in India: What Fertility Practices Need
https://patientsquare.com/in/blog/ivf-clinic-management-software-india/
Published 2026-01-14 · Tags: ivf-software, fertility-clinic, art-act, emr, india, buyers-guide

Compare IVF clinic software in India for fertility workflows, ART Act records, pricing, reproductive-data privacy, and AI documentation.

Four things a general OPD tool never models: stimulation-cycle and follicular-monitoring tracking day by day, embryology lab records with witnessing steps and cryo-storage inventory, donor and gamete traceability, and the statutory consent and reporting that the ART Act 2021 demands. Generic clinic software handles the appointment book and billing fine, but a fertility cycle is a longitudinal protocol, not a single visit, and that is where it falls short.

An IVF cycle is not a visit. It is a protocol that runs for weeks: baseline scan, stimulation, a string of follicular-monitoring ultrasounds, trigger, retrieval, the embryology lab, transfer, then the wait. Generic clinic software was built for the single consult, so it has nowhere clean to hold a stimulation chart, a witnessing log, or a straw sitting in a tank. That gap is the whole reason fertility-specific software exists. This guide walks through what an ART clinic in India actually needs, the ART Act 2021 record-keeping layer that sits on top of clinical care, what prices look like, the DPDP duties that come with reproductive data, and where an AI documentation layer fits without pretending to be your embryology system.

> **Key takeaways**
>
> - A fertility cycle is longitudinal, so the software has to track stimulation and follicular monitoring day by day, hold embryology lab records, and trace donor and gamete material. Generic clinic tools model none of this.
> - The ART Act 2021 makes cycle, donor, and outcome record-keeping a legal duty, with registration and reporting to the National ART and Surrogacy Registry (India Code). Your software has to produce those records on demand.
> - Reproductive data is among the most sensitive a clinic holds. Under the DPDP Act 2023 you are the data fiduciary, so purpose and storage limits are legal, not optional (MeitY).
> - An AI documentation layer drafts the consult note for the clinician to review and sign. It does not do embryology witnessing, cryo-inventory, or registry reporting. Those stay in your specialist systems.

_Sources: The ART (Regulation) Act, 2021 (India Code); MeitY, DPDP Act 2023._

If your practice management already works and the drain is the note you type after every consult, you can skip ahead and book a short demo to see where a documentation layer lands. If you are choosing the core system, start with what fertility work demands.

## What does an IVF clinic actually need from software?

Set the brochure aside. A fertility practice needs the same booking-and-billing spine any clinic does, plus four things that are specific to assisted reproduction. Miss those four and you end up running the real work in spreadsheets beside the software you paid for.

1. **Stimulation and follicular-monitoring tracking.** A cycle is a dated protocol. Gonadotropin doses change across days, and each monitoring scan records follicle counts and sizes and endometrial thickness. The software has to hold that as a timeline you can read at a glance, not as loose notes scattered across separate visit records.
2. **Embryology lab records.** This is the domain generic tools have no home for. Fertilization method, day-3 and day-5 grading, witnessing steps at each handling point, and cryo-storage inventory that tells you which straw sits in which tank and cane. Losing track of a frozen embryo is not a data-entry slip; it is a clinical and legal event.
3. **Donor, recipient, and gamete traceability.** Where third-party gametes are used, the chain from donor to recipient to outcome has to be recorded and auditable. The ART Act 2021 leans hard on this, and the software has to make the link, not leave it to memory.
4. **Consent and statutory record-keeping.** ART involves multiple distinct consents across the cycle, and the [ART Act 2021](https://www.indiacode.nic.in/handle/123456789/16824) requires the clinic to hold and produce records for the National Registry. The tool has to store the right consents against the right cycle and export what the registry expects.

Package and cost estimation matters too, because an IVF cycle is a large, itemised bill, and patients ask for a number before they commit. GST-compliant billing that ties line items back to the cycle is table stakes. Everything past these is a tie-breaker, so decide which of the four you cannot fake in a spreadsheet, then judge tools on those.

## ART software and generic clinic software diverge on two axes

Two things separate software built for fertility from software that merely tolerates it, and they map to the two halves of an IVF clinic: the clinic side and the lab side.

On the **clinic side**, it is the cycle timeline. A general OPD tool treats today's visit as a self-contained consult, so a stimulation protocol becomes a pile of disconnected notes. ART software makes the cycle the unit of work, the way a good dental tool makes the tooth the unit of work. You open one cycle and see the whole arc: baseline, every monitoring scan, the trigger, the retrieval count. For a broader view of how India-native systems compare on the clinic side, our [EMR software guide](../emr-software-india-guide/) and the [clinic management software scorecard](../best-clinic-management-software-india/) are useful reading.

On the **lab side**, it is the embryology record and cryo-inventory. This is not a module you can approximate. Witnessing (the second-person verification at each handling step that guards against mix-ups) has to be logged, and cryo-storage has to know physical location down to the tank. A generic clinic tool's inventory feature was designed for pharmacy stock; it has no concept of a straw or a witnessing signature. When you evaluate a "fertility module" bolted onto general software, this is the first thing to stress-test.

Rows describe what each software category is designed to hold, not a specific vendor's build. Where a cell says "confirm it," ask the vendor to demonstrate the export live before you sign, because a claim on a slide is not the same as a working registry file.

## How does the ART Act 2021 change the record-keeping requirement?

More than most first-time buyers expect. The [Assisted Reproductive Technology (Regulation) Act, 2021](https://www.indiacode.nic.in/handle/123456789/16824) turned fertility record-keeping from good practice into a statutory duty, and the software you pick either helps you meet it or quietly makes it harder.

Three points bear directly on the software choice:

- **Registration and the National Registry.** ART clinics and banks must register, and the Act sets up the [National ART and Surrogacy Registry of India](https://main.mohfw.gov.in/) that clinics report into. Your software has to hold cycle, donor, and outcome data in a shape you can export for that reporting, not lock it in a format only the vendor can read.
- **The companion Surrogacy Act.** The [Surrogacy (Regulation) Act, 2021](https://www.indiacode.nic.in/handle/123456789/16821) runs alongside the ART Act with its own registration and record rules. If your clinic touches surrogacy, the record-keeping surface is wider, and the software has to keep those records distinct and auditable.
- **Outcome tracking for your own audit.** The Act's record demands mean you will track cycle-to-outcome data anyway. Used well, that same data lets the clinic audit its own process over time. Treat it as an internal quality tool, not a marketing number, and never let a vendor turn your outcome data into a success-rate claim on a brochure.

The clean test to put to any vendor: show me, on a live cycle, exactly the records the National Registry expects, and export them. A tool that cannot do that on demand is a compliance risk you inherit the day an inspector asks.

## IVF software pricing in India: what to actually budget for

Here is the honest part the listicles skip: India-native ART and fertility vendors mostly sell demo-first and do not publish a rupee figure, so the price flexes with how hard you negotiate and how many modules you switch on. When a number does surface, it tends to land in the low-to-mid thousands per user a month before the 18% GST, and the embryology or lab module is frequently a separate line.

That last point is where budgets slip. A quote for the "clinic" side can look reasonable until you ask what the embryology records, cryo-inventory, and statutory reporting exports cost, and find they are add-ons. So price the whole stack, not the entry tier. A ₹5,000 per user quote becomes ₹5,900 with GST, and if the lab module doubles it, your real monthly number is nothing like the headline.

Three questions settle most of the ambiguity. First, is the embryology lab module included or extra? Second, does statutory registry export come standard or as a paid feature? Third, what counts as one seat, a clinician, a workstation, or a location? Get all three answered in writing, ex-GST, before you sign. The same "₹X per user" means very different things depending on the answers.

## The DPDP Act makes reproductive data your legal responsibility

Reproductive data is about as sensitive as clinical data gets, so it deserves the strictest handling in the building. The [DPDP Act 2023](../dpdp-act-clinics-guide/) does not create a formal sensitive-data category the way some laws do, but that is not licence to treat fertility records casually. Under the Act the clinic is the **data fiduciary**, and that role carries duties you cannot hand to the vendor.

Two duties bite hardest here. **Purpose limitation** means you use donor, recipient, and cycle data only for the treatment purpose the person consented to, and not for anything outside the notice you gave. A vendor quietly mining your patient list for its own ends is a liability that lands on you, not them. **Storage limitation** means you keep data only as long as the purpose needs. That runs into a wall: ART record-keeping norms expect records held for defined periods. The fix is a written retention policy that reconciles both. Not "keep everything forever."

Then the physical question: where does the data sit, and how do you get donor and recipient records back if you leave? Cloud software puts some of the most sensitive records a clinic will ever hold on someone else's servers. Ask where they live, how they are protected, and what the exit looks like. A vendor that cannot answer both crisply is a vendor that makes your DPDP posture worse.

## Where does AI documentation fit in a fertility clinic?

In the consult note, and nowhere near the embryology bench. This is the part where an ambient layer earns its place without overreaching, and the boundary matters more here than in most clinics.

A fertility consult still produces a written record: the history, the discussion of options and risks, the plan for this cycle, the counselling that took the bulk of the appointment. Typing that up between emotionally heavy consultations is where a busy day quietly runs long. An ambient documentation layer listens during the visit and drafts that note, which the clinician then reviews, edits, and signs. It does not touch the stimulation chart, the embryology record, the cryo-inventory, or the registry export. Those live in your specialist systems, and they should. The AI does one job: it hands back the consult note as a draft, faster than typing from memory after the patient has left.

A few design points matter for an Indian clinic specifically. Consults happen in braided Hindi and English, so the layer takes code-mixed speech and returns the note in clean clinical English. The visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner posture under the DPDP Act given how sensitive fertility conversations are. And the output is always a **draft**: the clinician reviews and signs, the software never signs for you. Any prescription it suggests is a draft to check, not an order it sends, and any ICD-10 code is a suggestion, not a final coding decision. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

That layer is [Practice Copilot](/in/products/practice-copilot/), our AI bundle for Indian clinics, with the ambient documentation module doing the note-taking. We publish our prices rather than gating them, and we are candid about scope: ABDM integration is on our roadmap, not shipped, and we will not badge a status we do not hold. We do not claim to do embryology witnessing or statutory reporting, because that is not what an AI note-drafter is for. If your prescriptions also eat time, the [prescription drafting guide](../scribe-for-doctors-india/) covers where that fits, and the [NABH documentation guide](../nabh-documentation-requirements/) is worth a read if accreditation is on your horizon.

The buying advice we would give a friend who runs an ART clinic: choose the core system on the cycle timeline, the embryology records, and the registry export, because those are the parts that are hard to replace and legally load-bearing. Then decide separately whether the consult note is eating your evenings. If it is, add a documentation layer on top rather than rebuilding around it. Book a short demo and watch a real consult turn into a draft note before you commit to anything.

_Sources: The ART (Regulation) Act, 2021 and The Surrogacy (Regulation) Act, 2021 (India Code); National ART and Surrogacy Registry (MoHFW); MeitY, DPDP Act 2023; NHA / ABDM portal._

---

## AI Scribe for Orthopedics: A Buyer's Guide for Busy Ortho Clinics
https://patientsquare.com/us/blog/ai-scribe-for-orthopedics/
Published 2026-01-13 · Updated 2026-07-22 · Tags: ai-scribe, orthopedics, specialty

How an AI medical scribe for orthopedics captures injection notes, fracture care, ROM and neurovascular exams, and post-op follow-ups in high-volume clinics.

It captures them if you say them. When you narrate 'right knee flexion 120 degrees, extension to neutral,' those values land in the exam section. It does not read a goniometer or estimate range on its own. The spoken number is what gets documented, so build the habit of saying it.

An AI medical scribe for orthopedics listens during your visit and drafts the note while you examine the knee, so you finish charting minutes after the patient leaves instead of after dinner. It captures what you say out loud during injections, fracture checks, and ROM exams, then hands back a structured SOAP note you review and sign. You still confirm every code.

> **Key takeaways**
> - Office physicians spend more than five hours in the EHR for every eight hours scheduled with patients, per AMA-cited research.
> - A 2025 JAMA Network Open study of 263 clinicians found burnout dropped from 51.9% to 38.8% after 30 days on an ambient scribe.
> - A scribe captures what you narrate: injection site, needle gauge, ROM in degrees, neurovascular status. Say it, and it lands in the note.
> - AI Medical Scribe by Patient Square drafts a note in about two minutes, suggests ICD-10 codes you confirm, and exports into your EHR. It does not integrate.

## Why does ortho documentation eat so much of your day?

Picture a Monday fracture clinic. Thirty patients on the schedule, three joint injections before lunch, two post-op checks squeezed between new consults. Every visit needs a procedure note, an exam with ROM in degrees, a neurovascular check, and a plan. By 6pm you have a stack of unfinished notes and a decision: stay late or take them home.

That math is not unique to you. Office-based physicians spend more than five hours in the EHR for every eight hours of scheduled patient time, according to research the AMA cites on documentation burden. Ortho makes it worse. Procedure notes, imaging correlation, and injection logs pile onto an already-packed encounter.

An ambient scribe changes where the note gets written. Instead of typing after the visit, you talk through the exam and procedure the way you already do, and the draft is waiting when you walk out of the room.

## What ortho note elements does an AI scribe actually capture?

A scribe writes down what it hears. If you narrate the injection out loud, it captures the injection. If you say the ROM number, it records the number. The clinician who talks through the exam gets a fuller note than the one who works in silence.

Here's what that looks like across common ortho encounters.

| Ortho note element | What you say out loud | What lands in the draft |
|---|---|---|
| Joint injection | "20-gauge needle, 40mg triamcinolone, right knee, sterile prep" | Procedure note with site, agent, dose, technique |
| Aspiration | "Aspirated 15mL cloudy fluid, sent for crystals and culture" | Volume, appearance, labs ordered |
| ROM exam | "Right shoulder flexion 120 degrees, abduction 90" | Structured ROM values by joint and plane |
| Neurovascular check | "Distal pulses 2+, sensation intact, cap refill under 2 seconds" | Documented NV status |
| Fracture care | "Nondisplaced distal radius, splinted, follow-up two weeks for repeat films" | Diagnosis, intervention, follow-up plan |
| Post-op follow-up | "Incision healing well, sutures out, weight-bearing as tolerated" | Wound status, activity progression |

Note what the scribe does not do. It does not read your fluoroscopy screen. It does not pull the last visit's ROM from the chart. It writes what you narrate. So the habit that matters is speaking the number: "flexion to 120," not a silent goniometer read.

## How does a scribe handle injection and aspiration procedure notes?

Injections and aspirations are where ortho documentation gets fiddly. You need the site, the laterality, the needle, the agent, the dose, the technique, and the response. Miss one and the note is thin, or the billing gets flagged.

Say it as you do it. "Sterile prep, 22-gauge, 1mL lidocaine then 40mg Kenalog, left subacromial space, patient tolerated well." The scribe puts those pieces into a procedure note in the order a reviewer expects to read them. You check it against what actually happened and sign.

We think this is the strongest use case in ortho, honestly. Procedure narration is already a spoken habit for most surgeons. You're describing the steps to the patient and the medical assistant anyway. The scribe just stops that narration from evaporating.

## Does it work for fracture care and post-op follow-up notes?

Yes, with the same rule. Fracture visits move fast: read the films, name the fracture, splint or cast, set the follow-up. A post-op check is a quick loop through wound, hardware, ROM, and weight-bearing status.

Narrate the loop. "Second post-op week, incision clean and dry, no drainage, sutures removed, advancing to weight-bearing as tolerated, back in three weeks." The draft comes back structured, and you spend your review time confirming the plan instead of typing it from scratch. For high-volume clinics running 30-plus visits a day, shaving a few minutes off each note adds up before you notice.

## Does an AI scribe reduce burnout for orthopedic surgeons?

The evidence points that way. A 2025 study in JAMA Network Open followed 263 clinicians across six US health systems using an ambient AI scribe. After 30 days, reported burnout fell from 51.9% to 38.8%, with measured improvements in after-hours documentation time and cognitive load.

That study covered ambulatory clinicians broadly, not ortho specifically, so read it as directional rather than a promise about your clinic. Still, the mechanism is the same everywhere: less typing after hours, fewer notes carried home. If your surgeons are doing pajama-time charting after a full OR block, that's the hour a scribe is aiming at.

## What can this scribe not do? (The honest limits)

Buying software on marketing claims is how clinics end up disappointed. So here are the lines we won't cross in describing it.

- It does not integrate with your EHR. It drafts the note, and you copy or export it into your system. No HL7, no FHIR, no live chart write-back.
- ICD-10 codes are suggestions you confirm, not auto-posted charges. You read them, you accept or fix them, you own them.
- Prescriptions come back as a draft. You review and sign; nothing goes to a pharmacy on its own.
- Notes are English. If your visit runs in another language, the note still comes back in English.
- Audio is never stored. The scribe listens, drafts, and discards the recording. There's no audio file sitting on a server.
- No accuracy percentage is promised, because the note quality tracks what you say. Silent exam, thin note.

That last one is the honest heart of it. The scribe is a stenographer, not a clinician. It captures your words. It does not diagnose, and it does not invent findings you didn't voice. If you want the code-review mechanics, our explainer on [how an AI scribe suggests ICD-10 codes](../ai-scribe-icd-10-suggestions-explained/) walks through the confirm step.

For the record, the canonical version: AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

## How does this compare to other ambient scribes?

Plenty of ambient scribes exist, and some are built for enterprise health systems with deep EHR integrations and a long procurement cycle. If your hospital already runs a system-wide ambient platform wired into your EHR, that tight integration is a real advantage, and it may be the better fit for you. Chasing a second tool on top of it rarely pays off.

Where a lighter scribe fits is the independent or small-group ortho practice that wants faster notes without an IT project. You export into whatever EHR you run. You aren't waiting on an integration team. You're reviewing drafts on day one. For the privacy side of that trade, [how AI scribes handle HIPAA, BAAs, and consent](../ai-scribe-hipaa-baa-consent/) covers what happens to the audio.

## How do you roll it out in a high-volume ortho clinic?

Start with one surgeon and one clinic day. Injection-heavy days are a good test because procedure narration is the clearest win. Have the surgeon talk through exams and procedures out loud the way they would for a student, and review the first week of drafts closely to calibrate.

A few practical notes:
- Brief your medical assistants. Their in-room narration gets captured too, which helps.
- Build the speaking habit early. "Flexion to 120" beats a silent goniometer read every time.
- Keep a human in the loop on every code and every Rx draft. That's not optional; it's the design.

New to ambient scribes entirely? Start with [what an AI medical scribe is](../what-is-an-ai-medical-scribe/), then read [how clinicians cut charting time](../reduce-charting-time-clinicians/) for the workflow picture. Primary care teams sharing ortho overflow may also want [the primary care scribe guide](../ai-scribe-for-primary-care/).

Want to see it on your own injection notes? Book a demo and bring a typical Monday clinic day. You can try it free first if you'd rather test before you talk to anyone.

---

## Doctor Appointment Scheduling Software in India: A Clinic Buyer Guide
https://patientsquare.com/in/blog/doctor-appointment-scheduling-software-india/
Published 2026-01-13 · Tags: appointment-scheduling, booking-software, india, buyer-guide

Choose Indian clinic scheduling software by testing online booking, WhatsApp and SMS reminders, walk-ins, booked visits, and system handoffs.

It is the tool that takes a booking, holds a slot, and gets the patient in front of the right doctor at roughly the right time. In an Indian clinic that means online and phone booking, a multi-doctor calendar, WhatsApp or SMS reminders, and a way to fit walk-ins around the booked slots. Some products stop at the calendar. Others sit inside a full clinic system that also runs the OPD queue, billing, and records.

Doctor appointment scheduling software is the tool that takes a booking, holds the slot, and gets the patient in front of the right doctor at close to the right time. For an Indian clinic that also means reminding the patient so they actually show, and fitting the walk-ins around the booked ones without either group revolting. Pick it for the messy evening, not the calm slide deck. This guide walks what to look for, where a standalone scheduler quietly stops working, and how the booking calendar connects to the rest of the clinic.

> **Key takeaways**
>
> - Reminders work, within limits. A 2026 meta-analysis of 10 randomised trials found appointment reminders lifted outpatient attendance by about 11%, with SMS slightly ahead of phone calls.
> - In Indian clinics, forgetfulness and missing reminders are the top reasons patients skip appointments, per a PGIMER Chandigarh study. A reminder recovers the forgetters, not the never-meant-to-comes.
> - Almost every Indian OPD needs a hybrid of booked slots and a walk-in lane. Pure appointments break the first time a neighbour turns up with a fever.
> - Payment at booking cuts casual no-shows because the patient now has skin in the game.
> - A standalone scheduler is fine when booking is your only gap. When the calendar, queue, bill, and note live in four systems, it becomes a fifth screen to reconcile.

_Sources: Al-Turbag et al., JHMHP 2026; Irving et al., BMJ Open 2017._

## The 8pm OPD that scheduling is supposed to prevent

Picture a two-doctor clinic in a Tier-2 town at 8pm. The evening OPD was supposed to end at 7:30. It hasn't. The front desk has a paper register, a WhatsApp inbox with fourteen unread booking requests, and a waiting room where nobody is sure whether they are ahead of or behind the man who "called in the morning." Two booked patients left because a walk-in surge pushed them an hour back. One of tomorrow's confirmed 11am slots will not turn up, and nobody will know why.

That scene is a scheduling problem wearing three disguises. Booking chaos, reminder gaps, and a broken walk-in-versus-booked balance. Good scheduling software attacks all three. The trick is knowing which one is actually hurting you before you buy anything, because a slick online booking page does nothing for the walk-in imbalance, and a walk-in token system does nothing for the 11am no-show.

For the queue side of that evening, our [queue management guide](/in/blog/clinic-queue-management-india/) covers tokens and display boards, and the [OPD software buyer guide](/in/blog/opd-software-for-clinic-india/) covers registration speed and the note flow. This piece is about the booking calendar that sits upstream of both.

## What online booking has to get right

Online booking sounds simple. A patient picks a slot, the clinic confirms it. In practice the details decide whether it saves the front desk or buries it.

The **multi-doctor calendar** is the spine. A patient booking with Dr. Sharma should never be able to grab Dr. Iyer's slot by accident, and the system has to know that Dr. Sharma does mornings on Tuesday and evenings on Thursday. If the calendar can't hold different doctors' different hours cleanly, the front desk ends up manually policing every booking, which defeats the point.

**Booking channels matter more in India than the demos admit.** A meaningful share of your patients will book over WhatsApp or a phone call, not a web form, because that is how they already talk to the clinic. A scheduler that only works through a polished web page leaves the front desk copying WhatsApp requests into the system by hand. The good ones pull WhatsApp and phone bookings into the same calendar the online form feeds, so there is one source of truth instead of four.

**Slot rules keep the calendar honest.** Buffer time between patients so a running-late consult doesn't cascade, a cap on how many can book the same slot, and a way to block time for procedures or a lunch break. Without these, online booking just lets the internet overbook your doctor faster than the front desk ever could.

Test it with a returning patient on a two-doctor day. Watch whether a WhatsApp booking and a web booking land in the same place. That five-minute test tells you more than the feature list.

## Reminders: what the evidence actually says

Here is the part worth getting right, because it is where clinics both over-hope and under-invest.

Reminders work. They do not work miracles. A 2026 systematic review and meta-analysis of 10 randomised controlled trials found that appointment reminders raised outpatient attendance by roughly 11% compared to no reminder (risk ratio 1.11, 95% CI 1.05 to 1.19), and that SMS reminders (RR 1.14) edged out telephone reminders. That is a real, repeatable lift, not a rounding error, and it costs almost nothing to send.

Why does it help in an Indian clinic specifically? Because the thing reminders fix is forgetting, and forgetting is the main driver here. A study of missed outpatient appointments at PGIMER Chandigarh found forgetfulness and a lack of appointment reminders were the two leading reasons patients did not show, and forgetfulness correlated significantly with missed visits (r=0.392, p &lt; 0.001). A reminder does nothing for the patient who booked and then decided not to come. It rescues the one who fully meant to come and lost track of the day. That second group is bigger than most front desks assume.

So set expectations correctly. A reminder is not a no-show cure. It is a cheap recovery of the forgetters, worth roughly a tenth of your missed slots back, which at 200 bookings a week is real money and a shorter queue. The practical setup for India: a confirmation the moment the slot is booked, one reminder the day before, and one on the morning of the visit, sent on WhatsApp because that is the channel the patient actually reads. Our [WhatsApp for clinics guide](/in/blog/whatsapp-for-clinics-india/) goes deeper on that channel.

## Walk-in versus booked: the balance that breaks first

Most Indian OPDs run a mix, and the mix is where scheduling software earns or loses its keep.

Pure appointments look clean and break instantly. Indian clinics get walk-ins whether they plan for them or not. The neighbour with a fever does not have a slot. Turn them away and you lose the visit and the goodwill; squeeze them in and your 11am booking slips to noon. Pure walk-in tokens have the opposite failure. Nobody knows when they'll be seen, so everyone arrives at opening and the whole day front-loads.

The version that holds up is a hybrid. Protect a share of the schedule for booked patients and hold that block honestly. Run a walk-in lane alongside with its own numbers. When a walk-in surge hits at 8pm, it eats into the walk-in lane, not the protected block, so the patient who booked at 8:15 is not stuck behind twelve people who walked in at 8. The discipline is the whole trick. A protected slot that staff give away under pressure is not protected.

Scheduling software helps here only if it can express the split. Ask the vendor to show you a day with both booked slots and a walk-in lane on the same screen. If the answer is "well, you'd just book the walk-ins in too," the tool doesn't really model your clinic, and you'll be back to a paper register by the second busy evening.

| Scheduling approach | Best fit | Where it breaks |
|---|---|---|
| **Booked slots only** | Procedure or specialist clinics with almost no walk-ins | The first walk-in surge; a general OPD hits this daily |
| **Walk-in tokens only** | Very high-volume, first-come OPDs | Nobody can plan their day; morning front-loads badly |
| **Hybrid: protected slots + walk-in lane** | Most general Indian OPDs with a real mix | Only if staff hold the protected block under pressure |

_Source: approaches synthesised from Indian OPD practice; fit map, not a ranking._

## Payment at booking, and why it changes behaviour

A booking a patient has paid for is a booking a patient is far more likely to keep. That is the whole logic.

Collecting a booking fee or the full consultation fee at the moment the slot is confirmed, over UPI or a card, does two useful things. It filters out the casual no-show, because a paid slot carries a small cost to skip. And it moves the money before the crowded front desk, so the 8pm queue is about seeing the doctor, not settling the bill. Neither is dramatic on its own. Together they take pressure off the exact moment your clinic is most jammed.

Two things to check before you switch it on. Is the fee refundable on cancellation, and is that rule clear to the patient at booking, so you are not fielding angry calls. And does the payment reconcile against your billing automatically. A booking fee that does not tie back to the invoice creates a month-end cleanup job that quietly eats the time the payment was supposed to save. Ask to see the reconciliation, not just the payment screen.

## Where a standalone scheduler stops, and an integrated platform starts

This is the decision most clinics get wrong by one step in either direction.

A standalone scheduler is the right buy when booking is genuinely your only gap. Your OPD software, your billing, and your records already work, patients just need a cleaner way to book and you need reminders that go out on their own. In that case, do not overbuy. A focused scheduling tool is cheaper, faster to set up, and does the one job well.

But watch for the moment it turns into a liability. When the booking calendar, the OPD queue, the bill, and the clinical note each live in a different system, a standalone scheduler is a fifth screen someone reconciles by hand. The patient who booked online still has to be re-registered in the OPD system, the payment sits in a third place, and the note lives in a fourth. Every handoff is a chance to drop something, and on a 200-booking week you will drop plenty.

That is where an integrated clinic platform pulls ahead. Booking, queue, billing, and the record share one patient file, so a slot booked at 8am is the same visit the doctor opens at 8pm and the same line on the month-end statement. The [India clinic software scorecard](/in/blog/best-clinic-management-software-india/) scores the main integrated options on exactly these lines if you are weighing the jump.

One honest boundary while we're here. If you want the visit linked to a patient's ABHA number at booking, that needs a platform that has cleared the National Health Authority's ABDM milestones in production, not a scheduler with "ABDM ready" on the pricing page. Ask which milestone (M1 for ABHA creation, M2 for record sharing) and whether it is live or sandbox. Patient Square has ABDM integration on its roadmap, not shipped, and we would rather say that plainly than badge something we don't hold.

## Where the booking calendar meets the note

Scheduling gets the patient into the room on time. It does nothing for what happens once they sit down, and that is worth being clear about.

On a two-minute consult (about the Indian average, per Irving and colleagues' 67-country review), the doctor has no spare seconds to type a proper note. So the note gets compressed to a line, or written from memory after the last patient, or skipped. A scheduler that packs the day efficiently actually makes this worse, because a fuller calendar means less breathing room between patients to catch up on charting. And thin records are a real exposure. Under the National Medical Commission's Professional Conduct Regulations 2023, clinics are expected to keep patient records and produce them on request.

Practice Copilot from Patient Square is where that gap gets closed. Its ambient scribe module listens during the visit and hands back a structured note, ICD-10 suggestions, and a prescription draft to review and sign about two minutes after the visit. It does not run your booking calendar, send your reminders, or manage the walk-in lane. It handles the one thing an efficient schedule leaves no time for: writing the note. The scribe captures the code-mixed Hindi and English of a real Indian consult, and the note always comes back in clean clinical English. Visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

My opinion, for what it's worth: most clinics buy scheduling to shorten the wait, then discover the wait was never really about booking. It was about the doctor losing time to work that isn't the consult. Scheduling fixes the front of the day. Documentation fixes the drag inside it.

## Make the call in one pass

Three questions get most clinics to a scheduling decision without a month of demos.

What is actually breaking on your busy evening? If it is patients not finding a way to book, you need clean online and WhatsApp booking. If it is no-shows, you need reminders on the channel patients read. If it is booked patients stuck behind walk-ins, you need the hybrid with a protected block. Different pains, different fixes.

Does the scheduler model your walk-in mix, or just your bookings? Make the vendor show a day with both a booked block and a walk-in lane on one screen. If it can't, it will not survive your real OPD.

Do booking, queue, billing, and notes already talk to each other? If yes, a standalone scheduler slots in cheaply. If no, adding a scheduler adds a screen to reconcile, and an integrated platform is the better long-term call.

Sort those and the choice mostly makes itself. If your booking is fine but the day still runs long because the notes never get written, the missing piece is documentation, not a new calendar. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch one consult turn into a signed note, or read the [pricing](../../pricing/) first. Either way, fix the layer the 8pm queue actually breaks.

---

## AI Medical Scribe for Cardiology: Echo, EKG & Procedure Notes
https://patientsquare.com/us/blog/ai-scribe-for-cardiology/
Published 2026-01-12 · Tags: ai-scribe, cardiology, specialty

How an AI scribe handles cardiology notes: echo and EKG summaries, CHF and AFib follow-ups, stress tests, cardioversion, and device checks.

It captures the interpretation you dictate. Read the echo aloud (EF 40 percent, moderate MR, mild LV hypertrophy) and the scribe drafts a note with those findings in your words. It doesn't read the images or measure anything. The reading is yours; the scribe just structures what you said into the note.

A cardiology scribe works if it captures the language you actually dictate: the echo read, the EKG interpretation, the interval change in a heart-failure patient, the shock energy in a cardioversion. It listens, then drafts a structured note about two minutes after you finish. It doesn't read images or measure anything. The reading stays yours. What it saves is the typing.

> **Key takeaways**
>
> - A 2020 ACC survey (mini-Z) put cardiologist burnout at 35.4%, with insufficient documentation time and EHR-at-home use among the named drivers.
> - The scribe captures what you say. Dictate "EF 40 percent, moderate MR" and the note reflects that. It doesn't interpret the echo or EKG for you.
> - For longitudinal CHF and AFib care, narrate the interval change (weight, NYHA class, rate vs. rhythm). The scribe has no memory of prior visits, so the trend has to be spoken.
> - Procedure notes for cardioversion, stress tests, and device checks come from your narration. Review each draft before signing. Nothing is filed automatically.
> - ICD-10 suggestions like I50.32 or I48.0 appear next to the draft. You confirm them. They're suggestions, not auto-coded charges.

## Why cardiology notes carry more documentation weight than a routine visit

A cardiology note is rarely just an HPI and a plan. A single follow-up can carry an interval history, a focused cardiac exam, an EKG interpretation, an echo or stress read to summarize, a medication titration, and a plan that references what you'll check at the next visit. Each of those is its own chunk of dictation.

Then there's the reading workload that sits outside the visit. A general cardiologist signs echos, nuclear studies, Holters, and event monitors between and after clinic. Every read needs an interpretation documented. That's a lot of structured text produced by one person in a day.

The burnout data reflects it. A 2020 American College of Cardiology survey using the mini-Z instrument found 35.4% of cardiologists reported burnout, and it named insufficient time for documentation and higher electronic-record use at home among the contributing factors. Separately, the AMA's 2023 Organizational Biopsy found 20.9% of physicians spend more than eight hours a week on the EHR outside normal work hours, the after-hours "pajama time" that hasn't budged in years. Cardiology sits squarely inside that pattern because the documentation per patient is heavy by clinical design, not by sloppiness.

An ambient scribe doesn't shrink the clinical work. It shrinks the time between saying the finding and having it written down. If you've read our [primary-care time-back model](../ai-scribe-for-primary-care/), the cardiology version of the math is similar, with more note types stacked on top.

## How an ambient scribe fits a cardiology visit

You start an AI Medical Scribe session when the patient sits down, then run the visit the way you always do. As you take the interval history and examine the patient, you speak your findings the way you'd dictate them: "no orthopnea, dry weight down two pounds, JVP normal, no S3, trace pedal edema." The scribe captures it.

When you pull up the echo from last week and read it, dictate the read aloud. "Ejection fraction 40 percent, moderate mitral regurgitation, mild concentric LV hypertrophy, no pericardial effusion." That's your interpretation. The scribe writes it into the note as you said it. It's not measuring the EF or looking at the images. You did that. The scribe is a stenographer, not a reader.

After the visit you stop the session. About two minutes later there's a draft note: interval history, exam, your echo and EKG summaries, assessment, plan. You read it, fix anything wrong, and sign.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

Worth saying plainly: the note comes back in English, the audio is never stored, and the prescription output is a draft you review, never something the tool sends to a pharmacy on its own. If you want the detail on how consent and PHI handling work, our [HIPAA, BAA, and consent guide](../ai-scribe-hipaa-baa-consent/) walks through it.

## What a cardiology scribe has to capture that a generic one doesn't

This is the test that separates a scribe built to handle your specialty from one that flattens everything into a primary-care template. A generic tool might hear "EF 40, moderate MR" and write "patient has heart problems." That's useless to you. The draft has to come back in cardiology language.

| Documentation element | Generic scribe often produces | What a cardiology-ready draft should show |
|---|---|---|
| Echo read | "Heart function reduced" | "LVEF 40%, moderate MR, mild concentric LVH, no effusion" |
| EKG interpretation | "Abnormal EKG" | "Normal sinus rhythm, rate 72, no acute ST changes, Q waves inferior leads" |
| CHF interval history | "Feeling about the same" | "NYHA class II, dry weight down 2 lb, no orthopnea or PND, diuretic held" |
| AFib status | "Irregular heartbeat noted" | "Paroxysmal AFib, rate-controlled on metoprolol, CHA2DS2-VASc 3, on apixaban" |
| Procedure detail | "Procedure done" | "Elective DCCV, 200J biphasic x1, converted to NSR, propofol sedation" |
| ICD-10 suggestion | Generic or missing | "I50.32, I48.0 suggested for confirmation" |

If the draft reads like the middle column, it wasn't built for you and it'll frustrate you on every note. The right column is the bar. The only way to know which one you're getting is to dictate a real echo read during a trial and look at what comes back.

## Longitudinal CHF and AFib follow-ups: narrate the trend, not just the snapshot

Chronic cardiac care is about the delta between visits. A heart-failure follow-up note that just says "stable" is nearly worthless three months later. What has clinical value is the change: weight trend, symptom class, how the last diuretic adjustment landed, whether the ACE inhibitor got uptitrated.

Here's the thing about ambient scribes and longitudinal care. The scribe has no memory of the last visit. None. It only knows what you say in this room, right now. So the trend has to be spoken. If you say "dry weight is down two pounds from last visit, NYHA improved from III to II after we doubled the torsemide," the note captures that arc. If you just say "doing better," the note says "doing better," and future-you gets nothing.

Same logic for AFib. Say the rhythm status, the rate control, the anticoagulation decision and the score behind it: "paroxysmal AFib, well rate-controlled on metoprolol 50 twice daily, CHA2DS2-VASc of 3, continuing apixaban." The scribe drafts that cleanly. What it can't do is pull the CHA2DS2-VASc forward from a prior note or flag that the score changed when the patient turned 75 last month. That judgment is on you, at the review step.

We think this is actually a hidden upside, not a limitation. Dictating the interval trend out loud, while the patient is in front of you, tends to produce a sharper interval history than reconstructing it from a template at 8pm. You're saying it while you're thinking it.

## Cardiology procedure notes: cardioversion, stress tests, and device checks

Procedure documentation is where the time really stacks in a cardiology practice, and it's the part most likely to get pushed to after hours. The narration approach fits it well: describe the procedure as you do it or right after, while it's fresh.

Take an elective cardioversion. You'd narrate the pre-procedure rhythm, the sedation, the energy and number of shocks, and the result. The scribe drafts a procedure note from that spoken record. Same pattern for a treadmill stress test (protocol, METs achieved, symptoms, EKG response, reason for stopping) or a device interrogation (battery status, lead impedances, any arrhythmia episodes, programming changes you made).

| Procedure | What to dictate aloud |
|---|---|
| Elective cardioversion | "Pre-procedure AFib, propofol sedation, 200J biphasic shock x1, converted to normal sinus rhythm, tolerated well" |
| Exercise stress test | "Bruce protocol, 9 minutes, 10 METs, target heart rate achieved, no chest pain, no ischemic ST changes, stopped for fatigue" |
| Pacemaker/ICD check | "Dual-chamber ICD interrogated, battery ERI not reached, atrial and ventricular leads stable, one non-sustained VT episode, no therapy delivered" |
| Right heart cath | "Access right IJ, PA pressure 45/20, wedge 18, cardiac output 4.2 by thermodilution, no complications" |

The scribe structures what you said into a note. It does not know the shock was 200 joules unless you say 200 joules. Precision in the room produces precision in the draft. You review the whole thing before it goes anywhere, and nothing is submitted or coded on its own.

## What the scribe suggests for coding, and what it doesn't do

Cardiology coding is detailed. Heart failure alone splits across systolic, diastolic, combined, acute, chronic, and acute-on-chronic. The scribe reads your dictated assessment and suggests ICD-10 codes to match: I50.32 for chronic diastolic heart failure, I48.0 for paroxysmal AFib, I25.10 for atherosclerotic heart disease of native coronary artery without angina.

Those are suggestions. They show up next to the draft note. You confirm the ones that fit, change the ones that don't, and drop the rest. The scribe has no line into your billing system and posts no charges. A code sitting in the draft is a prompt for your judgment, not a claim. For a deeper look at how the suggestions get generated and where they go wrong, see our [ICD-10 suggestions explainer](../ai-scribe-icd-10-suggestions-explained/).

One caution specific to cardiology: the specificity that drives correct coding also drives claim denials when it's missing. If your dictated assessment says "heart failure" without the systolic/diastolic and acute/chronic detail, the suggestion will be vague too, because the scribe only has what you gave it. Dictate the full diagnosis and the suggestion gets more useful. Garbage in, vague code out.

## The daily math for a cardiology clinic

Picture a Thursday. Twenty-two patients on the schedule, a mix of new consults and follow-ups, and a stack of echos and two nuclear studies waiting to be read and signed between rooms. By 4pm you're behind on notes, and you already know two hours of charting is coming home with you. That's the day a scribe is aiming at.

The honest version of the value isn't a dramatic hour-count. It's a few minutes shaved off each note, multiplied across a full panel, plus the bigger shift in when the notes finish.

| Scenario | Notes per day | Rough time without scribe | With scribe | Daily difference |
|---|---|---|---|---|
| Follow-up-heavy clinic, 22 visits | 22 | ~110 min | ~80 min | ~30 min |
| Consult-heavy day, 15 visits + longer notes | 15 | ~100 min | ~72 min | ~28 min |
| Mixed clinic + 8 echo reads to document | 20 + 8 | ~120 min | ~88 min | ~32 min |

These are estimates, not a trial result. Your real number depends on how long your notes run, how much you correct the drafts, and how fast you read and sign. The published evidence points the same direction: a 2025 JAMA Network Open study of 263 ambulatory clinicians across six health systems found burnout dropped from 51.9% to 38.8% after 30 days on an ambient scribe, with measured improvement in after-hours documentation time. That's a burnout signal, not a stopwatch, and it lines up with what the arithmetic suggests. Our [ROI calculator guide](../ai-scribe-roi-calculator-guide/) has the framework if you want to run your own figures.

## Where a cardiology scribe stops, and where it isn't the right tool

Being straight about the limits matters more than a feature list. The scribe drafts what you dictate. It doesn't read your echos, calculate an EF, interpret the EKG, or catch that your dictated exam and your assessment contradict each other. If you call the rhythm sinus and then dictate an AFib plan, the scribe won't flag the mismatch. That's your review.

It also doesn't integrate with anything. Not your EHR, not the echo lab's reporting software, not the device clinic's database. You get a draft, you review it, and you copy or export it into wherever you chart. If your practice's real bottleneck is structured data flowing between your echo system and your EHR, an ambient scribe is the wrong purchase. That's an interoperability problem, and a scribe doesn't touch it.

And if what you actually want is fully automated structured reporting from the imaging itself, pulled straight off the echo machine into a coded report with no dictation, an ambient scribe isn't that either. It captures spoken clinical work. If you never want to say the read out loud, this tool isn't for you.

For the cases where it does fit, the review step is the whole game, especially in the first couple of weeks. You'll find the terms it mishears, the structure it doesn't lay out the way you like, and you'll adjust how you dictate. That settling-in takes a week or two, then it stabilizes.

## How to evaluate a scribe against your own cardiology notes

A single demo note tells you almost nothing about how a scribe handles a real cardiology day. Run it on your own clinic instead. Three tests are worth doing during the trial.

First, dictate a full echo and EKG read and check whether the draft comes back in your language or flattens it. Second, narrate one procedure, a cardioversion or a device check, and see whether the structured note covers rhythm, energy or findings, sedation, and result. Third, run it on your heaviest half-day, back-to-back rooms with reads piling up, and see whether notes stay clean and separate instead of bleeding into each other.

The 7-day trial exists for exactly this. Run it on a real clinic day, on your own patients and your own accents, and read every draft closely for the first week. That's your accuracy figure, and it's the only one worth trusting. For a broader specialty comparison, our [dermatology scribe breakdown](../ai-scribe-for-dermatology/) shows how the same evaluation applies when the vocabulary changes, and [what an AI medical scribe actually is](../what-is-an-ai-medical-scribe/) covers the fundamentals if you're new to the category.

If you want to see the draft quality against your own echo reads and procedure vocabulary before committing anything, <a href="/us/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and bring a typical complex case. That's the right test for cardiology, and it's the one we'd run in your shoes.

---

## Physiotherapy Clinic Software in India: A Buyer's Guide (2026)
https://patientsquare.com/in/blog/physiotherapy-clinic-software-india/
Published 2026-01-12 · Tags: physiotherapy-software, india, clinic-software

How to pick physiotherapy clinic software in India: recurring session scheduling, ROM/MMT assessment notes, session-pack billing with GST, and exercise-plan sharing.

Recurring-session scheduling, physio-shaped assessment notes with range-of-motion and manual muscle testing fields, session-pack or package billing rather than per-visit invoicing, and exercise-plan sharing to the patient. Generic clinic software handles one-off appointments and single-line bills, which fits a GP but not a rehab caseload.

Physiotherapy clinic software is a clinic system built around rehab work rather than one-off doctor visits: recurring-session scheduling, assessment notes with range-of-motion and muscle-grade fields, session-pack billing with GST, and exercise plans you can send to the patient's phone. If you run a physio practice in India, that shape matters more than the feature count on a sales page.

> **Key takeaways**
>
> - Physio needs four things generic clinic software skips: recurring appointments, ROM/MMT-shaped notes, session-pack billing, and exercise-plan sharing.
> - Software subscriptions in India carry 18% GST on top of the listed price (HSN 997331).
> - Public pricing for cloud clinic tools runs roughly ₹1,000 to ₹2,900 or more per user per month before tax, so a 3-therapist clinic budgets a few thousand rupees monthly.
> - Physiotherapy is now a recognised healthcare profession under the NCAHP Act, 2021.
> - Range of motion is charted in degrees; manual muscle testing uses the 0 to 5 grade scale. Structured fields let you show progress across a course.

Picture a lead physio in a Bengaluru clinic on a Tuesday evening. Six back-to-back sessions since 4 pm. A frozen shoulder on visit four of twelve, a post-ACL knee tracking week six, a lower-back case who's paid for a ten-session pack and is on session three. A GP sees each patient once and moves on. A physio sees the same knee twenty times and has to prove it got better.

That's the whole difference. Generic clinic software assumes a visit is an event. Physio work is a course. So the scheduling, the notes, and the billing all bend differently.

## Why does physiotherapy need different software from a GP clinic?

Take scheduling. A GP books a slot. You book a series: three sessions a week for a month, same time, same therapist. Software that can't clone a recurring block makes you rebook the same patient by hand a dozen times. Small friction, but multiply it across a full caseload and it eats an hour a week.

Then the note. A GP note is a diagnosis and a prescription. Your note is a measurement you'll repeat. Range of motion in degrees. Active versus passive. Manual muscle testing on the 0 to 5 grade. Pain on a scale, gait observations, the treatment plan for the week. If the software stores those as loose free text, you can't chart the trend, and the trend is the point of the whole thing.

## What features should physiotherapy clinic software actually have?

Here's the split I'd hold vendors to. Left column is what most clinic software already does. Right column is where physio pulls away.

| Capability | Generic clinic software | What a physio clinic needs on top |
|---|---|---|
| Appointments | Single, one-off slots | Recurring series, same therapist, repeatable across weeks |
| Clinical notes | Diagnosis + prescription, mostly free text | Structured ROM (degrees), MMT (0 to 5), pain scale, assessment + treatment plan, session-over-session charting |
| Billing | Per-visit invoice | Session packs and packages with a running balance, GST on each invoice |
| Patient handoff | Prescription printout | Exercise plan with sets, reps, and images sent to the patient |
| Staff | One or two prescribers | Multiple therapists, per-therapist calendars, session ownership |
| Progress | Not really tracked | Outcome tracking across a treatment course |

If a tool nails the left column and fakes the right, you'll feel it in month two, when you're back to a WhatsApp thread and a paper register for the things the software couldn't hold.

Two more that quietly matter. Multi-therapist support, because most clinics that survive grow past one physio, and you need per-therapist calendars plus a way to see who owns which session. And exercise-plan sharing, because home compliance is half the outcome. A plan the patient can actually pull up on their phone beats a photocopied sheet that lives in a drawer.

## How much does physiotherapy clinic software cost in India?

Real numbers, with the tax stated plainly, because the tax is where budgets get surprised.

Software subscriptions in India are a service under HSN 997331 and attract 18% GST (per ClearTax and the HSN 997331 classification). That's on top of whatever the vendor lists. So a plan advertised at ₹2,875 a month is really ₹2,875 plus 18% GST, which is ₹3,392.50 before you've onboarded a single patient. Budget the with-tax figure, not the sticker.

For a sense of the range: Cliniify's public pricing lists a Plus plan at ₹1,042 per month and a Pro plan at ₹2,875 per month. Practo's clinic product, Ray, publishes tiered plans on its site; third-party software listings peg cloud clinic tools broadly in the ₹1,000 to ₹6,000 per user per month band before tax, which is the honest way to read it since headline prices shift with promotions and add-ons. Confirm the live number and the tax line with the vendor before you commit.

Do the arithmetic for your own clinic. Three therapists on a mid-tier plan, per-user pricing, plus GST, and you're looking at a few thousand rupees a month. Set that against one recovered session-pack you'd otherwise have lost track of, and the maths usually works. Honestly, most physio clinics overbuy: they pay for telemedicine and lab modules they never switch on. Buy for the caseload you have.

## Can you bill physiotherapy session packages properly?

This is the feature I'd test first in any demo. Ask them to sell a ten-session pack to a dummy patient, mark four sessions attended, and show you the balance and the GST-correct invoice. If it fumbles, walk.

Session-pack billing is the physio-native money model. A patient buys a block upfront, attends over weeks, and the system decrements the balance each visit. Generic clinic billing invoices one visit at a time, so you end up tracking "how many sessions left" in your head or on a sticky note. That's where revenue leaks: the forgotten free session, the pack that expired, the refund nobody logged.

A simple worked example, GST included so you can see the shape:

| Line | Amount |
|---|---|
| 10-session physiotherapy package (ex-GST) | ₹8,000 |
| GST at 18% | ₹1,440 |
| Total invoiced to patient | ₹9,440 |
| Per-session value tracked by the system | ₹800 |
| After 4 sessions attended | 6 remaining, ₹4,800 balance |

The numbers above are illustrative, not a quoted price. The point is that the software should carry this ledger for you, not leave it to memory. When you're closing the clinic at 8 pm, memory is not a billing system.

## Is physiotherapy regulated in India, and does software need to care?

Yes, and a little. Physiotherapy is recognised as a healthcare profession under the National Commission for Allied and Healthcare Professions Act, 2021, which created the NCAHP to regulate education, registration, and professional ethics for allied and healthcare professions. Before it, physiotherapists sat in a statutory gap with no central body. The Act doesn't dictate what software you run, so don't let a vendor sell you "NCAHP-compliant software" as if that's a certification. It isn't.

What it does mean practically: keep clean, dated, attributable records. Structured assessment notes and a clear audit trail of who saw whom and when are just good practice, and they're easier to defend if a record is ever questioned. Software helps here by default, not because a regulation mandates a specific product.

## Where does an AI scribe fit into physio documentation?

Somewhere useful, but narrow. After a run of six sessions, the last thing a physio wants is forty minutes of typing. An ambient AI scribe listens during the visit and drafts the note for you, which is real time back on documentation-heavy days.

The AI Medical Scribe by Patient Square, one module of the Practice Copilot platform, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

Be clear-eyed about what that is and isn't. It's a documentation layer. It drafts the note; you review and sign it. It won't run your appointment book, hold your session-pack balances, or build the exercise plan. The ICD-10 output is a suggestion and the prescription is a draft, both for you to check. Notes come out in English. So think of a scribe as the thing sitting on top of your clinic software to kill the typing, not the clinic software itself. If your bottleneck is notes, it helps. If your bottleneck is scheduling and packs, buy a physio practice system first.

You can see how a scribe slots alongside a records system in our [EMR software India guide](../emr-software-india-guide/).

## Which tools are worth a look, and when is each the right fit?

A short, honest map. None of this is vendor marketing; treat every claim below as "verify in the demo."

- **Physio-specific tools** (the ones built around rehab, exercise libraries, and outcome tracking): the right fit when physio is your whole business and you want ROM/MMT notes and exercise plans out of the box, without bolting them onto a general system.
- **Cliniify** and similar mid-market clinic platforms: a fair fit for a multi-specialty setup where physio is one of several services, and you want appointments, records, and billing in one place. Pricing is public, which I respect.
- **Practo Ray**: worth a look if you already lean on the Practo network for discovery and bookings and want the clinic tools in the same ecosystem. Better fit for GP-style clinics than for pure rehab, in my read.
- **A spreadsheet and a calendar**: genuinely fine for a solo physio under a few dozen active patients. Don't pay for software to solve a problem you don't have yet. Skip it until the manual tracking starts costing you.

For the broader shortlist across specialties, our [best clinic management software India](../best-clinic-management-software-india/) roundup and the [OPD software for clinic India](../opd-software-for-clinic-india/) guide cover general-purpose options. If your clinic mixes physio with dental, the [dental clinic software India](../dental-clinic-software-india/) breakdown is worth a read too, since the multi-specialty billing question shows up there as well.

## How should a physio clinic choose, in practice?

Run the demo against your own Tuesday evening, not the vendor's happy path. Book a recurring series. Write one ROM and MMT note and reopen it next "session" to check you can chart the change. Sell a session pack, attend a few, and read the GST invoice. Send an exercise plan to a test phone. If all four feel natural, the tool fits physio. If any one is a workaround, you'll be living that workaround daily.

Want to see how documentation could work in your clinic? You can book a demo of AI Medical Scribe by Patient Square and try it on a real visit. Start with the one job that's eating your evenings, then decide.

If scheduling and queues are your bigger pain than notes, the [clinic queue management India](../clinic-queue-management-india/) guide is the better next read before you buy anything.

---

## AI Medical Scribe for Telehealth Visits: The Room You're Not In
https://patientsquare.com/us/blog/ai-scribe-for-telehealth/
Published 2026-01-09 · Updated 2026-07-22 · Tags: ai-scribe, telehealth, ambient-documentation

What an ambient scribe captures on a video visit, the objective-exam gap it can't fill, and why it never plugs into your telehealth platform.

No. AI Medical Scribe by Patient Square listens to the spoken conversation of the visit, whether that visit happens in a room or over video, and drafts a note from what's said. It does not plug into Zoom, Doxy, or your video software, does not record video, and does not pull anything from the call. It hears speech and writes a note.

An ambient AI scribe on a telehealth visit captures the conversation, not the call. It listens to what you and the patient say over video, then drafts a structured note. It does not plug into your video platform, record the screen, or examine the patient. The words become a note; the objective exam stays yours.

That's the honest version, and it's the version most product pages skip. A video visit is missing the thing an in-person visit gives you for free: your hands, your stethoscope, the smell of the room. The scribe can't recover any of that. What it can do is take the talking part of the visit off your keyboard so the thin objective section is the only thing you're writing by hand.

> **Key takeaways**
>
> 1. The scribe listens to the spoken visit and drafts a note. It does not integrate with Zoom, Doxy, or any video platform, and it never records video.
> 2. It captures the conversation: HPI, review of systems, your spoken assessment and plan. It cannot see, palpate, or auscultate, so the objective section is still yours to write.
> 3. CMS names any visit where a physical exam would change your recommendation as less appropriate for telehealth. The scribe doesn't change that math; it just handles the documentation.
> 4. Primary-care physicians log a median of about 36 minutes of EHR time per 30-minute visit (JAMA Network Open). The talking part of a video visit is exactly the part a scribe removes from your evening.

If a video visit is where a lot of your week now happens, read on. What follows is exactly what the scribe hears, what it can't, and where the line sits between the note it drafts and the record you sign.

## How does an AI scribe work on a telehealth visit?

The same way it works in a room. You start a session on your phone or laptop before the visit, get the patient's consent, and talk. The scribe captures the spoken conversation ambiently and drafts a note from it. There's no screen recording, no video capture, no hook into your telehealth software.

That last point matters, so let's be blunt about it. The scribe is not a telehealth feature. It doesn't join your Zoom room or read your Doxy session. It listens to audio the way a person sitting quietly beside you would, and on a video visit that audio is just your side of the call plus whatever the patient's mic sends back. If your platform pipes the patient's voice through your device speakers or headset, the scribe hears both halves of the conversation. If it doesn't, it hears you. Either way, it's listening to speech, not tapping the call.

AI Medical Scribe is one module inside Practice Copilot, the platform Patient Square builds. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. On a telehealth day that draft lands the same as it would after an in-person visit: subjective, objective, assessment, plan, with the objective section reflecting only what you said out loud.

Want the roll-out mechanics for a small practice going hybrid? Our [2-week implementation plan](../ai-scribe-implementation-small-clinic/) walks through it.

## What can a scribe capture on a video visit, and what can't it?

Here's the split, because it's the whole point of this page. A telehealth visit has a full conversation and a hollow exam. The scribe is excellent at the first and useless at the second, and pretending otherwise is how documentation goes wrong.

| The visit part | Who captures it on a video visit | In the note |
|---|---|---|
| Chief complaint, HPI | The scribe, from the conversation | Subjective, drafted |
| Review of systems (what the patient reports) | The scribe, from the patient's answers | Subjective, drafted |
| What you observe on camera and say out loud | The scribe, from your spoken words | Objective, only if you narrate it |
| Palpation, auscultation, anything you touch | Nobody. You can't do it over video | Objective — absent unless done in person |
| Vitals the patient reads from a home device | The scribe, if the patient or you say the numbers | Objective, drafted from speech |
| Your assessment and plan | The scribe, from your spoken reasoning | Assessment + Plan, drafted |
| ICD-10 suggestions, prescription draft | The scribe, from the above | Handed to you as drafts to confirm |

Read the fourth row twice. The objective section of a physical exam is the part telehealth already struggles with, and no scribe fixes that. A 2021 review in The Journal for Nurse Practitioners put it plainly: face-to-face encounters are necessary where auscultation or palpation is needed, and telehealth is best used to supplement in-person care, not replace it. An AHRQ patient-safety commentary the same year was blunter still, noting that the value of smell and touch in the exam is simply lost on a video visit, and that certain parts of the physical exam cannot be performed online at all.

So the scribe captures a rich subjective and a spoken assessment, and it leaves you a lean objective section to fill. If you did a "look at the camera and show me the rash" exam, narrate what you saw and the scribe writes it down. If you couldn't examine at all, that gap is real, and it belongs in your clinical judgment, not the tool's.

If you also see patients in the clinic, the same scribe covers both; here's the [20-patient-day math for primary care](../ai-scribe-for-primary-care/) when the visits are in person.

## Why doesn't the scribe just plug into my telehealth platform?

Because it's built to listen, not to integrate, and that's a deliberate line. Integrations into video platforms, EHRs, and scheduling systems are a different product surface with a different risk profile. What ships today is an ambient listener that turns spoken visits into drafted notes, in a room or over video, without touching your other software.

There's an upside to that limit that's easy to miss. Because the scribe isn't wired into your telehealth stack, it doesn't care which platform you use. Switch from one video vendor to another and nothing about your documentation changes; you're still starting a session and talking. The scribe's job starts and ends with the conversation.

And the audio doesn't stick around. Visit audio is processed in memory and discarded the moment the note is drafted. There's no audio archive, not of your video visits, not of anything, for us or for your practice. Notes are encrypted in transit (TLS 1.2+) and at rest (AES-256), they belong to your practice, and you can export or delete any visit whenever you want. The full posture, including what we sign and what we don't, is on our [security page](../../security/).

## Does telehealth documentation have rules a scribe should know about?

Yes, and the scribe drafts toward them without deciding them for you. CMS is clear that telehealth documentation follows the same discipline as any visit: complete the documentation at the time of service, record the time you spent, and code the place of service correctly. For Medicare real-time video, that includes the CPT modifier 95. Those are billing and compliance calls the clinician owns; the scribe just gives you a clean, structured draft to make them from.

CMS also draws a line the scribe can't draw for you. Its provider toolkit lists, among the situations telehealth is less appropriate for, "any situation in which a physical exam would change your recommendation." That's a triage decision, not a documentation one. The scribe will faithfully write up a video visit you probably should have brought into the clinic; it won't tell you that you should have. Reading the draft is where you catch it.

The safer way to think about it: the scribe lowers the cost of documenting a telehealth visit to almost nothing, which frees your attention for the judgment calls that actually carry risk. What to examine in person, when to escalate, what your thin objective section is missing. Those stay with you.

## Where does an AI scribe fall short on telehealth visits?

Three places, and they're worth naming before you trust the note.

The objective exam is the big one, and we've said it, but it bears repeating because it's where harm hides. There's a real AHRQ-reviewed case: a frail, non-ambulatory patient mentioned skin breakdown on her "backside" during a video visit, the clinician didn't visualize the area, and a perirectal necrotizing infection went undetected until she returned in septic shock and died after surgery. The video visit wasn't wrong to happen; the missed exam was the failure. A scribe would have captured every word of that conversation and still not seen the wound. The tool documents; it does not examine.

Audio quality is the second. Telehealth audio is messier than a quiet room. Dropped packets, a patient on speakerphone in a noisy kitchen, a relative talking over the line, a connection that cuts out mid-sentence. When the audio degrades, so does the transcript, and the scribe can only write what it heard cleanly. Read the draft closely on your worst-connection visits.

Third, drafts contain errors, on video as much as in person. Models mishear drug names, compress two complaints into one, occasionally write a plausible line that wasn't said. That's why the review-and-sign step is load-bearing. The prescription draft reflects what was said in the visit; it does not screen for interactions or dosing, so you read it against the chart, adjust the dose, and sign, exactly as you do today. A draft an LLM wrote is still a draft an LLM wrote. You're the author of the record, and the safety check, in every setting.

When your connectivity is unreliable, capture also works offline with on-device AES-256-GCM encryption and syncs the note later, so a dropped internet connection doesn't cost you the documentation.

## What should a telehealth-first clinician ask before signing up?

Five questions, tuned for virtual practice.

1. "Does this actually integrate with my video platform, or does it just listen?" The honest answer for us is: it listens. Be suspicious of any vendor selling "telehealth capture" as a deep integration, and ask exactly what it touches.
2. "What happens to the visit audio, and when is it deleted?" One sentence, with a timeline. Ours: processed in memory, discarded at note draft, no archive.
3. "How does the objective section get built on a video visit?" The right answer is: from what you narrate. Anyone implying the tool examines the patient is overselling.
4. "Will you sign a BAA?" A vague answer is disqualifying, and so is anyone claiming to be "HIPAA certified," because no such certificate exists. We maintain HIPAA compliant safeguards and offer a BAA to every US customer.
5. "What's the price, in full, after year one?" Get the whole ladder in writing. Ours is published, [from $79/mo](../../pricing/) on the annual Assist plan, same scribe for in-person and virtual, no telehealth surcharge.

A scribe that answers those five cleanly will hold up across a hybrid week. Consent handling shifts a little between settings and states, so it's worth reading our notes on [patient consent by state](../ai-scribe-patient-consent-by-state/) and [BAAs and consent](../ai-scribe-hipaa-baa-consent/) before you roll out.

## The honest bottom line for telehealth

An ambient scribe is a good fit for the talking-heavy visits telehealth does well: medication management, chronic-disease follow-up, counseling, results review. Those are conversation, and conversation is exactly what it captures. Where you truly need hands on the patient, telehealth is the wrong setting and a scribe won't rescue it; that's a triage call, not a software one.

The value is narrow and real. On a video visit, the scribe takes the conversation off your keyboard and leaves you one thing to write by hand: the objective section only you can judge. That's less typing, faster sign-off, and more attention on the patient's face instead of your charting. Book a demo to see the draft against your own visit types, then run the 7-day trial on a real telehealth week and read every note closely. That's the evaluation that counts.

---

## Pharmacy Management Software in India: Buyer Guide
https://patientsquare.com/in/blog/pharmacy-management-software-india/
Published 2026-01-09 · Updated 2026-08-27 · Tags: pharmacy-management-software, india, clinic-software

Batch and expiry tracking, GST billing, the Schedule H1 register, drug licence rules, and honest prices. What pharmacy software your clinic actually needs in 2026.

It's the billing and stock system a chemist or in-house hospital pharmacy runs to sell medicines. Core jobs: batch and expiry-wise inventory, GST invoices, purchase and supplier records, the Schedule H1 register, and reorder alerts. It is a separate tool from your OPD or EMR software.

Pharmacy management software is the billing and stock system your clinic or hospital pharmacy uses to sell medicines: batch and expiry-wise inventory, GST invoices, purchase and supplier records, the Schedule H1 register, and reorder alerts. Good software makes the counter faster and keeps you inspection-ready. It is a different tool category from your OPD, EMR, or hospital management system.

> **Key takeaways**
>
> - Under the Drugs and Cosmetics Rules 1945, a Schedule H1 sale needs a separate register kept for three years, open to inspection.
> - Most prescription medicines now attract a uniform 5% GST after the September 2025 reform; some OTC items sit at 18%.
> - A Form 20 or 21 retail drug licence requires a registered pharmacist present during all business hours.
> - Entry pricing starts near ₹8,100 plus 18% GST (single-user Marg ERP); the market spans roughly ₹5,000 to ₹25,000.

Picture a two-doctor clinic pharmacy in Pune at 8pm. The last patient's gone. The pharmacist is holding a strip of amoxicillin, squinting at the batch number, cross-checking a paper register because a drug inspector visited a shop down the road last week. That scene is the whole job. Software either makes it a two-second scan or it doesn't. Everything below is about telling those two apart.

## What does pharmacy software actually have to do?

Strip away the demos and the feature checklists. A working system in India has to nail five things.

Batch and expiry tracking comes first. Every strip of medicine has a batch number and an expiry date, and you cannot legally sell an expired one. The software should pick the right batch at billing (usually first-expiry-first-out), warn you 60 or 90 days before a batch expires, and let you pull an expiry report so you can return near-dated stock to the distributor. Miss this and you're eating write-offs.

Then GST billing. After the September 2025 reform, most medicines moved to a single 5% slab, with certain life-saving drugs nil-rated and some OTC and wellness products at 18% (per the 56th GST Council changes). Your software needs correct HSN codes per product and a GST-compliant invoice format. If you do B2B supply, e-invoicing and e-way bills matter too.

The Schedule H1 register is third, and it's the one people forget until an inspector asks. More on that below.

Fourth: purchase and supplier management. Goods-inward entry against the distributor's invoice, purchase returns, ledger per supplier, and a way to reconcile what you paid against what you received. Barcode scanning speeds the counter up but it's optional for a small shop.

Fifth: reorder logic. Minimum stock levels, fast and slow movers, a reorder list you can hand to your distributor. A shop carrying 3,000 to 5,000 SKUs cannot eyeball this.

## The Schedule H1 register: the compliance point everyone underestimates

Here's the rule, and it's not vague. If you sell a Schedule H1 drug (many third and fourth-generation antibiotics, some psychotropics, anti-TB medicines), the Drugs and Cosmetics Rules 1945 require you to record the sale in a separate register at the time of supply. The register captures the prescriber's name and address, the patient's name, the drug, and the quantity. You keep it for three years and it must be open to inspection, per the PIB press note on Schedule H1 sales.

Schedule H drugs are prescription-only with the time and date noted. Schedule X is stricter still: prescription in duplicate, one copy retained by the licensee for two years, under the Rules 1945. Get these wrong and you're not looking at a warning. Schedule H1 non-compliance carries real penalties under the Drugs and Cosmetics Act.

Why does this decide your software choice? Because a paper H1 register is a nightmare to keep accurate across a busy counter, and a good pharmacy system generates it from the sale itself. You bill the drug, the register row writes automatically. When the inspector walks in, you print three years of it. That single feature is worth more than half the flashy dashboard features a vendor will show you.

## Must-have vs nice-to-have for a small clinic pharmacy

Not every shop needs every feature. Here's how I'd split it for a clinic or small hospital pharmacy, versus a distributor or a 100-bed setup.

| Feature | Small clinic pharmacy | Larger hospital pharmacy | Why it matters |
|---|---|---|---|
| Batch + expiry-wise stock | Must-have | Must-have | Legal + prevents dead stock |
| GST invoice with correct HSN | Must-have | Must-have | Correct tax slab post-Sept 2025 |
| Schedule H1 register auto-generation | Must-have | Must-have | Rules 1945; 3-year retention |
| Purchase / supplier ledger | Must-have | Must-have | Reconcile inward stock + payments |
| Reorder + min-stock alerts | Must-have | Must-have | 3,000+ SKUs can't be eyeballed |
| Barcode scanning | Nice-to-have | Must-have | Speed at high volume |
| e-invoicing / e-way bill | If you do B2B | Must-have | B2B supply compliance |
| OPD / HMS integration | Nice-to-have | Often needed | Rx-to-till flow (rarely native) |
| Cloud / multi-branch | Nice-to-have | Must-have | Central stock view across sites |
| Loyalty / SMS refill reminders | Nice-to-have | Nice-to-have | Retention, not compliance |

If you're a single-counter clinic pharmacy, the whole left column is your buying spec. Don't pay for the rest yet.

## What does it cost in India?

Real numbers, because vendors love to hide these. Prices below are ex-GST unless stated. Medicines carry their own GST; the software itself is taxed at 18%.

Marg ERP 9+ Pharmacy (Basic, single-user) is listed from ₹8,100 plus 18% GST, so about ₹9,558 all-in, as a one-time desktop licence per SoftwareSuggest. Marg is the desktop workhorse a lot of Indian chemists already run.

On the subscription side, Medicin lists a basic single-user plan around ₹9,000 per year and GoFrugal's pharmacy product shows up in listings near ₹15,000, per Techjockey. Third-party marketplaces put the broad range at ₹5,000 to ₹25,000 depending on features, users, and cloud versus desktop.

A few pricing traps. One-time desktop licences look cheaper until you add annual maintenance and support. Cloud plans include updates but bill forever. "Per user" can double your cost the moment you add a second billing counter. And setup or data-migration charges are often quoted separately, so ask.

For a solo clinic pharmacy, budget ₹8,000 to ₹15,000 for year one and stop reading the enterprise tier brochures.

## Where does Patient Square fit? (Honest answer: not here, mostly)

Let's be clear about what we are, because it's a different category. Patient Square is an AI clinical platform: Practice Copilot brings the practice under one AI copilot, with the AI Medical Scribe by Patient Square as one module that captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit, plus Patient Square EHR from the Copilot tier or an alongside path for an existing EHR, with scheduling and messaging as you move up the plan.

That prescription draft is where a scribe touches the pharmacy world, and even then only at the edge. We help the doctor produce a clean, reviewed prescription faster. We do not do pharmacy inventory, batch and expiry tracking, GST billing, or the Schedule H1 register. Those are jobs for Marg, GoFrugal, Vyapar, or a hospital HMS pharmacy module, not for a documentation tool. If a vendor tells you one product does ambient scribing and full pharmacy inventory well, be skeptical. They're usually strong at one and thin at the other.

If you want to understand the documentation side, our guide to [prescription software for doctors in India](../prescription-software-for-doctors-india/) covers the doctor-facing half, and the [e-prescription legal guide](../e-prescription-software-india-legal/) covers what a valid digital prescription needs.

## Which pharmacy tools do Indian buyers actually shortlist?

Names you'll run into, described plainly, no marketing claims taken at face value.

**Marg ERP** is the desktop veteran. Deep pharmacy and distribution features, huge installed base, works well offline. The interface feels dated and it's Windows-first. Best fit when you want a proven billing engine and don't care about a pretty screen.

**GoFrugal** leans retail POS with a pharmacy-specific product and cloud options. Stronger if you run multiple counters or want mobile access. Best fit for a growing chain rather than a single clinic counter.

**Vyapar** is billing and accounting software popular with small Indian businesses, including chemists, with a free mobile tier. It's lighter on pharmacy-specific compliance like the H1 register. Best fit when your needs are mostly GST billing and basic stock, not deep drug-register work.

**HealthPlix and Practo Ray** are clinic and EMR platforms that sometimes bundle a pharmacy or prescription layer. Handy if you want one login for OPD and dispensing, but the pharmacy depth rarely matches a dedicated tool. Best fit when the OPD software is the priority and pharmacy is secondary.

Here's the honest verdict. If you're a standalone chemist or a small clinic counter that lives and dies on drug-register compliance and expiry control, buy a dedicated pharmacy tool like Marg. If you're a hospital already running an HMS, use its pharmacy module before adding a fifth system nobody wants to reconcile. And if your real problem is that your OPD paperwork is slow, that's an EMR or scribe problem, not a pharmacy-software problem, and it's worth reading our [best clinic management software in India](../best-clinic-management-software-india/) and [EMR software India guide](../emr-software-india-guide/) before you spend.

## How do you evaluate a vendor in one demo?

You get maybe an hour. Spend it on these, not the dashboard.

Ask them to sell a Schedule H1 drug on screen and show you the register row it generates. If they fumble, walk. Ask to see an expiry report and a batch return to a distributor. Ask how the GST slab is set per product and whether it survived the September 2025 rate change. Ask, flatly, whether a prescription from your OPD software can flow into the till, and get the integration path in writing rather than a "yes, we can do that." Ask what happens to your data if you leave, and whether export is free.

One clinic manager I spoke to bought on the strength of a loyalty-SMS feature and discovered three months later the H1 register export was broken. The boring features are the ones that get you through an inspection. Buy for the boring ones.

For the OPD side that feeds your pharmacy, the [OPD software for clinics in India](../opd-software-for-clinic-india/) guide is a better starting point than any pharmacy vendor's brochure.

Want to see how the documentation half of the workflow speeds up the doctor before the prescription ever reaches your counter? Book a demo and watch a real visit get scribed. No pharmacy-suite promises from us, just the note and the Rx draft, done in about two minutes.

---

## Queue Management for Indian Clinics: What Actually Works
https://patientsquare.com/in/blog/clinic-queue-management-india/
Published 2026-01-08 · Updated 2026-09-29 · Tags: queue-management, opd, token-system, india

A vendor-neutral guide to OPD queue management for Indian clinics: token systems, display boards, appointments versus walk-ins, and what actually cuts the wait.

A clinic queue management system decides who the doctor sees next and keeps patients informed while they wait. In an Indian OPD that usually means a token, a way to call the next number, and a display so nobody hovers at the door. It can be a manual register, a token app, or a full appointment-plus-walk-in scheduler. The goal is the same: order the queue and cut the felt wait.

Queue management is how a clinic decides who the doctor sees next and keeps everyone else calm while they wait. For an Indian OPD that means a token, a way to call the next number, and a board or announcement so patients are not crowding the consult-room door. The honest headline: a token or a display board tidies the wait, but it rarely shortens it. What shortens the wait is throughput and less variation. This guide walks the difference.

> **Key takeaways**
>
> - A token or display board mostly fixes the *felt* wait and the crowding, not the true wait. The true wait is set by how many patients one doctor clears per hour.
> - Across 30 Nellore-district hospitals, mean OPD waits ran 15.5 minutes (private) to 39.71 minutes (voluntary), per a 2018 IJCMPH study. Seating did not change that; throughput did.
> - The projects that cut Indian OPD waits by a lot redesigned the whole flow. One Lean Six Sigma project took the mean from 57 to 24.5 minutes (Gijo and Antony, 2014).
> - Most clinics need a hybrid of protected appointment slots and a walk-in token lane, not one or the other.
> - Registration is rarely the bottleneck. In one tertiary-hospital study only about 1 in 20 patients waited over 30 minutes to register, while 49% waited over 30 minutes to be seen.

_Sources: Sriram & Noochpoung, IJCMPH 2018; Gijo & Antony, QREI 2014; Saxena et al., JCHM 2020._

## What is a clinic queue management system, really?

Strip the vendor language and a queue management system does two jobs. It sets the order patients are seen in, and it tells each patient where they stand so they are not glued to the door.

That is it. Everything else is packaging. A queue system can be a paper register and a token slip with a number called out by the front desk. It can be a small screen running a token app that shows the current number and the next few. It can be a full scheduler that mixes booked appointments with walk-ins and pushes an SMS when your turn is close. All three do the same two jobs. They differ in how much crowding they remove and what they cost.

The trap is thinking the system creates capacity. It does not. If one doctor can see roughly 20 patients an hour, no board, app, or token changes that number. What the system changes is the experience of waiting for those slots, and whether the 21st patient knows to come back after lunch instead of standing in the corridor. Keep that split clear and most queue decisions get simpler.

For the software layer underneath the queue, our [OPD software buyer guide](/in/blog/opd-software-for-clinic-india/) covers registration speed and the note flow, and the [India clinic software scorecard](/in/blog/best-clinic-management-software-india/) scores the main clinic-management options on those lines.

## Why a token board tidies the wait but does not shorten it

Here is the uncomfortable part, stated plainly. In most Indian OPDs the wait is long because throughput is limited, not because the queue is disorganised. A display board makes the queue orderly. Order and speed are different things.

The evidence backs the split. A 2018 study in the International Journal of Community Medicine and Public Health, drawing on 830 patients across 30 randomly selected hospitals in Nellore district, measured mean outpatient waits of 20.3 minutes in government hospitals, 15.5 minutes in private, and 39.71 minutes in voluntary hospitals. Those gaps track ownership and staffing, not the presence of a token screen. A nicer board in the voluntary hospital would not have closed the 24-minute gap to the private one.

Now look at what did move the number. Gijo and Antony, publishing in Quality and Reliability Engineering International in 2014, ran a Lean Six Sigma project at a super-specialty hospital in India where OPD waits had climbed as high as two hours. They cut the mean from 57 minutes to 24.5, and the standard deviation from 31.15 to 9.27. They did that by redesigning the flow: removing non-value-added steps between registration and dispensing, not by installing a fancier display. The board tells you your number. Redesigning the steps behind the number is what shortens the wait.

So a token system earns its keep on a different metric. It cuts the crowding and the anxious "am I next" that makes 20 minutes feel like an hour. That is real, and it matters for patient satisfaction. Just do not buy it expecting the average wait to drop. Buy it expecting the waiting room to calm down.

## Where is the queue actually stuck: registration or the doctor?

Before you spend on any queue tool, find the bottleneck. It is almost never where clinics assume.

Most owners picture the jam at the front desk. The data points elsewhere. In a study of an armed-forces tertiary hospital in Northern India, published in the Journal of Community Health Management in 2020, registration was fast: about 95% of patients cleared it in under 30 minutes, so only around 1 in 20 waited longer than that to register. The consultation queue was the choke point. There, 49% of patients waited more than 30 minutes to be seen. Same patients, same day, and the wait sat almost entirely on the doctor's side of the desk.

That pattern repeats across busy Indian OPDs. Registration is a quick transaction. The consult is the scarce resource, because at an average primary-care consultation of about two minutes in India, per Irving and colleagues' 67-country BMJ Open review, a single doctor's day fills up fast and the line grows. Add a lab or a pharmacy step and you get a second, quieter queue a token board never sees.

The practical move is to time it yourself for one busy morning. Note when a patient registers and when they sit in front of the doctor. If most of the gap is on the consult side, a shinier registration screen buys you almost nothing. The fix is throughput: more consult hours, a second lane for quick cases, or less time lost per patient to work that is not the consult, like typing up notes after the queue clears.

## Which queue approach fits which clinic?

There is no single best queue system, only the right fit for your volume and your mix of booked-versus-walk-in patients. Here is the honest comparison, cost against fit against the real tradeoff.

| Queue approach | Rough cost | Best fit | The real tradeoff |
|---|---|---|---|
| **Manual token + register** | A printer and a marker | Low-volume clinics, under ~40 patients a day, one or two doctors | Cheapest and instantly understood, but no remote visibility. Patients must physically wait, and the front desk absorbs every "how long more?" |
| **Digital token app + display board** | Small monthly fee, or bundled in clinic software | Mid-to-high walk-in OPDs where crowding at the door is the pain | Cuts crowding and lets patients step out. Does not add consult capacity, so the true wait is unchanged unless throughput improves |
| **Appointment-first scheduler** | Bundled in most clinic/OPD software | Specialist or procedure clinics with mostly booked visits and few walk-ins | Predictable if walk-ins are rare. Falls apart the moment a walk-in surge hits, which in a general OPD is daily |
| **Hybrid: protected slots + walk-in lane** | Bundled; needs discipline to run | General OPDs with a real mix of booked and walk-in patients | Best throughput and fairness, but only if staff hold the slot protection. Without discipline it collapses back into one long walk-in line |

_Source: approaches synthesised from Indian OPD workflow studies (Sriram & Noochpoung 2018; Gijo & Antony 2014) and clinic practice; cost bands are practitioner estimates, not a price survey._

Read the table for what it is: a fit map, not a ranking. A busy general OPD that runs a manual register is leaving crowding on the table. A procedure clinic that forces walk-in tokens on a mostly-booked panel is manufacturing chaos it does not need. Match the approach to your patient mix, then argue about vendors.

## Should you run appointments, walk-ins, or both?

Both, almost always. The clinics that pick one and stick to it are the ones that suffer.

Pure appointments look clean on paper and break in practice, because Indian OPDs get walk-ins whether they plan for them or not. The neighbour with a fever does not have a slot. Turn them away and you lose the visit and the goodwill; squeeze them in and your booked patients slip behind. Pure walk-in tokens have the opposite failure: nobody knows when they will be seen, so everyone arrives at opening.

The hybrid fixes both, and there is trial evidence that structured access beats an undifferentiated queue. Harding and colleagues, in a stepped-wedge cluster randomised trial in BMC Medicine in 2018, tested a model that combined triage with a protected appointment instead of a rolling waiting list. It cut the mean wait to first appointment by 33.7%; the median fell from 42 days to 24. That was a specialist-service setting, not a daily OPD, so read it as a principle rather than a promise: protecting a share of the schedule and triaging into it moves the wait, where a single unmanaged line does not.

For a clinic OPD, the working version is simple. Reserve a block of slots for booked patients and hold it honestly. Run a walk-in token lane in parallel with its own numbers. When a walk-in surge hits, it eats into the walk-in lane, not the protected block, so a patient who booked at 11 is not stuck behind thirty people who arrived at 10:45. The discipline is the whole trick. A protected slot that staff give away under pressure is not protected.

## What actually cuts the wait, in order

If the goal is a shorter wait and not just a calmer one, here is the order that the evidence supports.

**Throughput first.** The wait is downstream of how many patients clear per hour. Anything that adds usable consult time or removes non-consult work from the doctor's plate moves the number more than any board. That is the lever the Lean Six Sigma redesign pulled to reach 24.5 minutes.

**Then variation.** A clinic that sees 15 patients some mornings and 60 others has a queue problem hiding as a staffing problem. Smoothing arrivals with the hybrid schedule above, and staffing to the busy morning not the average one, cuts the worst waits, which are the ones patients remember.

**Then the felt wait.** Now the token app and display board earn their place. Once throughput and variation are handled, a board showing the current number and an SMS that says "you are three away" turn a tolerable wait into a non-event. Bought before the first two are fixed, they just decorate a long line.

**Then the room.** Seating and comfort come last because they change how waiting feels, not how long it lasts. A bigger waiting room hides a queue. It never shortens it.

Notice where documentation sits in this list. It is a quiet throughput lever. When a doctor writes a full note after the queue clears, that is unpaid time that could have been another patient. When the note is skipped to keep the line moving, the record thins out and the exposure grows. Reclaiming that time is one of the few throughput moves fully inside a clinic's control.

## Where an AI scribe fits, and where it does not

At the note, and nowhere near the queue. We will be blunt about the boundary, because a health vendor is exactly the party tempted to overclaim here.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Read what is not in that sentence. It does not run tokens. It does not book appointments. It does not drive a display board or call the next number. It is not a queue management system, and we do not describe it as one.

The connection to your queue is upstream and deliberately small. On a packed OPD day the note is what steals the doctor's time, either mid-consult while the room waits or after the last patient when the charting piles up. When the note drafts on its own about two minutes after the visit, the consult room clears a little faster and the after-OPD backlog shrinks. That is a throughput nudge, the same lever the top of the list cares about, not queue software. For an Indian OPD there is a practical detail: the scribe captures the code-mixed Hindi and English of a real consult and the note always comes back in clean clinical English. Visit audio is processed in memory and discarded once the note drafts, so there is no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. Data is encrypted in transit and at rest, notes belong to your practice to export or delete, and a SOC 2 Type II audit is underway; the full posture is on our [security page](../../security/). Our reads on [cutting charting time](/us/blog/reduce-charting-time-clinicians/) and [an AI scribe for Indian doctors](/in/blog/scribe-for-doctors-india/) go deeper. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If your queue pain is really front-desk load rather than doctor time, that is a different tool. An [AI medical receptionist](/in/blog/ai-receptionist-clinic-india/) handles calls and intake; a scribe handles the note. Neither one manages the token queue, and it is worth being clear which problem you are actually solving before you buy anything. If the note is where your OPD time goes, you can <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch one consult turn into a signed note.

## How do you decide in one pass?

Three questions get most clinics to a queue decision without a month of demos.

Where is the wait actually stuck? Time one busy morning from registration to consult. If the gap is mostly on the consult side, which the tertiary-hospital data suggests, a bigger board will not help. Fix throughput.

What is your real booked-to-walk-in mix? Mostly booked with rare walk-ins points to an appointment scheduler. A genuine mix, which most general OPDs have, points to the hybrid with protected slots and a parallel walk-in lane.

Is the queue tool solving crowding or capacity? A token app and display board are the right answer for crowding at the door. They are the wrong answer for a long true wait, which needs more consult hours or less non-consult work.

Sort those and the choice mostly makes itself. If the wait is driven by the doctor writing notes the queue never had time for, the missing piece is documentation, not a new queue system. <a href="/in/compare/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="compare">compare the options</a> and watch a real consult turn into a signed note, or run a <a href={CTA_URLS.in.trial}>7-day free trial</a> across one clinic day and check whether the note holds up without stealing time from the line. Either way, fix the layer the busy morning actually breaks.

---

## History and Physical (H&P) Template: What AI Fills In
https://patientsquare.com/us/blog/history-and-physical-template/
Published 2026-01-08 · Updated 2026-07-22 · Tags: clinical-documentation, templates, ai-scribe

A section-by-section H&P template a hospitalist can actually use, plus a clear line on what an AI scribe drafts for each part and what you still own.

A comprehensive adult H&P runs: chief complaint, source and reliability, history of present illness (HPI), past medical and surgical history, medications, allergies, family history, social history, review of systems, physical exam, labs and imaging, problem list, and assessment and plan. The UCF College of Medicine H&P write-up guide lists them in that order.

A history and physical (H&P) note is the full workup you write on admission or a new patient. It runs in a fixed order: chief complaint, HPI, past medical and surgical history, medications, allergies, family and social history, review of systems, physical exam, then a problem-based assessment and plan. This page gives you that template section by section, then shows exactly what an AI scribe drafts for each part and what stays your job.

The template below follows the University of Central Florida College of Medicine's comprehensive adult H&P write-up guide, which is about as close to a canonical teaching version as exists. Copy it. Then read the second half, because the interesting question in 2026 isn't what an H&P contains. It's which lines a machine can fill and which ones it can't touch.

> **Key takeaways**
>
> - A comprehensive H&P has 12 sections, from chief complaint through assessment and plan (UCF College of Medicine H&P guide).
> - The HPI is built with OLDCARTS: Onset, Location, Duration, Characterization, Aggravating/alleviating, Radiation, Temporal, Severity (StatPearls, 2023).
> - An AI scribe can draft the history and the spoken exam. It cannot do your differential, order the workup, or sign.
> - Primary-care physicians log a median of 36.2 minutes of EHR time per 30-minute visit (JAMA Network Open, 2023). The H&P is a big part of that.

## What sections does a comprehensive H&P template have?

Here's the full template, in the order you write it. Each section is one job. The UCF College of Medicine H&P guide is the reference for the wording and sequence.

**Chief complaint (CC).** The primary symptom that brought the patient in, ideally in their own words. One line.

**Source and reliability.** If the history came from someone other than the patient, say who. If the patient isn't reliable, say why ("somnolent," "intoxicated"). Skip when it's the patient and they're clear.

**History of present illness (HPI).** The story of the complaint, in order. Open with age, sex, and reason for the visit, plus pertinent past history. Then walk the dimensions of the complaint. The clean way to do this is OLDCARTS, from the StatPearls SOAP Notes reference:

- **O**nset: when did it start?
- **L**ocation: where is it?
- **D**uration: how long, and is it constant or intermittent?
- **C**haracterization: how does the patient describe it?
- **A**ggravating and alleviating factors: what makes it worse or better?
- **R**adiation: does it move?
- **T**emporal: worse at a certain time of day?
- **S**everity: rate it 1 to 10.

**Past medical and surgical history (PMH/PSH).** Conditions with dates and complications, operations with indications, OB/GYN and psychiatric history where relevant, health maintenance, and significant childhood illness.

**Medications.** Every drug with dose, route, frequency, and generic name. Include over-the-counter meds and supplements. The guide is blunt here: do not use abbreviations.

**Allergies.** Not just the agent, the reaction. "Penicillin: hives" tells the next clinician more than "PCN allergy."

**Family history.** Health or cause of death of parents, siblings, children, and the diseases that run in the family (HTN, CAD, CVA, DM, cancer).

**Social history.** Occupation, education, home situation, and quantified tobacco, alcohol, and drug use. Advance directives, functional status, and safety concerns live here too.

**Review of systems (ROS).** A system-by-system checklist of yes/no symptom questions that catches complaints the patient never volunteered. If something's already in the HPI, note "refer to HPI" rather than repeating it.

**Physical exam.** Always start with vitals: temperature, pulse, blood pressure, respiratory rate, a pain rating, and pulse oximetry when you have it. Then general appearance, then a top-down system exam (HEENT, neck, heart, lungs, abdomen, extremities, neuro, MSK, skin).

**Labs and imaging.** The data relevant to the presentation, with your interpretation, not a copy-paste of the report.

**Problem list, then assessment and plan.** List problems, most important first. Then, per problem, a differential of at least three diagnoses ordered most-likely or most-serious first, followed by a diagnostic plan, treatment plan, and patient education.

## What does an AI scribe fill in for each H&P section?

This is the table worth bookmarking. An ambient AI scribe listens to the visit and drafts a structured note. But an H&P is part transcription and part judgment, and the split is not even. Some sections a scribe drafts almost completely from the conversation. Others it can only stub, because the content lives in your head or your EHR, not in the room.

Here's each section, what the AI can realistically draft, and what you still own.

| H&P section | What an AI scribe can draft | What the clinician still owns |
|---|---|---|
| **Chief complaint** | The patient's stated reason, captured in their words | Deciding what the real complaint is when the patient buries it |
| **HPI** | The narrative, structured by OLDCARTS, from the spoken history | Pulling the thread that matters, and the pertinent negatives you chose to ask |
| **PMH / PSH** | Whatever the patient recites in the room | Reconciling it against the chart; nothing pre-fills from your EHR |
| **Medications** | The med list as the patient states it | Reconciliation against pharmacy and chart, doses, and what they actually take |
| **Allergies** | Agent and reaction, as reported | Confirming and clarifying vague reports ("upset stomach" vs true allergy) |
| **Family history** | Named conditions and relatives from the conversation | Judging relevance to the current presentation |
| **Social history** | Occupation, habits, and quantities the patient shares | Screening you did that the patient didn't narrate |
| **Review of systems** | The positives and negatives you voice during the visit | The completeness of the screen; the AI drafts only what was said |
| **Physical exam** | Findings you speak aloud as you examine | Every finding you didn't verbalize, and the exam itself |
| **Labs / imaging** | Results you dictate or read out | Your interpretation and what to order next |
| **Assessment / plan** | A first-pass structure if you talk through your reasoning | The differential, the diagnosis, the workup, the treatment. All of it. |

Read that last row twice. The assessment is where an H&P earns its keep, and it's the section a scribe can least stand in for. A transcript can hold your spoken reasoning, but the reasoning is yours. Everything above the line is capture; the plan is medicine.

One more thing the table makes concrete: an AI scribe drafts from what happened in the room, not from your chart. It doesn't pull a med list from the EHR or a problem list from prior notes, so medication reconciliation and history verification stay hands-on. Anyone implying otherwise is describing an EHR integration, not an ambient scribe.

## How does an AI scribe hand back the H&P sections?

You start a session, get consent, and see the patient. The tool captures the conversation ambiently while you work. When the visit ends, it drafts the note, sorts the history into the right sections, and hands you something to review instead of a blank template at 9pm.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign minutes after the visit. For an H&P, that structured note is the scaffold: the history sections populated from the conversation, the exam findings you spoke, and a starting assessment structure. The ICD-10 codes are suggestions you confirm, never a coding engine, and never an E&M level. The prescription is a draft, too. The scribe doesn't screen it for interactions or dosing; you review it and sign it, the same clinical check you make on every script now.

What it does not do: pre-fill from your EHR, write back into it, generate a per-specialty H&P template, or produce a patient after-visit summary. The notes always come out in clean clinical English, and the visit audio is processed in memory and discarded once the note is drafted, so there's no recording sitting anywhere. The full data posture is on our [security page](../../security/). If you're a hospitalist weighing this for admission workups, [the hospitalist walkthrough](../ai-scribe-for-hospitalists/) covers the ward-round workflow in more detail.

## Where does the AI-drafted H&P still need you most?

Three places, every time.

**Medication reconciliation.** The scribe writes down what the patient says. It has no line into the pharmacy or the chart, so the drafted med list is a claim to verify, not a reconciled list. This is a patient-safety step, not a formatting one, and it stays manual.

**The physical exam.** A scribe can only record findings you verbalize. If you examine in silence, the exam section comes back thin. The fix is habit, not software: speak your findings as you examine, the way you would to a student. What you don't say aloud, the AI can't write.

**The assessment and plan.** Drafts contain errors. Models mishear a drug name, compress two problems into one, or write something plausible that didn't happen. The assessment is exactly where a plausible-but-wrong line does the most damage, because it's the reasoning the next clinician trusts. Read it hardest. For the shorter daily notes that follow the admission H&P, our [progress note examples](../progress-note-examples/) show the same review discipline on the SOAP format, and [what accuracy really means for an AI scribe](../ai-scribe-accuracy-what-to-expect/) is worth reading before you trust any vendor's demo.

The chart is yours, legally, no matter who typed the draft. A tool that fills the history and the spoken exam at the pace of the visit is the difference between signing the H&P before you leave the floor and finishing it in bed. That's the honest pitch: it drafts the parts that are transcription, and hands you back the time to do the parts that are judgment.

If you want to test it on a real admission, review the [pricing page](../../pricing/) and bring your own workflow to a trial. Run it on a live clinic day during the trial and read every section closely for the first week. That's the evaluation that tells you the truth.

## Frequently asked questions about H&P templates and AI

The FAQ block below is the short version. The template above is the one to copy.

---

## Hospital Bed Management Software: Tracking and Discharge
https://patientsquare.com/us/blog/hospital-bed-management-software/
Published 2026-01-07 · Updated 2026-08-27 · Tags: bed-management, hospital-operations, discharge-planning, capacity

A buyer guide for US hospital bed software: real-time tracking, AI-assisted discharge planning, operational handoffs, and clinical judgement.

It is the system that shows, in real time, which beds are open, occupied, being cleaned, or blocked, and moves patients through admission, transfer, and discharge. Instead of a whiteboard and phone calls, a bed coordinator sees the whole house on one screen and can spot a discharge that frees a bed before the ED calls asking.

Bed management software answers one question a bed coordinator asks fifty times a day: where can this patient go, and when. It shows every bed in the building as open, occupied, being cleaned, or blocked, and it tracks each patient through admission, transfer, and discharge so the picture stays current instead of living on a whiteboard and in three people's heads. That is the whole job of the core product. The newer question, and the one this guide is really about, is what artificial intelligence adds on top of that, and where it has no business being.

> **Key takeaways**
>
> - Core bed management gives you a real-time bed board plus admission, discharge, and transfer coordination. That alone replaces the whiteboard and the phone tree.
> - AI adds decision support: earlier discharge-planning signals, a length-of-stay estimate for planning, and flags on units about to bottleneck. Every signal is reviewed by staff.
> - What AI does not do is assign beds or decide who gets discharged. That judgment stays with the coordinator and the care team.
> - Boarding and discharge delays are now measured by CMS, which changes the buying case from "nice dashboard" to "reported metric."

8 hr), 2017 to 2024 (Becker\'s Hospital Review, 2025)' },
    { value: '21', unit: 'hr', label: 'Mean ED boarding duration at one academic hospital, 2022–2023 (West J Emerg Med, 2025)' },
    { value: '35', unit: '%', label: 'Of admitted patients boarded more than 24 hours in that study (West J Emerg Med, 2025)' },
  ]}
/>

_Sources: Becker's Hospital Review, 2025; Western Journal of Emergency Medicine, 2025._

If you already run a hospital and you already know discharge delays are your bottleneck, you can skip to the AI section. If you are scoping this for the first time, start with what the base product actually does.

## What does hospital bed management software actually do?

Three things, and they are worth separating because vendors bundle them.

First, **a real-time bed board.** One screen shows every bed and its status: occupied, available, dirty and awaiting housekeeping, or blocked for maintenance or infection control. When a patient is discharged, the bed flips to "needs cleaning," environmental services gets the request, and the board updates when the room is ready. No one calls the floor to ask if 4-West has an open bed, because the screen already says so.

Second, **admission, discharge, and transfer coordination.** This is the flow layer. A bed request comes in from the ED, the system routes it, the receiving unit accepts, transport moves the patient, and every step is timestamped. Transfers between units and the discharge process run the same way. The value is not the dashboard; it is that the handoffs stop falling through phone calls and sticky notes.

Third, **capacity dashboards.** House supervisors and administrators get a rollup: beds available by unit, pending admits, expected discharges, and where the pressure is building. This is the view that tells a nursing supervisor at 10 a.m. whether the afternoon is going to be tight.

None of that is AI. It is workflow software with a live data model of the building, and for many hospitals it is the whole win. A [full hospital management system](/in/blog/hospital-management-system-explained/) folds this in alongside billing, pharmacy, and records, but the bed-flow slice is a distinct capability you can reason about on its own.

## Why does bed management get measured now, not just managed?

Because the numbers stopped being an internal operations concern and became a reported one.

Prolonged emergency department stays roughly doubled over seven years. The share of ED visits with a length of stay over eight hours climbed from 7.8% in 2017 to 13.9% in 2024, and prolonged inpatient boarding, admitted patients waiting more than four hours for a bed, rose from 2.6% to 6.2% over the same span, per [Becker's Hospital Review](https://www.beckershospitalreview.com/care-coordination/hospital-capacity-in-2025-5-notes-on-volumes-boarding-and-length-of-stay/). At the extreme, one academic tertiary-care hospital studied in the [Western Journal of Emergency Medicine](https://pmc.ncbi.nlm.nih.gov/articles/PMC12698171/) found a mean boarding duration of 21 hours, with 35% of admitted patients boarding more than a full day before reaching an inpatient bed.

Regulators noticed. In the FY2025 inpatient payment rule, CMS added an [Age-Friendly Hospital measure](https://www.johnahartford.org/resources/view/cms-passes-new-2025-age-friendly-hospital-measure) to the Hospital Inpatient Quality Reporting Program, with responses posted publicly on Care Compare. Then, in the CY2026 outpatient rule, CMS finalized an Emergency Care Access and Timeliness measure that, per [ACEP](https://www.emergencyphysicians.org/press-releases/2025/11-21-25-acep-statement-on-cms-2026-opps-final-rule-and-new-emergency-department-boarding-measure), requires hospitals to track ED boarding duration and report it publicly. The practical effect for a buyer: boarding and flow are now metrics you report, not just problems you feel. Software that shows the picture in real time and shortens the discharge handoff is no longer a convenience. It is tied to a number your hospital publishes.

## What AI actually adds, minus the marketing

Three things, and the honest version of each is smaller and more useful than the pitch.

**Discharge-planning support.** The single biggest lever on bed availability is getting tomorrow's discharges started today. AI can read the current census and surface the patients most likely to be discharged in the next day, so a case manager begins the transport, medication reconciliation, and follow-up work in the morning instead of at 4 p.m. when the bed is already needed. The system suggests who to look at. The case manager confirms whether the patient is actually ready. That is the loop, and the human closes it.

**Length-of-stay signals as decision support.** From patterns in the data, the software can produce an expected length-of-stay estimate for a patient or a unit. Used correctly, that is a planning signal: it tells a supervisor which patients might occupy beds longer, so discharge and placement work can be sequenced earlier. It is not a clinical prediction, and it should never be read as one. A patient does not leave because a model said so; a patient leaves when the care team decides they are ready. The estimate informs when planning starts, nothing more.

**Bottleneck flags.** The capacity dashboard can go from descriptive to anticipatory: instead of only showing that 3-South is full now, it can flag that 3-South is trending toward a bottleneck given pending admits and slow discharges, giving a house supervisor a head start on redistributing load. Again, the flag is an alert a human acts on, not an automated reroute.

The through-line is deliberate. Every one of these is a draft, a suggestion, or an alert that a coordinator, case manager, or supervisor reviews before acting. None of them moves a patient or claims a bed on its own.

## The part AI in bed management does not replace

This is the part vendors gloss over, so it gets its own section.

It does not replace the bed coordinator's judgment. Deciding whether a fragile just-post-op patient can safely take a hallway-adjacent bed, or whether a behavioral-health admit needs a specific unit, or whether to hold a bed for an expected transfer from a referring hospital, is clinical and operational reasoning that no length-of-stay model captures. The software gives the coordinator a current, complete picture and an earlier warning. The coordinator still makes the call.

It does not replace bedside clinical judgment about readiness for discharge. A length-of-stay signal that says a patient "should" be dischargeable tomorrow is a planning prompt, not a discharge order. The attending decides when the patient is ready, weighing labs, vitals, family readiness, and safe follow-up. A model that pressures that decision is doing harm, not help. The correct design keeps the AI upstream of the decision, helping the team prepare, never substituting for the clinical read.

And it does not autonomously assign beds. A system that shuffled patients into rooms without human sign-off would be a patient-safety liability, not a feature. The right posture is decision support at every step, with a person in the loop for anything that touches a patient.

## How the three options compare

Bed management shows up in three shapes. Which one fits depends on how much of your hospital you are already running on one platform.

| | Standalone bed-flow platform | EHR-embedded bed management | Bed management as a Hospital Copilot module |
|---|---|---|---|
| **What it is** | A dedicated real-time capacity and patient-flow system | Bed tracking built into your existing EHR | Bed / IPD flow packaged inside an AI bundle for hospitals |
| **Core: real-time bed board** | Yes, its whole purpose | Usually, tied to the EHR's location data | Yes |
| **ADT + discharge coordination** | Yes, deep patient-flow workflows | Present, often lighter on cross-house coordination | Yes |
| **Capacity dashboards** | Yes, house-wide | Varies by EHR | Yes |
| **AI discharge-planning support** | Vendor-dependent | Vendor-dependent | Yes, as reviewed decision support |
| **Length-of-stay signal** | Some vendors | Some vendors | Yes, framed as a planning estimate a human reviews |
| **Autonomous bed assignment** | No (and you should not want it) | No | No, by design |
| **Best fit** | Large systems standardizing flow across many facilities | Hospitals wanting flow inside the record they already use | Mid-market hospitals adding AI to flow without ripping out systems |

A word on the standalone category, since it dominates the search results. [TeleTracking](https://www.teletracking.com/), for example, describes its own product as a real-time capacity management platform with bed tracking, patient-flow optimization, and predictive analytics for hospitals. That framing is theirs, and it is a reasonable description of the mature standalone category: enterprise-grade, built for large systems coordinating flow across many buildings. For a 50-to-300-bed facility, the question is usually whether you need a separate platform of that weight, or whether flow belongs inside something you already run.

## Where does bed management as a Hospital Copilot module fit?

In the middle of that table, and on purpose.

Patient Square packages hospital tools as **Hospital Copilot**, which can use the complete Patient Square HIS/EHR or work alongside an existing HIS/EHR. Bed / IPD Management is one module inside it. The [ambient AI scribe](../ai-scribe-for-hospitalists/) that drafts H&Ps, progress notes, and discharge summaries is a separate module in the same bundle. The reason to mention them together is practical: discharge planning and discharge documentation are the same bottleneck seen from two sides. The bed module flags a likely discharge early; the scribe module gets the discharge summary drafted quickly once the decision is made. A cleaner, faster summary is often what stalls a discharge at the last step, so the two modules pull on the same rope.

The design boundaries are the ones this whole guide has argued for. The length-of-stay signal is a planning estimate a human reviews, never an autonomous call on when a patient leaves. Discharge-planning suggestions surface likely candidates for a case manager to confirm. Nothing assigns a bed without a person. On the scribe side, visit audio is processed in memory and never stored, and notes come back in English for review before anyone signs. We do not claim EHR integration, we do not claim a certification we do not hold, and we do not put an accuracy number on the AI outputs, because those are review-and-sign drafts, not autonomous decisions.

For a mid-market hospital, that framing matters. You are not buying a standalone enterprise flow platform and running a second parallel system. You are adding an AI flow module, and a documentation module, to tools your staff already touches, with the human kept in the loop at every step that reaches a patient.

The way to judge any of this is the same for bed management as it is for anything that touches your floor: watch it on a real day. Review the [Hospital Copilot page](/us/products/hospital-copilot/) with your own census, your own discharge backlog, and your own ED boarding problem. See where the bed board lands, where the discharge-planning flags fire, and whether the length-of-stay signal actually helps your case managers start earlier. A comparison table narrows the field; your own Monday morning capacity crunch settles it.

_Sources: Becker's Hospital Review, 2025; Western Journal of Emergency Medicine, 2025; CMS FY2025 IPPS Age-Friendly Hospital measure (John A. Hartford Foundation); ACEP on the CMS CY2026 OPPS ED boarding measure, 2025; TeleTracking vendor page._

---

## WhatsApp for Clinics in India: Reminders and Reports
https://patientsquare.com/in/blog/whatsapp-for-clinics-india/
Published 2026-01-07 · Updated 2026-10-04 · Tags: whatsapp, patient-communication, dpdp, compliance, india

How Indian clinics use WhatsApp for reminders, reports, and follow-ups, the WhatsApp Business API basics, and the DPDP consent rules a practice must respect.

A personal WhatsApp number mixes patient messages with private chats and makes clinic oversight harder. A WhatsApp Business account can separate the clinic's conversations, but the app does not supply a purpose-specific consent record or a clinical audit log. Record the patient's opt-in in your clinic system, verify the recipient before sending, and use the message only for the agreed purpose.

Most Indian clinics already run on WhatsApp. The reminder the day before, the lab report photographed and sent, the "how are you feeling now" three days after an antibiotic course. The question is how to use it without exposing patient data or losing track of consent. Keep messages on a clinic-controlled account, record the patient's opt-in for a stated purpose, and check the recipient before sending health information. If you automate through the WhatsApp Business Platform, its template rules also apply.

> Key takeaways
>
> - On the WhatsApp Business Platform, a patient's message opens a 24-hour customer service window. Free-form replies are allowed inside it; outside it, the Platform requires an approved template. This API rule does not describe manual messages in the Business app.
> - Patient data on WhatsApp is personal data under the DPDP Act 2023. Prepare for the Act's purpose-specific consent duties, scheduled for 13 May 2027; get clear opt-ins now under applicable privacy and messaging rules.
> - A personal WhatsApp number is the weakest option: no opt-in trail, no separation from your private life, nothing to show later. Move to WhatsApp Business or the Platform.
> - Reminders and report delivery are legitimate uses. Marketing blasts are a different purpose and a different consent, and they collide with TRAI's commercial-communication rules.
> - An AI scribe does not touch any of this. It writes the note; your clinic sends the message.

## Common clinic uses

Three jobs, over and over, and they map cleanly onto how WhatsApp itself works.

The first is reminders. A message the evening before the appointment cuts no-shows, and for a chronic patient it carries the next review date. The second is reports and documents: a lab result, a scan summary, a prescription photo, a discharge note the family wants a copy of. The third is follow-up: a check-in after a procedure, a nudge to complete a medicine course, a "come back if the fever crosses three days" that the patient can re-read at home.

Each of these may be a message the clinic starts. If your clinic uses the Business Platform API, the rules differ for a message you start and a reply to a patient who contacted you. Manual messages from the Business app do not use that API's template flow. In both cases, the clinic still needs a record of the patient's consent and a check of the recipient.

## The Platform customer service window

This is the one mechanic worth understanding before you spend a rupee on any tool.

On the WhatsApp Business Platform, the API layer that powers automated messaging, Meta opens what it calls a customer service window the moment a patient messages your number. That window lasts 24 hours from the patient's most recent message. Inside it, you can send free-form messages: type whatever you like, answer their question, send the report they asked for. Once 24 hours pass with no new message from them, the window closes.

Outside a closed window, you cannot just send a free-form message. To reach a patient who hasn't written to you in the last day, which is exactly the case for a reminder about tomorrow's appointment, you have to send a pre-approved message template. Meta requires this and sorts templates into categories: utility (an appointment reminder, a report-ready notice), authentication (a one-time code), and marketing (a promotion). A delivered template message is charged per message, while ordinary replies inside an open window are free. All of this comes straight from Meta's WhatsApp Business Platform documentation on service messages and pricing.

So the practical shape of it: a patient writes to you, you have a day to reply freely; you want to reach them first, you use an approved template. A clinic that grasps this stops fighting the platform and starts designing around it.

## Consent before messaging

Consent, and a narrow one. India's Digital Personal Data Protection Act, 2023, enacted on 11 August 2023, has been enacted, but its core processing duties are scheduled to commence on 13 May 2027. A patient's name, phone number, diagnosis, and report are all personal data. Section 6 of the Act sets the bar for consent: it must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action signifying agreement," given for a specified purpose. That is close to the statutory wording, not a loose paraphrase.

Translate that to a clinic desk and it is not complicated:

- Free and specific. The patient agrees to WhatsApp messaging on its own, not buried in a general intake form they had to sign to be seen.
- Informed. You tell them what you'll send: appointment reminders, reports, follow-up checks. Not "communications," which says nothing.
- For a stated purpose. Consent for reminders is not consent to add them to a broadcast about your new physiotherapy package. That is a different purpose, and it needs its own opt-in.

Purpose limitation is the part clinics trip on. Once the core DPDP duties commence on 13 May 2027, the Act limits use to the purpose the patient agreed to. The number they gave you for their report is not a marketing list. The final DPDP Rules were notified on 13 November 2025 and phase in alongside the Act, so prepare now: get clean opt-ins on record, keep them purpose-scoped, and don't retrofit consent onto data you already hold for a different reason.

## Reminders, reports, follow-ups: what's allowed and what needs consent

This table maps common clinic messages to the Business Platform API rules and the consent records a clinic should keep. The template column does not apply to manual messages from the Business app.

| WhatsApp use | Who sends first | WhatsApp mechanic needed | Opt-in to record now (and for DPDP when applicable) | Notes |
|---|---|---|---|---|
| Appointment reminder (day before) | Clinic | Pre-approved utility template (window is closed) | Yes, opt-in for reminders | Utility category; charged per delivered template |
| Reply to a patient's question | Patient | Free-form message inside open 24-hour window | The patient started the chat, which supports a reply; still record the purpose | Free while the window is open |
| Sending a lab report or prescription | Usually clinic | Template if window closed, free-form if open | Yes, and send only to the confirmed number | Health data; never into a group |
| Post-procedure follow-up check | Clinic | Utility template, or free-form if patient replied recently | Yes, opt-in for follow-up | Keep it clinical, not promotional |
| One-time verification code | Clinic | Authentication template | Covered by the service consent | Rarely needed by a small clinic |
| Promotion or health-camp blast | Clinic | Marketing template | Separate marketing opt-in | Also engages TRAI commercial-communication rules |

Two lines in that table do the heavy lifting. Report delivery is fine, but it is health data, so it goes only to the number the patient confirmed and never into a group where other patients or your own staff can read it. And the promotion row is where clinics get into trouble: a marketing blast will be a different purpose under the DPDP duties from 13 May 2027, a marketing template under WhatsApp, and it also runs into TRAI's Telecom Commercial Communications Customer Preference Regulations, 2018, which require the recipient's consent, defined there as voluntary permission, before you send commercial communication. Reminders and reports are service, not marketing. Keep the two lanes separate.

## Choosing a clinic account

For a solo GP the honest answer is: start smaller than the vendors want you to.

A personal WhatsApp number is the setup to leave behind. It mixes patient chats with your family group, keeps no opt-in record, and gives you nothing to show if a patient ever disputes what you sent. It also drags your private number into a medico-legal record it shouldn't be in.

The free WhatsApp Business app can help a small clinic separate its messages from personal chats. It gives you a business profile, quick replies, labels to organise chats, and greeting or away messages. It does not create a purpose-specific consent record or a clinical audit log for you. Keep the opt-in and the agreed purpose in your clinic system, check the recipient number before every sensitive message, and retain records according to your clinic's policy.

The WhatsApp Business Platform (the API) is the step up. It adds automated template messages so reminders go out on their own, lets several staff work one number, and connects to other software through a provider. You take it on when manual sending stops scaling, or when you want reminders to fire without someone remembering to press send. It runs through an approved Business Solution Provider and carries the per-template costs described above. Move up when the app starts feeling like a bottleneck, not before.

Whichever you choose, use a purpose-specific opt-in now. The DPDP processing duties scheduled for 13 May 2027 will apply to either account type.

## The AI scribe boundary

At the note, and nowhere near the messaging. This is exactly the boundary a health vendor is tempted to blur, so we'll be plain about it.

The AI Medical Scribe is one module inside Practice Copilot, Patient Square's AI platform for the whole practice. The scribe listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Read what the scribe module itself does not do. On its own it does not send WhatsApp messages and it is not a patient-communication tool or a CRM. Patient Square does add WhatsApp messaging higher up the plan, at the Copilot tier, but that is a separate module from the scribe: the note-drafting piece we are talking about here is not the thing that reaches your patients. This post is about running WhatsApp itself well, so treat the two as distinct.

The link to your WhatsApp workflow is upstream and small. When the clinical note is complete and consistent, whatever your front desk sends afterward is easier to get right. The follow-up instruction is already in the note. The diagnosis and plan the report relates to are already captured. For an Indian OPD there's a practical detail: the scribe handles the code-mixed Hindi and English of a real consult, and the note always comes back in clean clinical English. Visit audio is processed in memory and discarded once the note drafts, so there's no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023. Data is encrypted in transit and at rest, notes belong to your practice to export or delete, and a SOC 2 Type II audit is underway; the full posture is on our [security page](../../security/). We think the honest version of the pitch is the useful one: better notes in, and your own messaging out. The rail that carries the reminder is your job, not ours. This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

If you're weighing the note side of this, our reads on [an AI scribe built for a solo doctor in India](../ai-scribe-for-solo-doctors-india/) and [what the DPDP Act asks of a clinic day to day](../dpdp-act-clinics-guide/) go deeper than we can here. For the wider consent picture, the [NMC teleconsultation rules explainer](../teleconsultation-guidelines-india-nmc/) covers the record-keeping side; the NMC's 2023 conduct regulations that touched retention were put in abeyance in August 2023, so treat the roughly three-year record-keeping expectation as guidance to plan around, not a live mandate.

## The short version, and where to start

WhatsApp is a genuinely good tool for reminders, reports, and follow-ups, and Indian clinics are right to lean on it. The two things that keep it safe are the same two things vendors gloss over. First, the 24-hour customer service window: reply free-form when a patient writes, use an approved template when you write first. Second, record a specific, purpose-scoped opt-in and keep marketing separate under current messaging and privacy rules; this also prepares you for the DPDP processing duties scheduled for 13 May 2027. Get those two right and the account choice, app or Platform, is just a matter of scale.

Review missed follow-ups to identify whether the gap was an incomplete clinical plan, an unclear staff handoff, or a failed message. Confirm the recipient, consent, and approved channel before sending health information. The [security page](../../security/) describes Patient Square's data handling; clinics should evaluate it alongside their own messaging procedures.

---

## AI Medical Receptionist for Clinics: A Safety-First Test
https://patientsquare.com/us/blog/ai-medical-receptionist-for-clinics/
Published 2026-01-06 · Updated 2026-08-29 · Tags: ai-receptionist, front-desk, scheduling, practice-copilot

Test an AI medical receptionist on scheduling, after-hours calls, staff takeover, privacy, and the clinical or emergency calls it must never handle alone.

Products in this category may answer calls, book or change appointments, send reminders, and route routine requests. Those are claims to test, not capabilities to infer from the label. The safe boundary is firm: the system must not give clinical advice, decide that a symptom can wait, or replace emergency and human escalation.

An AI medical receptionist is a voice or messaging system that may handle routine front-desk work such as answering, booking, changing appointments, reminders, and routing. Each verb needs a real test. The product must not give clinical advice, decide that an urgent symptom can wait, or replace emergency and human escalation. The buying decision is mostly a failure-and-handoff decision.

> **Key takeaways**
>
> - An AI receptionist may handle routine calls, but the vendor must prove each calendar, reminder, routing, and takeover path on your real system.
> - It does not replace clinical judgment or a human front desk. Urgent symptoms, distressed callers, and messy edge cases still need a person, and a good setup escalates them fast.
> - Phreesia found that 65% of surveyed patients preferred to book by phone. Treat phone coverage as a workflow to measure, not a promised booking outcome.
> - For most clinics the real question isn't AI-versus-human. It's what you free the human to do once the phone stops owning their day.

_Sources: Phreesia; Rotenstein et al., JAMA Network Open 2022 via AMA; MGMA._

If your problem is dropped calls and no-shows rather than documentation, start with the failure script below. The [medical office scheduling guide](/us/blog/medical-office-scheduling-software/) owns the calendar-software decision; this page owns voice automation and human takeover.

## What does an AI medical receptionist actually handle?

Four jobs appear often in this category. Treat each as a vendor claim until it passes your test.

**Scheduling and rescheduling.** A product may find a permitted slot, book it, change it, or cancel it. Test visit types, provider rules, lead times, buffers, double-booking, and staff override. Phreesia's patient-preference research found phone remained a major appointment channel; that makes the line worth testing, not a reason to assume any bot can run the calendar.

**After-hours and overflow calls.** The product may answer, complete a permitted task, or create work for the morning. Test what happens when the calendar is unavailable, the caller refuses recording, or the request needs a person who isn't on duty.

**Reminders and confirmations.** Automated reminders can support attendance, but a category page cannot promise recovered revenue. Test consent, opt-out, language, delivery failure, confirmation write-back, and the staff queue for replies.

**Intake routing.** A system may ask why the patient is calling and send a routine request to a queue. That is logistics, not clinical triage. It cannot decide that chest pain, shortness of breath, a medication problem, or a distressed caller can wait.

Put together, these are the calls that eat a front desk alive without ever needing a clinical brain. That's exactly the slice to automate, and exactly where the boundary needs to be drawn.

## What can an AI receptionist still not do?

Here's the part most vendor pages skip, so it's worth stating plainly. An AI receptionist is a logistics tool wearing a friendly voice. Push it past logistics and it gets dangerous.

- **Clinical triage.** Deciding whether a symptom is an emergency is a clinical act. An AI front desk can flag keywords and escalate, but it must not be the thing that tells a patient their symptom can wait. That's a nurse line or a clinician, not a scheduler.
- **Empathy-critical calls.** A frightened patient, a new diagnosis, a bereaved caller. These need a person who can read a pause and adjust. An automated voice handling one of these well is the exception, and betting on the exception is how clinics lose patients.
- **Messy edge cases.** The insurance question with three conditions, the scheduling request that breaks every rule, the caller who won't state a reason. Rule-based routing handles the common 80%. The remaining 20% is where a decent system hands off fast instead of improvising.
- **Anything medico-legally load-bearing.** Advice, dosing, results interpretation. None of it belongs to the front desk, human or AI.

The quality signal to look for isn't how much an AI receptionist tries to solve on its own. It's how cleanly and quickly it escalates the calls it shouldn't touch. A tool that guesses confidently on an urgent call is worse than a full voicemail box, because voicemail at least doesn't pretend.

| Test call | Safe expected behavior | Evidence to keep | Automatic failure |
|---|---|---|---|
| Routine new-patient booking | Offers only permitted slots and repeats the final date, time, clinician, and location | Calendar entry plus transcript or audit record | Wrong visit type, unavailable slot, or silent double-booking |
| Same-day cancellation | Applies the clinic's cutoff rule and creates the correct follow-up task | Calendar change and staff notification | Deletes the visit without the required task or notice |
| Caller says “chest pain” | Stops routine automation and gives the clinic-approved emergency direction or immediate human path | Timestamped escalation event | Reassurance, diagnosis, delay advice, or an ordinary callback queue |
| Distressed or grieving caller | Transfers or creates a high-priority human task with minimal repeated questioning | Handoff time and receiving owner | Continues a scripted intake after the caller asks for a person |
| Ambiguous insurance dispute | Routes to authorized billing staff without promising coverage | Queue owner and captured facts | Invented benefit, price, or coverage answer |
| Calendar or vendor outage | States the limitation, avoids booking, and records a recoverable task | Fallback task and later reconciliation | Confirms an appointment it could not write |
| Patient refuses automation | Honors the refusal and offers the approved alternative | Consent or refusal record | Keeps collecting optional details or blocks human access |

## Where does the AI receptionist fit inside Practice Copilot?

Patient Square packages its practitioner product as **Practice Copilot**. The public [pricing page](/us/pricing/) names AI Receptionist at the Autopilot tier. It does not document the detailed call, calendar, reminder, or takeover behavior claimed by this product category. We won't fill that gap with marketing prose.

The scribe is different because its public scope is defined: ambient capture, a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. The prescription is not transmitted to a pharmacy. Scheduling starts on Assist, and the Copilot tier adds the bundled AI Copilot EHR and WhatsApp messaging. None of those module names proves that the receptionist passes the seven calls above.

On data handling, ask where call audio, transcripts, tasks, and identifiers sit; how long each is retained; who can access them; what appears in an audit trail; and whether the vendor will sign a BAA when it needs PHI access. HHS says a software vendor that hosts patient information or accesses it to provide the service is a business associate and requires the agreement before access ([HHS software-vendor FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/256/is-software-vendor-business-associate/index.html)). The [Patient Square security page](/us/security/) states the platform posture, but the exact receptionist data flow still belongs in the trial acceptance review and contract.

## When is an AI front desk worth a trial?

Not for every clinic. Trial it when the phone is a measured bottleneck: long holds during a rush, missed after-hours calls, repeated routine requests, or staff spending a known block of time on confirmations. Record a baseline week before the trial. Count offered calls, answered calls, abandoned calls, completed bookings, booking errors, human handoffs, time to takeover, and unresolved tasks.

Don't trial it when the phone isn't the problem. A low-volume practice with a calm front desk and a portal-first patient base may gain little. The same is true when the calendar rules aren't documented or no person owns urgent takeover. Automation won't repair an undefined process.

At the end of the trial, compare the same measures. Don't turn every answered call into invented revenue. A completed appointment still can cancel or no-show, and a handled call can create downstream work. The product earns a wider test when it improves the baseline without increasing booking errors, unresolved tasks, or unsafe handoffs.

If the trial plan is ready and the clinic has a staffed fallback, [compare the product options](/us/compare/). Keep the first week narrow enough that every exception gets reviewed.

Start with one clear job and one staffed fallback window. Expand only after the clinic has reviewed every failure and updated the script, calendar rule, or takeover path. The [patient-management category guide](/us/blog/patient-management-software-guide/) helps separate the phone layer from portals, records, scheduling, and billing.

## How do you evaluate an AI receptionist without getting sold?

Skip the feature list. Four questions separate a useful tool from a script that falls apart on a real Tuesday.

1. **How does it escalate?** Ask for the exact behavior when a caller describes an urgent symptom or gets upset. If the answer is vague, the tool is guessing. You want a fast, explicit handoff to a human, not a confident bot.
2. **Where does the data live, and will you sign a BAA?** The moment it takes a name and a reason, it's handling protected health information. No BAA, no deal.
3. **Does it book against my real calendar, or a copy?** A receptionist that double-books because it's syncing on a delay creates more front-desk work than it removes.
4. **What happens when it doesn't understand?** The graceful failure is "let me get someone who can help." The bad one is a wrong answer delivered smoothly.

A tool that answers these cleanly is worth a trial on your own phone lines. One that dodges them is a liability wearing a pleasant voice, and the SERP is full of the second kind.

The deciding move is the same one we'd give a colleague. Don't buy on a feature grid, including this one. Run the seven failure calls, then a limited real-clinic week with a person ready to take over. [compare the product options](/us/compare/) when the clinic can test the AI Receptionist module inside [Practice Copilot](/us/products/practice-copilot/) against that script. If the product cannot show the behavior, count it as absent.

_Sources: Rotenstein et al., JAMA Network Open 2022 (via AMA); Phreesia patient-preferences survey; MGMA no-show benchmark; CDC / NCHS NAMCS._

## How Patient Square fits your existing record system

In the US, an established practice can keep its current EHR as the system of record while Practice Copilot works alongside it. A new practice can instead use the bundled Patient Square EHR, available from the Copilot tier, as its system of record. Neither path promises automatic filing or write-back into a named third-party EHR.

---

## Lab Management Software in India: LIMS vs HMS Modules
https://patientsquare.com/in/blog/lab-management-software-india-lims/
Published 2026-01-06 · Updated 2026-08-27 · Tags: lims, lab-management-software, diagnostic-lab-software, india

Compare Indian lab software, standalone LIMS, and HMS lab modules. See when diagnostic centres need separate systems and what drives price.

There is no single best one. A diagnostic centre running its own analyzers, worklists, and NABL file wants a standalone LIMS built for sample workflow. A small clinic that only orders a handful of tests is usually fine with the lab module inside its HMS. Score each on analyzer interfacing, result validation, TAT tracking, and NABL-oriented traceability, then trial the two or three that clear those. "Best" depends on how much lab you actually run.

Most Indian diagnostic centres discover the difference between a LIMS and an HMS lab module the hard way: on the day an NABL assessor asks to trace one sample from the collection tube to the signed report, and the "lab software" turns out to be an order-entry screen with a free-text result box. The order got billed. The workflow in between never existed in the system. If you run a lab that matters to your revenue, that gap is the whole question. This is a buyer's guide to what a standalone lab information management system does that a thin HMS module usually can't, and when the module is genuinely enough.

> **Key takeaways**
>
> - A LIMS and an HMS lab module solve different problems. The module handles order entry and billing. A real LIMS runs the sample lifecycle: accessioning, barcoding, analyzer interfacing with QC, result validation, formatted reports, and turnaround-time tracking.
> - You need standalone LIMS when volume rises, when you interface analyzers, when you run a collection-centre network, or when NABL traceability becomes part of how the lab is judged. A small internal lab is often fine on the HMS module.
> - No software makes a lab NABL-accredited. NABL, a constituent board of the Quality Council of India, accredits the lab itself against ISO 15189. Good software makes the evidence easier to produce; it does not confer the badge.
> - Prices are almost always sales-gated. Ask for the number in rupees, ex-GST with 18% GST stated, and price analyzer interfacing and support separately, because that is where the real cost sits.

_Sources: NABL / QCI; ISO; MoHFW EHR Standards 2016._

If you already know your lab has outgrown the HMS box, choose a proper LIMS first. Hospital Copilot can then use the complete Patient Square HIS/EHR or work alongside an incumbent HIS/EHR, but neither path invents analyzer or sample-routing capabilities. You can book a demo of Hospital Copilot after the lab boundary is clear.

## What is lab management software, and why the label misleads

"Lab management software" gets used for two things that are not the same, and the confusion costs labs money.

The first is the **lab module inside a hospital management system**. Your HMS already handles registration, OPD, IPD, billing, and pharmacy. Somewhere in it is a lab tab: the doctor orders a CBC, the order flows to the lab, someone types the result back, the bill goes out. For a clinic that sends a few tests a day, this is fine. It records that a test happened and charges for it. That is most of what a low-volume lab needs from software.

The second is a **standalone LIMS**, a laboratory information management system built for the work between the order and the report. This is a different animal. It assumes the lab is a workflow with its own rules, its own machines, and its own accountability, and it is designed to run that workflow end to end rather than just bookend it with an order and an invoice.

The trap is that both get sold as "lab software." A diagnostic centre owner hears "our HMS has a lab module" and assumes the sample workflow is covered. It usually is not. The module records the two ends of the process and leaves the middle, the part an NABL assessor cares most about, as manual work and a text box.

## What does a standalone LIMS actually do?

Here is the work that lives between the order and the signed report, and what a purpose-built LIMS does with each step.

- **Sample accessioning and barcoding.** Every sample gets a unique accession number and a printed barcode at the point of collection. From that moment the system, not a register, tracks where the sample is. A thin module that never issues a barcode cannot tell you which of today's forty tubes is sitting on which bench.
- **Worklists and bench organisation.** Tests are grouped into worklists by analyzer, department, or shift, so a technician sees exactly what to run and in what order. This is the operational heart of a busy lab and the thing an order-entry screen has no concept of.
- **Analyzer interfacing and quality control.** A real LIMS talks to your haematology, biochemistry, and immunoassay analyzers, pulling results in electronically instead of asking someone to read a printout and type it. It also holds QC data: Levey-Jennings charts, Westgard rules, control lots, so a run that fails QC is flagged before its results reach a patient. HMS modules almost never interface analyzers; they were built to bill, not to bench.
- **Rule-based result validation.** Results run through auto-verification rules, reference-range checks, delta checks against the patient's prior value, and critical-value alerts before a pathologist signs them out. The module's free-text box has none of this; it trusts whatever gets typed.
- **Report generation with reference ranges.** The output is a formatted report with age- and sex-specific reference ranges, flags for abnormal values, and the reporting pathologist's authorisation, ready to print or push to the patient. Consistent, traceable, and defensible.
- **NABL-oriented traceability.** Every step, who collected, who ran, which lot, which control, who validated, is logged with a timestamp. That audit trail is precisely what an ISO 15189 assessment looks for. It is far easier to hand an assessor a system that already records it than to reconstruct it from paper.
- **Turnaround-time tracking.** The LIMS timestamps each stage, so you can measure TAT per test, per shift, per analyzer, and see where samples stall. A lab that cannot measure turnaround time cannot manage it, and TAT is one of the numbers a referring doctor judges you on.

None of this is exotic. It is the ordinary daily work of a diagnostic lab. The point is that a system designed only to order and bill tests does not model any of it.

## How do a standalone LIMS and an HMS lab module compare?

Read the first row before the rest. It tells you which problem each tool was built for, and every difference below flows from that.

| Capability | HMS lab module | Standalone LIMS |
|---|---|---|
| **Built for** | Ordering and billing tests | Running the sample lifecycle |
| **Sample accessioning + barcoding** | Rare; often an order ID only | Core: unique accession + barcode at collection |
| **Worklists** | Not usually present | Grouped by analyzer / department / shift |
| **Analyzer interfacing** | Almost never | Bidirectional interfaces to lab analyzers |
| **Quality control (QC)** | Not modelled | Levey-Jennings, Westgard rules, control lots |
| **Result validation** | Free-text entry, trusted as typed | Auto-verify rules, reference-range + delta checks |
| **Reports with reference ranges** | Basic; often generic | Age/sex-specific ranges, abnormal flags, sign-out |
| **NABL / ISO 15189 traceability** | Partial at best | Full timestamped chain of custody |
| **Turnaround-time (TAT) tracking** | Order and bill dates only | Per-stage timestamps, TAT reporting |
| **Collection-centre / hub-spoke** | Weak | Designed for multi-site sample flow |

This is not a knock on HMS modules. They do their job, which is keeping the lab tied into the hospital's billing and records. The comparison only matters because buyers reach for the module to do a LIMS job, then find the middle of the workflow missing.

## When is the HMS lab module actually enough?

Plenty of the time. Buying a standalone LIMS for a lab that runs twenty tests a day is overbuying, and the extra system is real cost and real maintenance. Stick with the HMS module when:

- The lab is a **small internal service** for your own OPD and IPD, not a business you market to referring doctors.
- Your **test menu is modest** and you do not run your own analyzers, or you run one or two with manual result entry you are comfortable with.
- You are **not chasing NABL** and no external body is auditing your sample traceability.
- You value having **one system and one login** over deeper lab function, and the module's limits do not bite in daily work.

If that describes you, the module is the simpler, cheaper, correct answer. Do not let a LIMS vendor talk you into workflow you do not have.

## When does a diagnostic centre need standalone LIMS?

The switch is driven by workflow, not headcount. You have outgrown the module when two or more of these are true:

- **Volume has climbed** to where typing results one by one is a bottleneck and errors creep in.
- **You interface analyzers**, or want to, and manual transcription from machine printouts is both slow and a transcription-error risk.
- **You run collection centres** feeding a central lab, so samples move between sites and need barcoded chain of custody, not a shared register.
- **NABL accreditation is on the table**, and you need ISO 15189-grade traceability, QC records, and validation rules that a free-text box cannot produce.
- **Referring doctors judge you on turnaround time**, and you need to measure and report TAT to compete, which means per-stage timestamps you do not currently capture.

A diagnostic centre that is a business in its own right almost always lands here eventually. The tell is that the lab has stopped being a feature of the hospital and become a product with its own customers.

## What should lab management software cost in India?

Be sceptical of any single number, including any a vendor leads with. Most LIMS and diagnostic-lab software in India is sold through a sales call, and the sticker moves with your volume, your number of sites, and how many analyzer interfaces you need. That is normal for this category, but it means the headline price is rarely the real price.

When you ask for a quote, insist on three things. Ask for the figure **in rupees, ex-GST, with the 18% GST stated separately**, so you can compare like with like. Ask what **analyzer interfacing** costs, per instrument, because that line item is often where a "cheap" LIMS becomes expensive. And ask what **implementation, training, and annual support** run to, since a LIMS you cannot get live or keep running is not a saving.

We are not going to invent competitor LIMS prices here, because we do not sell a LIMS and publishing numbers we cannot stand behind would not help you. What we can tell you is the shape of the decision: the software licence is often the smaller part of the bill, and interfacing plus support is where the money goes. Price the whole thing, not the headline.

## What does NABL accreditation actually require of your software?

This is where buyers most often get sold a myth, so it is worth stating plainly. **No software makes a lab NABL-accredited.** NABL, the National Accreditation Board for Testing and Calibration Laboratories, is a constituent board of the Quality Council of India, and it accredits medical laboratories against **ISO 15189**, the international standard for quality and competence in medical labs. NABL recently launched a dedicated Medical Application Portal for ISO 15189:2022 applicant laboratories, which tells you how active this accreditation path is.

Accreditation assesses the **lab**, not the vendor: your people, your methods, your quality control, your records, and whether a result can be traced from sample to report. Software cannot pass that assessment for you. What good software does is make the evidence easy to produce. When an assessor asks to follow one sample through the whole process, a LIMS that has logged accessioning, the run, the QC lot, the validation, and the sign-out hands over that chain in seconds. A free-text module sends someone digging through paper.

So the honest framing for a buyer is: a capable LIMS supports NABL accreditation by producing the traceability ISO 15189 expects. It does not confer the badge. Any vendor who implies their software is "NABL-certified" for your lab is selling you a category error. And to be equally straight about our own position, Patient Square does not sell a LIMS and makes no accreditation claim of any kind for your lab.

## Where does Patient Square fit, honestly?

Not in the LIMS lane, and we are not going to pretend otherwise. Patient Square does not run your analyzers, accession your samples, or generate your lab reports. If that is what you need, buy a proper LIMS and score it on the capability table above.

Patient Square handles the **clinical note the doctor writes around the lab result**, not the sample workflow itself. Practice Copilot and Hospital Copilot each contain an ambient documentation module that drafts the encounter note for clinician review and signature. Hospital Copilot can use the complete Patient Square HIS/EHR as the record system or work alongside an incumbent HIS/EHR. In either deployment, the LIMS still owns analyzer, accession, sample, and result workflows. The draft is not a lab report and does not touch LIMS records.

If your lab has outgrown the HMS module, the move is a standalone LIMS, chosen on the workflow it actually runs. If you also want to cut the documentation time clinicians lose around every result, Hospital Copilot can pair that LIMS with either Patient Square's complete HIS/EHR or the hospital's incumbent record system. For the wider picture, the [HMS modules explained](../hospital-management-system-explained/) guide maps the stack, [clinic management software in India](../best-clinic-management-software-india/) scores front-office tools, and the [EMR software India guide](../emr-software-india-guide/) covers the clinical record. Book a demo of Hospital Copilot with those system boundaries in hand.

_Sources: NABL / Quality Council of India (medical-lab accreditation against ISO 15189); PIB (NABL Medical Application Portal for ISO 15189:2022, 2025); ISO 15189; MoHFW EHR Standards 2016._

---

## ABHA Linking at the Clinic: The Actual Front-Desk Workflow
https://patientsquare.com/in/blog/abha-linking-clinic-workflow/
Published 2026-01-05 · Tags: abdm, abha, india, front-desk, workflow

What ABHA is, how a clinic creates or verifies one at check-in, how patient consent works, and the real front-desk steps and pitfalls of linking a visit record.

No, they are two different things tied to one account. The ABHA number is a 14-digit randomly generated identifier for a person. The ABHA address is an easy-to-remember username in the format name@abdm that the patient uses to view and share records. NHA describes both as part of the same Ayushman Bharat Health Account. A patient can have the number without ever using the address.

At the desk, ABHA linking is usually not the clinic creating anything. The patient already has an Ayushman Bharat Health Account, they scan the clinic's QR code, and their name, date of birth, gender, mobile, and ABHA details drop into your registration screen. That is Scan and Share, it runs on the patient's implied consent at the moment they scan, and it is the fast lane most clinics actually use. Creating a fresh ABHA and linking clinical records are the two other jobs, and they come with rules that trip up front desks. This walks all three, in the order they happen at check-in. General information, not legal advice; confirm current steps on the NHA portal.

> **Key takeaways**
>
> - An ABHA number is a 14-digit identifier for a person; the ABHA address is a `name@abdm` username. Same account, two identifiers.
> - Creating an ABHA is free, voluntary, paperless, and takes about five minutes via Aadhaar OTP, mobile OTP, or driving licence, per NHA.
> - Scan and Share moves demographics at registration on implied consent. Sharing clinical records needs explicit, granular consent the patient grants in their app and can revoke.
> - The most expensive front-desk mistake is making a duplicate ABHA for someone who already has one.

_Source: NHA, Ayushman Bharat Digital Mission FAQ._

## What is an ABHA, and why does the front desk care about two identifiers?

One account, two things people confuse for each other.

The **ABHA number** is a 14-digit randomly generated number that identifies the patient. The **ABHA address** is a readable username, formatted like `name@abdm`, that the patient uses to log in, view records, and share them. NHA treats both as parts of the same Ayushman Bharat Health Account. A patient can hold the number and never touch the address, or use the address every visit. Your desk staff need to recognise both, because a patient may hand you either one.

Why this matters at check-in: when someone says "I have my ABHA," ask which one they have in front of them. A 14-digit number and a `name@abdm` handle are both valid, and both let you attach the visit to the right person. Keying the wrong field, or assuming the address is the number, is where the first mismatch starts. The account is free and enrolment is voluntary, so nobody can be turned away for not having one. That framing keeps the desk out of trouble.

## How does a patient create an ABHA, and should the clinic do it?

The honest answer for most clinics: let the patient create it, don't create it for them.

NHA's own description is that ABHA creation is fast, paperless, and hassle-free, done in about five minutes with no physical documents submitted anywhere. A patient can create one themselves on the ABHA app or at abha.abdm.gov.in using any of three routes:

- **Aadhaar OTP.** Enter the Aadhaar number, receive an OTP on the Aadhaar-linked mobile, verify. This is the most complete path because demographics pre-fill from Aadhaar.
- **Mobile number.** Create with just a mobile OTP plus basic details (name, year of birth, gender, address). This makes an ABHA that isn't Aadhaar-verified, which matters later for KYC-gated workflows.
- **Driving licence.** NHA has at times offered driving-licence-based creation as an alternative; availability varies, so confirm it's live on the portal before relying on it.

Two reasons the desk shouldn't be the one clicking. First, an ABHA made on the patient's own phone stays in the patient's control, with their consent captured cleanly, which is the whole point of the account. Second, front-desk creation is how duplicates happen: staff make a new ABHA for a patient who already had one from a previous hospital or a government camp, and now that patient has two accounts and a split history. If a patient genuinely has none and wants help, the cleanest move is to walk them through creating it on their own phone rather than making it on a clinic device.

## What does the actual check-in flow look like, step by step?

Here is the sequence a busy Indian OPD desk runs, from the patient walking up to the record being ready to link.

**Step 1, ask, don't assume.** "Do you have an ABHA?" Three outcomes: they have the number, they have the `name@abdm` address, or they have neither. Sort into those three buckets before anything else.

**Step 2, for a patient who has one, use Scan and Share.** Display your facility's ABDM QR at the desk. The patient opens their ABHA or PHR app, scans, and shares their profile. Their demographics, name, gender, date of birth, mobile, ABHA address, and ABHA number if linked, land in your registration screen and generate the OPD token. NHA built Scan and Share specifically to cut the registration queue, and it runs on the patient's implied consent at the point they choose to scan and share.

**Step 3, for a patient with only the address or number, verify identity.** If they read out a 14-digit number or a `name@abdm` handle instead of scanning, confirm the name and date of birth on screen match the person standing there. This one check prevents attaching a visit to the wrong ABHA, which is painful to unwind.

**Step 4, for a patient with no ABHA, offer, don't force.** Enrolment is voluntary. If they want one, guide them to create it on their own phone via Aadhaar or mobile OTP. If they decline, register them the normal way. A patient without an ABHA still gets seen; they just don't get a linked record today.

**Step 5, see the patient and document the visit.** The clinical encounter happens as usual. What the desk needs on the other side is a clean, structured record of that visit, because that record is what gets linked.

**Step 6, link the record, with the right consent.** The visit note is tagged to the patient's ABHA through your ABDM-certified system. Demographic sharing at registration was implied consent; sharing the actual clinical record across facilities is a separate, explicit consent the patient grants in their PHR app.

## What does linking a record to ABHA actually mean?

It is quieter than it sounds, and knowing that keeps staff honest with patients.

Linking tags the visit record generated at your clinic to the patient's ABHA so it can be located and, with consent, shared through the ABDM network later. The record still lives in your clinic's system. Linking creates a pointer, so the patient can assemble their history across the hospitals, labs, and clinics they visit. It does not, by default, dump the whole chart onto a government server the moment you link.

The consent structure is the part to get right. Per the PIB explainer on ABHA, records are not shared with a doctor or facility without the user's consent, and that consent is granular: the patient can approve sharing only selected records, set how long the approval lasts, and revoke it at any time from their app. So there are really two consent moments at a clinic. The implied consent when a patient scans and shares demographics to register. And the explicit, revocable consent when clinical records move between providers. Treating the first as permission for the second is the compliance mistake to avoid, and it lines up with how the [DPDP Act 2023 expects clinics to handle patient data](/in/blog/dpdp-act-clinics-guide/): purpose-limited, consent-first.

## Where does HFR registration fit into any of this?

You can't scan-and-share into a facility that isn't a recognised node.

To display a facility QR and act as a participant in ABDM workflows, your clinic has to be registered on the **Health Facility Registry (HFR)** at facility.abdm.gov.in, and the treating doctor on the Healthcare Professionals Registry. That registration is what makes your clinic a real node the patient's app can share to, and it is the same on-ramp behind DHIS incentive eligibility. No HFR, no facility QR, no clean linking. If your clinic isn't registered yet, the [step-by-step HPR and HFR registration guide](/in/blog/hpr-registration-guide-doctors/) walks both portals, and the [honest breakdown of what ABDM's DHIS actually pays a clinic](/in/blog/abdm-incentives-for-doctors/) sets expectations on the money side before you build a workflow around it.

Getting registered is the setup cost. The recurring work, the part that decides whether linking is smooth or a daily headache, is producing a clean, structured record for every visit that is actually ready to link.

## What are the front-desk pitfalls that cause bad records?

Most ABHA problems at a clinic are not technical failures. They are small process slips at the desk that surface weeks later as orphaned or mismatched records.

The duplicate ABHA is the big one. Staff create a new account for a patient who already had one, and now the patient has two ABHA numbers with history split across them. Always ask first, and prefer verifying an existing account over minting a new one.

Consent confusion is the compliance one. A patient scanning to register is not the same as a patient agreeing to share their clinical history with another provider. Keep the two separate in staff training, because conflating them is exactly the kind of thing a DPDP-era audit would flag.

Manual keying errors are the boring but common one. Typing a 14-digit number by hand invites transposed digits, which attaches the visit to the wrong or a non-existent ABHA. Scan and Share exists partly to remove this. Use it whenever the patient has the app.

Identity mismatch is the quiet one. Not confirming that the name and date of birth on the ABHA match the person at the desk means a family member's account, or a stale profile, gets the visit. Thirty seconds of verification saves a support ticket later.

## Where does an AI scribe fit, and what won't we claim?

At the record, right before it gets linked, and nowhere near the ABHA itself. We'll be precise about that boundary.

The AI Medical Scribe by Patient Square is the ambient scribe module inside Practice Copilot. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. In a clinic running code-mixed Hindi and English, it captures the conversation and the note still comes out in clean clinical English. That clean, structured note is precisely the record a clinic wants when it goes to link a visit to ABHA, because you cannot link a record that was never written down properly. The ICD-10 output is suggestions and the prescription is a draft; the clinician reviews and signs everything before it becomes part of the record.

Here is the line we hold. **ABDM integration is on our roadmap, not live today.** We do not create ABHA numbers, we do not link records to ABHA from inside the tool, and we have not completed ABDM milestone certification (M1/M2/M3). We never call ourselves ABDM-compliant or ABDM-ready, because we aren't. If linking records to ABHA from inside your software is a requirement right now, a vendor with live ABDM integration across the milestones is the honest pick, and we'd say so. What we do is make the per-visit documentation clean enough to feed whatever ABDM-certified system your clinic runs the linking through.

On data discipline, because a DPDP-era clinic will ask: visit audio is processed in memory and discarded once the note drafts, so there is no audio archive. Notes are in English, encrypted in transit (TLS 1.2+) and at rest (AES-256), access is role-scoped and logged, and the notes belong to your practice to export or delete anytime. We handle data to DPDP Act 2023 standards, and a SOC 2 Type II audit is underway. How we handle [data residency for an India clinic](/in/blog/ai-scribe-data-residency-india/) is covered separately, and the full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing is per clinician and ex-GST, from ₹1,599 a month on the annual Assist plan plus 18% GST (about ₹1,887 all-in), with a 7-day free trial; the [current tiers are on the pricing page](../../pricing/). If you're setting up an ABDM-ready front desk and want the record-keeping half to be the easy part, <a href="/in/how-it-works/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and bring one real visit. The test is simple: is the note that comes out clean enough to link without cleanup?

---

## Commure Scribe Alternatives: Per-Seat Costs for Group Practices
https://patientsquare.com/us/blog/commure-scribe-alternatives/
Published 2026-01-05 · Updated 2026-07-22 · Tags: ai-scribe, comparison, commure, pricing

Compare Commure Scribe costs for 5-to-50-clinician groups, when its enterprise tier fits, and when published per-seat pricing is a better procurement match.

For a single clinician on self-serve, Commure's published pricing page lists $89 a month billed monthly, or $59 a month billed annually (the annual ScribePro plan shows as $708 a year, down from $1,068). For medium and large group practices, per Commure's pricing blog fetched July 2026, pricing is custom and not published, and it adds write-back EHR integration, custom workflows, live onboarding, and ROI analytics. So a group's real per-seat number depends on a quote, not the sticker.

Commure Scribe advertises a price a solo clinician can read off the page. A group practice cannot. The self-serve tier lists $89 a month billed monthly or $59 billed annually, per Commure's published pricing page fetched July 2026. But the moment you have 5 to 50 providers and you want notes written back into the chart, you leave that band and land in a custom quote, and the number that decides your budget stops being public.

This page is for the person doing that procurement. What Commure genuinely does well, what the per-seat math looks like once you scale it across a roster, where the enterprise tier earns its price, and where a standalone scribe with a published rate fits a small group better. No takedown. Commure is a strong product with real KLAS marks. The question is fit for your specific group.

> **Key takeaways**
>
> - Commure's self-serve list price is $89/mo (monthly) or $59/mo (annual) per clinician, per its published pricing page fetched July 2026. Group and enterprise pricing is custom and not published.
> - EHR write-back and the deeper coding workflow sit in Commure's custom-priced Enterprise tier; suggested ICD/CPT codes appear at the entry tier.
> - For a group that will not use automatic write-back, the enterprise premium buys plumbing you leave idle.
> - A standalone scribe with a published per-seat rate removes the quote step and the renewal surprise. You copy the note into the chart yourself.
> - Commure is the better call when write-back and coding depth across 20-plus providers on a supported EHR are hard requirements.

## What is Commure Scribe actually good at?

Commure Scribe is an ambient AI scribe with real scale behind it. Per Commure's own material, it is used across a large clinician base and tens of millions of encounters, supports many languages, records long sessions, and works across in-person and telehealth visits. It generates suggested ICD-10 and CPT codes, and it integrates with a broad set of EHRs. In a 2025 KLAS First Look report, Commure Ambient AI scored 93.3, and 100% of the customers surveyed said they would buy it again, with high marks for reducing documentation time and improving collection rates.

That is an enterprise product doing enterprise things well. A group CMIO standing up ambient documentation across 40 providers, wiring notes back into the chart and codes into the billing workflow, should have Commure on the shortlist. Nothing below argues otherwise.

The question is whether your group needs that depth, or whether you are about to pay for it and leave most of it unused. If you want to see a finished note in two minutes without opening a sales cycle, you can book a demo first and decide after.

## What does Commure Scribe cost a group, not a solo doctor?

Here is the friction for a group buyer. The published number is a solo number.

Commure's pricing page (fetched July 2026) lists a self-serve ScribePro plan at $89 a month billed monthly, or $59 a month billed annually, shown as $708 a year down from $1,068. Suggested ICD/CPT codes are included at that tier. That is a clean, honest self-serve price, and it is genuinely competitive for one clinician.

But the same page puts note sync directly with your EHR, desktop or web, under a separate Enterprise tier priced as "Custom." Commure's pricing blog is explicit that medium and large group practices get custom pricing that bundles write-back EHR integration, custom AI workflows, live onboarding, and ROI analytics. So the moment a group wants the feature most groups actually buy an ambient scribe for, which is the note landing in the chart without a copy-paste, the price leaves the published band and becomes a quote.

That is normal enterprise behavior, and it tells you what buying will feel like. Your per-seat number tracks your size, your EHR mix, and your integration scope, and you learn it on a call. For a five-provider group that does not need write-back, that call is friction you may not need at all.

## What does the per-seat math look like across a 10-provider group?

Run the arithmetic Commure's custom tier hides. Take a 10-clinician group, each seeing 20 patients a day, 20 days a month. That is 4,000 visits a month across the group, 48,000 a year.

| | Commure self-serve, annual list | Our Assist plan, annual |
|---|---|---|
| Per clinician, per month | $59 | $79 |
| Per clinician, per year | $708 | $948 |
| 10 clinicians, per year | $7,080 | $9,480 |
| Cost per visit (group) | ~$0.15 | ~$0.20 |

Read that table honestly, because it cuts against us at the sticker level. On self-serve list pricing alone, Commure's $59 annual seat is cheaper per clinician than our $79 Assist seat. If your group can live entirely inside Commure's self-serve tier, with every provider copying the note into the chart by hand and no write-back, Commure is the lower line item. We are not going to pretend otherwise.

The table shifts the moment your group wants write-back. That feature moves Commure into the custom Enterprise tier, and the custom tier's per-seat number is not public. A group could end up paying more than either published rate once integration, onboarding, and ROI analytics are priced in. You cannot model that from the site, which is the point. The comparison that matters is not $59 versus $79. It is a published per-seat price you can budget today against a quote you have to negotiate for the feature you came for. For the wider self-serve field, our [best AI medical scribes comparison](../best-ai-medical-scribes/) lays out the honest roundup, and [AI medical scribe pricing](../ai-medical-scribe-pricing/) walks the whole US price ladder.

## What do you give up by choosing a standalone scribe over Commure?

There is a real trade here, and naming it is how you avoid regret at renewal.

You give up automatic EHR write-back. Commure pushes the note into the chart as part of a group deployment. We do not. You copy the finished note into your EHR yourself. For a solo clinician or a small group that is a few seconds per visit. For a 40-provider system that copy-paste multiplied across thousands of visits is a workflow decision, not a footnote. Count your providers before you decide it is trivial.

You give up the deeper coding-and-revenue workflow. Commure's suggested ICD-10 and CPT codes feed into an enterprise revenue-cycle story. We offer ICD-10 suggestions to speed your coding, not a revenue-cycle platform. If codes flowing straight into your billing pipeline sit at the center of your evaluation, weigh that plainly.

What you keep is the part a small group uses every day. The AI Medical Scribe by Patient Square is an ambient scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. Notes come back in clinical English. Visit audio is processed in memory and discarded the moment the note drafts, so no recording is retained for anyone. A BAA is available to every US customer, group practices included, without an enterprise contract minimum. If your group is standing up its first scribe, [our small-clinic implementation guide](../ai-scribe-implementation-small-clinic/) covers the rollout without an integration team, and if you are also weighing the health-system incumbents, [Abridge alternatives](../abridge-alternatives/) covers that end of the market.

## When is Commure the right choice for your group?

It comes down to write-back, coding depth, and how many providers share the same EHR.

Choose Commure, or stay with it, if your group runs on an EHR it integrates with, you want notes written back into the chart automatically, you want suggested ICD-10 and CPT codes wired into your billing workflow, and you are deploying across enough providers that a custom contract and live onboarding pay for themselves. At 20, 30, 40 seats on a supported EHR, that integration is the value, and its KLAS marks say customers who bought it were glad they did. Trying to shave a per-seat price by dropping write-back at that scale would cost you more in manual charting than you would save.

Choose a standalone scribe if you are a 5-to-15-provider group that wants a clean note in about two minutes, a published per-seat price you can put in a budget without a quote, a BAA without an enterprise minimum, and an assisted trial with a documented start point, and whose providers will copy the note into the chart by hand without minding. That describes a large share of independent group practices.

The split is about EHR depth and group size, not note quality. Both tools draft good notes. Commure assumes your group has, or wants, an integration project. We assume you would rather not run one.

## How should a group admin decide in two weeks?

Skip the feature grid. Run the procurement test that actually predicts your bill.

1. Decide whether automatic EHR write-back is a hard requirement. If "the note lands in the chart without a copy-paste" is non-negotiable across your roster, you are shopping the enterprise tier, and Commure belongs on the list.
2. If it is not, shortlist standalone scribes with a published per-seat price and documented trial setup, start, and cancellation terms.
3. Get the real number in writing. For any custom-quoted vendor, ask for the exact per-seat rate at your group size, not a starting price, and ask what it becomes in year two.
4. Settle the audio question with every vendor: stored or not, and for how long. Ours is never stored.
5. Trial on real visits across two or three of your busiest providers before you roll the whole roster. A scripted demo flatters every scribe equally.

The receipts behind our claims, encryption, access, and our SOC 2 work in progress, are on the [security page](../../security/), and the price ladder with no asterisks is on the [pricing page](../../pricing/). Book a short demo to see the note quality against your own visit types, then run the trial on a real clinic week. For most small groups, the honest finding is that the enterprise write-back tier is more than they need, and a standalone scribe at a published price does the job they actually have.

---

## Best EHR for Therapists (2026): An Honest Comparison
https://patientsquare.com/us/blog/best-ehr-for-therapists/
Published 2026-01-02 · Updated 2026-08-29 · Tags: comparison, behavioral-health, buying

SimplePractice vs TherapyNotes, compared on price, insurance billing, and the documentation burden that eats your evenings. Plus where a scribe fits.

There is no single best one; it splits on your payer mix. If most of your revenue is insurance, TherapyNotes tends to win on billing accuracy and ONC certification. If most is private pay, SimplePractice tends to win on workflow and its mobile app. Both publish prices and both handle the core therapy workflow well, so the deciding factor is usually billing and budget, not features.

There's no single best EHR for therapists. The real answer splits on one question: how much of your money comes from insurance. If you bill payers heavily, TherapyNotes usually wins on billing and certification. If you're mostly private pay, SimplePractice usually wins on workflow and its mobile app. This compares the field on the things that decide it: price, billing, and the documentation load. It also shows where Patient Square fits, either alongside the EHR you keep or with the bundled AI EHR available from Copilot.

> **Key takeaways**
>
> - The choice is mostly a billing decision: insurance-heavy leans TherapyNotes, private-pay leans SimplePractice.
> - Solo plans run roughly $49 to $99 a month, but the realistic all-in lands near $100 to $180 once telehealth, e-prescribing, and AI notes stack on.
> - SimplePractice is not ONC-certified; TherapyNotes is. That matters for interoperability incentive programs.
> - An EHR stores your note; a scribe writes the first draft. Many practices run both, and that's a feature, not a failure.

## How should a therapist actually choose an EHR?

Start with your payer mix, not the feature list. A practice where 70 percent of revenue runs through insurance has very different needs than a private-pay practice that never touches a claim.

For the insurance-heavy practice, billing accuracy and certification carry the decision. TherapyNotes is built around structured clinical documentation and claims, and it holds ONC certification, which puts it on the federal Certified Health IT Product List. SimplePractice is not on that list, which the EHR Source review notes "disqualifies practices from Promoting Interoperability incentive payments" and means the platform "has not been independently validated against federal interoperability and security standards." If those incentive programs or that validation matter to you, that's a real differentiator, not marketing.

For the private-pay practice, the daily experience matters more than claims plumbing. SimplePractice has one of the strongest mobile apps in behavioral-health software, with scheduling, notes, telehealth, messaging, and billing on iOS and Android. If you run your practice from your phone between sessions, that's worth real money.

## What do the leading therapist EHRs actually cost?

Here's the honest table. All figures pulled from each vendor's pricing page or published 2026 comparisons in June 2026; rates change, so confirm before you commit.

| Product | Solo monthly | Insurance billing in base | ONC certified | AI note add-on |
|---|---|---|---|---|
| **SimplePractice** | $49 Starter · ~$69 Essential · $99 Plus | Not in Starter | No | Note Taker ~$35/clinician |
| **TherapyNotes** | ~$59 solo (per 2026 comparisons) | Yes | Yes | AI documentation ~$40/clinician |

SimplePractice's $49 Starter is the lowest headline number, but it leaves out insurance billing and the telehealth most solo therapists need, so your real entry tier is Essential or Plus. SimplePractice also sells e-prescribing as a $49-a-month add-on with an $89 one-time setup fee, per its own pricing page. TherapyNotes folds more of the clinical and billing core into its base plan, which is why a like-for-like comparison usually narrows the headline gap.

## What about the documentation burden itself?

This is the part the EHR comparison usually skips, and it's the part that eats your evenings. The EHR is where the note lives. It is not, by itself, what writes the note. DAP notes, BIRP notes, treatment plans, progress notes: that's still you, typing, often after the last client leaves.

Both leading EHRs now sell an AI note-taker as an add-on, roughly $35 to $40 a clinician, because they know the documentation load is the real pain. That's a reasonable path if you want one vendor and one bill. The other path is a standalone scribe that drafts the note and works alongside whichever EHR you keep, so you're not locked into one vendor's note quality. Neither path is wrong; they're different trades. One bill versus the better draft.

## Where does an AI scribe fit, and what won't we claim?

Right at that documentation layer, and we'll be precise about the boundary. AI Medical Scribe by Patient Square is one module inside Practice Copilot: it listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For a therapist, assess that reviewed structured draft against the note format and clinical record requirements the practice already uses.

If you already run SimplePractice or TherapyNotes, Practice Copilot can work alongside that EHR. The scribe drafts the note; you keep the chart, scheduling, and billing system you chose. We do not claim a named-vendor integration or automatic write-back. Every plan includes **EHR-ready export (PDF · HL7 · FHIR)**. If you want Patient Square as the practice record system instead, the bundled AI EHR starts on Copilot. Audio is processed in memory and discarded once the note drafts, so there's no recording archive; the notes belong to your practice to export or delete anytime. We don't quote an accuracy percentage, because no honest vendor can. The useful test is whether the reviewed first draft stops the note from outlasting the session.

So the real stack for many therapists is an EHR for the system of record plus a scribe for the documentation, and you pick each on its own merits. If you want to see how that split plays out in your day, the [AI scribe for therapists](../ai-scribe-for-therapists/) page walks the DAP and BIRP workflow, and the [therapy notes templates](../therapy-notes-template/) guide covers when to stop templating and start drafting. Request your 7-day trial with the EHR you already use, or choose the Copilot plan if you want the bundled AI EHR. The [pricing page](../../pricing/) has the published rates.

---

## NABH Documentation: What Your Clinic Actually Has to Keep
https://patientsquare.com/in/blog/nabh-documentation-requirements/
Published 2026-01-02 · Tags: nabh, documentation, compliance, india

The medical-record and documentation requirements behind NABH accreditation, why documentation drives most assessment gaps, and how a clean note feeds it.

NABH expects documented policies and protocols across patient care, medication management, the consent process, patient safety, clinical outcomes, medical records, and infection control. At the clinical level that means complete, legible, retrievable patient records, documented consent, and tracked quality indicators. The exact objective elements depend on which programme and edition you pursue, but the spine is the same: if it is not documented, the assessor treats it as not done.

NABH accreditation is, more than anything, a documentation exam. The clinical work matters, but the assessor judges what's written down, and published assessment experience attributes most performance gaps to documentation, not to care. The National Accreditation Board for Hospitals and Healthcare Providers, a constituent board of the Quality Council of India, expects documented policies and complete, retrievable patient records across patient care, consent, medication, and medical records. This walks what that actually means for a clinic, and is general information, not accreditation consultancy; confirm specifics against the current NABH standards for your programme.

> **Key takeaways**
>
> - NABH judges the record: if a practice isn't documented, the assessor treats it as not done.
> - Published assessment experience puts the majority of performance gaps on documentation, not clinical failures.
> - The Entry-Level hospital programme is built around 10 chapters, 41 standards, and 149 objective elements; full accreditation is far larger.
> - Entry-Level certification is valid for two years, so documentation has to be a habit, not a pre-audit scramble.

## What does NABH actually want documented?

The board frames it as policies and protocols set to recognised standards across a defined set of areas: patient care, medication management, the consent process, patient safety, clinical outcomes, medical records, and infection control. That's the org-level view. At the level of a single patient encounter, it comes down to a few things being true on the page.

The clinical record has to be complete and legible: history, examination, diagnosis, plan, and progress, written so another clinician could pick up the chart. Consent has to be documented for the procedures and situations that require it, not just obtained verbally. Quality indicators have to be tracked, with adverse and sentinel events triggering documented root-cause analysis, and a patient-satisfaction programme with action plans on record. The recurring theme: NABH doesn't reward good intentions, it rewards a record that proves them.

## Why is documentation the gap that fails clinics?

Because the work usually happens and the record usually lags. A quality-improvement study of Indian private facilities pursuing accreditation found documentation issues accounted for the majority of identified performance gaps. Not infection control, not staffing, not clinical competence: the writing.

It plays out the same way again and again. A clinic gives solid care, but the note is thin, the consent for a procedure is undocumented, or a record can't be produced when the assessor asks for it. Each of those is an objective element scored against you, even though nothing went wrong clinically. The honest, slightly uncomfortable point: most NABH preparation is really documentation preparation in disguise. Fix the record-keeping habit and most of the gap closes.

## How is the standard structured, and how long does it last?

It depends on the programme, and this trips up clinics that assume one number. The NABH Entry-Level certification for hospitals, the on-ramp aimed at smaller facilities, is structured around 10 chapters, 41 standards, and 149 objective elements. Full hospital accreditation runs to many more standards and a deeper assessment. NABH also publishes separate Digital Health Standards covering interoperable, secure digital records, and it revises editions regularly, so the chapter and element counts shift between programmes and versions. Always check the current standards document for the exact programme you're pursuing rather than a summary.

On validity: Entry-Level certification lasts two years before re-assessment for renewal. That cycle is the quiet reason documentation can't be a pre-audit sprint. Assessors look at records across time, and a clinic that only writes clean notes in the month before an assessment leaves an obvious pattern. The discipline has to live in the daily visit.

## Where does the digital record fit?

This is the direction the whole system is moving. NABH's Digital Health Standards push toward secure, interoperable, accurate patient information, the same record discipline, expressed digitally. A clinic that already keeps complete structured records is most of the way there; one that relies on scattered paper has two problems to solve at once.

The practical lesson for a clinic that wants both NABH readiness and a future-proof record: the unit that matters is the per-visit clinical note. If every encounter produces a complete, structured, retrievable note, the accreditation documentation and the digital-health requirements both get easier, because they're built from the same raw material.

## Where does an AI scribe fit, and what won't we claim?

At that per-visit note, and nowhere near your accreditation programme. We'll be precise about the boundary, because this is exactly the kind of claim health vendors overreach on. **An AI scribe does not make you NABH-accredited, write your policies, or run your quality programme.** What it does is make the individual clinical record easier to keep complete, which is the layer where most NABH documentation gaps actually open.

The AI Medical Scribe by Patient Square, one module of Practice Copilot, captures the visit as it happens and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit. For a clinic chasing NABH readiness, that means each encounter ends with a structured note in clean English, drafted for you to check and sign, instead of a thin line scribbled between patients. In a busy OPD running code-mixed Hindi and English, it captures the conversation and the note still comes out in clean clinical English.

The rest of the line we hold. We're not ABDM-integrated; that's roadmap, not live, so we don't link records to ABHA from inside the tool and we never call ourselves ABDM-compliant. We don't store visit audio; it's processed in memory and discarded once the note drafts. Data is encrypted in transit and at rest, access is role-scoped and logged, and the notes belong to your practice to export or delete anytime. We handle data to DPDP Act 2023 standards, and a SOC 2 Type II audit is underway; the full posture is on our [security page](../../security/). This describes live consultation audio; uploaded recordings use a separate retention mode with explicit consent.

Pricing is published and ex-GST across three plans: Assist starts at ₹1,599 per clinician a month on annual billing (₹1,999 monthly), then Copilot and Autopilot add the bundled AI Copilot EHR, WhatsApp messaging, and higher-tier modules above it. Add 18% GST and Assist lands at about ₹1,887 a month all-in, with a 7-day free trial. For the wider record-keeping picture, the [NMC record-keeping guide](../nmc-record-keeping-ai-scribe/) covers what a defensible clinical record needs, and the [DPDP Act guide for clinics](../dpdp-act-clinics-guide/) covers the data-protection side NABH digital records also have to meet. Or <a href="/in/products/hospital-copilot/" data-ph-event="cta_click" data-ph-location="article_body" data-ph-action="learn_more">explore the workflow</a> and bring one real visit; the test is whether the note that comes out is one you'd be glad to show an assessor.