Practice Fusion
Availability checks, booking, and chart writes run through the practice’s existing workflow — not a promised vendor API. The draft waits in the queue until a person releases it.
Integrations
Draft. Staff release. Then the chart.
DocAssistants prepares the write. Staff approve it. There is no silent write-back. If a capability is refused, staff see the refusal.
Where it writes today
Practice Fusion, eClinicalWorks, and a FHIR R4 path.
eClinicalWorks
The same pattern: capture, staff release, then the EMR action. Write-back follows the sanctioned path for that practice.
Certified FHIR R4 systems
Standards-based systems have a path. We do not list EMRs we have not run.
Refused capabilities
An adapter that does not support a capability refuses the call rather than guessing. Staff are notified in the queue.
What this is not
Not a silent write into the chart.
Sensitive actions wait on human release. Identity is verified before chart-specific work. The technical guarantees live on the platform page.