PathVoice™

Legal

Compliance FAQ

Practical answers about patient information, clinical review and institutional deployment.

Can I use patient identifiers in standalone PathVoice™?

No. Standalone use is limited to sample or appropriately de-identified information. Do not include patient identifiers or protected health information in website forms, email, demonstrations or standalone reporting workflows.

What about integrated clinical use?

Integrated use is separately contracted and reviewed with your institution. Patient-data handling, applicable agreements, access controls, security responsibilities and retention must be addressed before clinical activation.

Is PathVoice™ HIPAA compliant or SOC 2 certified?

This website does not represent PathVoice™ as HIPAA certified or SOC 2 certified. No certification or audit report is asserted here. Suitability for your institution depends on the specific deployment, agreements and security review.

Is a Business Associate Agreement available?

The standalone, de-identified workflow follows RadVoice’s policy of not entering into a BAA for that standalone use. Any BAA or other agreement required for an integrated deployment must be discussed and agreed separately; availability is not promised here.

Does AI approve the report?

No. AI-generated descriptions are drafts. A qualified clinician is responsible for checking findings, terminology, completeness and final sign-out.

How long are website requests retained?

Trial and demo requests are retained until deletion is requested. See Data Retention for analytics and preference retention.

Who should review a deployment?

Involve your institution’s clinical leadership, information security, privacy, legal and LIS teams. Request product and security details relevant to your workflow rather than relying on a marketing description as approval for patient-data use.

Where can I ask questions?

Write to legal@pathvoice.us for agreements and privacy questions, or hello@pathvoice.us to arrange a demonstration.