When an HCO or HCP is inactivated, sub-objects (previously called child objects) on the entity might remain active. To preserve data quality and ensure that sub-objects are also inactivated, administrators and data managers can use this data maintenance User directed automated jobs that improve data quality by targeting specific data quality issues like sub-object inactivation and data deduplication detection. job to find and automatically inactivate address, license, and Parent HCO sub-objects.
Using the automated sub-object inactivation job enables administrators and data managers to do the following activities:
- Apply different inactivation rules in different countries.
For example, if a business policy requires that licenses remain active in some countries, but the policy does not apply to other countries, you can create jobs for individual countries.
- Choose the sub-objects to inactivate: addresses, licenses, or Parent HCOs.
- View inactivation logs that identify the sub-objects that were inactivated during a job.
- Track where changes originated through the Revision History.
This feature is enabled by default.
Applicable records and fields
Only locally managed sub-objects can be updated. This includes locally managed sub-objects on Veeva mastered records or third party mastered records.
Sub-objects can be inactivated on records with the following statuses:
- HCPs - Dead, Inactive, Retired
- HCOs - Closed, Inactive
Note: Safeguards are in place to ensure that sub-objects are not inactivated on active HCOs and HCPs.
Considerations for US Veeva OpenData records
There might be inactive HCPs with active and unexpired State Licenses and DEA Registrations in US OpenData in Network. State License and DEA record status is determined by evidence provided by the source. There might be a delay in the timing between when an HCP is inactivated and when the State Board or DEA updates the License or Registration.