DPDra. Paula ReisPhysicianOpened the record12/11 14:05
JMJúlia MartinsFront deskSaw the schedule only12/11 13:50
DPDra. Paula ReisPhysicianPrinted the prescription12/11 14:22
Permissions by roleThe front desk does not need the record.
Access historyWho opened, printed and shared.
ConsentForms signed by the patient.
AWS cloudEncrypted transport, no server at the clinic.
Each person sees what their role allows
The front desk sees the schedule and the conversations, the professional sees the records of their patients, and finance sees the charges. Permissions are set by role in the clinic.
Roles set by the clinic
Professionals with council number
Two-factor sign-in
Every opening of a record leaves a trace
Who opened each record and when, and who unlocked, printed or shared a sheet. It is what the clinic needs to answer an audit or a request from the patient.
Access history of each record
Finished sheets locked
Signed documents that do not change
LGPD in the clinic routine
Consent for the procedure and for the use of personal data, signed by the patient and kept in the record. Verbum publishes how it treats data, who its subprocessors are and how to exercise rights.
Consent forms in the record
Public data processing overview
List of subprocessors
And more in this module
Hosted on AWS
No server to keep at the clinic.
Encrypted transport
TLS between the browser and Verbum.
AI with review
Clinical drafts marked for review.
Frequently asked questions
Can the front desk open the record?
Only if the clinic gives that permission to the role. Each role sees what its work needs.
Where is the data kept?
In the AWS cloud, with encrypted transport. The data processing overview and the subprocessors are public.
Who defines the roles?
The clinic itself, in the settings, and it can change them at any time.