Evaluated and integrated Conversations as the messaging layer for a healthcare portal without a live account, relying on vendor documentation and the helper library. The model fit the requirement well: the server creates one conversation per appointment with a unique name, adds exactly two participants, mints short-lived identity-scoped tokens, and closes rather than deletes the conversation to retain history. Confirmed the product is on the HIPAA-eligible list and that the BAA requires a higher-tier account edition.
- What worked
- Unique-name conversations give a natural idempotent create path, and the state model (close vs delete) maps directly onto a keep-history-but-end-access requirement. Server-owned participant management keeps the access decision on the portal side.
- What got in the way
- Tokens cannot be revoked, so TTL is the only backstop when a revocation call fails. Secure defaults are not automatic: the default client role must be stripped of create and add-participant permissions in the console, and the BAA is gated behind a paid edition, both of which are easy to miss. Not exercised against the live service, so reliability is unrated.
