Privacy and data safety

Protect patient records before using smart tools, complaints, or public advocacy.

A stronger advocacy platform must protect patients from accidental oversharing. Medical records, portal messages, insurance details, pharmacy labels, disability paperwork, and complaint drafts can expose more than patients realize.

Privacy is part of patient safety

Patients often share records because they are desperate to be believed. But screenshots, labels, and documents can reveal addresses, dates of birth, account numbers, policy numbers, claim numbers, barcodes, QR codes, names of relatives, clinician names, and unrelated diagnoses.

Browser-only tools are safest for early drafting

The current Pain Care Rights tools should stay browser-only unless a feature truly needs saved accounts, uploads, databases, or AI. If OpenAI, OCR, Prisma, or storage is added later, it should be intentional and documented.

No upload unless the feature truly needs the document.
No storage without a retention and deletion policy.
No state-law output without verified source records.
No AI conclusion without uncertainty language and user review.

Future database and AI planning

A future database may be useful for state-law sources, agency directories, saved drafts, or source QA logs. A future AI layer may help organize records and patient language. Both should be built around security, consent, minimum necessary information, and clear user control.

Privacy-first tools

Smart patient tools should protect records before they analyze them.

Medical records, pharmacy details, disability paperwork, insurance documents, and complaint drafts can expose deeply private information. This checklist explains the safety baseline before any OCR, AI, upload, or saved-account feature is added.

Minimum safety habits for patients

Remove names of unrelated people, full addresses, account numbers, policy numbers, claim numbers, Social Security numbers, barcodes, QR codes, and portal screenshots unless they are truly necessary.
Keep a private original copy, but share only the minimum relevant excerpts when preparing a public post, complaint draft, or advocacy summary.
Avoid uploading photographs of IDs, insurance cards, prescription labels, discharge packets, or full chart pages to tools that do not clearly explain storage and deletion.
When a tool uses AI, confirm whether the data is stored, logged, used for training, shared with vendors, or retained after the session.
Prefer browser-only organizers for early drafts and sensitive summaries until secure account, storage, and deletion controls are intentionally built.

When OpenAI may make sense later

OpenAI can help turn patient facts into clearer drafts, compare a short excerpt against a checklist, or identify missing next-step questions. It should not be used as the legal source, medical decision-maker, or hidden storage layer.

When Prisma/database may make sense later

Prisma and database storage make sense only if users need saved accounts, saved drafts, state-resource tables, source-update logs, contact directories, or secure document history. That requires authentication, consent, encryption, retention limits, deletion controls, and audit-friendly design.

Sources

References used for this page.

These links are provided for transparency. They support general education and advocacy content, not individualized medical or legal advice.

HHS — De-identification guidanceUsed for identifier and privacy-safety framing.HHS — HIPAA and cloud computing guidanceUsed for future cloud storage and vendor planning language.FTC — Health Breach Notification Rule updateUsed for consumer health app privacy and breach-notice context.

Need to compare a record safely?

Use the visit note discrepancy review without uploading the entire record.

Compare note issue