Account Attributes

The following lists the account attributes:

Identifies an object that exists on a target that is exposed by a provider

This is an Account ID which must not be changed.

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.

Contains an indicator on whether the user is an LDAP directory user or not.

  • True (LDAP user)
  • False (non-LDAP user)

Personnel's birthdate.

Personnel's first name.

Personnel's surname (last name).

Personnel's middle name.

Personnel's display name.

Personnel's suffix.

Privileges assigned to the Cerner account.

A coded value representing the gender of the personnel.

A restriction to be assigned to or unassigned from the account.

Personnel's title (or list of titles). For example, Dr., Mrs., or Mr.

An indicator if the personnel is a physician or not.

A coded value representing the position assigned to the personnel that is treated as a Group entity.

Date and time at which the personnel becomes or became effective.

Date and time at which the personnel ceases or ceased to be effective.

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.

A coded value representing the confidentiality code that applies to the relationship.

Personnel alias information.

Contains personnel group information.

Credentials are used to highlight the level of education and specialty of a care provider.

Personnel's email address.

Include 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.