Assisted registration (For hybrid / matched portals)

Assisted Registration helps prospect Portal users to create their account, by not asking them to type in their full set of identity attributes on HSID registration UI page. This is similar to Fast track registrationin the next section; however, Assisted registration is useful for the following cases:

• The account registration (Email / SMS) invite is currently sent by 3rd party application, and that application is not able to use Fast Track Registration API call directly. However, the portal can capture 3rd party application’s invitation token and extract the set of prospect user’s identity attributes.
• Portal does not know a full set of prospect users’ identity attributes.
• The assistance of registration is done in real-time, initiated from the portal (i.e. not Email / SMS based invitation), therefore there is no need to track the usage of the invitation link.
  

Here are the general steps of Assisted registration flow:

• Portal knows or collects prospect users’ identity attributes, either fully or partially.
• (Optional but strongly recommended): If a known set of identity attributes contains Big4 (FN/LN/DOB/search_keys identifier and assigningAuthority when applicable), then search EiMP golden record (GR) by HCP userservice search, retrieve all known EiMP person identity attributes, and perform the authorization check of the portal.
  • When the user’s EiMP GR and authorization is confirmed, then go to the next step.
  • When the user’s EiMP GR is not found, Portal has an option to create or update a golden record in EiMP for the user. (EiMP consultation / API call is required).
• After that, Portal will pass the Big4 (FN/LN/DOB/ search_keys identifier and assigningAuthority when applicable), email, phone number to HSID/Aikyam to initiate assisted registration. Assisted Registration does not require a complete set of attributes. If some attributes are missing, the prospect user needs to fill in by themselves.
• Assisted Registration will be achieved by initiating a registration OIDC (prompt=create) call and passing along the identity information in “login_hint” parameter.
• The prospect user skips the input of the provided identity attributes in login_hint token during the registration flow.