Ledger, sync, offline and hardware requirements · C0933
Does patient care wait for the ledger to be reachable?
Designed, not yet built
Short answer
How would it be tested? The specification says with ledger stopped, all clinical workflows still run; queue drains in order after restart. That is the check for REQ-3012: the ledger client must queue writes when the ledger is unreachable and append them in order on reconnect; care must not depend on ledger availability. This is on the design side of the line. Nothing in v0.2.0 does it.
This is designed, not built.
- Specification item
- REQ-3012
- 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 cryptographic erasure of a patient's data work? Designed
- Could the ledger's signature methods be upgraded later? Designed
- Which ledger technology is the baseline, and could it be replaced? Designed
- How are patient pseudonyms built, and how can they be cut? Designed
See it in context: Federated ledger, spheres, tokens, wallets, bridges · Search the help center · Ask a question