Messaging, Memo Desk and alert requirements
Memo Desk
In-house long-form correspondence inbox.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0984What is Memo Desk meant to do beyond chat?
The pilot covers part of this. The rest is designed, not built. Pilot detail: Plain-text memo up to 64 KiB; no rich text, folders or search. REQ-4101 says Memo Desk must provide an internal long-form correspondence inbox with subject, rich text body, attachments, threads, folders, priority, due date and confidentiality level. Its acceptance check: memo created, replied, filed.
C0985Who can send a memo, and can teams share an inbox?
REQ-4102 is a high-priority requirement for all three tiers: Memo Desk must be internal only, signed by the sender session, and must support shared pool inboxes with owners. The pilot covers part of this. The rest is designed, not built. Where the code stands: Internal only and session-signed; no sharing/delegation. To verify it, the specification says external recipient impossible; pool memos have an owner.
C0986How does a formal notice get acknowledged?
The memo desk part of the specification (REQ-4103) says Memo Desk must support formal notices with read-required acknowledgment recorded as a signature. The pilot covers part of this. The rest is designed, not built. In the pilot: Ack/read-required recorded; no formal-notice templates or deadlines. Acceptance check: unacknowledged notices escalate.
C0987Can a memo thread be put on legal hold?
How would it be tested? The specification says held thread cannot be purged. That is the check for REQ-4104: Memo Desk must support legal hold on threads and retention classes. Not built. What the pilot has is a stand-in, not the feature. What v0.2.0 does today: Retention='hold' is a column only; no purge job, no legal-hold workflow.
C0988Can memos be delegated while someone is away?
No. The specification describes it, but the pilot does not include it. For reference, REQ-4105 (a medium-priority requirement, the medium and large tiers) says Memo Desk must support delegation and coverage rules with expiry. Check: coverage ends on date.
C0989Should Memo Desk be used for urgent clinical matters?
Memo Desk must not be used for urgent clinical notifications; it must show a banner recommending the alert path for urgent items. That is REQ-4106, a high-priority requirement for all three tiers. It is one of the few requirements the pilot meets at MVP scope; nothing has touched real data. Where the code stands: Urgent-keyword memo is redirected to alert path (409 use_alert_path). Test in the specification: marking a memo emergency triggers the alert flow instead.