If your organization is planning to send a bulk file of credentials into the Passport System, you have the ability to either:
a) use our preset codes to represent common licenses, certificates, and documents
b) set up your own system of language or codes that is more meaningful to your organization
How does it work?
The following file specifications outline how you can bulk import a large set of codes and identifiers that match the values you are used to. From there, you can set up a mapping or translation to our standard types of credentials.
Below we will reference the "Integration Mappings" tab in Passport. The tab is restricted to only certain users, but those with access can locate the tab HERE. The following instructions outline how to manage these mappings in bulk, but these mappings can also be managed directly in the product one at a time.
This General Mapping File will now enable bulk adding, updating, and deleting of the following integration mappings in Passport:
- License Type
- License Issuer
- Certificate Type
- Document Type
| Column Name | Description |
| Org_id |
Required: This Organization ID is the Unique ID that identifies each client in Passport. The numerical Organization ID can be found on the Integration Tab under Integration Mappings. Ex. 43352 |
| Mapping Type |
Required: This will be one of the four types of mappings listed near the top of this article. Only one type can be entered per row, but you can have more than type in the same upload file. Must be either:
|
| ProviderTrust Code |
Required: The official ProviderTrust code for a particular mapping. This is pre-set on the ProviderTrust side. A list of all currently available codes can be found by exporting ProviderTrust Codes at the bottom of each Integration Mappings section. The format will almost always be three letters, then a dash, then numerical digits. Ex. LIC-0018 There is a more rare use case where the intention of the row is to delete an incomplete mapping. Incomplete mappings are created if a file is uploaded unsuccessfully with a code that has not yet been defined. If the desire of this row is to delete an incomplete mapping, this cell will be populated with the value "Not Mapped". A list of incomplete mappings can be exported from the Integration Mappings UI. There is no support to manually add or update an incomplete mapping through this file. |
| Facility Code |
Required: This field is for the code, word, or identifier that will be used on a future credential file. This is the client's preferred value to represent a particular license type, issuer, certificate, or document. Ex. OT |
| Facility Integration ID |
Optional: This field is to identify which locations this mapping is valid for. If the intention is to set up a mapping to apply to ALL facilities, leave the cell blank. When deleting an incomplete mapping, leave the cell blank. When the intention is to assign this mapping to only one facility, please include the official Facility ID here. The Facility ID can be the system generated ID or a mapped ID if that has already been configured before this file is being submitted. Ex. 6677 East Building |
| Delete |
Optional: For adding or updating a mapping, this field will be left empty. If the desire is to delete a complete or incomplete mapping that already exists, please populate this field with the lowercase word delete. Ex. delete |
Trying to map all 50 states for license issuers? We've attached a template of commonly used license issuer codes for states. Simply add your organization ID and upload.
