FAQ

Questions, answered.

The things prospective clients ask most — about security, fit, pricing, and getting started. Don't see yours? Ask us directly.

What does Paladyn Health do?

Paladyn is a prevention-first, AI-driven revenue cycle platform — plus the advisory work behind it. Instead of chasing denials after they happen, our engines predict and prevent them before claims go out, recover the few that slip through, and keep your payer intelligence current. The philosophy is simple: prevent, not pursue.

Where does our PHI live, and is it safe?

Protected health information is processed and stored only inside our HIPAA-eligible AWS environment, reached through a secure SFTP intake. It never touches this website, email, file shares, logs, or AI tools. Data is encrypted in transit and at rest, access is least-privilege with multi-factor authentication, and activity is recorded in tamper-evident audit logs. See the Trust Center for the full picture.

Are you HITRUST or SOC 2 certified?

Today we operate as a HIPAA Business Associate. We are building toward HITRUST certification and a SOC 2 Type II examination, and the underlying controls are already implemented — encryption, least-privilege identity, audit logging, immutable backups, and controlled change. We are transparent about what is in place versus in progress; it is all laid out in the Trust Center.

How does Paladyn connect to our EHR and clearinghouse?

Through the standard healthcare data your systems already produce — 837 claims, 835 remittances, 276/277 status, 270/271 eligibility, and 278 prior authorization — exchanged over a secure SFTP intake. It is designed to work alongside clearinghouses and your existing EHR rather than replace them.

What is your pricing model?

Prevention-first, by design. We favor a subscription plus an outcome-aligned component tied to recovered dollars, rather than a pure percentage-of-collections model — because paying only to chase denials rewards pursuing them instead of preventing them. We'll tailor the model to your size and goals.

Can we use one engine, or do we need the whole suite?

Either. Every engine runs standalone, and they get smarter together on the shared Aegis foundation. Many organizations start with denial prevention or price transparency and add from there.

How long does implementation take?

It depends on your data and scope, but onboarding is intentionally light: a secure SFTP feed and read-only access to the data the engines need, rolled out in phases so you see value early.

Do you store patient data on this website?

No. This site is informational only. The calculator and forms here are PHI-free — they take aggregate numbers and contact details, never patient information.

Who is Paladyn built for?

Hospitals, health systems, and physician groups that want to move their revenue cycle from reactive collections to proactive prevention.

How do we get started?

Request a revenue cycle assessment and we'll show how Paladyn would apply to your denials, AR, and payer mix. We're also taking on a small number of design partners who want to shape the product.

See where prevention pays off.

Request a revenue cycle assessment and we'll show how Paladyn would apply to your denials, AR, and payer mix. We're also taking on a small number of design partners.

Request an assessment