FieldnoteHealth

For clinicians

Troubleshooting

Fixes for the issues clinicians hit most often.

Microphone permission denied

If your browser blocked microphone access (often after declining the first prompt), the device list on Capture or Settings stays empty and Allow microphone access won't do anything on its own.

  1. Open your browser's site settings for this page (usually the padlock or camera icon in the address bar).
  2. Set Microphone to Allow for this site.
  3. Reload the page, then select Allow microphone access again.

No audio level while recording

If the level meter stays flat while you are speaking:

  • Confirm the correct device is selected in the Microphone dropdown — a Bluetooth headset can silently fall back to a laptop's built-in mic if it disconnects.
  • Check the microphone is not muted at the OS or hardware level (a physical mute switch on a headset, for example).
  • Re-pair the Bluetooth microphone at the operating-system level, then refresh the device list.

Stuck in Processing

A typical visit finishes processing in a few minutes. It is safe to leave the screen and come back — your visit picks up where it left off from Today.

If it has been noticeably longer than that, refresh Today and reopen the visit. If the pipeline genuinely failed, the Processing screen shows an error message with a Retry option rather than spinning indefinitely.

EHR connection test fails

A failing connection test almost always traces back to the EHR side of onboarding rather than anything wrong on your end. Common causes: the connection was set up for the wrong environment (sandbox vs. production), the vendor has not finished activating the granted scopes yet, or a credential expired.

Share the exact error message with your practice administrator — see Connecting Epic / Oracle Health / another FHIR R4 system for what they will need to check.

Session timed out

Fieldnote warns you before signing you out after a period of inactivity, and signs you out automatically if you do not respond. Signing back in is quick, but note the trade-off: if you were idle mid-recording and part of the audio had not finished syncing yet, that portion may show as lost once you are back — see Recording a visit: if a recording shows as lost.

To avoid this during a visit, respond to the idle warning promptly, or keep the tab active until the sync banner shows everything is synced.