Define the record
A review may need a policy result and case reference, not a clinical note. Select the fields needed to explain the decision.
Trust Center, HIPAA
Investigate an AI decision with the policy check, the review, and the reported outcome in front of you, and with clinical detail kept out of the record whenever the decision did not need it.
A review may need a policy result and case reference, not a clinical note. Select the fields needed to explain the decision.
Field selection and supported redaction help limit sensitive content. Review a sample export to see what your team will receive.
Use the managed service or deploy in your Azure subscription. Discuss data requirements and Business Associate Agreement (BAA) terms with the review team.
Bring access, decision records, and integrity checks into the same review. The HHS Security Rule overview explains the broader safeguard requirements.
Scroll horizontally to see all columns.
| Review area | How VeriProof helps |
|---|---|
| Audit controls | Follow linked decisions, timestamps, policy results, and review activity. |
| Access control | Limit access through portal roles and tenant separation, with records of administrative activity. |
| Integrity | Check evidence against Azure SQL Database Ledger proofs, or Solana proofs if your environment uses them. |
| Transmission security | Connect through encrypted endpoints and the network controls of your chosen deployment. |
| Retention and deletion | Manage how long application records are kept, with export and deletion options for your deployment. |
The connected application decides which fields it sends. Use stable references where a reviewer does not need the underlying clinical content.
Configure redaction for selected sensitive values. Together with field selection, it keeps the review focused on the decision. Test it with the fields and formats your workflow uses.
Use hosted VeriProof today. Private Enterprise, coming soon to Azure Marketplace, will run entirely in your own Azure subscription, completely separate from VeriProof SaaS.
Azure SQL Database Ledger is the default proof provider. An environment set up with Solana publishes only a fingerprint and transaction metadata, not the decision content.
Connect the facts your application supplies to the questions your team handles every day.
Why was a request referred for review? Keep the policy result with the reviewer’s response and the outcome reported by the application.
What did the practitioner do after reviewing the recommendation? Connect the reported action to the model and policy context supplied by the application.
Which criteria applied? Include their version in the configured record so reviewers can follow the policy outcome and any human review.
Was the message allowed, changed, or stopped? Record the policy result and reported outcome without retaining the message body when it is not needed.
Bring AI decision evidence into your existing security and privacy reviews. Access controls, selected records, and integrity checks support your team's assessment.
Your application determines which information it sends. A case reference and policy result can provide useful context without including the full patient record.
BAA terms are agreed for your deployment during contracting, before any ePHI is sent. Our security review team walks through the data flow with you. HHS explains when business associate agreements are required.
Soon. Private Enterprise is coming to Azure Marketplace. It will run entirely in your own Azure subscription, completely separate from VeriProof SaaS, so decision records and their integrity ledger stay there.
Yes. Give investigators selected decision records and integrity checks in one pack, ready to examine alongside the case's other evidence.
Which AI decision does your team need to explain? Explore the policy checks, human review, and evidence that can support it.