3.3.1 Attribute Mappings for the Target Application

The Schema page for a target application displays the default schema (provided by the connector) that maps Oracle Identity Governance attributes to target system attributes. The connector uses these mappings during reconciliation and provisioning operations.

The following table lists the user-specific attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes The table also lists whether a specific attribute is used during provisioning or reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application Creating a Target Application of Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-3 Default Attribute for Cerner Health Data Intelligence Target Application

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Provision Field?	Recon Field?	Key Field?	Case Insensitive?
id	__UID__	String	No	No	Yes	Yes	No
Full Name	name.formatted	String	No	No	Yes	No	Not applicable
First Name	name.given	String	Yes	Yes	Yes	No	Not applicable
Last Name	name.family	String	Yes	Yes	Yes	No	Not applicable
Birth Date	birthDate	String	No	Yes	Yes	No	Not applicable
Gender	gender	String	No	Yes	Yes	No	Not applicable
IT Resource Name		Long	No	No	Yes	No	Not applicable

The following figure shows the default User account attribute mappings.

Figure 3-1 Default Attribute Mappings for Cerner Health Data Intelligence User Account

Cerner Health Data Intelligence Languages

The following table lists the Languages forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-4 Default Attribute Mappings for Languages

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Languages	languages	String	No	Yes	Yes	No

The following figure shows the default Languages mapping.

Figure 3-2 Default Attribute Mappings for Cerner Health Data Intelligence

Cerner Health Data Intelligence Emails

The following table lists the Emails forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-5 Default Attribute Mappings for Emails

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Email Type	emailAddresses~emailAddresses~type	String	No	Yes	No	Not Applicable
Email Value	emailAddresses~emailAddresses~value	String	No	Yes	Yes	No

The following figure shows the default Emails mapping.

Figure 3-3 Default Attribute Mappings for Cerner Health Data Intelligence Emails

Cerner Health Data Intelligence Phone Number

The following table lists the Phone Number forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-6 Default Attribute Mappings for Phone Number

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Phone Number Type	phoneNumbers~phoneNumbers~type	String	No	Yes	No	Not Applicable
Phone Number Value	phoneNumbers~phoneNumbers~value	String	No	Yes	Yes	No

The following figure shows the default Phone Number mapping.

Figure 3-4 Default Attribute Mappings for Cerner Health Data Intelligence Phone Number

Cerner Health Data Intelligence Aliases

The following table lists the Aliases forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Healtheintent target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-7 Default Attribute Mappings for Aliases

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Alias Type	aliases~aliases~type	String	No	Yes	No	Not Applicable
Alias Value	aliases~aliases~value	String	No	Yes	Yes	No
Alias Assigning Authority	aliases~aliases~system	String	No	Yes	No	Not Applicable

The following figure shows the default Aliases mapping.

Figure 3-5 Default Attribute Mappings for Cerner Health Data Intelligence Aliases

Cerner Health Data Intelligence Personnel IDs

Below table lists the Personnel IDs forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-8 Default Attribute Mappings for Personnel IDs

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Source Record ID	sourceIdentifiers~sourceIdentifiers~id	String	No	Yes	Yes	No
Data Partition ID	sourceIdentifiers~sourceIdentifiers~dataPartitionId	String	No	Yes	No	Not Applicable

The following figure shows the default Personnel IDs mapping.

Figure 3-6 Default Attribute Mappings for Cerner Health Data Intelligence Personnel IDs

Cerner Health Data Intelligence Personnel Groups Entitlement

Below table lists the Personnel Groups forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-9 Default Attribute Mappings for Personnel Groups

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Group Id	__GROUP__~__GROUP__~id	String	No	Yes	Yes	No
Group Name	__GROUP__~__GROUP__~name	String	No	Yes	No	Not Applicable
Mnemonic	__GROUP__~__GROUP__~mnemonic	String	No	Yes	No	Not Applicable
Mnemonic Type	__GROUP__~__GROUP__~mnemonicType	String	No	Yes	No	Not Applicable

The following screenshot shows the default Personnel IDs mapping.

Figure 3-7 Default Attribute Mappings for Cerner Health Data Intelligence Personnel Groups

Cerner Health Data Intelligence Organization Entitlement

Below table lists the Organization forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-10 Default Attribute Mappings for Organization

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Organization Id	__ORGANIZATION__~__ORGANIZATION__~id	String	No	Yes	Yes	No
Organization Name	__ORGANIZATION__~__ORGANIZATION__~name	String	No	Yes	No	Not applicable

The following figure shows the default Organization Entitlement mapping.

Figure 3-8 Default Attribute Mappings for Cerner Health Data Intelligence Organization

Cerner Health Data Intelligence Personnel Group Views

The below table lists the Personnel Group View forms attribute mappings between the process form fields in Oracle Identity Governance and Cerner Health Data Intelligence target application attributes. The table lists whether a given attribute is mandatory during provisioning. It also lists whether a given attribute is used during reconciliation and whether it is a matching key field for fetching records during reconciliation.

If required, you can edit the default attribute mappings by adding new attributes or deleting existing attributes as described in Creating a Target Application in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance.

Table 3-11 Default Attribute Mappings for Personnel Group Views

Display Name	Target Attribute	Data Type	Mandatory Provisioning Property?	Recon Field	Key Field?	Case Insensitive?
Personnel Group Views Id	__DYNAMICGROUP__~__DYNAMICGROUP__~id	String	No	Yes	Yes	No
Personnel Group Views Name	__DYNAMICGROUP__~__DYNAMICGROUP__~name	String	No	Yes	No	Not Applicable
Mnemonic	__DYNAMICGROUP__~__DYNAMICGROUP__~mnemonic	String	No	Yes	No	Not Applicable
Mnemonic Type	__DYNAMICGROUP__~__DYNAMICGROUP__~mnemonicType	String	No	Yes	No	Not Applicable

The following figure shows the default Personnel Group Views mapping.

Figure 3-9 Default Attribute Mappings for Cerner Health Data Intelligence Personnel Group Views