Skip to main content

Create an Account

The Create Account screen registers a new patient when the provided email address does not match an existing account.

The platform returns this screen from the Log in flow when the email is not associated with an existing identity. Navigation depends on the integration level and is handled by the host application or the SDK.

This screen includes

  • Email address field — required identifier used to create the patient account.
  • First name field — required field for the patient’s given name.
  • Last name field — required field for the patient’s family name.
  • Password field — required credential subject to platform password policy.
  • Terms of Use and Privacy Policy consent checkbox — mandatory consent required before account creation.
  • Marketing opt-in checkbox — optional user preference for marketing communication.
  • Continue with email button — submits the account creation request.
  • Log in link — redirects the user to the Login screen if an account already exists.
Existing account

If the email address already exists, the platform rejects the registration request.
Redirect the user to the Login flow.

Navigation ownership depends on the selected integration level.

After successful registration, the platform may:

  • continue the onboarding workflow,
  • redirect to the next application route, or
  • return navigation control to the host application.

Workflow​

  1. Launch the Air Doctor Patient App from the host application entry point.
  2. Select Log in.
  3. The platform evaluates the submitted email address.
  4. If the email does not match an existing account, the Create Account screen appears.
  5. Enter the required identity information:
    • Email address
    • First name
    • Last name
    • Password
  6. Select the Terms of Use and Privacy Policy consent checkbox.
    The form cannot be submitted until consent is provided.
  7. Optionally select the marketing opt-in checkbox.
  8. Select Continue with email to submit the registration request.
  9. The platform validates the request.
    • If validation succeeds, the platform creates the patient identity and establishes an authenticated session.
    • If validation fails, the UI displays an error message and allows the user to correct the input.

Validations​

Validation enforcement

Validation occurs at two levels:

  • Client-side validation blocks invalid submissions.
  • Platform validation enforces identity, policy, and security rules.

The Air Doctor platform is the authoritative source of validation decisions.

Validations​

ConditionApp BehaviorSDK Output
Email format is invalid.The form blocks submission and highlights the email field.Validation error indicating invalid email format.
Email already exists.Account creation is rejected and the screen prompts the user to return to login.Error response indicating existing account.
First name or last name is missing.Submission remains disabled and the required field is highlighted.Validation error indicating missing required field.
Password does not meet complexity rules.Submission remains disabled and the password field displays a validation message.Validation error indicating invalid password format.
Terms of Use consent is not selected.Submission remains disabled until consent is provided.Validation error indicating missing consent.
Request violates identity or security policy.The screen displays an error state.Error response identifying invalid registration request.

Actions​

ConditionApp BehaviorSDK Output
User submits valid registration data.The screen transitions to the next onboarding state.Runtime update creating the patient identity and establishing an authenticated session.
Platform validation fails.The screen displays the returned validation error and allows the user to correct the input.Structured error response containing validation details.
Account creation succeeds.The platform continues onboarding or redirects to the next application screen.Runtime update with authenticated session context.
Error handling

Client applications must display validation errors returned by the platform and allow the user to correct the input.

Requests rejected by backend validation must not be retried automatically.

Session handling and navigation ownership depend on the configured integration level.

Endpoint Resources​

Signup​

POST 

/v3/account/create

Creates a new user account with email, password, personal details, and required agreements.