HEALTHCARE DATA RESPONSIBILITIES
HIPAA & healthcare data
Updated November 8, 2026.
The public website, demonstrations and general project workspace are not approved for patient records or protected health information (PHI).
Keep patient information out of general workflows
Do not enter patient names with treatment details, medical histories, diagnoses, insurance records, patient photographs or other PHI in consultation forms, general uploads, support messages, demos, website assessments or AI prompts. Use fictional data when evaluating demonstrations. HTTPS encryption alone does not establish HIPAA compliance.
Healthcare engagements require separate approval
Before we create, receive, maintain or transmit PHI on a healthcare customer’s behalf, the parties must establish the appropriate business associate relationship, execute the required Business Associate Agreement (BAA), approve the specific deployment and confirm the safeguards and downstream agreements required for its data flows. A public page, purchase, account registration or confidentiality statement is not a BAA.
Deployment responsibilities
A healthcare deployment must address risk analysis and risk management, workforce access and training, minimum-necessary permissions, authentication, audit review, secure transmission and storage, incident response, contingency planning, tested recovery, retention and secure disposal. Responsibilities, approved integrations, subcontractors and reporting obligations must be documented for the engagement. Hosting or software providers’ certifications do not automatically extend to our application or a customer’s operations.
AI, email and integrations
General-purpose AI, analytics, email and other integrations are not authorized to receive PHI merely because they are connected. Each PHI-related use requires review of the provider, agreement, configuration, retention and permitted use. Ordinary email and lock-screen notifications must not contain PHI through the general workspace.
Patient rights and incidents
Patients should direct medical-record access, amendment and other patient-rights requests to their healthcare provider. If we process records for that provider under an approved engagement, we assist as required by the agreement and applicable law. Suspected accidental submission or unauthorized access should be reported promptly to info@cybersecuritydoctors.com without including additional patient information. Applicable incident and breach reporting requirements are handled under law and the relevant agreement.
Our current representation
We do not claim that this public website or the general project workspace is HIPAA certified or authorized for PHI. Healthcare suitability must be established for the actual deployment before use.