Health problems in elderly patients during the first post-stroke year

BACKGROUND: A wide range of health problems has been reported in elderly post-stroke patients. AIM: The aim of this study was to analyse the prevalence and timing of health problems identified by patient interviews and scrutiny of primary health care and municipality elderly health care records during the first post-stroke year. METHODS: A total of 390 consecutive patients, ≥65 years, discharged alive from hospital after a stroke event, were followed for 1 year post-admission. Information on the health care situation during the first post-stroke year was obtained from primary health care and municipal elderly health care records and through interviews with the stroke survivors, at 1 week after discharge, and 3 and 12 months after hospital admission. RESULTS: More than 90% had some health problem at some time during the year, while based on patient record data only 4-8% had problems during a given week. The prevalence of interview-based health problems was generally higher than record-based prevalence, and the ranking order was moderately different. The most frequently interview-reported problems were associated with perception, activity, and tiredness, while the most common record-based findings indicated pain, bladder and bowel function, and breathing and circulation problems. There was co-occurrence between some problems, such as those relating to cognition, activity, and tiredness. CONCLUSIONS: Almost all patients had a health problem during the year, but few occurred in a given week. Cognitive and communication problems were more common in interview data than record data. Co-occurrence may be used to identify subtle health problems.

Reasoning about Requirements Evolution Using Clustered Belief Revision

During the development of system requirements, software system specifications are often inconsistent. Inconsistencies may arise for different reasons, for example, when multiple conflicting viewpoints are embodied in the specification, or when the specification itself is at a transient stage of evolution. These inconsistencies cannot always be resolved immediately. As a result, we argue that a formal framework for the analysis of evolving specifications should be able to tolerate inconsistency by allowing reasoning in the presence of inconsistency without trivialisation, and circumvent inconsistency by enabling impact analyses of potential changes to be carried out. This paper shows how clustered belief revision can help in this process. Clustered belief revision allows for the grouping of requirements with similar functionality into clusters and the assignment of priorities between them. By analysing the result of a cluster, an engineer can either choose to rectify problems in the specification or to postpone the changes until more information becomes available.