PRAVA

Privacy and Security at PRAVA

A careful, practical approach to the sensitive information involved in dental revenue-cycle work.

PRAVA recognizes the sensitivity of dental-practice and patient information. Public forms should never contain PHI. Before patient information is accessed, workflows, responsibilities, secure platforms, and escalation procedures are established with the client practice. Business associate agreements are put in place where legally required.

Minimum necessary

Access to client information is limited to assigned responsibilities and the information needed to complete agreed work.

Secure setup

Secure platforms, workflow rules, and access expectations are defined during onboarding before client information is handled.

Protected access

Credentials should be unique, protected, and provisioned according to the practice’s approved access controls.

Shared responsibility

PRAVA and each client practice share responsibility for secure communication, appropriate access, training, and prompt responses.

Prompt escalation

Suspected privacy or security incidents should be reported promptly through the agreed escalation process.

Public website safety

No patient information is needed to start a conversation.

Use the contact form only for business contact information and a high-level description of your workflow needs. Do not include patient names, insurance details, clinical records, or other PHI.

Discuss Your Security Requirements

A clearer revenue cycle starts here

Ready to Move Your Practice Forward?

Let’s discuss where revenue is being delayed and how PRAVA can support your team.