Status Submitted when an item is logged and reported for repair. – Assigned when an item is assigned for repair. – Opened when an anomaly is assigned for correction. – Deleted when an item is originally reported as an anomaly, but later deleted because – the item is either a duplicate or not an anomaly. Resolved - when an anomaly is corrected and sent for review or verification. Re-Opened when an anomaly is closed and then reopened for modification. – Returned - when an anomaly is reviewed, verified as "incorrect", and returned to author. Verified - when an anomaly is reviewed and verified as "correct". Closed - when an anomaly is successfully reviewed and closed with a resolution and resolution date. Deferred - when an anomaly is designated for correction at a later date. Duplicated when an item is assessed to be a duplicate of a prior record. – Escalated when an item requires evaluation by management. – Note: The statuses listed above reflect the use of Rational ClearQuest for anomaly tracking. Manual tracking may use a simplified list of statuses. The classification of anomalies according to their potential damage to the software, Impact systems, patient, personnel or operating systems. They are classified in three levels: High Impact - an error or absence of functionality that may severely jeopardize patient or personnel safety; adversely impacts all users; represents a significant value or cost; is governed by Congressional mandate; affects either a large database or critical data; requires Food and Drug Administration (FDA) certification/approval; affects Veterans Integrated Service Network (VISN) issues; or negatively impacts the interdependence of applications. Medium Impact - an error or absence of functionality that adversely affects the safety of Veteran issues or users of large applications, i.e., Pharmacy, Lab, etc.; represents a high value or cost; sponsored or initiated by the National Program Office; or negatively impacts essential operational or business processing. Low Impact - an error or absence of functionality that may cause operator/user inconvenience and minimally affects operational functionality.
Status Submitted – when an item is logged and reported for repair. Assigned – when an item is assigned for repair. Opened – when an anomaly is assigned for correction. Deleted – when an item is originally reported as an anomaly, but later deleted because the item is either a duplicate or not an anomaly. Resolved - when an anomaly is corrected and sent for review or verification. Re-Opened – when an anomaly is closed and then reopened for modification. Returned - when an anomaly is reviewed, verified as "incorrect", and returned to author. Verified - when an anomaly is reviewed and verified as "correct". Closed - when an anomaly is successfully reviewed and closed with a resolution and resolution date. Deferred - when an anomaly is designated for correction at a later date. Duplicated – when an item is assessed to be a duplicate of a prior record. Escalated – when an item requires evaluation by management. Note: The statuses listed above reflect the use of Rational ClearQuest for anomaly tracking. Manual tracking may use a simplified list of statuses. Impact The classification of anomalies according to their potential damage to the software, systems, patient, personnel or operating systems. They are classified in three levels: High Impact - an error or absence of functionality that may severely jeopardize patient or personnel safety; adversely impacts all users; represents a significant value or cost; is governed by Congressional mandate; affects either a large database or critical data; requires Food and Drug Administration (FDA) certification/approval; affects Veterans Integrated Service Network (VISN) issues; or negatively impacts the interdependence of applications. Medium Impact - an error or absence of functionality that adversely affects the safety of Veteran issues or users of large applications, i.e., Pharmacy, Lab, etc.; represents a high value or cost; sponsored or initiated by the National Program Office; or negatively impacts essential operational or business processing. Low Impact - an error or absence of functionality that may cause operator/user inconvenience and minimally affects operational functionality.