In version 4.12 HIMSA started enforcing validation for legacy data formats. This means that Noah will check all data being saved to the Noah database to ensure it is following the known data standard format that makes it possible for all HIMSA Member Company modules read and understand publicly formatted data.
If data is being saved to Noah and is not validating, Noah will not save the data and the module trying to save will return a validation error. It will likely be a specific test in the module that is causing the problem, not all tests.
If you see a validation error saving to Noah, for example Noah500ActionValidationFailed, HIMSA has provided an update to the data standard schema that can be run on the computer having the error. This schema update is valid for Noah version 4.12 and earlier, the update is included in Noah 4.13 and higher. Please see the information here.
For more information, contact the HIMSA Member company whose measurement module is saving the data.
Q: Why is HIMSA enforcing validation for legacy data formats?
A: Many years ago, HIMSA implemented an updated strategy with our data standards to help ensure that data would be validated before being allowed to be stored within Noah 4. This was accomplished by companies utilizing our XML/XSD based data standards. Some companies have adopted the use of the new standard format but there are still many companies that have not.
HIMSA has noted an increased number of support issues where applications making use of the new formats and run-time converters are receiving data based on older formats that contain incorrectly formatted data causing an error or in inability to read the data. HIMSA feels that we must do all that we can do to ensure applications can expect to read data in a predictable fashion.
Q: What data formats does this change impact?
A: The legacy data formats are format 100 or 200. Data formats 500 or higher are XML formatted and Noah already validates this data when saved to Noah.
Q: What will Noah do in 4.12 to validate data formatted with one of the legacy formats?
A: All legacy formats have 1-to-1 mapping to XML (as format 500). When a legacy format is saved, then Noah will step in and run-time convert the data for format 500 and then run the validation method against this data. If the data is found to be valid, it will then be allowed to be saved in the legacy format. HIMSA will not permanently store the legacy data in the converted format.
Q: What will the Noah user experience be if the data is found to not validate when saving new impacted data to Noah?
A: Noah will throw an exception and will not allow the data to be saved to Noah. How the module displays this fact will depend on each application’s development.