A patient has told their story. The clinician still needs to know which appointment it belongs to, what has been checked and where the reviewed note will appear. Those details determine whether intake saves work or creates another inbox to manage.
FaceMed.ai gathers the clinical history before the visit through an adaptive video conversation. It prepares a structured draft in your preferred format. Your team reviews and corrects that draft, then uses the agreed route to place the history in the clinical record.
The patient completes your configured questions before the appointment, with follow-ups that clarify their account.
02 · Review
Check what matters
The clinician checks the draft, corrects details and marks what still needs discussion or verification.
03 · Deliver
Use the agreed destination
Transfer the reviewed history through your chosen workflow, keeping the patient, appointment and note status clear.
Connected EHR integration: plan the data flow
Choose the authorized interface for your clinic’s chart and encounter process. FaceMed.ai prepares clinician-reviewed histories in the format you need; the practice and EHR team agree which records can be accessed, which note or document type receives the approved content, and how delivery is confirmed.
FHIR, HL7 or an EHR-specific API
FaceMed.ai can produce FHIR-formatted output. Each EHR has different interfaces and permissions: some enable record access, some support approved note or document delivery, and some require additional vendor or customer review.
Validate the clinical chart handoff
Confirm patient and encounter matching, reviewer approval, note placement, supported write operations, failure handling and the audit trail. Start with one visit type and a reviewed sample note.
Separate option — One-click browser transfer: A clinician may move an approved history through the FaceMed.ai browser-extension workflow where it has been tested for that environment. This does not require or imply an activated native API connector. See how the delivery options fit the product workflow.
A specialty clinic · First consultation
What a useful handoff looks like in practice
A new patient completes the clinical-history conversation before their consultation. They describe their main concern, previous care and current medications. One medication name is unclear, and a detail about earlier treatment needs confirmation.
Before the appointment
A named reviewer checks the draft. The uncertain medicine remains labelled for verification, and the earlier treatment becomes a question for the visit. The reviewer confirms that the history belongs to the scheduled patient and appointment.
At the chart handoff
The reviewer may use the One-click browser extension for the approved note, or the team may use a configured FHIR/HL7 connection after validation. Staff verify the patient, destination and completion; manual transfer remains a fallback if delivery fails.
The result is a starting point for the consultation: an organized history and visible gaps. It is not an automatically signed clinical assessment. The treating clinician confirms the account and makes the care decisions.
Bring the EHR your practice already uses
Keep the EHR your practice already uses. FaceMed.ai will work with your team to design and implement a suitable handoff for clinician-reviewed clinical history, including for EHRs not listed here. Depending on your setup, that may use our One-click browser extension, an approved FHIR/HL7 interface or another agreed transfer workflow.
This list is illustrative, not exhaustive. If your EHR isn't shown, tell us which platform you use. We'll scope the integration around your practice's note destination, permissions, configuration and approvals before activating it.
EHR-specific clinical history and note handoff
Epic and MyChart
MyChart eCheck-In handles patient-facing tasks and questionnaires. FaceMed.ai adds an adaptive pre-visit clinical history for clinician review. Discuss the Epic note destination, patient and encounter matching, and the extension or authorized FHIR/HL7 path.
Enhanced Self Check-In supports administrative and clinical check-in. FaceMed.ai focuses on the more detailed narrative history, reviewed before an athenaOne handoff. Check the encounter note template, reviewer role and approved transfer method.
For Oracle Health Millennium environments, identify the relevant clinical document or note destination and which FHIR APIs, HL7 interfaces and authorizations are available. Confirm the workflow with the health system before assuming direct delivery.
Identify whether your practice uses EMA/ModMed PM or another ModMed platform. The available API and document workflows differ by product, so agree note placement, permissions and any synapSYS review before a production integration. Explore the ModMed One-click transfer and interface guide.
Veradigm EHR
Start with the specific Veradigm product and your preferred clinical note format. Determine whether a One-click user-reviewed transfer or a separately approved interface fits your practice's EHR configuration.
Keep healow portal tasks and use an adaptive pre-visit interview where the visit needs more context. Validate a reviewed note transfer, and distinguish patient-facing healow FHIR access from provider-facing eClinicalWorks interfaces. Explore the eClinicalWorks guide.
Use Healthie Forms and Onboarding Flows for configured intake. When a patient needs adaptive follow-ups, prepare a reviewed history and evaluate the Healthie GraphQL API or a validated browser workflow. Explore the Healthie guide.
Another EHR?
These examples are not the limit of the EHRs we can support. Bring your system, visit type, note destination and access requirements, and plan the appropriate handoff.
A named EHR is not a guarantee of native certification, one-click compatibility in every environment or automatic data write-back. We demonstrate and validate the chosen method with your team before deployment.
Does FaceMed.ai work with my EHR?
Explore a few common EHR environments below. This is not an exhaustive EHR list, and a named platform does not imply that a native connection is already enabled for every practice. FaceMed.ai prepares the clinical history before the visit; the reviewed note follows the handoff your practice agrees and validates.
How does FaceMed.ai fit alongside Epic and MyChart?
MyChart can handle the portal and eCheck-In steps. FaceMed.ai gathers the deeper pre-visit clinical story for clinician review. The Epic handoff is planned around the correct patient, encounter and note destination, using a validated One-click browser workflow or an authorized interface as appropriate.
How does FaceMed.ai fit alongside athenahealth and athenaOne?
athenaOne remains the clinical record, while FaceMed.ai prepares a structured patient-reported history ahead of the visit. Your team reviews the draft and confirms the template, chart permissions and agreed transfer approach before enabling it in practice.
Start with the exact ModMed product and specialty workflow. EMA/ModMed PM and gGastro/gPM do not have interchangeable interface requirements, so review the clinical note format, reviewer approval and available transfer route with the practice before rollout.
What if our clinic uses Oracle Health, Veradigm or another EHR?
These are examples of EHR environments where an implementation conversation can start. FaceMed.ai offers FHIR-formatted output and a One-click browser-extension workflow, while exact browser compatibility, permissions, FHIR/HL7 connections and chart placement must be validated for your EHR configuration.
Our EHR is not listed. Can we still integrate FaceMed.ai?
Yes. We work with practices using EHRs beyond the examples shown. Tell us your exact EHR product, one visit type and your preferred approved-note format. We'll plan the integration with your team, then configure and validate the appropriate One-click browser, FHIR/HL7 or other agreed handoff for your environment.
Keep portal questionnaires, clinical intake and scribes in context.
Your portal may already collect useful history, use conditional questions or support registration and consent. Review what it gathers well and where clinicians still need to ask for a fuller account. The value of a pre-visit conversation is in the history it clarifies for your team.
An ambient scribe documents the conversation during the encounter. Pre-visit clinical history-taking gathers the patient’s account beforehand. These workflows can sit alongside one another; decide where each belongs so patients do not repeat the same work unnecessarily. Compare the workflow categories.
Confirm these details before the first patient.
A practical handoff checklist
Decision
What your team should agree
Patient and visit matching
How the history is associated with the correct patient and appointment, and how staff handle ambiguous matches.
Review responsibility
Who checks the draft, when review happens and how corrections or unresolved questions are recorded.
Note format and destination
The sections clinicians need and the place reviewed content belongs in the chart.
Access and approvals
The permissions, EHR-side configuration and organizational approvals required for the agreed data flow.
Data handling
The relevant agreements, access controls, retention and deployment-specific compliance requirements. Read our privacy information.
Failure and fallback
Who checks delivery, handles duplicates or failures and completes the handoff when the normal route is unavailable.
Measure the whole workflow—not just a successful transfer.
Begin with one clinician, a defined visit type and a clear baseline. Include the time spent reviewing, correcting, supporting patients and entering notes when you compare the new process with your current one.
History ready before review
Track how often patients finish in time for the team’s planned review window.
Review and correction effort
Measure the work required to make the draft useful, including information that needs verification.
Reliable chart delivery
Check the correct patient, destination and note status, plus failed or duplicate handoffs.
Usable time recovered
Compare the full pathway and ask clinicians whether the history improves the start of the consultation.
Bring one visit type and a sample note.
Bring your EHR name, a sample note and one visit type. We can show the reviewed history, discuss the One-click browser extension and scope FHIR/HL7 delivery where appropriate.