-
Type:
Task
-
Resolution: Applied
-
Priority:
Critical
-
None
Syndrome resolution - How does the diagnostician know whether a symptom is related to an existing condition or is of entirely new origin.
For example,
- "Server Failure for usabc.ca.com" - 12:30pm - the first symptom
- "Server Failure for usabc.ca.com" - 12:31pm - redundant symptom
- Usabc.ca.com gets fixed
- "Server Failure for usabc.ca.com" - 12:32pm - another instance of the problem
(unrelated to the original)
Original notes:
Dave: Prescription "duration" is of some assistance to the diagnostician.
Abdi: Duration is a guide, but not enough. We need a "success" symptom to close the case.
Paul: What if the practitioner notifies when the prescription has completed. Any related symptoms thereafter could be considered a new incident.
Dave: Some prescriptions will be "fire and forget". The prescription might be complete, but we can't know when the effects of the prescriptions will be complete.
Notes from Nov 5, 2009:
Alvin framed this debate as "Interoperability/Composability" versus "Implementation/Optimization".