<XML><RECORDS><RECORD><REFERENCE_TYPE>3</REFERENCE_TYPE><REFNUM>9239</REFNUM><AUTHORS><AUTHOR>McGee-Lennon,M.R.</AUTHOR><AUTHOR>Gray,P.</AUTHOR></AUTHORS><YEAR>2009</YEAR><TITLE>Keeping Everyone Happy: Multiple Stakeholder Requirements for Home Care Technology</TITLE><PLACE_PUBLISHED>Proceedings of the 3rd International Conference on Pervasive Computing Technologies for Healthcare, April 2009.</PLACE_PUBLISHED><PUBLISHER>N/A</PUBLISHER><LABEL>McGee-Lennon:2009:9239</LABEL><KEYWORDS><KEYWORD>home care systems</KEYWORD></KEYWORDS<ABSTRACT>Marilyn McGee-Lennon presented the issues involved in capturing and satisfying multiple stakeholders’ needs and requirements in the design of home care technology. Home care systems can range from simple stand-alone electro-mechanical alarms installed in a person’s home, perhaps to indicate a bath overflowing, to systems integrated into the home’s physical infrastructure that monitor patient state, perform sophisticated analyses, deliver customised information to patients and clinicians and support communication among them. The network of people involved in home care can be complex and ranges from the end user or patient themselves, to friends and family interested in their well being, and the various health and social care professionals interested directly or indirectly in the information or results that the home care system provides. With this range and number of stakeholders involved, it is crucial to adapt traditional user requirements methods, and/or develop novel methods and tools for appropriately capturing the needs, values, and goals of the different stakeholders. It is also important to allow these requirements to be monitored and adapted over time as a person’s care needs change. This talk presented some examples of user engagement work with a variety of stakeholders in home care that explored (1) the methods themselves, (2) the needs and values of the individual stakeholder groups, and (3) possible conflicts in needs and values when there are multiple stakeholder groups involved.</ABSTRACT></RECORD></RECORDS></XML>