Questions about security and data protection

In layers: DataClic reads Tasy in read-only mode; patients travel to the cloud identified only by a code; each hospital has its own key and sees only its own data; access is per user, with a password and personal code; and every access is logged. See security and LGPD.

The tables the dashboards need: encounters, accounts, payers, departments, costs, accounting entries, receivables and payables. Patients are identified only by a code. Names, national ID numbers (CPF) and dates of birth never leave the hospital.

Clic Health was designed to reduce risk when processing health data: it minimizes what leaves the hospital, does not carry data that directly identifies patients, controls and logs access, and publishes its terms of use and privacy policy. LGPD compliance is a shared responsibility with the hospital, which defines the legal bases and internal policies; the article LGPD and hospital BI lists what to assess.

Users authorized by the hospital administrator, each within the BIs granted to them. The Clic Health support team has access for maintenance, and that access is also logged. Users from other hospitals never see your hospital's data.

Yes. Clic Health logs every access, the screens opened and configuration changes, for the hospital's audit.

Yes, with a temporary user: read-only, with an expiry date set by the administrator. When it expires, access ends, and the record of what was viewed remains logged.