PRIVACY

Use health and personal information only for an authorized purpose.

Intelligent Radiology treats privacy as a data-lifecycle requirement: identify the information, determine the lawful and contractual purpose, limit access and reuse, preserve rights, govern vendors, and retain or delete data according to approved rules.

PRIVACY OPERATING PRINCIPLES

Privacy controls follow the data from collection through deletion.

The exact legal duties vary by role, jurisdiction, customer, and data type. The controls below express the enterprise privacy baseline and must be mapped to the applicable legal and contractual requirements before production use.

Classify before use

  • Distinguish PHI, medical information, consumer health data, account data, workforce data, credentials, and other sensitive information.
  • Identify the source, purpose, jurisdiction, and organization responsible for the data.

Minimum necessary and least access

  • Limit access to the people, roles, systems, and purposes that require it.
  • Separate educational, quality, research, clinical, administrative, and public workflows.

Staging and demonstration boundaries

  • Do not place real PHI in staging or demonstration environments unless an approved production-grade workflow explicitly authorizes it.
  • Use synthetic, de-identified, or otherwise approved test data whenever practical.

Notice, consent, and rights

  • Provide required notices at collection and privacy disclosures where applicable.
  • Support access, correction, deletion, restriction, opt-out, appeal, and other rights when the governing law provides them.

Vendor and subprocessor governance

  • Define permitted processing, security duties, breach obligations, data location, retention, return, and deletion.
  • Use BAAs, DPAs, SCCs, or other required agreements when applicable.

Tracking and secondary use

  • Do not expose protected or sensitive health information to advertising, analytics, or other third parties without an authorized basis.
  • Evaluate pixels, SDKs, logs, telemetry, and AI inputs before enabling them in health-data workflows.

Retention and deletion

  • Keep information only for an approved legal, clinical, contractual, or operational period.
  • Apply controlled deletion, return, archival, and backup-expiration processes.

Privacy incident response

  • Escalate suspected unauthorized access, disclosure, or use promptly.
  • Preserve evidence, assess notification duties, document decisions, and close corrective actions.
Production gate: Privacy review is not complete because a page exists. Applicable privacy obligations must be mapped, assigned, evidenced, and closed—or formally documented as not applicable—before PHI-enabled or clinical production release.