All EHR integrations
Embedded chart sidebar

Practice Fusion integration

MedScrub runs as an embedded sidebar app inside the Practice Fusion chart. Patient context is provided by Practice Fusion to the embedded panel, and MedScrub’s clinical skills operate on the loaded patient.

Integration model

How Practice Fusion and MedScrub connect

MedScrub is embedded inside the Practice Fusion chart view. Practice Fusion supplies the active patient context to the embedded panel; MedScrub does not independently pull or sync FHIR data. PHI handled inside MedScrub passes through the self-hosted de-identification proxy.

Capabilities

What MedScrub does with Practice Fusion

SOAP note generation

Drafts a structured SOAP note from the patient context handed in by the EHR. Physician reviews, edits, and signs before copying into the EHR or using the EHR’s native document import flow.

Chart-context chat

Ask clinical questions grounded in the loaded patient’s data — differential diagnosis, drug interactions, evidence-based protocols.

Pre-visit summary for the loaded patient

On-demand summary of the active patient’s history, problems, and medications, generated when the chart is opened.

Screening surface for the loaded patient

Per-patient HEDIS / USPSTF screening recommendations based on the chart data the EHR provides.

Patient messages and care-gap nudges

Drafts patient messages (pre-visit prep, post-visit follow-up, care-gap reminders) with clinical context from the loaded chart.

Data scope

Patient context provided by the host EHR

  • Active problem list
  • Current medications
  • Allergies and intolerances
  • Recent vitals
  • Patient demographics
  • Loaded encounter context

Setup

How a Practice Fusion customer onboards

01

Embedded app configuration

The Practice Fusion administrator configures MedScrub as an embedded application inside the chart workflow.

02

Account provisioning

Clinicians sign into MedScrub from the embedded panel; the session inherits the patient context from the EHR.

03

LLM key configuration

Clinicians configure their own LLM API key in the MedScrub settings.

Tier limitations

What requires the native FHIR tier

The embedded sidebar integration is the EHR vendor’s third-party app pattern. Some MedScrub workflows require deeper FHIR connectivity that this tier does not provide.

  • Population-level workflows require the native FHIR integration tier.
  • Automated EHR write-back at scale requires the native FHIR integration.
  • Longitudinal patient context across visits requires syncing into the MedScrub clinical data repository via native FHIR.

Ready to connect Practice Fusion?

MedScrub onboards Practice Fusion customers sales-led, with deployment engineering, EHR registration, and compliance review running in parallel. Most deployments are live in four to eight weeks.