Single code per report
A universal identifier (UUID) that is never repeated, assigned at the time of creating each report.
Un PDF común lo edita cualquiera: una fecha, un diagnóstico, tu firma. Cada informe de Brauni sale con código único, hash SHA-256 y un portal público donde obras sociales, ART y juzgados comprueban su autenticidad en segundos.
30 days freeNo cardIncluidos en todos los planes
PDF Hash
01SHA-256
Code per report
02Unique
Verification
03Public
Access by the third party
04No account
From the patient's file, with his medical records by hand. For health insurance, a referral, the school or the court that asked for it.
When generated, the system calculates an SHA-256 hash of the file and prints a unique verification code with its URL at the bottom of all pages.
Enter the public portal, enter the code, or upload the PDF, and receive instant confirmation that the report is authentic and not altered. No account or login.
A universal identifier (UUID) that is never repeated, assigned at the time of creating each report.
The fingerprint of the document. If someone changes a comma, the hash changes completely and the verification detects it. The same standard as SSL certificates.
The verification code and URL appear in the footer of each page: it is impossible to separate a sheet without notice.
Anyone can check the authenticity without an account or login: enter the code or upload the PDF and get ready.
health insurance, private health plans, ART, courts, schools or the colleague who receives your referral: everyone can verify what you signed.
The report is written from the medical records, not from a loose Word: it is registered with the rest of the documentation.
In a clinical tool, privacy cannot be an aggregate. We design Brauni to protect professional secrecy from infrastructure to every access.
We protect professional secrecy without marketing data, without training models and without small lyrics.
TLS 1.3
Encrypted traffic connections
Google Vertex AI
Zero training with your data
AWS Multi-Region
Backups and high availability
HIPAA BAA
Agreements signed with Google Cloud and AWS
AAIP
Recording of persons in the process
The clinical fields are encrypted with Fernet (AES-128), the infrastructure applies rest encryption and communications use TLS 1.3.
You can add authentication in two steps and biometrics so that only you can access the clinical notes.
Your session data is not used to train models. Restriction is part of our supplier agreements.
Continuous backups and distributed services protect the availability of information.
You can export your clinical history in universal formats when you need it, without hindrance or special orders.
Relevant accesses and movements are recorded so that you can review the account activity.
The complete technical detail of the verification system.
Read articleThe guide to drift well, with note model included.
Read articleYour obligations when a court asks for clinical information.
Read articleThe documentation from which your reports come out, according to Law 26.529.
Read articleTry it in your clinical practice.
30 days · without · card human support