Click any of the questions to display the corresponding answer.
If you have a question that is not answered here, please email us at [email protected] or see our contact page for other ways to contact us.
Secure Meeting Place is organized around ‟rooms”. You can also think of rooms as ‟topics” — a room might be used for discussions about a client, patient, story, movie, topic, case, or anything else. Access to rooms is by invitation only — you must be invited by a host to participate (read or post messages).
A room contains messages, grouped in ‟threads”, a series of related messages. Messages can also contain links to external sites or attached documents.
Rooms have both an internal name and an external name. The external name will be used for external communications (e.g. new message notification emails) and should always be considered non-confidential.
You can organize your rooms into groups for your convenience, for example you might have ‟Active” and ‟Inactive” groups. Each user groups rooms as she pleases; the group name and organization are private to you.
All user data entered on Secure Meeting Place is considered confidential, with a few carefully noted exceptions. Please refer to our Security page for an explanation of how we ensure the confidentiality of your data.
In particular, room internal names, message subjects and contents, attached documents and group names are all stored in encrypted format. By virtue of being encrypted with a key derived from your password, the personnel of Secure Meeting Place are unable to view any confidential data. See our Password Info page for more info on how passwords are used.
The only user data which is not treated as confidential (and thus stored in unencrypted format) are the rooms' external names. The external name is used to refer to rooms in notifications which can be sent via email. Since email should be treated as non-confidential, the system always uses the non-confidential external name in notifications. For example, a room's internal name might be a client's full name while the external name might be a first name only or a case number or some other pseudonym.
Note that information about messages, rooms and user accounts is not encrypted. For messages, this means who posted it, when it was posted, and who has read it is not encrypted. Similarly, for rooms, information such as when it was created, who is a member, who has a release for whom, etc. is not encrypted. User account information (your contact info, which rooms you are a member of, etc) is similarly not encrypted.
Access to messages and documents in a room can optionally be controlled by requiring releases. Releases allow you to post to everyone in the room, yet ensure that only people who you have explicitly allowed access are permitted to read your messages.
Requiring releases in a room is optional; the host of a room decides if releases should be required or not. If releases are not required, then all members of the room can always see all messages.
Because rooms can have multiple particpants, and not everyone will have a release for everyone else, this allows you to invite everyone to the room and each member of the room manages who should and should not see their messages by confirming (or not confirming) that they have a release for each other member.
The canonical use for this is controlling access to confidential patient data (such as medical records). For example, consider a room being used to discuss patient care for a patient Paul and that three providers (Alice, Bob and Cary) are members of the room. Alice needs a release from the patient for each other provider who she will communicate with. Alice may have a release for Bob but not yet have one for Cary. Alice records the release for Bob and when she posts a message to the room, Bob can read it, but Cary sees only that a message was posted, the contents are hidden from for him.
Note that releases are unidirectional, they are not reciprocal. Alice and Bob each need to confirm a release for each other if they want the other person to be able to read their messages. If Alice has recorded a release for Bob and Bob has not recorded one for Alice, then Bob will be able to read Alice's messages but Alice will be unable to read Bob's messages.
Note that Secure Meeting Place does not validate or store releases, it only tracks which members have confirmed that they have releases for which other members. Once you confirm a release for a given member in a specific room, all your messages (past and future) in that room become viewable by that person. You can also revoke a release for a room member at any time; all of your messages then become unreadable by that member when you do this.