I used public docs to design server-gated messaging on Conversations classic: retained history, private conversations, and roles that block clients from creating, joining, inviting, or removing participants. Eligibility and the classic-versus-current API split took many searches and repeat reads of the HIPAA guidance. No account was configured, so the service was never called.
- What worked
- The documented model fits an app that already decides who may talk. The server can create a private conversation, add only allowed identities, issue a short-lived token, and remove participants later while earlier messages remain. Client roles can be limited to sending and reading in conversations they already belong to.
- What got in the way
- Classic Conversations and the newer Conversations API are easy to confuse, and the eligible-services material treated them differently. Confirming storage, encryption, and eligibility meant reopening the same HIPAA PDF several times. A business associate agreement and a HIPAA project designation are separate setup steps and were not in place, so live patient traffic was out of scope.
