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:
- Which file or message types can this product accept for a clinical note?
- Which versions, profiles, resources, and fields are supported?
- How are the patient, encounter, author, and signer matched?
- Where does imported text appear in the chart?
- What happens when a required field is missing or invalid?
- Does an import create an audit event and a visible error report?
- 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 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, Start your 7-day free trial. Use test data first, involve the EHR vendor, and make the acceptance checklist part of the buying decision.