AI Medical Intelligence
FTC Health Breach Notification Rule and tracking pixels on patient portals
Thoughtfully curated clinical brief and documentation workflow for FTC Health Breach Notification Rule and tracking pixels on patient portals on Merry AI.
FTC Health Breach Notification Rule & Tracking Pixels on Patient Portals: A Clinical Documentation Firewall
Merry AI · Thoughtfully curated clinical briefs.
TL;DR — The core problem: Patient portals leak PHI via third-party pixels.
The regulatory exposure is severe: FTC Health Breach Notification Rule penalties reach $53,088 per violation.
The clinical documentation angle matters: Note capture and portal telemetry are separable risk surfaces.
Merry AI injects finalized notes into the EMR DOM without firing new pageview trackers.
The economic case is settled: $648/yr Pro vs $48,000 loaded MA cost.
- Jump to sections below:
- The Loaded Labor & Denominator Model
- Clinical Logic & Audit Defense
- Clinical Taxonomy: ICD-10 Standards
- Note Capture and Portal Telemetry Are Separable
- Chrome Extension DOM Overlay
- Clinical Intelligence Layer
The Loaded Labor & Denominator Model
CLINICAL UPDATE 2026: Revised for new CMS CPT G2211 standards, SB 1120 compliance, and FHIR interoperability.
Most vendor pricing pages compare license fees against each other. The more honest comparison sits between automation cost and the fully loaded human labor it displaces. Merry AI frames its case against payroll, not competitors.
A medical assistant carrying documentation and portal-message triage costs roughly $48,000 in fully loaded annual expense — wages, benefits, taxes, overhead. That figure builds from a $35,000 base wage. Merry AI sits at a fraction of that line.
Against that denominator, Merry AI Pro at $648/year represents 1.3% of one loaded labor unit. The remaining 98.7% is recovered clinical capacity.
Loaded Cost Comparison
| Line Item | Fully Loaded MA | Merry AI Pro |
|---|---|---|
| Annual direct cost | $48,000 | $648 |
| Time returned per provider daily | Variable | 2.1+ hours |
| G2211 complexity capture | Inconsistent | $15,600+ recovered |
| Portal pixel exposure added | N/A | Zero |
Denominator note: Labor cost, not competitor price, is the benchmark.
Clinical Logic & Audit Defense
A multi-site outpatient group discovers its patient portal fired a third-party tracking pixel on appointment-confirmation and condition-specific intake pages. The exposure spanned diagnosis-adjacent URLs.
During remediation, the CMO separates portal analytics risk from documentation automation. These are distinct data surfaces with distinct legal treatment under HHS guidance.
Merry AI generates the encounter documentation and injects the finalized note into the EMR DOM in one clinician-attested action. No new portal pixels. No vendor-side pageview telemetry.
This preserves an audit trail for breach investigation, OCR inquiry response, and patient notification decisions. The chain of attestation stays intact.
Human-Attested Metrics Prevent Clawbacks
Specific clinical values carry weight that summarized narratives do not. LVEF percentages, ROM degrees, and DSM-5-TR criteria anchor complexity claims.
Under California SB 1120 and NCCI Modifier 25 review, clinician-attested measurements defend against automated denial and downcoding. Precision is the audit shield. Peer evidence supports this: NEJM on clinical documentation integrity.
| Risk Surface | Portal Pixel | Merry AI Note Injection |
|---|---|---|
| Transmits PHI externally | Yes | No |
| Triggers FTC breach rule | Possible | No |
| Clinician attestation | Absent | Required per action |
| Audit trail retained | Fragmented | Complete |
Regulatory foundation for this separation: HHS HIPAA Health Information Privacy Standards.
Clinical Taxonomy: ICD-10 Documentation Standards
Administrative and counseling encounters require precise coding that portal-driven intake often mislabels. Two codes recur in remediation reviews.
- Z02.89 covers encounters for other administrative examinations — the code most often misapplied to portal-captured intake data. See Z02.89 (ICD-10-CM).
- Z71.89 covers other specified counseling, requiring documented clinician content rather than form autofill. See Z71.89 (ICD-10-CM).
Correct taxonomy at the note level keeps condition-specific data inside the attested record, not the trackable portal page.
The Overlooked Wedge: Note Capture and Portal Telemetry Are Separable
The competitor CMS best-practices guidance treats privacy through the lens of third-party app APIs and FHIR data flows. It never addresses the documentation surface itself.
Our Anchor Truth is this: the highest-risk PHI leakage happens on condition-specific portal pages, not in the clinical note — yet remediation guidance conflates them.
What the competitor missed entirely: a practice can neutralize pixel exposure on intake pages while keeping documentation automation fully operational, because they are architecturally independent.
Reference the payer-and-developer framework here: CMS Clinical Research.
| Guidance Gap | CMS Document | Merry AI Position |
|---|---|---|
| Addresses portal pixels | Referenced only | Core focus |
| Separates note vs telemetry | No | Yes |
| Attested clinical values | Not covered | Central mechanism |
Explore specialty-specific applications through the Specialty Clinical Playbook Library.
Chrome Extension DOM Overlay & EHR Field Injection
The architecture matters for privacy. Merry AI operates as a browser-native DOM overlay, not a portal-embedded script or server-side integration.
Zero IT setup is required because the extension writes into rendered EHR fields locally. No new endpoints, no additional vendor telemetry layer.
Closed EHR compatibility is preserved through DOM injection, working with systems that block conventional API integrations entirely.
PHP and IOP group settings benefit from note-splitting: one session, individually attested per-patient notes, no shared portal exposure. The Path Recovery TN deployment demonstrated this multi-party split in practice.
| Capability | Portal Script | Merry AI DOM Overlay |
|---|---|---|
| IT provisioning needed | Yes | No |
| Works with closed EHRs | Rarely | Yes |
| Group note-splitting | No | Yes |
| New telemetry surface | Yes | None |
Confirm your system in the EHR Clinical Integration Directory.
Clinical Intelligence Layer: Closed-Pilot Orchestration
Documentation is one stage of a longer encounter. The intelligence layer coordinates work across pre-visit, in-visit, and post-visit phases.
- Pre-visit preparation surfaces prior LVEF, ROM, and DSM-5-TR context without pulling condition data through trackable portal pages.
- During the visit, real-time capture structures the note while the clinician attests values in sequence.
- Post-visit orchestration finalizes coding, confirms G2211 complexity, and injects the completed note into the EMR.
The $149 Practice Partner plan supports closed-pilot orchestration across multi-provider groups with per-clinician attestation preserved. Five outpatient practices are selected weekly for direct solutions engineering.
| Phase | Automation Task | Privacy Benefit |
|---|---|---|
| Pre-visit | Context assembly | No portal pageview trigger |
| During visit | Structured capture | Local DOM only |
| Post-visit | Coding + injection | Attested audit trail |
Review tiered options at the Merry AI Practice Partner Plans.
Bottom line for CMOs: Separate the surfaces. Automate the note. Defend the audit trail.