Review and add validation rules to Natural objects

Background and Strategy

As discussed in previous tasks (see Create and run Semantic Mapping objects and 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.