--- title: "Review and add validation rules" slug: "bpw-cnol-review-and-add-validation-rules-to-natural-objects" updated: 2022-12-21T20:54:14Z published: 2022-12-21T20:54:14Z canonical: "docs.ursahealth.com/bpw-cnol-review-and-add-validation-rules-to-natural-objects" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.ursahealth.com/llms.txt > Use this file to discover all available pages before exploring further. # Review and add validation rules to Natural objects ### Background and Strategy As discussed in previous tasks (see [Create and run Semantic Mapping objects](/v1/docs/bpw-sm-create-and-run-semantic-mapping-objects) and [Create and run Local Transform objects](/v1/docs/bpw-clto-create-and-run-local-transform-objects)), Ursa Studio provides users with the ability to define *Validation Rules* that are executed when an object is ELTed. Just as in those earlier scenarios, it can be useful to flag suspicious or illegal data patterns in the *Natural Object Layer* using this same feature. Existing *Natural* objects in the *Ursa Health Core Data Model* come pre-configured with a starting set of validation rules. For example, a warning will be triggered if any institutional claim header records is missing a Claim Covered Start Date, Billing Provider ID, or CMS Type of Bill Code. To the extent the integration of a new data source might have inspired some paranoia about a particular field or data pattern, it might be useful to set up a new *Validation Rule* to catch the most worrisome failure modes. Similarly, if the integration resulted in the creation of new *Natural* objects, a set of appropriate *Validation Rules* should be considered.