Security starts with understanding how data flows
Hospital solutions handle personal and health data. In each project, we assess which data is used, who accesses it and how long it is kept.
See the portfolio’s features and the points to clarify before contracting.
- Web dashboard
- PWA app
- Kiosk
Documented features, with a defined scope
On their own, these features are not equivalent to multi-factor authentication, certification or full LGPD compliance. Biometric data requires a specific assessment. Controls are assessed per solution and environment.
EasyBot Médico
Individual access by phone number.
EasyBot Paciente
Identification by CPF (Brazilian taxpayer ID) and date of birth.
EasyAtend
Identification by CPF (Brazilian taxpayer ID) and date of birth, with a queue ticket.
EasyPABX
Employee/role validation in Tasy and an auditable log.
EasyMove
Auditable timeline of internal transport.
Medusa
Access profiles, card/biometric/facial credentials and auditable events.
LGPD: purpose, responsibilities and rights
Each project defines purposes, necessary data, legal bases and each party’s responsibilities.
Data processing roles
As a general rule, the institution is the controller of patient data and dualpath acts as a processor. Each party’s responsibilities are set in the contract, in accordance with Brazil’s data protection law (LGPD).
Personal data requests
Write to contato@dualpath.dev.br. When the institution is responsible for the processing, we forward the request to it.
Security and data questions
Where is data processed and stored?
It depends on the solution and deployment environment. Data location, the providers involved and any international transfers are assessed for each deployment.
How is access controlled?
In web solutions, through Tasy’s own login and permissions. On WhatsApp, physicians are identified by the mobile number registered in Tasy and patients by their Brazilian taxpayer number (CPF) and date of birth, with a limit on attempts.
What protection measures are used?
Encrypted communication and data validation during operations. Available records vary by solution and are assessed with the institution’s team.
How long is data retained?
Data retention, disposal and return are defined in the contract with each institution, in accordance with the LGPD.
How are incidents and continuity handled?
Responsibilities for incidents, continuity and support are defined in the contract with each institution, in accordance with the LGPD.
Technical documentation and security questionnaires are provided on request during the evaluation.
Assess the requirements with your team
Bring questions from IT, security, legal and user areas to the conversation.