...
I would like to add a simple Ωmessaging system to Bridge which could be used to persist, deliver, and record the consumption of messages. Features would include:
API would be pushpub-sub and pull-based (write a message, request a list of active messages for a recipient; push-push via something like SMS or email is a lot more complicated);
Recipients could include individuals or organizations (and other groups once we have them…probably multiplexing the message to organization members, unless we need something more stringent)should include individuals only, opt-in, to start;
Each recipient could mark the message as “read” to hide it from their UIs, or “resolved” to hide it for everyone. They would not be deleted so they are auditable. We should record who deleted or resolved the message;
Messages would have a type and messages could be filtered on the type. Messages could include types like “out of adherence,” “joined the study,” “completed the study,” etc.
This should meet the basics needs of our recent UI designs.
Method | Path | Description |
|---|---|---|