Skip to main content

Why do I need to ID proof to use Kno2?

How ID verification creates a trusted network to safely share PHI

Stacy Lane avatar
Written by Stacy Lane
Updated yesterday

This article explains why identity verification (ID proofing) is required . You'll understand the regulatory requirements and security benefits of this verification process.

What is Identity Verification

Identity verification, also known as ID proofing, is a security process that confirms you are who you claim to be before granting access to healthcare systems. This process validates your identity using official documents and third-party verification services.

Kno2 requires this verification to meet federal security standards and protect patient health information during electronic exchanges.

Why Identity Verification is Mandatory

Federal Security Requirements: Kno2 must comply with IAL2 (Identity Assurance Level 2) standards as defined by:

  • OMB (Federal Office of Management and Budget)

  • NIST (National Institute of Standards & Technology)

Healthcare Network Security: Identity verification is required because your app connects to networks that exchange confidential patient information with other healthcare providers, including Direct Messaging systems.

HIPAA Compliance: Under HIPAA regulations, participants in healthcare networks must confirm the validity and confidence of user identities within their organization.

What IAL2 Requirements Mean

Identity Assurance Level 2 requires:

  • Identity verification and validation of an individual

  • Confirmation that the person is approved to represent the entire healthcare organization

  • Verification before any activity can be conducted within the application

  • Third-party validation using approved verification services

This verification ensures:

  • Only authorized individuals access healthcare information systems

  • Organizations can trust the identity of people they exchange information with

  • Patient data remains protected during electronic transfers

The Identity Verification Process

Verification Service: Kno2 users CLEAR as the identity verification vendor. CLEAR provides secure, automated identity verification services that meet federal standards.

When Verification Occurs:

  • Identity verification is required for activation of your organization's account

  • Verification must be completed before any activity can be conducted

  • This is a one-time process during initial setup

What Gets Verified:

  • Your personal identity information

  • Your authority to represent your healthcare organization

  • Your eligibility to access protected health information

How Identity Verification Creates Trust

Nationwide Network Security: Identity verification allows a nationwide "trust" to be established across healthcare providers. When organizations know that all participants have been properly vetted, they can safely exchange sensitive patient information.

Protection for All Users: This requirement protects ALL users of Direct messaging and healthcare information exchange by ensuring that any technology solution provider exchanging health information online properly vets their end users.

Secure Information Exchange: Verified identities enable secure exchange of:

  • Patient medical records

  • Lab results and diagnostic reports

  • Referral information

  • Treatment summaries

  • Insurance and authorization documents

Regulatory Background

Federal Requirements: Healthcare information exchange systems must comply with strict identity verification requirements to participate in national networks and meet meaningful use criteria.

HIPAA Protection: Identity verification is a critical component of HIPAA compliance, ensuring that only authorized individuals can access and exchange protected health information.

Direct Messaging Standards: The Direct messaging protocol, used for secure healthcare communication, requires Level 3 Assertion/Identity Verification for all participants.

Third-Party Standards & Resources

HealthIT.gov Guidelines: Federal health IT resources provide detailed guidance on ID proofing requirements for healthcare providers participating in Direct messaging networks: HealthIT.gov

Industry Best Practices: Healthcare industry standards consistently require identity verification for systems that exchange patient information electronically: Certificate Issuance and Assurance in Direct Messaging (page 6, Identity Proofing for Healthcare Providers)

National Network Participation: To join national healthcare information exchange networks, organizations must demonstrate that their users have been properly identity verified: Direct Implementation Guidelines (Page 3, Item 6)

What This Means for Your Organization

Enhanced Security: Identity verification ensures that your organization maintains the highest security standards when exchanging patient information with other healthcare providers.

Regulatory Compliance: Meeting identity verification requirements helps your organization comply with federal healthcare IT regulations and HIPAA requirements.

Network Access: Proper identity verification enables your organization to participate in secure healthcare information exchange networks and communicate with other verified providers.

Patient Trust: Patients can be confident that their health information is only accessible to properly verified healthcare professionals and organizations.

The Verification Process Steps

Initial Account Setup:

  1. Your organization administrator begins the account setup process

  2. Identity verification is required before the account can be activated

  3. The verification process uses CLEAR's secure identity verification system

Automated Verification:

  1. Personal information is submitted through secure channels

  2. CLEAR automatically verifies identity using multiple data sources

  3. Most verifications are completed quickly through this automated process

Manual Review (If Needed):

  1. If automated verification is unsuccessful, manual review may be required

  2. Additional documentation may be requested to complete verification

  3. All submitted information is kept secure and confidential

Privacy and Security Protections

Data Protection:

  • All identity verification information is handled securely

  • Personal data is protected according to federal privacy standards

  • Information is only used for verification purposes

Limited Access:

  • Only authorized verification personnel have access to submitted information

  • Data is not shared with unauthorized parties

  • Information is retained only as required by regulations

Secure Processing:

  • All verification activities use encrypted, secure connections

  • Industry-standard security practices protect your information

  • Regular security audits ensure ongoing protection

Benefits of Identity Verification

Secure Healthcare Network: Verified identities create a secure network where healthcare providers can safely exchange patient information with confidence.

Reduced Fraud: Identity verification helps prevent unauthorized access to healthcare systems and protects against identity fraud in medical settings.

Improved Patient Safety: When healthcare providers can trust the identity of those they communicate with, patient safety improves through more secure information sharing.

Streamlined Communication: Once verified, healthcare providers can communicate efficiently and securely without questioning the legitimacy of their communication partners.

Understanding the Requirements

Not Optional: Identity verification is not an optional security feature—it's a mandatory requirement for participating in secure healthcare information exchange.

One-Time Process: While the verification process may seem involved, it's typically a one-time requirement during initial account setup.

Industry Standard: All legitimate healthcare information exchange systems require similar identity verification to meet federal security standards.

Investment in Security: The verification process represents an investment in the security and integrity of the entire healthcare information exchange network.

Did this answer your question?