Statutory Compliance Architecture for Ohio Medical Board
Documenting clinical encounters under Ohio licensure means the physician is the legal author of every entry. The software is not. The State Medical Board of Ohio disciplines licensees under ORC 4731.22(B)(5) for false or misleading statements in relation to the practice of medicine. It also disciplines under ORC 4731.22(B)(6) for departures from minimal standards of care. An ambient draft that enters the chart unreviewed exposes the internist to both grounds at once.
Ohio has not yet enacted an ambient-documentation statute comparable to California AB 3030. That law requires disclaimers on AI-generated patient communications and treats content differently once a licensed provider has reviewed it. Without a direct Ohio analogue, the Board applies its existing record-integrity and standard-of-care provisions. Those provisions already presume human authorship.
Physician Attestation Under ORC 4731.22
The attestation sequence is fixed: draft, review, edit, attest, sign. Merry AI enforces this order at the interface layer. Each injected draft carries a visible unsigned-draft banner that identifies the encounter. The physician must confirm review before using the EHR's native signature control. Electronic signatures carry legal effect under ORC 1306.06, so the signature must represent genuine physician verification rather than a pass-through of machine text.
CMS signature requirements reinforce this. Medicare Program Integrity Manual Chapter 3, §3.3.2.4 requires that services be authenticated by the ordering or rendering practitioner. A signature applied by automation, or applied without review, authenticates nothing. It creates an audit finding instead.
Draft Injection Controls and the Auto-Sign Prohibition
Merry AI writes plain, editable text into the existing note field through Chrome DOM APIs. It targets textarea, input, or contenteditable elements by stable selectors. It never applies signatures, orders, diagnoses, or billing codes. Before writing, the extension checks for readonly or disabled attributes. If the note is signed or locked, injection is refused. This prevents post-signature alteration that would compromise record integrity under ORC 4731.22(B)(6).
Iframe and Multi-Tab Patient Binding
Internal medicine workflows rarely stay in one pane. Web EHRs often nest the note editor inside iframes or shadow DOM components. Internists frequently keep lab results, prior notes, and a second encounter open at the same time. Merry AI binds each draft to a specific patient identifier, encounter identifier, and note type. It refuses injection when the foreground context does not match. This keeps one patient's assessment out of another patient's chart and keeps an office-visit note out of a telephone encounter.
Ephemeral Audio and ORC 2933.52
Ohio permits one-party consent recording under ORC 2933.52(B), but lawful capture does not justify retention. Merry AI buffers encounter audio in RAM for real-time transcription and then discards it. No audio is written to disk, localStorage, IndexedDB, or vendor storage. This narrows the exposure surface under 45 CFR 164.312 and simplifies breach analysis under ORC Chapter 1354. Practices should still disclose ambient capture to patients as a matter of trust.
CMS 2026 Coding Integrity for Internal Medicine
G2211 rewards genuine longitudinal management, not phrasing. For 2026, the add-on attaches to office/outpatient codes 99202–99205 and 99211–99215. It now also attaches to home or residence codes 99341, 99342, 99344, 99345, and 99347–99350. CMS denies G2211 when the base visit carries modifier 25. The exceptions are same-day annual wellness visits, vaccine administration, and qualifying Part B preventive services. Merry AI never suggests G2211 and never inserts generic complexity language.
Modifier 25 and 59 decisions remain physician judgments. Modifier 25 requires a significant, separately identifiable E/M service. Modifier 59 and the X-series modifiers apply to non-E/M procedure pairs flagged by NCCI. The draft contains no hidden tags that downstream billing engines could read as modifier triggers.
| Compliance Dimension | Manual Charting | Standard Generic AI Scribes | Merry AI Compliance Architecture |
|---|---|---|---|
| Authorship (ORC 4731.22) | Physician-authored | Vendor-drafted note, often finalized outside the editor | Draft injected into editable field; physician edits and attests |
| Auto-Sign Exposure | None | Present when completed notes are pushed via API | Blocked; readonly and signed fields refused |
| Audio Retention | None | Cloud storage for QA or model training | RAM-only; discarded after transcription |
| G2211 / Modifier Logic | Physician-selected | Suggested or auto-flagged | Never suggested; physician-determined |
| Specialty Criteria | As documented | Inferred staging possible | Spoken values only |
| Wrong-Chart Risk | Low | Import mismatch possible | Patient and encounter binding enforced |
This comparison reflects architectural defaults, not individual vendor contracts. Practices should verify retention terms in each executed BAA.
Specialty Criteria Fidelity and Audit Readiness
Internal medicine notes routinely carry structured criteria. Examples include NYHA class and LVEF, KDIGO CKD stages, GOLD COPD classification, A1c trends, and DSM-5-TR specifiers for comorbid depression. Merry AI reproduces only the values the physician speaks. It does not upstage NYHA class II to III, infer an LVEF, or assign a DSM-5-TR specifier from narrative tone. Discrete fields linked to echo reports and lab feeds remain the source of truth.
Peer-reviewed informatics literature supports this separation of structured data from narrative text. The AMDIS consensus on EHR documentation and related work are indexed at https://www.ncbi.nlm.nih.gov/pmc/. Copy-forward and unverified template text remain leading sources of documentation error.
Prepare an audit binder containing four items: architecture diagrams of audio flow, evidence that telemetry excludes raw audio and identifiable transcripts, the executed BAA, and EHR audit logs. Those logs should show physician edits preceding each signature timestamp, consistent with 45 CFR 164.312(b).
Practices preparing for Board inquiry or payer review can Schedule a 15-Minute Workflow Audit to map their current attestation sequence against these controls.
