Troubleshooting Tips

Review these tips when you troubleshoot inbound API calls with Health Cloud Integration.

While calling Health Cloud Integration Inbound APIs, if you’re unable to see the AccountAccountRelation or ContactContactRelation objects, verify if you have enabled the group membership settings.

To resolve this issue:

  1. From Setup, in the Quick Find box, enter Group Membership Settings, and then select Group Membership Settings.
  2. Enable the group membership settings.
  3. Save your changes.

While calling Health Cloud Integration Inbound APIs, the system throws an error that you don’t have field-level security enabled for a field. For example, when you try to access the AdmissionType column on the CareRequest object with field level security disabled, you get this error:

No such column 'AdmissionType' on entity 'CareRequest'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

To resolve this error:

  1. From Setup, open Object Manager, and then in the Quick Find box, enter the name of the object that contains the field.
  2. Select the object, and then click Fields & Relationships.
  3. Select the field you want to modify.
  4. Click Set Field-Level Security.
  5. Specify the field's access level.
  6. Save your changes.

While calling Care Management Inbound API, if you receive an error response related to accessing CarePlan entities, verify if you have enabled Care Plan settings.

sObject type 'CarePlan' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.

To resolve this error:

  1. From Setup, in the Quick Find box, enter Care Plan Settings, and then select Care Plan Settings.
  2. Enable the care plan settings.
  3. Save the changes
  4. From Setup, in the Quick Find box, enter Permission Sets, and then click Permission Sets.
  5. Select the Care Plans Access permission set.
  6. Click Manage Assignments and then Add Assignments.
  7. Select the checkboxes next to the names of the users you want to assign to the permission set, and click Next.
  8. Optionally, select an expiration date for the user assignment to expire. For more information, see Permission Set and Permission Set Group Assignment Expiration in Salesforce Help.
  9. Click Assign.

While calling RelatedPerson Post resource under Admin API, if the response returns this error, verify if there is a default picklist value set. If the default value is not set, add a Unknown picklist value and make it default.

To resolve this issue, add Unknown picklist values to PersonLanguage.SpeakingProficiencyLevel and PersonLanguage.WritingProficiencyLevel and make this value default.

  1. From Setup, open Object Manager.
  2. In the list of objects, click Person Language.
  3. From the Contact details, click Fields & Relationships.
  4. Click Speaking Proficiency Level.
  5. In Values, click New.
  6. Type the name of the new value as Unknown.
  7. Click Save.

Now, you can see the new field as an option under the preferred value on a Speaking Proficiency Level record.

Repeat the same steps for the Writing Proficiency Level.

While accessing the patient API, if you receive this error response, verify if you have enabled users to add reciprocal roles.

To resolve this issue, follow the steps in the Enable Users to add Reciprocal Roles.

While accessing the administration APIs, the system throws this error:

This issue occurs when there are more than one person accounts in the org.

To resolve this issue, pass the recordTypeLabel in request and specify which person account the patient record must be associated with.

Example: payload.recordTypeLabel = “Patient”

For Practitioner and RelatedPerson, use payload.recordTypeLabel to associate the account with a recordType. The default RecordType is PersonAccount.