Requirements explained (from the specification)
Ledger, sync, offline and hardware requirements
Federated ledger, sync and limiter, offline printing, on-site hardware, server-to-server transfer, analog layer and downtime.
Federated ledger, spheres, tokens, wallets, bridges (15)
Only hashes, consent and audit on the ledger.
- What may be written to the ledger, and what is never allowed on it? Designed
- What is a sphere, and how does a clinic or network fit in one? Designed
- Does AuroraMed implement the token types ID, ROLE, CONS, GRANT, XFER, BRG-A/BRG-B, NODE, ALERT, BG and DELEG with the semantics in design 11.5, all… Designed
- Does AuroraMed support mintable wallets of classes W-P, W-D, W-S, W-N, W-B, W-G with minting by quorum, identity binding, expiry and rate limits? Designed
- How many people would have to agree before a sensitive ledger action goes ahead? Designed
- How would two spheres be connected through a bridge? Designed
All 15 answers in this section →
Sync, backup, read limiter and safe degradation (14)
Cloud sync and clinic-to-clinic sync; limiter; pause.
- Which copy of the data is the working one: the clinic's or the cloud's? Designed
- What does a sync bundle contain, and how is it protected? Designed
- Can clinics sync directly with each other? Designed
- What is the read-side limiter and what does it limit? Designed
- If the limiter trips, does the clinic stop working? Designed
- Does a detected integrity problem also pause sync? Designed
All 14 answers in this section →
Offline behavior and printing (7)
Local operation, offline printing.
- Can the clinic keep working and print records when sync or transfer is down? Designed
- How would printers be connected to keep printing off the network? Designed
- Is every print job recorded? Designed
- Would printed pages be watermarked? Designed
- Is there a limit on how much one user can print? Designed
- Does printing a highly restricted compartment need extra steps? Designed
All 7 answers in this section →
On-site server, sealed terminals, hardware profile (7)
Physical system.
- What does the on-site server look like for a small hospital versus a large one? Designed
- What are the sealed terminals meant to be? Designed
- Are USB ports on the terminals open? Designed
- Do the camera-resistant screens work? Designed
- How would a terminal prove it has not been tampered with? Designed
- What happens if someone opens a terminal? Designed
All 7 answers in this section →
Server-to-server transfer, three streams (5)
Secret-shared, decoy-padded transfer.
- How would server-to-server clinical transfers be protected? Designed
- Which encryption would transfers use? Designed
- Does AuroraMed document that decoys provide traffic-analysis resistance and not confidentiality or quantum resistance? Designed
- Who authorizes a transfer before data leaves? Designed
- What happens if a transfer behaves oddly? Designed
Analog timing layer (4)
Least mature component.
- Is the analog timing layer part of the pilot? Designed
- How are out-of-schedule signals from the analog layer handled? Designed
- Would the analog layer ever be the only lock? Designed
- How well does the analog layer work? Designed
Downtime and business continuity (3)
Safe-mode ladder L0-L5.
- Does AuroraMed provide the safe-mode ladder L0 normal through L5 paper/downtime, with defined entry conditions and UI banners? Designed
- Does AuroraMed generate downtime reports (census, MAR, orders, allergies, medications, problem list, code status, contact list) at schedule and on… Designed
- Does AuroraMed provide back-entry of downtime paper records with reconciliation and audit flag? Designed