--- title: "Validate the Local Transform object results" slug: "bpw-clto-validate-the-local-transform-object-results" updated: 2022-11-09T14:59:38Z published: 2022-11-09T14:59:38Z canonical: "docs.ursahealth.com/bpw-clto-validate-the-local-transform-object-results" stale: true --- > ## 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. # Validate the Local Transform object results ### Background and Strategy When the *Local Transform Layer* objects have been completed, a holistic validation of the newly created objects should be performed. As with the prior validation exercises, the main venue will be the *Case Review* screen for each object, with useful configurations of sorting and column pinning -- as well as filtering to suspicious or otherwise interesting cases -- memorialized as boards. ### Key Diagnostics / Heuristics - Are the Source ID and Source Data Effective Datetime fields published for every object and populated on each record? - Are critical fields (e.g., Patient ID, various Provider ID fields) sometimes or always NULL? - Is the construction of the *Data Model Key* identifiers (especially *Patient ID* and *Provider ID* fields) consistent? (Look especially for the inadvertent omission of prepended tokens described in [Determine the mappings for identifier fields](/v1/docs/bpw-sm-determine-the-mappings-for-identifier-fields).) - Are service line numbers well-formed, always with a single record with line number = 1. - Do the minimum and maximum values of fields, especially numeric and date columns, fall within the expected range? - Do any fields still contain special characters or strings meant to represent missing or NULL data? - For objects representing final action claims or billing records, are there any records with negative allowed or paid amounts?