---
title: Flow Reference
description: Learn about the flows included in the Healthcare flow pack and find links to reference documentation about them.
component: pingone-solutions
page_id: pingone-solutions:healthcare:flow-reference/healthcare-flow-reference
canonical_url: https://docs.pingidentity.com/pingone-solutions/healthcare/flow-reference/healthcare-flow-reference.html
revdate: January 29, 2025
page_aliases: ["flow-reference/index.adoc"]
---

# Flow Reference

The Healthcare flow pack solution uses three main flows and multiple subflows. This section explains what each flow does and how it works.

A DaVinci flow consists of nodes, each of which presents a page to the user, performs a backend action, or launches another flow. These nodes are connected by logical operators, allowing you to construct a user journey such as authenticating with a known device or making a transfer.

The flows included in the Healthcare flow pack solution are designed to work together to provide the solution. They require no configuration beyond that described in [Configuring flows in DaVinci](../getting-started/healthcare-configuring-flows-in-davinci.html). However, you can customize these flows to provide additional services to your end users. Learn more in [How To Manage Flows](https://docs.pingidentity.com/davinci/flows/davinci_how_to_manage_existing_flows.html) in the PingOne DaVinci documentation.

The main section of the Healthcare flow pack solution contains the following flows:

* [Healthcare - Registration with Threat Detection and ID Verification - Main Flow](healthcare-registration-with-threat-detection-and-id-verification-main-flow.html)

  This flow is the beginning of the process by which a user registers a new account. It's meant to be invoked directly.

  * [Healthcare - Account Registration - Subflow](healthcare-account-registration-subflow.html)

    This flow lets users register an account.

  * [Healthcare - Agreement (ToS) - Subflow](healthcare-agreement-tos-subflow.html)

    This flow lets users read and agree to any agreements required by the environment.

  * [Healthcare - Identity Verification and Managed Credential Issuance with Biometric Binding - Subflow](healthcare-identity-verification-and-managed-credential-issuance-with-biometric-binding-subflow.html)

    This flow uses PingOne Verify to verify the user and issue credentials.

  * [Healthcare - Pair A Digital Wallet - Subflow](healthcare-pair-a-digital-wallet.html)

    This flow lets users pair a new digital wallet.

  * [Healthcare - Registration with Threat Detection and ID Verification - Main Flow](healthcare-registration-with-threat-detection-and-id-verification-main-flow.html)

    This flow lets users register an account after performing threat detection and ID verification.

  * [Healthcare - Threat Detection - Subflow](healthcare-threat-detection-subflow.html)

    This flow uses PingOne Protect to perform a threat assessment of the user.

  * [Healthcare - Verify Email - Subflow](healthcare-verify-email-subflow.html)

    This flow lets users verify their email address using PingOne SSO.

* [Healthcare - Progressive Verification during Authentication - Main Flow](healthcare-authentication-with-username-and-password-main-flow.html)

  This flow is the beginning of the process by which a user signs on. It's meant to be invoked directly.

  * [Healthcare - Progressive Verification during Authentication - Agreement (ToS) - Subflow](healthcare-authentication-agreement-tos-subflow.html)

    This flow lets users read and agree to any agreements required by the environment.

  * [Healthcare - Progressive Verification during Authentication - Change Password - Subflow](healthcare-authentication-change-password-subflow.html)

    This flow lets users change their password.

  * [Healthcare - Progressive Verification during Authentication - Device Authentication - Subflow](healthcare-authentication-device-authentication-subflow.html)

    This flow lets users authenticate using a known device.

  * [Healthcare - Progressive Verification during Authentication - Device Registration - Subflow](healthcare-authentication-device-registration-subflow.html)

    This flow lets users register a new device.

  * [Healthcare - Progressive Verification during Authentication - Magic Link Authentication - Subflow](healthcare-authentication-magic-link-authentication-subflow.html)

    This flow lets users authenticate using a magic link.

  * [Healthcare - Progressive Verification during Authentication - SignOn - Subflow](healthcare-authentication-signon-subflow.html)

    This flow lets users sign on.

  * [Healthcare - Progressive Verification during Authentication - Threat Detection - Subflow](healthcare-authentication-threat-detection-subflow.html)

    This flow uses PingOne Protect to perform a threat assessment of the user.

  * [Healthcare - Progressive Verification during Authentication - Verify Email - Subflow](healthcare-authentication-verify-email-subflow.html)

    This flow lets users verify their email address using PingOne SSO.

* [Healthcare - CSR Help Desk - Main Flow](healthcare-csr-help-desk-main-flow.html)

  This flow is the beginning of the process by which customer service representatives assist users with account management. It's meant to be invoked directly by the CSR.

  * [Healthcare - CSR Help Desk - Verify User Magic Link Authentication - Subflow](healthcare-csr-help-desk-verify-user-magic-link.html)

    This flow verifies the user using a magic link.

  * [Healthcare - CSR Help Desk - Change Password - Subflow](healthcare-csr-change-password-subflow.html)

    This flow enables the CSR to have the user's password changed.

  * [Healthcare - CSR Help Desk - Active Directory - User Functions API - Subflow](healthcare-csr-active-directory-user-functions-api-subflow.html)

    This flow takes account management actions such as enabling or disabling the user account based on parameters passed by other flows.

  * [Healthcare - CSR Help Desk - Password reset Magic Link - Subflow](healthcare-csr-password-reset-magic-link-subflow.html)

    This flow enables the CSR to reset the user's password with a magic link.

  * [Healthcare - CSR Help Desk - Device Authentication - Subflow](healthcare-csr-device-authentication-subflow.html)

    This flow lets the CSR perform device authentication for the user.