Ledger, sync, offline and hardware requirements · C0953
Is every print job recorded?
Designed, not yet built
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. Designed, not built: there is no code for this in the pilot. Acceptance check: offline print log appears on ledger after reconnect in order.
This is designed, not built.
- Specification item
- REQ-3203
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of September 30, 2026. Version 0.2.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? Designed
- Would printed pages be watermarked? Designed
- Is there a limit on how much one user can print? Designed
- Can the clinic keep working and print records when sync or transfer is down? Designed
See it in context: Offline behavior and printing · Search the help center · Ask a question