Skip to content

Schema Reference

The application schema is used to configure the objects returned from a connector.

Note

  • The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.

  • The schema attributes that are not present by default must be defined as strings if not specified.

The Cerner Healthcare connector uses the following default correlation and object configurations.

Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.

Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.

Caution

Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.

To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

Account ID Schema Object Type
ID (numeric) Account
Id Group
Id organizationGroup

Account Attributes

The Cerner Healthcare connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

Attribute Name Description
ID Identifies an object that exists on a target that is exposed by a provider. This is an Account ID which must not be changed.
username The user name associated with the account. The value of the user name field must be unique within the target Cerner Millennium domain. Can be any value between 1 and 48 characters.
directoryIndicator Contains an indicator on whether the user is an LDAP directory user or not. Values: True (LDAP user), False (non-LDAP user).
birthdate Personnel's birthdate.
firstname Personnel's first name.
lastname Personnel's surname (last name).
middleName Personnel's middle name.
displayName Personnel's display name.
suffix Personnel's suffix.
privilege Privileges assigned to the Cerner account.
gender A coded value representing the gender of the personnel.
restriction A restriction to be assigned to or unassigned from the account.
title Personnel's title (or list of titles). For example, Dr., Mrs., or Mr.
physicianInd An indicator if the personnel is a physician or not.
position A coded value representing the position assigned to the personnel that is treated as a Group entity.
beginEffectiveDateTime Date and time at which the personnel becomes or became effective.
endEffectiveDateTime Date and time at which the personnel ceases or ceased to be effective.
organization Group When a personnel record is unassigned from an organization group, all organizations in the group are also unassigned from the personnel record, unless they are associated to another organization group that is still assigned to the personnel. It is a read-only field and data is displayed during account aggregation.
confidentialityLevel A coded value representing the confidentiality code that applies to the relationship.
personnelAlias Personnel alias information.
personnelGroup Contains personnel group information.
credential Credentials are used to highlight the level of education and specialty of a care provider.
email Personnel's email address.
roleProfile Role profile information with multiple positions that applies to the relationship. For an already existing source, the user must add the roleProfile attribute manually.

Adding a Roleprofile Schema Attribute

  1. In the Account Management section, select Account Schema.
  2. Select Add New Attribute. The Add Attribute window appears.
  3. Enter the following details:
    • Name: roleProfile
    • Type: string
    • Description: Contains role profile information
    • Attribute Property: Multi-Valued
  4. Select Save to apply the changes.

Including Permissions in Account Schema

When permissions are aggregated (for example, when includePermissions="true" is set to true in the account schema definition and the privilege attribute is included in the account schema), the permissions are aggregated under the directPermissions attribute, not the privilege attribute itself. This data is not visible in the UI but is included in the link or identity XML/JSON.

Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to Managing Entitlements for more information.

Caution

Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

Default Group Attributes

The Cerner Healthcare connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.

Attribute Name Description
ID The Id of the group. This is an Account ID which must not be changed.
Display Display name of the group.

Default Organization Group Attributes

Attribute Name Description
Id Unique identifier of the organization group. This is an Account ID which must not be changed.
Display Display name of the group.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.