How does the registration flow work with IQVIA Extension?
Email and consents
In order to start an account registration process the user needs to provide a valid email address and consent (depending on environment configuration) in order to continue. This step is crucial because of possible environment configuration settings available in order to remind the user to proceed with the setup of their account.
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
Profession type, -specialty, -association (optional) and license number(s)
After the user has provided all necessary credentials, we'll attempt multiple lookup queries with IQVIA in order to check if this user exists in their databases. All results will be checked until we're able to uniquely identify one user identity with correct activity status codes.
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
These fields have been removed, these details are available after completing the profession mapping setup.
Personal name
After the user has provided all necessary credentials, we'll attempt multiple lookup queries with IQVIA in order to check if this user exists in their databases. All results will be checked until we're able to uniquely identify one user identity with correct activity status codes.
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
This field can be removed, this question relates to most Germanic countries where name has last name prefixes.
Practise / organization address
After the user has provided all necessary credentials, we'll attempt multiple lookup queries with IQVIA in order to check if this user exists in their databases. All results will be checked until we're able to uniquely identify one user identity with correct activity status codes.
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
Password and password confirmation
This step does not do anything with IQVIA but we'll need to confirm this step in order for the user to authenticate in the future, if not the user would have to request a new password, please see dedicated article about password reset.
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
Email verification
Upon arrival through the registration/onboarding process the email is automatically sent to the user to verify the provided email address in order for them to continue on. If the user has not received any email or it has expired already the user is able to request a new verification email by clicking "Send again" button (depending on environment and translation settings).
If needed an administrator can also manually verify their email address from the administration panel, please see the dedicated article for this on how to do so.
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
Email verification template sent to user
Any other text that you see in the image above is adjustable per environment using language overrides.
Details have been removed, all details are adjustable using configuration settings per environment.
Addressed with variable input from the tenant environment, such as Dear {{FIRST_NAME}} for example.
Submission of validation request (manual HCP lookup by IQVIA)
There is no image available for the submission of the validation requet, this will only be requested when there is no direct identification possible with all input provided by the user themselves. There is the possibility for this user to be identified in the background, once identified and checks have passed the user is automatically updated in order for them to continue as an IQVIA verified user.