Working offline
MedJot is built for a job done in places with no signal. The entire clinical workflow works offline.
What works with no connection
- Building a report — every section, every finding, every free-text field
- Observations and NEWS2
- Every score, care bundle and the frailty scale
- The whole toolbox — notepad, stopwatch, timer, calculators
- Autosave
- Copy and PDF export
- Templates you have already loaded
This works because the interface is cached on the device and clinical data is on the device to begin with. There is no server round trip in the critical path of documenting a patient.
What needs a connection
| Needs a connection | What happens without one |
|---|---|
| AI tools | Fail clearly, and offer to queue — for three of the five |
| Device transfer | Unavailable; both devices need to be online |
| Signing in for the first time on a device | Unavailable |
| Payment and subscription changes | Fail clearly rather than queue — see below |
| Support tickets | Sending waits |
Payments deliberately fail rather than queue
A payment that silently retries later is a payment you did not knowingly make, possibly at a price that has since changed. MedJot refuses to queue them; you get a clear failure and can try again when you have signal.
Fire-and-forget writes do queue
Non-clinical background writes — usage counters, settings sync and the like — go into an on-device queue and flush when the connection returns, on reload, when the network comes back, or when you switch back to the tab.
The connection indicator shows a count of anything still waiting.
Signing in
You need a connection the first time you sign in on a device. After that your session persists and MedJot opens signed in with no signal.
Some account-level information is cached, so entitlement is known offline. A subscription that changed while you were offline is reconciled when you reconnect.
Practical advice for a shift with no signal
- Open MedJot before you lose signal if you can. It works either way once installed, but a first load needs the network.
- Export as you go rather than accumulating reports on the device. The report is not a record of care until it is in the system that is.
- Do not rely on a queued pre-alert. It sends when the connection returns, which may be after it mattered. Use the radio.
- Watch the globe. Amber means the connection is unreliable rather than absent, which is when AI requests are most likely to fail slowly. See The connection indicator.