MyChart supports eCheck-In tasks and configured questionnaires. Keep the work it already handles well. For visits that need a more connected symptom story, FaceMed.ai can ask adaptive follow-up questions about onset, changes, function, prior treatments and the patient’s goals.
The result is an editable HPI and relevant history for clinician review. It complements, rather than replaces, MyChart’s native forms or the clinical evaluation in Epic.
Two ways to plan the EHR handoff
One-click browser workflow
A reviewer verifies the draft and uses the FaceMed.ai One-click browser-extension workflow where supported. Demonstrate the actual Hyperspace or Hyperdrive browser, patient encounter and Epic note destination with your team before rollout.
Authorized EHR interface
Epic controls access at each customer organization. Explore SMART on FHIR R4, authorized Epic Bridges HL7v2 interfaces or other approved routes for the required use case. Epic Showroom (formerly App Orchard), Connection Hub and Toolbox are ecosystem terms, not proof of local authorization or certification of FaceMed.ai.
Start with the clinical value. A manual transfer of the reviewed draft remains a pilot fallback while the team confirms permissions, browser compatibility or connected interfaces. No fixed activation timeline or automatic two-way sync is promised.
What to map with your Epic / MyChart team
Bring one visit type, the clinical note template and the permissions your practice can actually authorize. The table is a planning guide, not a list of already activated interfaces.
Relevant platform concepts and the FaceMed.ai handoff to validate
Layer
Epic / MyChart context
Implementation check
Launch and review
Epic Hyperspace / Hyperdrive; MyChart eCheck-In
Review the pre-visit HPI and confirm the Epic user, patient and encounter
Optional appointment trigger
Epic Bridges HL7v2 scheduling events or FHIR R4 Appointment
Agree which event identifies the visit and who may send the intake link
Optional chart context
Permitted SMART on FHIR R4 patient, condition and medication resources
Request only the needed scopes; no prior-chart retrieval by default
Reviewed note destination
A locally approved Epic note, NoteWriter / SmartText workflow or document route
Validate content placement, editing, signature responsibility and failure handling
An illustrative clinical workflow
Orthopedics: a clearer knee-pain history before the Epic visit
A patient writes “knee pain—see notes” in a pre-visit form. FaceMed.ai can clarify injury timing, pain location, swelling, walking and stair limitations, previous imaging and physical therapy. The orthopedic clinician reviews the chronology before evaluating movement and deciding the plan.
For a health-system pilot, confirm the business associate agreement and data processing terms, minimum necessary access, secure transport and storage, role-based review, patient and encounter matching, audit requirements and a correction/fallback process. Epic customers approve their own app deployments.
The patient’s conversation creates an editable history draft. A clinician verifies it, determines clinical relevance, manages urgent findings under practice protocols and approves chart use.
Questions Epic / MyChart teams ask
Do we need Epic Showroom activation before evaluating FaceMed.ai?
Not necessarily for an initial clinical-history evaluation. A practice can assess the conversation and reviewed output first. Any browser-extension handoff must be demonstrated in its actual Epic environment; an API connection needs the health system’s authorization, testing and deployment approval.
How is FaceMed.ai different from MyChart questionnaires?
MyChart can collect useful pre-visit information through eCheck-In and configured questionnaires. FaceMed.ai adds an adaptive video conversation for narrative timelines and follow-up questions. The clinician reviews the resulting history, rather than treating it as an automatically verified Epic record.
Where does the reviewed history appear in Epic?
That is selected during implementation. The team validates whether an encounter note, a NoteWriter or SmartText workflow, or a document destination is appropriate and permitted for its Epic configuration. The clinician remains responsible for review and signing.
Bring us your Epic / MyChart workflow
Show one appointment type and a sample note. We can demonstrate the patient conversation and clinician-reviewed output, then plan the right handoff with your clinical and technical teams.
Vendor references explain available platform features; they do not establish a FaceMed.ai certification, partnership or pre-enabled native connector. Each practice confirms its specific interface and permissions.