I’m an attorney and a code jockey. The legislation is incomprehensible. The regulation is worse. How do you get usable requirements from a web of interconnected, cross-referenced, external law referenced, and intentionally vaguely written liberal fantasy law that nobody gets except their personal favorite parts? That’s where the rule base is going to come from? Not likely. No doubt that’s where at least some of the garbled data is coming from for the insurers. Other data issues are probably based on trying to match fields in assorted remote dbs that have a myriad of different normalizations, and fields that should match have the data in incompatible formats. But nothing is so irresolvable as unknowable requirements.
now you're talking a real issue. if the business rules are at cross purposes and unable to resolve logically, then you have a problem with the analysis
such issues would have to be isolated and resolved... while waiting for resolution, a local override would most likely be needed.
in the early 90s i worked for one of the companies providing the tax software for one of the big 6. as i demonstrated the dependency driven calcs and human readable rules associated with the various fields (like a spreadsheet)... i was asked to implement the ability to 'override' any of the calculated fields. as such, the customer could arbitrarily change a field from 'c = a + b' to a fixed value.
this type of 'data fixing' is most likely what they intend to do with 0failurecare... which i figure was their intention all along