A data innovations' customer reported that quality control rules configured to fire when there was a quality control violation were not consistently firing (running).If a rule is created and has at least three level of rules, some of the third level rules will not fire (run).This can result in a result that should have been held due to a quality control violation being erroneously released.The customer who reported the incident has stated these rules were never implemented in a live system, and no patients were harmed.Investigation is continuing to determine root cause of the issue.
|
A data innovations' customer reported that quality control rules configured to fire when there was a quality control violation were not consistently firing (running).If a rule is created and has at least three level of rules, some of the third level rules will not fire (run).This can result in a result that should have been held due to a quality control violation being erroneously released.The customer who reported the incident has stated these rules were never implemented in a live system, and no patients were harmed.Investigation is continuing to determine root cause of the issue.
|
Data innovations investigation into the root cause of this incident is complete.There was no malfunction of instrument manager.This issue involved the user configuration of a rules set that had multiple layers of rules.Due to the way the rules set was configured, under certain circumstances, the rule would not fire as expected, but under other circumstances the rule fired as expected.The device was functioning as designed, and was not a non-conformance.The customer has been provided with a new rule design, and the problem has been resolved.The rule had not been made live, the issue was caught in a test environment, and no patients were harmed.
|