For clinicians
Sending to your EHR
What gets filed, what stays a checklist, and what each write-back status means.
What is filed
Once you approve an encounter, Fieldnote files the note to your EHR as a clinical document. Every follow-up action you approved — imaging orders, labs, referrals, prescriptions, follow-up exams — is captured inside that note as a structured, ready-to-act section, both human-readable and coded where a match was found.
The note is filed to your EHR; follow-up actions are captured in the note as a ready-to-act section and checklist for your EHR's own workflows. Fieldnote does not place orders, appointments, or prescriptions on the provider's behalf.
This is the primary design, not a fallback: Epic and Oracle Health both reliably support filing a clinical document, but neither reliably supports a third-party app placing orders, prescriptions, or most appointments directly. Filing to the chart and letting your EHR's own ordering workflows take it from there is the dependable path.
What stays a checklist
Because most EHRs don't accept discrete orders or prescriptions from an outside app, the follow-up actions in the filed note double as a checklist your staff (or you) complete using your EHR's normal ordering screens — the same information, just entered where your EHR expects it rather than pushed in behind the scenes.
Write-back status meanings
The write-back screen shows one row per artifact — the note, and each follow-up action — with one of these statuses:
| Status | Meaning |
|---|---|
| Written to the EHR | Placed as a discrete FHIR resource in your EHR — only possible where native order write-back is turned on and the connected system supports it for that action type. |
| Included in filed note | The default outcome for follow-up actions. Embedded in the filed note as a ready-to-act section rather than placed as a discrete order — not a degraded result, this is how write-back is designed to work by default. |
| Complete manually in the EHR | The note carrying this item couldn't be filed, so it needs to be entered directly in your EHR. |
| Failed | The write-back attempt errored. See the error message on the write-back screen and use Retry. |
Retrying a failure
If write-back fails, the write-back screen shows the error and a Retry button. Retrying re-attempts the same filed content — it does not create a duplicate note if the earlier attempt partially succeeded.
If retries keep failing, check your connection's status in Settings or contact your practice administrator. The underlying cause is usually on the EHR side — expired credentials, a scope that was never granted, or a system that's temporarily unreachable. See Troubleshooting: EHR connection test fails.
Native order write-back (opt-in)
For the small set of cases where a connected EHR (currently, some Oracle Health resources) genuinely supports accepting a discrete order or appointment from an outside app, Fieldnote can attempt that too. This is called native order write-back, and it is off by default for every connection.
It is a deliberate, per-connection opt-in your practice administrator turns on in Settings, not a default behavior: with it off, follow-up actions are always filed as part of the note. With it on, Fieldnote additionally attempts to place a native order, appointment, or prescription for the action types your connection supports, and falls back to the ready-to-act section for anything it does not.
See Settings & audio devices: native order write-back to check or change this for a connection.