Ledger, sync, offline and hardware requirements · C0953
Is every print job recorded?
In the pilot (v0.5.0, synthetic data)
Short answer
The offline behavior and printing part of the specification (REQ-3203) says every print job must be an audit event with user, hashed patient reference, time and terminal, queued locally while offline and appended to the ledger on reconnect. The pilot covers part of this. The rest is designed, not built. In the pilot: Print log: user, hashed patient ref, time, terminal. Acceptance check: offline print log appears on ledger after reconnect in order.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-3203
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of October 2, 2026. Version 0.5.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- How would printers be connected to keep printing off the network? Simulated
- Would printed pages be watermarked? Pilot
- Is there a limit on how much one user can print? Pilot
- Can the clinic keep working and print records when sync or transfer is down? Pilot
See it in context: Offline behavior and printing · Search the help center · Ask a question