Searching OneKey Accounts from Global Account Search (Available on December 3, 2026)
End users can search the IQVIA OneKey database directly within Global Account Search to find and import HCPs and HCOs not currently loaded in Vault CRM. This allows users to preview account details, import OneKey-only records, and immediately log activities against newly imported accounts without additional data entry.
Who can use this feature?
- End Users — Browser
- Searching OneKey Accounts from Global Account Search
- Importing OneKey Accounts from Global Account Search
- Users require access to the OneKey Webservices API
Configuring OneKey Account Searches from Global Account Search for
To configure this feature:
- Ensure Global Account Search is configured.
- Navigate to Admin > Users & Groups > Permission Sets.
- Select the appropriate permission set.
- Select Objects.
- Grant the following permissions:
Object Object Permission Object Type Fields Field Permission account__v
CRE
All applicable object types
- onekey_id__v
- onekey_specialty_code__v
- data_source__v
- first_name_cda__v
- last_name_cda__v
- middle_name_cda__v
- country_code__v
- ispersonaccount__v
- account_identifier__v
- primary_parent__v
Read
address__v CRE All applicable object types - onekey_id__v
- onekey_sub2_code__v
- onekey_sub3_code__v
- city_cda__v
- postal_code_cda__v
- country__v
- primary_cda__v
Read child_account__v CRE All applicable object types - onekey_id__v
- child_account__v
- parent_account__v
Read manual_territory_alignment_history__v CRE All applicable object types - data_source__v
Read - Navigate to Business Admin > Objects > Global Account Search Settings.
-
Populate the onekey_connector_host__v Global Account Search Setting with one of the following values depending on the environment:
- okws.ok.imshealth.com (Production)
- okws-qa.ok.imshealth.com (Staging)
If no value is populated on this field, the Production value is used.
- Select All from the onekey_connection_scope__v picklist.
- Enter the OneKey connector ID in the onekey_connector_id__v field.
- Enter the object type api name for HCO records in the onekey_hco_object_type__v field.
- Enter the object type api name for HCP records in the onekey_hcp_object_type__v field.
- Enter the object type api name for Address records in the onekey_address_object_type__v field.
Vault Platform Integration
The following Vault Platform configuration is required to support this feature:
- Navigate to Business Admin > Objects > Connections.
- Populate the IQVIA OneKey Connection with the appropriate Username and password for IQVIA OneKey WebServices.
Searching OneKey Accounts from Global Account Search as
End users can search OneKey reference data, preview matching accounts, and import additional records directly into Vault CRM.
To search for accounts in OneKey:
- Select the entity type (HCP or HCO) in Global Account Search. The All option is unavailable for OneKey searches because OneKey requires separate queries for HCPs and HCOs.
- Enter search criteria in the Search Terms field and Location field.
- Select Search Outside of CRM to run the query against IQVIA OneKey.
- Choose Search HCPs or Search HCOs from the dropdown menu.
- Select Search.
Search results display up to 50 records on Browser based on the end user's country. Search results automatically exclude inactive records.
Existing Vault CRM accounts matching OneKey records by onekey_id__v display in the Vault CRM results section only to prevent duplicates.
To preview account details, select a row in the search results list. The preview pane displays details for the selected account, including contact details, addresses, and parent HCO affiliations.
GAS User Filters and Implicit Filters do not apply to OneKey search results.
Importing OneKey Accounts from Global Account Search as
To import a OneKey record into Vault CRM:
- Select the Add to Territory button on a OneKey search result.
- Select the parent HCO affiliations to include with the import.
- Select Confirm.
The system creates the account record, populates mapped fields and OneKey IDs (onekey_id__v), creates associated address records, and adds the record to the OneKey population subscription. A manual_territory_alignment_history__v record is created with the data_source__v field set to iqvia__v to track account sourcing for MDM integrations.
Users can log calls or activities against the newly imported account immediately.

