MedScrub runs as an embedded sidebar app inside the eClinicalWorks chart. Patient context — active problems, current medications, allergies, recent vitals — is provided by eClinicalWorks to the embedded panel, and MedScrub’s clinical skills operate on the loaded patient without an independent FHIR connection.
Integration model
MedScrub is loaded as an embedded panel inside the eClinicalWorks chart view. The host EHR supplies the active patient context; MedScrub does not pull or sync data from eClinicalWorks independently. PHI handled inside MedScrub still passes through the self-hosted de-identification proxy before reaching any large language model.
Capabilities
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.
Ask clinical questions grounded in the loaded patient’s data — differential diagnosis, drug interactions, evidence-based protocols.
On-demand summary of the active patient’s history, problems, and medications, generated when the chart is opened.
Per-patient HEDIS / USPSTF screening recommendations based on the chart data the EHR provides.
Drafts patient messages (pre-visit prep, post-visit follow-up, care-gap reminders) with clinical context from the loaded chart.
Data scope
Setup
01
The eClinicalWorks administrator configures MedScrub as an embedded application inside the chart workflow.
02
Each clinician signs into MedScrub from the embedded panel using their MedScrub account; the MedScrub session inherits the patient context from the EHR.
03
Clinicians configure their own LLM API key in the MedScrub settings; keys are stored locally and never sent to MedScrub-operated servers.
Tier limitations
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.