# SailPoint MEDITECH SaaS Connector Documentation > MEDITECH SaaS Connector Documentation # Documentation # Connecting SailPoint and MEDITECH SaaS To connect SailPoint with MEDITECH, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings Provide the information required to connect to the MEDITECH instance and who can access the information. OAuth2 with Client Credentials is the supported authentication and grant types. > [!NOTE] > > **Screenshot** > > [![Connection Settings]()]() 1. Enter the fully qualified URL of the MEDITECH instance in the **Host URL** field. 2. Enter the scopes to include when creating a token on MEDITECH in the **Scopes** field. Multiple scopes can be included as space separated values. For example, you can use: ```text meditech.users.read&meditech.users.manage&meditech.groups.read&meditech.groups.manage&meditech.schemas.read&meditech.roles.read.manage ``` 3. Enter the **Token URL** for token generation. For example: ```text https://{yourmeditechDomain}/oauth2/v1/token ---> https://{yourmeditechDomain}/oauth2/token ``` 4. Enter the values for OAuth2 authentication in the **Client ID** and **Client Secret** fields. For more information, refer to MEDITECH documentation. 5. Select **Save**. ## Aggregation Settings On the Aggregation Settings page, configure the aggregation parameters such as filter and page size. Use a semicolon delimiter to add multiple filter conditions. For more information about aggregation, refer to [Loading Account Data](). > [!NOTE] > > **Screenshot** > > [![Aggregation Settings]()]() 1. Enter **Account Filter** to filter accounts during aggregation. Only strings are supported as a filter condition. For multiple conditions, use a semicolon delimiter. 2. Enter the number of records per page in the **Page Size** field: - Default: 100 - Minimum: 1 - Maximum: 100 3. Select **Save**. ### Advanced Settings In the **Aggregation Settings \> Advanced Settings** section, you can provide settings for Thread Count and Connection Timeout. > [!NOTE] > > SailPoint recommends that you do not change the default settings. Changing the settings could result in performance issues. > [!NOTE] > > **Screenshot** > > [![Advanced Settings]()]() 1. Select **Enable Delta Aggregation** to aggregate accounts that have changed since the previous aggregation. A delta aggregation typically takes less time and fewer system resources than a full aggregation. 2. Select **Enable Partitioning** to process data in parallel across multiple threads. When partitioning aggregation is enabled, account aggregation is performed with the filters specified in **Account Filter**. Only accounts that matches the filter will be aggregated. The following parameters can be used in the **Account Filter** field to filter by account attributes. To include multiple conditions in the filter, separate them with an ampersand (`&`): > **`active`** > > `true`, `false`, `all` > > When set, this filters based on `active` status. > > For example, `active=true&isProv=false` returns all accounts with an active status. > **`isProv`** > > `true`, `false` > > This filters by the provider status for MisPerson. > > For example, `isProv=true` returns all accounts that have a provider status. > **`provFacilities`** > > Provide a comma separated list of `MisFacility` values. This filters accounts by providers at the specified facilities. This parameter requires `isProve=true`. > > For example, `isProve=true&provFacilities=MisFacility1, MisFacility2` returns provider accounts at MisFacility1 and MisFacility2. > **`provGroups`** > > Provide a comma separated list of MisProviderGroup values. When set this filters providers based on the specified groups. This parameter requires `isProve=true`. > > For example, `isProv=true&provGroups=nurse_general,physician_oncology` returns providers in the nurse\_general and physician\_oncology groups. 3. (Only required when **Enable Partitioning** is selected) Specify **Number of Partitioning Threads**, the connector should use to simultaneously execute the partitions. 4. Specify the time span in **Aggregation Timeout in Seconds** after which an aggregation operation should terminate. The default value is 900 seconds. 5. Specify the time span in **Connection Timeout in Seconds** after which the connection attempt should terminate. The default value is 60 seconds. 6. Specify the errors in the **Retry Error List** that should prompt the connector to attempt the aggregation again. Begin typing the error type and press Enter to add these errors to an ongoing list. The list of errors to retry appears below the field. 7. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with MEDITECH SaaS > [!NOTE] > > **Integration** > > This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager. Connecting SailPoint to your MEDITECH system allows you to manage users as accounts and roles as account-groups. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features MEDITECH SaaS connector supports the following features: #### Account Management Manage MEDITECH users as Account - Aggregation - Delta Aggregation - Partitioning Aggregation - Refresh Accounts - Create/Update - Enable/Disable - Add/Update Entitlements #### Entitlement Management Manage MEDITECH Roles as Entitlements - Aggregation # Machine Account Attributes ## Machine Account Provisioning Attributes The following table lists the attributes in the machine account creation template, including the type, generator, and description for each attribute. > [!IMPORTANT] > > Account attributes marked with an asterisk(\*) are mandatory attributes for machine account creation. | Attribute | Type | Description | | --- | --- | --- | | mnemonic | string | Mnemonic for the MIS record of the account | | nameFirst | string | First name of the account | | nameLast | string | Last name of the account | | active\* | boolean | Whether the account is active or not | | unvActive\* | boolean | Whether the associated universal record of the account is active | | nameMiddle | string | Middle name of the account | | nameOtherFirst | string | Other first name of the account | | nameOtherLast | string | Other last name of the account | | nameFull | string | Full name of the account | | namePrefix | string | Prefix for the name of the account | | nameSuffix | string | Suffix for the name of the account | | monogram | string | Monogram for the associated universal record of the account | | domainAccounts | string | Domain accounts of the account | | credentials | string | Credentials of the account | | isProvider | boolean | Whether the account is identified as a provider | | providerType | string | Type of provider for the account | | providerSpecialties | string | List of MIS provider specialties for the account | | createMISOnly | boolean | Whether the account is created as an MIS record only | For more information, refer to [Machine Identity Security Overview](). # 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](<#default-account-schema>) must be defined as strings if not specified. The MEDITECH SaaS 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. ### Default 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 | Account | | mnemonic | Group | ### Default Account Attributes The MEDITECH SaaS 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 | Unique Identifier of the person. | | mnemonic | Mnemonic for this MIS person record. | | monogram | Monogram for the associated universal record. | | active | Whether the person is active or not. | | nameFirst | First name of the person. | | nameMiddle | Middle name of the person. | | nameLast | Last name of the person. | | nameFull | Full name of the person. | | name\_prefix | Prefix for the name of the person. | | name\_suffix | Suffix fro the name of the person. | | nameOtherFirst | Other first name of the person. | | nameOtherLast | Other last name of the person. | | credentials | Credentials of the person. | | domainAccounts | Domain accounts of the person. | | isProvider | The person being identified as a provider or not (Read only attribute). | | providerType | Type of provider (Read only attribute). | | role | Role of the person. | | isSupervisor | Is the person being identified a supervisor or not. | | supervisorId | Identifier of the supervisor. | | lastEditedBy | The person who last edited the account. | | lastEditDateTime | Date the account was last edited. | | onStaff | Whether the person is on staff or not. | | providerSpecialties | List of MIS provider specialties. | | unvid | ID for the associated universal user record (Read only attribute). | > [!NOTE] > > If mnemonic value is not provided, the default value would be the first character of `firstName`, seven characters of `lastName`, and a two digit random value of the user. For example, for `firstName=Alfa`, `lastName=Bravo`, then the mnemonic would be `ABRAVO1E`. ## 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 Role Attributes The MEDITECH SaaS connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles. | Attribute Name | Description | | --- | --- | | id | Unique ID of the role. | | name | Name of the role. | | mnemonic | Mnemonic for the role. | | active | Status of the role, "active" or "inactive". | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](). ## Aggregation Errors ```text Retryable exception has occurred. Retry after 10000 MS ``` Warning message observed while performing account aggregation: **Resolution:** A retryable exception was received from MEDITECH. You can ignore this warning message and aggregation will be successful in this case. ```text Web Services Failed to Execute - connector.sdk.webservices.exception.WebServicesSdkException: {"resource":"v1/resource/error/_version/1/","detail":"resource not found"} ``` Occurs in the account aggregation: **Resolution:** Whenever there are UNV records without MIS person record present in the MEDITECH system, no records are fetched from MEDITECH and this error message is populated in the logs. You can ignore this warning message. ## Operations Errors ```text [ ConnectorException ] [ Error details ] Request execution failed. {"resource":"v1/resource/error/_version/1/","detail":"Internal Server Error"}. Status: 500 ``` Operation fails **Resolution:** Verify the MEDITECH system is up and running. There must be a smooth connection to MEDITECH system. ## Create Account Errors ```text [ ConnectorException ] [ Error details ] Request execution failed. {"resource":"v1/resource/error/_version/1/","detail":"Conflict"}. Status: 409] ``` Fails while creating account in MEDITECH **Resolution:** Verify the mnemonic value is unique and account does not exist in the MEDITECH system. ```text Cannot assign multiple roles. Ensure that only one role is selected. ``` **Resolution:** MEDITECH accounts can not be created with multiple roles. Make sure that only one role is provided while creating the account. ```text sailpoint.connector.InvalidRequestException: [ InvalidRequestException ] [ Error details ] Invalid request received to MEDITECH System. Status: 400, Output {"resource":"v1/resource/error/_version/1/","detail":"invalid mnemonic value"} ``` Create account fails in MEDITECH. **Resolution:** Verify the mnemonic value is provided with upper case letter and with a maximum of 10 characters. > [!NOTE] > > If mnemonic value is not provided, the default value would be the first character of `firstName`, seven characters of `lastName`, and a two digit random value of the user. For example, for `firstName=Alfa`, `lastName=Bravo`, then the mnemonic would be `ABRAVO1E`. ```text sailpoint.connector.InvalidRequestException: [ InvalidRequestException ] [ Error details ] Invalid request received to MEDITECH System. Status: 400, Output: {"detail":"Request Validation Failed"} ``` Create account fails in MEDITECH. **Resolution:** Verify the required mandatory parameters are provided while creating the account.