Health Cloud: Care Request History object not available as a reportable object or for custom report types

Use the following workarounds to meet reporting and audit requirements on Care Request when the history object is not exposed.

Cause 1: Care Request History object is not exposed for reporting
1. Confirm the limitation. Navigate to Setup > Object Manager > Care Request [CareRequest] > Fields & Relationships and verify that field-level history tracking is already enabled on the fields you need.
2. Navigate to Setup > Report Types and click New Custom Report Type.
3. In the Primary Object picklist, search for "Care Request History". The object will not appear — this is expected because CareRequestHistory is not exposed as a reportable entity by the HealthCloudGA managed package.
4. As a workaround, build a Case-based report. Click New Custom Report Type, select Case [Case] as the Primary Object, then add Care Request [CareRequest] and any Care Request extension objects as related (secondary) objects. Save and deploy the report type.
5. For long-term audit retention, enable Field Audit Trail on the tracked Care Request fields and query history through the Tooling/REST API where the CareRequestHistory rows are accessible programmatically, even though they are not exposed in the report builder.
6. To request platform exposure of CareRequestHistory as a reportable object, submit an idea on the Salesforce IdeaExchange and have affected users vote on it. The Health Cloud Product team tracks these requests for future releases.

Cause 2: Enable Reports, Track Activities, and Track Field History checkboxes are greyed out on Care Request
1. Navigate to Setup > Object Manager > Care Request [CareRequest] > Details.
2. Observe that the Enable Reports, Track Activities, and Track Field History checkboxes cannot be edited. This is expected: the object is delivered by the HealthCloudGA managed package, and these object-level toggles are controlled by the package, not the subscriber org.
3. Do not open a support case to request that these checkboxes be enabled — Salesforce Support cannot toggle managed-package object settings at the platform level. Use the Case-based custom report type from Cause 1 step 4 to satisfy reporting requirements.
4. For activity tracking on related records, enable Activities on a parent or related custom object that you do control, and relate Care Request records to it through a lookup.

Confirm the issue is resolved by opening Setup > Report Types, creating the Case-primary custom report type that includes Care Request as a related object, then building a report from it and verifying that Care Request field values and related Case data appear as expected.