This article explains why Health Cloud history objects do not appear in the Custom Report Type builder and how to retrieve the field history data using supported alternatives.
After you enable Field History Tracking on a Health Cloud clinical object such as MedicationRequest, CareRequest, HealthcareProvider, MemberPlan, HealthcarePractitionerFacility, CareBarrier, DiagnosticSummary, or PatientMedicalProcedure, the platform creates the associated history sub-object (for example MedicationRequestHistory, CareRequestHistory, HealthcareProviderHistory, MemberPlanHistory, HealthcarePractitionerFacilityHistory, CareBarrierHistory, DiagnosticSummaryHistory, PatientMedicalProcedureHistory) and starts capturing changes.
However, when you go to Setup > Custom Report Types > New Custom Report Type and search for the history object, the history sub-object is not selectable as the Primary Object, and it does not appear in the Related Objects dropdown when the clinical object is the Primary Object.
Common symptoms include:
1. The Medication Request History object cannot be found when creating a report type, even though field history tracking is enabled
2. Account & Account History, Case & Case History appear as separate objects in the report builder, but only Care Request is available without Care Request History
3. HealthcareProvider field history does not appear in the FieldHistoryArchive object
This behavior is by design for Industry Cloud / Health Cloud standard objects: Although the platform documentation confirms that History is available for tracked fields of these objects, the Custom Report Type builder currently does not expose those Industry Cloud history objects. The behavior affects all Health Cloud orgs on Enterprise, Performance, Unlimited, and Developer editions in Lightning Experience.
The history data itself is captured and is queryable through SOQL and through the History related list on the parent record.
Step 1: Confirm Field History Tracking is enabled on the clinical object
Navigate to Setup > Object Manager > [Clinical Object, for example MedicationRequest, CareRequest, HealthcareProvider, MemberPlan, HealthcarePractitionerFacility] > Fields & Relationships > Set History Tracking. Select Enable [Object] History, select the fields to track (up to 20 standard, or up to 60 with Field Audit Trail), and click Save.
Step 2: Verify the history object exists and contains data
Open the Developer Console > Query Editor and run a SOQL query against the history object, for example:
SELECT Id, ParentId, Field, OldValue, NewValue, CreatedById, CreatedDate
FROM MedicationRequestHistory
LIMIT 10
Replace MedicationRequestHistory with CareRequestHistory, HealthcareProviderHistory, MemberPlanHistory, HealthcarePractitionerFacilityHistory, CareBarrierHistory, DiagnosticSummaryHistory, or PatientMedicalProcedureHistory as appropriate.
If rows are returned, history is being captured correctly even though the object is not exposed in the CRT builder.
Step 3: Expose the history data on the record page using the History related list (supported alternative)
Navigate to Setup > Object Manager > [Clinical Object] > Page Layouts > [Layout Name] > Related Lists. Drag the [Object Name] History related list (for example "Medication Request History") onto the layout and click Save. Users can now view per-record history directly on the record page.
Cause 1: Industry Cloud history objects are not exposed in the Custom Report Type builder
Confirm in Setup > Custom Report Types > New Custom Report Type that the history object (for example MedicationRequestHistory, CareRequestHistory, HealthcareProviderHistory, MemberPlanHistory, PatientMedicalProcedureHistory) does not appear in the Primary Object dropdown.
Confirm that with the clinical object selected as Primary, the history sub-object does not appear under "A related '[Object]' record". This is a current limitation for Industry Cloud / Health Cloud standard objects.
Workaround: Build an external report using the Salesforce Reports and Dashboards REST API, Tableau, or CRM Analytics, and source the history sub-object directly via SOQL. The history object is fully queryable through the API.
Cause 2: Master-detail children of an Industry Cloud object cannot be reported with their parent's history
If the clinical object is the detail side of a master-detail relationship, the standard "[Object] History" Custom Report Type may not be available in the CRT builder.
Workaround: Use SOQL against the history sub-object as in Step 2 above, or expose the History related list on the parent record's page layout as described in Step 3.
Cause 3: FieldHistoryArchive does not contain the data
FieldHistoryArchive is populated only when Field Audit Trail (FAT) retention policies are configured and the original field history records have aged past the standard 18-month retention window. Recently changed records remain in the [Object]History sub-object, not in FieldHistoryArchive.
Resolution: To extend retention, license Field Audit Trail and configure a HistoryRetentionPolicy on the clinical object using the Metadata API. Until records age out under that policy, query [Object]History (for example HealthcareProviderHistory) instead of FieldHistoryArchive.
Confirm the issue is resolved by:
1.Running the following query in the Developer Console:
SELECT Id, Field, OldValue, NewValue, CreatedDate
FROM [Object]History
WHERE ParentId = '[Record Id]'
2. Verifying that the field changes you expected to report on are returned
3. Viewing the [Object Name] History related list on the parent record page
005385095

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.