Telehealth Identity Verification | MyProof
MyProof verifies patient or provider identity and assigned identity-policy predicates. It does not establish professional licensure, clinical credentials, employment, or authorization to practice.
Never sent during verification
- Medical history
- Diagnosis
- Treatment record
- Full ID record
Best for
- Telehealth intake where identity assurance matters but PHI scope should stay narrow.
- Patient account recovery, high-risk visit types, and provider identity checks before an access workflow.
- Healthcare teams that want a founder-led pilot scoped directly with Dr. Hollins.
Not for
- Replacing a provider's full HIPAA compliance program.
- Collecting or storing medical history, diagnosis, treatment, or payment records.
- Clinical authorization decisions that require medical judgment.
- Professional licensure, clinical credential, employment, or authorization-to-practice checks.
Legacy IDV vs MyProof
| Legacy IDV |
MyProof |
| Upload ID images into a vendor workflow, then store or reconcile the identity record. |
Evaluate the identity policy on the user's phone and return only the proof result needed for check-in. |
| Treat patient identity as another data object inside the clinical workflow. |
Keep identity proofing separate from medical records and minimize what the healthcare system receives. |
| Increase PHI-adjacent exposure every time a new identity copy is retained. |
Reduce the data surface by keeping medical history and full ID records out of the verification payload. |
Keep patient identity separate from the medical record
Patient identity proofing can support telehealth intake, sensitive account recovery, and high-risk access without collecting diagnosis, treatment history, or the full identity record in the verification payload. The verification question should be narrower than the clinical workflow around it.
Supported document processing, face match, liveness risk signals, and policy evaluation happen on the patient's phone. The healthcare workflow receives the configured identity result and receipt reference.
What HIPAA alignment does and does not mean
HHS describes minimum necessary as a reasonableness standard for limiting many uses, disclosures, and requests for protected health information. A lower-data identity layer can support that strategy, but it does not make the provider automatically HIPAA compliant.
Providers remain responsible for security risk analysis, policies, safeguards, vendor management, exception handling, and determining how HIPAA applies to their workflow.
- Keep medical history out of the identity-verification request.
- Request only the identity facts needed for intake or access.
- Document the vendor boundary and retained receipt data.
- Maintain provider safeguards and a human exception path.
Questions for a telehealth pilot
Test where the check appears in the patient journey, which document modes are supported, how failed checks are reviewed, what accessibility path exists, and what data reaches each system.
Frequently asked questions
How does MyProof help telehealth identity verification?
MyProof verifies identity and assigned identity-policy predicates such as age or document validity while keeping raw ID data out of the partner API result.
Does MyProof store medical history?
No. Medical history is not part of the verification payload and is never sent through the phone visualized flow. MyProof is focused on identity proofing and data minimization.
Can telehealth teams verify both patients and providers?
MyProof can verify the identity of a patient or provider. It does not verify the provider's license, clinical credentials, employment, or authorization to practice.
Is MyProof a complete HIPAA compliance product?
No. MyProof supports a privacy-preserving verification architecture and data minimization, but it does not replace a provider's full HIPAA compliance program.
Is MyProof HIPAA-appropriate for patient identity verification?
MyProof can support a healthcare team's data-minimization strategy by keeping medical history and full ID records out of the verification result. Each provider remains responsible for its own HIPAA risk analysis, policies, contracts, and compliance program.
Does MyProof collect medical history to verify a patient?
No. Medical history, diagnosis, and treatment records are not needed for the MyProof identity check. The workflow receives the requested proof result rather than those clinical records.
Canonical page: https://myproof.ai/telehealth-identity-verification