Create Your Account


[SCREENSHOT — the Jiro Health registration page, showing the sign-up form with fields for first name, last name, email, and NPI]



Overview

Registering for Jiro Health takes approximately five to ten minutes and gives you immediate access to your personalized practice intelligence — your metrics, peer benchmarks, patient data, and clinical consultation tools, all anchored to your NPI. Registration requires identity verification to confirm licensure as a practicing physician.


What You'll Need

Before beginning registration, have the following ready:

  • Your full name as it appears on your record with NPPES.
  • Your NPI number (Type 1 — individual practitioner). Registration cannot be completed without a valid Type 1 NPI.
  • A valid email address you can access immediately. A one-time passcode will be sent to this address as part of the verification process.

The Registration Process

Step 1: Enter Your Information

Navigate to the Jiro Health registration page and complete the four required fields: first name, last name, email address, and NPI number. Select Sign Up to submit.

[SCREENSHOT — the completed registration form prior to submission]

Step 2: Verify Your Email

After submission, a one-time passcode is sent to the email address you provided. Enter the code on the verification screen to confirm your email address. The code is valid for 30 minutes. If it expires before use, a new code can be requested.

[SCREENSHOT — the email verification screen with the one-time passcode entry field]

Step 3: NPI Validation

Once your email is verified, Jiro Health validates your NPI automatically. This step confirms that:

  • The NPI is active and not expired
  • The name on the NPI record matches the name you entered
  • The NPI is not already associated with an active Jiro Health account

No action is required during this step. Registration advances automatically once validation is complete. If validation does not pass, you will receive a notification with the specific reason.

Step 4: Identity Verification via Plaid

After NPI validation, you are redirected to Plaid, a third-party identity verification service. Complete the prompts within Plaid's interface. On completion, you are automatically returned to Jiro Health.

[SCREENSHOT — the Plaid redirect prompt, showing the transition from Jiro Health to the Plaid interface]

Step 5: Create Your Password

After returning from Plaid, enter and confirm a password for your account.

[SCREENSHOT — the password creation screen]

Step 6: Account Activation

Once your password is set, your account is activated and you are logged in automatically.

[SCREENSHOT — the Jiro Health home screen immediately after account activation]


Consent Agreements

During registration, you will be prompted to review and accept four documents:

  • AI Governance Policy — describes how Jiro Health's data processing and clinical intelligence capabilities operate and interact with clinical data
  • Business Associate Agreement (BAA) — establishes Jiro Health's obligations under HIPAA with respect to protected health information
  • End User License Agreement (EULA) — defines the terms under which the Jiro Health platform may be used
  • Privacy Policy — describes how Jiro Health collects, uses, and protects personal data

All four documents must be accepted to complete registration. Each is accessible at any time from the Account tab in your profile after login.


Important To Remember

  • Jiro Health accounts are restricted to licensed physicians. The NPI validation step enforces this requirement; registration cannot proceed without a valid Type 1 NPI.
  • Each NPI can be associated with only one active Jiro Health account. If your NPI is already in use, contact Jiro Health support.
  • If a colleague shared a referral link with you, use that link rather than navigating directly to the registration page to ensure the referral is recorded.
  • For issues encountered during registration, see Account Access Issues in the Help Center or contact support directly.

Related Articles


Version History

Updated: April 22, 2026

Reviewed by: Caitlyn Edwards, Head of Communications

Approved by: [Name, Title]

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us