HIPAA: What Has Been Implemented in the Platform
Which medical data protection requirements have been implemented in DocPats, and which documents and audits the platform does not yet have.
An honest formulation: DocPats is built with HIPAA requirements for handling medical data in mind. This is not the same as a completed third-party audit and a signed business associate agreement (BAA) — we do not have these yet, and claiming otherwise would be dishonest.
Below is exactly what has been implemented, so that you can assess it yourself rather than take our word for it. A plain-language description for patients is available in the /docs/privacy section. For questions: support@docpats.com.
An Access Log That Cannot Be Scrubbed
Every access to a medical record is written to a separate log. Modification and deletion of entries are prohibited at the data model level, not by a permissions setting: the platform administrator cannot edit the access history. The retention period is seven years.
The log captures structure: who accessed what resource, when, and with what action, along with the network address. Clinical content is not written to the log — this is a separate rule in the code: the log outlives the data itself and must not become a second, less protected repository for it.
In addition to record access, the same log captures:
- account logins, failed logins, and lockouts of clinic staff;
- enabling, disabling, and resetting two-factor authentication, and use of a backup code;
- phone number confirmation and removal;
- account deletion requests and cancellations, and account activation via link;
- document submission by a physician and every credentialing decision (approval, rejection, suspension, renewal, automatic revocation upon expiration).
Patients can view their own log — the /patient/access-log page: when, which organization, which section of the record, and what was done. The name of the individual staff member is not shown to the patient (the organization is accountable for access); a name-level review is available to the clinic administrator.
Encryption of Data at Rest
Textual information that can identify a patient, as well as medical records, is encrypted before being written to the database. Surgical modeling uses a separate algorithm with integrity verification: a tampered surgical plan will fail to decrypt rather than return plausible but incorrect data.
Search across encrypted fields is implemented via irreversible fingerprints: a physician can find a patient by phone number, but the number cannot be reconstructed from the fingerprint.
Passwords are stored only as a strong irreversible fingerprint. The second-factor secret is stored encrypted, and backup codes are stored only as fingerprints.
Clinic images and examination files reside in closed storage: there is no direct public link; the file is served by the server after a permissions check, with an entry written to the log.
Database backups are taken several times per day and stored encrypted.
Access Control and Authentication
- Email confirmation is mandatory: logging in with an unconfirmed email address is not possible.
- Brute-force protection: 5 consecutive incorrect passwords lock the account for 15 minutes; in addition, the number of login attempts is rate-limited by network. The site does not disclose whether an email address is registered, either at login or during password recovery.
- Two-factor authentication — a code from an authenticator app, 10 one-time backup codes, and the option to remember a computer for 30 days. Recommended for physicians; the platform may make it mandatory for physicians. Disabling it requires both the password and a valid code. See
/docs/account-securityfor details. - Session revocation: changing the password and enabling the second factor terminate all other logins to the account.
- Sessions are time-limited (14 days; 30 with "Remember me").
- Platform administration login is separate and requires a second factor. Administration staff receive access only to the sections assigned to them; only the platform owner can reset a user's second factor.
Minimum Necessary Access
A registered patient personally confirms a clinic's access and opens data types individually: visits, allergies, chronic conditions, surgeries, family history, immunizations, and imaging studies. A single individual record may also be opened. Consent has a purpose (treatment, referral, second opinion, emergency care, research); emergency consent expires automatically after 7 days. Consent can be revoked — access ceases for future requests, and the consent history is retained.
Within a clinic, permissions are divided across nine roles — owner, administrator, manager, physician, nurse, receptionist, accountant, pharmacist, marketer — and a permission can be narrowed down to an individual section for a specific staff member. It is not possible to elevate another person's role above one's own: a staff member cannot grant permissions that they do not themselves hold.
Students and residents do not work with real patients and do not issue prescriptions — regardless of the documents submitted.
Who Is Authorized to Write to the Medical Record: Physician Verification
A physician without verified credentials cannot issue prescriptions, write to the medical record, issue medical certificates, or publish articles. The required documents are the license, diploma, proof of specialization, and identity document; these are reviewed by a person, not by automated recognition.
Credentialing has an expiration date — the earliest confirmed expiration date among the required documents. The physician is notified 30, 7, and 1 day in advance; on the expiration date, credentialing is revoked automatically, and this event is written to the log. Expiration is also checked on every request, not only by a nightly job — therefore an expired license does not keep prescriptions open "until the next night." See /docs/account-security for details.
Clinic staff (who are not DocPats users) are not subject to this rule: the clinic is accountable for their credentialing.
Isolation Between Clinics
Clinic affiliation is automatically applied to every database query, and a query attempting to retrieve another organization's data is rejected. This is a property of the data access layer, not an interface check. The project includes dedicated tests for this scenario: clinic A's data is requested in clinic B's context and must return nothing.
What Artificial Intelligence Does and Does Not Do
Analysis of laboratory results and imaging studies is labeled as supportive; the label is immutable and is stored together with the data. A case cannot be closed until the physician writes their own conclusion, and the model's output is never inserted into it automatically. Responsibility for the clinical decision remains with the human — this is built into the architecture of the system, not into fine-print disclaimers.
Only text that a person has explicitly submitted for analysis or translation is sent to AI providers, without any information by which a patient could be identified.
Patient Rights
- Access to one's own data — in the personal account, regardless of plan; individual medical history entries can be downloaded as PDF; a complete copy can be requested from support.
- "Who opened my record" log —
/patient/access-log. - Revocation of consent granted to a clinic — in the personal account.
- Account deletion —
/account-deletion: 30 days to cancel, then de-identification. Records that a physician or clinic is required to retain remain with them without any link to the individual; the access log is retained.
What Is Not Yet Available
- A third-party HIPAA compliance audit.
- A signable BAA for partner clinics.
- SOC 2 certification.
- A list of active sessions with a "log out on all devices" button (currently a password change is used for this).
- A button to export all patient data as a single archive (currently available by request to support).
If you need these documents for your practice, write to us and we will discuss timelines: support@docpats.com.
Frequently Asked Questions
Is DocPats HIPAA-certified? No. The platform is built with HIPAA requirements in mind, but it has not undergone a third-party audit and holds no certificate.
Will you sign a BAA with our clinic? There is no ready BAA at present. Write to support@docpats.com and we will discuss timelines.
Can a DocPats administrator delete or modify an entry in the access log? No. Modification and deletion of log entries are prohibited at the data model level.
How long is the access log retained? Seven years.
Do diagnoses and names appear in the log? No. Only the structure is written to the log: who, when, which section, and what action.
Can a staff member of one clinic see another clinic's patients? No. A request for another clinic's data is rejected at the database level.
Is two-factor authentication mandatory? For the platform owner, yes. For physicians it is recommended, and the platform may make it mandatory. Patients enable it at their discretion.
Can AI enter a diagnosis into the record on its own? No. AI analysis is labeled as supportive, and a case is closed only with the physician's conclusion.
How does a patient find out who viewed their data? On the /patient/access-log page.
See also: how the platform handles your data, login, security, and physician verification.
<!-- translated-from-ru: 3dbab6d004ebeda4c0ff4e295d31cd6a8e19f20d -->